Troubleshooting
Problem
Control Center will not start after applying 6.0.0.1 iFix03 and choosing to initialize the database when running configCC.
Symptom
Control Center fails to start.
CJDB027E Control Center required tables are not up-to-date at the target DB
Server.
Cause
6001 upgrade script was not executed.
Diagnosing The Problem
Check the Engine logs for the following errors.
Invalid column name 'FASP_FSZ_TRS_DEP'.
Resolving The Problem
Enter the manual commands to correct the database tables.
MSSQL - Commands to manually execute contained in <install>/db/cc6000001_configCC_sqlserver_changes.sql:
ALTER TABLE CC_SERVER ADD FASP_SUPPORTED VARCHAR(10)
DROP INDEX CC_SERVER_MESSAGE.SERVER_MSG_IDX
ALTER TABLE CC_SERVER_MESSAGE ALTER COLUMN MSG_ID NVARCHAR(512)
CREATE UNIQUE INDEX USER_CAT_IDX ON CC_USER_ALERT_CAT_LIMIT(USER_ID, CATEGORY_ID)
CREATE UNIQUE INDEX SERVER_MSG_IDX ON CC_SERVER_MESSAGE(SERVER_TYPE, MSG_ID)
--------------------------------------------------------------------
DB2 - Commands to manually execute contained in <install>/db/cc6000001_configCC_db2_changes.sql:
ALTER TABLE CC_SERVER ADD FASP_SUPPORTED varchar(10)
DROP INDEX SERVER_MSG_IDX
ALTER TABLE CC_SERVER_MESSAGE ALTER COLUMN MSG_ID SET DATA TYPE VARCHAR(512)
CREATE UNIQUE INDEX USER_CAT_IDX ON CC_USER_ALERT_CAT_LIMIT(USER_ID, CATEGORY_ID)
CREATE UNIQUE INDEX SERVER_MSG_IDX ON CC_SERVER_MESSAGE(SERVER_TYPE, MSG_ID)
--------------------------------------------------------------------
Oracle - Commands to manually execute contained in <install>/db/cc6000001_configCC_oracle_changes.sql:
ALTER TABLE CC_SERVER ADD FASP_SUPPORTED VARCHAR2(10) NULL
DROP INDEX SERVER_MSG_IDX
ALTER TABLE CC_SERVER_MESSAGE MODIFY MSG_ID VARCHAR2(512 CHAR)
CREATE UNIQUE INDEX USER_CAT_IDX ON CC_USER_ALERT_CAT_LIMIT(USER_ID, CATEGORY_ID)
CREATE UNIQUE INDEX SERVER_MSG_IDX ON CC_SERVER_MESSAGE(SERVER_TYPE, MSG_ID)
Wait and apply iFix04 when it is released if this is a test environment.
IT13181/R488083 (2016-01-31)
Description of issue: The following error occurred during engine startup after upgrading from CC 6000 to 6001: DB2 SQL Error: SQLCODE=-206, SQLSTATE=42703, SQLERRMC=T0.FASP_SUPPORTED. This occurred when configCC.sh|bat was executed the for the first time after the upgrade -and- Init DB=Yes is specified. In this scenario, the 6001 upgrade script was not executed. Consequently, the existing CC_xxxx configuration tables were not altered for the 6001 environment. One of the commands in the upgrade script is to add a column named FASP_SUPPORTED to the CC_SERVER table. Hence the error message above indicating the column name does not exist.
Description of fix: Corrected configCC DB initialization logic to recognize the context of the upgrade (i.e. from 6000 to 6001 with DB Init=Yes) and to correctly execute the DB upgrade script to update the existing CC_xxxxx configuration tables.
[{"Product":{"code":"SS9GLA","label":"IBM Control Center"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Not Applicable","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"6.0.0.1","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Was this topic helpful?
Document Information
Modified date:
17 December 2019
UID
swg21976910