Slow performance in the Components step when installing Service Catalog

Products

• CA Service Catalog

Issue/Introduction

When installing the Service Catalog, the "Configuring CA Service Catalog - Components" step takes more time than expected, almost hours to complete. It gets stuck in 93% of progress for hours.

USM_HOME\logs\install\seeddata.log shows the amount of inserted rows and the time it takes to complete. 

Environment

Service Catalog 17.x

Cause

The delay in the components installation is related to one action during the installation (seeddata.log) which is a high database-intensive action.

Resolution

This behavior suggests there might be a latency between their servers (Catalog and DB Server) or it could be something related to DB performance.

Suggestions:

1. Engage the DBA to check if there are performance issues with the Database instance.

2. Run a ping test between Catalog and DB Server to see if there a latency issue.

From Catalog server: Open CMD > Run: ping <DB Server>

 

Additional Information

The seeddata.log logging may start out with "Started loading the seeddata" and can take an hour or longer to run, depending on database performance and capability

Sample seeddata.log logging observed may indicate:

20XX/XX/XX 09.50.19.144 INFO  Started loading the seeddata 
...
20XX/XX/XX 10.13.09.117 INFO  6263 row(s) processed in 628662 ms
...
20XX/XX/XX 10.24.23.730 INFO  4539 row(s) processed in 608474 ms
...
20XX/XX/XX 10.39.42.736 INFO  3920 row(s) processed in 752186 ms
...
20XX/XX/XX 10.57.12.452 INFO  Successfully loaded the seeddata 

 

In the install.log or stdout.log generated during Catalog install, a line may present such as:

XX/XX/XX XX:XX:XX.XXX DEBUG SLCMPatch.java         283 SLCM create TelemetryAdmin user Command: "C:\Program Files\CA\Service Catalog\scripts\user\createuser.bat" "<PASSWORD>" "<PASSWORD>"

The creation of the TelemetryAdmin user could also trigger the seeddata activity