This appendix provides a series of checklists and additional information to assist in troubleshooting problems in using BusinesSuite Module for Oracle version 2.1. The checklists are designed to enable a minimal installation of the product.
There is a checklist for each of four different sections of the NetWorker documentation—the installation chapter in this book, and Chapters 3 through 5 of the IRIX NetWorker BusinesSuite Module for Informix Administrator's Guide. For more details on any of the points in these checklists, see the relevant section of the specific document.
If you run into any problems during an upgrade to BusinesSuite Module for Oracle version 2.1 or during a new installation of the product, use the following checklist to verify that you have performed all the required steps:
Check the prerequisites for the versions of the Oracle7 Server, Enterprise Backup Utility, SQL*Net, and the NetWorker server for your particular operating system. For details, refer to the latest compatibility matrixes on Legato's Web site at http://www.legato.com/prod/dmo_mat.html and on Oracle's Web site at http://www.oracle.com/products/servers/ebu/html/availmat.html .
Visit the Silicon Graphics Web site (http://bits.csd.sgi.com/digest/patches/ ) for any patches required for your particular system.
Check the disk and memory requirements for BusinesSuite Module for Oracle version 2.1 and the Enterprise Backup Utility.
Install an up-to-date version of NetWorker client software on the database host.
Install the NetWorker server software on the backup server. The backup server is the server with the tape device(s) attached to it.
To upgrade from Database Module for Oracle version 1.0.x to BusinesSuite Module for Oracle version 2.1:
Remove the obkasm symbolic link.
Remove the nsr.cf and script.cf files, if desired. Use the environment variable values from these scripts in configuring the nsrdmo script.
Remove directives from Oracle clients in the NetWorker server configuration.
Remove the Oracle directive from the NetWorker server configuration.
Remove all entries from Remote access list for each Oracle client in NetWorker.
Review the points below for a new BusinesSuite Module for Oracle installation.
For a new installation of BusinesSuite Module for Oracle version 2.1:
If you are installing the product from CD-ROM software distribution, mount the CD-ROM.
With IRIX, run the appropriate inst command as root to install the software.
If the Enterprise Backup Utility has not yet been installed, install it as follows:
Run the command orainst to install the Enterprise Backup Utility executables.
Create the Enterprise Backup Utility Backup Catalog database.
Install the Backup Catalog using the command orainst.
Run root.sh as the superuser.
If you purchased the BusinesSuite Module for Oracle product:
Install the BusinesSuite Module for Oracle license, perhaps with LicenseManager.
Enable the BusinesSuite Module for Oracle software using nsrcap.
If you are evaluating the BusinesSuite Module for Oracle product:
If the NetWorker server has license codes already enabled, enter a temporary license for your BusinesSuite Module as provided. This license lasts for 45 days.
If the NetWorker server license is not yet enabled, (for example, it is still in 30-day evaluation mode), no BusinesSuite Module for Oracle enabler is required for 30 days. After that period, the NetWorker server requires enabling, and you can enter the temporary enabler as provided to continue evaluating the module for another 45 days.
Prerequisites:
Have you completed the “Installation Procedures—Checklist”?
Procedure:
Register the database in the Enterprise Backup Utility Backup Catalog, using an appropriate obackup command script.
Add the oracle owner to the NetWorker server's valid Administrator list as oracle@db_servername, where db_servername is the fully qualified name of the database server machine.
Even if you plan to do only scheduled backups, complete Chapter 4 of the Administrator's Guide before going on to Chapter 5. This will ensure that the basic connection is set up correctly before you attempt scheduled database backups.
Prerequisites:
Have you completed the installation checklist and the checklist for Chapter 3?
Procedure:
Be sure you are logged in as the oracle owner.
Set the NSR_SERVER and OBK_HOME environment variables.
Unset the NSR_CLIENT environment variable, if required.
Create an obackup command script named partial_ts2, to perform a backup of a tablespace of manageable size.
Run obackup partial_ts2, to execute the sample on-demand backup.
To manually back up the NetWorker server's client indexes and bootstrap file, run the following command on the NetWorker server:
% savegrp -O -l full -P printer_name -c client_name -c networker_servername
After the on-demand backup completes successfully, try a scheduled backup.
Prerequisites:
Have you completed all the checklists above?
Procedure:
Copy the nsrdmo.sh script template to a new file such as nsrdmo2.
Modify the nsrdmo2 file to create your own customized script:
Verify that the OBK_HOME environment variable is set to the home directory of Enterprise Backup Utility.
Verify that the PATH environment variable is set to include the path to the Enterprise Backup Utility executables and the NetWorker program mminfo.
If you have a UNIX shell script to perform pre-processing commands before the database backup (for example, to shut down the database), specify this with the PRECMD variable in nsrdmo2.
If you have a UNIX shell script to perform post-processing commands after the database backup (for example, to restart the database), specify this with the POSTCMD variable in nsrdmo2.
Set up a NetWorker schedule for the Oracle backups. Remember to select level full to execute any Oracle backup and level skip to skip an Oracle backup. No other levels are valid.
Set up the database server as a NetWorker client, by performing the following on the NetWorker server:
Create a new client resource, such as dmo_client.
Select Default as the group for the client.
Be sure that the save set entry is the full pathname of the obackup command script.
Enter nsrdmo2 in the Backup command field.
Specify all the known aliases for the database host.
To test the scheduled backup using the NetWorker administrator program on the NetWorker server, select Group Control from the Server menu, select the Default group, and click Start. Verify that the database is saving to tape, and check the savegroup completion message to verify that the database backup was successful.
To stop BusinesSuite Module for Oracle processes on the client, use an obackup cancel script. BusinesSuite Module for Oracle does not currently support use of the Stop button in the Group Control window for scheduled backups.
If you are running scheduled backups from NetWorker, be aware that the default Instance Manager configuration as provided by Oracle could cause those scheduled NetWorker backups to appear to fail under certain circumstances. The nsrdmo script tunes the Instance Manager environment variables in order to avoid this problem. The following Instance Manager environment variable settings from the nsrdmo script are used if a new Instance Manager process needs to be started by the Enterprise Backup Utility when running a scheduled save from NetWorker:
BRD_TOT_TIME = 300 5 minutes BRD_SAMP_TIME = 1 1 second BRD_ERR_TIME = 1 1 second BRD_RETRIES = 1 |
Refer to the section “Instance Manager Environment Variables” on page 6-5 of the Oracle7 Enterprise Backup Utility Administrator's Guide Release 2.1 for more detailed information on setting these four variables. The nsrdmo script itself also contains more comments on the settings of these variables.
OBK-2464: Internal error. Instance Manager process was not started |