|
Option 1: Upgrades the system tables in the Marketing Operations database and populates the tables with required default data.
|
1.
|
From the <IBM_EMM_Home>\<MarketingOperations_Home>\tools\bin directory, locate and open the setenv file in a text editor.
|
2.
|
Verify that the JAVA_HOME variable indicates the correct directory for your installation of Java™, and that the JDBC drivers are the first entry for the DBDRIVER_CLASSPATH variable. For more information about setting the environment variable, see the Marketing Operations Installation Guide.
|
4.
|
From the <IBM_EMM_Home>\<MarketingOperations_Home>\tools\bin directory, locate and open the umo_jdbc.properties file.
|
By default, the utility detects the version of the database you are upgrading. However, if an earlier attempt to upgrade the database failed in some way, the version may have been updated even though the upgrade failed. When you have corrected the problem and run the utility again, you use this variable with the -f variable to specify the correct base version.
For example, -f -b 9.0.0.0
|
|
For upgrades only. Instructs the utility to use the base version specified by the -b variable, overriding the base version it may detect in the database. See the description of the -b variable.
|
|
Records the output from the actions that the umodbsetup utility performs in the umo-tools.log file. This file is located in the <IBM_EMM_Home>\<MarketingOperations_Home>\tools\logs directory. This variable specifies the logging level.
|
|
Sets the default Locale for the installation. For example, use -L de_DE for a German installation.
|
|
Outputs the scripts to a file in the <IBM_EMM_Home>\<MarketingOperations_Home>\tools directory, which you can then run manually. Use this option if there is a reason you need to run scripts from your own database client application. When you use this variable, the umodbsetup tool does not run the script.
|
|
Copyright IBM Corporation 2014. All Rights Reserved.
|