开发人员告诉我在使用基于事物的临时表的时候报了下面错误:ORA-14450: attempt to access a transactional temp table already
开发人员告诉我在使用基于事物的临时表的时候报了下面错误:
ORA-14450: attempt to access a transactional temp table already in use
下面根据实验模拟了2种临时表使用不当报ORA-1445O的原因:
1)基于事物的临时表
SQL> create global temporary table temp_tab on commit delete rows as select 'a' as a1 from dual;
Table created.
SQL> select sid from v$mystat where rownum=1;
SID
----------
191
SQL> insert into temp_tab values ('b');
1 row created.
SQL>
在191回话不做commit,打开另外一个session 执行ddl(如果在同一会话可以成功执行ddl语句)
SQL> alter table temp_tab add b1 varchar2(10);
alter table temp_tab add b1 varchar2(10)
*
ERROR at line 1:
ORA-14450: attempt to access a transactional temp table already in use
SQL> select sid from v$mystat where rownum=1;
SID
----------
40
SQL>
返回session 191 执行自定义事物
SQL> declare
2 pragma autonomous_transaction;
3 begin
4 insert into temp_tab values ('c');
5 commit;
6 end;
7 /
declare
*
ERROR at line 1:
ORA-14450: attempt to access a transactional temp table already in use
ORA-06512: at line 4
2)基于session 的临时表
SQL> drop table temp_tab purge;
Table dropped.
SQL> create global temporary table temp_tab on commit preserve rows as select 'a' as a1 from dual;
Table created.
SQL> select sid from v$mystat where rownum=1;
SID
----------
191
SQL> insert into temp_tab values ('a');
1 row created.
SQL> alter table temp_tab add b1 varchar2(10);
alter table temp_tab add b1 varchar2(10)
*
ERROR at line 1:
ORA-14450: attempt to access a transactional temp table already in use
SQL> select * from temp_tab;
A
-
a
a
SQL> commit;
Commit complete.
SQL> alter table temp_tab add b1 varchar2(10);
alter table temp_tab add b1 varchar2(10)
*
ERROR at line 1:
ORA-14450: attempt to access a transactional temp table already in use
上面实验可以看出基于session 的临时表在同一个session内运行一个事物,无论是提交还是未提交都不能做ddl操作
再运行一个事物,不提交到另外一个session做ddl报错同样错误
SQL> delete from temp_tab;
2 rows deleted.
SQL> select sid from v$mystat where rownum=1;
SID
----------
40
SQL> alter table temp_tab add b1 varchar2(10);
alter table temp_tab add b1 varchar2(10)
*
ERROR at line 1:
ORA-14450: attempt to access a transactional temp table already in use
提交之后,在另外session测试发现还是无法ddl
SQL> commit;
Commit complete.
退出session,仅有一个会话做ddl
SQL> alter table temp_tab add b1 varchar2(10);
Table altered.
总结:
a, 基于transaction的临时表在同一个session里面不允许做自定义事物,并且若在一个session里面运行了一条事物未做提交,在另外一个session无法做ddl操作
b, 基于session的临时表若在某一个sesson里面运行了事物,任何session都不运行做ddl包括运行该事物的session
相关阅读:
Oracle ORA-01555 快照过旧 说明
ORA-01078 和 LRM-00109 报错解决方法
ORA-01555超长的Query Duration时间
ORA-00471 处理方法笔记
ORA-00314,redolog 损坏,或丢失处理方法
ORA-00257 归档日志过大导致无法存储的解决办法

MySQL index cardinality has a significant impact on query performance: 1. High cardinality index can more effectively narrow the data range and improve query efficiency; 2. Low cardinality index may lead to full table scanning and reduce query performance; 3. In joint index, high cardinality sequences should be placed in front to optimize query.

The MySQL learning path includes basic knowledge, core concepts, usage examples, and optimization techniques. 1) Understand basic concepts such as tables, rows, columns, and SQL queries. 2) Learn the definition, working principles and advantages of MySQL. 3) Master basic CRUD operations and advanced usage, such as indexes and stored procedures. 4) Familiar with common error debugging and performance optimization suggestions, such as rational use of indexes and optimization queries. Through these steps, you will have a full grasp of the use and optimization of MySQL.

MySQL's real-world applications include basic database design and complex query optimization. 1) Basic usage: used to store and manage user data, such as inserting, querying, updating and deleting user information. 2) Advanced usage: Handle complex business logic, such as order and inventory management of e-commerce platforms. 3) Performance optimization: Improve performance by rationally using indexes, partition tables and query caches.

SQL commands in MySQL can be divided into categories such as DDL, DML, DQL, DCL, etc., and are used to create, modify, delete databases and tables, insert, update, delete data, and perform complex query operations. 1. Basic usage includes CREATETABLE creation table, INSERTINTO insert data, and SELECT query data. 2. Advanced usage involves JOIN for table joins, subqueries and GROUPBY for data aggregation. 3. Common errors such as syntax errors, data type mismatch and permission problems can be debugged through syntax checking, data type conversion and permission management. 4. Performance optimization suggestions include using indexes, avoiding full table scanning, optimizing JOIN operations and using transactions to ensure data consistency.

InnoDB achieves atomicity through undolog, consistency and isolation through locking mechanism and MVCC, and persistence through redolog. 1) Atomicity: Use undolog to record the original data to ensure that the transaction can be rolled back. 2) Consistency: Ensure the data consistency through row-level locking and MVCC. 3) Isolation: Supports multiple isolation levels, and REPEATABLEREAD is used by default. 4) Persistence: Use redolog to record modifications to ensure that data is saved for a long time.

MySQL's position in databases and programming is very important. It is an open source relational database management system that is widely used in various application scenarios. 1) MySQL provides efficient data storage, organization and retrieval functions, supporting Web, mobile and enterprise-level systems. 2) It uses a client-server architecture, supports multiple storage engines and index optimization. 3) Basic usages include creating tables and inserting data, and advanced usages involve multi-table JOINs and complex queries. 4) Frequently asked questions such as SQL syntax errors and performance issues can be debugged through the EXPLAIN command and slow query log. 5) Performance optimization methods include rational use of indexes, optimized query and use of caches. Best practices include using transactions and PreparedStatemen

MySQL is suitable for small and large enterprises. 1) Small businesses can use MySQL for basic data management, such as storing customer information. 2) Large enterprises can use MySQL to process massive data and complex business logic to optimize query performance and transaction processing.

InnoDB effectively prevents phantom reading through Next-KeyLocking mechanism. 1) Next-KeyLocking combines row lock and gap lock to lock records and their gaps to prevent new records from being inserted. 2) In practical applications, by optimizing query and adjusting isolation levels, lock competition can be reduced and concurrency performance can be improved.


Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

ZendStudio 13.5.1 Mac
Powerful PHP integrated development environment

SublimeText3 Linux new version
SublimeText3 Linux latest version

VSCode Windows 64-bit Download
A free and powerful IDE editor launched by Microsoft

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Dreamweaver CS6
Visual web development tools