Check the database state
- Last Updated: January 16, 2024
- 1 minute read
- OpenEdge
- Version 12.8
- Documentation
OpenEdge lets you determine database availability if issues prevent startup. To check the current operational state of the database for startup, liveness, or readiness, use the PROUTIL PROBE qualifier.
- 0—Success. The database passed the health check for the specified state.
- 1-15—Internal failures prevented the utility from running.
- 16—Startup check failed.
- 32—Liveness check failed.
- 64—Readiness check failed.
-verbose argument. -
A startup probe checks that the broker has begun serving users, for example:
proutil sports2020 -C probe startup -verbose0The command returns success status code
0, which indicates that some logins are enabled for the database. The check succeeds, so-verbosereturns no messages. -
A liveness probe checks that startup is completed and the broker is responsive. The optional
-livenessTimeoutargument limits the duration for which the probe waits for a response.The following example shows a liveness probe with a liveness timeout of 90 seconds:
proutil sports2020 -C probe liveness -livenessTimeout 90 -verbose32Broker process with PID 14459 is dead. (20888)The failure code
32and message indicate an unresponsive broker. -
A readiness probe checks that the database passed the liveness state and is ready to connect with any language client for completing the activity allowed on the database. For example, a successful readiness response means that read operations are allowed on read-only databases.
The following example shows a readiness probe with the optional
-verboseargument:proutil sports2020 -C probe readiness -verbose64Database is in a quiet point. (20898)The failure status code
64and message indicate that the client cannot perform CRUD operations. In a database quiet point, all file write activity to the database is stopped.
For more information, see PROUTIL PROBE qualifier.