In our project I create some global temp table that will be like these:
CREATE GLOBAL TEMPORARY TABLE v2dtemp (
id NUMBER,
GOOD_TYPE_GROUP
Killing sessions is the only way to work around ORA-14452 errors. Use the data dictionary to find other sessions using the temporary table and kill them
with a statement like alter system kill session 'sid,seriall#,instance_id';
.
This is the "official" solution mentioned in the Oracle support document HOW TO DIAGNOSE AN ORA-14452 DURING DROP OF TEMPORARY TABLE (Doc ID 800506.1). I've successfully used this method in the past, for a slightly different reason. Killing sessions requires elevated privileges and can be tricky; it may require killing, waiting, and trying again several times.
This solution is almost certainly a bad idea for many reasons. Before you implement this, you should try to leverage this information as proof that this is
the wrong way to do it. For example, "Oracle documentation says this method requires alter system
privilege, which is dangerous and raises some
security issues...".