- 17.9K All Categories
- 3.3K Industry Applications
- 3.3K Intelligent Advisor
- 60 Insurance
- 534.5K On-Premises Infrastructure
- 137.7K Analytics Software
- 38.5K Application Development Software
- 5.3K Cloud Platform
- 109.1K Database Software
- 17.5K Enterprise Manager
- 8.8K Hardware
- 70.8K Infrastructure Software
- 105.1K Integration
- 41.5K Security Software
OBIEE 12C connect string update
I hope this is the right place to ask this question.
BI Platform 184.108.40.206.0
OS: RHEL 7.8
DB: Oracle 12C
We replace our old OBIEE 11G with OBIEE 12C about a month ago, when we did the install we used the connection format example in the Graphical Installer to our then active DB, e.g server2:port:service_name.
After the install we updated the connection string for all the data sources to use the TNS type connection string so that we can use the Data Guard failover e.g.
Last night we wanted to failover to server1 so that we can get some maintenance done on server2. After the failover we test PDF generation from our application and it failed, we tried to restart the OBIEE and at first noticed this error:
Received error message from Node Manager Server: [Server start command for OBISCH server 'obisch1' failed due to: [Server failed to start up but Node Manager was not aware of the reason]. Please check Node Manager log and/or server 'obisch1' log for detailed information.]. Please check Node Manager log for details.
Failure to start one or more ManagedServers and or Components
Fatal: Failed to start one or more Servers (return 3)
Then further back in the startup sequence we noticed this error message:
Received error message from Node Manager Server: [Server start command for OBIS server 'obis1' failed due to: [Unexpected exception from Plugin: java.lang.RuntimeException: Failed to get environment
Unable to obtain Jdbc connection from DataSource
SQL State : 08006
Error Code : 12514
Message : Listener refused the connection with the following error:
ORA-12514, TNS:listener does not currently know of service requested in connect descriptor
At this point our application has failed over to the DB on server and we had no other errors. Only OBIEE did not start up.
I then did a grep through the config files in Oracle home and found the old config in the below two files.
I manually edited the file to have the correct server details, trying both the TNS connection string style as well as the hostname:port:service_name style of connection string but neither worked.
The only thing that worked was to fail back to the old DB server and then everything started up. Now we in a situation were we cannot do a failover on the DB (Data Guard failover) because we depend on proper working of the OBIEE to generate our PDF files.