We routinely create aliases on DB2 z/OS that reference tables in a remotely catalogged DB2 LUW database:
create alias MYSCHEMA.MY_TAB LE for REMOTEDB.MYSCHE MA.MY_TABLE;
When we create an ALIAS on Z/OS for LUW table SYSIBM.SYSCOLUM NS and try to SELECT from it, we get this error:
DSNT408I SQLCODE = -204, SQLSTATE = 42704, SYNTAX ERROR OR ACCESS RULE VIOLATION FROM DB2 UDB FOR AIX,LINUX,HP-UX,SUN AND WINDOWS TOKENS MYSCHEMA.SYSCOL UMNS
We can solve the problem by creating another alias -- using the same syntax used on z/OS -- in the LUW database so that the same alias exists in both databases.
We don't have to create the LUW alias for any "regular" user tables. Why do we need it for SYSIBM.SYSCOLUM NS ?
Thanks for any info!
create alias MYSCHEMA.MY_TAB LE for REMOTEDB.MYSCHE MA.MY_TABLE;
When we create an ALIAS on Z/OS for LUW table SYSIBM.SYSCOLUM NS and try to SELECT from it, we get this error:
DSNT408I SQLCODE = -204, SQLSTATE = 42704, SYNTAX ERROR OR ACCESS RULE VIOLATION FROM DB2 UDB FOR AIX,LINUX,HP-UX,SUN AND WINDOWS TOKENS MYSCHEMA.SYSCOL UMNS
We can solve the problem by creating another alias -- using the same syntax used on z/OS -- in the LUW database so that the same alias exists in both databases.
We don't have to create the LUW alias for any "regular" user tables. Why do we need it for SYSIBM.SYSCOLUM NS ?
Thanks for any info!