HP Archive Backup System for OpenVMS Guide to Operations

HP Archive Backup System for OpenVMS Guide to Operations HP Archive Backup System for OpenVMS Guide to Operations

h71000.www7.hp.com
from h71000.www7.hp.com More from this publisher
06.11.2014 Views

System Backup to Tape for Oracle Databases 9.1 Linking System Backup to Tape with the Oracle Server 1. Linking SBT with the Oracle server 2. Defining the logical MDMS$SBT_TRACE_LEVEL 3. Configuring ABS 4. Testing the configuration of SBT 5. Using SBT with Oracle's Recovery Manager 6. Using the show catalog command 7. Using the MDMS scheduler 8. System Backup to Tape defaults 9. System Backup to Tape logicals names 10. System Backup to Tape Restrictions 11. Troubleshooting tips 9.1 Linking System Backup to Tape with the Oracle Server Note This section is not applicable for Oracle9i Release 2 (9.2.0.2). If you are using Oracle9i Release 2 (9.2.0.2), please skip this section (9.1) and refer to section 9.2 for configuring SBT with Oracle9i Release 2 (9.2.0.2). Before you can use SBT, you must link the SYS$SHARE:MDMS$SBTSHR_MA64.EXE shareable image with the Oracle server. This is a one time procedure. After performing this procedure, you can install a new release of ABS/MDMS and not have to relink the Oracle server to the new release of SBT. Note This linking of SBT to the Oracle server is not the same as described in the Oracle installation guide. The procedure in the Oracle installation guide does not use a shareable image and has you shutdown the database and relink with the vendors product with each new release. With the SBT shareable image and this procedure, you only have to shutdown the database and link one time. This section takes you through the procedure to link the SYS$SHARE:MDMS$SBTSHR_MA64.EXE shareable image with the Oracle server: 1. Testing Oracle's Recovery Manager 2. Authorizing privileges and Granting rights to the Oracle server account 3. Editing Oracle's link option file and command procedures 4. Shutdown the database 5. Relinking the ORA_RDBMS: executables 6. Startup the database 7. Retesting Oracle's Recovery Manager 9-2 System Backup to Tape for Oracle Databases

System Backup to Tape for Oracle Databases 9.1 Linking System Backup to Tape with the Oracle Server 9.1.1 Testing Oracle's Recovery Manager before linking System Backup to Tape Before doing the configuration for SBT, you should make sure that Oracle's Recovery Manager is setup and you are able to access it. If you have been using Oracle's Recovery Manager to write to disk, then you are ready to switch to SBT. If you have not been using Oracle's Recovery Manager, you should try a backup of a tablespace as shown in Example 9–1. Example 9–1 Oracle's Recovery Manager Backup of System Tablespace to Disk RMAN> run 2> { 3> allocate channel d1 type disk; 4> backup tablespace system; 5> release channel d1; 6> } Example 9–1 created the file ORA_DB:02D9MBV4_1_1.;1 on my system. Of course your file name will be different. If everything works then you are ready to link Oracle to SBT. If this step did not work, then your Oracle Recovery Manager is not setup correctly. You need to correct this before proceeding. 9.1.2 Authorizing privileges and granting rights to the Oracle server account Before using SBT, you must authorize the VOLPRO privilege and grant the MDMS_APPLICATION identifier to the Oracle server database administrator account. The VOLPRO privilege allows the Oracle server to mount volumes that belong to ABS. All volumes belong to ABS. The MDMS_APPLICATION allows the Oracle server to use the objects in the MDMS database. The following example shows the commands that modify the privileges and grant the right to an account called ORACLE9I: $ MCR AUTHORIZE UAF> MODIFY ORACLE9I/PRIVILEGES=VOLPRO UAF> GRANT/ID MDMS_APPLICATION ORACLE9I UAF> EXIT $ Note Be sure to logout and log back in so that the privileges and rights take effect. 9.1.3 Editing Oracle's Link Option File and Command Procedures In order to link the SBT shareable image, you must change Oracle's link option file and command procedures. This section covers what you need to do for Oracle8i and Oracle9i. 9.1.3.1 Editing Oracle8i Link Option File and Command Procedures In order to link the SBTshareable image, you must change three of Oracle's files. Before editing these three files, we suggest that you make a copy of the file. In each file, you may need to comment out the line ora_rman_mml_64/lib and/or add the line SYS$SHARE:MDMS$SBTSHR_MA64.EXE/SHARE. The following are the three files and an example of each file with the line to comment out and/or the line to be added commented: • ORA_UTIL:RDBMS_RMAN_NOSHARE.OPT as shown in Example 9–2. • ORA_RDBMS:LORACLE_64.COM as shown in Example 9–3. • ORA_UTIL:LOUTL.COM as shown in Example 9–4 System Backup to Tape for Oracle Databases 9–3

<strong>System</strong> <strong>Backup</strong> <strong>to</strong> Tape <strong>for</strong> Oracle Databases<br />

9.1 Linking <strong>System</strong> <strong>Backup</strong> <strong>to</strong> Tape with the Oracle Server<br />

9.1.1 Testing Oracle's Recovery Manager be<strong>for</strong>e linking <strong>System</strong> <strong>Backup</strong> <strong>to</strong> Tape<br />

Be<strong>for</strong>e doing the configuration <strong>for</strong> SBT, you should make sure that Oracle's Recovery Manager<br />

is setup and you are able <strong>to</strong> access it. If you have been using Oracle's Recovery Manager <strong>to</strong> write<br />

<strong>to</strong> disk, then you are ready <strong>to</strong> switch <strong>to</strong> SBT. If you have not been using Oracle's Recovery Manager,<br />

you should try a backup of a tablespace as shown in Example 9–1.<br />

Example 9–1 Oracle's Recovery Manager <strong>Backup</strong> of <strong>System</strong> Tablespace <strong>to</strong> Disk<br />

RMAN> run<br />

2> {<br />

3> allocate channel d1 type disk;<br />

4> backup tablespace system;<br />

5> release channel d1;<br />

6> }<br />

Example 9–1 created the file ORA_DB:02D9MBV4_1_1.;1 on my system. Of course your file<br />

name will be different. If everything works then you are ready <strong>to</strong> link Oracle <strong>to</strong> SBT. If this step<br />

did not work, then your Oracle Recovery Manager is not setup correctly. You need <strong>to</strong> correct this<br />

be<strong>for</strong>e proceeding.<br />

9.1.2 Authorizing privileges and granting rights <strong>to</strong> the Oracle server account<br />

Be<strong>for</strong>e using SBT, you must authorize the VOLPRO privilege and grant the<br />

MDMS_APPLICATION identifier <strong>to</strong> the Oracle server database administra<strong>to</strong>r account. The<br />

VOLPRO privilege allows the Oracle server <strong>to</strong> mount volumes that belong <strong>to</strong> ABS. All volumes<br />

belong <strong>to</strong> ABS. The MDMS_APPLICATION allows the Oracle server <strong>to</strong> use the objects in the<br />

MDMS database.<br />

The following example shows the commands that modify the privileges and grant the right <strong>to</strong> an<br />

account called ORACLE9I:<br />

$ MCR AUTHORIZE<br />

UAF> MODIFY ORACLE9I/PRIVILEGES=VOLPRO<br />

UAF> GRANT/ID MDMS_APPLICATION ORACLE9I<br />

UAF> EXIT<br />

$<br />

Note<br />

Be sure <strong>to</strong> logout and log back in so that the privileges and rights take effect.<br />

9.1.3 Editing Oracle's Link Option File and Command Procedures<br />

In order <strong>to</strong> link the SBT shareable image, you must change Oracle's link option file and command<br />

procedures. This section covers what you need <strong>to</strong> do <strong>for</strong> Oracle8i and Oracle9i.<br />

9.1.3.1 Editing Oracle8i Link Option File and Command Procedures<br />

In order <strong>to</strong> link the SBTshareable image, you must change three of Oracle's files. Be<strong>for</strong>e editing<br />

these three files, we suggest that you make a copy of the file. In each file, you may need <strong>to</strong> comment<br />

out the line ora_rman_mml_64/lib and/or add the line<br />

SYS$SHARE:MDMS$SBTSHR_MA64.EXE/SHARE. The following are the three files and an<br />

example of each file with the line <strong>to</strong> comment out and/or the line <strong>to</strong> be added commented:<br />

• ORA_UTIL:RDBMS_RMAN_NOSHARE.OPT as shown in Example 9–2.<br />

• ORA_RDBMS:LORACLE_64.COM as shown in Example 9–3.<br />

• ORA_UTIL:LOUTL.COM as shown in Example 9–4<br />

<strong>System</strong> <strong>Backup</strong> <strong>to</strong> Tape <strong>for</strong> Oracle Databases 9–3

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!