Publication state rolls back

We have a problem with publications. On several occations a publication has been set back to a former state.
-The weight of publication items change to some prior settings
-SQL definition of publication items change to some prior SQL def.
We have not been able to sort of how or when the "rollback" appears, but it seems to be related to logging (RDP) into the Windows 2003 server with different users.
Mobile Server 10.3.0.2.0, runs on Windows 2003 server using the /console RDP user slot. We never log off this session, we close the window with Mobile Server running.
Administration through Mobile Manager is done by "standard" RDP user slot, and logging off the RDP session each time we "leave".
The state which the publication is rolled back to, is not the last state saved, but to some point several test iterations ago (weeks ago). It seems that is is allways rolling back to the same state, though.
Have anybody a clue what might cause this behaviour?
Marius

Gary, thanks for your help so far.
It is just weights and sql statements that are rolled back.
We might have found the problem. It seems that Mobile Workbench does not saves changes back to the xml publish file we use to open the project with, but to some other project file in another directory. It is probably the original location of the project file it saves to.
But how does this work? Are the settings saved to the database or do they just exist in the XML file and memory? When is the file picked up other than when opening Mobile Workbench? (the "rollback" happens while Mobile server is up and running)
Thanks,
Marius
Edited by: user10629674 on Nov 21, 2008 1:45 AM

Similar Messages

  • Statement in Transaction Does Not Roll Back

    I have a group of MySQL statements in a method of a Java application.
    I include an SQL error in the last statement to test the rollback of the transaction.
    All the statements roll back, EXCEPT for the one detailed below.
    The MySQL table:
         CREATE TABLE Counter (
              number INT( 4 ) NOT NULL DEFAULT 0,
              account_id VARCHAR( 12 ) NOT NULL PRIMARY KEY
         ) ENGINE = InnoDB;I have run the staement as a PreparedStatement and a Statement:
    PreparedStatement:
         String updateCounterStr =
              " UPDATE Counter " +
                   " SET number = number + 1 " +
                   " WHERE account_id = ? "
         updateCounter = con.prepareStatement ( updateCounterStr );
              updateCounter.setString( 1, accountID );
              int uc = updateCounter.executeUpdate();     Statement:               
         Statement updateCounterStatement = con.createStatement();
              int updatecounter = updateCounterStatement.executeUpdate(
                   "UPDATE Counter SET number = number + 1 " +
                   "WHERE account_id = \'" + accountID + "\'"
              con.setAutoCommit( true );     //     ------------------------------------ Transaction ENDS
              updateCounterStatement.close();
    //               updateCounter.close();
              ... several more
              con.close();
         } catch(SQLException ex) {
              System.err.println("SQLException: " + ex.getMessage());
              if (con != null) {
                   try {
                        System.err.print("Transaction is being ");
                        System.err.println("rolled back");
                        con.rollback();     //     < ------------------------------------ con.rollback() HERE
                   } catch(SQLException excep) {
                        System.err.print("SQLException: ");
                        System.err.println(excep.getMessage());
    }     //     ---------------------------------------- END the methodIn both cases Counter is incremented, but does NOT roll back.
    The other statements in the transaction do roll back,
    I am using:
    mysql Ver 14.12 Distrib 5.0.18, for apple-darwin8.2.0 (powerpc) using readline 5.0
    on Mac OS X 10.4.x
    I would greatly appreciate a solution to this problem.
    Many thanks in advance

    I think autocommit is true by default. Also, it looks like your'e setting it to true, and then executing more SQL.
    Explicitly set it to false, and DON'T set it back to trueif there's any chance you're going to want to rollback after that.

  • Info abt rolled back sql statements

    hi friends,
    Is there any way to check / get the rolled back sql statements in oracle for a specific time frame.
    eg: say at 10AM i have issued an insert statement and i have rolled it back. Now at 11AM if i want the list of rolled back statements, is there any way to check it ?
    What to do if tracing is also not enabled ?
    Thanks
    Ramya

    try logminer.

  • Time Machine reported 'volume is read only' & rolled back to old state

    I've been in love with Time Machine ever since Leopard arrived. This has all come crashing down over the last few days...
    Firstly I got a new 1tb drive, so I mirrored my old TM drive (using SuperDuper), and all seemed to be fine – backups were chugging along for a week or so as normal on the new, bigger drive.
    A few days ago I got a time machine error stating that "The backup volume is read only". I thought this was strange as the drive was working without issue for a week. I checked permissions, format, etc and all were set correctly. I restarted and Time Machine kicked back in and all seemed to work fine other the fact that there seemed to be no backups created for 6 hours before I got the error message. Then I made a scary realisation, somehow the files on my computer had been restored to a state from 6 hours prior, all the work I'd done for the morning was gone.
    I put this down to a one off glitch (stupid, stupid, stupid). I've today got the same "backup volume is read only" message again, and this time around my files have been restored to a state from 3 days ago. Fortunately this time around Time Machine has a backup of the important stuff a few hours ago.
    I am now very worried about using the same disk with Time Machine. I also have no idea if Time Machine is the culprit (but logic tells me with the rolling back of files it must be). What should I do? How can I figure out what is going on?

    This may fix the "read only" problem:
    What to do if Time Machine reports you don't have permission
    This was posted in the Apple Discussions by V.K. I have only modified it slightly to be more generic.
    The problem seems to be that 10.5.6 changes permissions on a file so that even the root user doesn't have write peivileges. I have no idea why they did this. The workaround suggested in [an]other post will probably work, too, but i did something less drastic. Instead of deleting the file I changed permissions on it, and it worked just fine. An added benefit is that the permission change seems to stick, so you don't have to delete the file every time you change a drive.
    [Open the Terminal application in your Utilities folder. At the prompt [enter] the following command:
    sudo chmod 644 /volumes/"TM drive name"/.xxxxxxxxxxxx
    The name of the file .xxxxxxxxxxxx is based on the MAC address of your computer and will be different for every computer. Put the name of the TM drive in the above and keep the quotes.
    You'll have to enter your admin password (which you won't see) which is normal.
    This was edited by Kappy just for cleanup.
    Enable Finder to Show Invisible Files and Folders
    Open the Terminal application in your Utilities folder. At the prompt enter or paste the following command line then press RETURN.
    defaults write com.apple.finder AppleShowAllFiles TRUE
    To turn off the display of invisible files and folders enter or paste the following command line and press RETURN.
    defaults write com.apple.finder AppleShowAllFiles FALSE
    Alternatively you can use one of the numerous third-party utilities such as TinkerTool or ShowHideInvisibleFiles - VersionTracker or MacUpdate.

  • MDB transaction getting silently rolled back?

              I have an MDB that is doing a delete of a database record in the onMessage method.
              It seems to work fine. I see no errors in the log, in fact I have some debug
              statements that indicate everything was completed normally. I even do a count
              sql using the same where clause and print the results and see a '0'.
              However, when I check the database, the record is still there.
              It seems as if the transaction is getting rolled back somehow. The MDB is transaction
              required/container tx. I never setRollbackOnly anywhere.
              The topic was originally published in a transaction that was rolled back, if that
              makes any difference. In fact, the point of the MDB is to clean up a record that
              was created during the transaction but not within the transaction.
              Any help is appreciated!
              ken
              

              It turned out that the MDB was using a different connection pool than it should
              have, which was pointed to an old copy of the database. So it wasn't really rolling
              back, it really was deleting records as desired, just in the wrong database.
              Thanks
              ken
              Tom Barnes <[email protected].bea.com>
              wrote:
              >Some random ideas:
              >
              >Is the app sending a delete request to the MDB, and
              >the MDB acting on it, before the record is even inserted?
              >
              >Does the delete request have the correct row-id/PK?
              >
              >Is the MDB app failing without your knowledge? You
              >can instrument the MDB onMessage() with a
              >"try catch Throwable" to see.
              >
              >Is the MDB tx timing out trying to get a lock
              >on the row? You can instrument the onMessage
              >with timestamps to see if its taking longer than 30 seconds...
              >
              >Tom
              >
              >Ken Clark wrote:
              >
              >> I have an MDB that is doing a delete of a database record in the onMessage
              >method.
              >> It seems to work fine. I see no errors in the log, in fact I have
              >some debug
              >> statements that indicate everything was completed normally. I even
              >do a count
              >> sql using the same where clause and print the results and see a '0'.
              >>
              >> However, when I check the database, the record is still there.
              >>
              >> It seems as if the transaction is getting rolled back somehow. The
              >MDB is transaction
              >> required/container tx. I never setRollbackOnly anywhere.
              >>
              >> The topic was originally published in a transaction that was rolled
              >back, if that
              >> makes any difference. In fact, the point of the MDB is to clean up
              >a record that
              >> was created during the transaction but not within the transaction.
              >>
              >> Any help is appreciated!
              >>
              >> ken
              >
              

  • Transaction is not Rolling Back in Stateless Session Bean

              Hi,
              I am using UserTransaction in Stateless Session bean .
              Transaction is not rolling back.
              The following code is writen in stateless session bean. In UserTransaction i am
              calling Two methods of another stateless session bean.
              The problem is if doJob2() method fails, doJob1() method is rolling back. These
              two methods consist of SQL statement with different Connection Object from TXDataSource.And
              session bean(TestSession) is set to CMT, attribute as "Required".
              try{
              Context ictx=new InitialContext();
              TestHome home=(TestHome)ictx.lookup("TestSession");
                   utx = sessionCtx.getUserTransaction();
                   utx.begin();
              TestRemote remote=home.create();
                   remote.doJob1();
                   remote.doJob2();
                   utx.commit();
              }catch(Exception e)
                   try{
                   utx.rollback();
              }catch(Exception ex)
                   System.out.println("unable to rollback"+ex);
              if any SQL Exception as occured in doJob2(), its calling method utx.rollback()
              in catch block. but SQL statements executed thru. doJob1() are not rolling back.
              what might be the reason?
              thanks
              Ranganath
              

              Thanx Priscilla ,
              Transaction is working.
              ranganath
              "Priscilla Fung" <[email protected]> wrote:
              >
              >In your ejb-jar.xml, you should specify <transaction-type> element to
              >be "Container"
              >for container-managed transaction. If you specified it to be "Bean" for
              >bean-managed
              >transaction, EJB ontainer will suspend the caller's transaction before
              >starting
              >a new transaction for your doJobX() methods. Thus, doJob1()nd doJob2()
              >will be
              >executing in different transactions, and thus rolling back doJob2()'s
              >transaction
              >will have no effect on work done and committed in doJob1()'s transaction.
              >
              >Regards,
              >
              >Priscilla
              >
              >
              >"Ranganath" <[email protected]> wrote:
              >>
              >>
              >>
              >>I am sending config.xml,deployment descriptors, code snippet for TestSession.
              >>i
              >>am using weblogic6.0sp2.
              >>if you need any aditional info. please let me know.
              >>
              >>thanks
              >>ranganath
              >>
              >>EJB-JAR.xml
              >>
              >><?xml version="1.0"?>
              >>
              >><!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise
              >JavaBeans
              >>1.1//EN' 'http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd'>
              >>
              >><ejb-jar>
              >>     <enterprise-beans>
              >>     <session>
              >>          <ejb-name>TestSession</ejb-name>
              >>          <home>com.apar.sslbridge.test.TestHome</home>
              >>          <remote>com.apar.sslbridge.test.TestRemote</remote>
              >>          <ejb-class>com.apar.sslbridge.test.TestBean</ejb-class>
              >>          <session-type>Stateless</session-type>
              >>          <transaction-type>Bean</transaction-type>
              >>          <resource-ref>
              >>     <res-ref-name>jdbc/oraclePool</res-ref-name>
              >>     <res-type>javax.sql.DataSource</res-type>
              >>     <res-auth>Container</res-auth>
              >>          </resource-ref>
              >>     </session>
              >>     </enterprise-beans>
              >>     <assembly-descriptor>
              >>     <container-transaction>
              >>          <method>
              >>          <ejb-name>TestSession</ejb-name>
              >>          <method-intf>Remote</method-intf>
              >>          <method-name>*</method-name>
              >>          </method>
              >>          <trans-attribute>Required</trans-attribute>
              >>     </container-transaction>
              >> </assembly-descriptor>
              >></ejb-jar>
              >>
              >>
              >>TestSession CODE:
              >>
              >>
              >>     public void doJob1() throws RemoteException
              >>     {
              >>     Statement st = null;
              >>     String query=null;
              >>     try{
              >>     con=getConnection();
              >>     st=con.createStatement();
              >>     query="insert into x values("+x+++")";
              >>     System.out.println(query);
              >>     int rec=st.executeUpdate(query);
              >>     }catch(SQLException sqle)
              >>     {
              >>     System.out.println("SQL Exception "+sqle);
              >> throw new RemoteException("RemoteException*****SQLError");
              >>     } catch (Exception e) {
              >>     System.out.println("Exception "+e);
              >> throw new RemoteException("RemoteException*****GenralError");
              >> }
              >>}
              >>
              >>
              >> public void doJob2()throws RemoteException
              >> {
              >> Connection con=null;
              >> Statement st = null;
              >> String query=null;
              >> try{
              >> con=getConnection();
              >> st=con.createStatement();
              >> query="insert into y values("+x+++")";
              >> System.out.println(query);
              >> int rec=st.executeUpdate(query);
              >> }catch(SQLException sqle)
              >> {
              >> System.out.println("SQL Exception "+sqle);
              >> throw new RemoteException("RemoteException*****SQLError");
              >> } catch (Exception e) {
              >> System.out.println("Exception "+e);
              >> throw new RemoteException("RemoteException*****GenralError");
              >>}
              >>}
              >>private Connection getConnection(){
              >>try {
              >>Connection con = StaticParams.POOL_DATASOURCE.getConnection();
              >>return con;
              >>     } catch(Exception e) {
              >>     System.out.println("TestBean.getConnection() Unable to get get pool
              >>connection
              >>" + e);
              >>     }
              >>}
              >>
              >>
              >>
              >>
              >>"Priscilla Fung" <[email protected]> wrote:
              >>>
              >>>It should work if you are using TxDataSource. Could you post your
              >config.xml,
              >>>deployment descriptors, code snippet for TestSession?
              >>>
              >>>Regards,
              >>>
              >>>Priscilla
              >>>
              >>>"Ranganath" <[email protected]> wrote:
              >>>>
              >>>>Hi,
              >>>>
              >>>> I am using UserTransaction in Stateless Session bean .
              >>>> Transaction is not rolling back.
              >>>>
              >>>>The following code is writen in stateless session bean. In UserTransaction
              >>>>i am
              >>>>calling Two methods of another stateless session bean.
              >>>> The problem is if doJob2() method fails, doJob1() method is rolling
              >>>> back. These
              >>>>two methods consist of SQL statement with different Connection Object
              >>>>from TXDataSource.And
              >>>>session bean(TestSession) is set to CMT, attribute as "Required".
              >>>>
              >>>> try{
              >>>> Context ictx=new InitialContext();
              >>>> TestHome home=(TestHome)ictx.lookup("TestSession");
              >>>>     utx = sessionCtx.getUserTransaction();
              >>>>     utx.begin();
              >>>> TestRemote remote=home.create();
              >>>>     remote.doJob1();
              >>>>     remote.doJob2();
              >>>>     utx.commit();
              >>>> }catch(Exception e)
              >>>> {
              >>>>     try{
              >>>>      utx.rollback();
              >>>> }catch(Exception ex)
              >>>> {
              >>>>     System.out.println("unable to rollback"+ex);
              >>>>     }
              >>>> }
              >>>>if any SQL Exception as occured in doJob2(), its calling method utx.rollback()
              >>>>in catch block. but SQL statements executed thru. doJob1() are not
              >>rolling
              >>>>back.
              >>>>what might be the reason?
              >>>>
              >>>>thanks
              >>>>Ranganath
              >>>
              >>
              >
              

  • Photoshop Elements/Premiere 9 OEM Bundle not installing. Rolls back at end

    I have a toshiba satellite T135 with AMD Turion Neo X2 Dual Core processor L625, 4 GB RAM, ATI Radeon HD 3200 graphics operating on Windows 7 64 bit Home Premium edition.
    I am trying to install adobe photoshop elements 9 and adobe premiere elements 9.  It gets to the end where it is almost done.  Icon on desktop, and then it decides to rollback the installation.  I tried many of the suggestions on this forum: copied disc info to folder on c drive.  Started with a clean boot.  That actually made it worse because it also caused the computer to blue screen.
    Here are come windows errors that pop up at the end:
    prior to clean boot installation:
    Files that help describe the problem:
      C:\Users\Sara\AppData\Local\Temp\WERDE2B.tmp.WERInternalMetadata.xml
      C:\Users\Sara\AppData\Local\Temp\WERF841.tmp.appcompat.txt
      C:\Users\Sara\AppData\Local\Temp\WERFB5D.tmp.WERDataCollectionFailure.txt
    Read our privacy statement online:
      http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
    If the online privacy statement is not available, please read our privacy statement offline:
      C:\windows\system32\en-US\erofflps.txt
    Post clean boot installation:
    Problem signature:
      Problem Event Name:                        BlueScreen
      OS Version:                                          6.1.7600.2.0.0.768.3
      Locale ID:                                             1033
    Additional information about the problem:
      BCCode:                                               1000007e
      BCP1:                                                    FFFFFFFFC0000005
      BCP2:                                                    FFFFF80002CD3670
      BCP3:                                                    FFFFF88002FD37F8
      BCP4:                                                    FFFFF88002FD3060
      OS Version:                                          6_1_7600
      Service Pack:                                       0_0
      Product:                                               768_1
    Files that help describe the problem:
      C:\Windows\Minidump\031611-44912-01.dmp
      C:\Users\Sara\AppData\Local\Temp\WER-103569-0.sysdata.xml
    Read our privacy statement online:
      http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
    If the online privacy statement is not available, please read our privacy statement offline:
      C:\windows\system32\en-US\erofflps.txt
    Please help me get this software installed.  Frustrating that a legit well known piece of software has so many problems just getting installed.

    I am trying to install a new purchased version of PSE 9 and havin the same issues.  It simply rolls back when near the end of the installation process.   I am on hold with phone support now, but from the sounds of things here on this forum, Adobe is aware of the issue but has no suggestions to fix it.
    This is the first time in my life that I have had issues with installing a new, purchased piece of software.
    C'mon Adobe Support, time to answer us on this and get it solved, or perhaps you would offer us refunds?

  • Remote or transactional roll back exception occurred

    Hi,
    I am getting this message, anybody could help me?
    SEVERE ( 1166): EJB5071: Some remote or transactional roll back exception occurred
    com.sun.jdo.api.persistence.support.JDOFatalInternalException: Got an unknown exception.
    NestedException: java.lang.IndexOutOfBoundsException: Index: 1, Size: 1
    at com.sun.jdo.spi.persistence.support.sqlstore.SQLStateManager.updatePersistent(SQLStateManager.java:1012)
    at com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerImpl.beforeCompletion(PersistenceManagerImpl.java:1251)
    at com.sun.jdo.spi.persistence.support.sqlstore.impl.TransactionImpl.notifyBeforeCompletion(TransactionImpl.java:1115)
    at com.sun.jdo.spi.persistence.support.sqlstore.impl.TransactionImpl.commitBefore(TransactionImpl.java:743)
    at com.sun.jdo.spi.persistence.support.sqlstore.impl.TransactionImpl.beforeCompletion(TransactionImpl.java:646)
    at com.sun.ejb.containers.ContainerSynchronization.beforeCompletion(ContainerSynchronization.java:105)
    at com.sun.enterprise.distributedtx.J2EETransaction.commit(J2EETransaction.java:183)
    at com.sun.enterprise.distributedtx.J2EETransactionManagerOpt.commit(J2EETransactionManagerOpt.java:310)
    at com.sun.ejb.containers.BaseContainer.completeNewTx(BaseContainer.java:1786)
    at com.sun.ejb.containers.BaseContainer.postInvokeTx(BaseContainer.java:1585)
    at com.sun.ejb.containers.BaseContainer.postInvoke(BaseContainer.java:510)
    at br.com.inttegra.infra.businesslayer.ejb.ControllerBean_EJBObjectImpl.insert(ControllerBean_EJBObjectImpl.java:136)
    at br.com.inttegra.infra.businesslayer.ejb._ControllerBean_EJBObjectImpl_Tie._invoke(Unknown Source)
    at com.sun.corba.ee.internal.POA.GenericPOAServerSC.dispatchToServant(GenericPOAServerSC.java:569)
    at com.sun.corba.ee.internal.POA.GenericPOAServerSC.internalDispatch(GenericPOAServerSC.java:211)
    at com.sun.corba.ee.internal.POA.GenericPOAServerSC.dispatch(GenericPOAServerSC.java:113)
    at com.sun.corba.ee.internal.iiop.ORB.process(ORB.java:275)
    at com.sun.corba.ee.internal.iiop.RequestProcessor.process(RequestProcessor.java:83)
    at com.iplanet.ias.corba.ee.internal.iiop.ServicableWrapper.service(ServicableWrapper.java:25)
    at com.iplanet.ias.util.threadpool.FastThreadPool$ThreadPoolThread.run(FastThreadPool.java:283)
    at java.lang.Thread.run(Thread.java:536)

    Hi,
    Please make shure, that your sun-cmp-mappings.xml is correct. The exception in your message just indicates a problem executing a sql statement. Please look into your log file again if you could find another exception trace showing where the IndexOutOfBoundsException happens.
    Thanks,
    -- markus.

  • BDC-Roll back

    Can we rollback the changes in database by BDC call transaction (sychronous) method (using rollback statement)?
    Misha

    Hi Misha,
    it is not possible in bdc but you can have one more option in indirectly
    keep one check box in selection-screen,like test mode
    when you click test mode then do not use save ok_code ( It works like Roll back )
    if you use call transaction ,then if you use update mode is Synchronous ,it works like committ work.
    Regards
    Kiran Sure

  • Regarding roll back and reassign the value.

    hi all,
    i am using forms6i.
    Re: how to avoid the form's message situation
    as we discussed my process has to happen like this. since it is a new topic so i have raised new thread.
    what i want to do is based on the input values(base table values) i have to call one procedure, the procedure returned value i have to assign to one of my database field and one new record should go into other table.
    so what i am doing is at the key-commit trigger i have written a procedure inside that i am calling a procedure which results in one value which i have to assigned to my blocks item. and one record to the table
    my code in key commit trigger is something like
    go_block('block name');
    first_record;
    based on the forms parameter call procedure
    if procedure returns error then rollback otherwise assign value to base table item and one record to other table so
    job_proc();
    :block.item:= output ;
    insert into job_table() values();
    if system.last_record = 'TRUE' then
    exit
    else
    next_record;
    end loop;now senario is like if i am in fifth record four record processed as i explained before. in fifth record if i am getting error means
    all four records value and insert statement should be reassined and rolled back.
    so i have written like
    exception when others then
    forms_ddl('rollback');
    go_block(block name);
    go_record(system.current_record);
    :block.item := null;
    if :system.trigger_record = 1 then
    exit;
    else
    previous_record;
    end if;
    end loop;is this is the way to rollback or is there any better way?
    please advise.
    Thanks..

    Hi,
    Check these files on rollback and commit:
    Transactional Behavior of an Integration Process:
    http://help.sap.com/saphelp_nw04s/helpdata/en/45/058023846b2460e10000000a1553f7/frameset.htm
    Commit Handling:
    http://help.sap.com/saphelp_nw04s/helpdata/en/fa/814d3ccd6fba74e10000000a114084/frameset.htm
    Rollback:
    http://help.sap.com/saphelp_nw70/helpdata/en/23/5f5fd653b6f64d9bb0b468a8689838/frameset.htm
    Regards,
    Subhasha

  • Roll back process after certain time limit

    Hi All,
      I am using Oracle 11g. I am calling one stored procedure (MainProc) from my application. Through this procedure I am calling internally three more procedure (Insert recordProc1, InsertRecordProc2 and DeleteRecProc).
    The third stored procedure (DeleteRecProc) is taking more than 5 minutes. But if these process crossings more than 5 minutes, have to stop the process and roll back all three stored procedures functions.
    I don’t have any commit statement inside of these stored procedures. But I have EXECUTE IMMEDIATE Inside of stored DeleteRecProc.
    Help required: Help me to make a counter / Timer. I have a parameter, which has the assigned time limit. How to check whether the process crossing the time limit? How to stop the process and call Rollback?
    Thanks in advance.
    Manian

    Don't know if this helps your situation.
    http://docs.info.apple.com/article.html?artnum=301579
    here is the entire thread
    http://discussions.apple.com/message.jspa?messageID=1237801#1237801

  • Rolling back to iTunes 4.9 from 5 or 5.0.1

    I have posted a method of rolling back to iTunes 4.9 from iTunes 5 or 5.0.1 before and it works for some people, at least. I am posting this again in the hope that people who have problems with iTunes 5 or 5.0.1 will be able to solve their problems by rolling back.
    (1) Remove iTunes 5 and QuickTime 7 using the Add/Remove Program function in Control Panel
    (2) Copy the iTunes Library file in My Documents -> My Music -> iTunes -> Previous iTunes Libraries to My Documents -> My Music -> iTunes and rename it to iTunes Library (you need to delete the new iTunes Library file there created by iTunes 5 first)
    (3) Reinstall iTunes 4.9 (A copy can be found at http://www.5star-shareware.com/Windows/Music/MultimediaPlayers/itunes.html , the last time I visited the link is still active.)
    Also save the iTunes 4.9 installer in a safe place as you may need it later.

    Jim,
    Your statements indicate a clear understanding of why the furor appears here and the efforts to address it, but your last admission (regarding issue management) negates it all. How can
    i you
    now determine that there is a problem (one that is pervasive enough to warrant a major response or action on Apple's part)?
    None of us here have any insight as to the extent (or lack thereof) of the problem. Only Apple knows (if that) how many iTunes installations there are and what proportion of these are experiencing a problem. There have been calls for the iTunes developers' heads since I've seen the release of 4.7 - and all prior indications are that this is not a new event with that version. Some folks have always been getting caught in the ‘fatal error’ trap with each new iTunes release.
    Over the 2005 year, the iTunes users have expanded greatly. As such, I would expect a similar increase in folks coming here to seek help and express dismay. It certainly
    i seems
    to me as if there are greater instances of iTunes failing, but as a proportion of total users, I cannot say if the percentages are, in fact, increasing.
    As for a 'forced migration’,...the apparent policy has been to provide only the current version of the programs. I realize that folks want a 'fool-proof' upgrade, but any experience with PCs teaches one that without backups, archived earlier version of programs, prudence before jumping into a new version release, and a good understanding of one's system, you are just inviting trouble.
    I feel for the folks with difficult problems. I am not blaming them, nor am I willing to blame Apple. I remain here trying to assist them where possible. I do, however, expect us as 'users' to be able to proactively protect ourselves as we so often have been warned by various technology experts: make multiple backups, keep copies of previous programs, learn a little bit about our computers, and exercise a little personal responsibility in keeping them correctly operating - or pay for someone else to manage it for us.

  • Differences between Commit work, Logical Unit of Work and Roll back work

    Hi all,
    Can any one explain me in details what is the difference between Commit Work, Logical Unit of Work and Roll back work. Pls explain by providing some example.
    and also explain me where and when these are used and what are the importance of using these.
    Thanks in advance.
    Regards
    Ramana Prasad.T

    Hi Ramana Prasad,
    A Logical Unit of Work (LUW or database transaction) is an inseparable sequence of database operations which must be executed either in its entirety or not at all. For the database system, it thus constitutes a unit.
    LUWs help to guarantee database integrity. When an LUW has been successfully concluded, the database is once again in a correct state. If, however, an error occurs within an LUW, all database changes made since the beginning of the LUW are canceled and the database is then in the same state as before the LUW started.
    An LUW begins
    o each time you start a transaction
    o when the database changes of the previous LUW have been confirmed (database
    commit) or
    o when the database changes of the previous LUW have been cancelled (database rollback)
    An LUW ends
    o when the database changes have been confirmed (database commit) or
    o when the database changes have been canceled (database rollback)
    COMMIT WORK.
    Executes a database commit and thus closes a logical processing unit or Logical Unit of Work ( LUW ) (see also Transaction processing ). This means that
    all database changes are made irrevocable and cannot be reversed with ROLLBACK WORK and
    all database locks are released.
    COMMIT WORK also
    calls the subroutines specified by PERFORM ... ON COMMIT * executes asynchronously any update requests (see CALL FUNCTION ... IN UPDATE TASK ) specified in these subroutines or started just before,
    processes the function modules specified in CALL FUNCTION ... IN BACKGROUND TASK ,
    cancels all existing locks (see SAP locking concept ) if no update requests exist,
    closes all open database cursors (see OPEN CURSOR ) and
    resets the time slice counter to 0.
    COMMIT WORK belongs to the Open SQL command set.
    Return code value
    The SY-SUBRC is set to 0.
    ROLLBACK WORK.
    Closes a logical processing unit by reversing all database changes made since the last COMMIT .
    You use this statement if you cannot be certain that all the database changes have been executed correctly.
    The update routines are not performed.
    ROLLBACK WORK belongs to the Open SQL command set.
    Note
    If the ROLLBACK statement occurs within a SELECT loop, the processing cannot continue because the database cursor is invalid. After the ROLLBACK statement, you should therefore ensure that all SELECT processing has been explicitly terminated.
    <b>Plz. Avoid Duplicate Threads.</b>
    Hope this resolves your query.
    Reward all the helpful answers.
    Regards

  • Drop a table when it is rolling back

    Hi,
    I created a table and started inserting into it using a select statement. After couple of hours I realized that i made a small mistake in the select statement that i used to insert into the table and cancelled the operation (it was still running). It is rolling back now and it seems that it will take atleast another few hours to rollback. My question is can i drop this table while it is rolling back and create the table again so that i don't have to wait until it rolls back?
    Thanks,
    Guna

    >
    My question is can i drop this table while it is rolling back and create the table again so that i don't have to wait until it rolls back?
    >
    No - but you can use ALTER SYSTEM DISCONNECT SESSION . . . IMMEDIATE to immediately terminate that session.
    Then you can drop the table.
    See the SQL Language doc for ALTER SYSTEM
    http://docs.oracle.com/cd/B28359_01/server.111/b28286/statements_2013.htm
    >
    DISCONNECT SESSION Clause
    Use the DISCONNECT SESSION clause to disconnect the current session by destroying the dedicated server process (or virtual circuit if the connection was made by way of a Shared Sever). To use this clause, your instance must have the database open. You must identify the session with both of the following values from the V$SESSION view:
    For integer1, specify the value of the SID column.
    For integer2, specify the value of the SERIAL# column.
    The IMMEDIATE setting disconnects the session and recovers the entire session state immediately, without waiting for ongoing transactions to complete.

  • 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

Maybe you are looking for

  • Open HTML pages in the same Browser

    HI All, I have a GUI with Help buttons which are required to open Help files in the default browser. Now i am able to acheive this using Runtime.getRuntime().exec("cmd /c start iexplore url") But the problem here is everytime the user clicks on the h

  • TS1363 How do you find ipod service to reinstall in windows 7

    I have an ipod nano 2nd generation and have trouble everytime I try and sync. Itunes tells me it's synced by it hasn't and the device disapears. I've tried help but it only give me Vista instructions I have Windows 7. I've done the re-set numerous ti

  • Changes made in Itunes not in Music Library

    Hi: I have spent countless hours fixing track names, adding artwork and all the other fun stuff. None of these changes are reflected in the music library and I can't figure out how to fix that situation. I've scrolled through the forum and can't fina

  • Remote: Albums sortet by album names and not by "Interpret"

    Hi, Why Remote sort the albums by album name? this is the second bug which is not "fixed" with the new version 2.0 of Remote. Again with the "Compilation" problem in my previous post I'm wondering why nobody is asking for that "bug"? The best solutio

  • How does one get Firefox to install 1 Password extension?

    When I download the installer, a pop-up says it cannot install because "Firefox cannot modify the needed file". What is the needed file and how can I change the file so that it will install on Firefox?