Troubleshooting issues when the AR System server takes a long time to start

The following logs are important to identify startup issues with the :

• arerror.log
• arstartup_trace logs
• ccs_config.log
• ccs_server logs
• SQL logs

You can also check the API logs to confirm when the connection with the  was established first time. 

Enable the API and SQL logging if not enabled and capture logs for the slow startup.

Consider performing the following actions if the  does not start or takes a longer time to start and you cannot enable the API and SQL logs:

1. In Centralized Configuration, select the com.bmc.arsys.server component for your specific server name.
2. Locate the Debug-mode setting.  
3. For API+SQL logging, set the Debug-mode to 17. 
4. Click Apply.
5. Restart the .

Review the arerror.log file and check if there are any errors reported during the  startup.

Use the table to analyze the specific errors.

Review the arstartup_trace log file. These logs represents the time duration of the  startup. 

Review the file and identify time gaps in the log. See the example below:

This example shows that the  is taking a longer time to load metadata.

Review the sample startup log that shows a successful  startup. sample_arstartup.log.

Use the table to analyze the specific symptoms and errors.

The  Centralized Configuration logs are updated during the Centralized Configuration activities. The configurations are loaded into memory during the  startup.

Use the timestamp of the actual server startup as a guideline to review the Centralized Configuration logs.

See the example below:

If you observe a gap during the time duration, that might be the reason for the slow startup of the .

Use the table to analyze the specific symptoms and errors.

The SQL logs represents data dictionary loading. The data dictionary includes a large amount of data and might be a reason for slow startups of the .

The SQL logs show activity for Client-RPC:390600  and a NULL or blank user name, which indicates that this was performed by the server itself. 

You can see SELECT statements for multiple metadata tables, such as arschem, aschema_group_ids, char_menu, filter_mapping, field_dispprop.

Search for the statements in the SQL logs that show a large gap from the prior statement. You might not see a long SQL statement but, you might see many SQLs that add up for a larger duration.

Analyze logs and identify the activities that might cause slowness. Use the table to analyze the specific symptoms and errors.

Review API logs and analyze the first API call made to an external source. For example, a call from queue Pvr:390680, or queue Fast.

Analyze the duration from starting the  until the external call. With this information, you can use other logs to analyze the time required for the  startup.

• Use the  table to analyze specific errors and troubleshoot the issues.

• If you cannot identify the cause, collect the logs and raise a case with BMC Support.

• Run the Log ZipperLog zipper utility and collect logs. You must run the Log Zipper utility on each server that causes the issue.

• Rename the zipped file to include the server name.

Collect and send the following information when you create a case with BMC Support:

• User(s) that experienced the problem (if not all users)
• Approximate timestamp when the problem was observed
• What happened prior to the startup issue? 
• Reason for the server restart.
• Any recent changes to the application, database, or other components of your environment.

Attach the Log Zipper zip file up to 2 GB or share the file over FTP with BMC Support.

For more information, see the knowledge article on BMC communities SFT - Steps to send logs, files, screenshots, etc to BMC Support for a Product related case.

Check the network between  and the database.

AR System Server Troubleshooting Slow AR Server Startup

Test the query directly against the database to see if it is slow outside of the  startup.   Let the database administrator determine cause of slowness.

How can I test a DB Query using JDBC outside of AR Server?

Large number of rows in ARSystem:RLS AutoDiscovery form.

See the example below:

Slow startup time caused by large number of records in AR System

Slowness due to statistics.

See the example below:

AR System Server - Slow startup time caused by large number of records in AR System