How to resolve F_JG202F?

This topic contains 1 reply, has 2 voices, and was last updated by  Mark Van de Wiel 1 month, 1 week ago.

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
  • #8867

    Mark Van de Wiel

    How to resolve the following error?

    F_JG202F: Attempt to load dynamic shared library ‘[some hvr connectivity library].so’ failed with error: ‘[referenced library].so: cannot open shared object file: No such file or directory’. This problem could be because this library or a library it referenced was not contained in library search path variable ‘LD_LIBRARY_PATH’.


    Mark Van de Wiel

    Error F_JG202F occurs every now and again when the first attempt to connect to a database is made on a Linux or Unix system. The issues is generally that [referenced library].so is not installed on the system, or cannot be found.

    Here is how to resolve the issue:

    1) Double check the HVR release notes $HVR_HOME/hvr.rel on the machine that connects to the database to make sure that the required connectivity libraries for your database have been installed. If connectivity libraries are missing then install these.

    2) With all libraries installed on the system you may still see F_JG202F. If that is the case then find out what is missing by using for example ldd on Linux to find the linked dynamic dependencies. E.g.:


    This command will output the list of referenced libraries for the HVR Oracle 12c connectivity library. It will be clear from the output if one of the referenced libraries cannot be found. You may then have to set or adjust the LD_LIBRARY_PATH (on Linux; Unix systems have their own equivalent) environment variable to ensure all dynamically linked dependencies can be found.

    3) The last step is to make sure that when HVR initiates the connection the environment is set correctly. This generally involves restarting the HVR remote listener, and depending on how it is started you may have to edit the xinetd setup you created or add the environment settings to the hvrtab file when using hvr_boot to start the remote listener upon server (re)start.

    Note that you may need to go back through these steps if you initially chose to run the hvrremotelistener process on the command line and later switched to an xinetd or hvr_boot automatic startup.

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.

© 2017 HVR Software

Request Trial Contact Us