Troubleshooting

If the publisher isn't publishing to the spool directory, try some of these tips to make sure things are running smoothly.

These troubleshooting tips involve running the publisher scripts manually, from the command line. This should only be done to test operation of the scripts. Normally, these scripts are executed automatically by the load_updates.sh script. The load_updates.sh script is configured to run periodically on your system.

Check that load_updates_post.sh Runs

Look in $LIMHOME/config/load_updates.hst log file to see if the load_updates_post.sh script is being run. The load_updates.sh script will log each time that it invokes the load_updates_post.sh script. If the load_updates_post.sh script is not running then perform the following steps:

  • Make sure you have enabled load_updates_post.sh by modifying the $LIMHOME/.limrc file. Set LUSPOST=yes in the $LIMHOME/.limrc file as described in the section called “Setup load_updates_post.sh”.

  • Check that $LIMHOME/load_updates_post.sh exists, and that the script has executable permissions set for the LIM user.

Ensure that load_updates_post.sh invokes the $LIMHOME/pub2/publish_records.ksh Script

Make sure to check the contents of the load_updates_post.sh file to make sure it invokes the publish_records.ksh script.

To test that the script properly invokes the publisher, run the load_updates_post.sh script from the command line. Change into the $LIMHOME directory, and execute it by typing ./load_updates_post.sh. If it runs successfully, then you know this script is working properly.

Ensure that $LIMHOME/pub2/publish_records.ksh Script Runs

Examine the contents of publish_records.ksh and make sure that it is configured to connect to the correct host and port.

To test that the publish_records.ksh script runs properly you can invoke the script from the command line. Change into the $LIMHOME/pub2 directory and run ./publish_records.ksh.

  • Check that the $LIMHOME/pub2/publish_records.ksh has executable permissions set for the LIM user.

Check the Creation of the Delta Log

If the publisher runs correctly, but no updates are being sent to the spool directory, check to make sure that the server is configured correctly.

To test that the delta log is created when data is loaded, insert some sample data into $LIMHOME/data.cust/xmim.mim. As long as the values that you loaded into the server are new values, you should see a delta log file in the database directory like this: $LIMHOME/data.cust/xmim.mimdb/upd_info_0.txt

The presence of the upd_info files indicates that the delta logs are being created by the server. After the publisher runs, you can confirm that these files have been removed. If these files are not being created, remember to modify your .xmimrc file to enable advUpdatesLogging as described in the section called “Configuring the MIM Server”.