find_sql_rollup and dbschema_sync command parameters
This section lists and describe the parameters for commands find_sql_rollup and dbschema_sync, which you run after you finish upgrading the core components of MainView Middleware Monitor (MVMM).
Note
During the normal process of upgrading to a newer version of MVMM, the tables and other objects used by the previous version of the database must be migrated to the new version. You can accomplish this by running a migration script provided in the installation.
Different migration scripts are available for each database/operating system combination. A special utility called find_sql_rollup is provided to determine the correct migration script to use.
When you know the name of the migration script to use, run it from the command line so you can observe any errors. You might miss errors if you use a graphical interface to run the scripts. Run the scripts from the user account that created the database. If that user account is not available, ensure that the user running the scripts has full access to the database. Failure to run the scripts with a qualified user can cause invalid database schema errors. If you use switches to stop the database script on errors, your installation might stop for non-fatal errors. Consult your DBA for more information.
Using find_sql_rollup and its parameters
Usage
find_sql_rollup userid [-p password | -s]
OR
find_sql_rollup -d db_type db_name db_userid [-p db_password | -s]
These commands query the Application Service using userid and password to get the database userid and database password. They also look up the database configuration and generate the SQL rollup script name.
-d skips the Application Service lookup and accepts the database user name and password directly.
find_sql_rollup parameters
Parameters and switches | Function | |
|---|---|---|
| Indicates direct access to database. | |
| Type of database you use. Your operating system might require quotes around these values. Valid values are:
| |
| Name of the database or ODBC connection. | |
| Database user name to use to connect to the database. | |
| Password for | |
| Password for the user name connecting to the database. | |
| Reads from standard input (stdin) for password. Mutually exclusive with | |
-v, --version | Prints out the product version. | |
-?, --usage | Prints out the program usage. | |
Using dbschema_sync and its parameters
Usage
dbschema_sync userid [-p password | -s] [-i] [-o] [-j] [-a] [-n]
OR
dbschema_sync -d db_type db_name db_userid [-p db_password | -s] [-i] [-o] [-j] [-a] [-n]
These commands query the Application Service using userid and password to get the database userid and database password. They then apply the schema synchronizations to the database.
dbschema_sync parameters
Parameters and switches | Function |
|---|---|
| Skips the Application Service lookup and accepts the database user name and password directly. |
| Type of database you use. Your operating system might require quotes around these values. Valid values are:
|
| Name of the database or ODBC connection. |
| Database user name to use to connect to the database. |
| MVMM name of user who is a member of the database_login group. |
| Password for |
| Password for the user name connecting to the database. |
-a | Includes the Audit Event tables in the purge of objects in the 'Deleted' state. |
| Reads from standard input (stdin) for password. Mutually exclusive with |
-i | Ignores the result of the check for the total number of database connections. |
-j | Includes the ES Journal in the purge of objects in the 'Deleted' state. |
-n | Does not preload attribute OIDs into memory. |
-o | Only does a purge of objects in the 'Deleted' state. |
-v, --version | Prints out the product version. |
-?, --usage | Prints out the program usage. |
Note
dbschema_sync duplicates all formatted standard output and errors (stdout/stderr) to the dbschema_sync.std.log file.
Comments