Data volumes are set to bad if the read or write access failed. If hardware is a kind of raid system such errors can occur temporary. If you are sure to have such situation you can unset the bad flag with util_execute enable devspace 'D:\...DATA_16' (complete path). If you want to be sure, check the operating system message files and the knldiag for further informations relating to your io and disc system. If you have a hardware problem, then you have to recover with the last data backup. kind regards Uwe
> -----Original Message----- > From: Case, Glen [mailto:[EMAIL PROTECTED] > Sent: Mittwoch, 28. Mai 2003 15:45 > To: '[EMAIL PROTECTED]' > Subject: RE: SAP DB database won't start. > > > I looked in the archives and found the answer. > > Glen Case > Oracle DBA/SAP Basis > Moen Incorporated > (440) 962-2462 > > > -----Original Message----- > > From: Case, Glen > > Sent: Wednesday, May 28, 2003 9:33 AM > > To: '[EMAIL PROTECTED]' > > Subject: SAP DB database won't start. > > > > Looking at the error log, it shows that file > 'D:\...DATA_16' marked bad at > > position 109400. Is there a way to run a command that will > correct the > > bad spot in this file or do I have to restore the database and roll > > forward ? > > > > Thanks for your input. > > > > Glen Case > > > > ______________________________________________________________ > __________ > This email has been scanned for all known viruses. > ______________________________________________________________ > _________ > _______________________________________________ > sapdb.general mailing list > [EMAIL PROTECTED] > http://listserv.sap.com/mailman/listinfo/sapdb.general > _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
