Joords Oracle DBA blog

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.

A recurring question during Grid Infrastructure and RAC courses I teach is “How do you manage Oracle password files in a clustered environment?”. The answer isn’t as straight forward as you might think because there are significant differences between ASM and RAC (==clustered database) environments. Additionally, in recent releases changes were made concerning password file [ ...Original article... ] A Posted by Harald van Breederode on January 14, 2011 Summary Password file maintenance on Clustered ASM and RAC databases For ASM releases prior to 11gR2 password files should either be placed on a shared filesystem (and symlinked from  $ORACLE_HOME/dbs ) or password file changes should be performed manually on all instances in order to keep the password file contents synchronized on all nodes. For ASM releases from 11gR2 onwards there is no need to place the password files on a shared filesystem because password file changes are automatically propagated to remote instances. Fo...