Neoview ODBC Drivers Manual (R2.2)

1. Check the integrity of the library:

• Verify MD5SUM

md5sum library

Compare the output with the contents of /etc/hpodbc/MD5SUM.

• Find the version of the driver:

— On Linux:

nm libhpodbc.so | grep HPODBC

nm libhpodbc_drvr.so | grep HPODBC

— On x86–64 Linux:

nm libhpodbc64.so | grep HPODBC

nm libhpodbc_drvr64.so | grep HPODBC

— On HP-UX(IA-64) and HP-UX(PA-RISC):

nm libhpodbc.sl | grep HPODBC

nm libhpodbc_drvr.sl | grep HPODBC

— On HP-UX(IA-64) 64–bit:

nm libhpodbc64.i.sl | grep HPODBC

nm libhpodbc64_drvr.i.sl | grep HPODBC

— On IBM AIX®:

nm libhpodbc.a | grep HPODBC

nm libhpodbc_drvr.a | grep HPODBC

The nm command returns this version information:

_###HPODBC_x_y_z_yymmdd

The “x_y_z” string is the version number (for example, 1_0_0).

The “yymmdd” string is the build date, where yy is the year, mm is the month, and dd is the

day (for example, 060419).

2. Check the configuration of the application:

• Set trace ON in the MXODSN configuration file.

• Make sure that the servers have been started.

• Make sure that the executable has been linked in with the correct version of the driver.

For example:

ldd connect_test

libhpodbc_l.so.1 => /usr/lib/libhpodbc_l.so.1

(0x0091f000)

libc.so.6 => /lib/tls/libc.so.6 (0x00334000)

libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x04d5a000)

libm.so.6 => /lib/tls/libm.so.6 (0x00465000)

libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x005c2000)

/lib/ld-linux.so.2 (0x0031b000)

Troubleshooting 39