1105错的困惑
<p>数据库为12.5.0.3,日志报Error: 1105, Severity: 17, State: 4</p><p>Can't allocate space for object 'syslogs' in database 'xxx' b<br/>ecause 'logsegment' segment is full/has no free extents. If you ran out of space in syslogs, dump the transacti<br/>on log. Otherwise, use ALTER DATABASE or sp_extendsegment to increase size of the segment.</p><p> 检查SYBASE文档提示</p><p>Recovery 1105 Errors on a User Database<br/>Use the following procedure to correct 1105 errors on a user database which occur during recovery:<br/>1.Manually set the database's status to no chkpt on recovery and single-user: <br/>Warning! Because the database was marked suspect on the original recovery attempt, this procedure also resets some internal status bits to allow the database to recover normally. Therefore, do not use this procedure under any other circumstances, or you may create additional serious problems.<br/>1> sp_configure "allow updates", 1<br/>2> go<br/>1> begin transaction<br/>2> go<br/>1> update master..sysdatabases <br/>2> set status = status & ~256<br/>3> where name = "database_name"<br/>4> go<br/>1> update master..sysdatabases <br/>2> set status = status | 4112<br/>3> where name = "database_name" <br/>4> go</p><p>2.Check that each of the above update commands affected only one row. If more than one row was affected, issue a rollback transaction. Otherwise, commit the transaction and shut down Adaptive Server:<br/>1> commit transaction<br/>2> go<br/>1> shutdown<br/>2> go<br/>3.Restart Adaptive Server.<br/>4.Dump the transaction log with the no_log option and reset the database status:<br/>1> use master <br/>2> go<br/>1> dump tran database_name with no_log<br/>2> go<br/>1> sp_dboption database_name, "no chkpt", false<br/>2> go<br/>1> sp_dboption database_name, single, false<br/>2> go<br/>1> use database_name</p><p>2> go<br/>1> checkpoint<br/>2> go<br/>1> sp_configure "allow updates", 0<br/>2> go</p><p>但是并管理员并未进行任何操作,而数据库也能使用,何故?</p> understand what the manual says.<br/>
页:
[1]