As described in that information, the customer can get a good idea of how many of the IBM HTTP Server child processes/threads are in use at a given time by activating mod_status and checking the server-status page, or by monitoring with mod_mpmstats.
This is an important message to watch out for when there is a symptom such as a hung server.
At the time the message was written, there were not any worker threads, or child processes in V1.3, available to process additional requests.
mod_mpmstats for IBM HTTP Server V2.0 and above provides better reporting of this condition; in particular, it can report when the Max Clients condition has been reached as often as once every 90 seconds.
If the Mdm Attribute is read from the OLAP Catalog, then run PL/SQL procedure CWM2_OLAP_VALIDATE. Metadata for the Mdm Measure was incomplete or inconsistent.
VALIDATE_OLAP_CATALOG with type_of_validation OLAP API. Possible causes are: 1) The Mdm Measure did not have an associated Mtm Measure Map.
This may have one of two causes: either you specified a hash join strategy when hash join is not allowed (no optimizable equijoin) or you are attempting to join two external virtual tables, each of which references the other, and so the statement cannot be evaluated. The verification process for the encryption key was not successful. Severe and non-recoverable corruption can result if 2 instances of Derby boot on the same database at the same time.
This could have been caused by an error when accessing the appropriate file to do the verification process. You are trying to execute a Data Definition statement (CREATE, DROP, or ALTER) while preparing a different statement. It can happen if you execute a Data Definition statement from within a static initializer of a Java class that is being used from within a SQL statement. (The relationship forms a cycle of two or more tables that cause the table to be delete-connected to itself (all other delete rules in the cycle would be CASCADE)). (The relationship causes the table to be delete-connected to the indicated table through multiple relationships and the delete rule of the existing relationship is SET NULL.). (The relationship would cause the table to be delete-connected to the same table through multiple relationships and such relationships must have the same delete rule (NO ACTION, RESTRICT or CASCADE).) The delete rule of foreign key cannot be CASCADE. The db2j.database.force Database Lock=true property has been set, so the database will not boot until the is no longer present.