db2 initialdata load on 21.0: SQL0613N The primary key ... "PK_CERT" is too long
search cancel

db2 initialdata load on 21.0: SQL0613N The primary key ... "PK_CERT" is too long

book

Article ID: 262548

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine CA Automic One Automation

Issue/Introduction

When attempting to upgrade from 12.3 to 21.0, the following error shows up in the db load log:

20230307/152009.129 - U00003590 UCUDB - DB error: 'SQLExecDirect', 'ERROR   ', '54008', ' SQL0613N  The primary key, unique key, or table partitioning key identified by "PK_CERT" is too long or has too many columns and periods.  SQLSTATE=54008

Environment

Release : 21.0.4

Resolution

Based on the info provided, it looks like the database doesn't have any matching table space to fit the UC_CERT table (which is new in version 21.0).  The table spaces in 8/16/32 K are needed as are the corresponding buffer pools within DB2 (This is also discussed in the Installation Settings Requirements for DB2).  It looks like on DB2 10.5, this is placed in the UC4T16K tablespace.  Please discuss this with a DBA.  The statements with CREATE TABLE UC_CERT...  in 

./db/db2/12.4/steps/step_003.sql
./db/db2/12.5/uc_ddl.sql
./db/db2/12.6/uc_ddl.sql
./db/db2/12.7/uc_ddl.sql
./db/db2/21.0/uc_ddl.sql

may need to be updated based on the info above and what a DBA says