psdi.configure

Class ConfigDB

  • All Implemented Interfaces:
    UpgConstants

    public class ConfigDB
extends CommonShell
implements UpgConstants
    Database Configuration utility. Uses configuration metadata to modify the database and/or write statements to a logfile. This performs tasks such as: changing a column's datatype or length, adding user-defined columns to a table, creating new user-defined tables, defining new indexes, and defining other Maximo-specific attributes for a table or column, such as domainid and customclassname.

    The -l parameter can be used for previewing the configuration process or verbose logging.

    This runs independently of MXServer. MXServer should NOT be running at the same time as this program, otherwise the database may be changing at the same time that this program is trying to determine what to output.

    This program is also run as part of the upgrade process, when called by Upgrade.

    For tables that require being dumped to a temp table and recreated, this program does NOT reload the new base table with the original data. This is done via a separate program, RestoreFromBackup.

    The commandline parameters for ConfigDB are as follows, in addition to those in the superclass CommonShell.

    Parameter IDParameter ValueDescription
    -g(none)This is optional. It indicates that this class has been instanciated by the Upgrade.
    -r(none)This is optional. It indicates that RestoreFromBackup will be launched immediately following ConfigDB, assuming there were no errors. Care should be taken when using this param, as there are occasions when the data in the temp tables (XX+tablename) must be modified before attempting the Restore. (The -r param will NOT launch DropBackup.)
    -z(none)The -z parameter is used ONLY for DB2. When the -z parameter is used and this is DB2, then the logic that enables text search for all tables is not performed from ConfigDB. Instead, ConfigDB will output a script containing all the relevant commands. The script name is db2text_configdb.bat, and it is output to the same directory as the logfile. A second script, db2text_configdb.sh, is output for Unix shell script.

    The reason this parameter is provided is because in DB2, text search procedures cannot be initiated from a remote machine. If Maxinst is run on a different machine than the machine where the database is located, it cannot run the text search commands. They will have to be run manually by a user on the database's machine by using the script output by ConfigDB.

    See Also:
    CommonShell
Skip navigation links