I'm seeing this error in the alert log (sorry, it's in italian!):
*** 2021-09-14 23:50:17.891*** SESSION ID:(249.6897) 2021-09-14 23:50:17.891*** CLIENT ID:() 2021-09-14 23:50:17.891*** SERVICE NAME:(SYS$USERS) 2021-09-14 23:50:17.891*** MODULE NAME:(DBMS_SCHEDULER) 2021-09-14 23:50:17.891*** ACTION NAME:(AUDIT_LAST_ARCHIVE_TIME) 2021-09-14 23:50:17.891ORA-12012: Errore nell'esecuzione automatica dei lavori "SYS"."AUDIT_LAST_ARCHIVE_TIME"ORA-46250: Valore non valido per l'argomento 'RAC_INSTANCE_NUMBER'ORA-06512: a "SYS.DBMS_AUDIT_MGMT", line 61ORA-06512: a "SYS.DBMS_AUDIT_MGMT", line 2241ORA-06512: a line 2
I was about to disable, drop and recreate the job correctly but I get the following error:
SQL> execute dbms_scheduler.disable('AUDIT_LAST_ARCHIVE_TIME');BEGIN dbms_scheduler.disable('AUDIT_LAST_ARCHIVE_TIME'); END;*ERROR at line 1:ORA-27476: "SYS.AUDIT_LAST_ARCHIVE_TIME" non esisteORA-06512: a "SYS.DBMS_ISCHED", line 4452ORA-06512: a "SYS.DBMS_SCHEDULER", line 2737ORA-06512: a line 1
But, if I query the follwing system table:
select LOG_ID, LOG_DATE, OWNER, JOB_NAME, STATUS, OPERATION from dba_scheduler_job_log where JOB_NAME like '%AUDIT%'order by LOG_DATE ASC;
I can see it (failing):
How is it possible? What am I doing wrong?On the same server there are a bunch of other databases created from the same binaries, where this last arch.ts job is created the same way and I'm not getting this anomaly.