About the Roll back mechanism
From the specification I know that when an instruction is a long-delay operation the instructions behind will be roll back, the question is how the queue of the thread recover?
for example, when encounter a store instruction, the instructions in E and D stage of the pipeline will be roll back, but the very instruction stay in the M stage, when the memory acess operation finish, how the schedualer recover the instruction queue?
Any comment is welcome, thanks
As I understand the documentation, a thread will roll back and (if the instruction in flight is a long latency instruction or a resource conflict) go to a Wait (not-ready-to-issue) state. The rolled-back instructions will not re-issue until their input conditions are resolved. Remember that the F and S stages (where the instructions are rolled back to) are Fetch and Thread Selection, so this is before instructions are picked from any of the threads on the core and before they are decoded. The in-flight instruction will continue from the M stage when the memory operation completes.
Also, I think the rollback condition caused a store operation only happens when the store buffer is full, not on all store operations.
Jeremy
Similar Messages
-
itunes 64 bit on windows 7 is unable to install, i have the 64 bit installer version but it keeps saying "errors occurred" at the ( rolling back ) phase. HELP!!!
I have the answer and this might be useful for any one else wondering about this in the future. If it helped you or explained what you wanted to know. Replay to the post pls
It's quite easy actually. First have your "iTunes Library Extras", "iTunes Library Genius", "iTunes Library", and "iTunes Music Library" backed up. Download ans install iTunes 64-bit. I don't know what's so 64-bit about iTunes 64 since Win7 reports it as a 32-bit application in the task manager. But anyway. Install iTunes 64 and launch it. If you migrated your library to another drive like me go to settings in iTunes and change the directory to your location. Close iTunes. Replace the newly created files with your backed up files. Launch iTunes. iTunes will load and then update your library and from there you are set to go! so basically it is just like a normal upgrade. But if you hesitated to go from 32 to 64 like me, here is your answer.
By the way. I'm using Windows 7 64-bit with iTunes 64-bit and it works without problems and syncing with my iPod Touch also works flawlessly. -
How to know how long the roll back is left?
Hi, experts,
I run a insert statment for about half hour. I just broke the procedure by clicking the break button in pl/sql. I want to know how long the roll back is left.
Thankspl/sql has a break button?
assuming that you're using some gui tool, and hit a break button while executing some pl/sql - when the "break" is hit, the gui either rolls back the transaction or it leaves the transaction alone, waiting for you to either commit or rollback.
the rollback will stay there until the transaction is either committed or rolled back.
when the session disconnects, it will either rollback or commit the transaction (depending on the tool). -
Questions about the Buy Back Program
If I purchased a phone today that costed $600 but $200 with new 2 year contract activation, would the Buy Back program money back percentages come from the $600 or $200?
Also in about 6 months if I decided to return the phone for another that costed (imaginary prices) $700 but $300 with a new 2 year contract, would the money I got back from the first phone go towards the new contract price ($300) or would I have to pay for the phone in full ($700)?
Thanks in advance.Crystallee,
Thank you for your kind replies to my question, but I'm still not getting it.
Please let me give a specific scenario that could happen with my situation.
I bought the Nexus s unlocked for full retail of $529.99 from my local retail Best Buy about 3 weeks ago. I also purchased the "Buy Back" program with it.
I then walked next door to the T-Mobile store with phone in hand and opened a non-contract "Even More Plus" month to month plan.
At that time my current line contract with AT&T had expired, so I had no early termination fee when I cancelled service to start with T-Mobile.
Now, If I decide to purchase a new phone four or five months down the road, my understanding from the sales associate at BB, is that I would give over my nexus to BB in exchange for a BB Gift card in the amount of 50% of what I paid originally, $529.99 for the Nexus s.
I could then proceed to open a new line of service with another carrier that BB sells, i.e. Sprint or Verizon and would only be liable for the new contract price for that new phone, and I would be able to use the Gift card from the nexus turn-in (Buy Back) to pay for the new phone on a new 2yr. contract.
That was the understanding I had from the BB sales associate, who I think was a lower level manager.
Let me know if I have misunderstood the "Buy Back" process as I've described it here.
Thank you again for your patience. My son would understand all of this. I'm getting too old! (lol) -
3G iphone outstanding spec! Shame about the plastic back cover!
WOW I am so totally blow away by the spec of the new 3G iphone!
I have only one criticism why when Apple put so much care into the styling of the new Macbook Air & the first gen iphone/ipod touch etc with sleek brushed metal finish to the case have they opted for a plastic back cover on the new 3G iphone?
I hope if they are giving us the option of a black or white back cover that they have a rethink and also give us the option of a metal back cover too!!! Just a thought...
Message was edited by: NRG1970There is a simple reason that it has a plastic case.
In side the new phone there are 10 radio transmitters / receivers that all need access to the outside world via a radio transparent material. The radios are the multiple phone standards for world coverage, GPS, Bluetooth, and WiFi. A metal case would not allow all these signals to pass through. -
Can a Rejection in an Approval Step roll back the data from table
Hi All
We are using the BPC 7.5 MS Version SP 4 for Quantity & Sales Planning.
The main drive dimenion is the Material Dimenion whiich is having almost 65000 member id's and increasing.
I have a situation where the a High Level Planner Input some quantity and it allocated down at Material Level.
When the Surbodinate Planner under the High Level Planner looking at the allocated value, he has the option to change the quantity.
But after he make the changes to quantity and send the data to the data base, the High Level Planner can accept the Change or Reject the change.
If the High Level Planner Reject the change, make by the Subordinate Planner, the Data will Roll Back to its original value, meaning the Data Submitted by Subordinate Planner will be deleted from the table and the earlier Value from the High Level Planner will show.
Is this kind of facility available in BPC 7.5 MS Version of Rolling Back the Data already comiited to the data base.
Looking forward to hear from you all on the same.
Regards
KrishOne idea will be that you have to insert the users like dimension into BPC. This will be probably the way how you have to design your application.
In this way probably you will be able to simulate this behaviour.
Any way I will come back to your request.
Why the roll back it wil help?
May be the reject is just for planning of one material why do we have to roll back everything planned for other materials?
Other idea for implementation is related to what means the approval and reject. Are we speaking about work status or are we speaking about another type of approval.
It is not a simple discussion. We have to speak about detailed reguirements and function by that it can be easy achieved this behavour requested.
Regards
Sorin Radulescu -
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,
blf2vkrHi 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 -
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. -
Photoshop 12 error 1935 roll back
I have received the error 1935 the roll back error in windows for photoshop 12 I have tried to resolve it but the file 00BE does not show on the C: drive
Hi Chrisvgr,
Thanks for posting on Adobe forums.
Please try steps written in the doc :
http://helpx.adobe.com/creative-suite/kb/error-1935-assembly-component-microsoft.html
for more information about the error Please check this document from Microsoft:
http://support.microsoft.com/kb/926804
Thanks
Sandeep -
RuntimeException in OnMessage() does not roll back
Hello All, I have a transacted queue, the consumer is a java application. I configured
an error queue for that queue. If I rollback manually in OnMessage(), the rolled
back messages go into the error queue. However, if I have a RuntimeException,
the last message (which has caused the exception) remains in the main queue pending
and does not go into the error queue. I thought a RuntimeException causes a rollback().
I use WLS 8.1. Any idea?
Zoltan
Hi Zoltan,
A runtime causes a rollback in an MDB, per the J2EE
spec, but a runtime exception does NOT cause a rollback
on a regular async client. The JMS specification is ambiguous
on the latter - thus the difference.
Instead, the message is
redelivered once, and then, if it fails again,
the message is no longer delivered
and is implicitly committed on the next call
to session.commit(). In your
case, I highly recommend explicitly forcing the rollback.
Tom
Zoltan Pinter wrote:
> Hello All, I have a transacted queue, the consumer is a java application. I configured
> an error queue for that queue. If I rollback manually in OnMessage(), the rolled
> back messages go into the error queue. However, if I have a RuntimeException,
> the last message (which has caused the exception) remains in the main queue pending
> and does not go into the error queue. I thought a RuntimeException causes a rollback().
> I use WLS 8.1. Any idea?
>
> Zoltan
-
Bean-managed stateless session bean can't roll back using JTA
I use weblogic6.1sp2 + jdk131
a stateless session bean must do 2 things:
insert a record to A table and delete another record in A table
this bean has the same structure as the example in
j2eetutorial/examples/src/ejb/teller
I use TxDataSource in weblogic
if delete fail, the roll back is run,but in database,
the insert record is STILL in A table.
any idea?make sure that your deployment descriptor says "transaction required".
Also, If the insert and delete are two different methods, the client must call these two methods in the same transaction scope. -
Several instances of MDB accessing a Q and one rolling back a message
I have one input queue being served by several instances of an identical
MDB.
When a problem occurs with an MDB processing one of the messagse read on the
queue (for instance, it could not forward the answer, the bean is being
brought down through an exception or otherwise), I would like to rollback
the message it was processing since it could not complete the job.
I would like to let the container manage the transaction and use
setRollbackOnly when the instance of MDB fails or has to abrupty end. What
would happen to messages that are currently being processed by other MDBs
(and thus have not been committed) and followed the message that caused the
rollback in the input queue? In other words, uncomitted messages submitted
to other MDB instances after the failed MDB started the transaction that
ultimately failed. Will they also be rollbacked?
Wim van der Kerkhoven wrote:
> I have one input queue being served by several instances of an identical
> MDB.
>
> When a problem occurs with an MDB processing one of the messagse read on the
> queue (for instance, it could not forward the answer, the bean is being
> brought down through an exception or otherwise), I would like to rollback
> the message it was processing since it could not complete the job.
>
> I would like to let the container manage the transaction and use
> setRollbackOnly when the instance of MDB fails or has to abrupty end. What
> would happen to messages that are currently being processed by other MDBs
> (and thus have not been committed) and followed the message that caused the
> rollback in the input queue? In other words, uncomitted messages submitted
> to other MDB instances after the failed MDB started the transaction that
> ultimately failed. Will they also be rollbacked?
No. Only the message participating in the rolled back transaction
will be rolled back. Messages in other transactions will not be
affected.
>
>
>
>
-
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 SCOM 2012 R2 after deploying Cumulative Updates
Hi,
I updated my SCOM 2012 R2 Environment into CU2 and I need to roll back this CU2 into the previous version CU1.
Is there any way to do the roll back to any previous version of CU?
Thanks,
KhaledYou should refer to http://support.microsoft.com/kb/2929891/en-us which provide uninstall information
To uninstall an update, run the following command:
msiexec /uninstall PatchCodeGuid /package RTMProductCodeGuid
Note In this command, <var>PatchCodeGuid</var> is a placeholder that represents one of the following GUIDs.
Collapse this tableExpand this table
Patch Code GUID
Component
Architecture
Language
{D6943F32-41C0-4252-B216-4EE6867F74FB}
Server
AMD64
EN
{1D38FCF3-DDB1-4810-B747-898E7FCCC57B}
Gateway
AMD64
EN
{3FF0B1F5-9A92-4544-A311-6CCFE552BD0F}
WebConsole
AMD64
EN
{033805E7-9FBA-45A8-B9E0-DEF1395D0E63}
Console
AMD64
EN
{4A2BA6B7-9A24-46FA-A379-1ABD74E576AB}
Console
x86
EN
Additionally, <var>RTMProductCodeGuid</var> is a placeholder that represents one of the following GUIDs.
Collapse this tableExpand this table
Component
RTMProductCodeGuid
Server
{C92727BE-BD12-4140-96A6-276BA4F60AC1}
Console (AMD64)
{041C3416-87CE-4B02-918E-6FDC95F241D3}
Console (x86)
{175B7A24-E94B-46E5-A0FD-06B78AC82D17}
WebConsole (AMD64)
{B9853D74-E2A7-446C-851D-5B5374671D0B}
Gateway
{1D02271D-B7F5-48E8-9050-7F28D2B254BB}
SCX-ACS (AMD64)
{46B40E96-9631-11E2-8D42-2CE76188709B}
SCX-ACS (x86)
{46B40E96-9631-11E2-8D42-2CE76188709B}
Roger -
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
Ramyatry logminer.
Maybe you are looking for
-
I got a new macbook. How can I transfer my old songs on my iphone onto the new itunes
I dont want my music deleted but I do want my new songs on my iphone. How can i do that?
-
How to resolve the decimal point issue??
hello friends, I had declared a variable of variable type P(16) decimals 6 for price. The price is calculated accurately and stored in the variable. The value that got stored is 5094390.000000. I declared one more variable of type ekpo-netpr and move
-
I need to create dml/ddl handlers, i have searched a lot, but yet to find such materiel to learn. I need from beginner to advance level material with examples. Can any one help me. I have thousands of DEQUEUE MESSAGES to handle.
-
Mac book air won't turn on after shutting down unexpectedly
I was surfing the internet, when it all of a sudden went black and shut off. No warnings or anything. The light on the charger no longer lights up. I have tried all the tips on apple website and nothing works. Any suggestions?
-
What you mean by WMS at storage location level & WMS at bin level??