SYBASE一些故障处理方法
Error: 3475, Severity: 21, State:7
00:00000:00001:2000/01/04 07:43:42.68 server Can't allocate space for object
'syslogs' in database 'DBbad' because 'logsegment' segment is full/has no free
extents. If you ran out of space in syslogs, dump the transaction log.
Otherwise, use ALTER DATABASE or sp_extendsegment to increase size of the
segment.
00:00000:00001:2000/01/04 07:43:42.68 server Error: 3475, Severity: 21, State:
7
00:00000:00001:2000/01/04 07:43:42.68 server There is no space available in
SYSLOGS for process 1 to log a record for which space has been reserved. This
process will retry at intervals of one minute. The internal error number is -4.
1. You will have to bring the server up with trace flag 3608 to prevent the
recovery of the user databases.
2. sp_configure "allow updates",1
go
3. Write down the segmap entries from the sysusages table for the toasted
database.
4. update sysusages
set segmap = 7
where dbid = db_id("my_toasted_db")
and segmap = 3
5. select status - 320
from sysdatabases
where dbid = db_id("my_toasted_db") -- save this value.
go
begin transaction
update sysdatabases set status = -32768 where dbid = db_id("my_toasted_db")
go -- if all is OK, then...
commit transaction
go
shutdown
go
6. Restart the server without the trace flag.With luck it should now have
enough space to recover.If it doesn't, you are in deeper trouble than
before, you do have a good, recent backup don't you?
7. dump database my_toasted_db with truncate_only
go
8. Reset the segmap entries in sysusages to be those as saved in 3. above.
9. Shutdown ASE and restart.(The traceflag should have gone at step 6., but
ensure that it is not there!)
sybase数据库error 3474的解决。
3474错误："During redo the page timestamp value is less than old timestamp from log.Page……"
isql -Usa -P -Ssybase :
1>sp_configure "allow updates",1
2>go
1>update sysdatabases set status=-32768 where name="xtsum"
2>go
1>shutdown
2>go
重新启动数据库服务。
isql -Usa -P -Ssybase
1>dbcc rebuild_log(xtsum,0,0)
2>go
1>dbcc rebuild_log(xtsum,1,1)
2>go
1>shutdown
2>g
重新启动数据库服务器
isql -Usa -P -Ssybas
1>update sysdatabases set status=12 where name="xtsum"
2>g
1>sp_configure "allow updates",0
2>
1>shutdown
2>
重启数据库后，恢复正常，rebuild log工作完成。
SYBASE3414错误处理:
解决办法:
重建数据库日志,方法如下:
(1)赋予sa用户sybase_ts_role的角色
isql -Usa -P
1>sp_role "grant","sybase_ts_role",sa
2>go
1>quit
(2)将数据库置为"bypass recovery"状态
isql -Usa -P
1>sp_configure "allow updates",1
2>go
1>use master
2>go
1>update sysdatabases set status=-32768
2>where name="database_name"
3>go
1>shutdown with nowait r`;m'H!
2>go
(3)rebuild数据库日志
重启Server
isql -Usa -P q=7$ |_.
1>use master
2>go
1>dbcc rebuild_log(database_name,1,1)
2>go
1>shutdown with nowait
2>go
(4)重启server
1>use master
2>go
1>update sysdatabases set status=0 where name="database_name"
2>go
1>sp_configure "allow updates",0
2>go
1>shutdown with nowait
2>go
(5)在重启server之后,如果数据库恢复正常，rebuild log工作将会成功完成，否则要恢复数据库备份，使用dump database或bcp命令。
上面都是本人在实际工作当中碰到过,并且成功处理过的,希望能够给大家提供一点帮助,因为个在在前期出现这些问题时,真得没办法,在网上找了很长时间,最后参考SYBASE相关的文档，希望其他人不要走弯路。 不错 看来需要的人不多呀,自个顶一下 多谢 收藏了，希望以后能用上 学习。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。 多谢,收藏 up log full最简单的办法加log的空间。如果采用LZ的做法，第一，当前做的事务有可以会产生部分数据被修改的问题，第二、已经提交的事务很有可能数据没有写入硬盘中。 原帖由 tyrone.dev 于 2009-2-27 05:27 发表 http://bbs3.chinaunix.net/images/common/back.gif
log full最简单的办法加log的空间。如果采用LZ的做法，第一，当前做的事务有可以会产生部分数据被修改的问题，第二、已经提交的事务很有可能数据没有写入硬盘中。
你说的有道理，但当时数据库服务器都无法启动，无法加载设备的情况下，采取的此种方式。不妥的正如你所说的情况，只能算是应急的一种办法了！
页:
[1]
2