| Oracle® Application Server Standard Edition One Release Notes 10g Release 2 (10.1.2) for Microsoft Windows (32 Bit) B15880-04 |
|
![]() Previous |
![]() Next |
This chapter describes management issues associated with Oracle Application Server Standard Edition One. It includes the following topics:
This describes general management issues with the Oracle Application Server Standard Edition One release:
Section 4.1.2, "Restoring an Oracle Application Server Instance"
Section 4.1.6, "Received Warning Message During Backup with Backup and Recovery Tool"
Section 4.1.7, "Using Enterprise Manager To Perform an Instance Recovery"
Section 4.1.8, "User Created OC4J Instances Require Entries in config_misc_files.inp File"
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.
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 @clusterstopproc 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 @clusterstartproc 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
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 @clusterstopproc 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 @clusterstartproc 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
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;
In section 19.2.2 step 2 of the Oracle Application Server Administrator's Guide, the default filename format is incorrect. The default filename should be ARC%S_%R.%T.
After performing a backup with the Backup and Recovery Tool, the config_bkp_XXXXXX.log file contains the following warning message:
Could not copy file D:\product\10.1.2\OracleAS/Apache/jsp/conf/ojsp.conf to D:\product\10.1.2\backup/2005-04-26_14-34-35/Apache/jsp/conf
This warning can be ignored.
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:
bkp_restore.bat
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:
bkp_restore.bat -c -m restore_instance -t <backup_timestamp>
The '-c' option is for restoring the control file. The <backup_timestamp> is the different timestamp.
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:
${ORACLE_HOME}/j2ee/<oc4j_instance_1>${ORACLE_HOME}/j2ee/<oc4j_instance_2>
Run the runstartupconsole.bat 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.bat {start|stop} [as|allas|em|allem]
Table 4-1 summarizes the parameters for the runstartupconsole.bat script.
Table 4-1 runstartupconsole.bat Script Parameters
| Parameter | Description |
|---|---|
|
|
Required parameter used to start processes in the Oracle home in which it is run: runstartupconsole.bat start If this command is run in the OracleAS Infrastructure Oracle home, the following processes are started:
If this command is run in the middle-tier Oracle home, the following processes are started:
|
|
|
Required parameter used to stop processes in the Oracle home in which it is run: runstartupconsole.bat stop If this command is run in the OracleAS Infrastructure Oracle home, the following processes are stopped:
If this command is run in the middle-tier Oracle home, the following processes are stopped:
|
|
|
Optional parameter used in conjunction with runstartupconsole.bat start as If this command is run in the OracleAS Infrastructure Oracle home, the following processes are started:
The equivalent of this command from the Start menu is Start > Programs > Oracle - InstanceName > Advanced Administration > Infrastructure > Start Infrastructure Instance. If this command is run in the middle-tier Oracle home, the following process is started:
The equivalent of this command from the Start menu is Start > Programs > Oracle - InstanceName > Advanced Administration > Middle Tier > Start Middle Tier. |
|
|
Optional parameter used in conjunction with runstartupconsole.bat start allas This command should be run only from the middle tier Oracle home. The following processes in the OracleAS Infrastructure Oracle home are started:
The following processes in the middle-tier Oracle home are started:
Note that this command is equivalent to running |
|
|
Optional parameter used in conjunction with runstartupconsole.bat start em The equivalent of this command from the Start menu is either Start > Programs > Oracle - InstanceName > Advanced Administration > Middle Tier > Start Application Server Control Console or Start > Programs > Oracle - InstanceName > Advanced Administration > Infrastructure > Start Application Server Control Console |
|
|
Optional parameter used in conjunction with runstartupconsole.bat start allas This command should be run only from the middle tier Oracle home. Note that this command is equivalent to running |
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 Z:\ASbackups is the mapped drive for backups, then configuration files and repository backups should have Z:\ASbackups as their backup directory.
This section describes Oracle Process Manager and Notification Server (OPMN) issues. It includes the following topic:
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.
This section describes other management issues. It includes the following topics:
Section 4.3.1, "Use Trusted Certificates When Enabling SSL Between mod_oc4j and OC4J"
Section 4.3.2, "Welcome Pages Display in English in Cloned Installations"
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
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
For an Infrastructure database in an OracleAS Cold Failover Cluster environment, one of the steps in the procedure for using the Oracle Application Server Backup and Recovery Tool to backup the Infrastructure database is to enable ARCHIVELOG mode for the database.
The command to do this is: alter database archivelog. However, if Oracle Fail Safe has database polling enabled, the following error message will appear:
ORA-01126: database must be mounted EXCLUSIVE and not open for this operation
Database polling opens the database and monitors or "pings" the database. Hence, for the alter database archivelog command to succeed, database polling must be disabled and the database be mounted EXCLUSIVE before executing the command.
To disable database polling:
Start Oracle Fail Safe Manager.
Select Clusters, <cluster_name>, Cluster Resources, <instance_name> (where <cluster_name> is the name of the cold failover cluster and <instance_name> is the name of the database instance).
Select the Database tab.
Disable Database Polling.
|
Note: When taking a cold backup of the database, ensure that database polling is disabled before shutting down the database. Otherwise, the database will still be opened by the Oracle Fail Safe. |
This section describes documentation errata. It includes the following topic:
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"
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. It is true.