IBM Support

"Unable to connect to Database" after updating from 3.1.0 to 3.1.3

Troubleshooting


Problem

The issue will appear after the update from 3.1.0 to 3.1.3.10, HMC reports error "Cannot connect to one or more Virtual I/O Servers."

Symptom

When we try to query the VIOS virtual networks or virtual storage configurations from HMC, the following error is reported:
"Error occurred while querying for SharedEthernetAdapter from VIOS <VIOS_name> with ID <VIOS_ID> in System <System_name> - Unable to connect to Database."
or
"Cannot connect to one or more Virtual I/O Servers.
Error occurred while querying for ViosStorage from VIOS with VIOS_LPAR_ID in System - Data cannot be retrieved from VIOS. Please, check the file system, network, and system resources of the VIOS. If the error persists, contact your service representative."
From the viosvc.err log file on VIOS the following error details are reported:
[0 6291874 19726675 10/27/21-16:17:03.737 viosvc_res.c 1.27 231] TRACING Level = 0 Message:0 -- Oct 27 2021, 16:17:03.737 violibDB.c           vioProcessSQLError 1.132.2.577 274 **(Calling Function: attemptDBConnection, Line: 1274)** SQL Native Error = 0, iSQL State = 00000, error message = [iODBC][Driver Manager]Could not load module /usr/ios/db/postgres13/lib/psqlodbcw.so.
    Dependent module /usr/lib/libpq.a(libpq.so.5) could not be loaded.
    The module has an invalid magic number.
Could not load module /usr/ios/db/postgres13/lib/psqlodbcw.

Cause

The use of a 32bit version of /usr/ios/db/lib/libpq.a library after the update.

Environment

VIOS level:  3.1.3.10
Only after the update from 3.1.0.
The issue is seen after the update from level 3.1.2 to 3.1.3.10.
Issue has also been seen  at version 3.1.3.14.
CAUTION
This does not apply to a VIOS that is part of an SSP cluster.

Diagnosing The Problem

When we run the following commands under oem_setup_env, we get similar outputs:

# ldd /usr/ios/db/postgres13/lib/psqlodbcw.so
/usr/ios/db/postgres13/lib/psqlodbcw.so needs:
         /usr/lib/libc.a(shr.o)
         /usr/lib/libiodbcinst.a(libiodbcinst.so.2)
         /usr/lib/libpthreads.a(shr_xpg5.o)
         /usr/ios/db/postgres13/lib/libpq.a(libpq.so.5)
         /unix
         /usr/lib/libcrypt.a(shr.o)
         /usr/lib/libdl.a(shr.o)
         /usr/lib/libpthreads.a(shr_comm.o)
# ar -tv /usr/ios/db/lib/libpq.a
rw-r----- 300/300 418709 May 22 11:33 2018 libpq.32so.5
# ar -tv /usr/lib/libpq.a
rw-r----- 300/300 418709 May 22 11:33 2018 libpq.32so.5

Resolving The Problem

IMPORTANT
If the VIOS in question is part of an SSP Cluster, do not use this procedure.  Contact IBM Support for problem determination.
$ oem_setup_env
# stopsrc -s vio_daemon
# rm /usr/lib/libpq.a
# startsrc -s vio_daemon

Then
# kill -1 vio_daemon's PID
Then, check again the HMC GUI where you were getting error before (either Virtual Storage or Virtual Network) . If you still facing issue get back to IBM.
 

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSPHKW","label":"PowerVM Virtual I\/O Server"},"ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.1.0"}]

Document Information

Modified date:
04 June 2024

UID

ibm16510156