When oracle executes the update statement, the problem is solved. During project development today, in order to test the SQL Execution effect in the project, PLSQL Developer executes the statement. Without commit, the code will continue to be typed, when PLSQL Developer is re-used, it may be due to network reasons. If PLSQL Developer is disconnected from the database and becomes stuck, it is forced to end. After the code is knocked out, the test will be conducted. After the project is executed, there will be no effect and no response. After debugging, I find that jdbc does not respond when executing the SQL statement. I asked Miss Gu to find the reason. Since there is no commit when PLSQL Developer executes update, oracle locks this record. Www.2cto.com can be solved through the following method: first query the lock record SQL code SELECT s. sid, s. serial # FROM v $ locked_object lo, dba_objects ao, v $ session s WHERE ao. object_id = lo. object_id AND lo. session_id = s. sid; then delete the lock record SQL code ALTER system KILL session 'sid, serial #';