Installing for an Oracle database

When you are installing for an Oracle database both for server and client, you first need to install client and provide connection string to the database.

The following list describes the fields that you might need to complete during the installation.

Installation path
 

Specify the path of an Oracle installation that satisfies the Tivoli Workload Scheduler prerequisites. The fully-qualified path must identify a tree in the Oracle structure that includes the sqlplus executable.
 

Net service name

The name used by clients to identify an Oracle Net server and the specific system identifier or database for the Oracle Net connection. A net service name is mapped to a port number and protocol. It is also known as a connect string, database alias, host string, or service name.

If your Oracle database is installed on the same system where you are installing your master domain manager or a backup master, the net service name is the name of your Oracle database.

If your Oracle database is not installed on the system where you are installing your master domain manager or a backup master, the net service name is the alias configured for the connection to the remote database.

Contact your database administrator to obtain the correct net service name.
 

Oracle administrator user

The database administrator user name (such as SYSTEM) required to authenticate to the Oracle database. This account must already exist.
 

Oracle administrator user password
 

The database administrator user password required to authenticate to the Oracle database.
 

Tivoli Workload Scheduler Oracle user (twsuser)
 

The owner of the Tivoli Workload Scheduler schema. The name must comply with the Oracle naming rules.

If you are installing a master domain manager and you leave this field blank, this name is defaulted to twsuser. If you are installing a backup master, you are required to enter the same name that is used in the master domain manager.

On a fresh installation of a master domain manager this user does not exist in the database. If this is not the case, it means that there already is a master domain manager or a backup master instance pointing to the same database with this user name. If your existing Tivoli Workload Scheduler instance is version 8.3 or 8.4, the installation process upgrades the current database schema to the new schema.

If your existing instance is the current version, the installation process assumes that the schema is at the right level and does not create the database objects (tables, views, clusters, procedures, indexes, and so on) for Tivoli Workload Scheduler.
 

Tivoli Workload Scheduler Oracle user password

The password for the twsuser user.
 

Create the Tivoli Workload Scheduler schema using the Oracle Partitioning option

If you are installing on Oracle Enterprise Edition, you can choose to implement the Oracle Partitioning option to improve the performance of event-driven workload automation. For information about event-driven workload automation, see Tivoli Workload Automation: Overview.
 

Tivoli Workload Scheduler data tablespace (USERS)

The name that identifies the Tivoli Workload Scheduler data table space. This table space must have been previously created by the database administrator. The default for this field is USERS.
 

Tivoli Workload Scheduler reports tablespace

The name that identifies the Tivoli Workload Scheduler table space where report data is to be stored. You can view the report data using the Tivoli Dynamic Workload Console.

This table space must have been previously created by the database administrator. The default value for this field is USERS.
 

Tivoli Workload Scheduler temporary tablespace (TEMP)

The name that identifies the Tivoli Workload Scheduler temporary table space. This table space must have been previously created by the database administrator. The default value for this field is TEMP.

Help -