Oracle Business Intelligence Enterprise Edition 11g Start and Stop - My Oracle Support Docs

UNIX or LINUX:

Note 1415520.1 - How To Start OBIEE 11.1.1.1.5.0. on Unix or Linux.
Note 1415581.1 - How To Stop OBIEE 11.1.1.1.5.0. on Unix or Linux.
Note 1240964.1 - How To Start / Stop An OBIEE 11g (11.1.1.x) Unix / Linux Environment Via Command-line

Generic:

Note 1415554.1 - Directories, Homes, Environment Variables Used by OBIEE 11.1.1.5.0
Note 1442242.1 - Automatically Stopping Bi Services In OBIEE 11g


Windows:

Note 1415584.1 - How To Start OBIEE 11.1.1.1.5.0. on Windows.
Note 1415587.1 - How To Stop OBIEE 11.1.1.1.5.0. on Windows.
Note 1372038.1 - Steps and order to start and launch Obiee 11g

Oracle E-Business Suite Concurrent Request That Shows Running or Hanging, but has Completed

SOLUTION:

1. Stop the concurrent managers only from the primary node. It should stop the concurrent manager
on the secondary node.

a. Run the Concurrent Manager Recovery within Oracle Applications Manager.

Navigate:

Oracle Applications Manager > Concurrent Managers OR Concurrent Requests > Site Map > Diagnostics and Repair > Concurrent Manager Recovery

See Concurrent Manager Recovery Troubleshooting Wizard (Document 134007.1)

b. Restart the concurrent managers on the primary node.


NOTE: If the above does not clear it up, then proceed to step 2.  ATTENTION: Manual updates to Application tables from sqlplus are not supported.

2. Backup the fnd_concurrent_requests table.

3. For the request_id that is running/hanging where 'request_id' is to be replaced with the actual concurrent request id:

SQL>update FND_CONCURRENT_REQUESTS
set STATUS_CODE='D', PHASE_CODE='C'
where request_id='request_id';


4. After commiting the update above, verify the request is now resolved.



Reference: How To Clear Up a Request That Shows Running, but has Completed (Doc ID 1684368.1)