My Oracle Support Banner

ORA-600 [kqlidp0: Bad Future_p_timestamp] In Database Alert File (Doc ID 1566937.1)

Last updated on SEPTEMBER 26, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.3 and later
Information in this document applies to any platform.

NOTE: In the images and/or the document content below, the user information and data used represents fictitious data. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.

Symptoms

Trying to create a DB with DBCA gives error: 

ORA-01513: invalid current time returned by operating system

At the same time the following internal error was reported in alert file:

ORA-00600: internal error code, arguments: [kqlidp0: bad future_p_timestamp]

 

 This internal error is reported in alert file with a wrong date.

For Example:

Thu Jul 04 08:26:07 2013
Thread 1 advanced to log sequence 5 (LGWR switch)
Current log# 2 seq# 5 mem# 0: /u02/oradata/SID/onlinelog/redo.log
Thu Jan 01 00:00:00 1970 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<------ Here
Errors in file /u01/app/oracle/diag/rdbms/DBNAME/SID/trace/SID_ora_1174.trc (incident=15893):
ORA-00600: internal error code, arguments: [kqlidp0: bad future_p_timestamp], [], [], [], [], [], [], [], [], [], [], []
Incident details in: /u01/app/oracle/diag/rdbms/DBNAME/SID/incident/incdir_15893/SID_ora_1174_i15893.trc

 
Please note these errors can be raised during other operations too.

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.