My Oracle Support Banner

19c DST Upgrade - "Disk file operations I/O" (Doc ID 2818498.1)

Last updated on OCTOBER 31, 2021

Applies to:

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

Symptoms

During 19c DST upgrade, DST packages/scripts are taking more time than usual. Hanganalysis could reveal the below.

Action:

DBMS_DST.UPGRADE_DATABASE

UTLTZ_UPG_APPLY

Wait Event:

"Disk file operations I/O"

Bug

Bug 32569603 - LNX64-1911: DBUA FAILS WITH "SEVERE ERROR DURING TIMEZONE UPGRADE"

Below script also monitors the DST operation and reveals the wait event, if any.

CONN / as sysdba
-- needs EXEC DBMS_APPLICATION_INFO.SET_CLIENT_INFO('upg_tzv') been set
set PAGES 1000
select TARGET, TO_CHAR(START_TIME,'HH24:MI:SS - DD-MM-YY'), TIME_REMAINING, SOFAR,
TOTALWORK, SID, SERIAL#, OPNAME from V$SESSION_LONGOPS
where sid in
(select SID from V$SESSION where CLIENT_INFO = 'upg_tzv')
and SOFAR < TOTALWORK
order by START_TIME;

select S.SID, S.SERIAL#, S.SQL_ID, S.PREV_SQL_ID,
S.EVENT#, S.EVENT, S.P1TEXT, S.P1, S.P2TEXT, S.P2, S.P3TEXT, S.P3, S.TIME_REMAINING_MICRO,
S.SEQ#, S.BLOCKING_SESSION, BS.PROGRAM "Blocking Program",
Q1.SQL_TEXT "Current SQL", Q2.SQL_TEXT "Previous SQL"
from V$SESSION S, V$SQLAREA Q1, V$SQLAREA Q2, V$SESSION BS
where S.SQL_ID = Q1.SQL_ID(+)
and S.PREV_SQL_ID = Q2.SQL_ID(+)
and S.BLOCKING_SESSION = BS.SID(+)
and S.CLIENT_INFO = 'upg_tzv';

 

Changes

Upgrading DST

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
Changes
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.