Disclaimer

These scripts come without warranty of any kind. Use them at your own risk. I assume no liability for the accuracy, correctness, completeness, or usefulness of any information provided by this site nor for any sort of damages using these scripts may cause.
Showing posts with label error. Show all posts
Showing posts with label error. Show all posts

Sunday, May 30, 2021

Error when application cloning- adcfgclone: EBS R12.2 /etc/inittab does not seem to contain default runlevel information. Linux 7.x

Environment Details:

OS: RHEL 7.8 
EBS Release: 12.2.4
AD/TXK delta 12
ATG: 7

Issue: 

While cloning (adcfgclone) the EBS R12.2 on Linux 7.8 getting below error.


Check Name:CertifiedVersions
Check Description:This is a prerequisite condition to test whether the Oracle software is certified on the current O/S or not. 
/etc/inittab does not seem to contain default runlevel information. 
Expected result: One of oracle-7,redhat-7,redhat-6,oracle-6,oracle-5,enterprise-5.4,enterprise-4,enterprise-5,redhat-5.4,redhat-4,redhat-5,SuSE-10,SuSE-11 
Actual Result: redhat-Red 
Check complete. The overall result of this check is: Failed <<<<

Solution:
Verify the RPM redhat-lsb-4.1-27.0.1.el7.x86_64 is Installed on the server. If missing, install it. This is a pre-requisite for EBS R12.2 on Linux 7.x

Thursday, July 20, 2017

java.sql.SQLException: ORA-28040: No matching authentication protocol


When connecting to 10g ,11g or 12c databases using a  JDBC thin driver , fails with following errors:
The Network Adapter could not establish the connection

ORA-28040: No matching authentication protocol

This happens because you are using a non compatible version of JDBC driver.

To resolve this issue, make sure that you are using the latest version of Oracle JDBC driver, if not use JDBC 12c or higher versions.


Oracle Client/Server Compatibility Matrix: 

Oracle Client
Version
Database Version
12.2.012.1.011.2.011.1.010.2.010.1.09.2.0
12.2.0YesYesYesNoNoNoNo
12.1.0YesYesYesWasMDSNoNo
11.2.0YesYesYesWasMDSNoWas
11.1.0NoWasWasWasWasWasWas
10.2.0NoMDSMDS WasMDSWasWas
10.1.0NoNoWas WasWasWasWas
9.2.0NoNoWas WasWasWasWas

Key:
YesSupported
ESSupported but fixes only possible for customers with Extended Support .
LES or MDSSupported but fixes only possible for customer with a valid Limited Extended Support or Market-Driven Support contract respectively.
WasWas a supported combination but one of the releases is no longer covered by any of Premier Support, Primary Error Correct support, Extended Support, nor Extended Maintenance Support. Fixes are no longer possible.
NoHas never been Supported
Courtesy: My Oracle Support

Wednesday, September 19, 2012

Using TOAD for Oracle on Windows 8 64bit

Update: Please note that TOAD 64 Bit is Now available for Windows 8 64 Bit Version. You can install it along with Oracle Client 64 Bit. It will work smoothly.

Today I have installed Oracle 10gR2 32 bit Client and TOAD for Oracle 11.5.0.56 on my Windows 8 laptop and when I try to connect to database it  gave the error :

can't initialize oci.error -1

So, Followed the below workaround to resolve this issue and I am able to connect to databases.

1. Go to the folder where Toad is installed.
2. Right Click on the Toad.exe and select Compatibility Tab
3. Select the check box "Run this program in compatibility mode for"
4. Select Windows XP (Service Pack 3) in the list box below
5. Save the settings by clicking OK

Now open the Toad and I am able to connect to the databases.successfully

Note the following:

Oracle Client Installed Must be 32 bit.
Toad is running in 32 bit environment.
Windows 8 is 64 bit