Geting Error Could not instantiate: ro.sync.db.nxd.berkeley

Having trouble installing Oxygen? Got a bug to report? Post it all here.
thungp
Posts: 3
Joined: Wed Sep 19, 2007 9:35 pm
Location: San Diego

Geting Error Could not instantiate: ro.sync.db.nxd.berkeley

Post by thungp »

To who it may concern,


Background I just upgraded from Oxygen 10.3 to 11.0 build 2009100911
although I left 10.3 on the machine so they both coexist.
I am sucesseful in making a connectino with 10.3 but seem to
get this error with 11.0
ERROR: "Could not instantiate: ro.sync.db.nxd.berkeley.BerkeleySession due to : java.lang.NoClassDefFoundError: com/sleepycat/dbxml/XmlDebuListener"

Any Suggestions?

Also there was this ability to be able to have oxygen help
generate xquery based off of a node that I can't figure out
how I did it. I'm not sure if it it was in versin 10.3 or 11.0
Can someone help me remember?

-Peter
sorin_ristache
Posts: 4141
Joined: Fri Mar 28, 2003 2:12 pm

Re: Geting Error Could not instantiate: ro.sync.db.nxd.berkeley

Post by sorin_ristache »

Hello,

Oxygen 11.0 supports only the latest version of Berkeley DB XML, that is version 2.5.13. If you want to use also a previous version of Berkeley DB XML you have to access it from Oxygen 10.3.

From your description I don't understand what feature you used for generating XQuery in Oxygen. Can you give an example? All the features of version 10.3 are also in version 11.0 and version 11.0 adds only one XQuery feature: the XQuery debugger for Berkeley DB XML. That means you used a feature that was also in version 10.3.


Regards,
Sorin
thungp
Posts: 3
Joined: Wed Sep 19, 2007 9:35 pm
Location: San Diego

Re: Geting Error Could not instantiate: ro.sync.db.nxd.berkeley

Post by thungp »

Sorin,

Thanks.

I didn't notice that 11.0 did not work with version 2.4.16 or Oracle.
I haven't tried it, yet, but that makes sense.
milko
Posts: 2
Joined: Thu Apr 22, 2010 1:21 am

Re: Geting Error Could not instantiate: ro.sync.db.nxd.berkeley

Post by milko »

I also have a similar problem, I get the following error after configuring a dbxml data source and connection:

Check datasource configuration. Could not instantiate ro.sync.db.nxd.berkeley.BerkeleySession due to java.lang.NoClassDefFoudError: Could not initialise class com.sleepycat.db.internal.db_javajNI

I am using XML Editor 11.2, build 2010031611 and I just compiled Berkeley DBXML version 2.5.16

I am not a java expert, so I might have not set environment variables, but I followed exactly the instructions in the documentation. Note that the environment home directory is empty (I want to create a container using Oxygen).

Any suggestion?

Thanks!
adrian
Posts: 2879
Joined: Tue May 17, 2005 4:01 pm

Re: Geting Error Could not instantiate: ro.sync.db.nxd.berkeley

Post by adrian »

Hello,

If you are on Mac or Linux you have to manually set an environment variable to point to the native libraries(libdb*.so or libdb*.dylib) of DB XML.

On Linux it is called LD_LIBRARY_PATH.
e.g.: LD_LIBRARY_PATH=/path/to/dbxml-2.5.16/install/lib

How to set an environment variable in Linux:
https://help.ubuntu.com/community/EnvironmentVariables
The recommended way is to set it in '/etc/environment'

On Mac OS X it is named DYLD_LIBRARY_PATH.
e.g.: DYLD_LIBRARY_PATH=/path/to/dbxml-2.5.16/install/lib

How to set an environment variable in Mac OS X:
http://stackoverflow.com/questions/1356 ... es-in-os-x

Restart the system if you set it in the global environment and start Oxygen again.
To check if the environment variable is available in Oxygen create an External Tool(Tools -> External Tools -> Preferences, New) give it a name and in the 'Command line' field type 'printenv'(without the quotes).
When you execute this external tool you will obtain a list with the environment variables and check if yours was properly set.

Regards,
Adrian
Adrian Buza
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com
milko
Posts: 2
Joined: Thu Apr 22, 2010 1:21 am

Re: Geting Error Could not instantiate: ro.sync.db.nxd.berkeley

Post by milko »

Thanks for the explanations, after googling around to understand where to set environment variables I opted for ~/.MacOSX/environment.plist and it works now (complains that there are no containers in the directory, which is correct).

Bye!
Post Reply