DB2 Error Codes
DB2 Error: SQL1245N
Description : Connection limit has been reached. No more connections are allowed from this client.
Explanation:
The maximum number of concurrent database connections has been reached for an environment where the number of connections is restricted or must be predefined. The primary example of where this would occur is when the NETBIOS [...]
Continue reading about Error: SQL1245N Connection Limit Reached
DB2 Error: SQL1263N
Description : The archive file name is not a valid log file for database name on node node-number.
Explanation:
The specified archive log file exists in the database log directory or the overflow log directory on the specified node, but the file is not valid.
Roll-forward recovery processing stops.
Solution:
To determine the correct [...]
Continue reading about Error: SQL1263N Archive file name not valid
DB2 Error: SQL0161N
Description : The resulting row of the insert or update operation does not conform to the view definition.
Explanation:
The WITH CHECK OPTION clause was specified in the view definition that is the object of the insert or update operation or a FROM clause specified an insert or update operation with a [...]
DB2 Error: SQL0284N
Description : The table was not created because the table space tablespace-name following the clause clause is a tablespace-type table space.
Explanation:
The CREATE TABLE or DECLARE GLOBAL TEMPORARY TABLE statement specified a table space named tablespace-name following the clause clause that is not a valid type of table space for this [...]
Continue reading about Error: SQL0284N The table was not created
DB2 Error: SQL0290N
Description :Table space access is not allowed.
Explanation:
A process attempted to access a table space which is in an invalid state for which the intended access is not allowed.
If the table space is in a quiesced state, only processes which also hold the table space in a quiesced state are [...]
Continue reading about Error: SQL0290N Table space access is not allowed
DB2 Error: SQL1762N
Description : Unable to connect to database because there is not enough space to allocate active log files.
Explanation:
There is not enough disk space to allocate active log files. Possible reasons include:
There is insufficient space available on the device used to store the recovery logs.
If userexits are enabled, the [...]
Continue reading about Error: SQL1762N Unable to connect to database
DB2 Error: SQL1749N
Description : The NOT LOGGED INITIALLY attribute cannot be activated for table table-name since it was not created with NOT LOGGED INITIALLY.
Explanation:
The table table-name was not created with the NOT LOGGED INITIALLY attribute specified and therefore this attribute cannot be activated using ALTER TABLE.
The statement cannot be processed.
Solution:
Remove [...]
