Home > database >  The oracle database to unlock
The oracle database to unlock

Time:10-10

Login database super-user: up sqlplus/as sysdba
The alter user name ACCOUNT UNlOCK;

CodePudding user response:

This is your unlock the user

CodePudding user response:

Can you tell me the database locking like?
Ink head sheave version of "" question the wisdom of" - the problem of how to ask questions that I can get a faster answer?"

CodePudding user response:

Oracle solutions to different cloth lock!
Often due to network instability or database of bugs, produced when use dblink asynchronous lock, the following will talk about asynchronous lock solution:
1) query dba_2pc_pending, determine the current state of the asynchronous lock,
The select local_tran_id global_tran_id, state, mix, host, commit# fromdba_ 2 pc_pending;


LOCAL_TRAN_ID | GLOBAL_TRAN_ID | STATE | MIX | HOST | COMMIT#
-- -- -- -- -- -- -- -- -- -- -- -- - | -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- - | -- -- -- -- -- -- -- -- - | -- - | -- -- -- -- -- -- -- -- -- - | -- -- -- -- -- -- --
1.10.255 | V817REP.BE.ORACLE.COM | committed | no | BE - ORACLE - | 202241
| 89 f6eafb 1.10.255 | | | NT/bel449 |


At this time through state=committed, said the session is to ask, just after the submission, accept less than global transaction information of the session, so produce asynchronous lock, at this time of common cause no table lock,
By invoking the execute DBMS_TRANSACTION. PURGE_LOST_DB_ENTRY (' 1.10.255 '); To solve this problem,
State, of course, there are the following condition:
Collecting: in the process of collecting data, produce abnormal
The solution: the execute DBMS_TRANSACTION. PURGE_LOST_DB_ENTRY (' 1.10.255 ');

Prepared: before receive the asynchronous commit/rollback command, produce abnormal
The solution: the rollback force tran_id/commit force tran_id; - can be decided according to the state of asynchronous transaction usage,

Forced the rollback: in the use of the rollback force in
The solution: the execute DBMS_TRANSACTION. PURGE_LOST_DB_ENTRY (' 1.10.255 ');

Forced to commit: when using the commit force appear
The solution: the execute DBMS_TRANSACTION. PURGE_LOST_DB_ENTRY (' 1.10.255 ');

CodePudding user response:

Fuck I have write wrong I'm really a brother

CodePudding user response:

The Oracle database lock is too much, you can say specific point is met what problem,
  • Related