RE: Upgrade from 7.3.4 to 8.0.6 - Possible Solution - Comments?

[Deshpande, Kirti]

Title: Message

Chris,

 

 That column is added to the table when upgrading to 7.3.3 release, by cat7303.sql script. It is possible that this script was not run after opening the database under 7.3.3.

 

 If you are not using Replication, I don't think you need to run catrep8m script.  

 

 If you reviewed Note# 47290.1 on Metalink, you will find your answer :) 

 

 I don't think your action (adding this column to the dictionary table) was wrong.

 

 Good Luck,

 

- Kirti

 

 

-----Original Message-----
From: Bowes, Chris [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 21, 2003 3:21 PM
To: Multiple recipients of list ORACLE-L
Subject: RE: Upgrade from 7.3.4 to 8.0.6 - Possible Solution - Comments?

I found a way around the problem.  I don't think Oracle will like it...

 

I hunted down the offending table that was missing the column DELIVERY_ORDER and added it to that dictionary table.  I then re-ran the scripts and they rebuilt without incident.  This was on the test system of course.

 

The offending table was system.repcat$_repprop.  On all other databases, this table has that column and has no rows in it and on the problem base, it doesn't have the column, but it also has no rows in it.  I know that doesn't mean we aren't using that table, but, does anyone know when it gets used?  Is what I did to fix this acceptable?

 

Changing dictionary tables is a major red flag, so before I even think of trying to push for this solution, I want any and all thoughts on this.

 

Thanks again.

 

--Chris

 

 

 

-----Original Message-----
From: Bowes, Chris [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 21, 2003 10:19 AM
To: Multiple recipients of list ORACLE-L
Subject: RE: Upgrade from 7.3.4 to 8.0.6

Hi Hemant,

 

     Thank you for your response.  I am calling it directly.  I do the startup nomount, alter database convert, alter database open resetlogs.  Then I fire off the cat8000 and then the catrep8m from svrmgrl. 

 

I think this is a problem in my dictionary in 7.3.4 as when I recreate the test base and do an export/import and convert the base, it goes flawlessly.  This base has limited downtime available, so I cannot do that to the live base.

 

Oracle support has told me to look at offline datafiles, but this is in the system tablespace, so if that file was offline or needed recovery, the base would be dead.

 

Any thoughts?

 

Thank you again,

 

--Chris

 

-----Original Message-----
From: Hemant K Chitale [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 21, 2003 8:55 AM
To: Multiple recipients of list ORACLE-L
Subject: Re: Upgrade from 7.3.4 to 8.0.6

Are you calling the catrep8m script directly ?  Or is it being called
from some other script [eg catproc.sql ?].
Are you using Advanced Replication ?
Hemant
At 02:28 PM 20-01-03 -0800, you wrote:

Hi everyone!

     Has anyone seen this and know a solution?  I am upgrading a base from 7.3.4 to 8.0.6.  Everything appears to go fine until the catrep8m script.  In that script I get several errors:

Statement processed.
                        (P.delivery_order < C.cscn)))))
                           *
ORA-00904: invalid column name
grant select on defcalldest to select_catalog_role
                *
ORA-00942: table or view does not exist
comment on table DEFCALLDEST is
                 *
ORA-00942: table or view does not exist
comment on column DEFCALLDEST.CALLNO is
                  *
ORA-00942: table or view does not exist
comment on column DEFCALLDEST.DEFERRED_TRAN_ID is
                  *
ORA-00942: table or view does not exist
comment on column DEFCALLDEST.DBLINK is
                  *
ORA-00942: table or view does not exist
DROP PUBLIC SYNONYM defcalldest
                    *
ORA-01432: public synonym to be dropped does not exist
Statement processed.
                              OR (P.delivery_order < C.cscn))))
                                    *
ORA-00904: invalid column name
Statement processed.
Statement processed.
Statement processed.

This then forces several dictionary packages invalid and they wont' recompile.

I have tried rebuilding the dictionary before I upgrade and rebuilding after I upgrade.   Neither one seems to work.  When I rebuild, the catrep script gives that same error.

So far Oracle hasn't been able to find it.  Has anyone seen this and know the fix?

Thanks in advance.

--Chris
[EMAIL PROTECTED]

Hemant K Chitale
My web site page is :  http://hkchital.tripod.com