I was evaluating Servoy 4 (Mac PPC 10.5.4)
Everything was working as advertised (tough Eclipse seems a bit unstable)
But suddenly seems Sybase would not start anymore, and there is no more access to the repository db etc…
Sybase log say :
I. 07/31 12:04:13. Running on Darwin 9.4.0 Darwin Kernel Version 9.4.0: Mon Jun
9 19:36:17 PDT 2008; root:xnu-1228.5.20~1/RELEASE_PPC Power Mac
E. 07/31 12:04:15. Database cannot be started – “/Applications/Servoy4/applicat
ion_server/database/bug_db.db” unable to open transaction log
As far as I can understand it starts (by hand last time) but complains about not finding the transaction log of the first db to open
I created a transaction file manually (touch bug_db.log) but still had the same error.
console sends following message :
pbg4:application_server PBG4$ sybase_db/dbsrv9 @sybase_db/sybase.config
dyld: Library not loaded: libdbserv9_r.dylib
Referenced from: /Applications/Servoy4/application_server/sybase_db/dbsrv9
Reason: image not found
Trace/BPT trap
I dont want to delve into the intricacies of Sybase for now, can someone tell me what the problem is ?
BTW Uninstalling and fresh install would not solve the problem.
The problem is that cannot find bug_db.log . At database creation it probably specified a log location ( relative or absolute) which is now incorrect. Maybe the log has been moved from its original location ? The simplest thing would be to delete the db and create it again with dbinit or from Servoy. Otherwise you can use, for example, dblog tool to see/modify the log of your database. Dblog is found in Sybase Central.
This is the classic nightmare of every developper
Being kept on hold with an unsupported product (Sybase) that shipped with a normally well supported one.
Sorry but nothing helps in this case, I just dumped everything and made a clean install (keeping the previous workspace) still strucked , there must be somewhere a hidden (unknown) config file that keeps some details from the previous installs.
And redirects everything in the wrong direction
Can you document this a bit more precisely.
BTW I did not find the Mac version of Sybase Central
janber:
This is the classic nightmare of every developper
Being kept on hold with an unsupported product (Sybase) that shipped with a normally well supported one.
Sybase is fully supported. Here in the forum you’ll find free support from the community and we also offer the possibility to file issues in our online support system.
In your case it looks like somehow the database engine was killed and left a hanging transaction, when that happens sybase (correctly) does not launch that database anymore until you decide what to do with the transaction. You can either process the logfiles or if you simply want to rollback it fire up the database once with the -f command, then relaunch it in normal mode.
OK lets close this thread
Problem is solved, but it took some time.
As far as I can conclude, the problem arised when after playing a bit with Servoy 4 intalled in a Folder named ‘Servoy4’ I foolishly decided to rename the folder ‘Servoy40’.
And indeed this probably disturbed SyBase, at least the transaction file.
Sybase would not start anymore, so Sybase Central could not repair anything.
The solution came as of starting another Sybase database with Sybase Central (launch) opening one of the databases of Servoy, not the one which was hanging the database start, then go to ‘Changing name Transaction file’. Which gave me a clue of a weird name for the existing transaction file, that was the origin of all the problems.
It was apparently not in the path of Sybase.
Saving it with a new name in the Servoy directory did the trick.