Re: OnLine 5.00 database corruption
>>>>> On Fri, 19 Nov 1993 17:03:30 GMT, oliver@infix.de (Oliver Okrongli) said:
> We just experienced inconsistencies in OnLine 5.00 databases on two
> different ports. It started with log messages "bfcheck: bad page ..."
> just two days after installation. Finally (after a week or so) the
> database was completely unusable and had to be re-built from scratch.
[...]
> Environment:
> INFORMIX-OnLine 5.00.UC2 PRODUCT RELEASE, DATE: 02/04/93
> PORT NUMBER: 001103, UnixWare SVR4.2 (running on USL SVR4.2)
> INFORMIX-OnLine 5.00.UD4 PRODUCT RELEASE, DATE: 07/06/93
> PORT NUMBER: 100051, Olivetti LSX5040, SVR4.0 MP
Fortunately, we managed to track down the problem. It occurs in a
MODE ANSI database when temporary tables created with CREATE TEMP
TABLE or SELECT INTO TEMP are rolled back.
For us it's still a serious problem. Significant parts of over
1,000,000 lines of code would have to be re-structured completely in
order to work around this bug. This is clearly not an option here.
We now hope Informix will provide a timely fix.
The following shell script should reproduce it.
----%<--snip----%<--snip----%<--snip----%<--snip----%<--snip----%<--snip----
#!/bin/sh
#
# Shell script reproducing problem informix/50
#
dbaccess -e << -END create database p50 with log mode ansi;-END
dbaccess -e p50 << -END create temp table table1
(
column1 integer
); rollback work;
-END
echo "First WARNING in OnLine's log file at `date`.\\n\\n"
dbaccess -e p50 << -END select tabid
from informix.systables
into temp table2; rollback work;
-END
echo "Another WARNING in OnLine's log file at `date`.\\n\\n"
dbaccess -e << -END drop database p50;-END
----%<--snip----%<--snip----%<--snip----%<--snip----%<--snip----%<--snip----
--
Oliver Okrongli infix Software-Systeme GmbH Phone +49 531 238090
Rebenring 33 Fax +49 531 2380935
oliver@infix.de 38106 Braunschweig F.R. Germany