Database - RAC/Scalability (MOSC)

MOSC Banner

Scheduled job failover behavior in RAC

in Database - RAC/Scalability (MOSC) 3 commentsAnswered ✓

Doc ID 2365434.1 explains stickiness of scheduled jobs in RAC, and that a correctly configured scheduler job will continue its schedule on a remote instance if the instance on which it was created is down.

After a Data Pump export/import of an application schema from an older version running standalone into 19c RAC, the scheduler jobs are set with INSTANCE_STICKINESS of TRUE but INSTANCE_ID of NULL. Which instance are they sticky to? It is not clear which instance it was created on because impdp ran in parallel across the whole cluster. Unless it counts the instance that impdp was started from?

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center