252 IBM Power Systems 775 for AIX and Linux HPC SolutionIf the ODBC setup is correct and the connection to SQL is successful, the command returnsthe output that is shown in Example 4-11.Example 4-11 ODBC correct setup+---------------------------------------+| Connected! || || sql-statement || help [tablename] || quit || |+---------------------------------------+SQL> quitThe error scenario that is shown in Example 4-11 results in the following output:[01000][unixODBC][Driver Manager]Can't open lib'/var/lib/db2/sqllib/lib/libdb2.so' : file not found[ISQL]ERROR: Could not SQLConnectThis message indicates a problem with the files in the /var/lib/db2/sqllib/lib/libdb2.sodirectory. Confirm that the correct files are available, then restart CNM and verify that theCNM starts without posting the previous errors.Another scenario of a CNM to DB2 communication issue with slightly different messagesposted in /var/opt/isnm/cnm/log/eventSummary.log is shown in Example 4-12.Example 4-12 CNM to DB2 communication scenario case# tail /var/opt/isnm/cnm/log/eventSummary.log13:19:23.283143 cnm_glob.cpp:1049: CNM Daemon is starting now13:19:23.283143 cnm_glob.cpp:400: Unable to create instance of XCATDB ppc table13:19:23.283143 cnm_glob.cpp:312: Unable to get cluster information from XCATDB13:22:08.372292 cnm_glob.cpp:1031: DB tread is starting nowWhen the EMS is rebooted, CNM might start before DB2 is ready, and this results in the errormessages that are described in Example 4-12. To resolve this problem, run the commandsthat are shown in Example 4-13.Example 4-13 Restarting and synchronizing DB2 when CNM is started before DB2 is ready# su xcatdb# db2This takes you to the db2 prompt:db2 => connect to xcatdbdb2 => db2stop forcedb2 => db2startRecycle CNM and verify that it starts without the previous errors.