Spurious error 197?
Related threads
- Pls Help: Cannot install IDS 7.30.UC7-1 on Fedora 8. Segmentation fault
- Indexing large fragmented table
Posted in 2003
Topics: Storage & Space Management, Error Codes & Troubleshooting, Connectivity: ESQL/C, 4GL & Embedded SQL, Data Types & Schema Design, Logging & Checkpoints
IDS9.30HC5, HPUX 11i, 4GL 7.20 Just had this on one of our test systems when writing to a table: ===================================================================== -197 ISAM error: Partition recently appended to; can't open for write or logging. If this internal error recurs, please note all circumstances and contact Technical Support at tsmail@us.ibm.com. ===================================================================== .... but we haven't added any chunks or anything. Tried a checkpoint and a logical log (Oh how the immature techies laugh when you tell them you're going to force a log to see what happens. sigh.) but still got the error (both INSERT and UPDATE); it cleared when I did a level-0 to /dev/null. There are no blobs or varchars or anything nasty on the table, and no untoward messages in the online log - the instance has been up happily for the last week. Anyone seen this before? I'll raise a tech support case but they won't be that interested as the fault has cleared up. Cheers Malc
Have you performed a load using the High Performance Loader? "Malc P" <malc_p@btinternet.com> wrote in message news:8c28402a.0312230839.5d09f3e9@posting.google.com... > IDS9.30HC5, HPUX 11i, 4GL 7.20 > Just had this on one of our test systems when writing to a table: > ===================================================================== > -197 ISAM error: Partition recently appended to; can't open for > write or logging. > > If this internal error recurs, please note all circumstances and > contact Technical Support at tsmail@us.ibm.com. > ===================================================================== > > .... but we haven't added any chunks or anything. Tried a checkpoint > and a logical log (Oh how the immature techies laugh when you tell > them you're going to force a log to see what happens. sigh.) but still > got the error (both INSERT and UPDATE); it cleared when I did a > level-0 to /dev/null. There are no blobs or varchars or anything nasty > on the table, and no untoward messages in the online log - the > instance has been up happily for the last week. > Anyone seen this before? I'll raise a tech support case but they won't > be that interested as the fault has cleared up. > Cheers > Malc
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.