Modes of configuring the database
You can choose from these modes to configure the database: command-line mode, partial live configuration with administration mode turned on or a full live configuration. The mode that you choose depends on the type of change to the Manage schema you are making. It is recommended that you back up the database for all structural changes before you configure the database.
The following table lists the advantages and disadvantages of each configuration mode:
Configuration modes | Advantages | Disadvantages |
---|---|---|
Command-line mode | Data is backed up for certain database changes if the affected table cannot be
changed with data in it. 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. |
Partial 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 are logged out of the system. Only administrators with Can Log in During Admin Mode permissions can access Maximo®. This permission is in the Security Groups application within the Start Center application permissions. Data is backed up for certain database changes if the affected table cannot be changed with data in it. |
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. |
Full 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 non-structural changes to Maximo such as adding a domain to an attribute. |
Configuration modes | Advantages | Disadvantages |
---|---|---|
Partial 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 are logged out of the system. Only administrators with Can Log in During Admin Mode permissions can access Maximo. This permission is in the Security Groups application within the Start Center application permissions. Data is backed up for certain database changes if the affected table cannot be changed with data in it. |
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. |
Full 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 non-structural changes to Maximo such as adding a domain to an attribute. |