Database Administration (MOSC)

MOSC Banner

After db_role_change action in trigger - scheduler unavailable

edited Sep 27, 2019 5:09AM in Database Administration (MOSC) 19 commentsAnswered

Hi

I have noticed that after db_role_change trigger fires in different time.

At least when I tested with 19c and 12c. On 19c my trigger runs scheduler job just fine, but with 12c, I get "scheduler unavailable". Looks like database is not open at that time on 12c.

Here is the alert.log section from the new primary database (19c).

I deliberately did mistake into after db_role_change trigger to simulate, where this trigger fires. Now I have tested this with 19c (no mistakes in trigger definition), and it will run my scheduler job just fine.

.....2019-08-29T11:19:01.030340+03:00

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

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center