Oracle AS10g Start Failure on Windows

Oracle AS10g Start Failure on Windows

The Oracle Application Server 10g is available for Windows.

If you worked with Oracle9iAS on Windows, you know that when the server reboots, the Application Server does not successfully restart without some help. Oracle AS10g on Windows has the same problem.

Metadata Repository Database and OID Returns Before They Can Accept Connections

The problem stems from the requirement to use Window's Services to restart the Application Server. Even after placing dependencies on the Services, the restart is unsuccessful. The Service that starts the Metadata Repository database (iasdb or asdb) returns before the database is ready to accept connections. The Oracle Internet Directory in the infrastructure tier tries to connect and fails. Once OID fails, then all components that rely on it also fail. Even if OID does successfully connect to asdb, the opmnctl utility returns before OID is fully up and running.

The Answer Is To Restart the Application Server.

There are a number of solutions to this problem, the easiest and least problematic is to use a batch file to bring the Application Server back down and restart it allowing time for each component to completely restart.

Here is a scripts that I use.

It uses the utility sleep.exe to provide time for each component to completely start.

The first step is to wait 5 minutes to let the server completely finish booting.

REM Wait 5 minutes for the services to finish REM loading
sleep 300

REM Stop both tiers
C:\oracle\midtier\opmn\bin\opmnctl stopall

sleep 20

C:\oracle\inftier\opmn\bin\opmnctl stopall

sleep 20

REM Start the Infrastructure
C:\oracle\inftier\opmn\bin\opmnctl startall

REM Wait at least 30 seconds for OID to start
sleep 60

REM Start Mid Tier
C:\oracle\midtier\opmn\bin\opmnctl startall

REM The mid tier takes 15 seconds to finish REM starting after it returns. This keeps
REM anything else from starting until the Mid REM Tier is up.
sleep 30
exit

The sleep time starts when the opmnctl utility returns.

I run this in the early morning so I can pad my sleep time to insure components start.

Notice that the infrastructure tier returns as started, but OID will take an additional 30 seconds before it is available.

Place this batch file in the startup folder so that it starts when the server starts.

Now when you reboot the server, the reboot takes an extra 10 minutes to complete but the Application Server is up and ready to accept users.

Learn more about the Managing the Oracle Application Server in Oracle Application Server 10g Administration Handbook by Oracle Press. In Book Stores Now!