There are two temporary tables in Oracle. One is session-based, that is, when a commit occurs, the data is cleared; the other is session-based. When a session is disconnected, the data
There are two temporary tables in Oracle. One is session-based, that is, when a commit occurs, the data is cleared; the other is session-based. When a session is disconnected, the data
There are two temporary tables in Oracle. One is session-based, that is, data is cleared after a commit occurs, and the other is session-based. When a session is disconnected, data is cleared.
-- Transaction-based temporary table
Create global temporary table test
(
ID number
)
On commit delete rows;
-- Session-based temporary table
Create global temporary table test
(
ID number
)
On commit preserve rows;
If your system architecture is a three-tier architecture with a connection pool, such as weblogic + oracle, the session will not actually exit, but after the request is complete, the session will be returned to the connection pool. If you operate a session-based temporary table without deleting the table after each operation, the data will accumulate. The best practice is to truncate after use, and use the problems found in the system test environment today.
Install Oracle 11gR2 (x64) in CentOS 6.4)
Steps for installing Oracle 11gR2 in vmwarevm
Install Oracle 11g XE R2 In Debian