Checking the Syntax of RMAN Scripts in Font

Create Code39 in Font Checking the Syntax of RMAN Scripts

You can use the CHECKSYNTAX parameter to check the syntax of a script (or any RMAN command) you plan to use with RMAN. Here s an example that shows a script contained in the script file testfile that has the correct syntax: $ rman CHECKSYNTAX @/tmp/testfile Recovery Manager: Release 11.1.0.6.0 - Production on Thu Mar 27 11:09:16 2008 Copyright (c) 1982, 2007, Oracle. All rights reserved. RMAN> # command file with correct syntax 2> restore database; 3> recover database; 4> The cmdfile has no syntax errors Recovery Manager complete. $

The scripts you ve seen so far are local scripts, since you can use them only in the database in which you create them. You can also create and execute an RMAN global script against a database registered in the recovery catalog, providing your RMAN client is connected to the recovery catalog and the target

database simultaneously. You can get databases to share RMAN scripts if they connect to the database with the RMAN catalog. The following statement shows the syntax for creating a global script: RMAN> CREATE GLOBAL SCRIPT global_full_backup { BACKUP DATABASE PLUS ARCHIVELOG; DELETE OBSOLETE; } created global script global_full_backup RMAN> You execute a global script in the same way as a local script: RMAN> RUN {EXECUTE GLOBAL SCRIPT global_full_backup};}

The following PRINT SCRIPT command prints out the contents of the global script example: RMAN> PRINT GLOBAL SCRIPT global_full_backup; printing stored global script: global_full_backup {backup database plus archivelog ; delete obsolete; } RMAN>

The LlST . . . SCRIPT NAMES command lets you view the names of all the scripts you stored in a recovery catalog. Here s an example: RMAN> LIST SCRIPT NAMES; The LIST . . . SCRIPT NAMES command shows all local and global scripts that you can execute for the database you are currently connected to. To view the script names for all the databases registered in the recovery catalog, execute the LIST ALL SCRIPT NAMES command instead.

Use the DELETE SCRIPT command to delete a stored script from the recovery catalog, as shown here: RMAN> DELETE SCRIPT 'my-script'; If the script is global, use the DELETE GLOBAL SCRIPT command instead.

You can create a dynamic stored script by specifying substitution variables while creating a script with the CREATE SCRIPT command. The USING clause lets you specify values for the substitution variables in a command file. Follow these steps to create and use a dynamic stored script: 1. Create a command file that you can use to create a stored script. In our example, the command file is named myscript.rman, and it contains the CREATE SCRIPT command to create the new stored script. Use substitution variables for values that you want to assign dynamically.

RMAN> CREATE SCRIPT quarterly { ALLOCATE CHANNEL c1 DEVICE TYPE sbt PARMS 'ENV=(OB_MEDIA_FAMILY=&1)'; BACKUP TAG &2 FORMAT '/disk2/bck/&1%U.bck' KEEP FOREVER RESTORE POINT &3 DATABASE; } The QUARTERLY script (created using the command file myscript.rman) uses three substitution variables: OB_MEDIA_FAMILY to specify the name of the tape set, FORMAT to specify the format string, and RESTORE_POINT to specify the name of the restore point. 2. Connect to the target database and the recovery catalog, specifying initial values for the three substitution variables in the QUARTERLY script. Place the values after the keyword USING, as in the following example: $ rman target / catalog rman@catdb USING arc_backup bck0908 FY08Q3 Note that at this point, you re merely logged in to RMAN: specifying the USING clause during the RMAN login enables you to pass values for the three substitution variables in the script. You ll create the script in the next step. 3. Once you log in to RMAN, execute the command file myscript.rman to create the stored script QUARTERLY. RMAN> @catscript.rman RMAN now has a new stored script named QUARTERLY, which can accept different values for its three substitution variables. Now that you have created the dynamic stored script, you can execute it every quarter by passing the correct values for the three substitution variables. For example, I can assign the following values to the substitution variables: arch_bkp for the media family, bkp1208 as part of the FORMAT string, and FY0804 as the name of the restore point. Here s how to invoke the stored script with those parameter values: RUN { EXECUTE SCRIPT quarterly USING arch_bkp bkp1208 FY08Q4; } As the example shows, it s very easy to pass different runtime values for the variables inside the dynamic stored script.