Modify the DB Connection String of an LFC Host

Pre-requisites

First you need these five things:

• <Intervention> Schedule an intervention in advance. Contact the GMOD for this.
• <lfcNSCONFIG> The last version in SINDES of the lfcNSCONFIG.tar.gz file. Contact FIO for this.
• <lxadm> Access to lxadm cluster. Ask someone with CDB access.
• <SINDES> Access to SINDES. Ask someone with CDB access.
• <DB support> You may need support from DB group to change the DB password.

Steps to Perform the Change

Update the lfcNSCONFIG file in SINDES

• Connect to an lxadm machine.
• Untar the lfcNSCONFIG.tar.gz and modify the passwordfile which is inside with the new string.
• Build again the lfcNSCONFIG.tar.gz file and upload it to SINDES typing:

sindes-upload-file  -f lfcNSCONFIG.tar.gz -i lfcNSCONFIG --target gridlfc -S sindes-server -s cluster

Update first one of the two nodes which are behind the alias

• Get the name of the 2 machines which are behind the alias:

host prod-lfc-atlas-central

host ip_number_1

host ip_number_2

• Set the first one into maintenance:

sms set maintenance other "to change Oracle connection string" lfcxxx

• Update the lfcNSCONFIG package via Sindes:

wassh root@lfcxxx ncm_wrapper.sh sindes

Change the password of the DB account

• Try to connect to the Oracle DB account with the old password and update it by yourself:

sqlplus account_name/my_old_pwd@db_name

SQL> alter user my_user_name identified by my_old_pwd REPLACE my_new_pwd;

• If the step above failed, you should ask the DB group to expire the pwd of this account or change the pwd for you.
• If they make it expire, just trying to login again with the old pwd, you will be forced to enter a new one.

Restart the LFC in the maintenance node and put it back to production

• Go back to lxadm and restart the LFC:

wassh root@lfcxxx service lfcdaemon status

wassh root@lfcxxx service lfc-dli status

wassh root@lfcxxx service lfc-dli stop

wassh root@lfcxxx service lfcdaemon stop

wassh root@lfcxxx service lfcdaemon start

wassh root@lfcxxx service lfc-dli start

• Check if the daemons are running with the new DB string:

wassh root@lfcxxx service lfcdaemon status

wassh root@lfcxxx service lfc-dli status

• Put the node back in production:

sms set production other "after changing Oracle connection string" lfcxxx

Do the same for the second node

• Put it in maintenance as explained above.
• Update the lfcNSCONFIG package via Sindes as explained above.
• Restart the LFC daemons as explained in the last point.
• If the daemons are running fine, put this node back to production.

-- Main.dcollado - 14 Dec 2006