Reports on UNIX EH may take hours to complete
A user has an Oracle report running on the IMS node. The report queries the MOD database for objects (tags) that meet a specific criteria. The queries go against tables such as CCF_CONTIN_LOOP.
At one point in time, the reports would take minutes to run. However, following a top-down compile of the database, the reports are now taking many hours to complete.
It may even appear to the end-user that the reports are not running at all.Symptoms:
The cause for the report slowdown is the contents of the Location Table, and the fact that tags (objects) in the location table are no longer in the MOD database.
In order for a tag to be queried against the MOD database, it must have an entry in the location table. If an entry exists in the location table that does NOT exist in the MOD database, each entry may take a minute or more to timeout when a query is issued.
There are 4 utilities described in the SQL*Connect User;s Guide to help manage the Location table.
gtuListAll will list all the entries in the location table
gtuCheckLT will check the location table and remove entries from the location table that no longer exist in the database.
gtuPopLT adds new entries to the location table.
It is recommended to do a gtuListAll to list out the current location table. Then use gtucheckLT to remove the entries that no longer exist, and then use gtuPopLT to add new entries to the location table. Note: you need to know the tag (object) name to add it to the location table.