Roll In Roll Out issue
I've got a button that shifts down when you roll over it, then moves back up then you roll out. All is keen except when you roll slowy from the top, if you hit the right spot you get into a tedder todder effect of rolling in and rolling out until you move up more. Thinking about adding a timer or to count how long ago you rolled out, are any of you familar with a solution to this? Seems like it would have popped up.
If you are using a button symbol, go into the Hit frame and make the area defined in that frame large enough to cover both the Up and Over frame areas.
Similar Messages
-
Consolidation issue after Roll-out
Hello Experts,
We are rolling out ECC 6.0 to Singapore.
Scenario - India is selling to Singapore as a customer. India has ECC 6.0 and solution has to be rolled out to Singapore in June 2010. Singapore financial period is starting from April 2010onwards.
From April till Go-live for Singapore, India will still keep selling the goods to Singapore and Singapore will be purchasing from india.
After Go-live, Singapore will use ECC 6.0. Till then, Singapore is treated as a customer to india and India is supplying goods to Singapore.
During cut-over, how can we migrate the April to June data of Singapore?
Since it is not a legal entity and treated as customer in India system, how can we knock off the financial entries pertaining to Purchases and Sales done by India over Singapore from April to June.
I repeat that we cannot show the cross company transactions since Singapore does not have the system and from Apr to June, India is still selling to SG as customer and we deem that issue will appear in Consolidation pertaining to-
Knocking off - Purchase & Sales for cross company txns
Knocking off - Vendors and Customers for Cross company
Sales entries for India and Purchase entry for Singapore during consolidation from Apr till June (quarterly consolidation).
Please let me know if anyone has done this before or any ideas how to achieve it.
regards
raviHi Ravi
did you manage to figure out this as I am having similiar issue where my management wants to see intercompany tansactions after roll out.
Thanks
Hiren -
Roll-out project implementation issue
Dear colleagues,
This issue might have already been turned up but couldn't find any related threads.
We have created our template project, set up the structure, added project documentations (11MBs converted to PDF ), training materials, everything seems to be ok here.
Now we have to create our first implementation project based on the template. Template is defined and is public (visible), Global Rollout Functionality is activated. The issue is, when we cretate the implementation project the structure is copied from the template, even the training materials can be seen in SOLAR02, but none of our blueprint documents are copied to the roll-out project.
Have you ever faced such situation before? Do you have any clue where to find the root cause of this?
thanks in advance for your replies
Szabolcs
Edited by: Szabolcs Dombó on Jul 17, 2008 1:26 PMHi,
Below mentioned is the details of using the SOLMAN for template rollout project. Hope this helps you.
The process of setting up and using the template in projects involves two or more individual projects. The first project is referred as "Master Project".
For Master project: Global Program Setup(Project Preparation)
- Create a master project. this must be of project type template since this will allow the packaging of reuse elements.
- Create the required number of templates(with in master project). At this stage, these templates are empty packages.
- Select standard scenarios as a starting point to build business scenarios in the master project, in the same way as for a normal project.
For Master project: Global Buisness Blueprint
- Detail standard scenarios to customer specific solution structure
- Assign template(s) at the scenario level of the customer specific solution structure
- Set global attributes to determine global/standard/harmonised/local processes
- Describe global business and technical requirement.
==========================================
Reuse of template at local rollout site
Project Preparation:
- Create a local "rollout" project. This can be either an implemetation project type or can itself be a template project type if you may need to reuse sections of this project in its own right.
- Select one or multiple templates and related scenarios in the scope tabbed page.
Note: there is no direct relationship between the templates choosen here. In other words you can attach tempalte form multiple other "master" projects, which may have no other relationship to one another.
Business Blueprint:
- The contents of the templates which have been attached to the "roll-out" project appears as elements of the project structure.
- Processes defined as global attributes with in the template area dopted wholesale with no changes.
- Adapt harmonised and local processes to local specific requirement(such as enhance process scope).
- Document local specific requirements of harmonised or local processes.
- Add further local specific structure elements as required and document.
Hope this help. Pls assign points.
Rgds
Manish -
Does anyone can help me with Typical issues to deal with when rolling out ERP in Japan?
Does anyone can help me with Typical issues to deal with when rolling out ERP in Japan?
If it were me I would schedule an appointment at the store where you bought it and meet with the Manager of the store in person. Print this post and bring it with you along with your iMac.
And change the password on your Apple ID and then see if there are in purchases in your account that you did not make. If there are then someone did get your ID and password. If not someone got your Credit Card information from somewhere and used it. -
Issue during Template roll-out during FIT-GAT session
Hello SD Guru,
Hope you all are doing fine these days...!!!
I am facing a typical challenging situation in my Template roll-out project based out of Europe and would need some expertise advice to tackle the current situation. As a matter of fact, we are using a Development system and landscape is :- DXX --> QXX --> PXX for major Consumer Products and Goods based client, The support team works for any kind of bug fixing and small CR on this landscape i.e DXX, Development for the earlier roll-out exist in the current landscape set-up with template version 1.0. Now since we are having changes in business operating model, we are having template based roll-out in the same landscape and the new template would be version 2.0.
Could anyone suggest what should be the mitigation plan when Support team, Template version 1.0 and Template version 2.0 would be co-existing in the same environment ?
Once the realization of the template version 2 is done and after that we get any specific bugs....where do we need to troubleshoot ? Is it template version 1.0 or template 2.0. The best line of thought could be done in terms of small example...lets say Have a custom program created due to template version 1.0 for creation of Rush order and Consignment sales based on business critical field maintained in a custom table, now due to some requirement gathered during current roll-out and this functionality is extended to include free of change sales with VAT. Hence functionality (sales order create program with custom table) come to template 2.0.
If you have ever come across this kind of situation, please share your inputs or any kind valuable approach would be appreciated...!
Thanks,
SarthakHi Yandamuri,
(Incorrect account determination: IN02 V1 100501) - Please check whether account determination is missing for this account in OB09.
Enter account number with a maximum of 10 characters -
This is related to the number of digits defined in the Transaaction code OBD4 Please see the OSS Note 548947 and 907032 is clearly stating about this error.
Posting for general ledger account 100501 amount 5,880.00- set in batch input - Check the document type related to batch input session.
Please contact SAP India if necessary.
Warm regards,
Murukan Arunachalam -
Rolling out ADE to Open Access Computers in libraries
(In the UK). In Plymouth we are using Secure Electronic Delivery as the default to deliver access to documents provided by the British Library. Internet Explorer 7 (and this is also known with Firefox and other browsers) causes an ebook reader detection error as part of the downloading process "Downloading this eBook requires Adobe Acrobat eBook Reader version 2.2 or later to be installed on your computer" (even though all our computers are on Reader 7.0.9). The page then provides a link to download the latest version. The problem is that, despite being told to ignore the link and scroll to the 'download your ebooks' link further down the screen, many users are clicking the update link and ending up with Adobe Reader 8 without ADE, or a misfunctioning ADE because they do not have administrator rights, or a screen which hangs and does nothing, or an ADE that will not allow them to print. In open access areas all computers are locked to a standard 'frozen' image which is restored after each log-out. Users, therefore, are unable to save any changes which means that they also have to repeat the steps every time they want to download an SED everytime they log-in. (Yes, because of 'easy activation', we also have to make it clear to these users that it is 'download and then print' or there is no further access to the document, despite a 14day access rule; and no-use of memory sticks too!). We would love to be able to maintain our ability to standardise these computers on the latest version of the Reader software, but are unable to do so because we do not have the manpower to manually install ADE on each computer (over 2,500!) to make it part of the 'locked' image. We know the eBook Reader detection error is most probably caused by the underlying software technology difference between IE7 and Adobe 7 and would hope that installing Adobe Reader 8 and ADE would restore the seamless process that we had long established using the Reader 7 series!
Could not Adobe please consider a means by which, say ADE 1.5, could be packaged and rolled-out centrally? Then also consider doing the same for future releases - it would really make life easier for everyone. If not we will have to remain on Reader 7.0.9 and users will 'suffer' as the technology becomes more and more obsolete, and suffers from more and more problems caused by a widening gap in software technologies. We understand the idea behind the decision to make ADE an IRA (internet rich application) but the growing use of DRM and the need to delivery these documents within closed environments, to people who cannot be given full access permissions, means that there should also be a concurrent method to allow updating in such situations. Our 'problem' rate for SED is beginning to climb (from under 3% (based on 16,000 transactions) before the release of Adobe 8, to 6% afterwards (based on 7,000 transactions). Before the release of 8, 70% of the problems were because people didn't read instructions we provided; after 8's release, 70% of the problems are caused by the technologies (eBook detection; downloading Reader 8 and not ADE; ADE not functioning due to local permissions etc etc). These seriously affect the value of the service and also the perception people have of the service and of Adobe products (eg: the IE7 error states "Adobe eBook Reader not detected" so, even though your product may not be to blame for the users' inability to get to their document, they blame Adobe Reader, especially if they know they have Reader 7 installed!
My apologies for a long post but I consider it an important issue as well as it being important to lay out some of the logic and arguement as to why.
GrahamThank you very much for taking the time to write this long and accurate post. We are very much aware of this issue and are working as hard as we can to resolve this. It might not be possible to squeeze it into 1.5, but we will get to it as soon as we possibly can.
Can you submit a support incident at www.adobe.com/support/digitaleditions/ so we can try and resolve the immediate problem (incorrect detection and misleading message)? We can also discuss offline how your organization and our can work together to resolve the larger problem. Thanks. -
Versioning and parallel development streams for worldwide SAP roll-out
Hi SDN folks,
My customer is in the process of a worldwide roll-out of SAP. They have a transport environment for ECC that looks like this:
D -
> QA -
> R -
> P
We have SAP Charm installed and running in solution manager - to manage the creation of transports in the D system.
The problem we are facing is how to manage parallel development changes and configuration changes.
For example - if we have developers working on a change that is in test in the QA environment - and we hit a production emergency in P - we then need to make an emergency change to the P version (which would only be available in P and R) - and transport this change through to P - in the process - overwriting the changes that our developers are working on in the D and QA environments.
We also have the issue of objects for multiple countries being developed and configured in parallel - and so there will be version conflicts up the to the QA system as well.
Is there any kind of solution for the management of parallel development streams - and versioning - for all custom code / development objects and for configuration changes(other than introducing a second development system)?
Is there any kind of 3rd party product for SAP that helps to solve this issue?
Currently we are considering development freezes, manually renaming objects with versioning identifiers (will only work for some objects), manual backups of versions. - none of these seem to be a tidy universal solution, is there one?
Any help / directions you can offer will be appreciated,
many thanks,
JulianHi Julian,
Thanks for the clarification!
Managing production support and new development after go live is always a challenge. It can be addressed in many ways, but it is most important to create a set of rules and stick to the procedure. If you do not want a "second" landscape, you are going to have objects "overwritten" in the D and Q systems when you need to make a production fix -- as you must revert the object in D to the P version to make the fix. Even with a second landscape, objects will have to be merged somehow when a fix is promoted to production.
As I said above, what you can do is have your developers save their current development in released transports before making the production fix. This saves a version that must be merged with the fix, anyway. That is:
Object A is the produciton version and must be fixed.
Object A' is the current development version (unfinished) and is saved into a released transport request.
In D, Object A' is reverted to the A version and corrected for the production error, creating object A'' that is promoted to production.
Object A' and A'' are manually "merged" into A''' as the new current development version.
Yes, objects are overwritten with this method. However, you can always retrieve what has been overwritten since it has been saved in a released transport.
Another option is to bypass Q for production fixes. I.e. D -> R -> P. However, this invalidates the objects in Q until the merged version is created in D and transported to Q.
In any method you choose to do this -- dual development landscapes or not -- discipline and managment are a must.
Best Regards,
Matt -
Creating Company Codes in Global Roll-out Project
Dear Experts
Our Company operates out of multiple countries and we have embarked on implementing SAP across all our subsidiaries in these countries. We are planning on a Single Instance Single Client Landscace. With this in mind, we have completed the Global template design for the overall Enterprise Organization structure and also standardized on the business processes to be followed.. We are planning to configure these in our golden client against a company code (copy of 0001) to be used as reference for the subsequent actual country roll-outs. The strategy for rollout in those countries where SAP does not provide any Country template, we will use BC sets to copy the GT configurations and move on with the country specifc configurations. This will ensure the GT specific configurations will carry forward to those country legal entities. Thi doubt we have is for those countries where SAP recommends we start with a copy of the country template. In those countries what is the best / recommended practice to creae company codes. If a create a company code by copying the country template (say IN01 or BR01), then how do I get to use all the configurations already done for the GT reference company code. If I just copy of the GT reference company code to create a country specifc company code, then how do the country specific configurations (that comes with the country template) be available?
Appreciate if I could get some light on this subject
Regards
NSKDear NSK,
Did you find a solution to your problem?
We are facing exactly the same situation with roll-out on multiple countries on a single client single instance environment. We are still trying to create our Global Template in such a way that we can later on use it with all the aforementioned localizations needed for our subsidiaries.
Can you provide any information on how you dealt with this issue?
Thanks and regards,
Heraklis -
SAP GUI Roll Out Best Practice
I was wondering what is the best practice for rolling out a new SAP GUI. My plan is to upgrade our IT Department, and Super Users with the upgraded GUI and see if any errors/problems occur. If I don't have any major issues I would roll out to the User Community after about two/three weeks.
Is this typical practice ? I have heard other Professionals say to just roll the GUI out, and don't worry about testing it ? and I have heard other companies etc.. do a set of testing scripts etc..
Any feedback appreciated. - Thanks.Hi,
yes I have done it on our company for years.
once new released or new patch of SAPGUI is launched, I will ask my SAP Functional, ABAP and BASIS mates to try it for a month with various report and transaction variation for standard and Z-tcodes, for dialog and background processing, printing, and export and import data.
After my IT-SAP mates feels that SAPGUI is ready to be used, I will launched it to all user in another department and keep to listen any feedback from them regarding this SAPGUI.
hope it help you.
rgds,
Alfonsus Guritno -
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 -
Dear ALL ,
I am a basis conslustant....
I have a query. In our company recently implementation got finished in our main branch.
They are obout to go for roll out in couple of months....
I want to know that as basis consultant what could be or what will be my responsibilites...as they will go for roll out in India and as well as other international branches.
Please suggest me....So that I can prepare myself properly, if they select me for this assignment.
ThanksDecisions about whether clustering or not should have been done before If you go live in a month, it's pretty unlikely that you will be able to set up a clustering.
You can't "distribute" a database across locations to do "load balancing", how should that work technically? Database nodes would need to have a HIGH SPEED interconnect - and if you have such a connection, network speed is not an issue However, it's possible to set up a FAILOVER cluster on a different location.
For more information about High Availibility see http://service.sap.com/ha
The SAP network protocol is VERY good, depending on the type of the connection you won't see much difference between working locally and remotely.
Markus -
Repository for legal, local requirements (at a global roll out project)?
Hi,
we are currently working on a global roll out into several Eastern European countries. We have got a question concerning the localization of the SAP Systems. Are you aware of any repository for the legal, local requirements of SAP systems on a country basis?
Examples:
What needs to be considered designing an invoice for Poland
Is there any specific VAT reporting required for Poland
Thanks!
Kind regards
IngaDear NSK,
Did you find a solution to your problem?
We are facing exactly the same situation with roll-out on multiple countries on a single client single instance environment. We are still trying to create our Global Template in such a way that we can later on use it with all the aforementioned localizations needed for our subsidiaries.
Can you provide any information on how you dealt with this issue?
Thanks and regards,
Heraklis -
Infinity roll-out kills Standard Broadband Service
BT have rolled out Infinity to my area and since the roll-out my Standard Broadband Service has deteriorated to an extent that BT have confirmed they can longer guarantee me that service (despite the fact they are still willing to charge me for it)! Anyone else been impacted in this way? I've been told my only option to obtain Broadband is to pay for the more expensive Infinity.
Its not an issue in all areas, but the longer the distance from the cab, the more noticeable it is. Generally, if people are getting very low speeds due to distance, it does make sense for them to upgrade to Infinity, if its available.
I believe that the Infinity pricing is fairly competitive anyway.
Infinity has not really interested me because I get between 9-11Mb on my line, and I use broadband talk quite a lot.
My local connection is not perfect, and one of the two pairs into my house are faulty anyway, and the current pair does have a HR somewhere, which can show itself if the landline is not used for a week (no DC wetting, if you know what that means)
That can result in an occasional disconnection on an incoming PSTN call, but not enough to worry about.
To fb3
What connection speed do you get at the moment?
There are some useful help pages here, for BT Broadband customers only, on my personal website.
BT Broadband customers - help with broadband, WiFi, networking, e-mail and phones. -
Why must I upgrade RIGHT NOW or quit CC when an update rolls out?
After the umteenth iteration of this, I'm growing very tired of being FORCED to update my creative cloud manager every single time an update rolls out. I come from a an IT strategic background that strongely believes in not changing smoothly running setups until the most opportune time (between projects), and this is necessitating mid-project version changing.
What is changing so frequently with that app manager service? Why is it so critical that I be up to date that you force the exiting of the service rather than let it run one version back? Please consider changing this policy as it is disruptive to professional workflow, though, admittedly, the app manager itself isn't likely to cause a project jeaopardizing problem as much as, say, after effects or premiere are. THe more significant issue may simply be that it's annoying me and the staff here when it seems pretty much every time we ever click that CC icon, we have to sit through an update.I agree. Sick of this kind of blackmail from Adobe.
-
Hi,
Iam new to this forum but not sure where to post this question. Pls tell me where to post and in the meantime can someone guide me on the following
we are in France and we are doing some changes for France market in SAP. Additionally we need to do roll out for Romania, sweden market and swiss market i.e. our company is not in sap in Romania but we are on SAP in sweden but need to bring in some additional functionalities for swedish market.
My question is ,can we do the roll rout for Romania market and do some major changes for existing swedish market right here sitting witth the whole team in France including doing integration testing , cutover etc.... or do we need to form additional team in Romania ?
our present team in France can handle the task for Romania (roll out) and changes for sweden. But the issue is it necessary to have a team in romania and sweden too (i mean for blueprint/realisation phase at least ) ??
regdsFor organizations with lots of business units, locations, as a safe approach sometimes, the implementation will be carried out in one place. If found sucessful and acceptable, then the same will be "rolled out" to other business units, locations with or without modifications.
IN this context you would also have heard of a concept called "global template". The global template will be built and this template will be "rolled out" to other locations with or without modifications.
Ravi Thothadri
Maybe you are looking for
-
Opening an exisiting file or site on another machine
I have macs, a desktop and portable. I would love to edit my site from both machines. I use the idisk to transfer file and keep both system update. I can see the site and it's files on my idisk, but iWeb will not import or open the files. I know ther
-
Oracle 11g B2B commandline utilities to manage trading partners, agreements
Hi, I am working on Oracle 11g b2b server configured with ebMS messaging protocol. My host trading partner is having more number of remote trading partners and hence more agreements. I am exploring the possible means of automating the creation and de
-
To Get Clander Id based upon company codes....
hi all, i need to get the calender id based upon the company code.. is there any table for that... Example: 1000 for US, 2000 for CA(canada). helpfull answers will be rewarded... Regards, Murali.
-
Actual GoodsIssue date not updated
Hi We have a problem in Actual PGI date. For few documents system is not populated the actual PGI date in it's field, later we are able to complete the billing etc. This is only an incident. What will be the reason, why it is not populated, what will
-
Can't login to Apple Discussions from phone
I've done it before.. but now every time I try to login I just get a white screen... of couse I am writing this from my Mac Pro because I can't from the iPhone... all the other websites seem to work fine. I can get to apple.com and see the discussion