informix onbar 備份失敗Archive API processing failed at line 258 for rc.

今天發現一臺伺服器Onbar備份的時候失敗，日誌提示：

2008-03-25 12:25:42 16841 16839 /home/informix/bin/onbar_d -b -L 0
2008-03-25 12:25:43 16841 16839 Archive started on rootdbs, llogdbs, plogdbs, datadbs01, datadbs02, fstempdbs, indexdbs01 (Requested Level 0).
2008-03-25 12:25:46 16841 16839 Unable to start the storage space backup: buc_fe.c : Archive API processing failed at line 258 for rc.
2008-03-25 12:25:46 16841 16839 Archive on rootdbs, llogdbs, plogdbs, datadbs01, datadbs02, fstempdbs, indexdbs01 ABORTED (Requested Level 0).
2008-03-25 12:25:56 16841 16839 /home/informix/bin/onbar_d complete, returning 131 (0x83)

google搜尋得到ibm的解釋為：

Error: Archive failed - buc_fe.c : Archive API processing failed at line 258 for rc
Technote (FAQ)

Problem
This article describes a known issue when taking an ontape archive.

Solution
PROBLEM

When you run an ontape command in order to perform an archive, you receive the error message:

Archive failed - buc_fe.c : Archive API processing failed at line 258 for rc

SCOPE

The following products and operating systems are affected:

Product Name Product Version(s)
IBM Informix? Dynamic Server? 9.40.xC7 and earlier
10.00.xC4 and earlier

x can be T, U, H, or F depending on your operating system.

CAUSE

This is a known product defect. The defect number is 175568 .

Important: This is only one possible cause of the problem. If this document does not provide you with a solution to your problem, you should search for other documents that refer to this topic.

SOLUTION

Contact your local technical support office for an upgrade.

If you have Then request
IBM Informix? Dynamic Server?
9.40.xC7 and earlier
IBM Informix? Dynamic Server?
9.40.xC8 or later

IBM Informix? Dynamic Server?
10.00.xC4 and earlier
IBM Informix? Dynamic Server?
10.00.xC5 or later

x can be T, U, H, or F depending on your operating system.

但是我們發現現在這個資料庫還有一些其他的原因，估計也是這個原因造成的，需要把資料庫重新匯出匯入。

其他原因出現的日誌：
13:03:08 Results: Unused temp tables and/or deferred indexes may remain
13:03:08 Action: Cleanup will be reattempted during next initialization