Well, I also had the idea to compile MaxDB from CVS but came back
disillusioned: CVS Head does not seem to contain the latest sources or patches.
The MaxDB developers use Perforce internally an sync with the public CVS as
they choose. The last checkins are from Dec 2005 so the solution for our
problem will not be in CVS. Apart from that no tagging information is available
in CVS making it impossible to grab the sources of a particular MaxDB version.
To the MaxDB developers: Would it be possible to provide the patch(es) for this
particular problem ("Error 1139199: Kernel") out of your internal repository so
that I can apply it to the sources of 7.6.00.16 and try to build myself.
THIS IS SUPER URGENT!
Regards
Matthias Ohlemeyer
Abteilung E-Business
EASY* systems GmbH
Elpke 109
33605 Bielefeld
Fon: +49 521 2092-767
Fax: +49 521 2092-993767
___________________________________________
by EK/servicegroup
-----Ursprüngliche Nachricht-----
Von: news [mailto:[EMAIL PROTECTED] Im Auftrag von Sven Köhler
Gesendet: Donnerstag, 11. Mai 2006 23:26
An: maxdb@lists.mysql.com
Betreff: Re: Encountered error 1139199; Availability of version 7.6.00.24?
> SQL Exception while executing the following:UPDATE ... [-9404]: System
> error: AK System error: VAK507 5
Hooray! Welcome to the club!
> I assume this is caused by "Error 1139199: Kernel"
> (http://www.sapdb.org/webpts?wptsdetail=yes&ErrorType=0&ErrorID=113919
> 9)
> . The Web PTS entry says that the problem is fixed in version 7.6.00.24.
> This version is not releasd on the MaxDB site. Is there any chance of
> obtaining this version? Or maybe another idea how to solve our problem?
> The suggested workarounds in PTS do not help us because we do not have
> fine grained control of the SQL statements which are generated by a
> persistence framework.
You can build it yourself. Check it out from CVS, and then somehow get through
the build process (which is quite complicated IMHO). There are some HOWTOs out
there. I don't have any link at hand, sorry.
I'm waiting for a new release too.
Actually, the bug you mentioned _should_ make the database useless for many
people out there.
Greetings,
Sven
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
