I attempted to set up the jdbc connection to as400 iSeries DB2 for Dynamic Cube features...
However the creation connection doesn't work out and returning error message :
XQE-DS-0020 "DB2 UDB for AS/400" server version "6.1" is not supported
I have placed in the jt400-6.4.jar in both
1.\webapps\p2pd\WEB-INF\lib
2.\v5dataserver\lib
and restarted my server..
still no luck..
With 10.2.2 the version supported is 7.1 and 7.2.
Check this specs.
To use JT400 driver you must be using IBM Cognos 10.2.1 FP3 or higher. DB2 version must be 7.1 or above and that is why the connection is rejected and states that it is because the version is not supported by the Dynamic Query engine.
http://www-01.ibm.com/support/docview.wss?uid=swg27037784
http://www-01.ibm.com/support/docview.wss?uid=swg27042164
Related
I went to syswow64, selected odbcad32,added IBM DB2 ODBC driver 8.01.10.812 and configured in system DSN for checking the Host Name is getting connected or not and when i give the database name,username and password it is showing the below error
And in the Db2 run time client 8.2 it is showing this error in command line processor
I am connecting to DB2 Entreprise Edition 8.1.10 in the other Server where the database is available
I am facing this issue even after following the below settings.
Replacing ojdbc14.jar with ojdbc6.jar[also tried ojdbc5.jar]
Added "SQLNET.ALLOWED_LOGON_VERSION_SERVER=8" to sqlnet.ora
file[under network/admin folder].
This is happening after upgrading the DB from 11g to 12c.
ORA-28040: No matching authentication protocol
I faced a similar issue when trying to connect a
32-bit Oracle 11g Client to a 64-bit Oracle 12c Server
I then proceeded to add the following to sqlnet.ora
SQLNET.ALLOWED_LOGON_VERSION_CLIENT = 8
SQLNET.ALLOWED_LOGON_VERSION_SERVER = 8
I then experienced the following error
ORA-01017: invalid username/password: logon denied
Adding the following to the Client sqlnet.ora as well as the Server, I was able to connect an old version of Toad and PL/SQL to the new 12c Server.
SQLNET.AUTHENTICATION_SERVICES = (NONE)
JDBC drivers have both a Java version and an Oracle version. The versions are usually correlated, but it's possible for an ojdbc14.jar to support a later version of Oracle than a ojdbc6.jar. Make sure you are using the latest version of ojdbc6.jar.
Run this command to see which version of Oracle the driver was built for:
>java -jar ojdbc6.jar -getversion
Oracle 11.2.0.3.0 JDBC 4.0 compiled with JDK6 on Thu_Jun_28_00:38:25_PDT_2012
#Default Connection Properties Resource
#Mon Dec 21 12:38:41 CST 2015
For SQLNET.ORA changes, to be safe you should restart both the listener and the database. This sounds extreme, but there are some parameters that require restarting the database.
Also make sure that you are modifying all relevant SQLNET.ORA files. If the database's Oracle home is different than the listener's Oracle home you should modify both.
First of all the difference between ojdbc driver's versions depends on the version of the JDK you use drivers with.
So ojbdc14 is suitable for JDK version 1.4, ojdbc5 for JDK 1.5, and so on.
I'm currently using ojdbc7.jar with a 12c database version since my environment uses a JDK 1.7, so upgrade this first.
Having said that, in the Parameters for the sqlnet.ora File for Oracle 12c release page you can read:
Purpose
To set the minimum authentication protocol allowed for clients, and
when a server is acting as a client, such as connecting over a
database link, when connecting to Oracle Database instances.
Usage Notes
The term VERSION in the parameter name refers to the version of the
authentication protocol, not the Oracle Database release.
If the version does not meet or exceed the value defined by this
parameter, then authentication fails with an ORA-28040: No matching
authentication protocol error.
The default for this property is 11.
Allowed values are 8,10,11,12 and 12a.
The recommended value is 12. Try this out.
Moreover there is a useful and interesting solution Database Administrators Stack Exchange
You should use the latest JDBC thin driver (12.1.0.2) and JDK8. With this configuration your driver will support the latest version of the database password verifier and your issue should be resolved.
After upgrading Oracle 12c or higher versions
for java version jdk7 & jdk8 supported ojdcc7.jar
for java version jdk6 ojdbc6.jar
This worked for us...
Download [ojdcc7.jar]: https://mvnrepository.com/artifact/com.oracle/ojdbc7/12.1.0.2
I am using Oracle ODI 11.1.1.7 version on a Windows 7 64bit machine. I want to connect to a SQL Server 2005 database using the driver com.microsoft.sqlserver.jdbc.SQLServerDriver.
I have downloaded and installed from Microsoft the drivers
Microsoft JDBC Driver 4.1 for SQL Server
and also
Microsoft JDBC Driver 4.0 for SQL Server
But I still have a connection error:
ODI-26039: Connection failed
Java.lang.RuntimeException: java.lang.IllegalArgumentException: Could not load JDBC driver class [com.microsoft.sqlserver.jdbc.SQLServerDriver]
Did anyone else experience this issue?
Thank you in advance.
Kindly check this url. You need the specific driver depending upon the version of JDBC. You need to elaborate more on your question.
https://msdn.microsoft.com/en-us/library/ms378422(v=sql.110).aspx
My team are trying to migrate from ORACLE 10g to 11g. These are our system specs:
Our current production server:
ORACLE 10.2g
ORACLE Application Express(3.0)
Apache
Red Hat 64 bit
Our new server (not yet in production):
ORACLE 11.2g
ORACLE Application Express (4.1.1)
ORACLE HTTP Server
Red Hat 64 bit
We have managed to setup 11g, install APEX 4.1 and apply the recent patchset.
The only bit that's delaying us with our migration is that our business users have access to Crystal Reports XI, MS Access/Excel 2003 whcih they use to connect to our database. A typical user has Window XP SP 3 (32bit) operating system. At the moment we are using Microsoft ODBC for Oracle driver (version 2.575.1132.00) to connect to our 10g Database and have not had any issues. However when we try connect to 11g we keep getting ORA-03113: end-of-file on communication channel errors. In ORACLE SQL Developer, we're able to connect to our 11g instance using the "basic" connection. I have also used the "TNS" entries and that works well.
I think the business users obtained the Microsoft ODBC for Oracle driver by installing ORACLE Discover 3.1.3.6 which is used for another Oracle DB. They also have Oracle Client 7.3.3 which I can see Oracle73 (2.00.03.01) mentioned in the ODBM Data Source Admin screen.
We have tried googling for a result and after various tests, we have come to the conclusion that it is an ODBC driver issue. As far as our understand it ORACLE SQL Developer uses a different JAVA based driver to connect so it does not use the Microsoft version.
Can someone confirm that our understanding is correct about there being a compatibility issues with Microsoft ODBC for Oracle driver (version 2.575.1132.00) and 11.2g?
If so, what could you recommend a compatible driver to use with Crystal and Access/excel to extract the data?
I think the business users obtained the Microsoft ODBC for Oracle driver by installing ORACLE Discover 3.1.3.6 which is used for another Oracle DB. They also have Oracle Client 7.3.3 which I can see Oracle73 (2.00.03.01) mentioned in the ODBM Data Source Admin screen.
The Microsoft ODBC Driver for Oracle is written using an ancient version of the OCI (Oracle Call Interface) API that was deprecated when Oracle 8 was released (which was more than a decade and 11 major releases ago). Microsoft chose to desupport this driver rather than port it to the new version of the OCI API. Oracle 7 clients can connect to Oracle 10.2 databases but Oracle does not support connections between Oracle 7 clients and Oracle 11.2 databases.
You'll need to upgrade the version of the Oracle client that is installed on the business user's machines and you'll want to use the latest version of the Oracle ODBC driver that is appropriate for that version of the Oracle client. Assuming that you install the 11.2 version of the Oracle client (the only reason not to upgrade all the way to the 11.2 client would be if the users still needed to connect to older databases that don't support connections from an 11.2 client), you'd want to use the most recent version of the 11.2.0.x Oracle ODBC driver. The Oracle client install should also have the option to install a version of the Oracle ODBC driver-- that should be sufficient as well.
I recently upgraded my oracle client to 10g (10.2.0.1.0).
Now when I try to connect to a legacy 8.0 database, I get
ORA-03134: Connections to this server version are no longer supported.
Is there any workaround for this problem, or do I have to install two clients on my local machine?
Yes, you can connect to an Oracle 8i database with the 10g client, but the 8i Database requires the 8.1.7.3 patchset, which you can get from Oracle's Metalink support site (requires login).
Here's an Oracle forum post with the details.
If updating your Oracle Database isn't an option, then you can have 2 different clients installed (in different "Oracle Homes" (or directories), and use the selecthome.bat file to switch between your installed clients.
For example, before connecting to 8i, you'd run:
C:\Oracle\Client1_8i\bin\selecthome.bat
or this to use your Oracle 10g client:
C:\Oracle\Client2_10g\bin\selecthome.bat
I had to connect a C# code to an Oracle 7 (I know you it's 8...)... the only way I get it was to get the CD to install the Oracle Server and to go in the "Optional Configuration Component" and to use the Oracle73 Ver2.5.
I think you should go check the CD of the Oracle 8 Server and check if an ODBC is still available.
The best way to connect an Oracle 8.1.7 and higher is through Instant Client. Download Instant client 10.2 from oracle site, copy all files in the same folder where .NET assemblies resides and use classes located in System.Data.OracleClient. This work for me in .NET 4 project and oracle DB 8.1.7 server.