When doing a U TA report in RC/Query with ACM on, why do I receive: DSNT408I SQLCODE = -206, ERROR: A.GRANTOR IS NOT VALID IN THE CONTEXT WHERE IT IS USED

Products

• RC Compare for DB2 for z/OS

Issue/Introduction

When doing a U TA report in RC/Query with ACM (Alternate Catalog Mapping) on, why do I receive:

DSNT408I SQLCODE = -206, ERROR: A.GRANTOR IS NOT VALID IN THE CONTEXT WHERE IT IS USED 

Environment

Release:
Component: RCQ

Resolution

The U TA report goes against the SYSTABAUTH which contains the GRANTOR column.  If the ACM View or Shadow table that was defined does not contain this column, a -206 will occur.

From the DB2 Tools Main Menu:

- Go to Option M (Alternate Catalog Mapping)

- Find the ACM ID being used, place an 'S' next to it.

- Check that the view or table name next to SYSIBM.SYSTABAUTH does contain the GRANTOR column.  If it does not, recreate the view or table ACM is using for the SYSTABAUTH catalog table.  Ensure the correct name shows under the ACM ID definition.