Troubleshooting ora-12154

This content has been relocated to edstevensdba.wordpress.com

5 Comments


  1. // Reply

    Hi Ed,

    Good day.

    I’ve read your article entitled Troubleshooting ora-12154. It’s very informative.

    My problem with the ora-12154 error is a random one.

    I’m refreshing several materialized views (MV) and the source tables are on a separate database. The database link has been tested to work well; it uses an entry in the tnsnames.ora. The MVs are “refresh complete on demand” thru dbms_scheduler jobs that run every hour.

    The extractions run without problem every hour for 2-3 days and then suddenly, a few of the MV extractions will throw the ora-12154 error while others refresh without the same error. No changes done on the tnsnames.ora and sqlnet.ora files. All succeeding runs of these few MVs will have the same error until I issue the DBMS_SCHEDULER.RUN_JOB manually on each one, then the error goes away. It’s like the jobs cannot recover after they encounter the ora-12154 error and I have to run them manually to somehow give them a boost.

    DB: Cluster Database; v 10.2.0.4.0

    Any advise would be greatly appreciated. Thanks.


    1. // Reply

      At first glance this is very puzzling. You mentioned RAC. Is there any chance one particular node is referencing a different copy of tnsnames?


  2. // Reply

    Thank you very much ! This troubleshooting guide met its goal by helping me solve my connection issue.


Leave a Reply

Your email address will not be published. Required fields are marked *