After a transaction is completed, it is considered a bad programming habit to COMMIT or roll back the transaction without display. Therefore, ensure that the COMMIT or ROLLBACK statement is executed after each transaction.
After a transaction is completed, it is considered a bad programming habit to COMMIT or roll back the transaction without display. Therefore, ensure that the COMMIT or ROLLBACK statement is executed after each transaction.
A transaction is a logical unit of work used to separate database activities. A transaction has a starting point and an ending point;
When one of the following events occurs, the transaction starts:
Connect to the database and execute the DML statement on the first day;
After the current transaction ends, another DML statement is entered;
When one of the following events occurs, the transaction ends:
Note: after the transaction is completed, if you do not explicitly COMMIT or roll back the transaction, it is considered a bad programming habit. Therefore, ensure that the COMMIT or ROLLBACK statement is executed after each transaction.
Oracle Tutorial: instance fault recovery
Installing Oracle 12C in Linux-6-64
Install Oracle 11gR2 (x64) in CentOS 6.4)
Steps for installing Oracle 11gR2 in vmwarevm
Install Oracle 11g XE R2 In Debian