7 Frequently Performed Tasks

This chapter contains instructions for tasks performed frequently during the upgrade process using the command line tools. They include:

Commands for Oracle9iAS Infrastructure
Commands for Information Storage Database
Oracle Collaboration Suite Middle Tier Release 1 (9.0.3.1) and Release 2 (9.0.4.2) Tasks

7.1 Commands for Oracle9iAS Infrastructure

This section contains instructions for performing the following tasks:

Starting an Oracle9iAS Infrastructure Instance
Shutting Down an Oracle9iAS Infrastructure Instance
Verifying that Oracle Internet Directory is Running

7.1.1 Starting an Oracle9iAS Infrastructure Instance

To start an Oracle9iAS Infrastructure instance, perform the following steps:

Set the ORACLE_HOME environment variable to the location of the Oracle9iAS Infrastructure. You can set the ORACLE_SID system variable using the System Properties control panel.

For example:
```
(Bourne or Korn shell) ORACLE_HOME=/opt/oracle/infra9042; export ORACLE_HOME
(C shell) setenv ORACLE_HOME /opt/oracle/ocs/infra9042
```
Start the Oracle9iAS Metadata Repository.
1. Start the Oracle9iAS Metadata Repository listener:
```
ORACLE_HOME/bin/lsnrctl start
```
2. Set the ORACLE_SID environment variable to the Oracle9iAS Metadata Repository system identifier. The default ORACLE_SID is iasdb.
```
(Bourne or Korn shell) ORACLE_SID=iasdb; export ORACLE_SID
(C shell) setenv ORACLE_SID iasdb
```
3. Start the Oracle9iAS Metadata Repository instance using SQL*Plus:
```
ORACLE_HOME/bin/sqlplus /nolog
sql> connect sys/password_for_sys as sysdba
sql> startup
sql> quit
```
Start Oracle Internet Directory.
1. Make sure the ORACLE_SID is set to the Oracle9iAS Metadata Repository system identifier as in the previous step.
2. Start the Oracle Internet Directory monitor:
```
ORACLE_HOME/bin/oidmon start
```
3. Start the Oracle Internet Directory server:
```
ORACLE_HOME/bin/oidctl server=oidldapd configset=0 instance= n start
```
  where n is any instance number (1, 2, 3...) that is not in use. For example:
```
ORACLE_HOME/bin/oidctl server=oidldapd configset=0 instance=1 start
```

Start the Oracle Enterprise Manager Web site.

Even though you are using command-line, the Web site is required because it provides underlying support for the command-line tools. The Web site must be started after every system boot.

You can run the following commands in the Oracle home of the primary installation (the first installation on the host) to get status and start the Web site:

ORACLE_HOME/bin/emctl status
ORACLE_HOME/bin/emctl start

Note:

Do not start the Oracle Enterprise Manager if you are going to run the Oracle Universal Installer. If the Oracle Enterprise Manager is running, the Oracle Universal Installer requires you to shut it down.

Start Oracle HTTP Server.
```
ORACLE_HOME/dcm/bin/dcmctl start -ct ohs
```
Starting Oracle HTTP Server also makes Oracle9iAS Single Sign-On available.

Start the OC4J_DAS instance.

ORACLE_HOME/dcm/bin/dcmctl start -co OC4J_DAS

Start Oracle Application Server Web Cache (optional).

Oracle Application Server Web Cache is not configured in the infrastructure by default, but if you have configured it, start it as follows:
```
ORACLE_HOME/bin/webcachectl start
```

7.1.2 Shutting Down an Oracle9iAS Infrastructure Instance

This section describes how to shut down an Oracle9iAS Infrastructure using command-line tools.

Stop all Oracle Collaboration Suite middle tier instances that use the infrastructure.
Stop the Oracle Enterprise Manager Web site (for system shutdown only).

If you are preparing to shut down your system, stop the Oracle Enterprise Manager Web site by running the following command in the Oracle home of the primary installation (the first installation on the system):
```
ORACLE_HOME/bin/emctl stop
```
```
ORACLE_HOME\bin\emctl stop
```
Provide the ias_admin password when prompted.
Stop Oracle Application Server Web Cache (optional).

Oracle Application Server Web Cache is not configured in the infrastructure by default, but if you have configured it, stop it as follows:
```
ORACLE_HOME/bin/webcachectl stop
```
Stop OC4J instances and Oracle HTTP Server.

If you are preparing to shut down your system, stop all running OC4J instances, Oracle HTTP Server, and OPMN as follows:
```
ORACLE_HOME/dcm/bin/dcmctl shutdown
```
Otherwise, if you are not preparing to shut down your system, stop all running OC4J instances and Oracle HTTP Server (leave OPMN running):
```
ORACLE_HOME/dcm/bin/dcmctl stop
```
Note that stopping Oracle HTTP Server also makes Oracle9iAS Single Sign-On unavailable.
Stop Oracle Internet Directory.
1. Make sure the ORACLE_SID is set to the Oracle9iAS Metadata Repository system identifier (refer to the next step).
2. Stop the Oracle Internet Directory server:
```
ORACLE_HOME/bin/oidctl server=oidldapd configset=0 instance=n stop
```
  where n is the instance number that was used to start the server (1, 2, 3...). For example:
```
ORACLE_HOME/bin/oidctl server=oidldapd configset=0 instance=1 stop
```
```
ORACLE_HOME\bin\oidctl server=oidldapd configset=0 instance=1 stop
```
3. Stop the Oracle Internet Directory monitor:
```
ORACLE_HOME/bin/oidmon stop
```
Stop the Oracle9iAS Metadata Repository.
1. Set the ORACLE_SID environment variable to the metadata repository system identifier. The default ORACLE_SID is iasdb.
```
(Bourne or Korn shell) ORACLE_SID=iasdb; export ORACLE_SID
(C shell) setenv ORACLE_SID iasdb
```
2. Stop the Oracle9iAS Metadata Repository instance using SQL*Plus:
```
ORACLE_HOME/bin/sqlplus /nolog
sql> connect sys/password_for_sys as sysdba
sql> shutdown
sql> quit
```
Stop the Oracle9iAS Metadata Repository listener:
```
ORACLE_HOME/bin/lsnrctl stop
```

7.1.3 Verifying that Oracle Internet Directory is Running

Verify that the Oracle Internet Directory server is up and running, using the following commands where ssl_port and non_ssl_port are the port numbers used by SSL and non-SSL. Port numbers are listed in ORACLE_HOME/install/port.ini file.

ORACLE_HOME/bin/ldapbind -p non_ssl_port
ORACLE_HOME/bin/ldapbind -p ssl_port -U 1

ORACLE_HOME\bin\ldapbind -p non_ssl_port
ORACLE_HOME\bin\ldapbind -p ssl_port -U 1

If Oracle Internet Directory server is running, each command returns the message "bind successful."

7.2 Commands for Information Storage Database

This section covers the following topics:

Starting an Information Storage Database Instance
Shutting Down an Information Storage Database Instance

7.2.1 Starting an Information Storage Database Instance

Start the Oracle Collaboration Suite information storage database by performing the following steps.

Set the ORACLE_HOME environment variable to the location of the Oracle Collaboration Suite information storage database Oracle home.

(Bourne or Korn shell) ORACLE_HOME=/opt/oracle/infra9042; export ORACLE_HOME
(C shell) setenv ORACLE_HOME /opt/oracle/ocs/infra9042

Start the Oracle Collaboration Suite information storage database instance.
1. Start the Oracle Collaboration Suite information storage database listener:
```
ORACLE_HOME/bin/lsnrctl start
```
2. Set the ORACLE_SID environment variable to the Oracle Collaboration Suite information storage database system identifier.
```
(Bourne or Korn shell) ORACLE_SID=infodb; export ORACLE_SID
(C shell) setenv ORACLE_SID infodb
```
3. Start the Information Storage Database instance using SQL*Plus:
```
ORACLE_HOME/bin/sqlplus /nolog
sql> connect sys/password_for_sys as sysdba
sql> startup
sql> quit
```

7.2.2 Shutting Down an Information Storage Database Instance

Shut down the Oracle Collaboration Suite information storage database by performing the following steps.

Set the ORACLE_HOME environment variable to the location of theOracle Collaboration Suite information storage database Oracle home.

(Bourne or Korn shell) ORACLE_HOME=/opt/oracle/info9042; export ORACLE_HOME
(C shell) setenv ORACLE_HOME /opt/oracle/ocs/info9042

Set the ORACLE_SID environment variable to the Oracle Collaboration Suite information storage database system identifier.
```
(Bourne or Korn shell) ORACLE_SID=infodb; export ORACLE_SID
(C shell) setenv ORACLE_SID infodb
```
Stop the database instance using SQL*Plus:
```
ORACLE_HOME/bin/sqlplus /nolog
sql> connect sys/password_for_sys as sysdba
sql> shutdown
sql> quit
```
There are four options you can use with the SHUTDOWN command: NORMAL, IMMEDIATE, TRANSACTIONAL and ABORT. For more information about these options, refer to Oracle9i Database Administrator's Guide Release 2 (9.2).
Stop the database listener.
```
ORACLE_HOME/bin/lsnrctl stop
```

7.3 Oracle Collaboration Suite Middle Tier Release 1 (9.0.3.1) and Release 2 (9.0.4.2) Tasks

This section covers the following topics:

Starting a Middle Tier Instance
Shutting Down a Middle Tier Instance

7.3.1 Starting a Middle Tier Instance

Start the middle tier instance by setting the appropriate variables and running the commands listed below.

Set the environment variables for your operating system's library search path (such as LD_LIBRARY_PATH, ORACLE_HOME and PATH) as appropriate for your platform and version of Oracle Collaboration Suite.
Start OPMN and the processes it controls:
```
ORACLE_HOME/opmn/bin/opmnctl startall
```
Start the Oracle Calendar server:
```
$ORACLE_HOME/ocal/bin/unistart
```
Start the OracleAS Web Cache:
```
$ORACLE_HOME/bin/webcachectl start
```
Start the Oracle Enterprise Manager
```
$ORACLE_HOME/bin/emctl start
```

Start Oracle Email and the Oracle Email listener:

$ORACLE_HOME/bin/oesctl startup $machine:um_system:smtp_in
$ORACLE_HOME/bin/oesctl startup $machine:um_system:smtp_out
$ORACLE_HOME/bin/oesctl startup $machine:um_system:imap
$ORACLE_HOME/bin/oesctl startup $machine:um_system:gc
$ORACLE_HOME/bin/oesctl startup $machine:um_system:list
$ORACLE_HOME/bin/oesctl startup $machine:um_system:pop
$ORACLE_HOME/bin/oesctl startup $machine:um_system:nntp_in
$ORACLE_HOME/bin/oesctl startup $machine:um_system:nntp_out
$ORACLE_HOME/bin/oesctl startup $machine:um_system:vs
$ORACLE_HOME/bin/lsnrctl start listener_es

where $machine is the fully qualified host name of the system running the middle tier.

Start Oracle Files:
```
$ORACLE_HOME/ifs/files/bin/ifsctl start DOMAIN_NAME password
```
where password is the Oracle Files schema password.

Start Oracle Web Conferencing:

$ORACLE_HOME/imeeting/bin/imtctl start

Start Oracle9iAS Wireless from the Oracle Enterprise Manager console:
1. Enter the URL of the Oracle Enterprise Manager console in a browser:
```
http://servername:port
```
  where servername and port are the name of the system and the port where Oracle Enterprise Manager is running. The default ports are 1810 and 1811.
2. Enter your user name and password. The Oracle Enterprise Manager Home Page appears.
3. From the System Components table, select Wireless. The Wireless page appears and defaults to the Wireless Server tab.
4. From the Wireless Server tab, click Start All.

7.3.2 Shutting Down a Middle Tier Instance

Shut down the middle tier instance by setting the appropriate variables and running the commands listed below.

Shut down Oracle Email:

$ORACLE_HOME/bin/oesctl shutdown $machine:um_system:smtp_in
$ORACLE_HOME/bin/oesctl shutdown $machine:um_system:smtp_out
$ORACLE_HOME/bin/oesctl shutdown $machine:um_system:imap
$ORACLE_HOME/bin/oesctl shutdown $machine:um_system:gc
$ORACLE_HOME/bin/oesctl shutdown $machine:um_system:list
$ORACLE_HOME/bin/oesctl shutdown $machine:um_system:pop
$ORACLE_HOME/bin/oesctl shutdown $machine:um_system:nntp_in
$ORACLE_HOME/bin/oesctl shutdown $machine:um_system:nntp_out
$ORACLE_HOME/bin/oesctl shutdown $machine:um_system:vs
$ORACLE_HOME/bin/lsnrctl stop listener_es

where $machine is the fully qualified host name of the system running the middle tier.

After the new Oracle Collaboration Suite Applications is installed you can stop Oracle Email in the source Oracle home using the following command. The value of $DEST_ORACLE_HOME is the location of the new Oracle home and $SOURCE_ORACLE_HOME is the location of the Oracle home you are upgrading:

$DEST_ORACLE_HOME/oes/bin/install_shutdown_all.pl $SOURCE_ORACLE_HOME

Shut down the Oracle Calendar server:
```
$ORACLE_HOME/ocal/bin/unistop -y
```
Shut down Oracle Files:
```
$ORACLE_HOME/ifs/files/bin/ifsctl stop
```
When you execute the command, it will ask for the Files Schema password. Once you provide the password, files will be brought down.
Shut down Oracle Web Conferencing:
```
$ORACLE_HOME/imeeting/bin/imtctl stop
```
Note:
Perform this step on all middle tiers that have Oracle Web Conferencing configured
Shut down OPMN and the processes it controls:
```
$ORACLE_HOME/opmn/bin/opmnctl stopall
```
Shut down the Oracle Application Server Web Cache:
```
$ORACLE_HOME/bin/webcachectl stop
```
Shut down Oracle9iAS Wireless from the Oracle Enterprise Manager console:
1. Enter the URL of the Oracle Enterprise Manager console in a browser:
```
http://servername:port
```
  where servername and port are the name of the system and the port where Oracle Enterprise Manager is running. The default ports are 1810 and 1811.
2. Enter your user name and password. The Oracle Enterprise Manager Home Page appears.
3. From the System Components table, select Wireless. The Wireless page appears and defaults to the Wireless Server tab.
4. From the Wireless Server tab, click Stop All.
Shut down Oracle Enterprise Manager:
```
$ORACLE_HOME/bin/emctl stop
```
Provide the ias_admin password when prompted.

7.3.3 Creating a Database User for an Ultra Search Instance

Use the following procedure to create a new schema users in the upgraded Oracle Collaboration Suite Database. Perform this step before running the Oracle Universal Installer as part of the middle tier upgrade which migrates the existing instances from the Oracle9iAS Metadata Repository to the Oracle Collaboration Suite Database.

Note:

Make sure you have sufficient system privileges to perform these procedures.

Log into the upgraded Oracle Collaboration Suite Database 10g (10.1.2) as the WKSYS, SYS, or SYSTEM database user.
Optionally, create a default tablespace for each instance user. The tablespace must be large enough to contain all data obtained during the crawling and indexing processes. This amount depends on the amount of data you intend to crawl and index. For example:
```
CREATE TABLESPACE lmtbsb DATAFILE '/u02/oracle/data/lmtbsb01.dbf' SIZE 500M AUTOEXTEND ON;
```
Enter the following command:
```
@ORACLE_HOME/ultrasearch/admin/wk0create_user.sql username password tablespace default_tablespace_string
```
where:
- username is the name of the Ultra Search schema owner.
- password is the password of the Ultra Search instance owner.
- tablespace is the name of the default tablespace created in step 2. If you do not specify a tablespace, the default is the same tablespace as UltraSearch schema WK_TEST.
- default_tablespace_string is the string "default tablespace" and the name of the default tablespace created in step 2. You can also use a temporary tablespace name. If default_tablespace_string is not specified, then the default and temporary tablespace settings for the WK_TEST user will be used. If WK_TEST does not exist, then the script uses the default settings for the database.
Some examples are:
```
$ORACLE_HOME/bin/sqlplus "/ as sysdba"@$ORACLE_HOME/ultrasearch/admin/wk0create_user.sql my_test my_test
```
```
$ORACLE_HOME/bin/sqlplus "/ as sysdba"@$ORACLE_HOME/ultrasearch/admin/wk0create_user.sql my_test my_test 'default tablespace lmtbsb temporary tablespace TEMP'
```
```
$ORACLE_HOME/bin/sqlplus "/ as sysdba"@$ORACLE_HOME/ultrasearch/admin/wk0create_user.sql my_test my_test 'default tablespace lmtbsb'
```
Grant the user WKUSER privileges by entering the following command:
```
grant wkuser,resource,connect to username;
```
where username is the same user name provided in step 3.

The script creates a new user and assigns it the tablespaces created in the step 2. Now WKSYS or an Ultra Search superuser can create an Ultra Search instance on this user schema. See the Oracle Ultra Search User's Guide for more information.