SYBASE数据库系统检查和日常维护命令指南(2)

device_fragments size usage created free kbytes

---------------- ---- ----- ------- -----------

ksqhdb_part1 1000.0 MB data only Sep 6 2006 9:37AM 705104

ksqhdb_part2 1000.0 MB data only Sep 6 2006 9:37AM 1019490

ksqhdb_part3 1000.0 MB data only Sep 6 2006 9:37AM 1006902

ksqhdb_part4 1000.0 MB data only Sep 6 2006 9:37AM 1020000

ksqhdblog 1000.0 MB log only Sep 6 2006 9:37AM not applicable

- log only free kbytes = 1019850

所有设备均显示data only或log only，代表数据段和日志段都使用独立设备

B． 如果日志段使用独立设备，当可用空间为50%以下时，使用dump tran dbname to ‘dumpfile’命令备份并

截断非活动日志

C． 如果日志段使用混合设备或者数据库选项’trunc log on chkpt’被打开，当可用空间为50%以下时，

需确保当前数据库为空闲状态后，运行dump tran dbname with truncate_only命令截断非活动日志。

日志被截断后后，请尽快执行dump database dbname命令，确保数据库故障时可以利用备份介质恢复到 故障发生点。

D． 一般情况禁止使用dump tran dbname with no_log截断日志空间，该命令仅用于数据库崩溃后的紧急恢复。

执行周期：可随时执行。

1.4 SYBASE数据库日志文件检查

检查方法：检查SYBASE数据库.log消息日志文件，详见下表：

检查内容 数据库消息日志 正常状态 非正常状态和采取措施 消息日志中无severity消息日志中出现severity大于大于18的出错信息， 18的信息，代表数据库发生关键错误，联系SYBASE支持小组确认解决方案。 命令举例： bash-2.05$ tail -100 /opt/sybase/ASE-12_5/install/SYBASE.log

此处应根据实际情况确定需要查看消息日志文件长度。

00:00000:00001:2006/09/07 14:51:03.20 server Started estimating recovery log boundaries for database 'archivedb'.

00:00000:00001:2006/09/07 14:51:03.20 server Database 'archivedb', checkpoint=(2385377, 4), first=(2385377, 4), last=(2385377, 4).

00:00000:00001:2006/09/07 14:51:03.20 server Completed estimating recovery log boundaries for database 'archivedb'.

00:00000:00001:2006/09/07 14:51:03.20 server Started ANALYSIS pass for database 'archivedb'. 00:00000:00001:2006/09/07 14:51:03.20 server Completed ANALYSIS pass for database 'archivedb'.

00:00000:00001:2006/09/07 14:51:03.20 server Started REDO pass for database 'archivedb'. The total number of log records to process is 1.

00:00000:00001:2006/09/07 14:51:03.23 server Completed REDO pass for database 'archivedb'.

00:00000:00001:2006/09/07 14:51:03.23 server Recovery of database 'archivedb' will undo incomplete nested top actions.

00:00000:00001:2006/09/07 14:51:03.23 server Started recovery checkpoint for database 'archivedb'. 00:00000:00001:2006/09/07 14:51:03.23 server Completed recovery checkpoint for database 'archivedb'. 00:00000:00001:2006/09/07 14:51:03.24 server Started filling free space info for database 'archivedb'. 00:00000:00001:2006/09/07 14:51:03.24 server Completed filling free space info for database 'archivedb'.

00:00000:00001:2006/09/07 14:51:03.24 server Started cleaning up the default data cache for database 'archivedb'. 00:00000:00001:2006/09/07 14:51:03.24 server Completed cleaning up the default data cache for database 'archivedb'.

00:00000:00001:2006/09/07 14:51:03.24 server The transaction log in the database 'archivedb' will use I/O size of 2 Kb.

00:00000:00001:2006/09/07 14:51:03.25 server Database 'archivedb' is now online.

00:00000:00001:2006/09/07 14:51:03.31 server Recovery has restored the value of 'local async prefetch limit' for '16K' pool in 'default data cache' from '80' to 'DEFAULT'.

00:00000:00001:2006/09/07 14:51:03.31 server Recovery has restored the value of 'local async prefetch limit' for '2K' pool in 'default data cache' from '80' to 'DEFAULT'.

00:00000:00001:2006/09/07 14:51:03.38 server Recovery has restored the original size for '16K' pool and '2K' pool in 'default data cache'.

00:00000:00001:2006/09/07 14:51:03.41 server Recovery complete.

00:00000:00001:2006/09/07 14:51:03.41 server SQL Server's default unicode sort order is 'binary'. 00:00000:00001:2006/09/07 14:51:03.42 server SQL Server's default sort order is: 00:00000:00001:2006/09/07 14:51:03.42 server 'bin_iso_1' (ID = 50)

00:00000:00001:2006/09/07 14:51:03.42 server on top of default character set: 00:00000:00001:2006/09/07 14:51:03.42 server 'iso_1' (ID = 1).

00:00000:00001:2006/09/07 14:51:03.42 server Master device size: 60 megabytes, or 30720 virtual pages. (A virtual page is 2048 bytes.)

执行周期：可随时执行。