Insufficient base table information for updating or refreshing

For example, the SQL statement "Select * from qiws.q Custcdt" generates the error message listed above.An SQL log shows that MDAC built the SQL Statement "Insert into "qiws"."q Custcdt" ....".To resolve the problem, try upgrading MDAC, using a client side cursor, or changing the cursor and lock type.Note that a unique key on the table might be required.

The user must have Read authorization to all logical files and all indexes built over the table.Some applications suppress this error message and only report a message such as "table is read only." For a detailed description of this problem, refer to the authority section below. The data source or application have set the isolation level to an isolation of read uncommitted or higher and attempted to modify a table that was not journaled.Set the commit mode in the data source to *NONE or journal the table. DB2/400 treats logical files similar to an SQL view.Even though OS/400 or i5/OS can allow updates of the view/logical file, some PC applications can report the logical file as being read-only.At this time, the OS/400 or i5/OS database server does not return information to a request for unique keys on a logical nor does it return catalog information on the constraints that a logical inherits from a physical file.

Search for insufficient base table information for updating or refreshing:

insufficient base table information for updating or refreshing-62insufficient base table information for updating or refreshing-82insufficient base table information for updating or refreshing-24insufficient base table information for updating or refreshing-15

Leave a Reply

Your email address will not be published. Required fields are marked *

One thought on “insufficient base table information for updating or refreshing”