Troubleshooting Oracle Configurations

Table of Contents

Database Readiness Check

The Database Readiness Check is available on UNIX clients and verifies the pre-requisites are met for the Oracle Agent to successfully perform backups and restores.

It verifies the following configuration:

  1. The database user has read and write permissions on the SnapProtect registry, log files and base directories.
  2. The database user is a member of the SnapProtect install group.
  3. RMAN can load the CommVault SBT Media Library.

You can run the Database Readiness Check from the command line on the client with the verify option, or the fix option which interactively fixes the permission failures. The Database Readiness Check automatically handles the restart when the fixes require the SnapProtect services to be restarted.

For a root install, the Database Readiness Check uses root credentials to access the CommServe computer. For a non-root install, the Database Readiness Check prompts for the CommCell Console credentials to access the CommServe computer.

Navigate to the Simpana_Install_Dir/iDataAgent directory and execute the following command.

./DBAgentReadinessCheck.sh -o <fix|verify> -f <log_file_full_path>

Option Description
o Specify whether the Database Readiness Check verifies of fixes the permissions.
  • verify - This is the default option and performs the verification as specified in the Introduction
  • fix - This option fixes the permissions
f Specify the full path for the log file. The default log file path is "/tmp/CV_DBAgentReadinessCheck.log".

Follow these steps when you run the Database Readiness Check.

  1. Run it with the verify option.
  2. Check the output. If there are no failed cases, then the database agent is ready for backup and restore operations.
  3. If there are permission failures, use the -o fix option to correct the database user permissions. The Database Readiness Check prompts for a user confirmation before changing the permissions. See Example of Fixing the Database User Permissions.

Example of a Database Agent Ready for Backups and Restores

This is an example of the Database Readiness Check for a database agent that is ready for backups and restores.

[root@dbserve4 iDataAgent]# ./DBAgentReadinessCheck.sh -o verify
****************************************************************
Tool: Check Readiness of "Database Agents"
****************************************************************
- Simpana instance: [Instance004]
- Simpana install group: [dba]
- Simpana database agents installed:
- Oracle Agent:
   - Instance: [rman10g] DbHome: [/oracle/oracle10g]
   - Instance: [trialdb] DbHome: [/oracle/oracle10g]
   - Instance: [auto] DbHome: [/oracle/oracle10g]
   - Instance: [LUN_DUP] DbHome: [/oracle/oracle10g]
   - Instance: [LREPDB] DbHome: [/oracle/oracle10g]
   - Instance: [RDMDB] DbHome: [/oracle/oracle10g]
Checking [Oracle] Agent Readiness
*****************************************
- Database user name:[oracle]
- Database home: [/oracle/oracle10g]
- Check if user is member of Simpana install group [dba] ... [OK]
- Check if install group has (Read & Write) permissions on:
   - /oracle/db20/simpana4/Base/Temp ... [OK]
   - /etc/CommVaultRegistry ... [OK]
   - /oracle/db20/simpana4/Log_Files ... [OK]
   - /oracle/db20/simpana4/iDataAgent/jobResults ... [OK]
   - /oracle/db20/simpana4/Base/certificates ... [OK]
- Check if RMAN can load CommVault SBT library for: (Connecting to rman TARGET / )
   - SID=rman10g ... [OK]
   - SID=trialdb ... [OK]
   - SID=auto ... [OK]
   - SID=LUN_DUP ... [OK]
   - SID=LREPDB ... [OK]
   - SID=RDMDB ... [OK]
##############################################
#### Oracle Agent is READY ####
##############################################

Example of a Database Agent not Ready for Backups and Restores

This is an example of running the Database Readiness Check with the verify option. Errors are indicated by "[FAILED]".

If the Oracle instances is not up, or the listener is not running, users see a SID=Oracle_SID...[FAILED] in the "Check if RMAN can load CommVault SBT library for: (Connecting to rman TARGET /)" section.

[root@dbserve4 iDataAgent]# ./DBAgentReadinessCheck.sh -o verify
****************************************************************
Tool: Check Readiness of "Database Agents"
****************************************************************
- Simpana instance: [Instance004]
- Simpana install group: [dba]
- Simpana database agents installed:
- Oracle Agent:
   - Instance: [rman10g] DbHome: [/oracle/oracle10g]
   - Instance: [trialdb] DbHome: [/oracle/oracle10g]
   - Instance: [auto] DbHome: [/oracle/oracle10g]
   - Instance: [LUN_DUP] DbHome: [/oracle/oracle10g]
   - Instance: [LREPDB] DbHome: [/oracle/oracle10g]
   - Instance: [RDMDB] DbHome: [/oracle/oracle10g]
Checking [Oracle] Agent Readiness
*****************************************
- Database user name:[oracle]
- Database home: [/oracle/oracle10g]
- Check if user is member of Simpana install group [dba] ... [OK]
- Check if install group has (Read & Write) permissions on:
   - /oracle/db20/simpana4/Base/Temp ... [FAILED]
   - /etc/CommVaultRegistry ... [OK]
   - /oracle/db20/simpana4/Log_Files ... [OK]
   - /oracle/db20/simpana4/iDataAgent/jobResults ... [OK]
   - /oracle/db20/simpana4/Base/certificates ... [OK]
- Check if RMAN can load CommVault SBT library for: (Connecting to rman TARGET / )
   - SID=rman10g ... [FAILED]
   - SID=trialdb ... [FAILED]
   - SID=auto ... [FAILED]
   - SID=LUN_DUP ... [FAILED]
   - SID=LREPDB ... [FAILED]
   - SID=RDMDB ... [FAILED]
##############################################
#### Oracle Agent is NOT READY ####
##############################################
Please correct the FAILED checks.
Please see [/tmp/CV_DBAgentReadinessCheck.log] for more details.

Example of Fixing the Database User Permissions

This option presents changes that must be approved, as indicated by the lines in bold starting with "WARNING".

If a restart of the Oracle services is required, the Database Readiness Check automatically handles it.

[root@dbserve4 iDataAgent]# ./DBAgentReadinessCheck.sh -o fix
****************************************************************
Tool: Check Readiness of "Database Agents"
****************************************************************
- Simpana instance: [Instance004]
- Simpana install group: [dba]
- Simpana database agents installed:
- Oracle Agent:
   - Instance: [rman10g] DbHome: [/oracle/oracle10g]
   - Instance: [trialdb] DbHome: [/oracle/oracle10g]
   - Instance: [auto] DbHome: [/oracle/oracle10g]
   - Instance: [LUN_DUP] DbHome: [/oracle/oracle10g]
   - Instance: [LREPDB] DbHome: [/oracle/oracle10g]
   - Instance: [RDMDB] DbHome: [/oracle/oracle10g]
Checking [Oracle] Agent Readiness
*****************************************
- Database user name:[oracle]
- Database home: [/oracle/oracle10g]
- Check if user is member of Simpana install group [dba] ... [OK]
- Check if install group has (Read & Write) permissions on:
   - /oracle/db20/simpana4/Base/Temp ... [FAILED]
   - /etc/CommVaultRegistry ... [OK]
   - /oracle/db20/simpana4/Log_Files ... [OK]
   - /oracle/db20/simpana4/iDataAgent/jobResults ... [OK]
   - /oracle/db20/simpana4/Base/certificates ... [OK]
- Check if RMAN can load CommVault SBT library for: (Connecting to rman TARGET / )
   - SID=rman10g ... [FAILED]
   - SID=trialdb ... [FAILED]
   - SID=auto ... [FAILED]
   - SID=LUN_DUP ... [FAILED]
   - SID=LREPDB ... [FAILED]
   - SID=RDMDB ... [FAILED]
##############################################
#### Oracle Agent is NOT READY ####
##############################################
Please correct the FAILED checks.
Please see [/tmp/CV_DBAgentReadinessCheck.log] for more details.
Fixing database group [dba] permissions
*****************************************
WARNING!! Group [dba] will be given WRITE permissions. Please answer [y/n] to proceed: ?y
Using installer version 10116174.
Assigning setup GUID ... 10-116-dbserve4.devemc.commvault.com-172.19.65.247-19602
Stopping Simpana services for Instance004 ...

Simpana 10 (BUILD116) Change
Changing Unix Group for Instance004

Changing group to dba for the following directories...
- Registry(/etc/CommVaultRegistry) ... done.
- Executables(/oracle/db20/simpana4) ... done.
- Logs(/oracle/db20/simpana4) ... done.
- DC Cache(/oracle/db20/simpana4/iDataAgent/jobResults/cvdccache) ... done.
- Job Results for dbserve4(/oracle/db20/simpana4/iDataAgent/jobResults) ... done.
Updating /oracle/db20/simpana4/Base/pkginfo for GALAXY_GROUP=dba ... done.
Updating /oracle/db20/simpana4/Base0/pkginfo for GALAXY_GROUP=dba ... done.

Simpana 10 (BUILD116) Change
Changing Group and Other User's Access Permissions for Instance004

Changing access permissions for group users to 7 and other users to 5 for the following directories...
- Registry(/etc/CommVaultRegistry) ... done.
- Executables(/oracle/db20/simpana4) ... done.
- Logs(/oracle/db20/simpana4) ... done.
- DC Cache(/oracle/db20/simpana4/iDataAgent/jobResults/cvdccache) ... done.
- Job Results for dbserve4(/oracle/db20/simpana4/iDataAgent/jobResults) ... done.
Updating /oracle/db20/simpana4/Base/pkginfo for GALAXY_OTHER_ACCESS=5 ... done.
Updating /oracle/db20/simpana4/Base0/pkginfo for GALAXY_OTHER_ACCESS=5 ... done.
Updating /oracle/db20/simpana4/Base/pkginfo for GALAXY_GROUP_ACCESS=7 ... done.
Updating /oracle/db20/simpana4/Base0/pkginfo for GALAXY_GROUP_ACCESS=7 ... done.
Cleaning up /oracle/db20/simpana4/Base/Temp ...
Starting Simpana services for Instance004 ...

Simpana 10 (BUILD116) Change
Done

[ PLEASE READ THE FOLLOWING NOTES ]
(1) Depending on the file type, the actual permission might be more restrictive.
For example, a text file may not have executable bit on.

(2) If you run installer to add more instances or modules, you might need to
rerun this utility to fix certain files changed during the install.
Thank you for using CommVault Systems, Inc. Simpana.

ORCL0040: Subclients for CommCell Console Auto Discovered Instances May Have Unavailable Properties

Issue

If you discovered instances by using the CommCell Console, the default subclient may have the Back up SP File check box and Protect backup recovery area check box on the subclient Content tab unavailable.

Resolution

Refresh the instance properties.

  1. From the CommCell Browser, expand Client Computers > client > Oracle.
  2. Right-click the instance and then click Properties.
  3. On the Instance Properties dialog box click OK.

Alternatively, use the SnapProtect Command Line Interface to update the instance.

  1. On the Oracle Agent host, run the qlogin command to log on to the CommServe computer.
  2. Download the refreshInstance.xml file to the computer where you will run the command.
  3. Optional: Open the refreshInstance.xml file, add your specific parameters, and save the file.

    For information on supported instance XML parameters, see Available XML Parameters for Oracle Instance Configuration.

  4. On the command line, go to Software_Installation_Directory/Base and type the command.

    Refresh the properties of a specific instance that was discovered from the CommCell Console:

    qoperation execute -af refreshInstance.xml -appName 'oracle' -clientName 'client1' -instanceName 'dbname'

    Refresh the properties of all instances that were discovered from the CommCell Console:

    qoperation execute -af refreshInstance.xml -appName 'oracle' -clientName 'client1'

    Note: If you have updated the instance properties of all the CommCell Console instances, verify the crosscheck timeout of the existing instances’

  5. In the CommCell Console, select the agent, or the Oracle instance.
  6. From the CommCell Console ribbon, click the View tab and then click Refresh.