3 Management Issues

3.1.1 OracleAS Guard Not Supported

Oracle Application Server Standard Edition One does not support OracleAS Guard as disaster protection feature.

If you need OracleAS Guard, please use Oracle Application Server Release 10g (10.1.2.0.0). Upcoming releases of Oracle Application Server may also support this feature.

3.1.2 Restoring an Oracle Application Server Instance

In section 20.2.10 of the Oracle Application Server Administrator's Guide, the following paragraphs should be added to the section:

Before performing a restore operation (restore_instance or restore_config) on an instance in a cluster, all OC4J processes across the cluster must be stopped. Use the following command to stop the processes:

ORACLE_HOME/opmn/bin/opmnctl @cluster stopproc ias-component=OC4J

Some OC4J components (such as Wireless) do not have ias-component=OC4J. For these components use the uniqueid value to stop the OC4J process. To determine which components have a uniqueid, use the following command:

ORACLE_HOME/opmn/bin/opmnctl @cluster status -fmt %typ%uid%prt -noheaders

The following is an example of the output from the command:

CUSTOM | N/A | DSA
LOGLDR | N/A | logloaderd
DCMDaemon | 1444413512 | dcm-daemon
WebCache | 1500577871 | WebCache
WebCache-admin | 1500577872 | WebCacheAdmin
OHS | 1500577870 | HTTP_Server
performance | 1500577873 | performance_server
messaging | 1500577874 | messaging_server
OC4J | 1500577865 | OC4J_Wireless

Stop all the OC4J processes, for which the second column (uid) value is not "N/A", with the following command:

ORACLE_HOME/opmn/bin/opmnctl @cluster stopproc uniqueid=1500577865

opmnctl: stopping opmn managed processes...

After the restore operation is complete, use the following command to restart the OC4J processes across the cluster:

ORACLE_HOME/opmn/bin/opmnctl @cluster startproc ias-component=OC4J

For components that use uniqueid, you can restart their process by using the appropriate ias-component value or by using the following command:

opmnctl startall

3.1.3 Using Oracle Enterprise Manager 10g Application Server Control Console To Perform a Recovery of an Oracle Application Server Instance

In section 20.2.11 of the Oracle Application Server Administrator's Guide, the following paragraphs should be added:

Before performing a restore operation (restore_instance or restore_config) on an instance in a cluster, all OC4J processes across the cluster must be stopped. Use the following command to stop the processes:

ORACLE_HOME/opmn/bin/opmnctl @cluster stopproc ias-component=OC4J

Some OC4J components (such as Wireless) do not have ias-component=OC4J. For these components use the uniqueid value to stop the OC4J process. To determine which components have a uniqueid, use the following command:

ORACLE_HOME/opmn/bin/opmnctl @cluster status -fmt %typ%uid%prt -noheaders

The following is an example of the output from the command:

CUSTOM | N/A | DSA
LOGLDR | N/A | logloaderd
DCMDaemon | 1444413512 | dcm-daemon
WebCache | 1500577871 | WebCache
WebCache-admin | 1500577872 | WebCacheAdmin
OHS | 1500577870 | HTTP_Server
performance | 1500577873 | performance_server
messaging | 1500577874 | messaging_server
OC4J | 1500577865 | OC4J_Wireless

Stop all the OC4J processes, for which the second column (uid) value is not "N/A", with the following command:

ORACLE_HOME/opmn/bin/opmnctl @cluster stopproc uniqueid=1500577865

opmnctl: stopping opmn managed processes...

After the restore operation is complete, use the following command to restart the OC4J processes across the cluster:

ORACLE_HOME/opmn/bin/opmnctl @cluster startproc ias-component=OC4J

For components that use uniqueid, you can restart their process by using the appropriate ias-component value or by using the following command:

opmnctl startall

3.1.4 Using the Backup and Recovery Tool to Perform a Recovery Fails Due to an Unknown Log Sequence Number

When performing a recovery using the Backup and Recovery Tool, the RMAN recovery fails due to an unknown log sequence number. Use the following command to correct the problem:

sqlplus> alter database open resetlogs;

3.1.5 Unable to Restore the Metadata Repository Backup to Same Point Twice

When performing a recovery on OracleAS Metadata Repository using the Backup and Recovery Tool, if you try to recover the metadata repository to the same time point twice, then the RMAN recovery fails the second time. The following error message is displayed:

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 03/28/2005 16:56:41
ORA-01147: SYSTEM tablespace file 1 is offline   
ORA-01110: data file 1: '/home/sunishar/oradata/orcl/system01.dbf'

This bug has not been fixed for Oracle Application Server Standard Edition One. The base bug number is 4274921, which in in the rdbms.

3.1.6 Enabling ARCHIVELOG Mode

In section 19.2.2 step 2 of the Oracle Application Server Administrator's Guide, the default filename format for UNIX is incorrect. The default filename should be:

(Optional) The default filename format for archive logs is:

• For UNIX systems:

  %t_%s_%r.dbf
  
  

3.1.7 Using Enterprise Manager To Perform an Instance Recovery

If you use Enterprise Manager to perform an instance recovery and you run the recovery a second time using the same backup timestamp, you will receive RMAN errors similar to the following:

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 06/20/2005 17:53:30
ORA-01147: SYSTEM tablespace file 1 is offline
ORA-01110: data file 1:
'/private/OraHome_se1/infra/oradata/orclyc/system01.dbf'

The same RMAN errors occur if two consecutive recovery operations are performed in command mode, ("-m restore_instance -t <backup_timestmap>" or "-m restore_repos -u <timestamp>") specifying the same timestamp.

After the errors occur, the recovery is incomplete and the repository database is not opened but remains in the 'mounted' state. To reopen the database, restore the control file and recover the instance to an earlier or later timestamp. To do this, run the following command:

UNIX:

bkp_restore.sh

To find the available backup timestamps for recovery, run the following command:

bkp_restore.sh -m restore_instance

The Oracle Application Server Backup and Restore Tool responds by displaying a list of available backup timestamps. Choose a different backup timestamp from the one that was used before and execute the following command:

UNIX:

bkp_restore.sh -c -m restore_instance -t <backup_timestamp>

The '-c' option is for restoring the control file. The <backup_timestamp> is the different timestamp.

3.1.8 User Created OC4J Instances Require Entries in config_misc_files.inp File

For every OC4J instance that you add to Oracle Application Server after the initial installation, you must add an entry for that OC4J instance to the config_misc_files.inp file. This is required so that the Backup and Recovery Tool can perform backups correctly. The following example shows how the entries should be made:

${OH}/j2ee/<oc4j_instance_1>
${OH}/j2ee/<oc4j_instance_2>

3.1.9 Invoking the runstartupconsole.sh Script

Run the runstartupconsole.sh script to start and stop the processes in a middle tier or OracleAS Infrastructure installation. The script is located in the ORACLE_HOME/bin directory. Its usage is described below:

runstartupconsole.sh {start|stop} [as|allas|em|allem]

Table 3-1 summarizes the parameters for the runstartupconsole.sh script.

runstartupconsole.sh start

runstartupconsole.sh stop

runstartupconsole.sh start as

runstartupconsole.sh start allas

runstartupconsole.sh start em

runstartupconsole.sh start allas

3.1.10 Forbidden Error When Using Portal After the Installation Completes Successfully

Database connections using Java or JDBC from a locale where NLS_LANG and LC_ALL is set to Simplified Chinese, zh_CN, can fail with the ORA-604 error and the ORA-2268 or ORA-1756 error.

LANG=en_GB.UTF-8 
LC_ALL=en_GB.UTF-8

If you are running in the zh_CN locale, then apply the following fixes after completing the installation of Oracle Application Server Standard Edition One:

1. Shutdown all processes in all instances.

2. Apply Database Server patch set (10.1.0.4).

3. Apply Patch 4406738

4. Restart all processes in all instances.

Both database 10.1.0.4 patch set and patch 4406738 can be downloaded from http://metalink.oracle.com.

When using OracleAS Metadata Repository Creation Assistant against an existing Database 10.1.0.4 instance, apply oneoff patch 4406738 to Database home before running OracleAS Metadata Repository Creation Assistant.

3.1.11 Create Local Mapped Drive For Backups

If you want to store backups on a remote file system, you must create a local mapped drive and specify it as the backup storage directory.For example, if /ASbackups is the mapped drive for backups, then configuration files and repository backups should have /ASbackups as their backup directory.

3.2.1 Error Message When Running 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.

3.2.2 Internal Error Message When Running opmnctl Commands

After you apply the Linux x86 10.1.0.4 patch set to the OracleAS Infrastructure, the following error message will appear:

Internal error message 684 could not be found in the msb file 

This error appears when you run the opmnctl stopall or opmnctl startall command after applying the patch set. To resolve this issue, Oracle recommends that you download the patch 4420409 and apply it on the infrastructure ORACLE_HOME. The patch can be downloaded from Oracle Metalink (http://metalink.oracle.com)

3.3.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 

3.3.2 Welcome Pages Display in English in Cloned Installations

After cloning an installation using Oracle Universal Installer, the Welcome Pages in the cloned installation display in English, regardless of the locale selection.

To resolve this problem, perform the following steps in the cloned Oracle home:

cd ORACLE_HOME/Apache/Apache/htdocs
rename index.html index.html.html

3.4.1 Missing Element in Common Configuration Example

Example 3-1 in the Oracle Process Manager and Notification Server Administrator's Guide is missing the following sub-element for the ipaddr element:

local="ip"

Required: true

Default: none

Valid Values: IP address (in ###.###.###.### format) or host name to which ONS will bind its local port. IP address or host name to which ONS will bind its local port. All local OPMN requests are routed through the local port, and all local applications connect to ONS through the local port to send and receive notifications.

3.4.2 Incorrect Attribute Definition

In Chapter 3, "Common Configuration" of the Oracle Process Manager and Notification Server Administrator's Guide, the process-set parameter incorrectly lists the restart-on-death default value as false. The correct value is true.