ORA-12012: when executing a job (ORA-6512, ORA-6550)
(Doc ID 75070.1)
Last updated on NOVEMBER 23, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 10.1.0.2 to 10.2.0.5 [Release 10.1 to 10.2]Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
You submit a job using DBMS_JOB.SUBMIT, but the job does not run and the following errors are written to the alert file:
ORA-12012: error on auto execute of job 62
Cause: Some kind of error was caught while doing an automatic execute of a job.
Action: Look at the accompanying errors for details on why the execute failed.
ORA-06550: line 1, column 143
Cause: A PL/SQL compilation error has occurred.
The numbers given for line and column are the location in the PL/SQL block where the error occurred.
Action: Refer to the following PL/SQL messages for more information about the error.
PLS-00201: identifier 'user_name.table' must be declared
See: Note:27287.1
ORA-06550: line 1, column 96
Cause: A PL/SQL compilation error has occurred.
The numbers given for line and column are the location in the PL/SQL block where the error occurred.
Action: Refer to the following PL/SQL messages for more information about the error.
PL/SQL: SQL Statement ignored
The job inserts data from one schema (userA) into a table in another schema (userB), and is submitted from userB.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |