[v7.5.00.23 on 64-bit Linux]
I have 2 data and 2 (mirrored) log volumes (created at install time) and
then the autolog activated. I had to add 2 more data volumes on the fly to
deal with the temp space saturation problem while I was running a data
import but I cannot add their corresponding log vo
According to the change log for 7.5.0.23 you fixed the problem (quoted
below) where unclosed cursors chew up temp space...well it still happens
with apps even when using the latest jdbc driver.
I also have a bug for "db_adddevice LOG" but I will submit that in another
email.
looking into this file i found out that it is only for IA64.
you surely mean x86_64, don't you?
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Hi,
after upgrading from SapDB 7.3.0.24 to MaxDB 7.5.0.16 we experienced
some troubles with Indexes not beeing used. So we upgraded to MaxDB
7.5.0.23.
But now the Instance_type of the Database has suddenly changed.
Previously we used the BW-Type AFAIK (No Log since it is used for a
DataWareHou
