Best Practices › Best Practices for Protecting Oracle Data › Troubleshooting Oracle RMAN Backups with UNIX and Linux Data Mover › Log in Errors Occur When You Attempt to Expand the Oracle Instance in the Backup Manager

Log in Errors Occur When You Attempt to Expand the Oracle Instance in the Backup Manager

Valid on UNIX and Linux platforms.

Symptom

When you expand the Oracle instance in the Backup Manager, log in errors occur.

Solution

To remedy the log in errors, consider the following solution:

1. Ensure the user name and password specified is correct.
2. Ensure the Oracle instance is available. The Oracle instance may not be running or in a suitable status.
3. If the user name and password are correct, and the instance is available, do the following:
   • Ensure that the name of the Oracle instance and the relative Oracle home directory values that are specified in the instance.cfg configuration file are identical to the environment variable values specified when you started the Oracle instance.

   The Agent for Oracle uses the Oracle system shared memory handle to retrieve these values, and the values must be identical.

   Example:

   Instance name: orcl

   Home directory: AAAA/BBBB

   When you start the Oracle instance, you must specify orcl and AAAA/BBBB respectively. When running orasetup, you must also specify orcl and AAAA/BBBB for the instance name and the home directory.

4. If you continue to receive error messages, ensure that the directory /tmp resides on the target server, and has a permission value of 777. Permission 777 lets the Agent for Oracle write temporary files to the /tmp directory.