Configuration Review :
HugePages not enable.
Refferences : When And Why To Use HugePages on Linux x86-64? (Doc ID 2314903.1)
max locked memory & stack size below oracle recommendation:
Ref : https://docs.oracle.com/en/database/oracle/oracle-database/19/ladbi/checking-resource-limits-for-oracle-software-installation-users.html
Swap Spcae Allocation Below Recommendation.
Ref : https://docs.oracle.com/en/database/oracle/oracle-database/19/ladbi/server-configuration-checklist-for-oracle-database-installation.html
SELECT session_id FROM gv$locked_object v, dba_objects d WHERE v.object_id = d.object_id AND object_name = 'YOUR_TABLE_NAME'; ALTER SYSTEM KILL SESSION 'sid,serial#'; TRUNCATE TABLE your_table_name;
Select object_id from dba_objects where object_name= ' T1 '; object_id ---------- 52505 Sql> Select Object_id,session_id,oracle_username,os_user_name,process,locked_mode from V$locked_object where object_id=52505; object_id session_id oracle_username os_user_name PROCESS Locked_mode --------- ---------- ---------------- ------------- -------- ----------- 52505 149 SCOTT Oracle 5333 3 Visible from above, it is the user Scott, who is Sid 149, who is working on this table and can get more information by querying V$session: Sql> Select sid,serial#,username,process from v$session where sid=149; SID serial# USERNAME PROCESS --------- ---------- -------------- ------------ 149 136 SCOTT 5333 Then, if the operation allows, you can kill the transaction: Sql> alter system kill session ' 149,136 ';