My Oracle Support Banner

OBIEE11g: Essbaseserver1 is Down After Changing OBIEE listener Database port in JDBC datasource (Doc ID 1636367.1)

Last updated on DECEMBER 02, 2019

Applies to:

Business Intelligence Server Enterprise Edition - Version 11.1.1.7.1 and later
Information in this document applies to any platform.

Symptoms

The EssbaseServer1 is down we change the database listener port in the JDBC datasource.

The output of opmnctl status is shown as below:
Processes in Instance: <INSTANCE_NAME>
---------------------------------+--------------------+---------+---------
ias-component                    | process-type       |     pid | status  
---------------------------------+--------------------+---------+---------
essbasestudio1                   | EssbaseStudio      |   <PID1> | Alive  
essbaseserver1                   | Essbase            |     N/A | Down    
coreapplication_obiccs1          | OracleBIClusterCo~ |   <PID2> | Alive  
coreapplication_obisch1          | OracleBIScheduler~ |   <PID4> | Alive  
coreapplication_obijh1           | OracleBIJavaHostC~ |   <PID3> | Alive  
coreapplication_obips1           | OracleBIPresentat~ |   <PID5> | Alive  
coreapplication_obis1            | OracleBIServerCom~ |   <PID6> | Alive  

Changes

 Steps made in the JDBC datasource.

  1. Login to Oracle Weblogic Admin console and navigate to: Home Page >> Domain Configurations >> Services >> JDBC >> Data Sources >> Connection Pool for each Data Sources
  2. Update the URL property to the new listener port. 

    from 

         jdbc:oracle:thin:@<DB_HOSTNAME1>:<DB_PORT1>/<SID>

    to

         jdbc:oracle:thin:@<DB_HOSTNAME1>:<DB_PORT2>/<SID>

 

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.