This is a discussion on Confounding -567 error within the Informix forums, part of the Database Server Software category; --> We have a 4GL report (r4gl 7.32, hitting IDS 10.00.UC5, Solaris 8) that occasionally fails with error -567 (cannot ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| We have a 4GL report (r4gl 7.32, hitting IDS 10.00.UC5, Solaris 8) that occasionally fails with error -567 (cannot write sorted rows), ISAM -2 (no such file or directory). I have no earthly idea why. We do have PSORT_DBTEMP set to three different file systems, all of which are writable by Informix, and all of which have plenty of space available. Also, the temp spaces listed in DBSPACETEMP (which should be irrelevant with PSORT_DBTEMP set) have gobs of space available. Yes, we have support, and yes, I've opened a PMR (pending), but I was hoping someone here could shed some additional insight. As an added bonus, the problem seems to prefer to occur during the wee hours of the morning. I need to confirm with our developers, but I'm reasonably sure that the report runs from an automated nightly job -- when run manually, I believe the report runs successfully, with no such error. Any ideas? I'd be glad to provide whatever additional information you dee |