Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.server -> Re: EXP-00056: ORACLE error 1403 encountered HELP PLEASE
Sybrand Bakker wrote:
> Answers embedded
>
> On Fri, 02 Apr 2004 17:28:35 GMT, Hans Forbrich <forbrich_at_yahoo.net>
> wrote:
>
>>Since it happens (for the OP) at the Cluster section, I'd suggest checking >>whether there are any clusters. If not, there is probably not a problem >>(just another example of deteriorating QA tests cases). I hear your >>comment already & agree - it still needs to be verified. >> >>> 2 In my case: 9.2.0.3 database server here and 9.0.1 client >> >>Intrigued by the 9.0.1 client part. Are you saying you are using a 9.0.1 >>client for the connection betw. exp and server? Or a 9.0.1 exp client?
Let's see if I understand this ......
You have a couple of 9.2.0.3 'live' instances and a 9.0.1.x 'infrastructure' instance ('cause that's the only version of infra database instance allowed). Which should be in separate ORACLE_HOMEs and are hopefully full, and not customized (bastardized), installs, therefore providing two versions of the exp command.
Probably on a Wintel box ('cause of the McAfee/Norton AV statement).
Don't quite get this part - you have a separate 9.0.1 client, or the 9.0.1 client from the Infrastruture is taking precedence?
And, knowing your skill set, you've checked the connectivity to the 9.2.0.3 using both the 9.0.1 and and the 9.2.0.3 SQLPlus executables - which of course, in Windows, implies the correct ORACLE_HOME since the selecting the binary with a full OH/bin path automatically decides the OH.
And there are no clusters. (Except, of course, SYS owns at least 6 cluster objs such as C_COBJ#, C_OBJ#, C_TS# ... )
And the ORA-1403 and EXP-00056 are happening consistently from both the 9.2 and 9.0 exp executables?
And (you could not know this) my full exp of a 9.2.0.1 test database, using both a 9.0.1.3 and 9.2.0.1 exp executables, cleanly passes the cluster def'n export both times.
Then I'd guess you either have corrupt executables (unlikely) or a corrupt catalog.
But that's just a guess.
/Hans
Received on Fri Apr 02 2004 - 14:02:06 CST
![]() |
![]() |