Now all my worker status is 'Fixed ,Restart'...Is this the status for all workers? Do you still get the same error in the database log file?
After this , Do i need to run the adpatch and continue with the previous session?Starting the patch again and continuing with the previous session would not have any impact on the workers status. However, you may try this option and see if it works (you may bounce the database as well).
Yes i do adpatch with restart from previous session..Do you still get the same error in the database log file? If yes, fix the issue and restart the failed workers.
Now my patch started running from where it failed....
I don't know ,, is this the correct way...Yes, it is the correct way, but if the status of the workers is not correct then you may need to apply the patch from the beginning.
If anyone could help me to clarify.. please
I engaged 4 workers...No wonder it takes that long. I did a similar upgrade (on a single node) with 4 CPU (16 workers -- 4 * Number of CPUs) and it took almost 15 to 18 hours.
The server has 2 CPU's and 16 GB of Memory and it's a single node installation on RHEL 5.3 32 bit..
If anything ends up in error...What kind of backup you have taken? If it is physical backup, just stop all the services, delete all the files, restore it, and bring the services up then.
How to restore from the backup that i have taken while in a working instance...
Is there any docs ?