This is one of the alert found on an 11.2.0.3 database.
The alert error is :-
Errors in file /oracle/ora_ctl/oraadmin/ORCLDB/diag/rdbms/orcldb/ORCLDB_1/trace/ORCLDB_1_j001_25510.trc:
ORA-12012: error on auto execute of job "SYS"."BSLN_MAINTAIN_STATS_JOB"
ORA-06502: PL/SQL: numeric or value error
ORA-06512: at "DBSNMP.BSLN_INTERNAL", line 2073
ORA-06512: at line 1
Cause for this error :-
Inconsistent information on DBSNMP.BSLN_BASELINES table.
Query the table
SQL> select * from DBSNMP.BSLN_BASELINES;
DBID INSTANCE_NAME BASELINE_ID BSLN_GUID TI A STATUS LAST_COMP
---------- ---------------- ----------- -------------------------------- -- - ---------------- ---------
3757044803 ORCLDB 0 A8AF70B18D010F36F77705A08EEFFD58 NX Y ACTIVE 29-SEP-13
3757044803 ORCLDB_1 0 51587F1AC1AC5A6F68F96CC9F467CE7F HX Y ACTIVE 29-SEP-13
The alert error is :-
Errors in file /oracle/ora_ctl/oraadmin/ORCLDB/diag/rdbms/orcldb/ORCLDB_1/trace/ORCLDB_1_j001_25510.trc:
ORA-12012: error on auto execute of job "SYS"."BSLN_MAINTAIN_STATS_JOB"
ORA-06502: PL/SQL: numeric or value error
ORA-06512: at "DBSNMP.BSLN_INTERNAL", line 2073
ORA-06512: at line 1
Cause for this error :-
Inconsistent information on DBSNMP.BSLN_BASELINES table.
Query the table
SQL> select * from DBSNMP.BSLN_BASELINES;
DBID INSTANCE_NAME BASELINE_ID BSLN_GUID TI A STATUS LAST_COMP
---------- ---------------- ----------- -------------------------------- -- - ---------------- ---------
3757044803 ORCLDB 0 A8AF70B18D010F36F77705A08EEFFD58 NX Y ACTIVE 29-SEP-13
3757044803 ORCLDB_1 0 51587F1AC1AC5A6F68F96CC9F467CE7F HX Y ACTIVE 29-SEP-13
We can see there are two entries in the table. In this database, the current instance name is ORCLDB_1. So we need to remove the other entry.
SQL> DELETE FROM DBSNMP.BSLN_BASELINES WHERE INSTANCE_NAME='ORCLDB';
1 row deleted.
SQL> commit;
Commit complete.
Now execute the job manually.
SQL> exec dbms_scheduler.run_job('BSLN_MAINTAIN_STATS_JOB',false);
SQL> DELETE FROM DBSNMP.BSLN_BASELINES WHERE INSTANCE_NAME='ORCLDB';
1 row deleted.
SQL> commit;
Commit complete.
SQL> exec dbms_scheduler.run_job('BSLN_MAINTAIN_STATS_JOB',false);
PL/SQL procedure successfully completed.
The issue got fixed. You can query the Job run details and find the status :-
SQL> select log_date,status from dba_scheduler_job_run_details
where job_name='BSLN_MAINTAIN_STATS_JOB' order by log_date; 2
LOG_DATE STATUS
--------------------------------------------------------------------------- ------------------------------
09-FEB-14 12.00.02.223379 AM +00:00 FAILED
16-FEB-14 12.00.01.233061 AM +00:00 FAILED
23-FEB-14 12.00.01.376403 AM +00:00 FAILED
02-MAR-14 12.00.01.187070 AM +00:00 FAILED
06-MAR-14 01.03.48.689335 PM +00:00 SUCCEEDED
No comments:
Post a Comment