Today in the project development, in order to test the project SQL execution effect, with Plsql developer execution, no commit to continue to tap the code, and then re-use Plsql Developer, may be network reasons, Plsql Developer disconnected from the database and was stuck, forcing it to end. The code after the test, the project did not effect after the execution, and no response, debug found that JDBC did not respond to SQL, asked the Valley teacher to find the reason. because there is no commit,oracle to lock the record when Plsql developer executes the update. can be resolved by querying the lock record first 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 locked record SQL code alter system KILL session ' sid,serial# '; Where SID fills in the SID values found above, serial# fills in the values of serial# columns such as: ALTER system KILL Session ' 214,23456 ';
Solutions to the problem of card-dead when Oracle executes update