Administrative troubleshooting

• Delete unnecessary files to provide more room on your computer.
• Close all open applications and rerun the installation.

To calculate your heap requirements, use the following formula:

Maximum heap size = 45 MB + (Number of simultaneous pollers * 30 MB) + (Number of servers * .5 MB) 
 				        + (Max file agent activity cache size * 1 KB * Number of CD file agents)

If more than 1.5 GB of heap is required, you must use a 64-bit system.

Changing Java heap settings in both Microsoft Windows and UNIX environments involves editing the InstallationInfo.properties file to add an entry. Next, you must run the configCC.bat/sh configuration script and restart the IBM Sterling Control Center Monitor engine.

To change Java heap settings:

1. Make a backup of the file InstallationInfo.properties at ControlCenterInstallDirectory\conf.
2. Open InstallationInfo.properties (at ControlCenterInstallDir\conf) with a text editor (such as Notepad on Microsoft Windows or vi on UNIX).
3. Look for line that starts with MAX_HEAP_SIZE. (If it is there, change the value to the wanted number). If it is not there, add a line at the end of the file as shown in the following example:

   MAX_HEAP_SIZE=-Xmx???m

4. Replace ??? with the wanted number.

   Example: MAX_HEAP_SIZE=-Xmx8192m

5. Save the file.
6. Run the configCC.sh (UNIX) or configCC.bat (Microsoft Windows) file at ControlCenterInstallDirectory/bin.
7. Answer no to all the questions. Merely running the script makes the necessary updates to different runEngine scripts.
8. Stop the engine by using stopEngine.sh (UNIX) or stopEngine.bat (Microsoft Windows).
9. Start the engine by using runEngine.sh (UNIX) or runEngine.bat Microsoft Windows).

• If you specify multiple criteria, all criteria must be met for the rule to take effect. Try reducing the number of criteria.
• Rule values are case-sensitive. Verify that you are using the proper case.
• Earlier rule criteria was met. Verify that the rules are in proper order.
• Verify that the rule is enabled. If the rule has a schedule associated with it, the schedule is enabled and active during the time in question.

If you want to send a notification that IBM Sterling Control Center Monitor shutdown, create a rule that identifies this error message and sends a notification.

If the database server was shut down, restart the database server and restart the IBM Sterling Control Center Monitor engine.

This can be caused by IBM Sterling Control Center Monitor using the JDBC connection pooling mechanism, which maintains a fixed number of connections with the SQL server or by using statement pooling which reuses the same JDBC connection with many different SQL Statements.

For more details refer the following link: PRB: Unexpected Connections to SQL Server with JDBC.

• Stop the IBM Sterling Control Center Monitor engine.
• From the IBM Sterling Control Center Monitor engine installation location, edit the following lines in the installation directory/conf/services/system/JDBCService.xml file and change the values to the number that you want:

<maxpool>50</maxpool>

<maxconn>100</maxconn>

<initsize>16</initsize>

• Save the modified file.
• Restart the IBM Sterling Control Center Monitor engine.

ERROR CDTask - javax.security.auth.login.
FailedLoginException: 
com.sterlingcommerce.component. 
persistence.PersistenceException: 
java.sql.SQLException: [SQL0204] 
INITPARMS in <Library name> type 
*FILE not found. 

CGRP034E Server group IDs found with matching 
system server Group IDs. Edit 
conf\servergroups\systemGroups.properties 
and change these names: {0}.

INFO  RecoverableDAO - Retrying for another time to execute query

SQL Exception msg : The query has timed out.

In the JDBCService.xml file under the CC_installation_directory/conf/services/system directory, modify the value of the dbTimeout parameter. 600 is default value, which means the query times out in every 10 minutes.

<dbTimeout>600</dbTimeout>