AAKE 21.0 Impossible to bring an additional CP to start
Article ID: 234232
Updated On:
Products
Issue/Introduction
After deployment One Automation on a Kubernetes container, only one Communication Process can be started. If a user tries to start up a additional CPs (higher than CP006) , it stops automatically with the following error in the CP log file (tablespace name error):
===============================================================
U00003590 UCUDB - DB error: 'ERROR: relation "mq1cp006" does not exist LINE 1: SELECT * FROM MQ1CP006 WHERE MQCP_SchedTime <= date_trunc('s... ^', '', '', ''
U00003592 UCUDB - Status: '42P01' Native error: '6844177' Msg: 'relation "mq1cp006" does not exist'
U00003594 UCUDB Ret: '6' opcode: 'SLCU' SQL Stmnt: 'SELECT * FROM MQ1CP006 WHERE MQCP_SchedTime <= date_trunc('second', clock_timestamp() at time zone 'UTC') AND MQCP_Status=0 ORDER BY MQCP_Priority, MQCP_SchedTime, MQCP_PK'
U00000006 DEADLOCK or Connection to database lost - Rollback handling initiated. See previous messages.
U00003590 UCUDB - DB error: 'ERROR: tablespace "ae_index" does not exist', '', '', ''
U00003592 UCUDB - Status: '42704' Native error: '6820852' Msg: 'tablespace "ae_index" does not exist'
U00003594 UCUDB Ret: '6' opcode: 'EXEC' SQL Stmnt: 'CREATE TABLE MQ1CP006(MQCP_PK int GENERATED BY DEFAULT AS IDENTITY NOT NULL,MQCP_System varchar (8) NULL,MQCP_CAddr varchar (32) NULL,MQCP_CSRName varchar (8) NULL,MQCP_CAcv int NULL,MQCP_BAddr varchar (32) NULL,MQCP_BSRName varchar (8) NULL,MQCP_BAcv int NULL,MQCP_FAddr varchar (32) NULL,MQCP_LogAddr varchar (32) NULL,MQCP_PhysAddr varchar (32) NULL,MQCP_BTable varchar (8) NULL,MQCP_SchedTime timestamp NULL,MQCP_Status int NULL,MQCP_Priority int NULL,MQCP_DRole varchar (32) NULL,MQCP_LAddr varchar (32) NULL,MQCP_Len int NULL,MQCP_Msg bytea NULL,CONSTRAINT PK_MQ1CP006 PRIMARY KEY (MQCP_PK) USING INDEX TABLESPACE AE_INDEX) TABLESPACE pg_default'
U00000006 DEADLOCK or Connection to database lost - Rollback handling initiated. See previous messages.
U00003410 Server 'AAKE_E1#CP006' version '21.0.0+build.54' ended abnormally.
===============================================================
Environment
Release : 21.0
Component : AUTOMATION ENGINE on Kubernetes
Cause
The CP is unable to start because the related MQCP006 is not present in the database
Resolution
Workaround:
Create the MQCPx006 table manually in the database. Use therefore the creation instruction for the MQCPxxx table from the initial data script. You may have to adjust the script with the appropriate CP name.
Solution:
This is a bug from the AAKE 21.0.0, it is fixed in the versions of AAKE
Automation Engine 21.0.0 HF1 -- available
Automation Engine 21.0.1 -- available
Additional Information
For troubleshooting such kind of errors, it's useful to launch this kind of query as it's the one that will be launched in case the table MQCPxxx is missing as it would mean that the table OH has no primary key:
select TABLESPACE_NAME from USER_INDEXES where INDEX_NAME = 'PK_OH';
In case of no results, please check with your DBA how is that possible and ask them to fix the database tablespaces and indexes.
Feedback
