Skip to Main Content

Database Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

impdp fails via database link

667901Jan 20 2009 — edited Jan 30 2013
Hi,

I am trying to import a particular schema from another instance into my instance over a database link using Data Pump.

Source instance: Solaris on Sparc 10.2.0.4.0 64bit
Target instance: Linux on x32, 10.2.0.4.0

I created a database link on the target database and verified that the link works, i.e. I could query tables in the remote database using the user which should receive the data.

I created a directory 'exp' on the target database and granted appropriate permissions to 'mh03'.

Then I tried the import and got an error:

-----

oracle@padsw7ora01 imp$ impdp mh03/*** NETWORK_LINK=padsol25 SCHEMAS=test_bas_bkrus_d123120 REMAP_SCHEMA=test_bas_bkrus_d123120:mh03 DIRECTORY=exp LOGFILE=imp.log

Import: Release 10.2.0.4.0 - Production on Tuesday, 20 January, 2009 14:47:30

Copyright (c) 2003, 2007, Oracle. All rights reserved.

Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORA-39006: internal error
ORA-39113: Unable to determine database version
ORA-02083: database name has illegal character '-'

ORA-39097: Data Pump job encountered unexpected error -2083

oracle@padsw7ora01 imp$

-----

I tried searching metalink and web but could not find any meaningful information. I tried to use parameter VERSION='10.2.0.4.0' but this did not help either (error message stays as is).

I found this which seemed slightly related:

ORA-39113: Unable to determine database version
Cause: The Data Pump was unable to determine the compatibility level and version of the current database using SYS.DBMS_UTILITY.DB_VERSION.
Action: Make sure access to the DBMS_UTILITY package is granted to you. If this is a network job, be sure that access to the DBMS_UTILITY package is granted to you on the remote instance.

But even doing "grant execute on SYS.DBMS_UTILITY to mh03" did not help at all.

I do realize though that the target database is set compatible to 10.2.0.3.0:

-----

1 declare
2 v varchar2(1000 char);
3 c varchar2(1000 char);
4 begin
5 DBMS_UTILITY.DB_VERSION(v,c);
6 dbms_output.put_line(v);
7 dbms_output.put_line(c);
8* end;
SQL> /

PL/SQL procedure successfully completed.

SQL> set serverout on
SQL> /
10.2.0.4.0
10.2.0.3.0

PL/SQL procedure successfully completed.

SQL>

-----

Any ideas what went wrong and how I can remedy this? Thanks a lot!

Kind regards

robert

Edited by: rklemme on Jan 20, 2009 6:16 AM
This post has been answered by 679289 on Jan 26 2009
Jump to Answer
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Feb 27 2013
Added on Jan 20 2009
8 comments
6,815 views