Friday, August 9, 2013

Reason: Cannot apply patch due to fatal error & CheckActiveFilesAndExecutables failed

We have seen below error when user applying latest SBP patch on Oracle Database .


Running prerequisite check "CheckMultipleTranslationPatches" ... UtilSession failed: Prerequisite check "CheckActiveFilesAndExecutables" failed.Prerequisite check "CheckActiveFilesAndExecutables" failed.
Log file location: /oracle/RACP/112_64/cfgtoollogs/opatch/opatch2013-07-24_17-44-07PM_1.log

OPatch failed with error code 73
Processing patch "!16056266!16056266"...failed.
Reason: Cannot apply patch due to fatal error.

In mopatch or opatch log file, user will not find enough information except “Reason: Cannot apply patch due to fatal error”. The log file mention in the mopatch log will have reason for failure.

Contents from log file /oracle/RACP/112_64/cfgtoollogs/opatch/opatch2013-07-24_17-44-07PM_1.log

[Jul 24, 2013 5:37:13 PM] Following executables are active :
[Jul 24, 2013 5:37:13 PM] Prerequisite check "CheckActiveFilesAndExecutables" failed.
[Jul 24, 2013 5:37:13 PM] OUI-67073:UtilSession failed: Prerequisite check "CheckActiveFilesAndExecutables" failed.Prerequisite check "CheckActiveFilesAndExecutables" failed. 

Opatch or Mopatch needs to modify some files which are still being used by some process. As you see one of the Oracle library is still active.

Find out the process which is still actively using the library /oracle/RACP/112_64/lib/ and kill or stop the process.

$ /sbin/fuser /oracle/RACP/112_64/lib/
/oracle/RACP/112_64/lib/ 9785m

$ ps –ef |grep 9785
oraracp 9785 1 0 Jul24 ? 00:02:39 /oracle/RACP/112_64/bin/tnslsnr LISTENER_RACP -inherit
oraracp 19813 7919 0 17:25 pts/2 00:00:00 grep 9785

$ lsnrctl stop LISTENER_RACP
$ kill -9 9785

The listener process is still running and causing the issue. We have stopped the listener process and reapplied the patch successfully.


Satisbabu Gunukula, Oracle ACE

Wednesday, August 7, 2013

Database error : (CS) "Java Class not found in classpath : com.mysql.jdbc.Driver"(WIS 10901)

The users will see below error if they don’t configure JDBC connection properly to connect MYSQL database.

Database error : (CS) "Java Class not found in classpath : com.mysql.jdbc.Driver" . (WIS 10901)

Follow below troubleshooting steps

1. Locate jdbc.sbo file and make sure that you have added “ClassPath” with correct MySQL Connector jar file.

<Path>/home/boxi/ bobj/enterprise_xi40/dataAccess/connectionServer/jdbc/mysql-connector-java-5.1.25-bin.jar</Path>

2. Update environment variable CLASSPATH with correct jar file path.

3. Make sure that the MySQL Connector jar file is right version, means for 64bit O/S or app use 64bit jar file.

Common Error in ODBC:- 

1. The below error message is very common when using ODBC(.odbc.ini) connection

[01000][unixODBC][Driver Manager]Can't open lib '/home/boxi/bobj/enterprise_xi40/linux_x64/odbc/lib/' : /home/boxi/bobj/enterprise_xi40/linux_x64/odbc/lib/ wrong ELF class: ELFCLASS32

Cause: The file is not the right version

Possible Solution: The file is not 64-bits version of the, install the right version. Use 32bit version of the, if using 32bit.

Download MySQL Connector/ODBC

Satishbabu Gunukula, Oracle ACE 

Error (1023040): msg from remote site and (1051293) Login fails due to invalid login credentials

Users may receive below error while running Hyperion Financial Reports and also may see similar error message in Smart-view

Error Execuring query: Error: Internal Essbase JAPI error: [Cannot perform cube view operation. Essabase Error (1023040): msg from remote site [[Thu jul 25 10:11:13 2013]Local////Error(1051293) Login fails due to invalid login credentials]]

For troubleshooting check the logs under diagnostics ($APPLICATION_CONFIG_HOME/ Middleware/user_projects/epmsystem_linux/diagnostics/logs).

When looking into the Essbase Application log found below error message…

Error executing formula for [529100_OVH]: status code [1051293] in function [@_XREF]
An error [1051293] occurred in Spreadsheet Extractor.
Transaction [ 0x89002e( 0x51ef11b9.0x3e7a ) ] aborted due to status [1051293].

By looking all the error messages, it looks like some issues with the user credentials trying to read essbase cube. When we look into the cube location alias found out the actual issue.

The user account that is using under “Location Alias” is a Microsoft Active Directory Account which is expired. Updated the “Location Alias” with Admin credentials and RESOLVED the issue.

It is always advisable to use admin credentials instead of individual users to avoid these MSAD issues in future.

To update Location Alias follow the steps.

1. Login into Essbase Admin Services console
2. Select the Reveneu/Expense cube à Edit ‘ Location Alias’
3. Enter the corrent credetials or Admin credentials.

Satishbabu Gunukula, Oracle ACE