Troubleshooting a Situation Where the Visutl Utility Reports That the Record Is Visible

This topic describes how to troubleshoot a situation where the Visutl utility reports that the record is visible on the local database.

To troubleshoot a situation where the visutl utility reports that the record is visible

1. To verify that the record resides on the local database, use SQL*Plus to log in to the local database.

2. To determine if the record resides on the local database, run the following query:

   Select * from SIEBEL.TABLENAME where ROW_ID = ‘Row id of the record that is not visible’
   

3. If the record resides on the local database but is not visible through the user interface, and if you use a custom Siebel runtime repository, then try to log in to the Siebel application using the predefined Siebel runtime repository.

   If the records are visible, then something in the configuration is filtering out the records and you must investigate the configuration.

4. To identify the configuration that filters out the records that must be visible, start the Siebel application in the Siebel Developer Web Client, using the -s option, and then examine the query or joins that the application runs.

   The -s option spools out the SQL that the Siebel application runs on the view that does not display the record. For more information, see the following items:

   • About the Siebel Enterprise and the Siebel Enterprise Server.

   • For more information about using the -s option to examine the SQL that a Siebel applications creates, see the Siebel Installation Guide and Siebel Performance Tuning Guide.

5. If the record does not reside on the local database, then this situation indicates a potential problem with the server processes that Siebel Remote uses. You can do the following:

   1. Confirm that the user synchronized successfully with the Siebel Server.

   2. Examine the syncthrd log files for errors.

      For more information, see Log Files on the Remote Client.

   3. If transaction, routing and synchronizing are fine, then reextract the user and determine if the record is visible after the reextraction.