Power

Hello,

Not sure how to proceed. Everything I found about this error does not apply here.

When I run "python", I get this.

Could not load program python:
Symbol resolution failed for /usr/lib/libpython2.7.so because:
        Symbol _GLOBAL__AIXI_libsqlite3_so (number 219) is not exported from dependent
          module /usr/opt/rpm/lib/libsqlite3.so.
        Symbol _GLOBAL__AIXD_libsqlite3_so (number 220) is not exported from dependent
          module /usr/opt/rpm/lib/libsqlite3.so.
Examine .loader section symbols with the 'dump -Tv' command.

Anyone got a clue?

Thanks

I ran into a similar issue and it has to do with setting AIX LIBPATH.

Have a look at this: AIX Open Source

Ibm		remove preview
AIX Open Source I'm using PowerHA ROHA feature which utilizes program clcloudroha included in PowerHA software. That program requires "/usr/lib" to be the first component in LI View this on Ibm >

For the record and next time please, include:

AIX version: oslevel -s

Python version: rpm -qa | grep -i python

For this error : rpm -qa | grep -i sql

I guess you know Python 2.7 is now dead and has been for a few years. Time to upgrade.

Cheers, Nigel

The error message indicates that when attempting to run a Python program, the system fails to correctly load the Python dynamic link library (libpython2.7.so) because it depends on certain symbols from the libsqlite3.so library, which are not properly exported in libsqlite3.so. This is typically caused by incompatible library versions, installation errors, or configuration issues.

Here are some advice:

Verify the compatibility of the library files:

• Check if libpython2.7.so and libsqlite3.so are compiled for the same system architecture (e.g., 32-bit or 64-bit).
• Confirm that these two libraries come from compatible software packages or distributions.

Check the installation location of the library files:

• Typically, system library files should be installed in standard directories such as /usr/lib or /lib. The path /usr/opt/rpm/lib appears to be a location for third-party or manually installed libraries, which may cause the system linker (e.g., ld) to fail in correctly finding or processing these libraries.
• Try moving libsqlite3.so to a standard library directory, such as /usr/lib, and ensure that the linker configuration (e.g., /etc/ld.so.conf) includes this directory.

Library version incompatibility: libsqlite3.so on your system may not be compatible with the desired version of Python. This may be because different versions of the SQLite library are installed on your system, or Python was built with a different version of SQLite than the one on your system.

Library file path problem: Python may not be looking for library files in the correct path. You may need to set or update the LIBPATH environment variable to ensure that Python finds the correct library files.

Corrupted library file: libsqlite3.so or libpython2.7.so may be corrupted or incomplete. This can be due to file corruption, incomplete software installation or updates.

For these problems, you can try the following solutions:

Check and repair library files: Use the dump-Tv command to check the libpython2.7.so and libsqlite3.so files to determine if there are unexported symbols. This can help you identify the problem
.

Update environment variables: Make sure the LIBPATH environment variable contains the directory containing the required library files. You can use echo $LIBPATH to view the current LIBPATH Settings and update them as needed.

Reinstall or update library files: If the library file version is incompatible or corrupt, you may need to reinstall or update libsqlite3 and Python. Make sure you are using libraries that are compatible with your system and Python version.

Check file system integrity: Use the fsck command to check the file system for corruption and fix any problems.

Restore from Backup: If you have a backup of library files, you can try to restore them from the backup.