Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » Jubula » Jubula 8.3 - Database connection failed because of invalid or missing database detail
Jubula 8.3 - Database connection failed because of invalid or missing database detail [message #1743334] Wed, 14 September 2016 13:13 Go to next message
David Vlek is currently offline David VlekFriend
Messages: 20
Registered: September 2014
Junior Member
Hello People
After migrating to the new Jubula 8.3 installation. I get the error below. Please what am I missing. My database is an Oracle 11g db. What does it mean major version invalid. 

2016-09-14 15:13:16.331 [Worker-0] ERROR o.e.j.c.core.persistence.Persistor - DBVersion: major version invalid
2016-09-14 15:13:16.339 [Worker-0] ERROR o.e.j.c.core.persistence.Persistor - ITE version problem - database schema version: "60.0" <--> ITE expected version: "50.0"   
2016-09-14 15:13:16.343 [main] ERROR o.e.j.a.testexec.core.TestexecClient - Database connection failed because of invalid or missing database detail
java.lang.IllegalArgumentException: Database connection failed because of invalid or missing database detail
	at org.eclipse.jubula.app.testexec.core.ExecutionController.prepareDBConnection(ExecutionController.java:538) ~[na:na]
	at org.eclipse.jubula.app.testexec.core.ExecutionController.executeJob(ExecutionController.java:322) ~[na:na]
	at org.eclipse.jubula.app.testexec.core.TestexecClient.doRun(TestexecClient.java:78) ~[na:na]
	at org.eclipse.jubula.client.cmd.AbstractCmdlineClient.run(AbstractCmdlineClient.java:444) [org.eclipse.jubula.client.cmd_4.0.0.201603111021.jar:na]
	at org.eclipse.jubula.client.cmd.AbstractLauncher.start(AbstractLauncher.java:27) [org.eclipse.jubula.client.cmd_4.0.0.201603111021.jar:na]
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) [org.eclipse.equinox.app_1.3.200.v20130910-1609.jar:na]
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) [org.eclipse.osgi_3.10.2.v20150203-1939.jar:na]
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) [org.eclipse.osgi_3.10.2.v20150203-1939.jar:na]
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380) [org.eclipse.osgi_3.10.2.v20150203-1939.jar:na]
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) [org.eclipse.osgi_3.10.2.v20150203-1939.jar:na]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_66]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_66]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_66]
	at java.lang.reflect.Method.invoke(Method.java:497) ~[na:1.8.0_66]
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) [org.eclipse.equinox.launcher_1.3.0.v20140415-2008.jar:na]
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) [org.eclipse.equinox.launcher_1.3.0.v20140415-2008.jar:na]
	at org.eclipse.equinox.launcher.Main.run(Main.java:1465) [org.eclipse.equinox.launcher_1.3.0.v20140415-2008.jar:na]
	at org.eclipse.equinox.launcher.Main.main(Main.java:1438) [org.eclipse.equinox.launcher_1.3.0.v20140415-2008.jar:na]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_66]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_66]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_66]
	at java.lang.reflect.Method.invoke(Method.java:497) ~[na:1.8.0_66]
	at com.exe4j.runtime.LauncherEngine.launch(LauncherEngine.java:62) [i4jruntime.jar:na]
	at com.exe4j.runtime.WinLauncher.main(WinLauncher.java:101) [i4jruntime.jar:na]
	at com.install4j.runtime.launcher.WinLauncher.main(WinLauncher.java:16) [i4jruntime.jar:na]
2016-09-14 15:13:16.344 [main] ERROR o.e.j.c.cmd.AbstractCmdlineClient - An error ocurred: Database connection failed because of invalid or missing database detail




<configuration>
    <project>XXXXX</project>
    <version>XXXXXXX</version>
    <autconfig>XXXXXX</autconfig>
    <dburl>jdbc:oracle:thin:@XXXXX:XXXX:XXXXXX</dburl>
    <dbuser>JTA_NEW</dbuser>
    <dbpw>jta_new_sssss</dbpw>
	 <testjob>XXXXXX</testjob>
	 <server>qa-test-automation-pc1</server>
	 <port>60000</port>
	</configuration>



I created a new schema. Imported old projects to the new installation. Trying to test if everything works well I get the error. I have tried via testexec and directly from the ITE itself i get the same error. I attached the full client log to the post and also screen shot showing successful connection to the db.

I created a new schema. Imported old projects to the new installation. Trying to test if everything works well I get the error. I have tried via testexec and directly from the ITE itself i get the same error. I attached the full client log to the post and also screen shot showing successful connection to the db.

Thanks in advance.

Kind regards,

Dave

[Updated on: Wed, 14 September 2016 13:17]

Report message to a moderator

Re: Jubula 8.3 - Database connection failed because of invalid or missing database detail [message #1743345 is a reply to message #1743334] Wed, 14 September 2016 13:53 Go to previous messageGo to next message
Alexandra Schladebeck is currently offline Alexandra SchladebeckFriend
Messages: 1613
Registered: July 2009
Senior Member
Hi,

When does the error above come? Does it come when you try to open a project via Test->Open? Do you see an error in the ITE, or just in the log files?

Thanks,
Alex

Report message to a moderator

Re: Jubula 8.3 - Database connection failed because of invalid or missing database detail [message #1743354 is a reply to message #1743345] Wed, 14 September 2016 14:15 Go to previous messageGo to next message
Alexandra Schladebeck is currently offline Alexandra SchladebeckFriend
Messages: 1613
Registered: July 2009
Senior Member
After speaking to a developer, it looks like the version of the ITE or testexec that you are using to connect to the new database is the *old* version (database version 50.0). So the database is correctly created, but the client you are using to connect is outdated. Can you check whether you're starting testexec / the ITE from the right installation? Bear in mind, if you have multiple machines, that the installation needs to be updated on all of them. The version of the ITE can be checked via Help / About.

Best regards,
Alex

Report message to a moderator

icon14.gif  Re: Jubula 8.3 - Database connection failed because of invalid or missing database detail [message #1743365 is a reply to message #1743354] Wed, 14 September 2016 14:36 Go to previous messageGo to next message
David Vlek is currently offline David VlekFriend
Messages: 20
Registered: September 2014
Junior Member
Worked like a charm. I had to update my environment variable it was pointing to the old version.

Thank you Alex.

Dave.

Report message to a moderator

Re: Jubula 8.3 - Database connection failed because of invalid or missing database detail [message #1743403 is a reply to message #1743365] Thu, 15 September 2016 06:12 Go to previous message
Alexandra Schladebeck is currently offline Alexandra SchladebeckFriend
Messages: 1613
Registered: July 2009
Senior Member
Excellent news, great that it's working now! Smile

Report message to a moderator

Previous Topic:please delete
Next Topic:how to handle Project Language in Jubula 8.2.2
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Thu Apr 25 05:07:42 GMT 2024

Powered by FUDForum. Page generated in 0.02908 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top

Sign up to our Newsletter

A fresh new issue delivered monthly