Confirming Whether the Administration Server Is Running

Starting and Stopping Oracle Business Intelligence 4-11 ■ On UNIX, open a shell prompt and change the directory to MW_HOMEuser_ projectsdomainsbifoundation_domainbin. Then, run the following command which requires the administrator user name and password: .stopWebLogic.sh You can also use the process termination command for the operating system in use for example, kill on UNIX. Java indicates on the console window that it is shutting down when it receives a shutdown signal.

4.8 Starting and Stopping Managed Servers on Windows and UNIX

You can start and stop Managed Servers on Windows and UNIX. The system does not include a Managed Server if the Simple Install type was selected during installation. To start Managed Servers on Windows and UNIX: Use the appropriate method for the operating system: ■ Open an MS-DOS window and change the directory to MW_HOME\user_ projects\domains\bifoundation_domain\bin. Then, run the following command which requires the administrator user name and password, for example: startManagedWebLogic.cmd bi_server1 http:administration_server_host_ name:7001 You can also stop the Java components from the MS-DOS window in which they were started, if you press Ctrl+C. ■ On UNIX, open a shell prompt and change the directory to MW_HOMEuser_ projectsdomainsbifoundation_domainbin. Then, run the following command which requires the administrator user name and password, for example: .startManagedWebLogic.sh bi_server1 http:administration_server_host_ name:7001 To stop Managed Servers on Windows and UNIX: Use the appropriate method for the operating system: ■ On Windows, open an MS-DOS window and change the directory to MW_ HOME\user_projects\domains\bifoundation_domain\bin. Then, run the following command which requires the administrator user name and password, for example: stopManagedWebLogic.cmd bi_server1 http:administration_server_host_ name:7001 Caution: If you start Managed Servers from a Windows or UNIX command-line window, then do not close the window later on, or the server terminates. For more information, see Setting Up a WebLogic Server Instance as a Windows Service in Oracle Fusion Middleware Managing Server Startup and Shutdown for Oracle WebLogic Server. Do not use the startManagedWebLogic.sh script that is located in MW_HOMEwlserver_10.3commonbin because it is not supported. 4-12 System Administrators Guide for Oracle Business Intelligence Enterprise Edition You can also stop the Java components from the MS-DOS window in which they were started, if you press Ctrl+C. ■ On UNIX, open a shell prompt and change the directory to MW_HOMEuser_ projectsdomainsbifoundation_domainbin. Then, run the following command which requires the administrator user name and password, for example: .stopManagedWebLogic.sh bi_server1 http:administration_server_host_ name:7001 You can also use the process termination command for the operating system in use for example, kill on UNIX. Java indicates on the console window that it is shutting down when it receives a shutdown signal.

4.8.1 Confirming If the Managed Server Is Running and Starting It

You can use Oracle WebLogic Server Administration Console or Fusion Middleware Control to confirm whether the Managed Server is running, and start it if necessary. The system does not include a Managed Server if the Simple Install type was selected during installation. To confirm whether the Managed Server is running, and start it if necessary using Oracle WebLogic Server Administration Console: 1. Log in to Oracle WebLogic Server Administration Console using the following URL: http:host:7001console For information, see Section 2.3, Centrally Managing Oracle Business Intelligence Java Components Using the Oracle WebLogic Server Administration Console. 2. Under the bifoundation_domain, expand the Environment node in the navigation tree, and click Servers. 3. Display the Configuration tab. There should be two servers listed: AdminServer the Administration Server and bi_server1 Managed Server. 4. Start the Managed Server, if not running: a. Display the Control tab. b. Select the box next to the Managed Server for example, bi_server1.

c. Click Start.

Repeat this step for each Managed Server. For information about starting Managed Servers on Windows and UNIX, see Section 4.8, Starting and Stopping Managed Servers on Windows and UNIX. 5. Optional Perform an OPMN stopall for the system components, and then a startall. For information, see Section 4.5.1, Using the OPMN Command Line to Start, Stop, Restart, and View the Status of System Components. To confirm whether a Managed Server is running, and start it if necessary using Fusion Middleware Control: 1. Log in to Fusion Middleware Control using the following URL: http:host:7001em Starting and Stopping Oracle Business Intelligence 4-13 For information, see Section 2.2, Centrally Managing Oracle Business Intelligence Components Using Fusion Middleware Control. 2. Under the WebLogic Domain expand the bifoundation_domain node in the navigation tree, and select bi_cluster. Expand the bi_cluster node to display the Managed Servers for example, bi_ server1. Fusion Middleware Control displays the status in the Deployments region. 3. Select bi_cluster, and click the WebLogic Cluster menu.

4. Select the Control option from the menu, and select Start Up to start the Managed

Servers. 5. Optional Perform an OPMN stopall for the system components, and then a startall. For information, see Section 4.5.1, Using the OPMN Command Line to Start, Stop, Restart, and View the Status of System Components.

4.9 Troubleshooting System Startup

This section contains solutions that are related to system startup: ■ Section 4.9.1, Administration Server Fails to Start When the Database Is Not Running ■ Section 4.9.2, Managed Server Is Down ■ Section 4.9.3, Oracle BI Server Fails to Start ■ Section 4.9.4, Oracle BI Presentation Services Fails to Start ■ Section 4.9.5, Cannot Log In

4.9.1 Administration Server Fails to Start When the Database Is Not Running

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: \user_projects\domains\bifoundation_domain\servers\AdminServer\logs You can also check the Managed Server log files in the following directory: \user_projects\domains\bifoundation_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.