Has anyone got compiere working with Sybase?
I am still getting the following error when I start Compiere2.
14:17:36.219 IniDialog.accept: License Accepted
14:17:39.952 Ini.loadProperties: /opt/sybase/Compiere.properties #21
Exception in thread "main" java.lang.NoClassDefFoundError: oracle/jdbc/pool/OracleConnectionCacheCallback
at java.lang.ClassLoader.defineClass0(Native Method)
at java.security.AccessController.doPrivileged(Native Method)
at java.lang.Class.forName0(Native Method)
Do You suscessfully load dump of Sybase ?
I can not load dump in anyway. All doing as described on site , but get error when try load database in sybase.
What exact error do you get when trying to load ?
Also, the ASE and backup server errorlogs, by convention in $SYBASE/$SYBASE_ASE/install are quite useful.
HI I was able to successfully load the sybase dump into Sybase Devlopment Database 12. ASE does not work yet?
From what I can see all of the information is loaded into the database ok. I can the database came online ok.
The setup ran great - sucessfully.
When I run the Compiere2.sh I getthis error. I saw a post about running setup before importing the database. So I deleted the tables and all, ran the setup, and then loaded the database again. Howerver I got the same errors.
Dev Ed and Express Ed are two editions of the same product, Adaptive Server Enterprise (ASE). Difference is in licensing details, i.e. XE is free for dev/prod and has limitation on hardware resources while DevEd is free for dev/test - not prod! - and have other limitations.
On the errors, please post the more details. If you mail me directly we can post findings to the forums.
when i try load dump into compiere I get this:
1> LOAD DATABASE compiere FROM "compress::c:\compieresybase\compieresybase.dump
Backup Server session id is: 41. Use this value when executing the
'sp_volchanged' system stored procedure after fulfilling any volume change
request from the Backup Server.
Backup Server: 220.127.116.11: Attempting to open byte stream device:
Backup Server: 18.104.22.168: The database page size of 16384 bytes obtained from
ASE is different from the database page size of 8192 bytes read from the dump
header. The LOAD session must exit.
Backup Server: 22.214.171.124: Unrecoverable I/O or volume error. This DUMP or LOAD
session must exit.
Backup Server: 126.96.36.199: compress::c:\compieresybase\compieresybase.dump::00:
volume not valid or not requested (server: , session id: 41.)
Backup Server: 188.8.131.52: Unrecoverable I/O or volume error. This DUMP or LOAD
session must exit.
Msg 8009, Level 16, State 1:
Server 'PC', Line 1:
Error encountered by Backup Server. Please refer to Backup Server messages for
But compiere help recommended 8K OR 16K. Why this messages?
Perhaps the intent was to provide both 8kb and 16kb dumps?
In any case, 8kb is a better choice, and it unfortunately means you have to build/rebuild ASE with an 8kb page size.
Personally I use resource files quite a bit. If you check $SYBASE/$SYBASE_ASE/init/logs you will find the log and resource files from previous builds. You can either use them to go faster through the installation process or run the with srvbuildres to build ASE in batch mode. You will need to remove certain parts from your existing installation though, like interfaces entry, etc. - but srvbuildres will tell you.
I'm on Debian Sarge, and I even can install Sybase.. during the installation, after choose the 8k page size..
Building Adaptive Server 'OSHO':
Writing entry into directory services...
Directory services entry complete.
Building master device...
/opt/sybase/ASE-12_5/bin/dataserver: error while loading shared libraries: libstdc++-libc6.2-2.so.3: cannot open shared object file: No such file or directory
Server 'OSHO' was not created.
You need the compat-libstdc++ package.
Check e.g http://www.peppler.org/FAQ/linux.html#q1.18
As an aside, two excellent sources for running ASE on Linux are:
Compiere running on Sybase got a bug (1177931), I was told that the next realese should be functional...., anyway both the client & server got a bug the don't load the correct database conection... Check the bug I posted the error logs I got, as for the database dump, check the page file and the character set, I used utf-8 and the db dump loaded flawlessly...
Log in to post a comment.