Export ORACLE_HOME=/data/8020/d01/11.2.

0/OPatch
Export PATH=$ORACLE_HOME/OPatch:$PATH
Solution
Copy srvm.jar file from any other similar ORACLE_HOME
($ORACLE_HOME\oui\jlib\srvm.jar) to location $ORACLE_HOME\oui\jlib\ of corrupted
oracle_home and invoke opatch utility.

export ORACLE_HOME=/data/8020/d01/11.2.0
export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/OPatch:$PATH

5.a) Applying the RDBMS DSTv18 patch 13417321 on the server side in
11.2.
After a DST patch is installed in an 11.2 $ORACLE_HOME there are steps who need
to be done to change a existing database to use this newer DST version.
Simply applying the RDBMS DST patch and restarting the database will NOT enable
the new applied RDBMS DST version patch (like it did in pre-11.2 versions).

For 11.2.0.3 and 11.2.0.2 :

* Request (if needed) and download RDBMS DSTv18 Patch 13417321 for your
platform.
* Apply the RDBMS DSTv18 Patch 13417321 using Opatch. Note: unlike what
the readme may say, in 11.2 and up there is no need to shut down or stop
the database or other processes seen you are simply adding new files, not
replacing used ones.

* Then update all databases using this home by:

or using the scripts in note 1585343.1 Scripts to automatically update

the RDBMS DST (timezone) version in an 11gR2 or 12cR1 database .

Scripts to automatically update the RDBMS DST (timezone) version in an

11gR2 or 12cR1 database . (Doc ID 1585343.1

2) run upg_tzv_check.sql using SQL*PLUS from the database home

Note that upg_tzv_check.sql takes no arguments, it will detect the highest

installed DST patch automatically and needs no downtime, this can be
runned on a live production database but it WILL purge the dba_recyclebin.
Conn / as sysdba
spool upg_tzv_check.log
@upg_tzv_check.sql
spool off

Spool off;

3) if upg_tzv_check.sql has run sucessfully , run upg_tzv_apply.sql using SQL*PLUS from the
database home

Note:

For RAC databases make sure the database is started as single

instance
Make sure any application accessing or storing TSTZ data is stopped

upg_tzv_apply.sql will restart the database 2 times without asking any

confirmation

Typically upg_tzv_apply.sql will take less time than upg_tzv_check.sql

When runned against the CDB of a Multitenant db all PDB will be

closed

Conn / as sysdba
spool upg_tzv_apply.log
@upg_tzv_apply.sql
spool off

A succesfull run will show at the end:

INFO: The RDBMS DST update is successfully finished.
INFO: Make sure to exit this sqlplus session.
INFO: Do not use it for timezone related selects.

Bounce the db 2 times.

If you want to test if for other timezones then add affected timezones and see if the date is in DST or not.txt

The output on a system that has the OJVM DSTv4 applied is:

6) The OJVM DSTv18 patch 14112098.

Your current OJVM DST version can be found using the procedure provided
in Note 416860.1 Testing your Oracle JVM Time Zone Setup
There are very few applications who actually use the DST information of the
OJVM, hence this patch is not proactively backported to older releases. If you
are on a supported version or have an existing Extended Support contract
then you can of course request a backport if your application uses the OJVM
DST information. This patch is platform generic, please see the readme for
installation instructions.
To apply the patch you need to :
* shut down any database using this oracle home
* apply Patch 14112098 using opatch
Cd to patch 14112098 directory
./opatch apply

export ORACLE_HOME=/data/8020/d01/11.2.0
export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/OPatch:$PATH

The OJVM DSTv18 update includes the timezone information from

tzdata2012c.tar and contains all previous Oracle OJVM DST updates.
Note that , if an previous OJVM DST patch was applied, Opatch will report a
conflict between patch 14112098 and the old OJVM DST patch ( patch
5865568, 6113568, 6708377, 7449057, 7708501, 8603182, 9197935,
9751299, 10406470, 12565410, 12949919 ).
Seen OJVM DST patches always update the same files this is normal and can
be ignored.
There is no need to log an SR and ask a "merge" between the old and this
OJVM DST patch, the new OJVM DST patch has already all the old changes

5.

Start the services from the Oracle home.

(3) Postinstallation
----------------------connect as SYS and run script ORACLE_HOME/javavm/admin/fixTZa

Step5 : shutdown the database: SQL> shutdown

Step6 : If needed, edit init.ora back to cluster_database=TRUE
Step7 : Start Database without startup migrate: SQL> startup

Complying with Daylight Saving Time (DST) and Time Zone Rule Changes in EBusiness Suite 12 (Doc ID 563019.1)

II. Affected E-Business Suite Environments

When a country or region changes DST rules or Time Zones, your Oracle EBusiness Suite Release 12 environment will require patching if:

Your Oracle E-Business Suite environment is located in the affected

country or region OR
Your Oracle E-Business Suite environment is located outside the
affected country or region but you conduct business or have customers
or suppliers in the affected country or region.

If neither of the above conditions applies to your business, then your EBusiness Suite environment is not affected and you do not need to apply the
time zone patches.