1 minute reading time (199 words)

Oracle Fusion Apps: BI Instance processes would not start and result in error

Issue

Run the following command to start the BI instance (after successfully starting all the Fusion Applications domains). But BI processes wouldn't start and will result in error.

Command: $FA_BASE/instance/BIInstance/bin/opmnctl startall

Error Output

/app/APPLTOP/instance/BIInstance/bin/opmnctl startall
opmnctl startall: starting opmn and all managed processes...
================================================================================
opmn id=fa87.aclnz.com:10204
Response: 2 of 6 processes started.

ias-instance id=BIInstance
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
ias-component/process-type/process-set:
coreapplication_obijh1/OracleBIJavaHostComponent/coreapplication_obijh1/

Error
--> Process (index=1,uid=660672207,pid=7194)
failed to start a managed process after the maximum retry limit
Log:
/dev/null

ias-component/process-type/process-set:
coreapplication_obisch1/OracleBISchedulerComponent/coreapplication_obisch1/

Error
--> Process (index=1,uid=660672208,pid=7136)
failed to start a managed process after the maximum retry limit
Log:
/app/APPLTOP/instance/BIInstance/diagnostics/logs/OracleBISchedulerComponent/coreapplication_obisch1/console~coreapplication_obisch1~1.log
ias-component/process-type/process-set:
coreapplication_obiccs1/OracleBIClusterControllerComponent/BIClusterController/

Error
--> Process (index=1,uid=660672209,pid=7193)
failed to start a managed process after the maximum retry limit
Log:
/dev/null
ias-component/process-type/process-set:
essbaseserver1/Essbase/AGENT/

Error
--> Process (index=1,uid=660672210,pid=7084)
failed to start a managed process after the maximum retry limit
Log:
/app/APPLTOP/instance/BIInstance/diagnostics/logs/Essbase/essbaseserver1/console~AGENT~1.log

Cause

After an in-depth analysis and investigation we found that the issue had come as a result of someone previously using "root" superuser to start the BI instance. As a result some of the file ownership were automatically updated to the "root" user.

Fix

Simply change the ownership to the fusion apps user (in our case the user name was "fusion") and give 755 permission to the following directories using chown and chmod commands respectively:

$FA_BASE/instance/BIInstance

Now simply try restarting the BI instance and it will be successfully started this time.

Environment

+ Oracle Fusion Applications - Release 11.5.9

+ Oracle Linux 5.7


[SOLVED] How to concatenate ova files in Windows10...
Oracle Database Tier patch 24911308 failed to get ...