Starting OBIEE 12c from Command Prompt

You can directly start the OBIEE 12c services by going to the Middleware home folder and to the path below, 

Oracle_FMW/user_projects/domains/bifoundation_domain/bitools/bin

Now open a command prompt window, Shift + Righ Click and then type the filename start.cmd. This will start the execution of OBIEE 12c services. 

Alternatively you can run each component individually as it was done previously for OBIEE 11g.

OBIEE 12c Client Administration tool OCI DB connectivity issue

Issue: We were trying to make a connection to Oracle database to import metadata to the OBIEE repository.

Cause: The tnsnames.ora file not present in MW_HOME/network/admin

Resolution:  Even if you have tnsnames.ora in your app folder in your database client folder, you need to have a copy of the same tnsnames.ora file at network/admin folder inside MW_HOME folder created by OBIEE.

So copy the tnsnames.ora file to this location or create a new one and try restarting the Administration tool before trying again. Let us know if you are still facing issues in the comments. 

OBIEE/Weblogic 12c Node Manager Startup Error - DemoIdentity.jks file missing [Solved]

Here is an issue we faced while trying to startup the Node manager in Oracle Business Intelligence 12c when we trying to start the nodemanager service. The issue is caused by a java keystore file missing from a location inside middleware home folder. 

Issue: DemoIdentity.jks keystore file missing from the security folder inside nodemanager folder, i.e at the path

 FMW_HOME/oracle_common/common/nodemanager/security

weblogic.nodemanager.common.ConfigException: Identity key store file not found: Middleware/Oracle_Home/oracle_common/common/nodemanager/security/DemoIdentity.jks Cause: The DemoIdentity.jks file missing from the security folder for nodemanager.

Resolution:

The DemoIdentity.jks file would be available at the folder,

FMW_HOME/user_projects/domain/bifoundation/security

Copy the file from this folder to inside the secuirity folder for NodeManager. Once you have copied the file, try restarting the nodemanager. It worked well for us.