Oracle dump import

If you are using the old imp method the users and tablespaces must be created first. This includes grants, database links and any advanced queues you may be using. A sample script could look like this in Windows imp a_DBA_user/apassword LOG =C:\dump\logs\import.log file =user01.dmp fromuser=user_name touser=user_name

The newer datapump method works wonderfully. You don't need to create the user but I would create any custom tablespaces you may have on the original.

A sample data pump call requires you to create a database link to the original database and a directory. This creates a directory

CREATE OR REPLACE DIRECTORY 
DATA_PUMP_DIR AS 
'C:\app\Oracle\product\11.2.0\dbhome_1\rdbms\log\';


GRANT READ, WRITE ON DIRECTORY DATA_PUMP_DIR TO EXP_FULL_DATABASE;

GRANT READ, WRITE ON DIRECTORY DATA_PUMP_DIR TO auser;

GRANT READ, WRITE ON DIRECTORY DATA_PUMP_DIR TO IMP_FULL_DATABASE;

In your script to import set these variables NLS_LANG

ORACLE_SID= your database name

impdp a_user_who_exists/your database name directory=DATA_PUMP_DIR network_link=original database name schemas= user1,user2 LOGFILE=DataPump.log TABLE_EXISTS_ACTION=REPLACE

You have to initiate the duplicate from the target database to be able to connect to the not mounted target database. I suggest you to downgrade the oracle version on the 64 bit machine. The easiest way to do this will be to install 11.1.0.6.0 version on the 64-bit server into a separate oracle home and perform the duplicate. You can upgrade the database after duplicate and switch it to the 11.1.0.7.0 home.

The error you are getting on the 32-bit database seems to be a connection problem to the database. The target instance is not mounted and you cannot connect to is via SQLnet.

When performing the duplicate form 64 bit system, please make sure that you are using username/password in the connection string to the target database and not the system authentication.

Best regards, Yuri