Re: Restart files in AutoUpgrade.
- From: francisco.martinez@xxxxxxxxxxxxxx
- To: ora-apps-dba@xxxxxxxxxxxxx
- Date: Tue, 27 Jun 2006 11:35:43 -0500 (CDT)
Thanks a lot Yury.
I think my restart files got corrupted.
Also, I think there were a locking problem because I ran utlrp.sql script
to compile my "INVALID" objects during AutoUpgrade execution.
After telling to my "FAILED" worker to quit, it says that it was in "Quit"
Control Mode, but I saw it in "Done" mode. Adaimgr session never finished
and never gave me shell prompt.
Yury, just one question:
> PPS Next time just before to kill adadmin I would recommend to try to
> make a backup copy of $APPL_TOP/admin/$TWO_TASK/restart directory and
> of two tables fnd_install_processes and AD_DEFERRED_JOBS. In I would
> did it in that case presumably you would be able to restart adadmin
> session from the same place as where you got your problem by restoring
> those three things on the original locations.
>
Would I do your above advice before killing my "adaimgr" session?
Thanks in advance.
Kind regards,
Francisco Mtz.
> Hi Team,
>
> In the case described above:
> Then one of the adworkers is failed and there is need to restart
> database (for any reason, set parameters, set ) in order to sort the
> problem out.
> I would do the following:
>
> 1. run adctrl utility
> 2. would choose "3. Tell worker to quit" for all workers including
> failed one.
> 3. Normally that happens is aster some time all adworkrs processes quick
> 4. and adadmin giving up and shell prompt is available
> 5. restart the database.
> 6. Restart adadmin utility (it prompts if you would like to continue
> with previous session. the answer is Yes ;)
>
> Fadi - adadmin -> "hidden option 8" is to say adworker "please ignore
> that error and cary on with next step as you would execute it
> normally". I wouldn't recommend to use it unless you are instructed by
> Oracle or you know exactly what are you doing.
>
> Francisco - if optio 3 didn't help you. I would try to find out what
> "not waiting" adworkers are doing. It might appear that they are
> waiting for some lock in the database or whatever (switch on 10046
> trace or something).
> Adworkers in waiting state suppose to quick gratefully. If they are
> not it means that there is more serious problem need to be addressed.
>
> Next time you will face that type of problem. Please post "1. Show
> worker status" results of adctrl utility as well as last bit of
> adworker's log file which has failed.
>
> PS Your restart files get corrupted because of you killed admin I
> would assume. In that if you haven't got any other options I would try
> to execute the same patch from the beginning.
> PPS Next time just before to kill adadmin I would recommend to try to
> make a backup copy of $APPL_TOP/admin/$TWO_TASK/restart directory and
> of two tables fnd_install_processes and AD_DEFERRED_JOBS. In I would
> did it in that case presumably you would be able to restart adadmin
> session from the same place as where you got your problem by restoring
> those three things on the original locations.
>
> Just my 0.02£,
> Yury
>
>
> On 6/27/06, Fadi Hasweh <fhasweh@xxxxxxxxxx> wrote:
>> Yury might help us on this one.
>> Yury what do u think
>>
>>
>> Fadi
>>
>>
>> -----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:39 PM
>> To: ora-apps-dba@xxxxxxxxxxxxx
>> Subject: RE: Restart files in AutoUpgrade.
>>
>> 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."
>> >
>
>
> --
> Yury
> +44 7738 013090 (GMT)
> ============================================
> http://otn.oracle.com/ocm/jvelikanovs.html
>
Other related posts:
