OEM12c job fails after database upgrade
edited Oct 17, 2013 11:37PM in Managing Databases using Enterprise Manager (MOSC) 6 commentsAnswered ✓
Hi,
We just upgrade a monitored database from 11203 to 11204.
The /etc/oratab has been modified to reflect the change and the agent has been restarted.
I run a resync of the agent.
But a job is still failing with:
Execution Log=ERROR: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2:
No such file or directory Process ID: 0 Session ID: 0 Serial number: 0 SP2-0584:
EXIT variable "SQLCODE" was non-numeric Usage: { EXIT | QUIT } [ SUCCESS | FAILURE | WARNING | n | | : ] [ COMMIT | ROLLBACK ] Error from SQLPLUS: 1
Of course, if I check the targets.xml, the database entry is still pointing to the old Oracle Home 11203 !!
We just upgrade a monitored database from 11203 to 11204.
The /etc/oratab has been modified to reflect the change and the agent has been restarted.
I run a resync of the agent.
But a job is still failing with:
Execution Log=ERROR: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2:
No such file or directory Process ID: 0 Session ID: 0 Serial number: 0 SP2-0584:
EXIT variable "SQLCODE" was non-numeric Usage: { EXIT | QUIT } [ SUCCESS | FAILURE | WARNING | n | | : ] [ COMMIT | ROLLBACK ] Error from SQLPLUS: 1
Of course, if I check the targets.xml, the database entry is still pointing to the old Oracle Home 11203 !!
0