RMA543E error in Post Install ssid0000 Compare task
search cancel

RMA543E error in Post Install ssid0000 Compare task

book

Article ID: 226011

calendar_today

Updated On:

Products

Database Management for DB2 for z/OS - Administration Suite Database Management for DB2 for z/OS - Performance Suite Database Management for DB2 for z/OS - Recovery Suite Database Management for DB2 for z/OS - SQL Performance Suite Database Management for DB2 for z/OS - Utilities Suite DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS

Issue/Introduction

The Database Management Post Install DDLCOMP step in the Compare customization task (ssid0000) may fail with the following error messages:

RMA543E THE COLUMN LENGTHS IN CONSTRAINT CREATOR EXCEED 255
      CHARACTERS.                                          

RMA543E THE COLUMN LENGTHS IN CONSTRAINT (PRIMARY KEY) EXCEED 255
      CHARACTERS.                                                

   POST INSTALL ANALYSIS COMPLETED,  RETURN CODE =    8              
                                                                     
RCM00055: The ANALYSIS phase has completed with errors.  Please check
          the MSGFILE DD for more information on the error.          

Cause

The RMA543E errors are a result of RC/Compare for Db2 for z/OS (RCC) failing to identify the correct Db2 version.
This can occur when there is a module mismatch between the Xmanager runtime load library and the Product runtime load library.

Resolution

Check that Xmanager is using the same hlq.CDBALOAD as the Post Install job.

If not then you will need to recycle Xmanager pointing it to the correct runtime load library.

When there is any maintenance to the Xmanager authorized services, then there will be holddata to follow to run the Xmanager started task with
latest runtime libraries to avoid the module mismatch errors.

For example for PTF LU01362:

++HOLD (LU01362) SYSTEM FMID(CINSK00)                                   
  REASON (RESTART)   DATE (21155)                                       
  COMMENT (                                                             
+----------------------------------------------------------------------+
|     CA DBM Solutions for DB2 for z/OS Base In       Version 20.0     |
+----------+-----------------------------------------------------------+
|SEQUENCE  | Before Apply                                              |
+----------+-----------------------------------------------------------+
|PURPOSE   | Avoidance of module mismatch related errors in an Xmanager|
+----------+-----------------------------------------------------------+
|USERS     | Collections of DB2 statistics via Detector or Subsystem   |
|AFFECTED  | Analyzer.                                                 |
|          | DB2 subsystems that have active collections.              |
+----------+-----------------------------------------------------------+
|KNOWLEDGE | 1. SMP/E                                                  |
|REQUIRED  | 2. z/OS System Programming                                |
|          | 3. CA DB2 Tools Installation and Maintenance procedures.  |
+----------+-----------------------------------------------------------+
|ACCESS    | 1. Product runtime libraries.                             |
|REQUIRED  |                                                           |
+----------+-----------------------------------------------------------+
                                                                        
                      **************************                        
                      * STEPS    TO    PERFORM *                        
                      **************************                        
                                                                        
To implement the PTF:                                                   
1. Stop product collections.                                            
2. Stop the Xmanager task.                                              
3. Update the runtime library.                                          
4. Restart the Xmanager task.                                           
                                                                        
Important!                                                              
Please do not apply maintenance to the Xmanager runtime libraries with  
Xmanager active as it may result in a discrepancy between               
dynamically loaded components and statically loaded components.         
This may result in unpredictable behavior with CA-DB2 tools and/or may  
compromise the operating system/DB2 including possible failures.