Modes of configuring the database

There are three ways to configure the database: command-line mode, a partial live configuration, or a full live configuration with administration mode turned on. The option that you chose depends on whether the application server needs to be shut down and the impact on access to users.

The following table lists the advantages and disadvantages of each configuration mode:

Table 1. Configuration modes
Configuration modes Advantages Disadvantages
Command-line mode All data, logs, and control files are backed-up.

It is easier to restore data from this configuration mode as there are no updates while the database is being configured.

Must shut down the application server therefore, users have no access to the applications during the configuration.

Requires an information technology administration user who has control over the application server.

Full live with administration mode turned on Allows an administration user to perform tasks such as adding a column to a table without shutting down the application server.

Users have access to applications unrelated to the configuration changes.

Blocks users from the system applications.

Suspends CRON tasks.

Does not allow remote connectivity

Disables event listeners.

Requires the user to have Administrator login security authorizations, which you must assign in the Security Groups application.

Partial live Least impact on users as active transactions are not interrupted or lost.

Does not require administration mode to be turned on.

If changes performed during a live update are later determined to be incorrect, you can perform another live update to reverse the changes.

Changes do not disrupt the live business object definitions.

If you change the field validation class for an attribute and perform a live update to apply the changes, the business objects that are already instantiated are not revalidated.

Can be used only for changes with Maximo that have no impact on users such as changing an attribute name.


Feedback