>-----Original Message----- >From: SILVA Noah [mailto:[EMAIL PROTECTED]] >Sent: Montag, 18. November 2002 23:11 >To: [EMAIL PROTECTED] >Subject: Re: Repm hang > > >Hi, > >Please don't waste your time on my repm help request. >I found an error message from SQL Studio, where it returned >"log full". >using dmbgui, I found that my 8mb log was indeed full. > >I made another log devspace, to is should be 8192 + 16384 k now, but I >wonder: Why does the log grow so fast?, must it be >maintained? Can I >purge it? > >It was a single dev-space of 8192, and over 95% full, but I >expanded it to >include the second dev-space. > >Now when I look at the db statistics, the log says: >LOG: Used: 16kb, Free: 24,536 KB. > >Obviously this is wrong, since way more then 16kb were used. >Attempting to connect to it from SQL Studio yields: >ODBC Error: [SAP AG][SQLOD32.DLL][SAP DB]Unable to connect to >data source; >-901 POS(1) Log full. Return-code: SQL_ERROR (-901). > >I can only assume that this means that the log-space wasn't actually >mounted.
see http://listserv.sap.com/pipermail/sapdb.general/2002-May/011767.html the new logdevspace is not usable until the old log is written around once after adding the new logdevspace. You always should enable autosave log to ensure that no log-full situation occurs regards, martin -- Martin Brunzema SAP AG (SAP DB Kernel) _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
