Database Administration (MOSC)

MOSC Banner

DBMS_scheduler strange behavior

edited Mar 10, 2017 9:33AM in Database Administration (MOSC) 4 commentsAnswered

Release : 11.2.0.4

Hi,

I'm trying to use dbms_scheduler package to rebuild some indexes online in a particular windows.

I created my jobs but i got some ORA-54 for some of them.

To handle these errors i was thinking to use the attribute 'restartable' for the jobs but i got then some strange behavior.

I'm not sure if this is an issue or if i misunderstood the meaning and the attribute usage.

I'm creating my job with:

exec dbms_scheduler.create_job(job_name=>'RBLDIDXM1_201702271617361',job_type=>'PLSQL_BLOCK',job_action=>'begin execute immediate ''alter index XXEL.XXEL_ELIPS_LOT_ENT_N3 rebuild online parallel 8 nologging''; execute immediate ''alter index XXEL.XXEL_ELIPS_LOT_ENT_N3 noparallel logging''; end;',schedule_name=>'SYS.WIN_IDX_REBUILD',enabled=>TRUE,auto_drop=>TRUE,comments=>'XXEL/XXEL_ELIPS_LOT_ENT/XXEL_ELIPS_LOT_ENT_N3');

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