Error at step 11 of 12 in Scale out BI system while implementing horizontal clustering.

Error: When implementing horizontal clustering in OBIEE. The process failed at the step of starting BI_Server. The Scale out BI System completed up to 73%.

Cause: Extending domain can't start the BI_Server.

Solution:

1: Do not close the installation window.

2: Check the managed server(bi_server1) log

3: In our case error shown is:

"<Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: java.lang.AssertionError: java.net.UnknownHostException: Host Name
java.lang.AssertionError: java.net.UnknownHostException: Host Name"


4: Edit /etc/hosts file in both machines the one we are extending the domain and the one we installed our weblogic server

And added the following entries in the file.

ip hostname hostname.domainname(of the working machine)
ip hostname hostname.domainname(of the machine taht we want to connect)

5: Then try starting the managed server using the command startManagedWebLogic.cmd bi_server1 http://<Admin Server IP Address/Host name>:7001 

6: This will start your managed server.Then from the configuration wizard where we stuck select the tick box on the top.

7: Then retry the extending domain proess.

[SOLVED] Node manager is down after configuring SSL in weblogic [Cannot convert identity certificate]

Error:  <SEVERE>  <Fatal error in node manager server>
java.lang.RuntimeException: Cannot convert identity certificate

Cause:Reason for this issue is we configured SSL.enableJSSE=true  in weblogic console only. We need to set this option in startNodeManager.sh file also

Solution: Edit your startNodeManager.sh file and add the below tag in the following location

Tag to add : "-Dweblogic.security.SSL.enableJSSE=true"

[SOLVED] [BEA-090174] :The trust keystore configuration specified on the command line or in boot.properties does not match the trust keystore configuration specified in config.xml. in Linux

Error : After enabling SSL in OBIEE the SSL enabled URL is not working. In the admin and bi server start up log we got the following error

 "<BEA-090174> <The trust keystore configuration specified on the command line or in boot.properties does not match the trust keystore configuration specified in config.xml.>"

Cause: The keystore that specified in the Admin server is not matching with the one in boot.properties file, In our case admin server is configured to use Custom Identity and Custom Trust file but boot.properties file pointing to Demo certificates. 

Solution: Edit the boot.properties file in Admin and BI server. 

boot.properties file location: /home/oracle/MWHome/user_projects/domains/bifoundation_domain/servers/(select your server)/security/

Remove the tag TrustKeyStore=DemoTrust

Do the change in admin and bi_server after save the file and restart the services.

After restarting you can see Admin server can load the certificates from the mentioned locations as shown below.

Hope this will solve your issue.

Linux Commands to stop and start OBIEE11g and Managed servers.

------------Opmnctl stop--------------------------------

$ cd /home/oracle/MWHome/instances/instance1/bin/
$ ./opmnctl stopall


-----------Stop Managed weblogic---------------------

----bi_server1---------
$ cd /home/oracle/MWHome/user_projects/domains/bifoundation_domain/bin/
$ ./stopManagedWebLogic.sh bi_server1 t3://host name:7001 user_name Password

----odi_server1---------
$ ./stopManagedWebLogic.sh odi_server1 t3://host name:7001 user_name Password


------------Stop Admin server-------------------------
$ ./stopWebLogic.sh user_name Password t3://hostname:7001

-----------Stop Node Manager---------------------
$ ps -ef | grep Node | grep nodemanager | grep -v grep | cut -c10-15
$ kill -9 ****

------------Start Node Manager----------------------

$ cd /home/oracle/MWHome/wlserver_10.3/server/bin/

$ nohup ./startNodeManager.sh > Node_manager.out &

------------Start Admin server----------------------
$ cd /home/oracle/MWHome/user_projects/domains/bifoundation_domain/bin/
nohup sh startWebLogic.sh -Dweblogic.management.username=username -Dweblogic.management.password=Password > admin_server.log &

[Start up logs will be written to admin_server.log in the same directory]


to check the log :tail -f admin_server.log

ctrl-z or ctrl-c to exit log window


-----------Start Managed Server-------------

-----bi_server1----------------
$ nohup sh ./startManagedWebLogic.sh bi_server1 t3://localhost:7001 > managed_server_bi.log &

----odi_server1----------------
$ nohup sh ./startManagedWebLogic.sh odi_server1 t3://localhost:7001 > managed_server_odi.log &


---------Start Opmnctl----------------
$ cd /home/oracle/MWHome/instances/instance1/bin/
$ ./opmnctl startall



courtesy:http://hareeobiee.blogspot.in/2013/10/stop-and-start-obiee-11g-linux.html

OBIEE 11g Pointing Connection Pool to another data base in RPD.

Scenario : We need to point data source of OBIEE from one database to another database.

Solution: We can do this through RPD in RPD change the connection pool details and point this to another database

Connection Pool: Connection pool is an object in RPD physical layer that used to define the connection details between BI server and data source.

Double click on the connection pool that you want to edit.

If you are using OCI for connecting to database do the following

Edit the server details in tnsname file located in the below location or add new connection details.

D:\obiee11g\Oracle_BI1\network\admin

Add tns entry for new database and and save the file.

Now take the connection pool and edit the details

For Data source name give the name that you provided in the tns file. Then give the User name and Password for the connection.

After giving Password check the connection by updating row count of tables.


Another method for doing the same is gave the connection description in data source name itself

[OBIEE 11g] Weblogic SSL Error ERR_SSL_VERSION_OR_CIPHER_MISMATCH in Chrome [Solved]

Error:

While opening SSL enabled OBIEE url we got the following error as shown in the screen shot.

Description: SSL Error ERR_SSL_VERSION_OR_CIPHER_MISMATCH in Chrome

Cause:

Google chrome was updated to 48 and the latest version of chrome had dropped RC4 encryption support.

Solution:

Make a back up of the config file of OBIEE from the below mentioned location

$MW_HOME/user_projects/domains/bifoundation_domain/config

File: config.xml

Then edit the config file and add  line <ciphersuite>TLS_RSA_WITH_AES_128_CBC_SHA</ciphersuite>

after already existing cipher-suite

Then the file will look like.

Do the same for bi server also.

Then restart weblogic and you can log into the SSL enabled OBIEE easly.