Alternate Database 2 (-dbalt2)
- Last Updated: February 11, 2026
- 1 minute read
- OpenEdge
- Version 13.0
- Documentation
Use Alternate Database 2 (-dbalt2) to
specify an alternate OpenEdge database to connect to, in the event that the
connection to the primary database (database specified by -db) fails. The alternate can only be specified when using a
client-server connection, not a single-user or self-service (shared-memory)
connection.
| Operating system and syntax | UNIX / Windows |
-dbalt2 "dbname [-H hostname] -S port"
|
||
|---|---|---|---|---|
| Use with | Maximum value | Minimum value | Single-user default | Multi-user default |
| Client Connection | — | — | — | — |
- dbname
- The second alternate OpenEdge database to attempt to connect to, if connecting to the primary database fails. Specify the physical (not the logical) database name. The alternate's logical database name is implicitly set using the primary database connection's logical database name.
- hostname
- The hostname the database resides on. If the
-Hparameter is not specified, localhost is used. - port
- The port number of the host the database resides on.
Enclose the connection information in quotes. The order of the
-H and -S
parameters does not matter.
|
You specify the first alternate database using Alternate Database 1 (-dbalt1). The connection string specified
by -dbalt2 is tried after -dbalt1.
Retry Connect Set (-retryConnect) and Retry Connect Set Pause (-retryConnectPause) can be used to control the number of connection attempts and the pause interval between attempts.
For more information, see Learn about automatic database reconnect.