Yes, I did. Well, the status of the job was changed to "Skip and Restart", then I knowledged the worker to restart their job, then it FAILED again, then I choose the option number 8 for "all" the workers, but it never quit. Unfortunately I don't have an environment to "test" it again. I think the restart files are there, but I don't know which it needs. Thanks Fadi. Kind regards!!! Francisco Mtz. > Are you sure you chose the hidden option 8 it should work, its an hidden > option > > -----Original Message----- > From: ora-apps-dba-bounce@xxxxxxxxxxxxx > [mailto:ora-apps-dba-bounce@xxxxxxxxxxxxx] On Behalf Of > francisco.martinez@xxxxxxxxxxxxxx > Sent: Tuesday, June 27, 2006 4:14 PM > To: ora-apps-dba@xxxxxxxxxxxxx > Subject: RE: Restart files in AutoUpgrade. > > Thanks a lot Fadi for your quick response. > > I choose that option saying this failing worker to quit, but > AutoUpgrade's > execution never got me to the shell prompt, it just stayed there .... > > I tried a lot of options inside of adctrl's menu, but AutoUpgrade > execution screen never came back to the shell prompt. > > Thanks in advance. > > Kind regards, > > Francisco Mtz. > > >> Try to run adctrl then chose option 8 type all, then try to run the >> adutoupgrade >> >> -----Original Message----- >> From: ora-apps-dba-bounce@xxxxxxxxxxxxx >> [mailto:ora-apps-dba-bounce@xxxxxxxxxxxxx] On Behalf Of >> francisco.martinez@xxxxxxxxxxxxxx >> Sent: Tuesday, June 27, 2006 4:01 PM >> To: ora-apps-dba@xxxxxxxxxxxxx >> Subject: Restart files in AutoUpgrade. >> >> Hi partners, >> >> Yesterday I had an issue and I couldn't continue with an AutoUpgrade >> execution. >> >> Unfortunately I received a lot of problems during AutoUpgrade's >> execution >> due "INVALID" packages, and the last job finished with "FAILED" > status, >> so >> I couldn't continue with this process. >> >> Looking at Metalink the solution was to set next events in my init > file: >> >> event="10932 trace name context level 32768" >> event="10933 trace name context level 512" >> event="10943 trace name context level 16384" >> >> I tried to cancel my AutoUpgrade execution, saying to the "FAILED" >> worker >> to quit, but it never exit, so I decided to kill my "AutoUpgrade" >> process. >> >> After defining the above events I bounced my database, but I couldn't >> continue with my last AutoUpgrade's process execution, the problem was >> that restarted files couldn't be read. >> >> Fortunately it was only a test, but I would like to know which could > be >> the procedure to continue with my last AutoUpgrade execution?, what is >> the >> correct way to follow in case I want to restart AutoUpgrade's process? >> >> Any advice or help will be really appreciated. >> >> Thanks in advance. >> >> Francisco Mtz. >> >> >> "This email is intended for the above named adressee (s) only and may >> contain confidential and/or privilege information and should not be > used >> by anyone who is not the original intended recipient(s). Any review, >> print, copy, reliance or distribution by others or forwarding without >> express permission is strictly prohibited If you have received this > email >> in error, kindly notify the sender immediately by reply email and > delete >> this email and any attachments from your mailbox or any other storage >> mechanism. Thank you. >> Email transmission cannot be guaranteed to be secured or error free, > as >> information could be intercepted, corrupted, lost, destroyed, received >> late or incomplete, or could contain viruses. The sender therefore > does >> not accept liability for any error or omission in the contents of this >> message, which arises as a result of email transmission. Opinions, >> conclusions and other information in this message that do not relate > to >> the official business of Umniah Mobile Company and is not its >> responsibility shall be understood as neither given nor endorsed by > the >> organization." >> >> > > > > "This email is intended for the above named adressee (s) only and may > contain confidential and/or privilege information and should not be used > by anyone who is not the original intended recipient(s). Any review, > print, copy, reliance or distribution by others or forwarding without > express permission is strictly prohibited If you have received this email > in error, kindly notify the sender immediately by reply email and delete > this email and any attachments from your mailbox or any other storage > mechanism. Thank you. > Email transmission cannot be guaranteed to be secured or error free, as > information could be intercepted, corrupted, lost, destroyed, received > late or incomplete, or could contain viruses. The sender therefore does > not accept liability for any error or omission in the contents of this > message, which arises as a result of email transmission. Opinions, > conclusions and other information in this message that do not relate to > the official business of Umniah Mobile Company and is not its > responsibility shall be understood as neither given nor endorsed by the > organization." > >