Need quick help - someone messed up our maxdb install...

Here's the deal - We had a successfully running instance of MaxDB on Linux. Somebody in our operations group inadvertently started an rpm install of MaxDB on the same machine, and now (of course) things aren't happy. An attempt to restart via: '/etc/init.d/sapdb restart' Shows: Stopping SAPDB

gentoo ebuild for 7.5.0.18

Hi ! If you are still interested there are new ebuilds for maxdb 7.5.0.18 in the bugs.gentoo.org system. I successfully managed to build it on three systems type (1.4, 2004.1 and 2004.3). The ebuilds are not totally automatic as imf fails to run within the portage sandbox. But there are only very

Synchronization Manager docu

hi, where can i find how exactly to setup a Synchronization Manager? all i found in the online docu is a page saying that a Synchronization Manager exists , and a graphic how the different parts interact. see : http://dev.mysql.com/doc/maxdb/en/e4/5cee408a63732ae1000a155106/content.htm but n

Re: AW: alter table ... add ... not null

Ok, I misinterpreted because the use o check, that implies there is no null values automatically. Thanks, Edson Richter Anhaus, Thomas escreveu: Edson Carlos Ericksson Richter wrote : MaxDB doesn't allow I add a column with not null attribute. But, reading docs, if I put a check constraint on

RE: PHP function maxdb_options: Parameter mismatch

Hi, You are right. Use maxdb_options("MAXDB_UNICODE", "TRUE"). This option is then valid for the next maxdb_connect() call. Regards, Thomas Simenec SAP Labs Berlin -Original Message- From: "Hötzel, Jürgen" [mailto:[EMAIL PROTECTED] Sent: Donnerstag, 9. Dezember 2004 11:06 To: [EMAIL P

RE: 7.6.0-004: vdiaginit coredumps

> [1] _malloc_unlocked(0x2008), at 0xd2380cf5 > [2] malloc(0x2008), at 0xd2380c87 > [3] _findbuf(0x93b07c0), at 0xd239dcb0 This looks to me as if someone clobbered the heap. If Solaris has a debugging malloc, I'd tried to link with that one. Or write a routine that allocates 10 pointers an

7.6.0-004: vdiaginit coredumps

I have sucessfully built the tree as of yesterday and managed to use the built binaries to create a database instance :-) However, the database will not come up when executing "db_admin -f", it will coredump without any further erros in vdiaginit: dbx) where

PHP function maxdb_options: Parameter mismatch

Hi, Using this function as described in http://dev.mysql.com/doc/maxdb/pdf/php_presentation.pdf: maxdb_options($link, MAXDB_UNICODE, TRUE); fails: Warning: maxdb_options() expects exactly 2 parameters, 3 given in .. By looking in the source (php_maxdb.c) i found out, that this function on

RE: MAXdb python module unicode support

>when the moment came to go in production, I have decided to >upgrade the >server to MAXdb 7.5 (upgrade goes well for the database) , >unfortunately it seems that the python interface is working very >bad with Unicode returning in some versions versions of maxdb binary >data and under the

MAXdb python module unicode support

I have a project entirely developed under python(2.3.4) and sapdb 7.4.3 with Unicode database instance all is functioning well under this configuration. when the moment came to go in production, I have decided to upgrade the server to MAXdb 7.5 (upgrade goes well for the database) , unfortunat