Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
T. Kramer 794-1472 — — source: Informix-list mailing list archive (1991-1998)
Hi
} The project I'm woking on requires some tables that have a lot of Insert and
} Delete activity. After a while these tables start generating failures
} (SQLCODE=-245, ISAM error 103). When this problem hits, it hits hard. Informix
} support has not been very helpful. They say it's fixed in a later release.
} That's all well and good, but it's not economically feasible to upgrade 50 sites
} right now. Informix suggested Dropping and reloading these tables. This is
} impossible on a POS system using real-time data collection.
}
} I have had to resort to filling these tables with a bunch of dummy data that is
} never deleted. This seems to be the best work around so far, but it only seems
} to delay the inevitable.
}
} Does anyone have some suggestions how solve this problem?
}
Are you sure about the -103? It rathers smells like a locking problem to me.
We have had problems like this but these have been due to the table being set
to page level locking. As soon as we changed it to row level locking the problem
dissappeared. If this doesn't help try increasing the lock wait time as follows:
'set lock mode to wait <time_in_seconds>'
Theo Kramer
theo@rascal.co.za
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.