Anyone have any clues as to what possible causes for the above error message could be?
The routine in which this occurs is part of a local refresh from a production db. It consists of an INSERT followed by multiple UPDATEs, most of which are 2-table correlations (WHERE t1.ColumnValue = T2.ColumnValue). Sometimes, the routine works, and sometimes it does not. It is run after a series of INSERTs from an SATTACHED ORACLE db. The RB database was "clean", i.e. ROWS DELETEd and PACKed shortly before the refresh. Got a pretty nice, new CPU, with plenty of HD space and RAM. Running VISTA. This is mostly a nuisance as it almost always works after this failure when I run it from the R>. Thanks, Steve in Memphis J. Stephen Wills Program Manager, Research Informatics Office of the Vice Chancellor for Research University of Tennessee Health Science Center 62 S. Dunlap, Suite 400 Memphis, TN 38163 Office: 901-448-2389 FAX : 901-448-7133
