ORA error TNS-12547: TNS:lost contact
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 8 of 8

Thread: ORA error TNS-12547: TNS:lost contact

  1. #1
    Join Date
    Nov 2008
    Posts
    2

    ORA error TNS-12547: TNS:lost contact

    after i patch upgrade from 10.2.0.1 to 10.2.0.4 i get this error when connecting to sqlplus

  2. #2
    Join Date
    Mar 2006
    Location
    Charlotte, NC
    Posts
    865
    is the tnsnames.ora file located in the directory where it is suppose to be in 10.2.0.4?

    Thanks,
    Vijay Tummala

    Try hard to get what you like OR you will be forced to like what you get.

  3. #3
    Join Date
    Nov 2008
    Posts
    2

    yes

    ORACLE_HOME/network/admin

  4. #4
    Join Date
    Mar 2006
    Location
    Charlotte, NC
    Posts
    865
    there is other post running since last few days with title "connection problem to database instance" by midora for the same error. Please read the whole post and see if you are missing any thing in configuration.

    Thanks,
    Vijay Tummala

    Try hard to get what you like OR you will be forced to like what you get.

  5. #5
    Join Date
    Nov 2008
    Posts
    11
    maybe you tnsnames.ora is crashed. you use move and copy the tnsnames.ora for test it health .

  6. #6
    Join Date
    Nov 2008
    Posts
    2
    In case really! tnsnames.ora file was crashed. If u Know Host or IP address andPort and SID then You can create a new tnsnames.ora file with Host name or IP address and SID and port are mandatory information. Your problem will resolved. Good Luck

  7. #7
    Join Date
    Nov 2008
    Posts
    9
    Quote Originally Posted by pstarr3
    after i patch upgrade from 10.2.0.1 to 10.2.0.4 i get this error when connecting to sqlplus
    i think that the things is not simple.
    1, you patch your database in host server and local pl/sql connection does not require tnsname.ora file. but remote connection need it.
    2, i suppose that you should check your listener information. in one case i have met the err, because the size of listener.log had reached 2GB on Linux system.
    Last edited by sqlany; 11-27-2008 at 09:44 AM.

  8. #8
    Join Date
    Oct 2006
    Posts
    175
    2G of listener.log! Need to check that. Also may be your new database is not registered to this listener, run lsnrctl, if it doesn't show any database registered to it, trying create new listener using netmgr and restart database. It should help.

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