How many people have really tried the other options in "adctrl".  Quite
rare that you
have to attempt them :

     3.    Tell worker to shutdown/quit

     4.    Tell manager that a worker failed its job

     5.    Tell manager that a worker acknowledges quit

     6.    Tell manager to start a worker that has shutdown


Hemant K Chitale
Principal DBA
Chartered Semiconductor Manufacturing Ltd


"Bellows, Bambi" <[EMAIL PROTECTED]>      30/01/2002 05:56 AM
Sent by: [EMAIL PROTECTED]

Please respond to ORACLE-L
                                                                                       
                        
             To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]>           
                        
             cc: (bcc: CHITALE Hemant Krishnarao/IT/CHRT/ST Group)                     
                        
             Subject: RE: adpatch question                                             
                        
                                                                                       
                        
                                                                                       
                        
                                                                                       
                        





Matt (and any others who are interested) -





My adpatch went fine after tinkering under the hood except for one place
where Oracle created a table, populated it and blew away its max extents.
Amusing, but lame.  I can't speak for Oracle on this one, but it looks to
me that if you wind up in the position I was (that is to say screwed) that
is the way to fix it.





Another thing to bear in mind is that the hidden option (8) in adctrl
should NOT be selected unless the workers are actively working.  If ps -ef
worker does not show any workers, do NOT quit an active process.  You are
better off, at that point, to rerun adpatch without killing anything and
letting adpatch attempt to clean up after itself.





HTH,


Bambi (head under the hood gal).





     -----Original Message-----
     From: Adams, Matthew (GEA, 088130) [mailto:[EMAIL PROTECTED]]
     Sent: Tuesday, January 29, 2002 3:28 PM
     To: Multiple recipients of list ORACLE-L
     Subject: RE: adpatch question





     If he's not interested, I am.  Please post a summary
     upon completion.


     Matt


     ----
     Matt Adams - GE Appliances - [EMAIL PROTECTED]
     <Discussing a black rectangle silhouetted on a martian landscape>
     "That is the top of the calibration target,
     that is NOT in fact a monolith"
       - NASA TV Commentator - 7/5/1997


     > -----Original Message-----
     > From: Bellows, Bambi [mailto:[EMAIL PROTECTED]]
     > Sent: Tuesday, January 29, 2002 2:53 PM
     > To: Multiple recipients of list ORACLE-L
     > Subject: RE: adpatch question
     >
     >
     > John --
     >
     > Thanks for the email back.  Apps suck, and going under the
     > hood is not for
     > the weak of stomach.  Of course, I'm not... and, at this
     > point, fighting a
     > fire is more fun than watching a heap of smoldering ashes.
     > So, I did it.  I
     > went under the hood, and found that the fnd_install_processes
     > table has one
     > entry for each worker plus one for worker 0, which, I assume,
     > is the driver.
     > The status for 0 was W, 1-3 was R and 4 was J.  I changed 4
     > to R and re-ran
     > and, so far, at least, everything is fine.  650 jobs have
     > run, so, I think
     > that if anything dangerous would have happened it would have
     > happened by
     > now.  It's just irritating.  I'm off to explore how to run a .jlt
     file
     > manually... maybe I could find an FM somewhere to R.
     >
     > I'll let you know how this finishes if you're interested...
     > Bambi.
     >
     > -----Original Message-----
     > Sent: Tuesday, January 29, 2002 1:15 PM
     > To: Multiple recipients of list ORACLE-L
     >
     > Bambi,
     >
     > I wouldn't touch *anything* under the hood as far as Apps
     > goes, esp. 11i.
     > Raise a TAR and let Oracle Support come back to you on this.
     > I assume that
     > you are testing the upgrade and not actually doing it. These
     > sort of things
     > should have been ironed out prior to the upgrade with lots of
     > iterations on
     > lots of clones. A 11i upgrade is NOT for the faint of heart.
     >
     > Sorry - but that's what I would recommend!
     >
     > John Kanagaraj
     > Oracle Applications DBA
     > DBSoft Inc
     > (W): 408-970-7002
     >
     > Fear is the darkroom where Evil develops your negatives.
     > Wanna break free of fear? Click on 'http://www.needhim.org'
     >
     > ** The opinions and statements above are entirely my own and
     > not those of my
     > employer or clients **
     >
     >
     > > -----Original Message-----
     > > From: Bellows, Bambi [mailto:[EMAIL PROTECTED]]
     > > Sent: Tuesday, January 29, 2002 10:21 AM
     > > To: Multiple recipients of list ORACLE-L
     > > Subject: adpatch question
     > >
     > >
     > >
     > > Hi Folks!
     > >
     > > I'm in the middle of an 11.5.5 upgrade.  Now, if you've done
     > > that type of
     > > thing before, you know those suckers just run forever, and if
     > > you leave it
     > > running overnight, you generally come in the next day to find
     > > that things
     > > failed overnight.  Well, that's where I was.  I left this
     > > sucker to run
     > > overnight, and, when I came in, sure enough, worker 4 had
     > > crapped out with a
     > > java error.  I checked metalink, and it said skip it, and
     > > when you're done
     > > with 1808429 (the 11.5.5 upgrade patch), just run
     > > asfakreg.jlt manually.
     > > Fine.  No big deal.  I went into adctrl and everything was in
     > > a wait state
     > > except for ol number 4 which crapped out.  I chose hidden
     > > option 8 (skip
     > > this thing) and the status changed to Skip & restart.  Great.
     > >  Except it
     > > didn't.  Evidently, having no response for X amount of time,
     > > all my workers
     > > stopped.  Again, no big deal, just re-run adpatch and let it
     > > start where it
     > > crapped out.  Well, now we run into a big deal, because it
     > > can't change the
     > > status from Skip & restart to anything that will allow
     > > adpatch to start
     > > again (like, maybe, failed where it was before I "fixed" it).
     > >
     > > I'm thinking of going under the sheets, finding the $%^&*
     > > table and updating
     > > the status myself.  Anyone have any reason why that's not
     > > such a great idea?
     > > Anyone have any other sneaky ways to change the status?
     > > Anyone have a list
     > > of the hidden options that Oracle doesn't tell you about
     > > (like ol number 8
     > > there?)?
     > >
     > > aTdHvAaNnKcSe!
     > > Bambi.
     > > --
     > > Please see the official ORACLE-L FAQ: http://www.orafaq.com
     > > --
     > > Author: Bellows, Bambi
     > >   INET: [EMAIL PROTECTED]
     > >
     > > Fat City Network Services    -- (858) 538-5051  FAX: (858)
     538-5051
     > > San Diego, California        -- Public Internet access /
     > Mailing Lists
     > >
     --------------------------------------------------------------------
     > > To REMOVE yourself from this mailing list, send an E-Mail message
     > > to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and
     in
     > > the message BODY, include a line containing: UNSUB ORACLE-L
     > > (or the name of mailing list you want to be removed from).  You
     may
     > > also send the HELP command for other information (like
     subscribing).
     > >
     > --
     > Please see the official ORACLE-L FAQ: http://www.orafaq.com
     > --
     > Author: John Kanagaraj
     >   INET: [EMAIL PROTECTED]
     >
     > Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
     > San Diego, California        -- Public Internet access / Mailing
     Lists
     > --------------------------------------------------------------------

     > To REMOVE yourself from this mailing list, send an E-Mail message
     > to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
     > the message BODY, include a line containing: UNSUB ORACLE-L
     > (or the name of mailing list you want to be removed from).  You may
     > also send the HELP command for other information (like subscribing).

     > --
     > Please see the official ORACLE-L FAQ: http://www.orafaq.com
     > --
     > Author: Bellows, Bambi
     >   INET: [EMAIL PROTECTED]
     >
     > Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
     > San Diego, California        -- Public Internet access / Mailing
     Lists
     > --------------------------------------------------------------------

     > To REMOVE yourself from this mailing list, send an E-Mail message
     > to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
     > the message BODY, include a line containing: UNSUB ORACLE-L
     > (or the name of mailing list you want to be removed from).  You may
     > also send the HELP command for other information (like subscribing).

     >




-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: 
  INET: [EMAIL PROTECTED]

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).

Reply via email to