My Oracle Support Banner

EM 12c: Error in the Enterprise Manager 12.1.0.4 Cloud Control Repository Database Alert Log: ORA-01866: the datetime class is invalid (Doc ID 1969582.1)

Last updated on AUGUST 19, 2022

Applies to:

Enterprise Manager Base Platform - Version 12.1.0.4.0 to 12.1.0.4.0 [Release 12.1]
Oracle Database - Enterprise Edition - Version 12.1.0.2 to 12.1.0.2 [Release 12.1]
Information in this document applies to any platform.
Environment: OMS 12.1.0.4
Repository Database: 12.1.0.2

Note that on 27-Aug-2014, the 12.1.0.2 database was no longer certified with EM 12.1.0.4 Cloud Control for repository database use.
See the following article for details on this action:

Temporary Suspension of 12c Database as EM 12cR4 Repository

For current certifications see the Cloud Control details at My Oracle Support/Certifications.

DO NOT configure 12c Cloud Control with the 12c RDBMS as a repository unless the certification states that is supported.

Symptoms

The following error is observed in the alert log for the version 12.1.0.2 database being used for the 12.1.0.4 Enterprise Manager Cloud Control Repository:


Thu Jul 24 09:04:27 2014
Errors in file /u01/app/oracle/diag/rdbms/emrep/emrep/trace/emrep_j000_18909.trc:
ORA-01866: (error message truncated)
....
ORA-01866: (error message truncated)
ORA-01866: (error message truncated) ORA-01866: the datetime class is in


An inspection of the trace file illustrates that the "EM_GROUP_MEMBER_SYNCUP" job was the cause:

*** 2014-07-24 08:20:33.925
*** SESSION ID:(1167.4607) 2014-07-24 08:20:33.925
*** CLIENT ID:() 2014-07-24 08:20:33.925
*** SERVICE NAME:(SYS$USERS) 2014-07-24 08:20:33.925
*** MODULE NAME:(DBMS_SCHEDULER) 2014-07-24 08:20:33.925
*** ACTION NAME:(EM_GROUP_MEMBER_SYNCUP) 2014-07-24 08:20:33.925
 


Set the event:
 alter system set events '1866 trace name errorstack level 3';
wait for the next ORA-1866
 alter system set events '1866 trace name errorstack off';

and see the underlying cause is dbms_isched.exec_job_run_lsa, e.g.:


----- Current SQL Statement for this session (sql_id=2uht9xbvjqyb1) -----
call dbms_isched.exec_job_run_lsa     (:1,:2,:3,:4,:5,:6,:7,:8,:9,:10,:11)

----- Call Stack Trace -----
calling              call     entry                argument values in hex      
location             type     point                (? means dubious value)     
-------------------- -------- -------------------- ----------------------------
skdstdst()+29        call     kgdsdst()            7FFFD51DBA80 ? 000000000 ?
                                                   7FFFD51BE340 ? 7FFFD51BE458 ?
                                                   7FFFD51DC138 ? 7FFFD51DBA30 ?
ksedst()+112         call     skdstdst()           7FFFD51DBA80 ? 000000000 ?
                                                   7FFFD51BE340 ? 7FFFD51BE458 ?
                                                   7FFFD51DC138 ? 7FFFD51DBA30 ?
dbkedDefDump()+1153  call     ksedst()             000000000 ? 000000000 ?
                                                   7FFFD51BE340 ? 7FFFD51BE458 ?
                                                   7FFFD51DC138 ? 7FFFD51DBA30 ?
ksedmp()+26          call     dbkedDefDump()       000000003 ? 000000000 ?
                                                   7FFFD51BE340 ? 7FFFD51BE458 ?
                                                   7FFFD51DC138 ? 7FFFD51DBA30 ?
dbkdaKsdActDriver()  call     ksedmp()             000000003 ? 000000000 ?
+880                                               7FFFD51BE340 ? 7FFFD51BE458 ?
                                                   7FFFD51DC138 ? 7FFFD51DBA30 ?
dbgdaExecuteAction(  call     dbkdaKsdActDriver()  7F9AB8E81618 ? 7FFFD51DEA50 ?
)+319                                              7FFFD51BE340 ? 7FFFD51BE458 ?
                                                   7FFFD51DC138 ? 7FFFD51DBA30 ?
dbgdaRunAction()+46  call     dbgdaExecuteAction(  7F9AB8E81618 ? 00C9F8580 ?
5                             )                    7FFFD51DD878 ? 7FFFD51DEA50 ?
                                                   7F9A00000001 ? 7FFFD51DBA30 ?
dbgdRunActions()+89  call     dbgdaRunAction()     7F9AB8E81618 ? 00C9F8580 ?
                                                   7FFFD51DD878 ? 7FFFD51DEA50 ?
                                                   7F9A00000001 ? 7FFFD51DBA30 ?
dbgdProcessEventAct  call     dbgdRunActions()     7F9AB8E81618 ? 00C9F8580 ?
ions()+241                                         7FFFD51DD878 ? 7FFFD51DEA50 ?
.....


An ORA-1866 may also occur with the EM_REPOS_SEV_EVAL job, seen in this same log, e.g.:

Fri Sep 05 01:01:30 2014
 Errors in file
 /u01/app/oracle/diag/rdbms/emrep/emrep/trace/oemz_j001_10650.trc:
 ORA-12012: error on auto execute of job "SYSMAN"."EM_REPOS_SEV_EVAL"
 ORA-01866: the datetime class is invalid

 

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!


In this Document
Symptoms
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.