Jobs are not working after Dataguard Switchover/Failover
(Doc ID 1292755.1)
Last updated on APRIL 03, 2020
Applies to:
Oracle Database Backup Service - Version N/A and laterOracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 11.1.0.6 to 11.2.0.2 [Release 11.1 to 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
Scenario:
1) Dataguard 11g with logical standby database
2) Customer implemented DBMS_SCHEDULER as SYS on both primary and standby site.
The job is listed in DBA_SCHEDULER_JOBS on primary/standby before a switchover/failover-action.
3) Customer performed dataguard switchover.
4) After the switchover the job is gone from view DBA_SCHEDULER_JOBS on NEW primary site,
however the job is visible in DBA_OBJECTS.
Since the job is still available in dba_objects recreating or dropping the job fails with:
Changes
After upgrade from 10g to 11g the jobs doesn't work anymore on the new primary in case of a switchover/failover.
This worked fine in 10g.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |