数据库被锁是什么原因

一个菜鸟

提示“329atabase not found or no system permission”
    “178:database is locked;pending change to logging mode”

我的环境是WIN2K、IDS9.4

谢谢

IFMXDBA

try to check if there is a staled ontape process, which was used to change database 'log mode' or archive. Also, check online.log, see if there was a long checkpoint.  When issue ontape to archive database/change log mode, it will trigger a checkpoint. Normally, the checkpoint will be finished very quickly. Sometimes, a long checkpoint duration might be seen due to the hardware ( disk, SAN/RAID) problem.

一个菜鸟

如题，能详细的说说怎么解决吗？谢谢

IFMXDBA

try to check if there is an staled ontape process ( a no-responding ontape process ), which was doing archiving/changing log mode ( ontape/onbar ).  
You can simply do that by "ps -elf | grep ontape"  or onstat -g ath to find the ontape thread.  Then, try to verify it by onstat -l  (logs) and onstat -d ( chunks ) to check if there is still disk read/write for log there.  If you find a problem ontape process, you can try to kill it.

一个菜鸟

以前出现过一次，后来没办法重做了

IFMXDBA

"没办法重做了",  do you mean you can not produce it ?   Or you re-initialized the instance ?    If so, that will be a sad experience.  Re-initialize the instance is the last thing you should do, since the data in the system may be lost.
Did you try to bounce the database instance ?  reboot the NT box  ?  call IBM support ?  Restore from level 0 archive and roll forward all the logical logs ?  
Don't hesitate to call support, mark down all the error msg before calling.  I am not sure the current support policy.  Normally, they will help you if your case is an urgent one, like the one you mentioned above.  It won't hurt to call for help.

一个菜鸟

我只买了一年的服务，技术支持他们不理我

IFMXDBA

It's too bad.  Informix delivered very good services before it was acquired by IBM ...

sqlnet

原帖由 一个菜鸟 于 2006-9-13 10:01 发表
我只买了一年的服务，技术支持他们不理我

一年的服务多少米啊？ 兄弟。。

华光骑士

-178    ISAM error: Database is locked; pending change to logging mode.

A request has been made to change the logging status of a database.
Until a level-0 archive is done for all the storage spaces that the
database uses, access to the database is blocked.

==============
From above information , you should check the server status and  running process which is tring to change database logging status .Follow IFMXDBA suggestion , first find the ontape/onbar process and kill it ,then reboot the database server and check the online.log .
Another , did you change the machine 's time before the accident ? If so , pls correct it and reboot DB server again .
Do a dummy backup in informix is very simple , modify the onconfig file parameter TAPEDEV to NULL and run 'ontape -s -L 0 ' from command window .