Anyone ever heard of this happening...a 4030 error that is not a real 4030 error? The client is a powerbuilder app running in a citrix environment? Is it possible to trigger a 4030 error on the client side within a PB application? This didn't make a lot of sense to me.=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D Oracle states that this was not an ora-4030 error. A 4030 error is a server side error and as such we would have received errors in the alert log, a trace file with a heap dump and very possibly a core dump. We have none of those. The trace file that was generated does not contain a heap dump and basically has no information that Oracle can look at to determine the problem. He stated that it appeared that the client software thought it had received an out-of-memory error=20 and so reported it as a 4030 error. This is possible as the Oracle messages are loaded on the client based on the client installs done here. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D -- //www.freelists.org/webpage/oracle-l