DBAsupport.com Forums - Powered by vBulletin
Results 1 to 5 of 5

Thread: dblink create error

  1. #1
    Join Date
    Feb 2007
    Posts
    212

    dblink create error

    Hi Friends,

    I run a script creating a database link which was an output of the replication
    deployment template, meaning the OEM utils created the script itself. But
    I got the following error:
    =========================================================
    SQL> CREATE PUBLIC DATABASE LINK "ORCL.REGRESS.RDBMS.DEV.US.ORACLE.COM" USING '(DESCRIPTION=(ADDRESS
    =(PROTOCOL=TCP)(HOST=172.15.0.14)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=orcl)))'
    2 ;
    CREATE PUBLIC DATABASE LINK "ORCL.REGRESS.RDBMS.DEV.US.ORACLE.COM" USING '(DESCRIPTION=(ADDRESS=(PRO
    *
    ERROR at line 1:
    ORA-02082: a loopback database link must have a connection qualifier
    =========================================================

    The '*' here is pointing to the word "USING". What qualifier could it possibly
    looking for? What do u mean by loopback dblink?

    Thanks a lot

  2. #2
    Join Date
    Mar 2007
    Location
    Ft. Lauderdale, FL
    Posts
    3,555
    ddzpy031/ddzpy031-3 [3]: oerr ORA 2082
    02082, 00000, "a loopback database link must have a connection qualifier"
    // *Cause: attempt to create a database link with the same name as the
    // current database.
    // *Action: a loopback database link needs a trailing qualifier, e.g.
    // MYDB.DEV.US.ORACLE.COM@INST1 - the '@INST1' is the qualifier
    //
    Pablo (Paul) Berzukov

    Author of Understanding Database Administration available at amazon and other bookstores.

    Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.

  3. #3
    Join Date
    Feb 2007
    Posts
    212
    thanks dear

  4. #4
    Join Date
    Mar 2007
    Location
    Ft. Lauderdale, FL
    Posts
    3,555
    Glad to help.

    By the way, very bad practice to fully qualify target instance in DBLink statement, you might want to point to a TNSNAMES entry.
    Pablo (Paul) Berzukov

    Author of Understanding Database Administration available at amazon and other bookstores.

    Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.

  5. #5
    Join Date
    Feb 2007
    Posts
    212
    Thanks honey,

    I am setting-up/configuring a materialized view replication using OEM.
    I'm not the one creating the scripts but OEM, and I intend
    to run it at the materialized view site (172.16.1.21) while the master site
    is (172.15.0.14) , I dont understand while the OEM is running it at the master
    site hence, this error.

    By the way, my two replication database have the same db name "ORCL" :(
    Could this be the cause of the error? I dont thinks so bacause they reside
    on SEPARATE servers of course.

    How do I rename my other database to "ORCL2"
    Last edited by jennifer2007; 05-07-2007 at 07:57 PM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


Click Here to Expand Forum to Full Width