Updating the RDBMS DST version in 11g Release 2 (220.127.116.11 and up) using DBMS_DST
(Doc ID 977512.1)
Last updated on FEBRUARY 15, 2019
Applies to:Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database - Standard Edition - Version 18.104.22.168 to 22.214.171.124 [Release 11.2]
Oracle Database - Enterprise Edition - Version 126.96.36.199 to 188.8.131.52 [Release 11.2]
Information in this document applies to any platform.
If the only goal is to update the RDBMS DST version to the default RDBMS DST version included in the 11.2.0.x version after an Oracle RDBMS version upgrade to 11.2.0.x
then simply run the scripts found in <note 1585343.1> Scripts to automatically update the RDBMS DST (timezone) version in an 11gR2 or 12cR1 database.
Those scripts do all the steps in this note.
This note provides an overview of
- what is changed related to RDBMS DST updates in 11gR2
- how to perform a manual RDBMS DST version update in Oracle RDBMS 11gR2 (= the steps used in the scripts of <note 1585343.1>).
The RDBMS and OJVM DST versions are NOT technically related so they do not NEED to be the same.
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
|1) What is changed in 11gR2 about RDBMS DST updates (when compared to 11gR1 and lower):|
|2) When do I need to apply RDBMS DST patches to the 11.2.0.x ORACLE_HOME before using DBMS_DST (= before going to step 3) in this note)?|
|2a) 184.108.40.206 : When updating to a RDBMS DST version higher than DSTv11|
|2b) 220.127.116.11, 18.104.22.168 or 22.214.171.124: When updating to a RDBMS DST version higher than DSTv14|
|3) Checks before doing the actual update of the RDBMS DST version using DBMS_DST in an 11.2.0.x database:|
|3a) check current RDBMS DST version and "DST UPGRADE STATUS" in your 11.2.0.x database.|
|3b) Check UPFRONT using DBMS_DST if there is affected data that cannot be resolved automatically in your 11.2.0.x database.|
|4) Do the actual RDBMS DST version update of the database using DBMS_DST in your 11.2.0.x database:|
|5) How long will DBMS_DST take ?|
|5.a) Things one can check upfront:|
|5.b) why does DBMS_DST.FIND_AFFECTED_TABLES sometimes takes longer than the actual upgrade?|
|5.c) Selects useful if DBMS_DST "hangs" or takes a long time:|
|6) Known Issues with DBMS_DST in 11.2.0.x:|
|* an ORA-54017: UPDATE operation disallowed on virtual columns error is seen during DBMS_DST.UPGRADE_DATABASE :|
|* if DBMS_DST.FIND_AFFECTED_TABLES fails with ORA-00907: missing right parenthesis or ORA-00927: missing equal sign|
|* DBMS_DST fails on some case insensitive table or column names with ORA-00904: invalid identifier or ORA-01747: invalid user.table.column, table.column, or column specification.|
|* DBMS_DST is very slow on some databases|
|* if the database is still in DST upgrade mode then select from timestamp with timezone columns will give the data without the second fractions|
|* EXEC DBMS_DST.BEGIN_PREPARE (or any other DBMS_DST call) fails with 'PLS-00201: identifier 'DBMS_DST.-insert name here-' must be declared':|
|* if DBMS_DST.BEGIN_PREPARE fail with ORA-02014: cannot select FOR UPDATE from view with DISTINCT, GROUP BY, etc.|
|* if DBMS_DST.BEGIN_PREPARE fails with ORA-56922: Starting a prepare window failed|
|7) Can the DST version be updated in 11.2.0.x without downtime? Or in a "rolling" fashion on RAC?|