Skip to main content

EXPDP/IMPDP Export/Import dumpfile to a Remote Server Using Network_Link.

EXPDP/IMPDP Export/Import dumpfile to a Remote Server Using Network_Link.


Step 1: First you have to create a TNS entry at destination database which will be used to connect to the remote target database.

pumplink =
  (DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = TCP)(HOST = 172.17.1.171)(PORT = 1521))
    )
    (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SERVICE_NAME = Ultimus)
    )
  )


Step 2: Connect to SQL plus:


--Issue the following command to create db link on destination database:


CREATE PUBLIC DATABASE LINK pumplink
   connect to scott identified by tiger USING 'pumplink';

Step 3: Issue the expdp command on the destination server using Network_link parameter:

expdp scott/tiger directory= dumpdir logfile=impi_temp.log network_link= pumplink  schemas=scott dumpfile=testnetlink.dmp

impdp  scott /tiger directory=dumpdir logfile= impi_temp.log network_link=pumplink schemas= scott  dumpfile=testnetlink.dmp

**In this case the "SCOTT"."SYS_IMPORT_SCHEMA_01" meta table is created in the local DB's importing schema not on the remote schema.

---------------------------------------------------------------------------------------------------
Heppy to Help !!!


Labels:

Comments

  1. stormAugust 2, 2012 at 11:56 AM

    On exporting using network link in the remote server, where will be the server process for expdp will be started. Whether the expdp server process will be started in source database server or remote database server?

    ReplyDelete
  2. ZakirAugust 2, 2012 at 12:08 PM

    It will be created on local server as the expdp or impdp command is issued from local server.

    thanks for asking.

    ReplyDelete
  3. AlexandreAugust 2, 2012 at 6:32 PM

    Thank you for this blog entry.
    However, I get a

    Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
    With the Partitioning and Data Mining options
    UDI-00011: parameter dumpfile is incompatible with parameter network_link

    How do you manage to use both?

    ReplyDelete
  4. AnonymousDecember 5, 2012 at 7:46 PM

    Just, thank you !

    ReplyDelete
  5. AnonymousMay 23, 2013 at 5:48 PM

    why it is not working in remote workstation ?

    ReplyDelete

Post a Comment

Popular posts from this blog

ORACLE FLASH RECOVERY AREA USAGE QUERY

FINDING ORACLE FLASH RECOVERY AREA USAGE SELECT NAME,        (SPACE_LIMIT / 1024 / 1024 / 1024) SPACE_LIMIT_GB,          ((SPACE_LIMIT - SPACE_USED + SPACE_RECLAIMABLE) / 1024 / 1024 / 1024) AS SPACE_AVAILABLE_GB,        ROUND((SPACE_USED - SPACE_RECLAIMABLE) / SPACE_LIMIT * 100, 1) AS PERCENT_FULL   FROM V$RECOVERY_FILE_DEST;
Post a Comment
Read more

Shared Pool Tuning: Cursor Tuning (Tuning Open_Cursors, Session_Cached_Cursors, Cursor_Space_For_Time)

Shared Pool Tuning: Cursor Tuning The three most important parameter for shared pool tuning are OPEN_CURSORS , SESSION_CACHED_CURSORS and CURSOR_SPACE_FOR_TIME. But most of the time we see that these two parameters SESSION_CACHED_CURSORS and CURSOR_SPACE_FOR_TIME are ignored or unused . OPEN CURSORS Open cursors take up space in the shared pool, in the library cache. OPEN_CURSORS sets the maximum number of cursors each session can have open, per session. For example, if OPEN_CURSORS is set to 1000, then each session can have up to 1000 cursors open at one time. V$open_cursor shows cached cursors, not currently open cursors, by session. If you’re wondering how many cursors a session has open, don’t look in v$open_cursor. It shows the cursors in the session cursor cache for each session, not cursors that are actually open.  To monitor open cursors, query v$sesstat where name= ’opened cursors current’ . This will give the number of currently opened cursors, by session:
Post a Comment
Read more

How to delete/remove Management Agent from Oracle Enterprise Manager 12C

  1. Before you deinstall a Management Agent, do the following:     a. Stop the Agent using command from Management Agent home:                 cd /u01/oemcc_latest/core/12.1.0.2.0/bin/                 $ emctl stop agent     b. Wait for the Management Agent to go to the unreachable state in the Cloud Control console.     c. It is mandatory to delete the Management Agent and their monitored targets using any of the following methods: Remove the Agent target manually from the console: 1. Login to 12C Cloud Control 2. Navigate to Setup => Manage Cloud Control => Agents 3. Go to the Home page of the Agent that you want to remove 4. Expand the drop-down menu near the " Agent " 5. Expand the " Target Setup " option 6. Select " Remove Target "            In Cloud Control Release 12.1.0.2, the following dialog box will be displayed if the Agent is still monitoring targets. Click Continue. You can then remove all targets (usin
Post a Comment
Read more