e-Business Suite and the ODA - Practical Oracle Database Appliance - page 210

Connect to each of the database instances and change the local_listener and
remote_listener database initialization parameters. Note the local_listener parameter
requires different values on each node. For example:

11.

# on the 1st node
[oracle@s1 ~]$ sqlplus / as sysdba
SQL> alter system set remote_listener='PROD_REMOTE' sid='PROD1';
System altered.
SQL> alter system set local_listener='PROD1_LOCAL' sid='PROD1';
System altered.
SQL> exit

# on the 2nd node
[oracle@s2 ~]$ sqlplus / as sysdba
SQL> alter system set remote_listener='PROD_REMOTE' sid='PROD2';
System altered.
SQL> alter system set local_listener='PROD2_LOCAL' sid='PROD2';
System altered.
SQL> exit

12. Source the new environment files and run AutoConfig on each node:

[oracle@s1 ~]$ . $ORACLE_HOME/$CONTEXT_NAME.env
[oracle@s1 ~]$ cd $ORACLE_HOME/appsutil/scripts/$CONTEXT_NAME
[oracle@s1 PROD1_s1]$ ./adautocfg.sh
Enter the APPS user password:
...
AutoConfig completed successfully.

13. The last step, which concludes the configuration of the e-Business Suite database in RAC,

is adding an e-Business Specific ORA_NLS10 environment variable to the CRS service of the
database. Execute the following command on any of the database servers:

[oracle@s1 ~]$ srvctl setenv database -d PROD -t "TNS_ADMIN=$ORACLE_HOME/network/
admin,ORA_NLS10=$ORACLE_HOME/nls/data/9idata"

Additionally, it's important to know that AutoConfig on the database nodes sets the tcp.
validnode_checking=yes , and tcp.invited_nodes lists only the physical and virtual
IPs of the database nodes in the sqlnet.ora file. This means the listener will accept new
connections from the database nodes only. As you'll need to connect to the database from
two application servers, too additional nodes need to be added to the tcp.invited_nodes
by overriding that parameter in the custom include file sqlnet_ifile.ora , as shown next.
(If you prefer disabling the tcp.validnode_checking completely, the best way of doing so
is changing the e-Business Suite profile option “SQLNet Access” to ALLOW_ALL, and then
re-running AutoConfig on the database nodes).

14.

[oracle@s1 ~]$ echo "tcp.invited_nodes=(s1, s2, s1-vip, s2-vip, oevm1, oevm2)" >
$TNS_ADMIN/sqlnet_ifile.ora