Informix problem

[koko45]

What could be the cause of this problem ???
1. A problem was encountered by a user when trying to update a record and recieved a message like "Could not do a physical-order to fetch next row"

2. As they were trying to add record there was report running which was running to a long time, which was unusual.

3. The next day they system crushed - Production Environment was down and now they have to do a complete restore which has taken already 5 days to restore and also it is still restoring.

Can anyone help find the cause and help in anyway find a solution to it.

The Machine used is HP and running UnixWare. The programming tool is Infomix-4gl and Fourgen .

 

[olded]

Hi:

The "Could not do a physical-order to fetch next row" is a symptom of a locking or isolation level issue.

The most obvious thing to check is whether the table(s) in issue are at row level locking and not page level.

Regards,

Ed

 

[vpshriyan]

Hi,

1. "Could not do a physical-order to fetch next row" message is a common muti-user environment related issue. It can happen when row(s) needed is/are locked by other sessions. Even if the table which is configured for ROW level locking, it not not immune to this error message; but granularity or scope of locking will be limited to a single row. It will facilitate maximum concurrency. One should be able to solve this problem by setting "SET LOCK MODE TO WAIT" sql statement. As a thumb rule it is always suggested to set a table to ROW level locking mode, if the table is traffic oriented or it is fully prone to transactional volatility. It is far unlikely that this kind of error status is responsible to database server crash.

2. Row insertion may take long depending on different circumstantial conditions prevalent in a database server, like number of columns, numbere of indexes, load in dbserver, kind of database log etc.

3. A database server may crash owing to variety of reasons. Dbserver maintains messages of the crucial activites at message log. This log may tell more about the crash. If you can post the relevant portions of this log, it will be help us in indentifying the problem.

Regards,
Shriyan