This content has been marked as final. Show 7 replies
Applying the DSTv15 update for the Oracle Database [ID 1274498.1] says:
For 220.127.116.11 and 18.104.22.168 please download the DSTv15 Patch 10272702 for your platform and then see Note 977512.1 Updating the RDBMS DST version in 11gR2 (22.214.171.124 and up) using DBMS_DST.
For those keeping score:
and back to 977512.1
Who's on first?
stellr wrote:The Entity-Relationship model specifies that there is no ordering implied in the set of data. Therefore all related data is simply put into a heap and when you retrieve it, you get a bag worth of unordered data.
The information maze is just weird.
Oracle takes this to heart: All the data is there. Navigating it is ... well, it's all there, in the bag :-)
no reply from support on my SR. Are they as confused as I am?
Guess I'll go read my postgresql book.
977512.1 says, "there is no need to shutdown the database to apply the RDBMS DST patch."
The readme of patch 10272702 says: "8. Shut down services running from the ORACLE_HOME.
Before applying this patch, do a clean shut down of all services running from the ORACLE_HOME."
These aren't the droids you're looking for. - Obi-Wan
DSTv15diff is pure informative thing, it was added by customer request, i've made it hidden as attachement and added this text "(this is not a "DST patch" or needed to apply dst patches, it's pure informative)"
in 11.2 there is no need to shutdown a database to apply a new DST patch, it's simply add a new file to the home. Hence it is not in use (like on the older versions), i'll see the readme for 11.2 patch is changed for DSTv16)
you have 2 distinct different things you can do
* upgrade a software version (which, for 11.2. you may need to apply a dst patche to the target home)
* not upgrade the software version but simply update the DST version
both are handled in different note seen they are different actions, both are in Note 412160.1 Updated DST transitions and new Time Zones in Oracle Time Zone File patches
If you want to update a DST version of a existing database (= not upgrade the db) then you have the "normal" dst advisory's
for example if you want to upgrade 126.96.36.199 to the latest tz file from DSTv11-> note 1274498.1 Applying the DSTv15 update for the Oracle Database
which basically say's, apply the DStv15 patch and then use DBMS_DST to go to 15 for each database in that home
If you then (later) want to UPGRADE a 188.8.131.52 DSTv15 to 184.108.40.206 then you have notes like Note 1201253.1 Actions For DST Updates When Upgrading To Or Applying The 220.127.116.11 Patchset
there it basically bottoms down (when coming from 18.104.22.168) to:
If you do "Out-of-place upgrade" in 11.2 then make sure then new version has your current dst version included (for example you use DSTv15 in 22.214.171.124 , then you need to apply DStv15 on 126.96.36.199 because it's not by default in the 112.0.2 stack), if not, then apply it to the new home and then ,after upgrade, (if needed/wanted) go to the latest dst version
I will also ask to include a reference to Note 412160.1 Updated DST transitions and new Time Zones in Oracle Time Zone File patches in the upgrade docset (which I assume you follow)
Edited by: Gunther Vermeir, Oracle on Mar 14, 2011 5:25 PM
added "no" where it was missing