Database crashed if I try recreate the dbproc

2007-04-27 Thread Дмитрий Русанов
I'm changing string ' AND ' || p_version || ' < VALUE(toRevision, ' || p_version + 1 || ' )' to ' AND ' || p_version || ' < VALUE(toRevision, ' || p_version || ' + 1)' procedure created ok. -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe:http

Database crashed if I try recreate the dbproc

2007-04-27 Thread Дмитрий Русанов
I'm using MAXDB version 7.6.00.16 build 016-121-109-428 Database crashed if I try recreate the dbproc DROP DBPROC PACS.getProtocolFieldData // CREATE DBPROC PACS.getProtocolFieldData ( IN TableName VARCHAR(32) , IN ProtocolIdINT , IN objId INT , IN xpath VARCHAR(

Re: Performance problems with NFS connected DB server ( to NetApp filer)

2007-04-27 Thread Jonah H. Harris
On 4/27/07, Jonah H. Harris <[EMAIL PROTECTED]> wrote: On my NetApp: nfs.tcp.enable = on nfs.tcp.xfersize = 32768 I was also given alternate settings: nfs.tcp.enable = on nfs.tcp.recvwindowsize = 65536 nfs.tcp.xfersize = 65536 Sorry for the multiple messages, but I had to go through some old

Re: Performance problems with NFS connected DB server ( to NetApp filer)

2007-04-27 Thread Jonah H. Harris
On 4/27/07, Zuylen, G. van <[EMAIL PROTECTED]> wrote: Find below the original message which I send to the mail group. I hadn't done any significant benchmarking with these settings as I switched to iSCSI instead of NFS. However, these were the settings we had and what NetApp had suggested to u

RE: Performance problems with NFS connected DB server ( to NetApp filer)

2007-04-27 Thread Döhr , Markus ICC-H
> My *impression* (which I cannot back with any concrete figures as I > did not do specific performance tests with different setups): network > attached storages are not ideal for databases, especially with OLTP. > My reasoning goes like this: in order to retrieve a block from the > remove filesyst

Re: Performance problems with NFS connected DB server ( to NetApp filer)

2007-04-27 Thread Robert Klemme
Greetings, Am 27.04.07 schrieb Zuylen, G. van <[EMAIL PROTECTED]>: I have connected the DB server (MaxDB) to a NetApp filer (FAS3020) with an NFS mount. The database files are located on the NFS volume on the NetApp. But with heavy I/O load the NFS connection performance became very bad. On th

AW: MaxDB Crashes on complex statements

2007-04-27 Thread Jan-Hendrik Lendholt
Hi Alexander, Here is a the SELECT -Statement on which den view should be based: SELECT BUCHUNG.BUCHID, BUCHUNG.ANZAHL, BUCHUNG.NID, BUCHUNG.CATERINGID, BUCHUNG.ERGAENZUNGSTEXT, BUCHUNG.KOMMENTAR, BUCHUNG.CATERINGBEMERKUNG, BUCHUNG.CATERINGKOMMENTAR, BUCHUNG.CATERINGSTATUS, SERVICE.NAME AS CATE

Re: Performance problems with NFS connected DB server ( to NetApp filer)

2007-04-27 Thread Jonah H. Harris
Also, what which mount options did you use for NFS? On 4/26/07, Robert Klemme <[EMAIL PROTECTED]> wrote: I don't see the original question but AFAIK NetApp filers have a setting called "jumbo frame" or similar. Chances are that they can cope with such large window sizes. Regards robert Am 25

RE: MaxDB Crashes on complex statements

2007-04-27 Thread Schroeder, Alexander
Hello Jan, unfortunately, the attached sql script did not survive the mailing list processing, so would you mind putting it directly into the text? Also of course we would need an info on the used version of MaxDB, and the definitions of the tables that participate in the view statement that c

MaxDB Crashes on complex statements

2007-04-27 Thread Jan-Hendrik Lendholt
Hi Folks, Long time ago I wrote to this list. We have a database with about 180 tables. Now we want to join some small tables to a view. The View-Statement is prettty complex (see attached file script.sql). If I execute this script SQL-Studio tells me: General error; 800 implicit SERVERDB rest

MaxDB- Driver Bug? *** glibc detected *** ..., can you help?

2007-04-27 Thread Alexander Finke
Hi, i i` ve the folling problem: *** glibc detected *** /usr/sbin/httpd2-prefork: malloc(): memory corruption: 0x5594a620 *** I use apache2, php5 - 5.1.2, SLES 10, UnixODBC, MaxDB 7.6 (newest) (x86_64). This error occurs in my php- script in the odbc_exec() function. But only on the