RMA391E during analysis executing RC/Merger

Products

• RC/Merger for DB2 for z/OS
• RC/Migrator for DB2 for z/OS
• RC Compare for DB2 for z/OS

Issue/Introduction

A RC/Merger for Db2 for z/OS (RMM) analysis execution receives message :

RMA391E TABLESPACE database.tablespace CONTAINS 1 OR MORE TABLES DROPPED SINCE THE TABLESPACE
HAS BEEN REORGED. A REORG IS REQUIRED BEFORE USING RC/MERGER TO MOVE OR COPY THIS TABLESPACE

Even if a REORG has been run (with SPACE-DEFN YES ), the execution of RMM will not complete. The message still occurs.
RMM analysis cannot be completed.

Cause

An update of SYSIBM.SYSCOPY was not requested during the REORG. The RC/Merger analysis requires the presence
of the REORG row in SYSIBM.SYSCOPY after the Table has been dropped.

Resolution

The Rapid Reorg for Db2 for z/OS parameter UPDATE-SYSCOPY YES is required to perform this update,
if the UTIL parmlib member is set to SYSCOPY (USER).

To verify the necessary row exists in SYSIBM.SYSCOPY, use the following SQL WHERE conditions on a SELECT:
DBNAME=<database-name> AND TSNAME=<tablespace-name> AND ICTYPE IN ('W', 'X') .

Verify the TIMESTAMP column.

Setting the Rapid Reorg parameter UPDATE-SYSCOPY YES during Rapid Reorg execution allows the RMM
analysis to run without producing the RMA391W error.