Event alarm IDs

The class ID for event alarms indicates the type of event. The event ID indicates the specific event.

The following table lists event alarm IDs and messages or where to find more information. Many alarms have additional explanations and user actions. Many of the issues that trigger event alarms also result in messages in the online message log. The location of the message log is specified by the MSGPATH configuration parameter.
Table 1. Event Alarms
ID Severity Messages Explanation

Class ID:

1

Event ID:

1001

3 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

Page allocation error on 'object'

The database server detected an inconsistency during the allocation of pages to a table or index.

Online log: Assertion Failure or Assertion Warning with problem details.

Server state: Dependent upon the nature of the problem found.

User action: Review the online.log file for appropriate action. You will need to run the oncheck utility on the 'dbname:"owner".tabname' identified in the message. Occasionally, the database server automatically resolves the problem, and this resolution is identified in the online.log file.

Class ID:

1

Event ID:

1002

3 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

Row allocation error on 'object'

The database server detected an inconsistency during the allocation of a row to a table or index.

Online log: Assertion Failure or Assertion Warning with problem details.

Server state: Dependent upon the nature of the problem found.

User action: Review the online.log file for appropriate action. You will need to run the oncheck utility on the 'dbname:"owner".tabname' identified in the message. Occasionally, the database server automatically resolves the problem, and this resolution is identified in the online.log file.

Class ID:

1

Event ID:

1003

3 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

Slot allocation error for 'object'

The database server detected an inconsistency during row processing.

Online log: Assertion Failure or Assertion Warning with problem details.

Server state: Dependent upon the nature of the problem found.

User action: Review the online.log file for appropriate action. You will need to run the oncheck utility on the 'dbname:"owner".tabname' identified in the message. Occasionally, the database server automatically resolves the problem, and this resolution is identified in the online.log file.

Class ID:

1

Event ID:

1004

3 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

An internal error prevented the database server to find the next possible data page in this tblspace.

The database server detected an inconsistency in a bitmap page during the allocation of a row to a table or index.

Online log: Assertion Failure or Assertion Warning with problem details.

Server state: Dependent upon the nature of the problem found.

User action: Review the online.log file for appropriate action. Run the oncheck utility on the 'dbname:"owner".tabname' identified in the message.

Class ID:

1

Event ID:

1005

3 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

Dropping wrong TBLSpace, requested tblspace_name != actual tblspace_name

The database server detected a mismatch between the requested and existing tables while attempting to drop a table. No table was dropped.

Online log: Assertion Failure or Assertion Warning with problem details.

Server state: Online

User action: Review the online.log file for appropriate action. Run the oncheck utility on the 'dbname:"owner".tabname' identified in the message.

Class ID:

1

Event ID:

1006

3 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

An internal error which may have been caused due to data corruption prevented the database server from altering the bitmap pages for this partition.

The database server encountered a possible data corruption error during a table or index operation to alter bitmap pages.

Online log: Assertion Failure or Assertion Warning with problem details.

Server state: Online

User action: Review the online.log file for appropriate action. Run the oncheck utility on the 'dbname:"owner".tabname' identified in the message.

Class ID:

1

Event ID:

1007

3 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

[3] An internal error which may have been caused due to corrupted bitmap pages as the database server is still in the process of converting them.

The database server encountered an incomplete modification of internal bitmap pages during a table or index operation to alter bitmap pages.

Online log: Assertion Failure or Assertion Warning with problem details.

Server state: Online

User action: Note all circumstances and contact IBM® Software Support.

Class ID:

1

Event ID:

1008

3 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

An internal error which may have been caused due to unconverted bitmap pages.

The database server encountered a situation where the modification of the internal bitmap pages has not yet completed. during a table or index operation to alter bitmap pages.

Online log: Assertion Failure or Assertion Warning with problem details.

Server state: Online.

User action: Note all circumstances and contact IBM Software Support.

Class ID:

1

Event ID:

1009

4 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

Page Check Error in object

The database server detected inconsistencies while checking a page that was being read into internal buffers.

Online log: Assertion failure or assertion warning with a description of the problem.

Server state: Online or offline, depending on how serious the problem is.

User action: Follow the suggestions in the online log. Typically, run the oncheck -cD command on the table mentioned in the class message or on the database.

Class ID:

1

Event ID:

1010

4 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

Bad rowid rowid

The database server detected an invalid row ID.

Online log: Assertion warning with a description of where the problem was found.

Server state: Online.

User action: Repair the index by running the oncheck -cI command on the table mentioned in the class message or on the database.

Class ID:

1

Event ID:

1011

3 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

Closing TBLSpace tblspace_name

The database server determined that the table or index is closed.

Online log: Assertion Failure or Assertion Warning with problem details.

Server state: Online.

User action: None. The database server will correct the problem automatically.

Class ID:

1

Event ID:

1012

3 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

Cannot recreate index index_name for partnum partition_number, iserrno = error_number

The database server encountered an error that prevents recreating an index.

Online log: Assertion Failure or Assertion Warning with problem details.

Server state: Online.

User action: Review the online.log file for the index information, and then drop and recreate the index manually.

Class ID:

1

Event ID:

1013

3 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

An internal error occurred while the database server was trying to initialize the type of set read operation.

The database server was unable to initialize internal data structures for a set read operation.

Online log: Assertion Warning with database and table details.

Server state: Online.

User action: Review the online.log file for ISAM error codes, and table and database information. Try the operation again. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

1

Event ID:

1014

3 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

An internal error occurred while the database server was trying to read records from the tblspace's pages

The database server encountered an internal error when reading records from a table or index.

Online log: Assertion Warning with database and table details.

Server state: Online.

User action: Review the online.log file for table and database information. Try the operation again. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

1

Event ID:

1015

3 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

An internal error occurred while the database server was trying to read the current record.

The database server encountered an internal error when reading records from a table or index.

Online log: Assertion Warning with database and table details.

Server state: Online.

User action: Review the online.log file for table and database information. Try the operation again. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

1

Event ID:

1016

3 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

An internal error occurred while the database server was trying to initialize the set read buffer.

An internal error was triggered when the database server attempted to initialize a set read buffer.

Online log: Assertion Warning with database and table details.

Server state: Online.

User action: Review the online.log file for table and database information. Try the operation again. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

1

Event ID:

1017

3 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

An internal error occurred while the database server was trying to set the new mode on the bitmap page.

An internal error occurred during the conversion of a bitmap page from an earlier version of the database server.

Online log: Assertion Warning with problem details.

Server state: Online.

User action: None.

Class ID:

1

Event ID:

1018

3 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

An internal error occurred while the database server was attempting to convert bitmap pages to the correct format.

The database server was unable to correct an error which occurred during a bitmap page conversion.

Online log: Assertion Warning with problem details.

Server state: Online.

User action: Note all circumstances, review the online.log file for additional information, and contact IBM Software Support.

Class ID:

1

Event ID:

1019

3 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

An internal error occurred while the database server was trying to modify the bitmap pages during light append operation.

The database server encountered an internal error during a light append operation and could not locate the required bitmap page.

Online log: Assertion Warning with problem details.

Server state: Online.

User action: Try the operation again. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

1

Event ID:

1020

3 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

An internal error occurred while the database server was trying to perform light scan operation.

The database server encountered an internal error while performing a light scan operation.

Online log: Assertion Warning with problem details.

Server state: Online.

User action: Try the operation again. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

1

Event ID:

1021

3 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

An internal error occurred while the database server was trying to perform light scan I/O operation.

The database server encountered an internal error while performing a light scan operation.

Online log: Assertion Warning with problem details.

Server state: Online.

User action: Try the operation again. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

1

Event ID:

1022

3 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

An internal error was reported by the database server when it tried to validate light append buffer.

The database server encountered an internal error while performing a light scan operation.

Online log: Assertion Warning with problem details.

Server state: Online.

User action: Try the operation again. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

1

Event ID:

1023

3 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

An internal error was reported by the database server when it tried to write the next record to the page in the light append buffer.

The database server encountered an internal error while performing a light scan operation.

Online log: Assertion Warning with problem details.

Server state: Online.

User action: Try the operation again. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

1

Event ID:

1024

4 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

An internal error was reported by the database server when it tried to open a light append for a tblspace.

The database server encountered an internal error during a light append operation on a tblspace.

Online log: Assertion failure.

Server state: Online.

User action: Try the operation again. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

1

Event ID:

1025

4 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

An internal error was reported by the database server when it tried to load the first bitmap page for a light append operation.

The database server encountered an internal error during a light append operation.

Online log: Assertion Failure : Light Append(Redo/Undo): Can't find bitmap page

Server state: Online.

User action: Try the operation again. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

1

Event ID:

1026

4 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

An internal error was reported by the database server when it tried to write the cached bitmap pages for a light append operation.

The database server encountered an internal error during a light append operation.

Online log: Assertion failure.

Server state: Online.

User action: Try the operation again. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

1

Event ID:

1027

2 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

An internal deadlock database condition was caught by the Lock Manager in the database server.

The database server detected an internal deadlock database condition.

Online log: Assertion warning identifying the databases and tables involved in the deadlock.

Server state: Online.

User action: None.

Class ID:

1

Event ID:

1028

2 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

An internal deadlock database condition was caught by the Lock Manager in the database server.

The database server detected an internal deadlock database condition.

Online log: Assertion warning identifying the databases and tables involved in the deadlock.

Server state: Online.

User action: None.

Class ID:

1

Event ID:

1029

4 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

An internal error was reported by the database server when it tried to map the logical page number in the tblspace to its physical location in the chunk.

The database server could not access a table because of an inconsistency between the physical page and its logical page number.

Online log: Assertion failure with the page information.

Server state: Online.

User action: Run the oncheck -cDI command on the table mentioned in the class message or on the database, fix any issues reported, and then try the operation again. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

1

Event ID:

1030

3 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

An internal error was reported by the database server when it tried to allocate the alter information.

The database server encountered an internal error when attempting to read an internal disk structure.

Online log: Assertion Warning with problem details and table and database information.

Server state: Online.

User action: Try the operation again. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

1

Event ID:

1031

3 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

An internal error was reported by the database server when it tried to prepare the list of operations to be performed on a compressed row.

The database server encountered an internal error when it tried to create an internal operations list to transform a compressed version of a row to an uncompressed version of the latest row.

Online log: Assertion Warning with problem details and table and database information.

Server state: Online.

User action: Try the operation again. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

1

Event ID:

1032

3 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

An internal error was reported by the database server when it tried to insert an operation in the list of operations based on the offset in the row where the new operation points to.

The database server encountered an internal error when it tried to create an internal operations list to transform a compressed version of a row to an uncompressed version of the latest row.

Online log: Assertion Warning with problem details and table and database information.

Server state: Online.

User action: Try the operation again. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

1

Event ID:

1033

3 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

An internal error was reported by the database server when it detected an inconsistency with the operation list.

The database server encountered an internal error when it tried to create an internal operations list to transform a compressed version of a row to an uncompressed version of the latest row.

Online log: Assertion Warning with problem details and table and database information.

Server state: Online.

User action: Try the operation again. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

1

Event ID:

1034

3 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

An internal error was reported by the database server when it tried to free the partition header page.

The database server encountered an internal error when attempting to free the header page for a partition. The database server did not free the header page.

Online log: Assertion Warning with problem details, table and database information, and a specific oncheck command to run.

Server state: Online.

User action: Review the online.log file for information and run the specified oncheck command.

Class ID:

1

Event ID:

1035

3 or 4 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

An internal error was reported by the database server when it tried to validate the partition header page.

The database server cannot access a table because of a validation error for the tblspace page.

Online log: Assertion with details about the table.

Server state: Online.

User action: Examine the online log for information about the specified table. Run the oncheck -pt command on the table or on the database and correct any errors found. Retry the original operation. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

1

Event ID:

1036

3 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

An internal error was reported by the database server when it tried to update the special columns list during an alter table command processing.

The database server encountered an internal error when processing the special columns list associated with a table while the table was being altered.

Online log: Assertion Warning with problem details, table and database information, and a specific oncheck command to run.

Server state: Online.

User action: Review the online.log file for information and run the specified oncheck command.

Class ID:

1

Event ID:

1037

3 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

An internal error was reported by the database server when it tried to log the completion of the alter and remove the associated version information from the tblspace's header page.

The database server encountered an internal error when attempting to alter a table.

Online log: Assertion Warning with problem details, table and database information, and a specific oncheck command to run.

Server state: Online.

User action: Review the online.log file for information and run the specified oncheck command.

Class ID:

1

Event ID:

1038

3 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

An internal error was reported by the database server when it detected a buffer inconsistency.

The database server encountered an internal error during a consistency check of the internal buffers it was manipulating.

Online log: Assertion Warning with problem details, table and database information, and a specific oncheck command to run.

Server state: Online.

User action: Retry the original operation. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

1

Event ID:

1039

3 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

An internal error was reported by the database server when it tried to construct a forwarded row into a single tuple.

The database server encountered an internal error when processing rows.

Online log: Assertion Warning with problem details, and table and database information.

Server state: Online.

User action: Review the online.log file for more information. Retry the original operation. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

1

Event ID:

1040

3 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

An internal error was reported by the database server when it tried to read the data from a partition into the set read buffer.

The database server encountered a corrupt record during the process of reading data and was unable to retrieve the data.

Online log: Assertion Warning with details of the error encountered and the database:table involved.

Server state: Online.

User Action: Review the online.log file. Some instances of this error require the attention of IBM Software Support.

Class ID:

1

Event ID:

1041

3 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

An internal error was reported by the database server when it tried to read the data row for a given rowid.

The database server encountered a corrupt record during the process of reading data from an index and was unable to retrieve the data.

Online log: Assertion Warning with details of the error encountered and the database:table involved.

Server state: Online.

User Action: Review the online.log file for information and run the recommended oncheck command. Some instances of this error require the attention of IBM Software Support.

Class ID:

1

Event ID:

1042

3 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

An internal error was reported by the database server when it tried to alter the row in memory to the latest schema.

The database server encountered an internal error while trying to convert an old version of a record to the latest version of the record in an altered table.

Online log: Assertion Warning with details of the error encountered and the database:table involved.

Server state: Online.

User Action: Review the online.log file for more information. Retry the original operation. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

1

Event ID:

1043

3 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

An internal error was reported by the database server when it tried to undo the alter of a bitmap page.

The database server encountered an internal error while trying to revert an operation that had altered an internal bitmap page.

Online log: Assertion Warning with details of the error encountered and the database:table involved.

Server state: Online.

User Action: Review the online.log file for more information and run the recommended oncheck command.

Class ID:

1

Event ID:

1044

3 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

An internal error was reported by the database server when it tried to undo the addition of special column descriptors from the tblspace's header page.

The database server encountered an internal error while trying to revert an operation that had added information to the internal structure that tracks tables.

Online log: Assertion Warning with details of the error encountered and the database:table involved.

Server state: Online.

User Action: Review the online.log file for more information and run the recommended oncheck command.

Class ID:

1

Event ID:

1045

3 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

An internal error was reported by the database server when it tried to undo the addition of the new version to a partition.

The database server encountered an internal error while trying to revert an operation that had added information to the internal structure that tracks tables.

Online log: Assertion Warning with details of the error encountered and the database:table involved.

Server state: Online.

User Action: Review the online.log file for more information and run the recommended oncheck command.

Class ID:

1

Event ID:

1046

3 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

An internal error was reported by the database server when it tried to allocate the file descriptor for a partition number.

The database server encountered an internal error while trying to create a new file descriptor for a table or index.

Online log: Assertion Warning with details of the error encountered and the database:table involved.

Server state: Online.

User Action: Review the online.log file for more information and run the recommended oncheck command.

Class ID:

1

Event ID:

1047

3 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

An internal error was reported by the database server when it tried to free the file descriptor for a partition number.

The database server encountered an internal error while trying to release an internal data structure associated with a table or index.

Online log: Assertion Warning with details of the error encountered and the database:table involved.

Server state: Online.

User Action: None. The database server will internally correct the issue.

Class ID:

1

Event ID:

1048

3 Class message:

Table failure: 'dbname:"owner".tabname'

Specific message:

Error updating table record.

The database server was unable to update a database record for a table that has in-place alters. It was unable to write the new version of the record.

Online log: Assertion Warning with details of the error encountered and the database:table involved.

Server state: Online.

User Action: Review the online.log file for more information and run the recommended oncheck command.

Class ID:

2

Event ID:

2001

3 or 4 Class message:

Index failure: 'dbname:"owner".tabname:idxname'

Specific message:

Fragid fragment_id, Rowid rowid not found for delete in partnum partition_number

The database server did not delete a record because it could not find it in the index.

Online log: Assertion indicating that a DELETE operation failed and details of the table and index where the problem occurred.

Server state: Online.

User action: Run the oncheck -cI command on the specified table and index, or on the database, and correct any errors found. Retry the original operation. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

2

Event ID:

2002

3 Class message:

Index failure: 'dbname:"owner".tabname:idxname'

Specific message:

An internal error was raised due to an inconsistency in the index which is preventing the database server to position on the first record in that index.

The database server detected an inconsistent index and marked it as unusable.

Online log: Assertion Warning with details of the error encountered and the database:table:index involved.

Server state: Online.

User Action: Review the online.log file for more information and run the recommended oncheck command.

Class ID:

2

Event ID:

2003

3 Class message:

Index failure: 'dbname:"owner".tabname:idxname'

Specific message:

An internal error was raised due to an inconsistency in the index which is preventing the database server to read ahead pages in that index.

The database server detected an inconsistent index and marked it as unusable.

Online log: Assertion Warning with details of the error encountered and the database:table:index involved.

Server state: Online.

User Action: Review the online.log file for more information and run the recommended oncheck command.

Class ID:

2

Event ID:

2004

4 Class message:

Index failure: 'dbname:"owner".tabname-idxname'

Specific message:

Page Check Error in object

The database server detected inconsistencies with an index.

Online log: Various messages depending on where the issue was detected. For example: Possible inconsistencies in a DBSpace TBLSpace Run 'oncheck -cD' on all DBSpace TBLSpaces

Server state: Online.

User action: Review the online.log file for more information and run the recommended oncheck -cD command on the database.

Class ID:

2

Event ID:

2005

3 Class message:

Index failure: 'dbname:"owner".tabname:idxname'

Specific message:

An internal error occurred during batched index read because the database server had an invalid index key item.

The database server detected an inconsistent index and marked it as unusable.

Online log: Assertion Warning with details of the error encountered and the database:table:index involved.

Server state: Online.

User Action: Review the online.log file for more information and run the recommended oncheck command.

Class ID:

2

Event ID:

2006

3 Class message:

Index failure: 'dbname:"owner".tabname:idxname'

Specific message:

index_page log record too large to fit into the logical log buffer. Recommended minimum value for LOGBUFF is number.

The server detected that a log record for an index page is too large for the configured logical log buffer size.

Online log: Assertion Warning with details of the error encountered and the database:table:index involved.

Server state: Online.

User Action: Review the online.log file for more information and update the onconfig value for LOGBUFF to the recommended value.

Class ID:

2

Event ID:

2007

3 Class message:

Index failure: 'dbname:"owner".tabname:idxname'

Specific message:

Comparison based on locale 'locale_name' failed

The database server detected an inconsistent index and marked it as unusable.

Online log: Assertion Warning with details of the error encountered and the database:table:index involved.

Server state: Online.

User Action: Review the online.log file for more information and run the recommended oncheck command.

Class ID:

2

Event ID:

2008

3 Class message:

Index failure: 'dbname:"owner".tabname:idxname'

Specific message:

Comparison failed

The database server detected an inconsistent index and marked it as unusable.

Online log: Assertion Warning with details of the error encountered and the database:table:index involved.

Server state: Online.

User Action: Review the online.log file for more information and run the recommended oncheck command.

Class ID:

2

Event ID:

2009

4 Class message:

Index failure: 'dbname:"owner".tabname:idxname'

Specific message:

An internal error occurred while the database server was trying to add a new item to the index.

The database server could not insert a record into an index.

Online log: Assertion specifying the index and the recommended oncheck command to run.

Server state: Online.

User action: Examine the online log file and run the recommended oncheck command.

Class ID:

2

Event ID:

2010

4 Class message:

Index failure: 'dbname:"owner".tabname:idxname'

Specific message:

An internal error was raised due to an inconsistency in the index which is preventing the database server to position at the correct item in the index.

The database server could not retrieve the correct item in the index because of an inconsistency in the index.

Online log: Assertion specifying the index and the recommended oncheck command to run.

Server state: Online.

User action: Examine the online log file and run the recommended oncheck command.

Class ID:

2

Event ID:

2011

3 Class message:

Index failure: 'dbname:"owner".tabname:idxname'

Specific message:

Cannot drop index index_name for partnum partition_number, iserrno = error_number

The database server detected an inconsistent index and marked it as unusable.

Online log: Assertion Warning with details of the error encountered and the database:table:index involved.

Server state: Online.

User Action: Review the online.log file for more information and run the recommended oncheck command. Retry the original operation and if it fails again contact IBM Software Support.

Class ID:

2

Event ID:

2012

3 Class message:

Index failure: 'dbname:"owner".tabname:idxname'

Specific message:

An internal error occurred while the database server was trying to mark an index key descriptor as bad.

The database server detected an inconsistent index and marked it as unusable.

Online log: Assertion Warning with details of the error encountered and the database:table:index involved.

Server state: Online.

User Action: Review the online.log file for more information, run the recommended oncheck command, fix any problems detected, then re-enable the index.

Class ID:

2

Event ID:

2013

4 Class message:

Index failure: 'dbname:"owner".tabname:idxname'

Specific message:

An internal error occurred while the database server was trying to delete an item from the index.

The database server could not delete a record from an index.

Online log: Assertion specifying the index and the recommended oncheck command to run.

Server state: Online.

User action: Examine the online log file and run the recommended oncheck command.

Class ID:

3

Event ID:

3001

3 Class message:

Blob failure: 'dbname:"owner".tabname'

Specific message:

tb_sockid in blob descriptor is corrupted. Current® table is 'dbname:"owner".tabname'

 

Class ID:

3

Event ID:

3002

3 Class message:

Blob failure: 'dbname:"owner".tabname'

Specific message:

Incorrect BLOB stamps.

 

Class ID:

3

Event ID:

3003

4 Class message:

Blob failure: 'dbname:"owner".tabname'

Specific message:

BLOB Page Check error at dbspace_name

The database server performed a check on pages that are moving between disk and memory and the check failed.

Online log: Assertion describing the error.

Server state: Online.

User action: Try the operation again. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

3

Event ID:

3004

3 Class message:

Blob failure: 'dbname:"owner".tabname'

Specific message:

An internal error occurred while trying to read a blob from a table.

 

Class ID:

3

Event ID:

3005

3 Class message:

Blob failure: 'dbname:"owner".tabname'

Specific message:

An internal error occurred while trying to copy a blob from a table.

 

Class ID:

4

Event ID:

4001

4 Class message:

Chunk is offline, mirror is active: chunk_number

Specific message:

I/O error, error_number Chunk 'chunk_number' -- Offline

An error has occurred reading from or writing to a chunk. The database server has taken the chunk offline and switched to performing all I/O operations on the active mirrored chunk.

Online log: Assertion describing the error that occurred.

Server state: Online.

User action: Examine the online log for information and fix the error. Run the onspaces -s command to recover the offline chunk. Retry the original operation. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

4

Event ID:

4002

3 or 4 Class message:

Chunk is offline, mirror is active: chunk_number

Specific message:

An internal error occurred during physical I/O because the chunk was not opened.

The database server cannot access a chunk and switched to performing all I/O operations on the active mirrored chunk.

Online log: Assertion describing the error and information about the chunk where the problem occurred.

Server state: Online.

User action: Examine the online log, fix any errors, and recover the mirror by using the onspaces utility. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

4

Event ID:

4003

3 Class message:

Chunk is offline, mirror is active: chunk_number

Specific message:

I/O error, error_number Chunk 'chunk_number' -- Offline (sanity)

 

Class ID:

4

Event ID:

4004

3 Class message:

Chunk is offline, mirror is active: chunk_number

Specific message:

Chunk failed sanity check

 

Class ID:

4

Event ID:

4005

3 Class message:

Chunk is offline, mirror is active: chunk_number

Specific message:

Mirror Chunk chunk_number added to space 'space_number'. Perform manual recovery.

 

Class ID:

5

Event ID:

5001

4 Class message:

Dbspace is offline: 'dbspace_name'

Specific message:

Chunk chunk_number is being taken OFFLINE.

The database server took a dbspace offline because of an error in accessing a chunk.

Online log: Assertion failure if the dbspace was a critical dbspace, such as the rootdbs. Assertion warning if the dbspace is not critical. Both provide information about the chunk and dbspace being taken offline.

Server state: Online if a non-critical media failure. Offline if a critical media failure.

User action: Examine the online log file and fix the underlying problem that caused the dbspace to be taken offline. You might need to restore the dbspace.

Class ID:

5

Event ID:

5002

4 Class message:

Dbspace is offline: 'dbspace_name'

Specific message:

WARNING! Chunk chunk_number is being taken OFFLINE for testing.

The database server has taken a dbspace offline as a result of an onmode command.

Online log: Assertion warning indicating that the dbspace has been taken offline.

Server state: Online.

User action: None.

Class ID:

6

Event ID:

6016

3 Class message:

Internal subsystem failure: 'message'

Specific message:

Pool not freed. pool name:pool_name, address:address

 

Class ID:

6

Event ID:

6017

4 Class message:

Internal subsystem failure: 'message'

Specific message:

CDR Grouper FanOut thread is aborting

A problem occurred with Enterprise Replication.

Online log: Assertion describing the problem.

Server state: Online.

User action: Follow the instructions in the online log.

Class ID:

6

Event ID:

6018

4 Class message:

Internal subsystem failure: 'message'

Specific message:

CDR Pager: Paging File full: Waiting for additional space in CDR_QDATA_SBSPACE

The storage space of an Enterprise Replication queue is full.

Online log: Assertion describing the problem.

Server state: Online.

User action: Add a chunk to one or more of the sbspaces specified by the CDR_QDATA_SBSPACE configuration parameter.

Class ID:

6

Event ID:

6021

3 Class message:

Internal subsystem failure: 'message'

Specific message:

An internal error was reported by the database server during conversion when it found some indices in the old format.

 

Class ID:

6

Event ID:

6022

3 Class message:

Internal subsystem failure: 'message'

Specific message:

An internal error was reported by the database server when it checks for any new in-place alter pending in the current server during reversion.

 

Class ID:

6

Event ID:

6023

3 Class message:

Internal subsystem failure: 'message'

Specific message:

Cannot open index 'dbname:index_name', iserrno = error_number

 

Class ID:

6

Event ID:

6024

3 Class message:

Internal subsystem failure: 'message'

Specific message:

Cannot drop index 'dbname:index_name', iserrno = error_number

 

Class ID:

6

Event ID:

6025

3 Class message:

Internal subsystem failure: 'message'

Specific message:

Cannot open table 'dbname:table_name', iserrno = error_number

 

Class ID:

6

Event ID:

6026

3 Class message:

Internal subsystem failure: 'message'

Specific message:

Cannot drop table 'dbname:table_name', iserrno = error_number

 

Class ID:

6

Event ID:

6027

3 Class message:

Internal subsystem failure: 'message'

Specific message:

An error was reported by the database server when it tried to drop the sysmaster database during reversion

 

Class ID:

6

Event ID:

6030

3 Class message:

Internal subsystem failure: 'message'

Specific message:

Invalid or missing name for Subsystem Staging BLOBspace

 

Class ID:

6

Event ID:

6033

5 Class message:

Internal subsystem failure: 'message'

Specific message:

Cache read error

The database server shut down after encountering an error while reading an internal cache.

Online log: Assertion Failure.

Server State: Offline.

User action: Start the database server and try the operation again. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

6

Event ID:

6034

3 Class message:

Internal subsystem failure: 'message'

Specific message:

Could not start remote server

 

Class ID:

6

Event ID:

6035

3 Class message:

Internal subsystem failure: 'message'

Specific message:

An error was reported by the database server during the handling of audit trail files.

 

Class ID:

6

Event ID:

6036

3 Class message:

Internal subsystem failure: 'message'

Specific message:

Archive on dbspaces_list ABORTED

 

Class ID:

6

Event ID:

6037

3 Class message:

Internal subsystem failure: 'message'

Specific message:

Waiting on BLOBSpace to appear for Logical Recovery

 

Class ID:

6

Event ID:

6038

3 Class message:

Internal subsystem failure: 'message'

Specific message:

An internal error reported by the database server. Users may need to look at the specific message which accompanies with this id.

 

Class ID:

6

Event ID:

6039

3 Class message:

Internal subsystem failure: 'message'

Specific message:

Wrong page for cleaning deleted items

 

Class ID:

6

Event ID:

6040

3 Class message:

Internal subsystem failure: 'message'

Specific message:

Buffer in wrong state for cleaning deleted items

 

Class ID:

6

Event ID:

6041

5 or 3 Class message:

Internal subsystem failure: 'message'

Specific message:

An internal error was detected by the Buffer Manager in the database server.

For severity 5, the database server buffer manager encountered an internal error and either shut down or corrected the problem.

Online log: Assertion warning or an assertion failure with a description of the operation being performed at the time of the error. Typically, an assertion warning shows that the error was internally corrected.

Server State: Offline if the error was unrecoverable. Online if the error was corrected.

User action: If the error was unrecoverable, start the database server and try the operation again. If the operation fails again, note all circumstances and contact IBM Software Support. No action is required if the error was internally corrected by the database server.

Class ID:

6

Event ID:

6042

5 or 2 Class message:

Internal subsystem failure: 'message'

Specific message:

An internal error was reported by the database server when it detected an inconsistency with the internal buffer queues.

For severity 5, the database server detected an inconsistency during the processing of internal buffer queues and either shut down or corrected the problem.

Online log: Assertion warning or an assertion failure with a description of the operation being performed at the time of the error. Typically, an assertion warning shows that the error was internally corrected.

Server State: Offline if the error was unrecoverable. Online if the error was corrected.

User action: If the error was unrecoverable, start the database server and try the operation again. If the operation fails again, note all circumstances and contact IBM Software Support. No action is required if the error was internally corrected by the database server.

Class ID:

6

Event ID:

6043

3 Class message:

Internal subsystem failure: 'message'

Specific message:

Internal file error

 

Class ID:

6

Event ID:

6044

3 Class message:

Internal subsystem failure: 'message'

Specific message:

An internal error was corrected automatically by the database server when it tried to save the log buffer into a system log buffer.

 

Class ID:

6

Event ID:

6045

5 Class message:

Internal subsystem failure: 'message'

Specific message:

Logical logging error for 'object' in 'space'

The database server shut down because of an error while processing logical logs.

Online log: Assertion failure with a description of the operation and logical log information.

Server State: Offline.

User action: Start the database server. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

6

Event ID:

6046

4 Class message:

Internal subsystem failure: 'message'

Specific message:

Page Check Error in object

The database server detected inconsistencies in the data.

Online log: Various outputs depending upon where the issue was detected. For example: Possible inconsistencies in a DBSpace TBLSpace Run 'oncheck -cD' on all DBSpace TBLSpaces

Server state: Online.

User action: Examine the online log file and run the recommended oncheck -cD command on the database.

Class ID:

6

Event ID:

6047

3 Class message:

Internal subsystem failure: 'message'

Specific message:

Errors occurred while recreating indexes

 

Class ID:

6

Event ID:

6049

5 Class message:

Internal subsystem failure: 'message'

Specific message:

Lock types lock_type and lock_type should never be merged

The database server shut down after attempting to merge incompatible locks.

Online log: Assertion failure with the lock types that the database server was attempting to merge.

Server State: Offline.

User action: Start the database server. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

6

Event ID:

6050

5 Class message:

Internal subsystem failure: 'message'

Specific message:

An internal error was reported by the database server when it detected some corruption in the lock free list chain.

The database server shut down after detecting corruption of an internal structure that manages an internal list of free locks.

Online log: Assertion failure.

Server State: Offline.

User action: Start the database server. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

6

Event ID:

6051

3 Class message:

Internal subsystem failure: 'message'

Specific message:

ERROR - NO 'waitfor' locks in Critical Section!!!

 

Class ID:

6

Event ID:

6052

3 Class message:

Internal subsystem failure: 'message'

Specific message:

Internal Tblspace error

 

Class ID:

6

Event ID:

6053

3 Class message:

Internal subsystem failure: 'message'

Specific message:

Session does not have exclusive access to partition partition_name. Request to drop the partition ignored.

 

Class ID:

6

Event ID:

6054

3 Class message:

Internal subsystem failure: 'message'

Specific message:

Error building 'sysmaster' database.

 

Class ID:

6

Event ID:

6055

3 Class message:

Internal subsystem failure: 'message'

Specific message:

Setread error on SMI Table, partnum partition_number

 

Class ID:

6

Event ID:

6056

3 Class message:

Internal subsystem failure: 'message'

Specific message:

Comparison based on locale 'locale_name' failed

 

Class ID:

6

Event ID:

6057

2 Class message:

Internal subsystem failure: 'message'

Specific message:

DBSPACETEMP internal list not initialized, using default

The database server did not create the necessary structures for holding the DBSPACETEMP information.

Online log: Message stating that the internal DBSPACETEMP list was not initialized.

Server state: Online.

User action: None.

Class ID:

6

Event ID:

6058

3 Class message:

Internal subsystem failure: 'message'

Specific message:

A data source accessed using a gateway (gateway_name) might be in an inconsistent state

 

Class ID:

6

Event ID:

6059

3 Class message:

Internal subsystem failure: 'message'

Specific message:

Prepared participant site site_name not responding

 

Class ID:

6

Event ID:

6060

5 Class message:

Internal subsystem failure: 'message'

Specific message:

Thread exited with number buffers held

The database server shut down after detecting that a thread is holding one or more buffers.

Online log: Assertion failure with the number of buffers being held by the thread.

Server State: Offline.

User action: Bring the database server online. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

6

Event ID:

6061

3 Class message:

Internal subsystem failure: 'message'

Specific message:

An internal error was automatically corrected by the database server when it detected that the undo log for the transaction was not applicable.

 

Class ID:

6

Event ID:

6062

3 Class message:

Internal subsystem failure: 'message'

Specific message:

Internal Error - Freeing transaction entry that still holds locks!

While freeing resources associated with a transaction, the database server detected that the transaction is holding locks. In most circumstances the database server can release these locks.

Online log: Assertion warning with the transaction and a statement that the database server internally corrected the problem.

Server State: Online.

User action: If the database server shut down, start the database server.

Class ID:

6

Event ID:

6063

3 Class message:

Internal subsystem failure: 'message'

Specific message:

User thread not on TX wait list

 

Class ID:

6

Event ID:

6064

3 Class message:

Internal subsystem failure: 'message'

Specific message:

Due to a heuristic decision, the work done on behalf of the specified transaction branch might have been heuristically completed or committed or rolled back or partially committed and partially rolled back.

 

Class ID:

6

Event ID:

6065

3 Class message:

Internal subsystem failure: 'message'

Specific message:

Errors occurred while recreating indexes

 

Class ID:

6

Event ID:

6066

3 Class message:

Internal subsystem failure: 'message'

Specific message:

An internal error is reported by the database server when it has checked all sites to see if a heuristic rollback was the reason for the failure.

 

Class ID:

6

Event ID:

6067

5 Class message:

Internal subsystem failure: 'message'

Specific message:

A fatal internal error (Recursive exception) has caused the database server processes to terminate unexpectedly.

The database server detected recursive calls to exception handling and immediately shut down to avoid an infinite loop.

Online log: Assertion failure.

Server State: Offline.

User action: Start the database server. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

6

Event ID:

6068

5 Class message:

Internal subsystem failure: 'message'

Specific message:

A fatal internal error (Internal exception) has caused the database server processes to terminate unexpectedly.

The database server shut down due to an unrecoverable internal error.

Online log: Assertion failure with information about the exception that caused the problem.

Server State: Offline.

User action: Start the database server. Look at the exception information in the assertion failure file. If the exception relates to a user-defined routine, investigate and correct the user-defined routine. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

6

Event ID:

6069

5 Class message:

Internal subsystem failure: 'message'

Specific message:

A fatal internal error (Master daemon died) has caused the database server processes to terminate unexpectedly.

The master daemon oninit process stopped and the database server shut down. This error can be caused by the termination of operating system processes.

Online log: Assertion failure.

Server State: Offline.

User action: Start the database server. Be careful when terminating operating system processes.

Class ID:

6

Event ID:

6070

5 Class message:

Internal subsystem failure: 'message'

Specific message:

A fatal internal error (VP died) has caused the database server processes to terminate unexpectedly.

An oninit process stopped and the database server shut down. This error can be caused by the termination of operating system processes.

Online log: Assertion failure.

Server State: Offline.

User action: Start the database server. Be careful when terminating operating system processes.

Class ID:

6

Event ID:

6071

5 Class message:

Internal subsystem failure: 'message'

Specific message:

ERROR: can not fork secondary Server thread (MACH11 Shutdown)

The secondary server shut down but was unable to create a thread to shut down normally.

Online log: DR: Shutting down the server. ERROR: can not fork secondary Server thread (MACH11 Shutdown) Can not run onmode -ky PANIC: Attempting to bring system down.

Server State: Offline.

User action: None.

Class ID:

6

Event ID:

6072

3 Class message:

Internal subsystem failure: 'message'

Specific message:

Generic unique event id when the server failed to fork a new thread.

 

Class ID:

6

Event ID:

6073

3 Class message:

Internal subsystem failure: 'message'

Specific message:

An error was reported by the database server when it could not initialize GLS for starting a session.

 

Class ID:

6

Event ID:

6074

3 Class message:

Internal subsystem failure: 'message'

Specific message:

WARNING: mt_aio_wait: errno == EINVAL

 

Class ID:

6

Event ID:

6075

5 Class message:

Internal subsystem failure: 'message'

Specific message:

A fatal internal error (KAIO) has caused the database server processes to terminate unexpectedly.

The database server shut down because of an error in the KAIO subsystem.

Online log: Assertion failure with the specific operation that failed.

Server State: Offline.

User action: Start the database server. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

6

Event ID:

6100

  Generic event for when the database server implicitly raises an assert warning. A generic internal error occurred.

Online log: Assertion warning with problem details.

Server State: Online.

User action: Look at the online log and take any recommended corrective action. The database server might correct the problem automatically. Try the operation again. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

6

Event ID:

6300

  Generic event for when the database server implicitly raises an assert failure. A generic internal error occurred.

Online log: Assertion failure with problem details.

Server State: Online.

User action: Look at the online log and take any recommended corrective action. Try the operation again. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

6

Event ID:

6500

  Generic event for when the database server terminates unexpectedly due to an internal error condition. An internal error occurred and the database server shut down.

Online log: Assertion failure.

Server State: Offline.

User action: Start the database server. Examine the assertion failure file for more information about what happened. If possible, fix any problems identified and try the operation again. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

7

Event ID:

7001

3 Class message:

Database server initialization failure

Specific message:

TABLOCKS log record too large to fit into the logical log buffer. Recommended minimum value for LOGBUFF is size.

I-STAR(C) begins prepare log record too large to fit into the logical log buffer. Recommended minimum value for LOGBUFF is size.

Partition blob log record too large to fit into the logical log buffer. Recommended minimum value for LOGBUFF is size.

Alter table special column desc log record too large to fit into the logical log buffer. Recommended minimum value for LOGBUFF is size.

 

Class ID:

7

Event ID:

7002

4 Class message:

Database server initialization failure

Specific message:

Unable to extend number reserved pages for checkpoint in ROOT chunk.

Unable to extend number reserved pages for log in ROOT chunk.

The database server could not start because it could not allocate more space for internal structures in the initial root chunk.

Online log: Assertion.

Server state: Offline.

User action: Try the operation again. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

7

Event ID:

7003

4 Class message:

Database server initialization failure

Specific message:

An internal error occurred during conversion. Users may need to take a look at the specific messages for further action.

The database server could not start during an upgrade because an internal error occurred during the conversion process.

Online log: Assertion describing the error.

Server state: Offline.

User action: Look at the online log and the specific message and take the necessary corrective action. Try the operation again. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

7

Event ID:

7004

4 Class message:

Database server initialization failure

Specific message:

An internal error occurred while trying to convert the database tblspace.

The database server cannot start because of an internal error when trying to convert the database tblspace, which holds information about the databases in the instance.

Online log: Assertion describing the error.

Server state: Offline.

User action: Contact IBM Software Support.

Class ID:

7

Event ID:

7005

4 Class message:

Database server initialization failure

Specific message:

An internal error occurred while trying to convert blob free map pages.

The database server cannot start because of an internal error when trying to convert blobspace free-map pages.

Online log: Assertion describing the error.

Server state: Offline.

User action: Contact IBM Software Support.

Class ID:

7

Event ID:

7006

4 Class message:

Database server initialization failure

Specific message:

Cannot Open Logical Log.

The database server cannot start because it is still restoring physical or logical logs. This situation can occur if the onmode -m or onmode -s command is run before the restore is complete.

Online log: Assertion describing the error.

Server state: Recovering and starting.

User action: Run the onmode -m or onmode -s command after the restore is complete.

Class ID:

7

Event ID:

7007

4 Class message:

Database server initialization failure

Specific message:

Logical Log File not found.

The database server cannot start because a logical log file is missing.

Online log: Assertion describing the error.

Server state: Offline.

User action: Restore the database server from a backup.

Class ID:

7

Event ID:

7008

3 Class message:

Database server initialization failure

Specific message:

WARNING! LTXHWM is set to 100%. This long transaction high water mark will never be reached. Transactions will not be aborted automatically by the server, regardless of their length.

 

Class ID:

7

Event ID:

7009

4 Class message:

Database server initialization failure

Specific message:

A Physical or Logical Restore is active.

The database server cannot start because it is still restoring physical or logical logs. This situation can occur if the onmode -m or onmode -s command is run before the restore is complete.

Online log: Assertion describing the error.

Server state: Recovering and starting.

User action: Run the onmode -m or onmode -s command after the restore is complete.

Class ID:

7

Event ID:

7010

4 Class message:

Database server initialization failure

Specific message:

root_dbspace has not been physically recovered.

The database server cannot start because the restore was interrupted before the rootdbs was physically restored.

Online log: Assertion describing the error.

Server state: Offline.

User action: Restore the rootdbs.

Class ID:

7

Event ID:

7011

4 Class message:

Database server initialization failure

Specific message:

dbspace has not been physically recovered.

The database cannot start because a dbspace is not physically restored. This situation can occur if the database server is attempted to be started before a restore is complete.

Online log: Assertion describing the error.

Server state: Offline.

User action: Wait until the restore is complete before starting the database server.

Class ID:

7

Event ID:

7012

4 Class message:

Database server initialization failure

Specific message:

dbspace not recovered from same archive backup as dbspace.

The database server cannot start because a dbspace was not restored successfully.

Online log: Assertion describing the error.

Server state: Offline.

User action: Recover the dbspace from a backup and roll forward the necessary logs to bring the dbspace to the correct point in time.

Class ID:

7

Event ID:

7013

4 Class message:

Database server initialization failure

Specific message:

Log log_number not found.

The database server cannot start because a restore is not complete.

Online log: Assertion describing the error.

Server state: Offline.

User action: Wait until the restore is complete before starting the database server.

Class ID:

7

Event ID:

7014

4 Class message:

Database server initialization failure

Specific message:

Logical restore cannot be skipped. Perform a logical restore.

The database server cannot start because a logical restore is not complete.

Online log: Assertion describing the error.

Server state: Offline.

User action: Perform a logical restore (for example, by using the onbar -r -l command) and start the database server in quiescent or online mode.

Class ID:

7

Event ID:

7015

4 Class message:

Database server initialization failure

Specific message:

Cannot change to On-Line or Quiescent mode.

The database server cannot start because of an error during fast or full recovery.

Online log: Assertion describing the error.

Server state: Offline.

User action: Examine the online log for more information. Try the operation again. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

7

Event ID:

7016

4 Class message:

Database server initialization failure

Specific message:

Cannot Open Primary Chunk 'chunk_number'.

The database server cannot start because it could not access a primary chunk.

Online log: Assertion describing the error.

Server state: Offline.

User action: Examine the online log for more information. Try the operation again. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

7

Event ID:

7017

4 Class message:

Database server initialization failure

Specific message:

The chunk 'chunk_number' must have owner-ID "owner_id" and group-ID "group_id".

The database server cannot start because the owner and group of a chunk path are not correct.

Online log: Assertion describing the problem.

Server state: Offline.

User action: Correct the permissions on the chunk path mentioned in the specific message. Try the operation again. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

7

Event ID:

7018

4 Class message:

Database server initialization failure

Specific message:

The chunk 'chunk_number' must have READ/WRITE permissions for owner and group (660).

The database server cannot start because the permissions on a chunk path are not correct.

Online log: Assertion describing the problem.

Server state: Offline.

User action: Correct the permissions on the chunk path mentioned in the specific message. Try the operation again. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

7

Event ID:

7019

4 Class message:

Database server initialization failure

Specific message:

Memory allocation error.

The database server cannot start because it failed to allocate enough memory.

Online log:

Server state: Offline.

User action: Ensure that enough memory is available for the configuration you have specified for the database server. Try the operation again. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

7

Event ID:

7020

4 Class message:

Database server initialization failure

Specific message:

The chunk 'chunk_number' will not fit in the space specified.

The database server cannot start because there is insufficient space to create the specified chunk.

Online log: Assertion describing the problem.

Server state: Offline.

User action: Specify a smaller size for the chunk or free additional space for the chunk.

Class ID:

7

Event ID:

7021

4 Class message:

Database server initialization failure

Specific message:

device_name: write failed, file system is full.

The database server cannot start because the file system does not have free space.

Online log: Assertion describing the problem.

Server state: Offline.

User action: Ensure the file system mentioned in the specific message has enough space. Retry the original operation. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

7

Event ID:

7022

3 Class message:

Database server initialization failure

Specific message:

An error occurred while the database server was creating the SMI database.

 

Class ID:

7

Event ID:

7023

4 Class message:

Database server initialization failure

Specific message:

Unable to create boot strap config file - 'file_name'

The database server cannot start because it could not create a configuration file.

Online log: Assertion describing the error.

Server state: Offline.

User action: Examine the online log for more information and fix the problem. The problem might be incorrect permissions on a directory. Retry the original operation. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

7

Event ID:

7024

3 Class message:

Database server initialization failure

Specific message:

'sysmaster' database will not be built/checked

 

Class ID:

7

Event ID:

7025

3 Class message:

Database server initialization failure

Specific message:

WARNING! Physical Log size size is too small. Physical Log overflows may occur during peak activity. Recommended minimum Physical Log size is number times maximum concurrent user threads.

 

Class ID:

7

Event ID:

7026

3 Class message:

Database server initialization failure

Specific message:

WARNING! Logical log layout may cause __ISN__ to get into a locked state. Recommended smallest logical log size is number times maximum concurrent user threads.

 

Class ID:

7

Event ID:

7027

3 Class message:

Database server initialization failure

Specific message:

WARNING! Buffer pool size may cause __ISN__ to get into a locked state. Recommended minimum buffer pool size is number times maximum concurrent user threads.

 

Class ID:

7

Event ID:

7028

3 Class message:

Database server initialization failure

Specific message:

Checkpoint log record may not fit into the logical log buffer. Recommended minimum value for LOGBUFF is size.

 

Class ID:

7

Event ID:

7029

3 Class message:

Database server initialization failure

Specific message:

Temp transaction not NULL.

 

Class ID:

9

Event ID:

9001

4 Class message:

Physical recovery failure

Specific message:

Physical log recovery error

The physical recovery of the database server failed.

Online log: Assertion failure with a description of the problem.

Server state: Online.

User action: Retry the operation or restore from a backup.

Class ID:

10

Event ID:

10001

3 or 4 Class message:

Logical recovery failure

Specific message:

Rollback error error_number

Logical recovery failed because the database server could not roll back a transaction.

Online log: Assertion with details of the error and the log or log record where the problem occurred.

Server state: Online or offline, depending on the error.

User action: Examine the online log file for more information and run any recommended commands, such as an oncheck command. Retry the original operation. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

10

Event ID:

10002

4 Class message:

Logical recovery failure

Specific message:

Logical Recovery ABORTED.

The logical recovery of the database server failed.

Online log: Assertion warning with information about the log record. Assertion failure with information about the log record if the failure is associated with a critical dbspace.

Server state: Online if the dbspace is not critical. Offline if the dbspace is critical.

User action: Examine the online log to determine the appropriate action, for example, you might need to restart the warm restore.

Class ID:

10

Event ID:

10003

4 Class message:

Logical recovery failure

Specific message:

Log record (log_subsystem:log_type) in log log_number, offset log_position was not rolled back

Logical recovery encountered an internal error while rolling back a transaction.

Online log: Message describing the log record.

Server state: Online.

User action: Examine the online log and determine the appropriate action, for example, resubmit the transaction.

Class ID:

10

Event ID:

10004

3 Class message:

Logical recovery failure

Specific message:

Logical Logging error for 'log_subsystem:log_type' in 'object'

 

Class ID:

10

Event ID:

10005

4 Class message:

Logical recovery failure

Specific message:

An internal error occurred while trying to apply the log records during logical log recovery.

Logical recovery failed.

Online log: Assertion warning with information about the log record.

Server state: Depends on the failure.

User action: Examine the online log and determine the appropriate action, for example, restart the warm restore.

Class ID:

10

Event ID:

10006

3 or 4 Class message:

Logical recovery failure

Specific message:

An internal error occurred when the database server tried to find the file descriptor for the tblspace.

Logical recovery failed because the database server could not find an internal file descriptor for a partition.

Online log: Assertion indicating for which table the error occurred and instructions to run the oncheck command.

Server state: Online.

User action: Run the oncheck -cDI command for the table mentioned in the online log or for the database.

Class ID:

11

Event ID:

11001

3 Class message:

Cannot open chunk: 'pathname'

Specific message:

Cannot Open Mirror Chunk 'chunk_number', errno = error_number

 

Class ID:

11

Event ID:

11002

3 Class message:

Cannot open chunk: 'pathname'

Specific message:

Cannot Open Primary Chunk 'chunk_number', errno = error_number

 

Class ID:

12

Event ID:

12001

3 Class message:

Cannot open dbspace: 'dbspace_name'

Specific message:

ERROR: DBspace dbspace_name not found among table table_name fragments.

 

Class ID:

13

Event ID:

13001

2 Class message:

Performance improvement possible

Specific message:

The number of configured CPU poll threads exceeds number of CPU VPs specified in 'VPCLASS cpu'. NETTYPE 'protocol' poll threads started on NET VPs.

The database server detected a configuration mismatch between the number of CPU virtual processors and the number of requested CPU poll threads during server initialization.

Online log: Performance warning about the configuration mismatch. The database server uses NET virtual processors instead.

Server state: Online.

User action: Check the configuration of the server.

Class ID:

13

Event ID:

13002

2 Class message:

Performance improvement possible

Specific message:

Transaction table overflow due to parallel recovery.

An internal structure is not large enough to process the logical log. The database server will postpone the log processing until more space exists within the structure.

Online log: Warning message indicating that the transaction processing was delayed.

Server state: Online.

User action: None.

Class ID:

14

Event ID:

14001

3 Class message:

Database failure. 'dbname'

Specific message:

''dbname'' - Error error_number during logging mode change.

 

Class ID:

15

Event ID:

15001

3 Class message:

High-Availability Data-Replication failure

Specific message:

DR: Turned off on secondary server

 

Class ID:

15

Event ID:

15002

3 Class message:

High-Availability Data-Replication failure

Specific message:

DR: Turned off on primary server

 

Class ID:

15

Event ID:

15003

3 Class message:

High-Availability Data-Replication failure

Specific message:

DR: Cannot connect to secondary server

 

Class ID:

15

Event ID:

15004

3 Class message:

High-Availability Data-Replication failure

Specific message:

DR: Received connection request from remote server when DR is not Off

[Local type: type, Current state: state]

[Remote type: type]

 

Class ID:

15

Event ID:

15005

3 Class message:

High-Availability Data-Replication failure

Specific message:

DR: Received connection request before physical recovery completed.

 

Class ID:

15

Event ID:

15006

3 Class message:

High-Availability Data-Replication failure

Specific message:

DR: Local and Remote server type and/or last change (LC) incompatible

[Local type: type, LC: type]

[Remote type: type, LC: type]

 

Class ID:

16

Event ID:

16001

2 Class message:

Backup completed: 'dbspace_list'

Specific message:

Archive on dbspace_list completed without being recorded.

An archive completed, but the server detected corrupted pages during the archive.

Online log: Message indicating that the backup is complete but that corrupted pages have been detected.

Server state: Online.

User action: Do not use this backup. Use an earlier backup to immediately restore the bad chunks.

Class ID:

16

Event ID:

16002

2 Class message:

Backup completed: 'dbspace_list'

Specific message:

Archive on dbspace_list Completed with number corrupted pages detected.

An archive completed, but the server detected corrupted pages during the archive.

Online log: Message indicating that the backup is complete but that corrupted pages have been detected.

Server state: Online.

User action: Do not use this backup. Use an earlier backup with 0 bad pages to immediately restore the bad chunks.

Class ID:

16

Event ID:

16003

2 Class message:

Backup completed: 'dbspace_list'

Specific message:

Archive on dbspace_list Completed

An archive completed for the dbspaces listed.

Online log: Message indicating that the backup is complete for the dbspaces listed.

Server state: Online.

User action: None.

Class ID:

17

Event ID:

17001

4 Class message:

Backup aborted: 'dbspace_list'

Specific message:

Archive detects that page chunk_number:page_offset is corrupt.

The database server detected corruption and stopped the backup.

Online log: Assertion describing the problem.

Server state: Online.

User action: Examine the online log for information about the corruption. Try the operation again. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

17

Event ID:

17002

3 Class message:

Backup aborted: 'dbspace_list'

Specific message:

Page %d:%d of partition partition_number not archived.

 

Class ID:

18

Event ID:

18001

2 Class message:

Log backup completed: log_number

Specific message:

Logical Log log_number - Backup Completed

The logical log was backed up.

Online log: Message identifying the log number of the backed up logical log.

Server state: Online.

User action: None.

Class ID:

19

Event ID:

19001

3 Class message:

Log backup aborted: log_number

Specific message:

Logical Log log_number - Backup Aborted message

 

Class ID:

20

Event ID:

20001

3 Class message:

Logical logs are full—backup is needed

Specific message:

Logical Log Files are Full -- Backup is Needed

 

Class ID:

20

Event ID:

20002

3 Class message:

Logical logs are full—backup is needed

Specific message:

Waiting for Next Logical Log File to be Freed

 

Class ID:

20

Event ID:

20003

3 Class message:

Logical logs are full—backup is needed

Specific message:

Logical Log Files are almost Full -- Backup is Needed.

In Data replication scenario, this could block failure-recovery of the paired server.

 

Class ID:

21

Event ID:

21001

3 Class message:

Database server resource overflow: 'resource_name'

Specific message:

Archive arcbu_next_tbuf() – Buffer Overflow

 

Class ID:

21

Event ID:

21002

3 Class message:

Database server resource overflow: 'resource_name'

Specific message:

Archive tcp_logbu_hdr() – Buffer Overflow

 

Class ID:

21

Event ID:

21003

3 Class message:

Database server resource overflow: 'resource_name'

Specific message:

Archive tcp_logbu_trl() – Buffer Overflow

 

Class ID:

21

Event ID:

21004

2 or 5 Class message:

Database server resource overflow: 'resource_name'

Specific message:

Physical log file overflow

For severity 5, the physical log file is full and needs to overflow. If this happens during recovery, the database server attempts to extend the physical log.

Online log: Assertion failure if the database server is either not in recovery or is unable to extend the physical log. Assertion warning if the database server is in recovery and extends the physical log.

Server State: Offline.

User action: None.

Class ID:

21

Event ID:

21005

3 Class message:

Database server resource overflow: 'resource_name'

Specific message:

Lock table overflow - user id %d, session id %d

 

Class ID:

21

Event ID:

21006

5 Class message:

Database server resource overflow: 'resource_name'

Specific message:

Logical log buffer overflow detected

The database server shut down because the logical log buffer is full.

Online log: Assertion failure with the log record size and the buffer size.

Server State: Offline.

User action: Increase the value of the LOGBUFF configuration parameter in the onconfig file. Start the database server.

Class ID:

21

Event ID:

21007

3 Class message:

Database server resource overflow: 'resource_name'

Specific message:

Llog logbu_logfile() – Buffer Overflow

 

Class ID:

21

Event ID:

21008

3 Class message:

Database server resource overflow: 'resource_name'

Specific message:

Llog logbu_bpage() – Buffer Overflow

 

Class ID:

21

Event ID:

21009

3 Class message:

Database server resource overflow: 'resource_name'

Specific message:

Unable to allocate a user thread for user id user_ID

 

Class ID:

21

Event ID:

21010

3 Class message:

Database server resource overflow: 'resource_name'

Specific message:

Unable to allocate a transaction for user id user_ID, session id session_ID

 

Class ID:

21

Event ID:

21014

3 Class message:

OnLine resource overflow: Locks;

Specific message:

SID='session id' User ID='uid' NAME='user name' PID='process id'

The lock limit within this session is reached. The current transaction is terminated.

Online log: Session session id has exceeded the session limit of number locks.

Server state: Online

User action: Reduce your transaction size.

Class ID:

21

Event ID:

21016

3 Class message:

OnLine resource overflow: Memory;

Specific message:

Session info: 'session id username@hostname' pid 'pid'

The memory limit within this session is reached. The current session is terminated.

Online log: Session session id has exceeded the session limit of size of memory.

Server state: Online

User action: Reduce session memory consumption.

Class ID:

21

Event ID:

21017

3 Class message:

OnLine resource overflow: Tempspace;

Specific message:

Session info: 'session id username@hostname' pid 'pid'

The temporary space limit within this session is reached. The current session is terminated.

Online log: Session session id has exceeded the session limit of size of temporary space.

Server state: Online

User action: Reduce your data size.

Class ID:

21

Event ID:

21018

3 Class message:

OnLine resource overflow: Log Space;

Specific message:

Session info: 'session id username@hostname' pid 'pid'

The log space limit within this session is reached. The current transaction is terminated.

Online log: Session session id has exceeded the session limit of size of log space.

Server state: Online

User action: Reduce your transaction size.

Class ID:

21

Event ID:

21019

3 Class message:

OnLine resource overflow: Transaction Time;

Specific message:

Session info: 'session id username@hostname' pid 'pid'

The transaction time limit within this session is reached. The current session is terminated.

Online log: Session session id has exceeded the session limit of seconds of transaction time.

Server state: Online

User action: Reduce idle time for open transactions.

Class ID:

22

Event ID:

22001

3 Class message:

Long transaction detected

Specific message:

Blocking on XA transaction, tx transaction_number, till it is cleaned up.

 

Class ID:

22

Event ID:

22002

3 Class message:

Long transaction detected

Specific message:

Continuing Long Transaction (for COMMIT): tx:

 

Class ID:

22

Event ID:

22003

3 Class message:

Long transaction detected

Specific message:

Aborting Long Transaction: tx:

 

Class ID:

23

Event ID:

23001

2 Class message:

Logical log 'number' complete

Specific message:

Logical Log log_number Complete, timestamp: timestamp.

The logical log is full, and no more transactions can be written to it.

Online log: Message indicating that the logical log is full.

Server state: Online.

User action: None.

Class ID:

24

Event ID:

24001

3 Class message:

Unable to allocate memory

Specific message:

Generic unique event id when the server failed to allocate memory for starting a new thread.

 

Class ID:

24

Event ID:

24002

3 Class message:

Unable to allocate memory

Specific message:

Warning: unable to allocate requested big buffer of size size

 

Class ID:

24

Event ID:

24003

3 Class message:

Unable to allocate memory

Specific message:

The database server tried to allocate a shared memory virtual segment before it was actually needed, in accordance with the setting of the SHMVIRT_ALLOCSEG configuration parameter - but the segment could not be added. Next failure message will be printed in 30 minutes.

 

Class ID:

24

Event ID:

24004

3 Class message:

Unable to allocate memory

Specific message:

out of message shared memory

 

Class ID:

24

Event ID:

24005

3 Class message:

Unable to allocate memory

Specific message:

out of message shared memory

 

Class ID:

24

Event ID:

24006

3 Class message:

Unable to allocate memory

Specific message:

out of virtual shared memory

 

Class ID:

24

Event ID:

24007

3 Class message:

Unable to allocate memory

Specific message:

No memory available for page cleaners

 

Class ID:

24

Event ID:

24008

3 Class message:

Unable to allocate memory

Specific message:

kysearch(): Memory allocation error

 

Class ID:

24

Event ID:

24009

3 Class message:

Unable to allocate memory

Specific message:

Lock table overflow - user id user_ID, session id session_ID

 

Class ID:

24

Event ID:

24010

3 Class message:

Unable to allocate memory

Specific message:

Unable to allocate a user thread for user id user_ID

 

Class ID:

24

Event ID:

24011

3 Class message:

Unable to allocate memory

Specific message:

Unable to allocate a transaction for user id user_ID, session id session_ID

 

Class ID:

26

Event ID:

26001

3 Class message:

Dynamically added log file logid

Specific message:

Dynamically added log file logid to DBspace dbspace_name

 

Class ID:

27

Event ID:

27001

4 Class message:

Log file required

Specific message:

ALERT: The oldest logical log (log_number) contains records from an open transaction (transaction_number). Logical logging will remain blocked until a log file is added. Add the log file with the onparams -a command, using the -i (insert) option, as in:

onparams -a -d dbspace -s size -i

Then complete the transaction as soon as possible.

The database server needs an additional log file to continue processing.

Online log: ALERT: The oldest logical log (log_number) contains records from an open transaction (transaction_number). Logical logging will remain blocked until a log file is added. Add the log file with the onparams -a command, using the -i (insert) option, as in: onparams -a -d dbspace -s size -i Then complete the transaction as soon as possible.

Server state: Online.

User action: Add a new logical log.

Class ID:

28

Event ID:

28001

4 Class message:

No space for log file

Specific message:

ALERT: Because the oldest logical log (log_number) contains records from an open transaction (transaction_number), the server is attempting to dynamically add a log file. But there is no space available. Please add a DBspace or chunk. Then complete the transaction as soon as possible.

The database server cannot dynamically add an additional logical log file because not enough space is available.

Online log: Assertion warning indicating that there is not enough space available for an additional logical log file.

Server state: Online.

User action: Add a new logical log file or additional space.

Class ID:

28

Event ID:

28002

4 Class message:

No space for log file

Specific message:

Warning - Enterprise Replication is attempting to dynamically add a log file. But there is no space available. The replay position may overrun.

The database server cannot dynamically add an additional logical log file because not enough space is available.

Online log: Assertion warning indicating that there is not enough space available for an additional logical log file.

Server state: Online.

User action: Add a new logical log file or additional space.

Class ID:

29

Event ID:

29001

2 Class message:

Internal subsystem: subsystem

Specific message:

Skipped existing audit trail files file_name to file_name.

The auditing subsystem needs to change to a new output file.

Online log: Message indicating that the audit file changed, skipping over existing files.

Server state: Online.

User action: None.

Class ID:

30 - 39

2, 3, or 4 Enterprise Replication events. See Enterprise Replication Event Alarms.  

Class ID:

40

Event ID:

40001

3 Class message:

RSS alarm

Specific message:

RSS server_name added

 

Class ID:

40

Event ID:

40002

3 Class message:

RSS alarm

Specific message:

Password for RSS Source server_name changed

 

Class ID:

40

Event ID:

40003

3 Class message:

RSS alarm

Specific message:

RSS server_name deleted

 

Class ID:

40

Event ID:

40004

3 Class message:

RSS alarm

Specific message:

RSS server_name log replay position is falling too far behind RSS Source

 

Class ID:

40

Event ID:

40005

3 Class message:

RSS alarm

Specific message:

RSS server_name is not acknowledging log transmission

 

Class ID:

40

Event ID:

40006

3 Class message:

RSS alarm

Specific message:

Error receiving a buffer from RSS server_name - shutting down

 

Class ID:

40

Event ID:

40007

3 Class message:

RSS alarm

Specific message:

Delay or Stop Apply: I/O write error: error_number error_description.

 

Class ID:

40

Event ID:

40008

3 Class message:

RSS alarm

Specific message:

Delay or Stop Apply: Thread exiting due to error.

 

Class ID:

41

Event ID:

41001

3 Class message:

SDS alarm

Specific message:

ERROR: Removing SDS Node server_name has timed out - removing

 

Class ID:

42

Event ID:

42001

1 Class message:

Event occurred

The database server encountered an error while validating the tablespace page.

Online log: Assertion warning with details of the table.

Server state: Online.

User action: Examine the online log to determine which database.owner.tablename the issue occurred on. Run the oncheck -pt command on the table. Correct any errors identified by the oncheck utility and retry the operation. If the operation fails again, note all circumstances and contact IBM Software Support.

Class ID:

43

Event ID:

43001

3 Class message:

Connection Manager alarm

Specific message:

CM:Session for Connection manager name terminated abnormally

 

Class ID:

43

Event ID:

43002

3 Class message:

Connection Manager alarm

Specific message:

The FOC setting FOC_String for Connection Manager CM_Name does not match the FOC setting for the other Connection Managers that are configured to arbitrate failover for the cluster. If this Connection Manager becomes the active arbitrator, its FOC will not match the previous FOC policy.

 

Class ID:

44

Event ID:

44001

3 Class message:

DBSpace is full: dbspace_name

Specific message:

WARNING: dbspace_type dbspace_name is full

 

Class ID:

45

Event ID:

45001

3 Class message:

partition 'partition_name': no more extents

Specific message:

Partition 'partition_name': No more extents

 

Class ID:

46

Event ID:

46001

3 Class message:

partition 'partition_name': no more pages

Specific message:

Partition 'partition_name: No more pages

 

Class ID:

47 - 71

3 or 4 Enterprise Replication events. See Enterprise Replication Event Alarms.  

Class ID:

72

Event ID:

72001

2 Class message:

Audit trail is switched to a new file.

Specific message:

Audit trail switched to file_name

The auditing subsystem is switching to a new output file.

Online log: Message providing the file name of the new output file.

Server state: Online.

User action: None.

Class ID:

73-77

3 or 4 Enterprise Replication events. See Enterprise Replication Event Alarms.  

Class ID:

78

Event ID:

78001

3 Class message:

The storage pool is empty.

Specific message:

Warning: The storage pool is out of space.

 

Class ID:

79

Event ID:

79001

3 Class message:

Dynamically added chunk chunk_name to space

Specific message:

Dynamically added chunk chunk_name to space 'space_name'

Path: path, offset offset_number kilobytes

Size: size kilobytes

 

Class ID:

80

80001

2 Class message:

A new fragment for table table_name has been added in DBspace dbspace_name.

A new fragment was automatically added to a table because the table grew larger than the size of its existing fragments.

Online log: Message providing the table name and dbspace name.

Server state: Online.

User action: None.

Class ID:

81

Event ID:

81001

4 Class message:

Logical log file or dbspace corruption detected during backup. Loguniq or Dbspace id: ID.

Specific message:

Log Backup detected a corrupted logical log file.

Expected loguniq:pagenum log_number:page_number

Actual loguniq:pagenum log_number:page_number

Log backup continuing but the log backup cannot be used to restore a server.

You should run oncheck and take a level 0 archive.

A backup failed because the database server detected corruption in the logical log file or dbspace.

Online log: Assertion warning.

Server state: Online.

User action: Perform a new level-0 backup.

Class ID:

82

Event ID:

82001

3 Class message:

session ID (thread) network write operation has been blocked for at least 30 minutes, which might indicate an operating system problem

Specific message:

session ID (thread) network write operation has been blocked for at least 30 minutes, which might indicate an operating system problem

 

Class ID:

83

Event ID:

83001

3 Class message:

SDS: Failover aborted - detected primary server is still active.

Specific message:

SDS: Failover aborted - detected primary server is still active.

 
Event ID: 84001 3 Class message:

Generic network failure alarm

Specific message:

Unable to bind to the port (port number or service name) on the host (IP address or host name) for the server (dbservername).

The host name or IP address, the service name, or the port number might be incorrect. The port might already be in use.

Server state: Online, during server startup.

Online log: Assertion warning.

User action: Check the host name or IP address, the service name, and the port number entries in the sqlhosts file. Make that sure that the port is not already in use. Make the necessary changes and restart the server.

Event ID: 86001 3 Class message:

Space has reached its maximum configured size.

Specific msg:

Warning: Space space_name has reached its maximum configured size (size MB).

The extendable storage space is at the configured maximum size and cannot expand further.

Server state: Online

Online log:

User action: No action needed. If you want to increase the maximum size of the storage space, run the admin() or task() SQL administration API function with the modify space sp_sizes argument and specify a new maximum size.

Event ID: 87001 3 Message:

ifxguard utility connected

The ifxguard agent connected to the database server.

Server state: Online

Online log: Message that identifies the agent name.

User action: No action needed.

Event ID: 87002 3 Message:

ifxguard utility disconnected

The ifxguard agent closed the connected to the database server.

Server state: Online

Online log: Message that identifies the agent name.

User action: No action needed. The user session that the agent audited ended.

Event ID: 87003 3 Message:

ifxguard utility has not responded

The ifxguard agent did not connect to the database server during the timeout period.

Server state: Depends on the action set by the IFXGUARD configuration parameter.

Online log: Message that identifies the agent name.

User action: No action needed unless the database server shut down. If the database server shut down, examine the ifxguard log file to discover why the ifxguard agent failed to connect in time.


Copyright© 2019 HCL Technologies Limited