Roll back segment usage

Hi, i have a script which will report usage of roll back segments in my db, it gives me rb name #, username, and the table/schema.
I want to have a script which i can maybe enter a variable into (say, concurrent program id) and then have a list of the rbs its using and anything else that may be using the same ?
Anyone help?
regards

doh! i meant to after i posted but got sidetracked :-)
col "User" form a10
col "Table Name" form a10
col "Rollback segment name" form a21
select /*+ RULE */
rn.usn "Rollback segment number",
rn.name "Rollback segment name",
sess.schemaname "User",
sess.sid "sess",
o.name "Table Name"
from
v$rollname rn,
v$session sess,
sys.obj$ o,
v$lock lck1,
v$transaction t
where
sess.taddr = t.addr
and lck1.sid = sess.sid
and lck1.id1 = o.obj#
and lck1.type = 'TM'
and t.xidusn = rn.usn

Similar Messages

  • How to remove a roll back segment file in 8.1.7

    Hi,
    How to remove a roll back segment file in 8.1.7 ?
    My RBS tablespace has two datafiles, how can I delete one of them ?
    Thank you.

    You would
    a. Create a new tablespace to hold rollback segments
    b. Create rollback segments in the new tablespace
    c. Bring the new rollback segments online and the old rollback segments offline
    d. Wait for all the old rollback segments to go offline (they'd be in PENDING OFFLINE if there are active transactions)
    d. Drop the old rollback segments
    e. Drop the old rollback tablespace -- after confirming that it has NO active rollback segments and NO OTHER segments at all
    f. Modify your init.ora to specify the new rollback segments in the "rollback_segments=" parameter
    If you want to switch back to the old tablespace name and segment names, you'd do steps a to e and then run them again to recreate the old tablespace name (with 1 datafile, excluding the one you want to drop) and segment names.

  • Managing Undo tablespace & roll back segments

    Hi,
    I have oracle 9.1 version and have created 5g undo tablespace apart from 20m rbs tablespace for 15 rollback segments. But it is seen that whenever i give UNDO_MANAGEMENT=AUTO then rollback segments are created using undo tablespace and not allowing rollback segment in rbs tablespace ONLINE. In the reverse happens whenever I give UNDO_MANAGEMENT=MANUAL , the rollback segments in the rbs tablespace gets focus and roll back segments in the Undo tablespace goes offline. Is there anything that I can do so that both undo tablespace and redo segments in the rbs tablespace gets working together so as to minimize the undo contention. Moreover, any query given takes long time when select query given with || in the subquery.
    Please suggest the tuning need to do?

    brain_heart wrote:
    Hi,
    I have oracle 9.1 version and have created 5g undo tablespace apart from 20m rbs tablespace for 15 rollback segments. But it is seen that whenever i give UNDO_MANAGEMENT=AUTO then rollback segments are created using undo tablespace and not allowing rollback segment in rbs tablespace ONLINE. In the reverse happens whenever I give UNDO_MANAGEMENT=MANUAL , the rollback segments in the rbs tablespace gets focus and roll back segments in the Undo tablespace goes offline. Is there anything that I can do so that both undo tablespace and redo segments in the rbs tablespace gets working together so as to minimize the undo contention.No that's the way it would work, you can either use the automatic undo or the manual one.not both. And its better to stick with the automatic one IMHO. Have a read of this link to understand more about undo.
    http://download.oracle.com/docs/cd/B10501_01/server.920/a96521/undo.htm#8888
    HTH
    Aman....

  • Dump roll back segment too small

    Hii All,
    From last week i am getting this dump in my production system.
    Database error text........: "ORA-01555: snapshot too old: rollback segment
    number 20 with name "PRS_18" too small#"
    Internal call code.........: "[RSQL/FTCH/MKPF ]"
    What should i do to avoid this dump.
    Regards,
    Viren.

    HI Rana,
    When you have "ora-01555: snapshot too old (rollback segment _ too small)", it usually means failure due to the lack of rollback space. The failure indicates read consistency error, as your active transaction overwrites existing, uncommitted transaction, which implies that the system change number SCN in the block is newer than the SCN at the start of the transaction. The read consistency image of new data can therefore not be created. This can happen when large transactions are being written where there is not enough tablespace for the rollback segments to expand or when the rbs has reached its "MAXEXTENTS".
    Solution is to either add new roll back segment or extend the size of the existing ones.To extend the size of existing ones, increase both the values of their MINEXTENTS and OPTIMAL parameters with ALTER ROLLBACK SEGMENT statement or create additional ones.
    Thanks
    Prince Jose

  • Roll back segment

    Thanks for advance.
    I am learing Oracle8 database management. I am wondering if I create 5 roll back seg but only bring one of them online when starting up instance. Are the left four can be brought
    online automaticly when the first seg is full?
    Or it is a must to wake all roll back seg when you start the instance?
    Thanks again.

    You can edit initorcl.ora to increase "transactions" parameter.
    The formula of 'rollback segments goes online on restart' = transactions / transactions_per_rollback_segment
    RDBMS does not remember what rollback segment was online before restart.

  • Roll back segments into READ-ONLY Mode

    To bring an v8 database into READ-ONLY Mode do we need to put the Roll back tablespace RBS also into READ-ONLY Mode?

    You can put database in READ ONLY mode in Oracle 8i
    READ ONLY / READ WRITE Example
    The first statement below opens the database in read-only mode.
    The second statement returns the database to read-write mode and clears the online redo logs:
    ALTER DATABASE OPEN READ ONLY;
    ALTER DATABASE OPEN READ WRITE RESETLOGS;---
    http://download-west.oracle.com/docs/cd/A87860_01/doc/server.817/a85397/stateme3.htm#2048938

  • Roll back segments - Oracle 8i

    Hi :
    i am running my production db on 8i and i am noticing that my roll back tablespace is running out of space. I want to add a datafile to the tablespace. Can i do this while keeping the tablespace online ?
    - BMP

    In Oracle 9i Database and below, you can issue the query
    SELECT USED_UREC
    FROM V$TRANSACTION;
    which returns the number of undo records used by the current transaction, and if executed repeatedly, will show continuously reduced values because the rollback process will release the undo records as it progresses. You can then calculate the rate by taking snapshots for an interval and then extrapolate the result to estimate the finishing time.
    ~ Madrid

  • Short dump - reading from roll back segment

    Hi All,
    I am getting this short dump for few loads.The error is :
    "(FUNCTION)", or declared in the procedure's RAISING clause.                        
    To prevent the exception, note the following:                                       
    Database error text........: "ORA-01555: snapshot too old: rollback segment         
    number 108 with name "PRS_77" too small"                                           
    Did any body got this eror:If so,could you please explain why it's comming and how to fix this permanently?
    Thanks
    Manish                                                        

    The DBA probably needs to increase the size of the Rollback segment and/or tablespace.
    Google the error message for more info. Here's a link to Jonathan Lewis's (well known Oracle author)site.
    http://www.dba-oracle.com/t_ora_01555_snapshot_old.htm
    Added the link to J Lewis site.
    Message was edited by:
            Pizzaman

  • Set transaction use roll back segmet

    Hi all:
    I have lot of packages with the statement set transaction use roll back segment RBS_BIG.I am working on upgrade project and using undo tablespaces.
    Is there a quick way to grep the this statement from all the packages and remove off.Does the presence of this statement in packages of new database cause compilation errors ?
    Thanks,
    Ganesh

    Hi,
    Set init.ora parameter as follows and restart database. All SET TRANSACTION USE ROLLBACK SEGMENT statements will have no effect and ignored.
    UNDO_SUPPRESS_ERRORS=TRUE
    You may use ALTER SYSTEM rather than restart db. If your database use spfile.ora, you have to execute:
    ALTER SYSTEM SET UNDO_SUPPRESS_ERRORS=TRUE SCOPE=BOTH;
    Best regards,
    Dima

  • Set transaction use roll back

    Hi all:
    I have lot of packages with the statement set transaction use roll back segment RBS_BIG.I am working on upgrade project and using undo tablespaces.
    Is there a quick way to grep the this statement from all the packages and remove off.Does the presence of this statement in packages of new database cause compilation errors ?
    Thanks,
    Ganesh

    The set transaction use rollback segment <rbsegment> is ignored in 10g. In 9i databases this could cause errors when using automatic undo management. For your 9i databases you can suppress the errors by setting UNDO_SUPPRESS_ERRORS=true.

  • Difference between roll back and undo segment.

    Hi ,
    Oracle 10.2.0.1.0
    whats the difference between roll back and undo segemnt ? are they one and same as per changing version of oracle ? please help

    Hi,
    Both will do the same functionality,but in oracle 9i they made it simplify ,because if u are using rollback segments ,u need to put them online in init.ora and u need to take care space management etc.
    so in oracle 9i they introduced undo tablespaces on that u can creage undo segments and space management will be take care by oracle managed files ,so its reduces the burden of dba
    Regards,
    Simma....

  • Toplink 9.0.4.8 and JTS on OAS 10.1.2.0.0 and 10.1.2.0.2 not rolling back

    Re-Posting message with more information.
    Toplink 9.0.4.8 and JTS not rolling back transaction
    Hi
    Scenario:
    I have a session bean (EJB1) calling a session bean (EJB2).
    When an EJB1 is called, EJB1 persists data on to Table1 in database.
    And EJB1 makes multiple calls to EJB2 to create entries in three different tables. Trans-attribute is set as required on both EJBS.
    Problem:
    EJB1 gets a Runtime Exception while inserting the data into TABLE1 (ORA-12899: value too large for column), EJB1 transaction is rollback, but all other transactions related to EJB2 are getting committed. I assume that they should roll back too.
    Also, I did JAD on external transaction controller and listener and noticed that there is a transaction associated to each call. Meaning EJB1 had Transaction T1 and EJB2 had T2, T3, and T4 for the subsequent calls. When EJB1 is getting runtime exception in the method beforeCompletion(), the it calls rollbackGlobalTransaction() which is calling T1.setRollbackonly(). But not on on T2, T3, and T4 rollback
    Am I missing anything?
    Please help me
    Here are my configuration details:
    The datasource configuration:
    <data-source name="myTxDataSource"
    class="com.evermind.sql.OrionCMTDataSource"
    location="jdbc/myTxDataSourceCoreDS"
    xa-location="jdbc/xa/myTxDataSourceXADS"
    ejb-location="jdbc/myTxDataSourceDS"
    pooled-location="jdbc/myTxDataSourcePooledDS"
    connection-driver="oracle.jdbc.driver.OracleDriver"
    username="duser"
    password="d123"
    url="jdbc:oracle:thin:@localhost:1521:ORCL"
    inactivity-timeout="30"
    />
    Sessions.xml
    <login>
    <driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
    <connection-url>jdbc:oracle:thin:@localhost:1521:orcl</connection-url>
    <datasource>jdbc/DimpleTxDataSourceCoreDS</datasource>
    <user-name>duser</user-name>
    <encryption-class-name>oracle.toplink.internal.security.JCEEncryptor</encryption-class-name>
    <encrypted-password>22F7AFE6F6B9672435537CE1189E123DD62D1A19DF561D1E</encrypted-password>
    <uses-native-sequencing>true</uses-native-sequencing>
    <uses-external-connection-pool>true</uses-external-connection-pool>
    <uses-external-transaction-controller>true</uses-external-transaction-controller>
    </login>
    <external-transaction-controller-class>oracle.toplink.jts.oracle9i.Oracle9iJTSExternalTransactionController</external-transaction-controller-class>
    Toplink Helper class that is used by both EJB's
    This one uses SessionBroker. here is how it is initialized:
    SessionManager manager = SessionManager.getManager();
    sessionBroker = (SessionBroker) manager.getSession(xmlLoader,
    sessionBrokerName, this.getClass().getClassLoader());
    Oracle9iJTSExternalTransactionController extController = new Oracle9iJTSExternalTransactionController();
    sessionBroker.setExternalTransactionController(extController);
    It has common following commong methods:
    public UnitOfWork getUnitOfWork() {
    UnitOfWork uow = sessionBroker.getActiveUnitOfWork();
    return uow;
    public Object create(Object o)
    UnitOfWork uow = getUnitOfWork();
    uow.registerNewObject(o);
    // added so that the assigned sequence number will be available before the commit happens
    uow.assignSequenceNumber(o);
    return o;
    }

    A couple of this appear different in your sessions.xml. To do what you want you need to configure TopLink to:
    1. Use an external XT controller - requires flag to be set and controller provided
    2. Use the OC4J data source - requires flag to be set and data source name provided
    I notice that your sessions.xml has both a data source name as well as a direct connection URL.
    Here is a sample that shows the proper settings for the external TX and data source usage:
    <?xml version = '1.0' encoding = 'UTF-8'?>
    <!DOCTYPE toplink-configuration PUBLIC "-//Oracle Corp.//DTD TopLink Sessions 9.0.4//EN" "sessions_9_0_4.dtd">
    <toplink-configuration>
       <session>
          <name>default</name>
          <project-xml>META-INF/tlMap1.xml</project-xml>
          <session-type>
             <server-session/>
          </session-type>
          <login>
             <datasource>jdbc/DimpleTxDataSourceCoreDS</datasource>
             <platform-class>oracle.toplink.platform.database.oracle.Oracle10Platform</platform-class>
             <uses-external-connection-pool>true</uses-external-connection-pool>
             <uses-external-transaction-controller>true</uses-external-transaction-controller>
          </login>
          <external-transaction-controller-class>oracle.toplink.jts.oracle9i.Oracle9iJTSExternalTransactionController</external-transaction-controller-class>
          <enable-logging>true</enable-logging>
          <logging-options>
             <print-thread>false</print-thread>
             <print-date>false</print-date>
          </logging-options>
       </session>
    </toplink-configuration>Doug

  • Oracle 10g Paremeter to Auto Roll Back uncommited transanctions

    Hi all
    In SME Segment - People donot affort having Oracle Dba and at the same time less experienced persons keep making their own tests
    Situation goes as under :-
    a) Oracle 10g Windows 2003 64 Bit version on Branded HP Server with 8GB Ram having around 100 simultaneous users
    b) User A on Machine A fires command say
    Table Iledg has inventory data say around 2 Million records
    Update iledg set gwt = netwt + corewt where vrdate >= ??? and vrdate <= ??
    Records get updates - But user A does either of the following
    i) Does not give commit
    ii) Preses Ctl + Alt + Del
    iii) Switches off the Computer
    Problem
    All other users get hanged for their Transanctions relating to table Iledg. EDP person is not able identify the culprit i.e User A
    We have already tried - that if we kill the session of User A , position becomes OK
    Solution wanted for
    a) Set some Oracle Parameter which automatically rolls back un committed transnactions for say 5 Minutes
    b) Oracle automatically kills those sessions who have un commited transanctions for more than say 5 minutes.
    Because in SME Segment - It is very difficult to ask the users to fire some very technical commands to find out the culprit and to kill their sessions. At the same time we can not start the server again and again.
    Suresh Bansal

    Thanks for the reply.
    We were also very sure about Oracle 10g beharviour but it actually does not happen in abnormal disconnections.
    We tested this way
    a) Table Iledg has inventory data say around 2 Million records
    Machine A fires command say
    Update iledg set gwt = netwt + corewt where vrdate >= ??? and vrdate <= ??
    Oracle Results -> ?? rows updated ->Did not gave commit command ->Intentionally to test it switched off the machine without Exiting from
    SQL*Plus
    then on Machine B)
    Again tried to
    Update iledg set gwt = netwt + corewt where vrdate >= ??? and vrdate <= ??
    Session of Machine A is not killed by Oracle 10g and is blocking the Transanction of Machine B which is very unfortunate as we thought Oracle 10g must have killed the session of Machine A when he switched off his Machine. When blocking_session of Machine A is killed ->Position becomes absolutely OK and normal.
    This can be tested in just 2 minutes at your end.
    Kindly suggest some workable remedy to overcome such abnormal client disconnections. Setting Profile idle time is not the workable solution as we create Oracle Connection at the start of VB6 application and that connection goes on thru out applications for all reports and transanctions.
    This kind of problem is not faced in last 6 years over the same forms. But now the client network has grown to say 700 Computers and is creating problems intermittently which is diagnosed properly and terminates the Oracle Connections which sometimes creates these kinds of problems.
    Suresh Bansal

  • 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

  • Transaction - the subprocess rolling back parent JTA

    According to Oracle documentation,
    "if the caller partner link specifies transaction=participate and the subprocess also specifies transaction=participate, the subprocess rolls back the client JTA transaction."
    But what I experience is if I just set transaction=participate for the partner link alone (and not having transaction=participate in the subprocess), when the subprocess rolls back, it rolls back parent JTA transaction also.
    In fact, if we have just transaction=participate for the partner link (and not having transaction=participate in the subprocess), then the rollback in either Parent or Subprocess, is rolling back both Parent and Subprocess.
    Can somebody provide the exact usage of using transaction=participate at the subprocess level?
    Thanks,
    Joe

    Joe,
    You are seeing expected behaviour. Even though both flags are called "transaction" and both are set to "participate", they do different things.
    By specifying transaction=participate on the partner link, you are instructing the subprocess to enlist in the transaction. When the subprocess starts, it will then enlist itself. That's all. Now if a rollback occurs, all participating processes will be rolled back.
    If you specify transaction=participate at the process level, it has a different effect, and doesn't affect whether or not the transaction is rolled back or not. As I said in the previous paragraph, if the partner link specified transaction=participate, the subprocess will roll back if a rollback is issued, no matter what other settings you have.
    So what effect does that setting have at the process level? According to the doc:
    When transaction=participate, the process produces a fault that is not handled by fault handlers, which calls the transaction to be rolled back.
    This is not exactly crystal clear, to me, anyway. In practice if this is set and your subprocess throws an unhandled fault, it triggers a rollback instead of throwing a fault as it normally would. This exception goes immediately back to the calling process since it is participating on the transaction as well.
    If the property is not set, and the subprocess throws an unhandled fault, you get the normal behavior. Namely, the process will be flagged as faulted, and the calling process will wait until it gets a transaction timeout (no relation to the JTA transaction we're talking about here).
    It's a simple test. Create two processes, then run it twice. Once with that property set, and one without.
    The key is to remember that although they are both called "transaction=participate", the effect they have is very different. It was probably not a good move to use the same name and value like that. Hope this helps.
    Regards,
    Robin.

Maybe you are looking for

  • Add event in iCal from Mail

    I know there is a way to do this I just dont know how. Also, I need it to be only certain emails from a couple of senders, not every email they send with a date. Is there any way this can be done? I appreciate the help

  • Low Disk Space in the installation drive

    Dear all, One of our test server, is running out of space in the installation drive. Do we have any standard jobs/Tcodes to reduce/shrink the disk space of installation drive. Please share your inputs, Regards, Younus

  • How to run scripts in Numbers?

    In Yvan Koenig's script, the instructions say "Save the script as a Script: numberInLetters.scpt Move the newly created application into the folder: <startup Volume>:Users:<yourAccount>:Library:Scripts:Applications:Numbers: Maybe you would have to cr

  • In defence of the Apple Store Employees

    They are not informed on new products comming out until the day they are released. So if you bought your Ipod recently without them informing you about the new 80G, they didn't know any more about it than you did. I was in an apple store last week he

  • Antivirus crash after firmware update

    I installed the latest firmware update on my Yoga 10 last night and now my Avira antivirus has crashed.  I keep getting messages in the top bar about the crash.  I managed to delete Avira and reinstall it, but this has not fixed the problem.  I don't