Results 1 to 7 of 7
  1. #1
    Join Date
    Sep 2007
    Posts
    3

    Unanswered: Issue with Database Links after migration

    So, we have an application that uses database links. Once we migrated to a new server using 10g, we started having issues.

    On both the remote server and the local server, global_names is set to false.

    Before the migration database links were named things such as AA.WORLD. When they were queried, the .WORLD wasn't part of the statement (select * from sometable@AA) This worked successfully.

    Now, these select statements do not work unless the .WORLD is included in the database link name. (select * from sometable@AA.WORLD).

    I then created a "AA" database link and this works with the original code. (select * from sometable@AA)

    I am very much a novice, so please excuse me if I left out any necessary info or this doesn't make sense.

    What could have changed?

    I encounter these issues when I test from my machine. My sqlnet.ora has DEFUALT_DOMAIN = WORLD and my TNS Names file is current.

  2. #2
    Join Date
    Aug 2003
    Location
    Where the Surf Meets the Turf @Del Mar, CA
    Posts
    7,776
    Provided Answers: 1
    >I encounter these issues when I test from my machine. My sqlnet.ora has DEFUALT_DOMAIN = WORLD
    So remove that line from sqlnet.ora & the problem will go away.
    You can lead some folks to knowledge, but you can not make them think.
    The average person thinks he's above average!
    For most folks, they don't know, what they don't know.
    Good judgement comes from experience. Experience comes from bad judgement.

  3. #3
    Join Date
    Sep 2007
    Posts
    3
    That isn't the issue. I have been told this is what needs to be in the file and when I removed it, it didn't resolve the issue.

  4. #4
    Join Date
    Aug 2003
    Location
    Where the Surf Meets the Turf @Del Mar, CA
    Posts
    7,776
    Provided Answers: 1
    post the contents from $ORACLE_HOME/network/admin of both sqlnet.ora & tnsnames.ora from the new database server system.
    You can lead some folks to knowledge, but you can not make them think.
    The average person thinks he's above average!
    For most folks, they don't know, what they don't know.
    Good judgement comes from experience. Experience comes from bad judgement.

  5. #5
    Join Date
    Sep 2007
    Posts
    3
    I would prefer not to - I checked our global copy of those files and they match the files I am using. I will check with someone about this. Thanks for your help.

  6. #6
    Join Date
    Jun 2004
    Location
    Liverpool, NY USA
    Posts
    2,509
    When we migrated from Oracle 8i directly to Oracle 10G using export and import, we noticed that the restored database links failed until we dropped them and rebuilt them. AFter the rebuild, they worked fine.
    Bill
    You do not need a parachute to skydive. You only need a parachute to skydive twice.

  7. #7
    Join Date
    Sep 2007
    Posts
    2
    The DB_LINK name is resolved using the TNSNAMES file on the DB SERVER.

    Here is your solution:

    GLOBAL_NAME

    Select * FROM GLOBAL_NAME;

    Its probably something like DEV.US.ORACLE.COM

    So when you create a database link you get

    DB_LINK.US.ORACLE.COM (or something similar)

    Do you still have your old db up?

    Select * from global_name on your old database to see what it was set to.

    Then run:

    UPDATE GLOBAL_NAME
    SET GLOBAL_NAME = 'the name you want';

    You may need to recreate your db links because they may have gotten created incorrectly. If the db_links are identical in the old db, then updating global_name should be good enough.

Posting Permissions

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