Hi Alejandro, if your log is full then the appropriate action is execute a logbackup. For the access errors at the logvolumes have a look into the file knldiag. It contains information about the activities of the database-kernel and also error-messages. If you can't solve your problem, please post some more information (exact release, your actions before, errors during these actions ....) to the list
kind regards, Martin -----Original Message----- From: Alejandro Elviretti [mailto:[EMAIL PROTECTED] Sent: Thursday, January 26, 2006 9:26 PM To: maxdb@lists.mysql.com Subject: Problem with Logs Volume Hi group..i am having problems with logs volumes since are corrupted and services do not start. Server hung up during adding an addtional log file 'cause it was at 100 % full. This a example of Windows event Event Type: Error Event Source: SAPDB:Dev Event Category: Fast Event ID: 18159 Date: 1/26/2006 Time: 3:50:37 PM User: NT AUTHORITY\SYSTEM Computer: SAPDEV Description: SAPDB - Dev : - ERROR TID: 0x10DC PID: 0x1088 MsgID: 18159 Could not open volume 'F:\sapdb\DEV\saplog\DISKL003', rc = 2 Same error msg with DISKL002 & 1, in fact, diskl003 is the additional log file. Data db are ok so i need to know if any solution or any way to re create log volumes without reinstalling or restoring from external backup. Hi Version 7.4.3 Ale -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
smime.p7s
Description: S/MIME cryptographic signature
