OBIEE 11g（v.11.1.1.9.0）安装卡在部署Financial Reporting JEE应用步骤求助

Fixes for OBIEE 11g (11.1.1.9.0) Stuck at "Deploying Financial Reporting JEE Application" #

Hey there, sorry to hear you're hitting this roadblock during your OBIEE 11g installation—this is a super common pain point with the 11.1.1.9.0 release, so let's work through some tried-and-true solutions:

• First, dig into the logs to find the root cause
  Don't guess why it's stuck—check the installation and server logs for specific errors. Key log locations:

  • Installation log: ORACLE_HOME/inventory/logs/installActions<timestamp>.log
  • AdminServer log: MW_HOME/user_projects/domains/bifoundation_domain/servers/AdminServer/logs/AdminServer.log
  • Financial Reporting Server log: MW_HOME/user_projects/domains/bifoundation_domain/servers/FinancialReportingServer/logs/FinancialReportingServer.log
    Look for keywords like "port occupied", "permission denied", or "database connection failed"—these will point you to the exact problem.

• Check for port conflicts
  The Financial Reporting JEE app relies on specific ports (AdminServer defaults to 7001, FR Server to 9704). Use these commands to see if another process is hogging them:

  • Windows: netstat -ano | findstr :7001 (then kill the process with Task Manager using the PID)
  • Linux/Unix: lsof -i :7001 (kill with kill -9 <PID>)
    If ports are taken, you can either free them up or adjust the port settings in the WebLogic domain config before resuming the install.

• Verify directory permissions
  On Linux/Unix, make sure the user running the installer has full read/write access to your MW_HOME and ORACLE_HOME directories. A quick fix (use cautiously) is to run:

  chmod -R 755 /path/to/MW_HOME
  chmod -R 755 /path/to/ORACLE_HOME
  

  On Windows, ensure you're running the installer as Administrator to avoid permission locks.

• Restart the AdminServer and installer
  Sometimes the deployment gets stuck due to a temporary glitch. Here's what to do:

  1. Cancel the current installation process.
  2. Stop the AdminServer: run MW_HOME/user_projects/domains/bifoundation_domain/bin/stopWebLogic.sh (Linux) or stopWebLogic.cmd (Windows). Wait until it's fully shut down.
  3. Restart the installer—it should detect the partially completed install and give you a "Resume" option. Pick that and see if it proceeds past the stuck step.

• Check your OBIEE schemas in the database
  The Financial Reporting app depends on the BIPLATFORM and MDS schemas you created with RCU. Connect to your database and run this query to verify their status:

  SELECT OWNER, SCHEMA_VERSION, STATUS FROM SCHEMA_VERSION_REGISTRY WHERE OWNER IN ('<BIPLATFORM_SCHEMA_USER>', '<MDS_SCHEMA_USER>');
  

  All entries should show STATUS = VALID and match your OBIEE version (11.1.1.9.0). If any are invalid, re-run RCU to repair the schemas before continuing.

• Boost JVM memory for the AdminServer
  Insufficient JVM memory can cause deployment timeouts. Edit the domain's environment script:

  • Linux: MW_HOME/user_projects/domains/bifoundation_domain/bin/setDomainEnv.sh
  • Windows: MW_HOME/user_projects/domains/bifoundation_domain/bin/setDomainEnv.cmd
    Find the MEM_ARGS line and increase the heap size, for example:

  MEM_ARGS="-Xms1024m -Xmx2048m"
  

  Save the changes, restart the AdminServer, and resume the installation.

• Manual deployment as a last resort
  If none of the above works, skip the installer's deployment step and deploy the FR app manually via the WebLogic Console:

  1. Log into the WebLogic Console at http://<your-server>:7001/console using your admin credentials.
  2. Go to Deployments > Install.
  3. Navigate to ORACLE_HOME/bi/bifoundation/jee/FinancialReporting.ear, select the file, and follow the deployment wizard prompts.
  4. Once deployed, start the Financial Reporting application from the Deployments list.
  5. Go back to the installer—it should recognize the deployed app and let you finish the installation.

内容的提问来源于stack exchange，提问作者prasad