New Upgrade Kit Status: Request Submitted

Occasionally, you might notice that the status of a new upgrade kit remains Request Submitted after several minutes of waiting. This status means that the Upgrade Kit Builder has not yet picked up the server request to build the upgrade kit. There are several possible causes for this delay:

• The upgrade kit might have been created when the Siebel Anywhere component was not enabled. The status will not change until the component is enabled. After the component is enabled, the request will be processed automatically.

• The server component Upgrade Kit Builder (alias UpgKitBldr) might be busy building a previously submitted upgrade kit. Most upgrade kits take only a few minutes to build. However, Siebel Database Schema upgrade kits can take as long as two hours or more to build, depending on the database type, the database size, and the extent of the schema changes.

• The server component Upgrade Kit Builder (alias UpgKitBldr) might not be running.

• The server component Server Request Broker (alias SRBroker) might not be running correctly.

• The server component Server Request Processor (alias SRProc) might not be running correctly.

The following paragraphs provide information about troubleshooting some of these problems.

Checking for Current Upgrade Kit Builder Activity

The following procedures provide ways to check whether the Upgrade Kit Builder is busy building another upgrade kit:

To check Upgrade Kit Builder activity in a Siebel application  

1. Navigate to the Administration - Server Management screen, then the Components view.

2. In the Components list, select the Upgrade Kit Builder component.

3. Click the Tasks view tab, and inspect the status of any tasks submitted for the Upgrade Kit Builder component.

To check Upgrade Kit Builder activity using srvrmgr  

• In srvrmgr, enter the following command to check the status of Upgrade Kit Builder tasks:

  srvrmgr> list task for comp UpgKitBldr

Checking the Status of Components Related to Upgrade Kits

Use any of the following ways to check the status of the UpgKitBldr, SRBroker, and SRProc components:

• Navigate to the Administration - Server Management screen, then the Components view. Select each applicable component, and click the Tasks view tab to inspect the status of tasks submitted for that component.

• In srvrmgr, use the following command to view the status of a component, replacing component_name with UpgKitBldr, SRBroker, or SRProc:

  srvrmgr> list comp component_name

• In the log directory, check the log files as follows:

  • Inspect the enterprise_server_name.siebel_server_name.log to verify that all the processes for UpgKitBldr, SRBroker, and SRProc were created correctly.

  • See whether there are any signs of trouble in the SRProc_task#.log file or the SRBroker_task#.log file.

Troubleshooting Server Request Processor Problems

If you find evidence that the SRProc component is not running correctly, then check the following aspects of your server's configuration:

• Is the database connection information correct?

• Are the user name and password correct?

• Have you done server component synchronization? For more information about this procedure, see Siebel System Administration Guide.

For more information about troubleshooting server problems, see Siebel System Monitoring and Diagnostics Guide.