I wonder why the upgrade scripts were rebuilding the FET$, UET$ tables.
When you mention sql.bsq -- that applies only when you CREATE the database.
Did you CREATE and IMPORT to do the upgrade ?  IMPORT would certainly
be active on FET$ and UET$.

Hemant K Chitale
Principal DBA
Chartered Semiconductor Manufacturing Ltd


Dave Morgan <[EMAIL PROTECTED]>  23/01/2002 12:55 AM
Sent by: [EMAIL PROTECTED]

Please respond to ORACLE-L
                                                                                       
                        
             To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]>           
                        
             cc: (bcc: CHITALE Hemant Krishnarao/Prin DBA/CSM/ST Group)                
                        
             Subject: Re: multiple extents are OK, dagnabbit!                          
                        
                                                                                       
                        
                                                                                       
                        
                                                                                       
                        





Hi Jeremiah,
           The problem arose in the catalog upgrade script. It would never
return. My diary says we let one attempt run for 36 hours. The process
showed CPU usage and I/O but nothing happened. Some of the Oracle guys
figured the problem was with the $fet (or whatever tables hold the
extent
info, I never bother with  the internals of the data dictionary) having
problems while being restructured. Once the tables were changed from 40K
to 500M
extents the upgrade took less than 2 hours.

One of the suggestions I did not use was to edit sql.bsq to provide much
larger
extents for the table holding the extent info. Even though I do this for
the SOURCE$ table I am a big fan of the KISS principle and rebuilding
the tables
needed to be done anyways.

HTH
Dave


> Can you elaborate on exactly what happened?  8.1.5 to 8.1.6 is just a
> catalog script and a binary change.  What error did you encounter, and
> at which step in the upgrade?  Extents should not matter in an
> upgrade.

--
Dave Morgan
DBA, Cybersurf
Office: 403 777 2000 ext 284
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Dave Morgan
  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