Startup errors require specific troubleshooting procedures.
This section contains solutions that are related to system startup:
When you start the Administration Server, the repository database that was specified during installation must be running, or else you see JDBC errors that prevent startup.
Problem: The Administration Server fails to start.
If the Administration Server fails to start, then:
View the Administration Server and Managed Server log files in the following directory:
BI_DOMAIN/servers/AdminServer/logs
You can also check the Managed Server log files in the following directory:
BI_DOMAIN/servers/bi_server1/logs
Cause: Database Down: in AdminServer.log, "Caused By: java.net.UnknownHostException: yourcomputername" deep in the trace from:
####<Jan 19, 2010 8:04:09 PM PST> <Info> <JDBC> <username> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <Stack trace associated with message 001129 follows:
java.sql.SQLException: The Network Adapter could not establish the connection.
Resolution: Start the database.
If the Managed Server is down, then use the command line to start it.
For information, see Starting Oracle Business Intelligence Component Processes in a Domain.
If the BI Server fails to start, then view the log files.
View log files in the Log Viewer or in the following directory:
BI_DOMAIN/servers/obis1/logs, or use the Log Viewer.
Problem: Cannot log in to Oracle WebLogic Server Administration Console.
Cause: The Administration Server is not running.
Resolution: Check to see if http://<host>:<port>/console starts. If not, start the BI system. For information, see Using Commands to Start, Stop, and View Status of Oracle BI EE Processes.