My Oracle Support Banner

Archivelog complettion time mismatch from DB (Doc ID 2809858.1)

Last updated on OCTOBER 07, 2021

Applies to:

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

Symptoms

Archivelog completion time mismatch from DB and server time.


select thread#,SEQUENCE#,TO_CHAR(cast(FIRST_TIME as timestamp with time zone), 'YYYY-MM-DD HH24:MI:SSTZH:TZM') first_time,
2 TO_CHAR(cast(NEXT_TIME as timestamp with time zone), 'YYYY-MM-DD HH24:MI:SSTZH:TZM') next_time,
TO_CHAR(cast(COMPLETION_TIME as timestamp with time zone), 'YYYY-MM-DD HH24:MI:SSTZH:TZM') completion_time
3 4 from v$archived_log
where sequence#= 5 24748 and thread#=2;

THREAD# SEQUENCE# FIRST_TIME NEXT_TIME COMPLETION_TIME
---------- ---------- ------------------------- ------------------------- -------------------------
2 24748 2021-08-31 10:44:16-04:00 2021-08-31 10:44:17-04:00 2021-08-31 10:44:17-04:00 <<<<<<<<<<<<<<<<< Comletion time = 10:44

select to_char(sysdate, 'DD/MM/YYYY HH24:MI:SS') , to_char(systimestamp, 'DD/MM/YYYY HH24:MI:SS TZR') from dual;

TO_CHAR(SYSDATE,'DD TO_CHAR(SYSTIMESTAMP,'DD/MM/YYYYHH24:MI:SSTZR')
------------------- ----------------------------------------------------
31/08/2021 11:44:44 31/08/2021 11:44:44 -04:00 <<<<<<<<<<<<<<<<<< DB Time = 11:44

SYS@DBLAB2> !date
Tue Aug 31 11:44:58 EDT 2021 <<<<<<<<<<<<<<<<<<<<<<<<<<< Server Time = 11:44

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
References


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