Database Connection Failure, Errors 1132 and 551 in the .lg File

Database connection failure.

The client dies without an error message when a GUI client attempts to connect to a remote database at startup (prowin32.exe, prowin.exe) OR:
A CONNECT attempt to a database from a remote GUI client, fails with no error messages.
In both cases errors 1132 and 551 are written to the database log file.

These scenarios are a symptom that the database server was started without enough semaphores available to accommodate the maximum number of users (-n).

When not enough semaphores are available, the following message appears as the server starts: Error 1093 is not logged in the database log file. This is just a warning and the database server is started.

The only way to double-check whether the server was started short of the number of necessary semaphores is to shut down the database, restart it, and look for a recurrence of the Error 1093, or send STDOUT STDERR to a text file at startup.

Under these circumstances, from within the GUI client:

• If the connection is attempted at startup, the client dies with no error messages.
• If the connection is attempted via the CONNECT statement (without) the NO-ERROR clause, a STOP condition is raised and no error message is reported.
• If the connection is attempted via the CONNECT statement (with) the NO-ERROR clause, a STOP condition is raised and messages 748 and 700 appear. When the database connection attempt is from a UNIX client or from the Windows Character Client, messages 748 and 700 appear.

CONNECT raises the STOP condition and this is inconsistent with other with other connection failures from the 4GL (an ERROR condition should be raised instead).
 

Tune the semaphore-related parameters in the UNIX kernel. For further information, refer to Article  Calculating SEMMSL, SEMMNS and SEMMNU