sup_db_setup

Supplemental Database Setup

Creates or removes the supplemental database.

Note:

See “Special Procedure to Remove EMSs from Shared Memory” for information about removing EMSs from shared memory when removing supDB.

Keyword

sup_db_setup

Permission

The user must be logged in with the user name lsmsadm.

Syntax

$LSMS_DIR/sup_db_setup <Action>

This command must be executed from the $LSMS_DIR and must be run on the both servers. The operator must respond to a prompt to verify removal or creation of the database when a version already exists.

Options

None.

Parameters

Action

The function to be performed on the database. This mandatory parameter has the following values:

create

remove

Sample Output

To create a new Supplemental Database:

$ $LSMS_DIR/sup_db_setup create

------------------------------------------------------------------

Supplemental Database Setup Script The Supplemental Database name is supDB
Initializing Supplemental Database...supDB
The supplemental database supDB was created successfully.

To remove the current Supplemental Database

$ $LSMS_DIR/sup_db_setup remove

------------------------------------------------------------------

Supplemental Database Setup Script
WARNING: Supplemental Database supDB is about to be removed.
         All data in this database will be lost.
         Do you want to continue? [Y/N] Y
Removing Supplemental Database...supDB
$

Response Notes

The create action requires 20 or more seconds to create the database and respond.

Possible Errors

Error Messages: sup_db_setup
Exit Code	Cause	Suggested Recovery
1	Syntax was incorrect	Use correct syntax.
2	MySQL command failed	Contact Oracle.
7	User attempted to create a database that already exists	None needed.
9	User attempted to remove a database that is in use	Stop indicated processes before attempting to remove the database.
10	The root user cannot execute this command	Change users to lsmsadm.

Special Procedure to Remove EMSs from Shared Memory

Note:

Beginning with LSMS Release 6.0, Sentry information for LSMS processes is stored in shared memory, not the database. As a result, use of the sup_db_setup command to remove the supDB leaves Sentry in the state that it still monitors/restarts EagleAgents for EMS that were previously defined in the supDB. Therefore, Sentry will continually attempt to restart the EagleAgents for these EMS’s and will continue to display their status. To eliminate this problem, perform the following procedure:

Procedure:

Delete all EMS Components using the LSMS GUI. (For more information, refer to the Configuration Guide, Chapter 3, "Deleting an EMS Configuration Component.")
Deactivate all NPAC Regions using the LSMS GUI. (For more information, refer to the Configuration Guide, Chapter 3, "Modifying LSMS Configuration Components.")
Shutdown the LSMS using Sentry. Log in to the active server as root, and execute the sentry shutdown command:
# sentry shutdown
Delete the supDB. Log in to the active server as lsmsadm, and execute the sup_db_setup remove command:
$ $LSMS_DIR/sup_db_setup remove

You have now completed this procedure.