HP Neoview Messages, Manual

Page: 256 / 400

table-name
is the name of the table being altered.
actual-row-length
is the row length of the MV source or the trigger base table.
max-row-length
is the maximum row length of the MV source table or trigger base
table for which it is guaranteed that the compile error will not
occur.
Cause
Triggers and ON STATEMENT materialized views require the presence of an internal
table to help maintain them. The compilation of update DML statements that cause the firing
of UPDATE triggers or the refresh of ON STATEMENT materialized views might fail if the
table to be updated has a wide row. This informational message warns against the possibility
of this error occurring at compile time after altering the source table with the additional column.
Effect
None. This is an informational warning only.
Recovery None but the addition of the new column might have caused the new table record
length to be larger than the
max-row-length
and the user is advised to reconsider the design
of the table or the presence of UPDATE triggers and/or ON STATEMENT materialized views
on the table.
SQL 12069
12069 A materialized view cannot be created on volatile tables.
Cause Materialized views are not allowed on volatile tables.
Effect The creation of the materialized view fails.
Recovery None.
SQL 12070
12070 UPDATE Triggers and/or incremental materialized views exist on
table table-name and the record length is larger than the recommended
length of max-row-length. If you are updating multiple columns in the
same update statement, try splitting your update statement into multiple
update statements where less columns are updated per statement.
table-name
is the name of the table being updated.
max-row-length
is the maximum allowed row length for this operation.
Cause
The table row length is too large for this type of operation on a table with UPDATE
triggers. Or ON STATEMENT materialized views are defined on it.
Effect The UPDATE operation fails.
Recovery
If the UPDATE statement is updating multiple columns, try splitting the statement
into multiple UPDATE statements. If that does not work, you need to drop the UPDATE trigger
or ON STATEMENT materialized views defined on the table. You may also consider redesigning
your table so that the row is not as wide.
SQL 12074
12074 A materialized view cannot be directly updated.
Cause You attempted to update a materialized view.
Effect
The update failed.
Recovery
None.
SQL 12075
12075 A materialized view metadata table cannot be directly updated.
Cause You attempted to directly update a materialized view metadata table.
Effect The operation failed.
256 Materialized Views Messages (12000 Through 12329)