Export Errors

Printable View

09-20-2002, 04:49 AM
sabita_ban

Hi All,

I have an Oracle 7.3.4 server from where I am trying to export an user as follows.

C:\>exp73 orgsmgr/orgsmgr file=DB_USER.DMP compress=no grants=yes owner=orgsmgr
file=DBUSER.DMP log=DBUSER.log

But while doing so I am getting EXP-00008 and ORA-01003 for all the objects.

What can be the possible reason??
Can any one throw some light on this.
09-20-2002, 05:23 AM
ggnanaraj

Quote:

Originally posted by sabita_ban

C:\>exp73 orgsmgr/orgsmgr file=DB_USER.DMP compress=no grants=yes owner=orgsmgr
file=DBUSER.DMP log=DBUSER.log

You are using 'file=' twice in your command line ? ?

Check that out.
09-20-2002, 05:28 AM
sabita_ban

I have Rectified this..thanks
But even then getting the same problem
09-20-2002, 05:34 AM
denevge

are you sure you are using the correct executable ?

Did you ever run the catexp script ?

Normally this error appears when we run an exp-executable against a rdbms that's not the same version as the exp.
metalink note : 106155.1

Hope this helps
Gert
09-20-2002, 05:35 AM
denevge

you can also take a look at metalink not : Note:175624.1
a FAQ on export-import

Gert
09-20-2002, 05:50 AM
sabita_ban

Thanks all of you,

Running catexp.sql did the trick...
Now no errors encountered during Export

Can some one elaborate as to what for is this script actually required.

I found out that this script
creates the necessary export views,
assigns all necessary privileges to the EXP_FULL_DATABASE role,assigns EXP_FULL_DATABASE to the DBA role

But what has this to do with ORA-01003 error?? Which says

ORA-01003 no statement parsed

Copyright (C) 1995, Oracle Corporation
A host language program call referenced a cursor with no associated parsed SQL statement. A SQL call (for example, OSQL3) must be used to pass a SQL statement to Oracle and to associate the statement with an open cursor. A cursor must already have an associated SQL statement if referenced in any of the following calls: DESCRIBE, NAME, DEFINE, BIND, EXECUTE,and FETCH.

Copyright (C) 1995, Oracle Corporation

Thanks in advance
Sabitabrata
09-20-2002, 01:46 PM
nagarjuna

Export utility uses few views and procedures. Without having them how can Oracle do the process?? So, we have to create them. That's what you did by running catexp.sql.
09-20-2002, 02:15 PM
Shestakov

I saw problem like this. Probably this bug in exp/imp parser.

sitation was following:

if in CREATE TABLE statment was line -->
abc date default SYSDATE ,
bcd ... )
or
usr varchar2(30) default user ,
aaa ... )
all was OK

but if was:

abc date default SYSDATE )
or
usr varchar2(30) default user )

export utility issued error ORA-01003 .
different was only ) or , has been wrote after .. DEFAULT + function name without ().

Check does any table has text like this.