I manage an application that uses an Oracle DB. That DB resides on a host
running 8.1.7.3 on HP-UX 11.00. Since I don't have access to that system
and I am not confident that it is being backed up reliably, I have been
doing a nightly export from another system, run from a cron (my local Oracle
server). That has been working fine for some time.

Yesterday I upgraded my local server to 8.1.7.4. Now I can longer do a full
export. I get this error

.. exporting sequence numbers
EXP-00008: ORACLE error 904 encountered
ORA-00904: invalid column name
EXP-00000: Export terminated unsuccessfully

It seems to work OK until it begins exporting the sequence numbers. I was
able to confirm that a "exp full=yes" can be done successfully on the
8.1.7.3 system. What is the cause of this and what, if anything, can I do
to correct it?

Randy Harris wrote:
Do ya thunk it's possible that a 8.1.7.4 export executable might not be
compatible with a 8.1.7.3 export dictionary? What's metalink/support
say? (or perhaps the upgrade docco that comes with the upgraded s/w?)

One possibility - install a baseline 8.1.7.3 (no need to install a
database -just the s/w) in a separate Oracle Home on your local
machine. Use that instead of the new s/w to continue your exports.

A second possibility - shake some trees to ensure the backups on the HP
are done properly so you don't end up being responsible for things you
really can't control. (What happens when 'they' upgrade the HP-UX?)

A third - there's a reason for upgrading to 8.1.7.4 .... have the DB on
the HP-UX machine upgraded.

A fourth - get all the databases moved up to 9i

A fifth - investigate RMAN for backup.

(etc., etc., etc.)
--
/Hans
[mailto:`echo $from" | sed "s/yahoo/telusplanet/g"`]

Randy Harris wrote:


SELECT object_name
FROM dba_objects
WHERE status = 'INVALID';

I expect you'll find some. Then check the log file from the upgrade.
Then repeat the upgrade.

Make sure you perform any STARTUP MIGRATE or other recommendations that
are in the documentation
and be sure to run utlrp.sql in the /rdbms/admin directory.

--
Daniel Morgan
http://www.outreach.washington.edu/e...ad/oad_crs.asp
http://www.outreach.washington.edu/e...oa/aoa_crs.asp
damorgan@x.washington.edu
(replace 'x' with a 'u' to reply)

"Daniel Morgan" <damorgan@x.washington.edu> wrote

Oh boy, did I ever. 48 objects with status = 'INVALID' (all owned by SYS).
I don't think that can be a good thing. There was no upgrade of the
database, it was originally created with 8.1.7.3 and still is. When I
encountered the problem was attempting to do an export from a client running
8.1.7.4. It might be a matter of the 8.1.7.4 export utility simply not
being compatible with the 8.1.7.3 database (as suggested by Mr. Forbrich).
So far, I can't find any documentation indicating one way or the other.

I've already submitted a request to have the server and the database
upgraded to 8.1.7.4. Aside from that, can you suggest what steps I should
take to address this problem?

"Hans Forbrich" <forbrich (AT) yahoo (DOT) net> wrote

I'm beginning to think this is likely. So far, however, I've been unable to
fiind anything in the documentation to suggest one way or the other.

I'm sure you've heard sad stories before. This system used to host our SAP
server. We got merged with another company, SAP got moved from our
headquarters to theirs. Both our DBAs left. The system is now "managed" by
systems people with little Oracle knowledge.

I understand why this is important. I've already submitted a request to
have that done. (or let me do it).

At your suggestion, I've begun learning about RMAN. I suspect a visit to
the bookstore is in order.

Thanks for your input.

On Sat, 11 Oct 2003 20:27:40 GMT, "Randy Harris" <randy (AT) SpamFree (DOT) com>
wrote:


The usual issue of not running
catalog.sql
catproc.sql
----> catexp.sql
after every upgrade
though these steps are documented.


--
Sybrand Bakker, Senior Oracle DBA

"Sybrand Bakker" <gooiditweg (AT) sybrandb (DOT) demon.nl> wrote

Please correct me if I'm wrong. I thought those would only be run after
upgrading a databse? I ran them on all of my local databases (after
upgrading the server to 8.1.7.4), but the databse I'm having a problem with
is still at 8.1.7.3.