Oracle Database 11 g - Online Public Access Catalog

294 CHAPTER 6 ■ BACKUP AND RECOVERY1. To make sure the source database can connect to the auxiliary instance by means of anet service name, you must make the net service name available on the source databaseinstance. Add the auxiliary instance, which we named test1, to the listener.ora file onthe server hosting the source database, as shown here (you must also restart or reloadthe listener after this):SID_LIST_LISTENER =(SID_DESC =(GLOBAL_DBNAME = prod1)(ORACLE_HOME = /u01/app/oracle/product/10g/)(SID_NAME =prod1))(SID_DESC =(GLOBAL_DBNAME = test1)(ORACLE_HOME = /u01/app/oracle/product/10g/)(SID_NAME =test1)))Also add the following information to the tnsnames.ora file, located in the $ORACLE_HOME/network/admin directory.test1 =(DESCRIPTION =(ADDRESS_LIST =(ADDRESS = (PROTOCOL = TCP)(HOST = prod1)(PORT = 1521)))(CONNECT_DATA =(SERVER = DEDICATED)(SERVICE_NAME = test1)))The tnsnames.ora entry shown here maps the net service name test1 to the connectdescriptor for a database named test1.2. The next step is to create an initialization parameter file for the auxiliary instance. Sincewe’re using the more straightforward spfile technique for naming the duplicate files, wecan get by with a minimum of just a single parameter (db_name) in the spfile to denotethe name of the duplicate database. We’ll set the values for the initialization parametersdb_file_name_convert and log_file_name_convert directly in the duplicate databasecommand itself, rather than in the spfile. The simple spfile for our auxiliary instancewould then look like this:db_name=test1If you didn’t use the spfile technique for naming the duplicate database files, you’d havehad to set parameters such as db_file_name_convert and log_file_name_convert inyour initialization parameter file.