Central TNSNAMES.ORA inside RAC using TNS_ADMIN [PRKP-1001 and CRS-0215 errors]

Is it possible to use a central tnsnames.ora on a shared file systems insite a Real Application Server. The answer to the question is YES. If the centralized tnsnames.ora is not correctly setup, it will produce the following errors [PRKP-1001 and CRS-0215 errors] at startup of the database or instance with SRVCTL. When using SQLPLUS to startup the database instance everything works as designed. Why SRVCTL is not working correctly is that, the TNS_ADMIN is not register into the Oracle Cluster Registry for the current database and instances.

The following steps in this blog will explain to you how you can solved the [PRKP-1001 and CRS-0215 errors] at startup of a database or instances by using SRVCTL statement with a centralized tnsnames.ora.

tnsManager acts as a simple LDAP compliant server to serve just TNS information

tnsManager is a more robust alternative to using file shares or SMS for centralized tnsnames distribution and management.A perfect tool for centralization of the TNSNAMES.ORA

Simply place tnsManager into a directory with a tnsnames.ora and it will serve it to your client workstations using LDAP. No additional workstation software is required, and best of all it's completely free!

tnsManager is basically a very compact and focussed LDAP server; in fact all it has been designed to do is serve tnsnames - nothing else. Because of this, it requires very few system resources and it is extremely simple to configure - it usually takes less than 10 minutes to install!