dmn@stiatl.UUCP (Michael Nowacki) (03/07/90)
twice in the last few months i have encountered this error. apparently a non-printable character got loaded into a char attribute. the problem is that ingres gives no indication of which table is at fault, let alone which row. tech support is of no real help. anyone have any tricks up their sleeve about how to find it? error was encountered running a report whose query uses a 4 table join. i have already copied the data by doing a create table ... as select *, then used copydb to unload and reload as the original. it seems to have read the invalid char with no complaint. i got out of this last time because someone else got lucky while browsing the data and found the funky chars. i don't have time for this. -- Michael Nowacki gatech!stiatl!dmn Sales Technologies, Inc |\ /| 3399 Peachtree Rd, NE | \/ | Atlanta, GA (404) 841-4000 _|ike |_