Continuous operations

Automatic database reconnection

OpenEdge now provides a mechanism for automatically connecting to an alternate database, if the connection to the primary database fails. This mechanism uses new client connection startup parameters (-dbalt1, -dbalt2, -retryConnect, -retryConnectPause) and is available when using a client-server connection.

For more information, see Learn about automatic database reconnect in Manage ABL Applications.

Reconnect on application restart

-autoReconnect is a new client session startup parameter related to the automatic database reconnect feature; however, it only applies to non-batch mode AVMs. When a database disconnect occurs, the AVM raises a STOP condition. If the application does not handle the STOP condition on its own, then for an interactive client, the AVM restarts the application. However, the AVM does not attempt to re-establish database connections that were initially connected using the startup parameters. -autoReconnect changes this behavior and instructs the AVM to attempt to re-establish lost database connections before restarting the application.

For more information, see Learn about automatic database reconnect in Manage ABL Applications.

Brokers run throughout recovery transitions

To finish transitions faster, database brokers now continue running on single targets and replication sets. This change improves both manual and automatic recovery transitions.

For more information, see Plan for transition in Use Database Replication.

Disconnect secondary brokers from PROMON

A new PROMON option lets you disconnect secondary brokers without issuing a process kill signal. Secondary brokers let you manage the configuration for a specific group of end users, such as ABL clients, SQL clients, or both.

This option reduces potential database downtime.

For more information, see Server Options in Manage the OpenEdge Database.

Control database notification operations

The new -dbnotifyops startup parameter supports concurrent schema updates. The parameter controls the maximum number of concurrent notifications pending.

For more information, see Database Notification Operations (-dbnotifyops) in Manage the OpenEdge Database.

Manage database client notification

To prevent unnecessary network traffic and improve response time, notifications of certain schema changes are automatically sent to remote clients. Startup parameters, PROMON utility, and VST changes let you control the method and frequency of notification delivery.

For more information, see Database Notification Time (-dbnotifytime) in Manage the OpenEdge Database.

Change more database parameters while the database runs

In this release, more parameters can be changed while the database is running. Parameters that now allow such changes are -aiarcdir, -dbnotifyops,-dbnotifytime, -indexrangesize, -lobrangesize, -Ma, -Mm, -Mn, -n, -semsets, -ssj, -tablerangesize, -userindexrangesize, -userlobrangesize, and -usertablerangesize.

For a list of all parameters that you can modify online, see Change database parameters while the database is running in Optimize the OpenEdge Database for Continuous Operation.

Change ABL triggers online

You can create, change, or delete ABL triggers without acquiring an exclusive schema lock.

For more information, see Change ABL triggers online in Optimize the OpenEdge Database for Continuous Operation.

PROMON server screen changes support separate server and user numbers

VST changes support separate server and user numbers

The changed columns apply only to remote clients.

Database log file specifies both server and user numbers

The OpenEdge database log (.lg) now shows the server number and user number for each connected remote server or broker.

For an example of multiple, concurrent server connections, see Find connected brokers and servers in Manage the OpenEdge Database.

Database log file records secondary broker parameters

The database log (.lg) captures information that helps you understand the circumstances surrounding a failure. The log now records startup parameters for secondary brokers.

Although you can list broker parameters for running servers by using PROMON R&D Status or Virtual System Tables, the database log file lets you troubleshoot landscape or connection issues after server failure. You can easily determine which brokers were active during an event.

For more information about the database log, see OpenEdge database log file in Manage the OpenEdge Database..

PAS for OpenEdge continuous operations updates

Progress Application Server (PAS) for OpenEdge offers a new packaging and deployment strategy that supports the use of ABL applications in continuous integrations and continuous delivery (CI/CD) pipelines called OpenEdge Application Archives (OEAR).

For more information, see PAS for OpenEdge.

Rename fields using SQL

Renaming a database field using SQL no longer requires an exclusive schema lock or for users to be disconnected from the database.

For more information, see Rename fields using SQL in OpenEdge Data Management: SQL Development.

Rename fields using ABL

Renaming a database field using ABL no longer requires an exclusive schema lock or for users to be disconnected from the database.

For more information, see Rename fields using ABL in Optimize the OpenEdge Database for Continuous Operation.