Curious things on dbimport. Any Idea ?
Posted in 1998
Hi all,
We are now upgrading our application from SE 5.00 to OL 7.20 as engine
and from RDS 4.10 to RDS 6.05 on Solaris 2.5.
We experienced a lot of problem (do you remember error 507 ? ) but the
most strange thing is that one:
We have prepared a dbexport from our old database on SE and then
we have issued a dbimport on the new OL one.
After that we have changed the logging to unbuffered ( where is the
onmonitor ? ) and then we changed the mode lock to row.
All seems right 'til now so we started with tests on it and here
appeared the problem. we inserted a row in a table, started a report on
the table and we have seen two rows ???
So Isql for check and he say "two row".
At this time all was panic but as last resource we issued an "update
statistic" an magically the problem was fixed.
So we are now asking : what can be the problem ?
Is a bug of dbimport or maybe we need to run an update statistic for any
row we insert in table?
All that problem seems strange to us because we have had (quite ) no
problem with the old release of informix.
Any idea on that ?
Do we have to expect some other surprises during the upgrade?
Do Informix plan to begin to do some better work ?
T.I.A. and sorry for my not good english.
Pigi
--
___________
FRULLANI Pierluigi Frullani | Tel. +39 2-29003554 Fax +39 2-29003580
& Software Manager | Via Varese 12, 20121 Milano (Italia)
FRULLANI Frumar s.r.l. | Email Pierluigi.Frullani@frumar.it
___________ | http://www.frumar.it