ADM2000-2999
| ADM Message ID | Message | Explanation | User Response |
|---|---|---|---|
|
ADM2000E |
The Event Monitor eventMonitor was deactivated because it encountered an I/O error. | ||
|
ADM2001W |
The Event Monitor eventMonitor was deactivated because the MAXFILES and MAXFILESIZE CREATE EVENT MONITOR parameters' limits have been reached. | ||
|
ADM2002E |
The Event Monitor eventMonitor was deactivated when the process reading from the target pipe had disconnected. | ||
|
ADM2003W |
The Event Monitor eventMonitor was not activated because the limit on the number of active event monitors has already been reached. | ||
|
ADM2004E |
The Event Monitor eventMonitor was not activated because there was not enough storage space in the database monitor heap. To remedy this problem, increase the MON_HEAP_SZ DBM configuration parameter. | ||
|
ADM2005W |
The database monitor heap is exhausted. Increase the MON_HEAP_SZ DBM configuration parameter. | ||
|
ADM2006W |
The database monitor heap is exhausted. Statement elements may be unreliable. Increase the MON_HEAP_SZ DBM configuration parameter. | ||
|
ADM2007W |
The event monitor eventMonitor was deactivated due to PCTDEACTIVE limit reached. To reactivate the named event monitor, either increase the table space size or increase the PCTDEACTIVE threshold. | ||
|
ADM2009C |
The Event Monitor eventMonitor detected on table tableName (ID tableID) that the column name colName is invalid. | ||
|
ADM2010C |
The Event Monitor eventMonitor detected on table tableName (ID tableID) that the column colName is not allowed. | ||
|
ADM2011C |
The Event Monitor eventMonitor detected on table tableName (ID tableID) that the column colName has an invalid dataType data type. | ||
|
ADM2012C |
For table tableName, (ID tableID) the row size is bigger than the page size. | ||
|
ADM2013C |
The Event Monitor eventMonitor detected on table tableName (ID tableID) that the column colName is incorrect. The first column must be PARTITION_KEY. | ||
|
ADM2014W |
The Event Monitor eventMonitor detected on table tableName (ID tableID) that the size of the column colName is smaller than the default size of defaultColumnSize. Therefore, contents will be truncated to the user specified size. | ||
|
ADM2015W |
The SQLCODE received from the remote target node is SQLCODE. | ||
|
ADM2016W |
The table tableName (ID tableID) was not found. | ||
|
ADM2017C |
The Event Monitor monitor-name has reached its file capacity. Delete the files in the target directory directory or move them to another directory. | ||
|
ADM2018W |
The Event Monitor monitor-name has been deactivated. Event monitor data collection cannot be performed. |
The event monitor deactivated due to some error in processing that is described in probe information found in the administration notification and db2diag log files. |
Look in the administration notification or db2diag log file for probe information that indicates why the event monitor deactivated, correct the error, and then reactivate the event monitor by issuing the following statement: SET EVENT MONITOR monitor-name STATE 1 |
|
ADM2500E |
A serious error has occurred at the database server DRDAApplicationServer which has made continued processing impossible. A dump has been generated. If the remote server is DB2 UDB for OS/390,zOS, check the console log for information about this error. If the remote server is DB2 UDB for iSeries, the job log of the server job, and/or a first failure data capture (FFDC) spooled file is usually necessary to determine the cause of the error. If the remote server is DB2 Database for Linux, UNIX, and Windows, check the remote database server's administration log for information regarding this error. | ||
|
ADM2501C |
The amount of data received for a data type at the database server did not match the amount which was expected. A dump has been generated. If the remote server is DB2 UDB for OS/390,zOS, check the console log for information about this error. If the remote server is DB2 UDB for iSeries, the job log of the server job, and/or a first failure data capture (FFDC) spooled file is usually necessary to determine the cause of the error. If the remote server is DB2 Database for Linux, UNIX, and Windows, check the remote database server's administration log for information regarding this error. | ||
|
ADM2502C |
The remote database server has encountered an error. |
The client has detected a problem on the remote server. |
If the remote server is DB2 UDB for OS/390,zOS, check the console log for information about this error. If the remote server is DB2 UDB for iSeries, the job log of the server job, and/or a first failure data capture (FFDC) spooled file is usually necessary to determine the cause of the error. If the remote server is DB2 Database for Linux, UNIX, and Windows, check the remote database server's administration log for information regarding this error. If the remote server is IBM Informix Dynamic Server, check the online.log or use onstat (-m) for information about this error. |
|
ADM2503C |
A datastream parsing error has been detected. A dump has been generated. | ||
|
ADM2504C |
The LOB data type is not supported on this database server. APAR fixes are required. If this database server is DB2 for OS/390 v6 and v7, apply the fixes for APARs PQ50016 and PQ50017. If the database server is DB2 for iSeries, any release prior to V5.1 is not supported. For DB2 for iSeries v5.1, the PTF for APAR 9A00531 must be applied. If the database server is DB2 for VM and VSE, contact IBM Support. | ||
|
ADM2505E |
While the database manager was attempting to utilize sysplex support, a connection could not be established to the database server at SNA address SNAAddress due to an unknown cpic symbolic destination name destName. Check your SNA configuration and validate it with network support personnel or disable sysplex support at the DB2 Connect Server. | ||
|
ADM2506W |
While an application was attempting to issue a deferred SET statement, the server returned a non-zero sqlcode. The sqlcode is SQLCODE. Check your application, and validate the deferred SET statement. | ||
|
ADM2507I |
Client Reroute failed because of product signature violation. Original product signature: product signature. Retry product signature: product signature. | ||
|
ADM2508I |
Client Reroute successful. Hostname/IP Address: hostname/IP address and Service name/Port number: service name/port number. | ||
|
ADM2509I |
Database connection is successful. Connecting to --> Hostname/IP Address: hostname/IP address and Service name/Port number: service name/port number. |