Avinash C. Pillai

In order to facilitate manual failover below are the steps a sys admin should take when failing over the filesystems from one node to another when we have an LVM configured. NOTE: NODE02 uses ifcfg-eth5:0 for the listener VIP and NODE01 uses ifcfg-eth4:0 for the VIP. Please start these respectively. On NODE02 1. Ensure the DB, DB listeners and the VIP has been stopped on the active node. · Stop Oracle DB · Stop Oracle Listener · Stop the VIP Pointing to this DB Instance ( i.e. eth5:0) # Ifdown eth5:0 2. Unmount all mount points related to PDB: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> /dev/mapper/vg--oradata-lv.pdb01 40G 8.3G 30G 23% /pdb01 /dev/mapper/vg--oradata-lv.pdb02 493G 147G 321G 32% /pdb02/dev/mapper/vg--oradata-lv.pdb03 493G 133G 335G 29% /pdb03/dev/mapper/vg--oradata-lv.pdb_arch 197G 84G 104G 45% /pd

Problem : Unable to connect to Oracle DB from a Windows box, getting Oracle driver error while executing a perlscript. Resolution: By default windows OS don’t come with Oracle ODBC drivers hence Windows OS couldn’t get an ODBC connection to the Oracle DB. Hence we need to install Oracle client on the Windows box which puts the Oracle ODBC driver and this helps to get a connection established from the Windows Server to the Oracle DB. Picture below shows the Oracle driver on Windows box after Oracle 11g clinet installed. • You should ensure that you have the correct entries in tnsnames.ora on the Windows box for the Oracle DB. Thanks & Regards Avinash Pillai http://avinashpillai.blogspot.com/