The solution for this issue is to either change the password within Oracle for the Oracle Instance account back to what it was during initial Backup Exec Remote Agent configuration, or update the Backup Exec Remote Agent configuration with the new password.
In Windows, this would be accomplished by the following:
1. Open the Backup Exec Remote Agent Utility (Start | All Programs | Veritas Backup Exec for Windows | Backup Exec Remote Agent Utility)
2. Select the "Oracle" Tab
3. Click "Change Settings"
4. Select the "Oracle" Tab again
5. Select the Instance experiencing this issue.
6. Click "Edit"
7. Change the password of the account specified to reflect the current password.
In Linux, this would be accomplished by the following:
1. Login to the Linux server as "root"
2. Type (without quotes) "/opt/VRTSralus/bin/AgentConfig"
3. Type (without quotes) "2" (This option is "Configure Oracle instance information")
4. Type (without quotes) "2" (This option is "Edit an existing Oracle instance")
5. A list of protected Oracle instances will be displayed, type the number of the instance experiencing the issue.
6. Follow the on-screen prompts to complete the configuration. (Be sure to answer "y" to "Commit changes to the configuration file?)
7. Type (without quotes) "5" (This option is "Quit")
8. Type (without quotes) "3" (This option is "Quit")
After completing the Remote Agent configuration, verify the solution by creating a new backup selection, expanding the Oracle server, and noting that the instance is now listed as "Oracle Database "SID" [OPEN]".
Applies To
This scenario may be verified by creating a new backup selection and navigating to the server where Oracle is installed. Expand the server.
If the Oracle instance shows the name but does not list "[OPEN]" after "Oracle Database "SID"" then this is the cause of the error.