Roll Up patch

Hello,
What does roll up patch mean ?
BR

Hi Kashif;
Rollup Patch (RUP): An aggregation of patches that may be at the functional level, or at a specific product/family release level. For example, a Flexfields rollup patch contains all the latest patches related to Flexfields at the time the patch was created. A Marketing Family 11.5.10 rollup patch contains all the latest Marketing patches released since, and applicable to 11.5.10Your answer very similar wiht Hussein Sawwan's previous post :)
difference between Rollup patch and family pack
Anyway :) @poster
The R11/R12 RUPs combine error corrections, statutory/regulatory updates, and functionality enhancements that were made available after the initial release of Oracle E-Business Suite R11/R12
Each R11/12 RUP is cumulative and delivers system updates released in all prior R11/12 RUPs as well as one-off patches released in between RUPs (for example, RUP3 includes the system updates delivered in RUP1 and RUP2 plus any one-off fixes).
Source:
Oracle E-Business Suite Release 12 Release Update Pack (RUP) [ID 423541.1]
About Oracle Applications Technology 11i.ATG_PF.H.delta.7 (RUP 7) [ID 783600.1]
PS:Please dont forget to change thread status to answered if it possible when u belive your thread has been answered, it pretend to lose time of other forums user while they are searching open question which is not answered,thanks for understanding
Regard
Helios

Similar Messages

Roll Back Patches

Hallo,
I have a Enterpreise 450 with Solaris 2.7, I want to update the Patches but i need a Roll Back from the old one.
Please tell me how can I do this.
Regards,
Zareh Manasi

Hallo,
I have a Enterpreise 450 with Solaris 2.7, I want to
update the Patches but i need a Roll Back from the old
one.I doubt that it is Solaris 7 x86 (as per forum topic) ;-)
The answer is the same, though.
As long as you applied the patches originally without the -d option (and you didn't delete the patch backout files in /var/sadm/patch), then you can simply do
patchrm [patch-id]
Most patches are cumulative, so if you want, you can rollback a patch several times.
To get a list of all patches installed, patchadd -p or showrev -p
A+
Paul

Music not playing after IDT update last night (HP automated update) How can I roll the patch back?

I was notified of an HP update last night. After the update completed, Itunes/MS media player/You-Tube....applications are unable to play. Checked Installed programs and the only update listed was one for IDT drivers. How can I roll back to the previous version?
This question was solved.
View Solution.

I had the same issue, after reading several other posts with the same issue, I restored to before Oct 29th. Now my sound works just fine and my games that were also going hinky started to work as well.
It would be nice if HP fixed this issue before sending up another update. It is very annoying to have undo what they did so my computer works correctly.

Database rolling upgrade cpu patch with minimal service outage

Oracle 11gR2 Primary Instance
Oracle 11gR2 Active Physical Standby
Requirement of applying CPU and CVE patches with minimal downtime. I believe that I've been able to apply CPU patch to Active Standby after deferring redo transport and applying patch to active physical standby first and then performing a manual switchover to have the standby become the primary and former-primary become the standby and they apply CPU Patch there and then perform another role transition to its original role.
Appreciate your experience with primary and active physical standby rolling upgrades/patches. Thanks

Hello;
I believe you are over thinking this. All you have to do on the Standby is install the patch. No switchover, no SQL. No nothing.
The SQL will move from the Primary to the Standby.
Check the readme for the patch closely or post the patch number if you want to confirm.
OR
How do you apply a Patchset,PSU or CPU in a Data Guard Physical Standby configuration [ID 278641.1]
( If it helps I had the same thoughts after my first Data Guard setup !! )
If you are trying to avoid downtime entirely the switchover will take about as long as the patch.
If you have RAC this is interesting :
http://javeedkaleem.blogspot.com/2010/05/how-to-apply-oracle-database-patch.html
As is this :
http://docs.oracle.com/cd/B28359_01/server.111/b28282/schedule_outage.htm
Best Regards
mseberg

How to apply Bundle Patch in Rolling Mode for 2 Node RAC

Hi Guys,
I have a 2 node RAC environment (11.2.0.3) where each node has there own local Grid_home and RDBMS_home.
I am installing a Rolling Bundle Patch with OPatch in this environment. The installation document says that "The order of patching in RAC install is GRID_HOME, then RDBMS_HOME" so i did the following.
1. stopped all oracle related services on node1
2. set oracle_home=<Grid_home>
3. applied the opatch
4. opatch succeeded on node1 and it says "The node 'NODE2' will be patched next... Is the node ready for patching? y
Here i am bit confused.
1. Should i shutdown the oracle services in Node2 and continue to patch the Grid_home ? If yes then the DB will be completely down for user access. This defeats the purpose of rolling mode which says there is no downtime.
2. Should i patch the RDBMS_home on node1 , start all the oracle services on node1 , stop the oracle services on node2 and then resume the opatch on node1 which is waiting to patch the Grid_home on node2 ?
Please advice.
Thanks,
Ashok Kumar.G

Hi Sebastian,
14613223 patch install instruction did not mention about opatch -local option.
Here is what i followed and completed the installation successfully.
1. Shutdown all oracle services on node 1
2. applied opatch for grid home and then rdbms home using "opatch apply -local" on node1
3. Started all oracle services on node 1
4. Shutdown all oracle services on node 2
5. applied opatch for gridhome and then rdbms home using "opatch apply -local" on node 2
6. Started all oracle services on node 2
7. executed post installation steps on the DB (@catwinbundle.sql & @utlrp.sql )
Thanks,
Ashok Kumar.G

Help with cisco ISE 1.1.2.145 patch-3 to ISE 1.2.0.899-2-85601 upgrade procedure

Need help from ISE experts/gurus in this forum.
Due to a nasty bug in Cisco ISE (bug ID CSCue38827 ISE Adclient daemon not initializing on leave/join), this bug will make the ISE stopping working completely and a reboot is required (very nice bug from cisco) . This leaves me no choice but to upgrade to version 1.2.0.899-2-85601.
Scenario:
- 4 nodes in the environment running ISE version 1.1.2.145 patch 3
- node 1 is Primary Admin and Secondary Monitoring - hostname is node1
- node 2 is Secondary Admin and Primary Monitoring - hostname is node2
- node 3 is Policy service node - hostname is node3
- node 4 is Policy service node - hostname is node4
Objective: Upgrade the ISE environment to ISE version 1.2 with patch version 1.2.0.899-2-85601.
My understand is that I have to upgrade the existing environment from ISE version 1.1.2.145 patch 3
to ISE version 1.1.2.145 patch 10 (patch 10 was released on 10/04/2013) before I can proceed with
upgrading to ISE version 1.2 and patch it with 1.2.0.899-2-85601.
Can I patch my exsiting environment from 1.1.2 patch 3 to patch 10 prior to upgrading to version 1.2.0.899-2-85601?
I look at Cisco website and patch 10 was released on 10/04/2013 while version 1.2 was released back in 07/05/2013.
I am trying to get a definite answer from Cisco TAC but it seems like they don't know either.
Question #1: How do I proceed with upgrading the current ISE environment from 1.1.2.145 patch 3 to 1.1.2.145 patch 10?
Propose solution:
step #1: make ISE node1 to be both Primary Admin and Primary monitoring. ISE node2 is now Secondary Admin and Secondary Monitoring.
         Then go ahead and apply ISE version 1.1.2.145 patch 10 to ISE node2 via the GUI,
step #2: Once ISE node2 patch 10 is completed, make node2 Primary Admin and Primary Monitoring. At this point, apply ISE 1.1.2.145 patch 10
         to ISE node1 via the GUI,
step #3: Once ISE node1 patch 10 is completed, make node1 Primary Admin and Secondary Monitoring and node2 Secondary Admin and Primary Monitoring,
step #4: apply ISE 1.1.2.145 patch 10 to ISE Policy Service node3. Once that is completed, verify that node2 is working and accepting traffics,
step #5: apply ISE 1.1.2.145 patch 10 to ISE Policy Service node4. Once that is completed, verify that node2 is working and accepting traffics,
Question #2: How do I proceed with upgrading the current ISE environment from 1.1.2.145 patch 10 to ISE version 1.2 with patch version 1.2.0.899-2-85601?
Propose solution:
step #1: Make ISE node1 the Primary Admin and Primary monitoring. At this point ISE node2 will become Secondary Admin and Secondary Monitoring
step #2: Perform upgrade on the ISE node2 via the command line "application upgrade <app-bundle> <repository>". Once ISE node2 upgrade is completed, it will
          form a new ISE 1.2 cluster independent of the old cluster,
step #3: Perform upgrade on the ISE Policy Service node3 via the command line "application upgrade <app-bundle> <repository>". After the upgrade the ISE
          Policy Service Node3 will automatically joins the ISE node2 which is already in version 1.2
step #4: Perform upgrade on the ISE Policy Service node4 via the command line "application upgrade <app-bundle> <repository>". After the upgrade the ISE
          Policy Service Node4 will automatically joins the ISE node2 which is already in version 1.2
step #5: At this point the only node remaining in the 1.1.2.145 patch 10 is the ISE node1 Primary Admin and Primary Monitoring
step #6: Check and see if there are any more PSN's registered in ISE node1 (there should not be any)
step #7: Perform the upgrade on the ISE node1 from command line "application upgrade <app-bundle> <repository>"
step #8: Once upgrade on ISE node1 is complete, ISE node1 will automatically join the new ISE 1.2 cluster,
step #9: Make ISE node1 Primary Admin and Secondary and ISE node2 Secondary Admin and Primary Monitoring,
Question #3: How do I proceed with upgrading the current ISE environment from 1.2 patch0 to 1.2.0.899-2-85601?
Propose solution:
step #1: make ISE node1 to be both Primary Admin and Primary monitoring. ISE node2 is now Secondary Admin and Secondary Monitoring.
         Then go ahead and apply ISE 1.2.0.899-2-85601 to ISE node2 via the GUI,
step #2: Once ISE node2 1.2.0.899-2-85601 is completed, make node2 Primary Admin and Primary Monitoring. At this point, apply 1.2.0.899-2-85601
         to ISE node1 via the GUI,
step #3: Once ISE node1 patch 10 is completed, make node1 Primary Admin and Secondary Monitoring and node2 Secondary Admin and Primary Monitoring,
step #4: apply ISE 1.2.0.899-2-85601 to ISE Policy Service node3. Once that is completed, verify that node2 is working and accepting traffics,
step #5: apply ISE 1.2.0.899-2-85601 to ISE Policy Service node4. Once that is completed, verify that node2 is working and accepting traffics,
does these steps make sense to you?
Thanks in advance.

David,
A few answers to your questions -
Question 1: My recommendation is to follow vivek's blog since most fixes and upgrade steps are provided there - I would recommend installing the patch that was release prior to the 1.2 release date since the directions to "install the latest patch" would put you at the version of when the ISE 1.2 was released
https://supportforums.cisco.com/community/netpro/security/aaa/blog/2013/07/19/upgrading-to-identity-services-engine-ise-12
You do not have the ability to install ISE patch through the GUI on any of the "non-primary" nodes (you can use the cli commmand to achieve this), the current patching process was designed so you can install the patch on the primary admin node and it will then roll the patches out to the entire deployment (one node at at time). I painfully verified this by watching the services on each node and when a node was up and operational the next node would start the patching process. First the admin nodes then the PSNs.
Every ISE upgrade that I have attempted as not been flawless and I can assure you that I have done an upgrade on 1.1.2 patch 3 and this worked fine, however I used the following process. You will need the service account information that is used to join your ISE to AD.
I picked the secondary admin/monitoring node and made it a standalone node by deregistering (much like the old procedure) in your case this will be node2.
I backed up the certificates from the UI and the database from the CLI (pick the local disk or ftp-your choice).
I reset the database and ran the upgrade script (since I did not have access to the vsphere console or at the location of the non UCS hardware [for a 1.1.4 upgrade]).
Once the upgrade was completed I then restored the 1.1.x database, ISE 1.2 now has the ability to detect the version of the database that is restored and will perform the migration for you.
Once the restore finished, I then restored the certificate and picked one of the PSNs
backup the cert,
Had the AD join user account handy
reset-db,
and run the upgrade script.
Once that is done I then restore the cert
Join the PSN to the new deployment
Join both nodes to AD through primary admin node
Monitor for a few days (seperate consoles to make sure everything runs smooth)
If anything doesnt look or feel right, you can shut down the 1.2 PSN and force everything through the existing 1.1.2 setup and perform some investigation, if it all goes smooth you can then follow the above step for the other two nodes, starting with the last PSN and the the last admin node.
Thanks and I hope that helps,
Tarik Admani
*Please rate helpful posts*

Correct way to install patch in Oracle RAC

Hello,
What is the correct way to install a patch in an two-node Oracle RAC 11g on Windows server 2008? Each node has its own ORACLE_HOME.
Do I have to shut down one Node before I patch the other Node?
Or both nodes can be up when installing patch? First do it on Node 1 and then on Node2?
Thank you

Typically you can do a rolling upgrade, patch one node, then the next node without bringing down the entire cluster, but as rui_catcuddler suggested, follow the Oracle instructions as closely as possible.
We have found several bugs with RAC 11gR2 on Windows 2008 R2, some minor, some critical. If this is your Oracle version and platform then try to get to the latest Oracle RAC release 11.2.0.3.
Regards,
Kevin

OPatch encounters the following file roll-back issues: File Back-up Errors!

Operating System: Windows XP
Oracle Virsion: 9.2.0.8
Patches applied:
Oracle Patch: 5726045 - Successfully patched with zero return code.
Oracle Patch: 641703 - Failed with Error Code 200.
Scenario:
I have to apply CPUJAN2008 patch on 55 different servers located at different places in different states. Previously some other DBA had written a Windows NT Script for applying patch CPUOCT2007 on these
55 differnet servers which have the same instances, same filing system, same oracle version, same directories, same oracle_home, etc. In other words they are replicas to each other. For the purpose of
patching, the script is the best option. The Script for CPUOCT2007 was never went through, hence I am trying to test this CPUOCT2007 script and if tested allright, I will make certain amendmends to make it
ready for CPUJAN2008 patch.
Problem:
I tested the script for CPUOCT2007 patch and encountered the following problem:
I am providing the necessary information between the dotted lines:
Archive: p6417013_92080_WINNT.zip
Entered
Exited
~~~~~~~~~~~~~~6417013 patch~~~~~~~~~~~~~~
Oracle Interim Patch Installer version 1.0.0.0.57
Copyright (c) 2007 Oracle Corporation. All Rights Reserved..
We recommend you refer to the OPatch documentation under
OPatch/docs for usage reference. We also recommend using
the latest OPatch version. For the latest OPatch version
and other support related issues, please refer to document
293369.1 which is viewable from metalink.oracle.com
Oracle Home : D:\App\Oracle\Product\9.2.0
Oracle Home Inventory : D:\App\Oracle\Product\9.2.0\inventory
Central Inventory : C:\Program Files\oracle\inventory
from : N/A
OUI location : D:\App\Oracle\Product\9.2.0\oui
OUI shared library : D:\App\Oracle\Product\9.2.0\oui\lib\win32\oraInstaller.dll
Java location : "D:\App\Oracle\Product\9.2.0\jre\1.4.2\bin\java.exe"
Log file location : D:\App\Oracle\Product\9.2.0/.patch_storage/<patch ID>/*.log
Creating log file "D:\app\oracle\product\9.2.0\.patch_storage\6417013\Apply_6417013_03-29-2008_14-43-19.log"
Subset patches: 6417013,
The fixes for Patch 6417013, are included in the patch currently
being installed (6417013). OPatch will roll back the subset patch(es) and
install the new patch (6417013).
Backing up comps.xml ...
OPatch detected non-cluster Oracle Home from the inventory and will patch the local system only.
Please shut down Oracle instances running out of this ORACLE_HOME
(Oracle Home = d:\app\oracle\product\9.2.0)
Is this system ready for updating?
Please respond Y|N >
Y (auto-answered by -silent)
Rolling back patch 6417013...
Creating log file "D:\app\oracle\product\9.2.0\.patch_storage\6417013\RollBack_6417013_03-29-2008_14-43-35.log"
Rolling back with all-node mode.
OPatch detected non-cluster Oracle Home from the inventory and will patch the local system only.
Oracle instances have been shut down, proceeding with auto-rollback.
Executing the Roll-back pre-patch script (D:\app\oracle\product\9.2.0\.patch_storage\6417013\custom\scripts\pre.bat)...
Removing patch 6417013...
Restoring copied files...
OPatch encounters the following file roll-back issues:
The following files had problems with being restored:
1.     d:\app\oracle\product\9.2.0\bin\oracle.exe
2.     d:\app\oracle\product\9.2.0\bin\oraclient9.dll
3.     d:\app\oracle\product\9.2.0\bin\oracommon9.dll
4.     d:\app\oracle\product\9.2.0\bin\oracore9.dll
5.     d:\app\oracle\product\9.2.0\bin\orageneric9.dll
6.     d:\app\oracle\product\9.2.0\bin\oran9.dll
7.     d:\app\oracle\product\9.2.0\bin\oranl9.dll
8.     d:\app\oracle\product\9.2.0\bin\oranldap9.dll
9.     d:\app\oracle\product\9.2.0\bin\orannts9.dll
10.     d:\app\oracle\product\9.2.0\bin\orapls9.dll
11.     d:\app\oracle\product\9.2.0\bin\oraxml9.dll
12.     d:\app\oracle\product\9.2.0\rdbms\mesg\oraus.msb
Replying 'Y' will terminate the patch roll-back immediately. It WILL NOT restore any updates that have been performed to this point. It WILL NOT update the inventory.
Replying 'N' will update the inventory showing the patch has been removed.
Do you want to STOP?
Please respond Y|N >
Y (auto-answered by -silent)
ERROR: OPatch failed during patching, possibly due to missing files.
File Back-up Errors!
OPatch returns with error code = 200
The rollback file provided the following (See between the dotted lines)
Creating log file "D:\app\oracle\product\9.2.0\.patch_storage\6417013\RollBack_6417013_03-29-2008_14-43-35.log"
Starting OPatch Rollback session at 03-29-2008_14-43-35.
Command arguments parsed by OPatch are: -id 6417013 -ph D:\app\oracle\product\9.2.0\6417013
Checking the patch inventory.
Checking system activity.
Retrieving details of patch 6417013.
Accessing inventory ... (retry 10 times, delay 30 seconds each time)
System Command: ""D:\App\Oracle\Product\9.2.0\jre\1.4.2\bin\java.exe" -Doracle.installer.invPtrLoc=N/A -classpath "D:\App\Oracle\Product\9.2.0\oui\jlib\OraInstaller.jar;D:\App\Oracle\Product\9.2.0
\oui\jlib\srvm.jar;D:\app\oracle\product\9.2.0\OPatch\jlib\opatch.jar;D:\app\oracle\product\9.2.0\oui\jlib\xmlparserv2.jar;D:\app\oracle\product\9.2.0\oui\jlib\share.jar" opatch/GetPatchDetails
"D:\App\Oracle\Product\9.2.0\oui" "d:\app\oracle\product\9.2.0" opatch.pl 1.0.0.0.57 6417013"
Result:
6417013: D:/app/oracle/product/9.2.0/network/agent/events/oracle/rdbms/space/tbspfull.tcl
6417013: D:/app/oracle/product/9.2.0/bin/agentctl.exe
6417013: D:/app/oracle/product/9.2.0/bin/agntsrvc.exe
6417013: D:/app/oracle/product/9.2.0/bin/ctxhx.exe
6417013: D:/app/oracle/product/9.2.0/bin/dbsnmp.exe
6417013: D:/app/oracle/product/9.2.0/bin/dbv.exe
6417013: D:/app/oracle/product/9.2.0/bin/EXP.EXE
6417013: D:/app/oracle/product/9.2.0/bin/htmcnv.dll
6417013: D:/app/oracle/product/9.2.0/bin/htmsr.dll
6417013: D:/app/oracle/product/9.2.0/bin/IMP.EXE
6417013: D:/app/oracle/product/9.2.0/bin/jtdsr.dll
6417013: D:/app/oracle/product/9.2.0/bin/kvxwpsa.dll
6417013: D:/app/oracle/product/9.2.0/bin/mw8sr.dll
6417013: D:/app/oracle/product/9.2.0/bin/oidldapd.exe +> NEW
6417013: D:/app/oracle/product/9.2.0/bin/oracle.exe
6417013: D:/app/oracle/product/9.2.0/bin/oraclient9.dll
6417013: D:/app/oracle/product/9.2.0/bin/oracommon9.dll
6417013: D:/app/oracle/product/9.2.0/bin/ORACORE9.DLL
6417013: D:/app/oracle/product/9.2.0/bin/orageneric9.dll
6417013: D:/app/oracle/product/9.2.0/bin/oran9.dll
6417013: D:/app/oracle/product/9.2.0/bin/ORANK59.DLL
6417013: D:/app/oracle/product/9.2.0/bin/oranl9.dll
6417013: D:/app/oracle/product/9.2.0/bin/oranldap9.dll
6417013: D:/app/oracle/product/9.2.0/bin/oranmi.dll
6417013: D:/app/oracle/product/9.2.0/bin/orannts9.dll
6417013: D:/app/oracle/product/9.2.0/bin/ORAPLS9.DLL
6417013: D:/app/oracle/product/9.2.0/bin/ORAXML9.DLL
6417013: D:/app/oracle/product/9.2.0/bin/pdfsr.dll
6417013: D:/app/oracle/product/9.2.0/bin/SQLLDR.EXE
6417013: D:/app/oracle/product/9.2.0/bin/sqlplus.exe
6417013: D:/app/oracle/product/9.2.0/bin/sqlplusw.exe
6417013: D:/app/oracle/product/9.2.0/bin/vdc.dll
6417013: D:/app/oracle/product/9.2.0/bin/wp6sr.dll
6417013: D:/app/oracle/product/9.2.0/bin/xlssr.dll
6417013: D:/app/oracle/product/9.2.0/plsql/lib/orapls9.lib +> NEW
6417013: D:/app/oracle/product/9.2.0/rdbms/admin/oracle.sym
6417013: D:/app/oracle/product/9.2.0/rdbms/admin/oraclient9.sym
6417013: D:/app/oracle/product/9.2.0/rdbms/admin/oracommon9.sym
6417013: D:/app/oracle/product/9.2.0/rdbms/admin/ORACORE9.SYM
6417013: D:/app/oracle/product/9.2.0/rdbms/admin/orageneric9.sym
6417013: D:/app/oracle/product/9.2.0/rdbms/admin/ORAPLS9.SYM
6417013: D:/app/oracle/product/9.2.0/rdbms/admin/prvtbadd.plb
6417013: D:/app/oracle/product/9.2.0/rdbms/admin/prvtbath.plb
6417013: D:/app/oracle/product/9.2.0/rdbms/admin/prvtbkrs.plb
6417013: D:/app/oracle/product/9.2.0/rdbms/admin/prvtbmas.plb
6417013: D:/app/oracle/product/9.2.0/rdbms/admin/prvtbobg.plb
6417013: D:/app/oracle/product/9.2.0/rdbms/admin/prvtbrpc.plb
6417013: D:/app/oracle/product/9.2.0/rdbms/admin/prvtbrrq.plb
6417013: D:/app/oracle/product/9.2.0/rdbms/admin/prvtbsqu.plb
6417013: D:/app/oracle/product/9.2.0/rdbms/admin/prvtbut4.plb
6417013: D:/app/oracle/product/9.2.0/rdbms/admin/prvtbutl.plb
6417013: D:/app/oracle/product/9.2.0/rdbms/admin/prvtgen.plb
6417013: D:/app/oracle/product/9.2.0/rdbms/admin/prvtofln.plb
6417013: D:/app/oracle/product/9.2.0/rdbms/admin/prvtpexp.plb
6417013: D:/app/oracle/product/9.2.0/rdbms/admin/prvtsath.plb
6417013: D:/app/oracle/product/9.2.0/rdbms/admin/prvtxdbp.plb
6417013: D:/app/oracle/product/9.2.0/rdbms/admin/prvtxdbz.plb
6417013: D:/app/oracle/product/9.2.0/rdbms/admin/recover.bsq
6417013: D:/app/oracle/product/9.2.0/rdbms/mesg/dbvus.msb
6417013: D:/app/oracle/product/9.2.0/rdbms/mesg/oraus.msb
6417013: D:/app/oracle/product/9.2.0/rdbms/jlib/CDC.jar
6417013: D:/app/oracle/product/9.2.0/cpu/cpuoct2007/catcpu.sql +> NEW
6417013: D:/app/oracle/product/9.2.0/cpu/cpuoct2007/catcpu_rollback.sql +> NEW
6417013: D:/app/oracle/product/9.2.0/cpu/cpuoct2007/ctxcpu.sql +> NEW
6417013: D:/app/oracle/product/9.2.0/cpu/cpuoct2007/imcpu.sql +> NEW
6417013: D:/app/oracle/product/9.2.0/cpu/cpuoct2007/imcpu_rollback.sql +> NEW
6417013: D:/app/oracle/product/9.2.0/cpu/cpuoct2007/jvmcpu.sql +> NEW
6417013: D:/app/oracle/product/9.2.0/cpu/cpuoct2007/sdocpu.sql +> NEW
6417013: D:/app/oracle/product/9.2.0/cpu/cpuoct2007/wkcpu.sql +> NEW
6417013: D:/app/oracle/product/9.2.0/cpu/cpuoct2007/xdbcpu.sql +> NEW
6417013: D:/app/oracle/product/9.2.0/soap/webapps/soap/WEB-INF/lib/soap.jar
6417013: D:/app/oracle/product/9.2.0/soap/webapps/soap/WEB-INF/lib/xmlparserv2-soap.jar +> NEW
6417013: D:/app/oracle/product/9.2.0/Apache/Apache/Apache.exe
6417013: D:/app/oracle/product/9.2.0/Apache/Apache/ApacheCore.dll
6417013: D:/app/oracle/product/9.2.0/Apache/Apache/bin/htdigest.exe
6417013: D:/app/oracle/product/9.2.0/Apache/Apache/bin/htpasswd.exe
6417013: D:/app/oracle/product/9.2.0/Apache/Apache/bin/rotatelogs.exe
6417013: D:/app/oracle/product/9.2.0/Apache/Apache/modules/ApacheModuleDigest.dll
6417013: D:/app/oracle/product/9.2.0/Apache/Apache/modules/ApacheModuleDMS.dll
6417013: D:/app/oracle/product/9.2.0/Apache/Apache/modules/ApacheModuleFastCGI.dll
6417013: D:/app/oracle/product/9.2.0/Apache/Apache/modules/ApacheModuleOprocmgr.dll
6417013: D:/app/oracle/product/9.2.0/Apache/Apache/modules/ApacheModuleProxy.dll
6417013: D:/app/oracle/product/9.2.0/Apache/Apache/modules/ApacheModuleRewrite.dll
6417013: D:/app/oracle/product/9.2.0/Apache/Apache/modules/ApacheModuleSecurity.dll +> NEW
6417013: D:/app/oracle/product/9.2.0/Apache/Apache/modules/ApacheModuleSSL.dll
6417013: D:/app/oracle/product/9.2.0/Apache/Apache/htdocs/mod_ose.html
6417013: D:/app/oracle/product/9.2.0/Apache/Jserv/ApacheJServ.jar
6417013: D:/app/oracle/product/9.2.0/Apache/Jserv/ApacheModuleJServ.dll
6417013: D:/app/oracle/product/9.2.0/Apache/Jserv/dms2Client.jar
6417013: D:/app/oracle/product/9.2.0/Apache/Jserv/dms2Server.jar
6417013: D:/app/oracle/product/9.2.0/Apache/Jserv/servlets/IsItWorking.class
6417013: D:/app/oracle/product/9.2.0/Apache/Jserv/servlets/IsItWorking.java
6417013: D:/app/oracle/product/9.2.0/ocs4j/lib/cache.jar
6417013: D:/app/oracle/product/9.2.0/Apache/open_ssl/bin/openssl.exe
6417013: D:/app/oracle/product/9.2.0/lib/xmlcomp.jar
6417013: D:/app/oracle/product/9.2.0/ctx/admin/driload.plb
6417013: D:/app/oracle/product/9.2.0/ord/jlib/ordimimg.jar
6417013: D:/app/oracle/product/9.2.0/ord/jlib/ordimimg_depl.jar
6417013: D:/app/oracle/product/9.2.0/javavm/admin/classes.bin
6417013: D:/app/oracle/product/9.2.0/javavm/admin/ordimimg_lib.jar +> NEW
6417013: D:/app/oracle/product/9.2.0/md/admin/prvtcat.plb
6417013: D:/app/oracle/product/9.2.0/md/admin/prvtgmd.plb
6417013: D:/app/oracle/product/9.2.0/md/admin/prvtrtr.plb
6417013: D:/app/oracle/product/9.2.0/md/admin/sdolrsb.plb
6417013: D:/app/oracle/product/9.2.0/md/admin/sdopatch.sql
6417013: D:/app/oracle/product/9.2.0/ultrasearch/lib/ultrasearch_midtier.jar
6417013: D:/app/oracle/product/9.2.0/ultrasearch/admin/wk0qapi.plb
6417013: D:/app/oracle/product/9.2.0/ultrasearch/admin/wk0qry.plb
6417013: D:/app/oracle/product/9.2.0/oracore/zoneinfo/readme.txt
6417013: D:/app/oracle/product/9.2.0/oracore/zoneinfo/timezlrg.dat
6417013: D:/app/oracle/product/9.2.0/oracore/zoneinfo/timezone.dat
Retrieving patch to roll back: patch_found = 1.
Looking for pre-patch readme D:\app\oracle\product\9.2.0\.patch_storage\6417013\custom\pre.txt
Rolling back with all-node mode.
OPatch detected non-cluster Oracle Home from the inventory and will patch the local system only.
Oracle instances have been shut down, proceeding with auto-rollback.
Starting to remove patch from the system at 03-29-2008_14-43-41.
Looking for pre-patch script D:\app\oracle\product\9.2.0\.patch_storage\6417013\custom\scripts\pre.bat
preparing to execute D:\app\oracle\product\9.2.0\.patch_storage\6417013\custom\scripts\pre.bat
Executing the Roll-back pre-patch script (D:\app\oracle\product\9.2.0\.patch_storage\6417013\custom\scripts\pre.bat)...
======= Pre-Install Script Output ==============================
exit code = "0"
======= End of Pre-Install Script Output =======================
Removing patch 6417013...
Restore Archive File
Restore Copy File
Restoring copied files...
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\network\agent\events\oracle\rdbms\space\tbspfull.tcl_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\bin\agentctl.exe_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\bin\agntsrvc.exe_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\bin\ctxhx.exe_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\bin\dbsnmp.exe_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\bin\dbv.exe_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\bin\exp.exe_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\bin\htmcnv.dll_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\bin\htmsr.dll_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\bin\imp.exe_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\bin\jtdsr.dll_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\bin\kvxwpsa.dll_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\bin\mw8sr.dll_done_6417013
Restoring d:\app\oracle\product\9.2.0\bin\oidldapd.exe.
Restoring d:\app\oracle\product\9.2.0\bin\oracle.exe.
Restoring file: D:\app\oracle\product\9.2.0\.patch_storage\6417013\\bin\oracle.exe_pre_6417013 -> d:\app\oracle\product\9.2.0\bin\oracle.exe
Restoring d:\app\oracle\product\9.2.0\bin\oraclient9.dll.
Restoring file: D:\app\oracle\product\9.2.0\.patch_storage\6417013\\bin\oraclient9.dll_pre_6417013 -> d:\app\oracle\product\9.2.0\bin\oraclient9.dll
Restoring d:\app\oracle\product\9.2.0\bin\oracommon9.dll.
Restoring file: D:\app\oracle\product\9.2.0\.patch_storage\6417013\\bin\oracommon9.dll_pre_6417013 -> d:\app\oracle\product\9.2.0\bin\oracommon9.dll
Restoring d:\app\oracle\product\9.2.0\bin\oracore9.dll.
Restoring file: D:\app\oracle\product\9.2.0\.patch_storage\6417013\\bin\oracore9.dll_pre_6417013 -> d:\app\oracle\product\9.2.0\bin\oracore9.dll
Restoring d:\app\oracle\product\9.2.0\bin\orageneric9.dll.
Restoring file: D:\app\oracle\product\9.2.0\.patch_storage\6417013\\bin\orageneric9.dll_pre_6417013 -> d:\app\oracle\product\9.2.0\bin\orageneric9.dll
Restoring d:\app\oracle\product\9.2.0\bin\oran9.dll.
Restoring file: D:\app\oracle\product\9.2.0\.patch_storage\6417013\\bin\oran9.dll_pre_6417013 -> d:\app\oracle\product\9.2.0\bin\oran9.dll
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\bin\orank59.dll_done_6417013
Restoring d:\app\oracle\product\9.2.0\bin\oranl9.dll.
Restoring file: D:\app\oracle\product\9.2.0\.patch_storage\6417013\\bin\oranl9.dll_pre_6417013 -> d:\app\oracle\product\9.2.0\bin\oranl9.dll
Restoring d:\app\oracle\product\9.2.0\bin\oranldap9.dll.
Restoring file: D:\app\oracle\product\9.2.0\.patch_storage\6417013\\bin\oranldap9.dll_pre_6417013 -> d:\app\oracle\product\9.2.0\bin\oranldap9.dll
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\bin\oranmi.dll_done_6417013
Restoring d:\app\oracle\product\9.2.0\bin\orannts9.dll.
Restoring file: D:\app\oracle\product\9.2.0\.patch_storage\6417013\\bin\orannts9.dll_pre_6417013 -> d:\app\oracle\product\9.2.0\bin\orannts9.dll
Restoring d:\app\oracle\product\9.2.0\bin\orapls9.dll.
Restoring file: D:\app\oracle\product\9.2.0\.patch_storage\6417013\\bin\orapls9.dll_pre_6417013 -> d:\app\oracle\product\9.2.0\bin\orapls9.dll
Restoring d:\app\oracle\product\9.2.0\bin\oraxml9.dll.
Restoring file: D:\app\oracle\product\9.2.0\.patch_storage\6417013\\bin\oraxml9.dll_pre_6417013 -> d:\app\oracle\product\9.2.0\bin\oraxml9.dll
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\bin\pdfsr.dll_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\bin\sqlldr.exe_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\bin\sqlplus.exe_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\bin\sqlplusw.exe_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\bin\vdc.dll_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\bin\wp6sr.dll_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\bin\xlssr.dll_done_6417013
Restoring d:\app\oracle\product\9.2.0\plsql\lib\orapls9.lib.
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\rdbms\admin\oracle.sym_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\rdbms\admin\oraclient9.sym_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\rdbms\admin\oracommon9.sym_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\rdbms\admin\oracore9.sym_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\rdbms\admin\orageneric9.sym_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\rdbms\admin\orapls9.sym_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\rdbms\admin\prvtbadd.plb_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\rdbms\admin\prvtbath.plb_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\rdbms\admin\prvtbkrs.plb_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\rdbms\admin\prvtbmas.plb_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\rdbms\admin\prvtbobg.plb_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\rdbms\admin\prvtbrpc.plb_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\rdbms\admin\prvtbrrq.plb_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\rdbms\admin\prvtbsqu.plb_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\rdbms\admin\prvtbut4.plb_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\rdbms\admin\prvtbutl.plb_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\rdbms\admin\prvtgen.plb_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\rdbms\admin\prvtofln.plb_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\rdbms\admin\prvtpexp.plb_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\rdbms\admin\prvtsath.plb_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\rdbms\admin\prvtxdbp.plb_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\rdbms\admin\prvtxdbz.plb_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\rdbms\admin\recover.bsq_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\rdbms\mesg\dbvus.msb_done_6417013
Restoring d:\app\oracle\product\9.2.0\rdbms\mesg\oraus.msb.
Restoring file: D:\app\oracle\product\9.2.0\.patch_storage\6417013\\rdbms\mesg\oraus.msb_pre_6417013 -> d:\app\oracle\product\9.2.0\rdbms\mesg\oraus.msb
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\rdbms\jlib\cdc.jar_done_6417013
Restoring d:\app\oracle\product\9.2.0\cpu\cpuoct2007\catcpu.sql.
Restoring d:\app\oracle\product\9.2.0\cpu\cpuoct2007\catcpu_rollback.sql.
Restoring d:\app\oracle\product\9.2.0\cpu\cpuoct2007\ctxcpu.sql.
Restoring d:\app\oracle\product\9.2.0\cpu\cpuoct2007\imcpu.sql.
Restoring d:\app\oracle\product\9.2.0\cpu\cpuoct2007\imcpu_rollback.sql.
Restoring d:\app\oracle\product\9.2.0\cpu\cpuoct2007\jvmcpu.sql.
Restoring d:\app\oracle\product\9.2.0\cpu\cpuoct2007\sdocpu.sql.
Restoring d:\app\oracle\product\9.2.0\cpu\cpuoct2007\wkcpu.sql.
Restoring d:\app\oracle\product\9.2.0\cpu\cpuoct2007\xdbcpu.sql.
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\soap\webapps\soap\web-inf\lib\soap.jar_done_6417013
Restoring d:\app\oracle\product\9.2.0\soap\webapps\soap\web-inf\lib\xmlparserv2-soap.jar.
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\apache\apache\apache.exe_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\apache\apache\apachecore.dll_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\apache\apache\bin\htdigest.exe_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\apache\apache\bin\htpasswd.exe_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\apache\apache\bin\rotatelogs.exe_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\apache\apache\modules\apachemoduledigest.dll_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\apache\apache\modules\apachemoduledms.dll_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\apache\apache\modules\apachemodulefastcgi.dll_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\apache\apache\modules\apachemoduleoprocmgr.dll_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\apache\apache\modules\apachemoduleproxy.dll_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\apache\apache\modules\apachemodulerewrite.dll_done_6417013
Restoring d:\app\oracle\product\9.2.0\apache\apache\modules\apachemodulesecurity.dll.
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\apache\apache\modules\apachemodulessl.dll_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\apache\apache\htdocs\mod_ose.html_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\apache\jserv\apachejserv.jar_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\apache\jserv\apachemodulejserv.dll_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\apache\jserv\dms2client.jar_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\apache\jserv\dms2server.jar_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\apache\jserv\servlets\isitworking.class_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\apache\jserv\servlets\isitworking.java_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\ocs4j\lib\cache.jar_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\apache\open_ssl\bin\openssl.exe_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\lib\xmlcomp.jar_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\ctx\admin\driload.plb_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\ord\jlib\ordimimg.jar_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\ord\jlib\ordimimg_depl.jar_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\javavm\admin\classes.bin_done_6417013
Restoring d:\app\oracle\product\9.2.0\javavm\admin\ordimimg_lib.jar.
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\md\admin\prvtcat.plb_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\md\admin\prvtgmd.plb_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\md\admin\prvtrtr.plb_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\md\admin\sdolrsb.plb_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\md\admin\sdopatch.sql_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\ultrasearch\lib\ultrasearch_midtier.jar_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\ultrasearch\admin\wk0qapi.plb_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\ultrasearch\admin\wk0qry.plb_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\oracore\zoneinfo\readme.txt_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\oracore\zoneinfo\timezlrg.dat_done_6417013
File patched on previous run, will be skipped : D:\app\oracle\product\9.2.0\.patch_storage\6417013\\oracore\zoneinfo\timezone.dat_done_6417013
Restore Jar File
Restoring jar files...
OPatch encounters the following file roll-back issues:
The following files had problems with being restored:
1.     d:\app\oracle\product\9.2.0\bin\oracle.exe
2.     d:\app\oracle\product\9.2.0\bin\oraclient9.dll
3.     d:\app\oracle\product\9.2.0\bin\oracommon9.dll
4.     d:\app\oracle\product\9.2.0\bin\oracore9.dll
5.     d:\app\oracle\product\9.2.0\bin\orageneric9.dll
6.     d:\app\oracle\product\9.2.0\bin\oran9.dll
7.     d:\app\oracle\product\9.2.0\bin\oranl9.dll
8.     d:\app\oracle\product\9.2.0\bin\oranldap9.dll
9.     d:\app\oracle\product\9.2.0\bin\orannts9.dll
10.     d:\app\oracle\product\9.2.0\bin\orapls9.dll
11.     d:\app\oracle\product\9.2.0\bin\oraxml9.dll
12.     d:\app\oracle\product\9.2.0\rdbms\mesg\oraus.msb
Replying 'Y' will terminate the patch roll-back immediately. It WILL NOT restore any updates that have been performed to this point. It WILL NOT update the inventory.
Replying 'N' will update the inventory showing the patch has been removed.
Do you want to STOP?
Please respond Y|N >
Y (auto-answered by -silent)
File Back-up Errors!
ERROR: OPatch failed during patching, possibly due to missing files.
Please provide me a resolution as I have tried my best in google, yahoo and different place with no luck as yet.
Thanks,
blf2vkr

Hi there:
My greetings and regards for all the efforts you are putting to resolve this issue.
Thanks!
I have checked all the Oracle Related services including Distributed Transaction Coordinator were stopped. In a summury the following services were stopped before the patched were applied.
1. OracleOra920Agent
2. OracleOra920TNSListener
3. OracleServiceMission
4. OracleServiceReposit
5. Distributed Transaction Coordinator
Here it shows as follows when I execute the command lsinventory:
D:\app\oracle\product\9.2.0\OPatch>opatch lsinventory
Oracle Interim Patch Installer version 1.0.0.0.57
Copyright (c) 2007 Oracle Corporation. All Rights Reserved..
We recommend you refer to the OPatch documentation under
OPatch/docs for usage reference. We also recommend using
the latest OPatch version. For the latest OPatch version
and other support related issues, please refer to document
293369.1 which is viewable from metalink.oracle.com
Oracle Home : D:\app\oracle\product\9.2.0
Oracle Home Inventory : D:\app\oracle\product\9.2.0\inventory
Central Inventory : C:\Program Files\oracle\inventory
from : N/A
OUI location : D:\app\oracle\product\9.2.0\oui
OUI shared library : D:\app\oracle\product\9.2.0\oui\lib\win32\oraInstaller.dll
Java location : "D:\app\oracle\product\9.2.0\jre\1.4.2\bin\java.exe"
Log file location : D:\app\oracle\product\9.2.0/.patch_storage/<patch ID>/*.log
Creating log file "D:\app\oracle\product\9.2.0\.patch_storage\LsInventory__03-31-2008_10-34-33.log"
Result:
Installed Patch List:
=====================
1) Patch 5878965 applied on Sat Mar 29 14:43:08 EST 2008
[ Base Bug(s): 5726045 ]
2) Patch 6417013 applied on Fri Dec 21 10:42:43 EST 2007
[ Base Bug(s): 4689959 5263201 5354122 5214373 5901910 5211863 3308166 4057920 5660451 5172444 5744161 5530583 508423
9 4660718 5731178 3578226 5887105 6395038 5901875 4483286 5523578 6079582 3755693 5576565 5609388 5385973 5845928 2558849 5
369855 5865568 5958589 3036540 5116414 6417013 4401437 4219214 6130292 5723241 6130293 5860241 3870360 5129407 5065418 6404
861 5671074 6263319 5639513 5631836 5225596 5068565 5530958 5275475 5284862 5169684 5566937 5495695 5977665 5396877 6079599
6133610 5223027 4628013 5681320 5911532 4254094 5188321 5602654 3667025 4480159 6028753 3378426 5728380 5703297 5650477 60
38279 5842790 4905638 4593537 5629365 5970484 5933477 5523799 2775579 5895827 5345999 5031712 5140931 3639130 3521347 45415
24 5491035 5391326 5652380 5845232 5915901 3679014 4901089 4695511 3920693 4372359 4969005 5505981 5509707 5765361 5726094
5562159 6128197 3959063 5762618 2965960 4966417 5149865 5742895 4998554 5887577 ]
OPatch succeeded.
OPatch returns with error code = 0
D:\app\oracle\product\9.2.0\OPatch>
Truly Yours,
blf2vkr

Jdeveloper Patch for Ebusiness Suite 11.5.10

Dear Members,
I am confused regarding the JDeveloper patch i need to download from metalink pertaining to our version of e business suite and OA Frame Work.
OA Frame work version we have is :
Product/Component Version
OA Framework - 11.5.10 4RUP
Oracle Applications Extension - 9.0.3.8.13 - build 1541
Business Components - 9.0.3.13.87
UIX (Cabo) - 2_2_24
BiBeans Runtime - 3.1.0.70 nondebug BI Beans OAF 11.5.10 Production Release
MDS - 9.0.5.4.89_555
XML - Oracle XDK Java 9.0.4.0.0 Production
AOL/J - Applications Object Library, Core Java Roll Up Patch J
Servlet - 2.2
Java - 1.4.2
JDBC Driver - 9.2.0.6.0
Database - Oracle9i Enterprise Edition Release 9.2.0.7.0 - 64bit Production
Operating System - AIX 5.3
Browser - Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; GTB6; .NET CLR 2.0.50727; InfoPath.1)
From Metalink i found the below information:
Release 11i
OA Framework 5.10 patch      ---- JDeveloper 9i Patch
ATG.PF.H (patch 3438354 or Oracle Applications 11.5.10) --     Patch 4045639 9IJDEVELOPER WITH OA EXTENSION ARU FOR FWK.H
ATG PF CU1 (patch 4017300)      -- Patch 4141787 9IJDEVELOPER WITH OA EXTENSION ARU FOR CU1
ATG PF CU2 (patch 4125550)      -- Patch 4573517 Oracle9i JDeveloper with OA Extension for 11.5.10 CU2
11i.ATG_PF.H RUP3 (patch 4334965)      -- Patch 4725670 9IJDEVELOPER WITH OA EXTENSION ARU FOR 11i10 RUP3
11i.ATG_PF.H RUP4 (patch 4676589)      -- Patch 5455514 9IJDEVELOPER WITH OA EXTENSION ARU FOR 11i10 RUP4
11i.ATG_PF.H RUP5 (patch 5473858)      -- Patch 6012619 9IJDeveloper With OA Extension ARU FOR 11i10 RUP5
11i.ATG_PF.H.RUP6 (patch 5903765) -- Patch 6739235 9IJDeveloper With OA Extension ARU FOR 11i10 RUP6
AS you can see we are on 11.5.10 4RUP version of OA Framework, but in metalink when i see, i am confused between two patches :
ATG.PF.H (patch 3438354 or Oracle Applications 11.5.10) --     Patch 4045639 9IJDEVELOPER WITH OA EXTENSION ARU FOR FWK.H
11i.ATG_PF.H RUP4 (patch 4676589)      -- Patch 5455514 9IJDEVELOPER WITH OA EXTENSION ARU FOR 11i10 RUP4
Should i download Patch 4045639 or Patch 5455514 for Jdeveloper. Both of them seems like related to 11.5.10 version of ebusiness suite.
Thanks
Sandeep

11i.ATG_PF.H RUP4 (patch 4676589) -- Patch 5455514 9IJDEVELOPER WITH OA EXTENSION ARU FOR 11i10 RUP4

Oracle Time and Labor Patch 4773293 - HXT.I CUMULATIVE BACKPORTS 5

Oracle Time and Labor Patch 4773293 - HXT.I CUMULATIVE BACKPORTS 5 has been released to MetaLink for download.
This patch contains a number of important fixes. oracle Development recommends customers on HXT I level to apply this patch.
Patch details, prerequisites and installation instruction are contained in the 4773293 Readme.
Regards,
Greg

Greg,
Thanks for this update.
You state that this is the final roll up patch on HXT-I.
Isn't Oracle policy to provide backported patches on the last two minipacks? Wouldn't that currently be HXT-I and HXT-J?
Regards,
Mark

Latest Oracle DB 11g patch

Hi all,
Can you give me a link from where to download the latest patch for oracle database 11g R2? I've had some patch installed but i reinstalled Windows and i don't know exactly what patch was... and what includes that patch?
Also, do i need first to install the database 11g R2 and after that the patch, or directly the patch?
Thanks

Patch Set Updates
Document Description Rolling RAC Patch Download
Note:13343438.8 11.2.0.3.1 Patch Set Update (PSU) Yes Patch:13343438

SAP Kernel patch/Support pack Sequence

Hi,
I wanted to know if i need to follow up any order in applying latest kernel patch & Support Pack.
I have installed WAS 6.40 SR1 & want to upgrade to SPS 16. Before applying support pack do i need to apply latest
kernel ?
Is there any side effects for applying latest kernel patch ?
Kindly help me
Thanks,
ramki

Ramki, as other posts say the kernel update is part of SPS16 & should always be applied. But as to the order... it will most likely come down to business requirements and preference & may change for you from stack to stack.
Be sure to test first in your DEV environment (or similar) & always check the known issues notes which should tell you any patch to kernel dependancies that may dictate what order you have to install things (782140 is the note for WAS6.20, sorry don't have the WAS640 note number handy).
In terms of side effects? In my experience (4.0b - ecc6) the kernel will either work or not work (ie system will or wont start!) If it dosn't work roll back to the previous version (also keep a copy of the exe directory!) & things should all be OK.
Generally we always apply the kernel after the patches where I work (just fits in better with managing downtime on prod systems). However last time we patched the SPAM queue we defined was very large & not compatible with our R3Trans release when using the downtime minimised option (this was stated in the known issues note I mentioned earlier). So the kernel update was done 2-3 weeks before we rolled the patches in, once again just to manage prod system downtime better.
Hope that helps a little
Danny

Doubt about Rollup Patches and Family Packs

Hi All,
What is the difference between Rollup patches and family packs?And also applying family packs will increase the codelvel?Please specify the naming convention of both the pacthes also.
Thanks
Rajasekar

Thanks Kashif M &Hussein for your valuable replies.I've read the links. As per the documennt in r12.
Product family release update pack (product family RUP) An aggregation of patches on a given codeline created for all products in specific product family for a specific point release. For example, R12.FIN_PF.A.1.
Release update pack (RUP) A cumulative aggregation of product family release update packs on a given codeline created across Oracle E-Business Suite after the initial release. For example, 12.1.1.
RUP in r12 is similar to family pack(11i) which will change the third digit (12.1.1 to 12.1.2).right?
Product family release update pack(family pack) with new features called rollup patch?
(or)
About rollup patch I read in one apps dba blog
Rollup patces are usually fixes of all issues popped up because of a particular minipack/familypack or maintenance pack. Lets assume you applied a family pack & because of that some issue/bug came into picture or all bugs reported soon after family pack or maintenance pack are fixed and released as Roll Up patch . These are usually denoted as roll up 1 rollup 2 or roll up A roll up B.
So you will see maintenance pack 10 (11.5.10) roll up 1 or roll up2.
How can we identify the roll up level?
Thanks
Rajasekar
Edited by: user9113570 on Jun 5, 2012 8:30 AM

Patching Methodology and Configuration

SCCM 2012 SP1
We recently implemented monthly patching via SCCM and I’ve been asked to reevaluate the methodology I put into place as well as some configuration items.
My question revolves around methodology and configuration.
Sorry for long documentation but need to get point across and find out best methodologies and the way your organization is using SCCM to patch.
CURRENT METHODOLOGY
We roll out patches in a 3 wave approach to an organization that has 4 geographic sites.
IT department and testers during the 3 days following Patch Tuesday – configuration of ADR below.
Sub-Process
Evaluate on Wed of Update patches to include/decline from deployment as not included in software Update classification to prevent unwanted optional updates from being applied
Checklist review after patching by IT Dept. and testers
Deployment to local geographic site which is local to the IT Department on the Tuesday following Patch Tuesday with a 10 day window for install.
Approximately 150 users. Idea here was users are local to IT and we can respond faster to problems
Deployment to Entire Company on the 2<sup>nd</sup> day of following month (Approximately 400 Users (remote and local)
ADR Settings
Roll-Out 1
Software Update Tab
Date: Last month
Product: Lync, Office, Silverlight, Windows 7, Windows 8, Adobe patches
Update Classification: Critical Updates OR Security Updates OR Service Packs
Note: Not including Updates
Evaluation Schedule
Second Wed of every one month @ 7am
Deployment Schedule
Software Available Time: 2 hours
Installation Deadline: 46 hours
User Experience
Software Installation, System Restart Checked
Suppress: Only Servers checked (for configuration discussion)
Roll-Out 2
Same Software Update settings and User Experience settings
Evaluation Schedule
Third Monday of every 1 month
Deployment Schedule
Specific Time: 26 Hours
Installation Deadline: 249 Hours (6pm on following Friday)
Roll-Out 3
Same Software Update settings and User Experience settings
Evaluation Schedule
Occurs day 1 of every 1 month
Deployment Schedule
Specific Time: 26 Hours
Installation Deadline: 129 Hours (6 pm 5 days later)
MANAGEMENT QUESTIONS METHODOLOGY AND SUGGEST ALTERNATIVE
My management feels the above approach is not best practice for Patch Management.
They feel that we need a better approach to the testing phase and then an entire company rollout.
It is felt that the testing group should capture each type of machine type we have as well as User Profile (i.e. Marketing, Engineering, etc…)
My issue is getting users that fit machine type usage and User Profile to participate in the testing procedures.
I estimate we have 20 different machine types.
Thus under Management approach
Deploy on to test group and allow to test for 2 weeks
Deploy to entire organizaton
An alternative may be as follows:
ADR to the test group that consists of all machine types and identified user profiles
Deploy on day after Patch Tuesday
Run test period for a period of 8 days to following Friday
ADR to remainder of organization based on no issues in testing
Q: Are you using ADR – Automatic Deployment Rules or are you reviewing the patch list and then selecting them and creating a new Deployment?
Q: What are your organizations doing with SCCM and do they follow are current methodology, proposed methodology or something different.
CONFIGURATION
Our current configuration, as noted, pushes to the patches to the machine and then the user is notified over time to perform the patching or be patched by the mandatory deadline.
It has been asked of me to change this concept to immediately install patches on machine and then allow user to reboot when they want, i.e. no mandatory which causes reboot.
Q: How would this be configured and are their concerns that a user may wait a couple days after machine has patched to reboot and this causes ancillary issues?
The only way I know possibly how to do this is
Leave System Restart if Necessary uncheck
Check Suppress system restart on workstations
My concern is if I remember correctly is by setting mandatory deadlines it overrides these behaviors and installs and reboots the system?

Suggestion #1: Forget about them (management) dictating "who to target". If you want to be truly random, create a collection where the collection rule is... where smsguid like '%0' . See how many targets you get in that collection. Since the guid
is random, selecting a random sample of machines will also be random. The only thing to be aware of is that random MEANS random. So if that means you end up with the CEO's laptop in the pilot, that's exactly what that means. It could happen. But that's the
whole point.
Suggestion #2: It has always bugged me that management wants machine patched... but don't force people to reboot. It can easily happen (quite often) where that means a box is online and not rebooted for months. For pilot #1, #2, and production--set
the deadline for whatever means "likely to be online... but least likely to impact the end user", and enforce the reboot at deadline. Set your Client Agent Setting for countdown to a reboot to be reasonable for your environment--if that means
99 minutes, then so be it. give people 99 minutes and a 15 minute (or 60 minute if you want to be really obnoxious) can't-close-this notification that a reboot is about to happen. Forget about the 'allow a user to reboot when they want'.
Instead set it so that people get plenty of time to see that they will be rebooted... and they better save whatever it is they are working on prior to the reboot.
No matter what you set, people will complain about it. The people that want to work up to the last second prior to the reboot will complain about the notification they can't close, and the people that take a 70 minute lunch/coffee/siesta will complain
that the notification is only 60 minutes long and they didn't see it. Your job (management's job) will be to find the happy medium, or at least communication "this is what this means... basically... just save your work and reboot now, this is for
your own good."
Edit: also... remember in CM12 you can set a service window that applies ONLY to patches. So you could set that (for example) the machines that are always online (VDIs and servers) have their Software Update window on the weekends. and
laptops don't have a service window for Software updates... because who knows when they might be online; so you don't want to limit them. etc. etc... whatever makes sense for you computers.
Standardize. Simplify. Automate.

New FIOS Customer

We had our service started on 03-08-2012. For the first week it was okay, but we've started to have problems.
At first I noticed a delay in STB response time with the remote (VZ P265v2), then no STB response at all when buttons were depressed. This is intermittent.
Afew hours ago the Dear Wife was watching, and the STB display clock said 11:14PM EDT when it was 11:19PM.
I have had to reset the STB three times now all with FP6A, dec errors.
I may not be as knowledgeable or eloquent as John CF here: An Open Letter
but in his list, numbers 1, 2, 3, and 8 are dead on, and if I may add to #8 the inability to roll out patches, fixes, and updates without causing glitches or loss of service for the end user.
John CF was with Dish Network since 1997 like we were with DirecTv since 1998, back then it was USB, and Hughes.
I have re-set my Verizon STB the same amount of times in the last 12Days, that I had In fourteen years with DirecTv.
If anyone needs numbers from the ONT, STB or Internet router I will be glad to get them.

This has got to be the most convoluted Forum I have ever had the honor to be associated with!
It will report posting errors, but doesn't explain them or am I supposed to be a genius?
I am too frustrated to go on, so I'm siging-off!

Roll Up patch

Similar Messages

Maybe you are looking for