ADM0000-0999

ADM Message ID Message Explanation User Response

ADM0001C

A severe error has occurred. Examine the administration notification log and contact IBM Support if necessary.

ADM0500E

The DB2 Service does not have the necessary authority to complete the command. If a user account has been associated with the DB2 Service, ensure that the user account has the correct access rights on the local system and access to the Domain Security Database for user authentication and group enumeration.

ADM0501C

A stack overflow exception has occurred. The database manager instance has terminated abnormally. To remedy this problem, you may increase the default stack size for db2syscs.exe using the db2hdr utility as follows: db2hdr \sqllib\bin\db2syscs.exe /s:<stackreserve>[,<stackcommit>] Note that increasing the default stack size will consume virtual memory space and may reduce the maximum number of concurrent connections. Contact IBM Support for further assistance.

ADM0502C

The database manager instance has terminated abnormally. To remedy this problem, increase the AGENT_STACK_SZ DBM configuration parameter. Contact IBM Support for further assistance.

ADM0503C

An unexpected internal processing error has occurred. All database manager processes associated with this instance have been shutdown. Diagnostic information has been recorded. Contact IBM Support for further assistance.

ADM0504C

An unexpected internal processing error has occurred. All database manager processes associated with this instance have been suspended. Diagnostic information has been recorded. Contact IBM Support for further assistance.

ADM0505E

The database manager received a SIGDANGER signal from the operating system. This signal indicates that the system is running low on paging space. If the paging space gets too low, the operating system will forcibly terminate user processes. Contact your system administrator to increase your paging space.

ADM0506I

The database manager has automatically updated the parameter kernel parameter from originalValue to the recommended value recommendedValue.

ADM0507W

The database manager could not automatically update the parameter kernel parameter to the recommended value recommendedValue. Update this kernel parameter manually.

ADM0508E

The database manager was unable to load the Java interpreter library libraryPath. This error commonly occurs because of restrictions imposed by the operating system. Consult the IBM documentation for a solution. If this problem persists, contact IBM support.

ADM0509E

A non-root database manager instance has been detected. Limited functionality will be available.

ADM0510E

AGENTPRI configuration variable or Agent Priority Resource Configuration changes are not possible without root capabilities.

ADM0511E

Raw device access using the character device controller has been deprecated by the operating system and might be removed in the future. The database manager processes can access the same device by using the block device interface; however db2relocatedb will need to be run on each individual database to change the name of the affected device in any table space containers and raw log containers.

When working with containers to store data, the database manager supports direct disk (raw) access using the block device interface (that is, raw I/O).

Change the name of the affected device in any table space containers and raw log containers by using the db2relocate command.

ADM0512W

The database manager instance does not have permission to pin a database memory segment. Contact your system administrator to grant permission for the database manager instance owner to pin memory. The database manager will continue to function with unpinned database memory.

ADM0513W

db2start succeeded. However, no I/O completion port (IOCP) is available.

This error is returned when there are no I/O completion ports with status "Available" on the computer where DB2 database is installed. An I/O completion port is an operating system channel for I/O requests. Using I/O completion ports can improve the performance of very large databases.

If you want to use I/O completion ports to improve performance, configure I/O completion ports.

ADM0514W

The system Network Time Protocol (NTP) process was not detected to be up and running or properly synchronized.

To ensure that clock-sensitive operations like error-logging, monitoring and point-in-time recovery run optimally across a distributed environment, it is highly recommended that the Network Time Protocol (NTP) service be running and synchronized to the same system peer across all members.

Ensure that the NTP service is up and running and that all members are synchronized to the same host.

ADM0515W

The system clock on this member is out of synchronization by more than the allowed threshold with member coordinator-member. The differential is timestamp-diff minutes.

Timestamps from each member are periodically compared to ensure that the time discrepancy between members is less than the predefined allowable threshold set by the MAX_TIME_DIFF database manager configuration parameter. The differential between the local system clock on this host and that of the indicated remote member has been detected to exceed this limit.

Verify that the differentials between the system clocks on all members are within the limit specified by MAX_TIME_DIFF.

ADM0516W

CPU binding information: cluster caching facility (CF) processes are bound to number cores.

When a cluster caching facility and a DB2 member coexist on a single host, the CF processes will be assigned to a subset of the total cores available. For more specific information on the logical processors, see the db2diag.log file.

No user response is required.

ADM0517W

CPU binding information: DB2 member processes are bound to number cores.

When a DB2 member and a cluster caching facility (CF) coexist on a single host, the member processes will be assigned to a subset of the total cores available. For more specific information on the logical processors, see the db2diag.log file.

No user response is required.

ADM0518W

The Storage Scale cluster does not have a port range defined for the tscCmdPortRange setting in a Firewall enabled environment.