The max number of columns is 750, but….. the max length of a row in version 8 is 32K DB Audit creates a repository table whose columns match your data table, plus it adds several extra "header" columns to store information about who made the change, when, where and what type of change. All together this probably exceeds DB2's 32K row size limit. Another slim possibility is that for the DB Audit repository you selected a tablespace whose page size is smaller then in the tablespaces hosting your data table (same for temporary tablespace). This could also produce weird results leading to SQL1424N : Hi there, : When I try to set up auditing on a DB2 V8.11 table with 529 columns : I get the error message : A Database Error occurred... : SQLSTATE=54040 : SQL1424N Too many references to transition variables and transition : If I reduce the number of columns to be audited to say 502, then : the trigger is created and seems to work fine. : Is this due to an inherent restriction in DB Audit, in DB2 or is there : another explanation? : Thanks, : John
|