If running catexp.sql did not fix the problem, then I think that catalog.sql
won't either. I think that (and somebody correct me if I'm wrong) the
reason people sometimes run catalog.sql to fix this problem is that it in
turn calls catexp.sql. In principle, re-running catalog.sql shouldn't harm
your database - but you want to make sure you run the version that matches
your database!
Does the version of exp that you are using match the version of your
database?
--
Cheers,
Chris
___________________________________
Chris Leonard, The Database Guy
http://www.databaseguy.com
Brainbench MVP for Oracle Admin
http://www.brainbench.com
MCSE, MCDBA, OCP, CIW
___________________________________
"Anders" <ahansen1_at_yahoo.com> wrote in message
news:776f5b3c.0407210541.38c5bb49_at_posting.google.com...
> I am by no means a DBA so forgive me if this is a simple question. I
> am attempting to run an export against my Oracle database. When doing
> so I get the following:
>
> Connected to: Oracle9i Enterprise Edition Release 9.2.0.4.0 -
> Production
> With the Partitioning, OLAP and Oracle Data Mining options
> JServer Release 9.2.0.4.0 - Production
> Export done in WE8ISO8859P1 character set and AL16UTF16 NCHAR
> character set
> server uses WE8MSWIN1252 character set (possible charset conversion)
> Note: grants on tables/views/sequences/roles will not be exported
>
> About to export specified users ...
> . exporting pre-schema procedural objects and actions
> . exporting foreign function library names for user GDTMN_MNBUILD
> . exporting PUBLIC type synonyms
> . exporting private type synonyms
> . exporting object type definitions for user GDTMN_MNBUILD
> EXP-00008: ORACLE error 942 encountered
> ORA-00942: table or view does not exist
> EXP-00024: Export views not installed, please notify your DBA
> EXP-00000: Export terminated unsuccessfully
>
> Looking through the newsgroups I have found that catexp.sql needs to
> be run in order to enable export. So, I ran this file as SYSDBA,
> however my export is still not working. I then found some indication
> that catalog.sql may need to be ran again? I just wanted to make sure
> that this made sense and check that running catalog.sql would not "in
> theory" affect my existing data in the database. Any advice is
> greatly appreciated. Thanks!
Received on Fri Jul 30 2004 - 13:07:51 CDT
