Derby error on Windows 7
I have installed both 64 bit and 32 bit JDK's. Can't able to start the derby DB.
Derby 10.15 is for use with Java 9 and higher.
You are using Java 8.
You have two choices:
Upgrade your Java to Java 9
Get Derby 10.14, which supports Java 8
Note that on the Derby downloads page, the available releases are grouped by Java version.
Related
I have a 32 bit Oracle DB (version 9i - 9.2.0.7.0), a 64 bit Mac and am trying to connect to it using go-oci8 with Go Lang (version go1.11.1 darwin/amd64).
I used SQL-Developer 4.0.2 to successfully connect to the DB and then enabled InstantClient connection through it using this tutorial. So I've got things running from the Oracle Client's side.
I'm using InstantClient Version 11.2.0.4.0 (32-bit) for MacOS (basic and SDK), I've used mainly this tutorial almost successfully. After everything, the error I'm getting is:
github.com/mattn/go-oci8 ld: warning: ignoring file /Users/myusername/Downloads/instantclient_11_2/libclntsh.dylib, file was built for i386 which is not the architecture being linked (x86_64): /Users/myusername/Downloads/instantclient_11_2/libclntsh.dylib Undefined symbols for architecture x86_64:
And then a long stack of symbols. Basically the Go oci8 library is trying to use C (which is 64 bit) and tries to build 64 bit files, which will then be used by Go. If I try with the 64 bit version of InstantClient, I have no problems, but I get a "driver: bad connection" error which is because 64bit won't work to connect some reason.
I have no idea what to do to resole this issue - can I somehow force the build of 32 bit files while using go get -u -v github.com/mattn/go-oci8? Or somehow make the 64 bit InstantClient version connect to the old 32 bit Oracle DB?
Any kind of help on how to get this running would be much appreciated.
Edit: I've tried 10.2 Oracle Client, but I can't connect it with go-oci8 (I'm assuming it doesn't support it). The error I get is ../github.com/mattn/go-oci8/oci8.go:113:25: could not determine kind of name for C.OCI_SYSASM
Final edit for people who have the same problem (coming on to a very old Oracle Database) - you can't interface with the readily provided solutions using Go. The libraries listed to work with Oracle operate with Client versions 11.2 and up.
The architecture of the Oracle Client have to match so architecture of your application. I.e. if your Go Lang is 64-bit then the Oracle Client have to be also 64-bit. It does not matter whether the database is 32 or 64-bit.
I think the main problem is, you cannot connect with an Oracle 11.2 Client to a (20 years old!) Oracle 9i database.
Check Client / Server Interoperability Support Matrix for Different Oracle Versions (Doc ID 207303.1) for details.
It says:
For connections between 10.2 (or higher) and 9.2 the 9.2 end MUST be
at 9.2.0.4 or higher. Connections between 10.2 (or higher) and
9.2.0.1, 9.2.0.2 or 9.2.0.3 have never been supported.
You did not tell us which version of "Oracle 9i" your ar using.
When I was installing WAS, there was a prompt alerting me to use Java 8 by default. I aggreed, because back then it wasn't matter which version to use.
Time passed and now I have necessity to use Java 6 in one of my profiles, which is coming with the WAS by default. Since I aggreed to use newer Java, WAS working on Java 8 by default now. I searched in installation repository, but in IBM Installation Manager Java versions I need are greyed out and cannot be installed separately.
Is there a way to install Java 6 alongside Java 8 in WAS, so I could just switch between them in profiles' setting? I tried official repository for Java 6, but it is empty since IBM dropped it's support in April.
P.S. I tried to change variable JAVA_HOME in Websphere profile setting (as well as in system variables) to look at JDK 1.6 I installed separately, but then my profile refuses to start.
Java 6 is no longer supported, so the WAS Installation Manager has likely removed the option to use JDK 6. For WAS 8.5 you can use either Java 7 or Java 8.
This article talks more about Java 6 End of Support:
https://developer.ibm.com/wasdev/blog/2017/10/25/java-6-end-support/
Facing issue as mentioned in the error screen while starting Weblogic server. I am unable to start the server.
Windows 7 32 bit, 8gb ram
JDK 1.8.0
JRE 1.8.0
Error screen
Did you configure the memory properties of the WebLogic? Seems they are not the default.
Are you running out of space on your machine's hard-drive for temporary files?
I have Java 8 update 101 and I'm using the jTDS 1.2.5
I received the following error:
org.eclipse.birt.report.data.oda.jdbc.JDBCException: There is an error in get connection, I/O Error: SSO Failed: Native SSPI library not loaded. Check the java.library.path system property.
So I've a question: How can I know the compatibility of Java and jTDS?
I've checked on their site: http://jtds.sourceforge.net/
But I cannot find the java compatibility in the release note. The 1.2.5 jTDS works with java 7 but not 8 and it's written JDBC 3 in the release note
I may do not understand the error too.
I was using a 32 bit for Java and my application was install on 64 bit. That cannot work !
Thanks for your help #a_horse_with_no_name
Which jdbc driver should be used for connecting with oracle 8i? I am using jdk 1.6 and tomcat.
The choices would be (in the decreasing order of preference):
The JDBC driver that is provided with the database itself. This is typically found in the jdbc/lib directory of your Oracle database home.
The most recent driver for the 8i platform. You can get this from Oracle Technology Network. Use this if are encountering any issues (that are typically not patched in the driver supplied by the database).
The JDBC driver that ships with the application server. This is listed as the last preference, for the 8i platform is quite old, and the drivers supplied would have better characteristics for newer releases like the 10g and 11g platforms.
If you are on Java 1.4 or newer, i.e. Java 1.4/5/6, then use the driver within ojdbc_14.jar instead of classes12.zip. The driver within classes12.zip is meant to be used on versions of Java after 1.2 and before 1.4.
If you do have ojdbc5.jar or ojdbc6.jar (unlikely to be the case for the 8i drivers), then they'll need to used in preference over ojdbc14.jar, in the Java 5 and Java 6 platforms respectively. Use these drivers (meant for the Java 5 and Java 6 platforms) with caution though, as the some of these driver versions will simply not be supported when used against an 8i database. For example, the Oracle® Database JDBC Developer's Guide and Reference for 11g R1 states the following:
Backward Compatibility
The JDBC drivers are certified to work
with the currently supported versions
of Oracle Database. For example, the
JDBC Thin drivers in Oracle Database
11g Release 1 (11.1) are certified to
work with the 10.2.x, 10.1.x, 9.2.x,
and 9.0.1.x Oracle Database releases.
However, they are not certified to
work with older, unsupported database
releases, such as 8.0.x and 7.x.
The JDBC developer's guide for 10g R1/R2 might state the same, but you'll need to verify this if you intend to proceed with a driver version that works against a newer database release. In practice, ensure that you know the version of the driver in use, and that it is supported for use against 8i.