after
utilizing a pl/sql routine found on asktom.com we were able to catch the
offending query that was consistently causing the 1652. (this isn't
something that you can capture from the v$ views if the session has disconnected
(at least i know of know way)) ...anyways the problem was that the
relevant tables were not properly intexed and not the size of the temp
space.
thank
you for the suggestions though.
-----Original Message-----
From: Bernardus Deddy Hoeydiono [mailto:[EMAIL PROTECTED]]
Sent: Sunday, January 19, 2003 9:29 PM
To: Multiple recipients of list ORACLE-L
Subject: RE: temp spaceHi Chris,The error ORA-1652 is because of the temporary tablespace for the corresponding table is not enough. The temporary tablespace for the table normally assigned when create the table. Or when create the user. If you're not define the temporary tablespace when you create the table, the temporary tablespace will follow the temporay tablespace that already assign in the user creation.To solve this problem, please resize the teporary tablespace.Thank'sBernardus Deddy Hoeydiono.-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Chris Stephens
Sent: Friday, January 17, 2003 9:55 PM
To: Multiple recipients of list ORACLE-L
Subject: temp spaceanyone know how to identify the session that caused a ORA-1652?
-thank you
