thanks for response, but i have found the problem : the partition space for the raw devices where a little less than the pages specified by param_addvolume. That was the reason of the kernel died.
greets >Could you post the content of the knldiag.err file? Perhaps then it is possible to deduce >what incompatibility or problem exists here. > >Regards >Alexander Schröder >SAP DB, SAP Labs Berlin >-----Original Message----- >From: Fabrice Bourdel [mailto:[EMAIL PROTECTED] >Sent: Mittwoch, 31. Mai 2006 04:11 >To: maxdb >Subject: RE: RE: kernel died > >>Normally this is a problem with the libraries or the PAM (password) >>file. If there is no kernel diag file, then it is a library thing. Is it >>Linux? >> >>Gruss >>Bernd > > >oups... have found that the cache size that i set was too big. >thanks for the response anyway. > >The machine has 4Go RAM, and MaxDB64 was impossible to install >onto sarge because of too old libraries. There is then MaxDB >32 bits, 7.5.00.26 installed, with and 2.6.8-2-686-smp kernel. > >Question 1 >I set 3Go minus 128Mo for cache size, but dont worked. I set then >2Go and that was ok. >Can i set more ? i thaught that i could up to 3 (3Go for prog / 1Go system) >? > >Question 2 >And another problem, a set raw partitions. It work on the old production >machine, but on the new, i have a problem : >(it was possible to create the database with 2Go cache and normal files > for data and log, but with raw...) > >--- >># >># ************************* >># * taille de 10Go Data >># ************************* >>param_addvolume 1 DATA /dev/raw/raw1 R 1310720 >OK > >--- >># >># ************************* >># * taille de 1Go log >># ************************* >>param_addvolume 1 LOG /dev/raw/raw2 R 131072 >OK > >--- >># >>db_admin >OK > >--- >>db_activate DBA,DBA >ERR >-24895,ERR_SHUTDOWN: shutdown of database occured > >What could i do to solve this ? -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
