Database Notification Time (-dbnotifytime)
- Last Updated: February 11, 2026
- 2 minute read
- OpenEdge
- Version 13.0
- Documentation
Use Database Notification Time (-dbnotifytime) to specify how often an OpenEdge Release 12.2 or later
client checks for notifications sent automatically by the server.
| Operating system and syntax | UNIX / Windows |
-dbnotifytime
n
|
|
|---|---|---|---|
| Use with | Maximum value | Minimum value | Default |
| Database Server | 300 | 10 | 30 |
- n
- The time, in seconds, of how often a client checks for
notifications. When the
-dbnotifytimeexpires, the client checks for notifications. The default is 30 seconds, meaning that clients will check for notification every 30 seconds. The minimum value is 10 seconds; the maximum is 300 (5 minutes).
You can use PROMON or the_DbParams VST to modify the Database
Notification Time (-dbnotifytime) parameter while
your database is online. When a client next logs in, it will ask the database server
to specify the Database Notification Time value and change the value if applicable.
You can use this parameter to support continuous operation of the database. For more information, see Change database parameters while the database is running.
When -dbnotifytime is
changed online, a notification is sent to clients informing them of the change. This
parameter can be changed online, but it cannot be changed from zero to nonzero, nor
it can be changed from nonzero to zero. If -dbnotifytime is nonzero, all 12.2 and later clients will use this
value. If -dbnotifytime is 0, then the clients
will follow -usernotifytime.
Older remote clients always use -usernotifytime because they don't support notifications being pushed.
The following examples show how parameters affect the behavior of older and newer
remote clients.
The parameter settings below disable notifications:
|
The parameter settings below enable notifications, and all remote clients send messages asking for notifications:
|
These parameter settings enable notifications; remote clients for release 12.2 and later receive automatically sent notifications, and earlier version remote clients do not support notifications:
|
These parameter settings enable notifications; remote clients for release 12.2 and later receive pushed notifications, and earlier version remote clients send network messages asking for notifications:
|