Relink Scripts

OpenLink's relink scripts are associated with missing library errors and missing symbol errors. Use the following guidelines to troubleshoot these problems:

Missing Libraries

1. Search the machine for the missing library.

2. Insure that no file or directory permissions prohibit access to found libraries.

3. Insure that LD_ LIBRARY_PATH, LIBPATH, or SHLIB_PATH pass the location of found libraries.

4. Pass the full path to found libraries within the relink script itself. In most cases, pass the library on the cc -s -o line. However, pass the library on the make -f line in Oracle scripts. Pass the library under $PRO_EXTRA in Progress mkdlc scripts.

Missing Symbols

1. Login to the machine.

2. cd into the database's /lib sub-directory.

3. Run the following commands:

nm -A *.so | grep symbol - works for most Unix/Linux Operating Systems
nm -A *.sl | grep symbol - variant specific to HP/UX

For example:

nm -A *.so | grep xsendto       
nm -A *.sl  | grep xsendto       

4. Record the names of files, which contain the symbols. The filename will be the first name in the nm output.

5. cd to the /lib sub-directory of the OpenLink installation.

6. vi the script that produced the error.

7. Pass the full path to found libraries within the relink script itself. In most cases, pass the library on the cc -s -o line. However, pass the library on the make -f line in Oracle scripts. Pass the library under $PRO_EXTRA in Progress mkdlc scripts.

Note: Relink script failures are serious problems. OpenLink Product Support should create bugzillas when libraries or symbols cannot be found. In fact, OpenLink Product Support may request .tars of your database native /lib files where possible to assist Support and Development in the recreation of the problem.