Sunday, February 20, 2022

DST_UPGRADE_STATE set to DATAPUMP(1) when running preupgrade_fixups.sql

 

DST_UPGRADE_STATE set to DATAPUMP(1) when running preupgrade_fixups.sql



Performing 19c Upgrade from 12.2.1.0 . Came up with the following error while upgrading the timezone .

During the preparation for a 12.2 upgrade, I found that the preupgrade-tool reported about an incomplete DST upgrade, where DST_UPGRADE_STATE was set to "DATAPUMP(1)".

==

 SELECT PROPERTY_NAME, SUBSTR(property_value, 1, 30) value
FROM DATABASE_PROPERTIES
WHERE PROPERTY_NAME LIKE 'DST_%'
ORDER BY PROPERTY_NAME;

PROPERTY_NAME
--------------------------------------------------------------------------------
VALUE
------------------------------
DST_PRIMARY_TT_VERSION
31

DST_SECONDARY_TT_VERSION
14

DST_UPGRADE_STATE
DATAPUMP(1)


To fix the issues on PDB'S

SHOW CON_NAME
Alter session set container=<PDB_NAME>


1. ALTER SESSION SET EVENTS '30090 TRACE NAME CONTEXT FOREVER, LEVEL 32';

2. exec dbms_dst.unload_secondary;

I tried this, with the following result:
SYSproddb01 SQL> SELECT PROPERTY_NAME, SUBSTR(property_value, 1, 30) value FROM DATABASE_PROPERTIES WHERE PROPERTY_NAME LIKE 'DST_%' ORDER BY PROPERTY_NAME;

PROPERTY_NAME                            VALUE
---------------------------------------- --------------------
DST_PRIMARY_TT_VERSION                   36
DST_SECONDARY_TT_VERSION                 0
DST_UPGRADE_STATE                        NONE

I also executed

SQL> SELECT PROPERTY_NAME, SUBSTR(property_value, 1, 30) value
FROM DATABASE_PROPERTIES
WHERE PROPERTY_NAME LIKE 'DST_%'
ORDER BY PROPERTY_NAME;
  2    3    4
PROPERTY_NAME
--------------------------------------------------------------------------------
VALUE
------------------------------
DST_PRIMARY_TT_VERSION
36

DST_SECONDARY_TT_VERSION
0

DST_UPGRADE_STATE
NONE


ALTER SESSION SET EVENTS '30090 TRACE NAME CONTEXT FOREVER, OFF';

And the test is passed, and you are ready to upgrade

No comments: