DISCLAIMER: The information and links provided on this site are my personal notes, based on my limited experience installing, using, and deinstalling Oracle databases and application servers on a variety of computers using Windows NT/2000/XP operating systems. The installation and deinstallation procedures found here can cause irreversable loss of data and may damage your operating system. However, you are welcome to use them AT YOUR OWN RISK. I am in no way responsible for data you lose or operating systems you damage or destroy.
This startup sequence is for servers containing OracleAS 10g Infrastructure and OracleAS 10g middle-tier (Web Cache and J2EE-OC4J) installations. It was copied from Section 2.5 of the OracleŽ Enterprise Manager Advanced Configuration 10g Release 1 (10.1).
Oracle Enterprise Manager 10g components are used to manage a variety of Oracle software products. For example, each time you install Oracle Application Server 10g (9.0.4) instance, you also install an Application Server Control. Similarly, each time you install Oracle Database 10g, you install a Database Control. In addition, if you want to centrally manage your system with Database Control, the Management Agent is also installed on each host you monitor.
In most cases, in a production environment, you will want to distribute your database and application server instances among multiple hosts to improve performance and availability of your software resources. However, in rare cases where you must install multiple application servers or databases on the same host, consider the following guidelines.
When you start Application Server Control, the Management Agent, or the Database Control, Enterprise Manager immediately begins gathering important monitoring data about the host and its managed targets. Keep this in mind when you develop a process for starting the components on the host.
Specifically, consider staggering the startup process so that each Enterprise Manager process has a chance to start before the next process begins its startup procedure.
For example, suppose you have installed OracleAS Infrastructure 10g, the J2EE and Web Cache application server installation type, and the Management Agent on the same host. When you start up all the components (for example, after a restart of the system), use a process such as the following:
1. Use the opmnctl startall command to start all the OPMN-managed processes in the OracleAS Infrastructure 10g home directory.
2. Wait 15 seconds.
3. Use the emctl start iasconsole command to start the Application Server Control in the OracleAS Infrastructure 10g home directory.
4. Wait 15 seconds.
5. Use the opmnctl startall command to start all the OPMN-managed processes in the J2EE and Web Cache home directory.
6. Wait 15 seconds.
7. Use the emctl start iasconsole command to start the Application Server Control in the J2EE and Web Cache home directory.
8. Wait 15 seconds.
9. Use the emctl start agent command to start the Management Agent for the host.
Using a staggered startup procedure such as the preceding example will ensure that the processes are not in contention for resources during the CPU-intensive startup phase for each component.