4 General Management and Security Issues

This chapter describes management and security issues associated with Oracle Application Server. It includes the following topics:

Section 4.1, "General Issues and Workarounds"
Section 4.2, "Starting and Stopping Release 10.1.2.0.0"
Section 4.3, "Port Change Issues"
Section 4.4, "Cloning Issues"
Section 4.5, "Deployment Issues"

4.1 General Issues and Workarounds

This section describes general management and security issues. It includes the following topics:

Section 4.1.1, "Error Message When Executing opmnctl Commands"

4.1.1 Error Message When Executing opmnctl Commands

When you execute either an opmnctl stopall or opmnctl startall command, the oidctl log file contains the following error message:

*** Instance Number already in use. *** 
*** Please try a different Instance number. ***

This error message can be safely ignored.

This error message occurs in Oracle Application Server Infrastructure installations with Oracle Internet Directory.

4.2 Starting and Stopping Release 10.1.2.0.0

The Oracle Application Server Administrator's Guide Release 10.1.2 describes how to start and stop instances using the runstartupconsole command. However, this command is not available in releases earlier than Release 10.1.2.0.2. The following sections describe how to start and stop with Release 10.1.2.0.0:

Section 4.2.1, "Starting OracleAS Infrastructure"
Section 4.2.2, "Stopping OracleAS Infrastructure"
Section 4.2.3, "Starting a Middle-Tier Instance"
Section 4.2.4, "Stopping a Middle-Tier Instance"

4.2.1 Starting OracleAS Infrastructure

To start all processes in a Release 10.1.2.0.0 OracleAS Infrastructure, follow the procedure in this section. This procedure applies to all OracleAS Infrastructure types:

Oracle Identity Management and OracleAS Metadata Repository: Follow both steps to start Oracle Identity Management and OracleAS Metadata Repository.
OracleAS Metadata Repository only: Follow only Step 1 to start OracleAS Metadata Repository. You do not need to perform the second step of starting Oracle Identity Management because you do not need OPMN or the Application Server Control Console in a OracleAS Metadata Repository-only installation.
Oracle Identity Management only: Follow only Step 2 to start Oracle Identity Management. Make sure the OracleAS Metadata Repository that supports Oracle Identity Management (residing in another Oracle home) is already started.

To start OracleAS Infrastructure:

If your OracleAS Infrastructure contains OracleAS Metadata Repository, start it as follows:
1. Set the ORACLE_HOME environment variable to the OracleAS Infrastructure Oracle home.
2. Set the ORACLE_SID environment variable to the OracleAS Metadata Repository SID (default is orcl).
3. Start the Net Listener:
```
ORACLE_HOME/bin/lsnrctl start
```
4. Start the OracleAS Metadata Repository instance:
```
ORACLE_HOME/bin/sqlplus /nolog
SQL> connect SYS as SYSDBA
SQL> startup
SQL> quit
```
5. Start the Oracle Enterprise Manager 10g Database Control:
```
ORACLE_HOME/bin/emctl start dbconsole
```
If your OracleAS Infrastructure contains Oracle Identity Management, start it as follows:
1. Start components:
```
ORACLE_HOME/opmn/bin/opmnctl startall
```
  This command starts OPMN and all OPMN-managed processes such as DCM, Oracle HTTP Server, OC4J instances, and Oracle Internet Directory.
2. Start the Application Server Control Console:
```
ORACLE_HOME/bin/emctl start iasconsole
```

4.2.2 Stopping OracleAS Infrastructure

To stop all processes in a Release 10.1.2.0.0 OracleAS Infrastructure, follow the procedure in this section. This procedure applies to all OracleAS Infrastructure types:

Oracle Identity Management and OracleAS Metadata Repository: Follow both steps to stop Oracle Identity Management and OracleAS Metadata Repository.
OracleAS Metadata Repository only: Follow only step 2 to stop OracleAS Metadata Repository.
Oracle Identity Management only: Follow only step 1 to stop Oracle Identity Management.

To stop OracleAS Infrastructure:

If your OracleAS Infrastructure contains Oracle Identity Management, stop it as follows:
1. Stop the Application Server Control Console:
```
ORACLE_HOME/bin/emctl stop iasconsole
```
2. Stop components:
```
ORACLE_HOME/opmn/bin/opmnctl stopall
```
  This command stops OPMN and all OPMN-managed processes such as DCM, Oracle HTTP Server, OC4J instances, and Oracle Internet Directory.
If your OracleAS Infrastructure contains OracleAS Metadata Repository, stop it as follows:
1. Set the ORACLE_HOME environment variable to the OracleAS Infrastructure Oracle home.
2. Set the ORACLE_SID environment variable is set to the OracleAS Metadata Repository SID (default is orcl).
3. Stop the OracleAS Metadata Repository instance:
```
ORACLE_HOME/bin/sqlplus /nolog
SQL> connect SYS as SYSDBA
SQL> shutdown
SQL> quit
```
4. Stop the Net Listener:
```
ORACLE_HOME/bin/lsnrctl stop
```
5. Stop the Oracle Enterprise Manager 10g Database Control:
```
ORACLE_HOME/bin/emctl stop dbconsole
```

4.2.3 Starting a Middle-Tier Instance

To start all processes in a Release 10.1.2.0.0 middle-tier instance, follow the procedure in this section. This procedure applies to all middle-tier instance types.

To start a middle-tier instance:

If the middle-tier instance uses OracleAS Infrastructure services, such as Oracle Identity Management or OracleAS Metadata Repository, make sure they are started.
Start components:
```
ORACLE_HOME/opmn/bin/opmnctl startall
```
This command starts OPMN and all OPMN-managed processes such as DCM, Oracle HTTP Server, OC4J instances, and OracleAS Web Cache, Forms, and Reports.
Start the Application Server Control Console:
```
ORACLE_HOME/bin/emctl start iasconsole
```

4.2.4 Stopping a Middle-Tier Instance

To start all processes in a Release 10.1.2.0.0 middle-tier instance, follow the procedure in this section. This procedure applies to all middle-tier instance types.

To stop a middle-tier instance:

Stop the Application Server Control Console:
```
ORACLE_HOME/bin/emctl stop iasconsole
```
Stop components:
```
ORACLE_HOME/opmn/bin/opmnctl stopall
```
This command stops OPMN and all OPMN-managed processes such as DCM, Oracle HTTP Server, OC4J instances, and OracleAS Web Cache.

4.3 Port Change Issues

This section describes issues related to port changes. It includes the following topic:

Section 4.3.1, "Additional Step Needed After Changing Oracle HTTP Server Listen Port"

4.3.1 Additional Step Needed After Changing Oracle HTTP Server Listen Port

After you change the Oracle HTTP Server Listen Port, you should update portlist.ini with the new port number. This will avoid potential problems if you later associate the middle tier with an OracleAS Infrastructure or change the OracleAS Infrastructure associated with the middle tier. The portlist.ini file is located in the following directory:

(UNIX) ORACLE_HOME/install
(Windows) ORACLE_HOME\install

4.4 Cloning Issues

This section describes issues related to cloning Oracle Application Server instances. It includes the following topics:

Section 4.4.1, "Considerations for Cloning Oracle Ultra Search"
Section 4.4.2, "Considerations for Cloning OracleBI Discoverer"
Section 4.4.3, "Considerations for Cloning OracleAS Forms and Reports Services"

4.4.1 Considerations for Cloning Oracle Ultra Search

When you clone an OracleAS Portal instance that has SSL enabled, the Ultra Search Administration link on the Services portlet and Application Server Control Console page point to the URLs for the source instance, not the cloned instance.

To work around this problem, edit the following file and update the PortalListeningHostPort property with the correct port number:

Oracle_Home/sysman/emd/targets.xml

The port number can be found in the following file:

Oracle_Home/install/portlist.ini

4.4.2 Considerations for Cloning OracleBI Discoverer

The following describes important information about cloning OracleBI Discoverer:

Values set by users after installation in configuration.xml are not preserved in the cloned Oracle home. The file is located at:
```
Oracle_Home/discoverer/config/configuration.xml
```
To work around this problem, reset the overwritten values by copying them from the configuration.xml file in the source Oracle home to the configuration.xml file in the cloned Oracle home.
After you clone a OracleBI Discoverer instance, when you click the Exit link on the Discoverer Viewer page, it results in a corrupted page because the port number in the oc4j.properties file has not been properly updated. To work around this problem, edit the following file and update the oracle.discoverer.applications.port property with the correct port number:
```
Oracle_Home/j2ee/OC4J_BI_Forms/config/oc4j.properties
```
The port number can be found in the following file:
```
Oracle_Home/install/portlist.ini
```

4.4.3 Considerations for Cloning OracleAS Forms and Reports Services

The following describes important information about cloning OracleAS Forms and Reports Services (installed from a separate CD):

Before you run the prepare_clone.pl script, you must update the ias.properties file in the source Oracle home, changing the value of DatabaseManagedClusterSupport from false to true, as shown in the following example:
```
DatabaseManagedClusterSupport=true
```
On Windows, before you run the prepare_clone.pl script, you must update the ias.properties file in the source Oracle home, changing the value of installType from FRServices to Business, as shown in the following example:
```
installType=Business
```
If you clone OracleAS Forms and Reports Services and then associate it with an OracleAS Infrastructure, the cloned instance is not part of a farm. To make the instance part of a farm, use the following command in the cloned Oracle home:
```
dcmctl joinfarm
```
On Windows, if Grid Control Console is installed on the same machine as OracleAS Forms and Reports Services, the OracleAS Reports Services configuration tool fails. To work around this, delete the following file from the zip file before you extract the compressed Oracle home at the target:
```
ORACLE_HOME/sysman/emd/centralagents.lst
```

4.5 Deployment Issues

This section describes other management issues. It includes the following topics:

Section 4.5.1, "Use Trusted Certificates When Enabling SSL Between mod_oc4j and OC4J"
Section 4.5.2, "Benign Decoding Errors When Running ldapaddmt"
Section 4.5.3, "Missing Files During restore_config Operation"

4.5.1 Use Trusted Certificates When Enabling SSL Between mod_oc4j and OC4J

You must use trusted certificates on both ends when enabling SSL between mod_oc4j and OC4J.

Otherwise, you will get the following error when accessing the HTTPS port:

500 Internal Server Error

4.5.2 Benign Decoding Errors When Running ldapaddmt

Chapter 11, "Changing from a Test to a Production Environment," in the Oracle Application Server Administrator's Guide contains steps for migrating Oracle Internet Directory data to a production environment.These steps include running the ldapaddmt command, and examining the add.log file. The add.log file may contain a "Decoding Error" message. This is benign and can be ignored.

4.5.3 Missing Files During restore_config Operation

Running restore_config may result in missing files messages such as:

Could not copy file C:\Product\OracleAS\Devkit_1129/testdir/ to 
C:\Product\OracleAS\Devkit_1129\backup_restore\cfg_bkp/2004-12-01_03-26-22.

During a restore_config operation, a temporary configuration backup is taken so that, if the restore fails, the temporary backup can be restored returning the instance to the same state as before the restore.If some files are deleted (including files/directories specified in config_misc_files.inp) before a restore operation, then, during the temporary backup, messages are displayed indicating that certain files are missing. These error/warning messages should be ignored since the missing files are restored as part of the restore_config operation.