TROUBLESHOOTING (PS) - TMADMIN_CAT:196: ERROR: The boot mode is only available on the MASTER processor

ISSUE:
While booting the app server on Virtual box for PUM getting below error:

TMADMIN_CAT:196: ERROR: The boot mode is only available on the MASTER processor

SOLUTION:
Recently after upgrading my virtual box on windows 10, I am unable to boot the app server on PUM, possibly due to some configuration file PSTUXCFG corrupted.

To resolve the issue:
1. Take the backup of existing PSTUXCFG file.
2. Delete/Rename the PSTUXCFG file.
3. Reconfigured the domain with the same settings.
4. Boot the domain again.

Issue resolved.

TROUBLESHOOTING - X-server Xming unable to take input for Oracle FMW, Weblogic, DBCA wizard redirected using DISPLAY redirection

ISSUE:
X-server Xming unable to take input for Oracle FMW, Weblogic, DBCA wizard redirected using DISPLAY redirection

Recently while doing an OBIEE softtware install on linux server using EXPORT DISPLAY variable and rdirecting outout to a wintel machine using X-server like Xming, I was unable to provide keyboard input for Oracle FMW, Weblogic, DBCA wizard, as given  in below screenshots.





SOLUTION:
There was no solution found on MOS but after investigation it has been found that this kind of issue might appear due to incorrect JAVA version compatibility between XMing, Oracle software wizzards in commEnv.sh.

In order to fix the issue, I had to use a lower JDK version from a temp location.

1.) Download JDK version 1.6.0_45 could be downloaded from below URL:

http://www.oracle.com/technetwork/java/javase/downloads/java-archive-downloads-javase6-419409.html

2.) Once downloaded, extract install JDK in a temp location say /opt/oracle/test_java/jdk1.6.0_45

3.) Take the backup of commEnv.sh present inside <FMW_HOME>/wlserver_10.3/commn/bin

4.) Open the commEnv.sh and find JAVA_HOME
Comment out the exising higher version JAVA_HOME path and add New JAVA_HOME value for lower version JDK.

JAVA_HOME="usr/java/jdk1.7.0_05"
JAVA_HOME="/opt/oracle/test_java/jdk1.6.0_45"



5.) Save the file.

6.) Close the Oracle FMW, Weblogic, DBCA wizard on wintel.

7.) Execute the command fro Lnux machine using XMing & DISPLAY variable and this time you should be able to use keyboard and mouse successfully in the wizzard.

8.) Once wizzard run successfully. Rvert back the JDK version in commEnv.sh to original values for JDK higher version.

TROUBLESHOOTING (OBIEE)- “TNS:could not resolve the connect identifier specified at OCI call OCIServerAttach”

ISSUE/ERROR:

While generating result for a simple analysis in OBIEE getting below error when clicked on result tab :

Odbc driver returned an error (SQLExecDirectW).

  Error Details

Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P

State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 17001] Oracle Error code: 12154, message: ORA-12154: TNS:could not resolve the connect identifier specified at OCI call OCIServerAttach. [nQSError: 17014] Could not connect to Oracle database. (HY000)

SOLUTION:

This error indicate that when OBI reports/servers tries to connect to database something not working/appropraite at client(browser/BI server) and DB connectivity level. In OBIEE (an other apps too) it could primarily due to below reasons:

1.) At rpd level there is incorrect details of  Data Source Name (DSN) in your connection pool configuration. Make sure it matches to what you have in your tnsnames.ora file

2.) At rpd details of  Data Source Name (DSN) is correct but in tnsnames.ora file DSN details are not correct. Make sure it matches to what you have in your tnsnames.ora file

3.) Possibly you have multiple tnsnames.ora on the machine server names. (OBIEE usees tnsnames.ora file present at <FMW_HOME>\Oracle_BI1\network\admin for example C:\app\Manish\product\11.2.0\OBIEE11.1.1.6.0\Oracle_BI1\network\admin

In my case its was scenario-3 for the issue. Below are the steps I followed to resolve the issue.

1.) log in to the server

2.) go to the directory where the tnsnames.ora file is located

cd $FMW_HOME/Oracle_BI/network/admin

3.) create a copy of tnsnames.ora

cp tnsnames.ora tnsnames.ora[_orig_date]

4.) edit the tnsnames.ora file and add the entr for your DSN name. Save and Exit.

5.) Restart all the bI services to pick the latest tns/dsn entries.

TROUBLESHOOTING (OBIEE/WEBLOGIC) - Windows registry related error while running startWebLogic.cmd

ISSUE:

While running startWebLogic.cmd below error is displayed:

<20 Mar, 2016 8:23:39 PM IST> <Error> <oracle.bi.management.localservices> <OBI-SYSMAN-1108> <Unexpected error configuring ODBC DSNs
oracle.bi.installhandler.util.ConfigurationException: Non-zero (1) return value Updating windows registry entry: Key: HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\coreapplication_OH2030226780, Type: REG_SZ, Value: SecondaryCCS, Data: "", process stdout:

stderr:

ERROR: Access is denied.

Though the weblogic admin services gets started successfully and could login into weblogic console & EM but but notsure why error is appearing. Similar issue could also appear in starting the managed web servers as well.

SOLUTION:
The possible root cause seems related to the user id used to start the startWebLogic.cmd as windows 7, 8 & 10 have added constraints on access & permissions.

When startWebLogic.cmd is started as an administrator user i.e. "Run as Administrator", error does not appear.