英文网站seo 谷歌,高端网站建设jm3q,石家庄建站网页模板,销售推广案例网站今天工具箱报错#xff1a; ORA-08103: object no longer exists 查了原因#xff0c;是有session在操作表#xff0c;比如插入#xff0c;更新等。而工具箱这个操作刚好在select表#xff0c;所以报错。-------下文是英文解释----- ORA-08103: object no longer exists错…
今天工具箱报错
ORA-08103: object no longer exists 查了原因是有session在操作表比如插入更新等。而工具箱这个操作刚好在select表所以报错。-------下文是英文解释----- ORA-08103: object no longer exists错误 后描述是其中一进程顺序执行truncateinsert动作而同时有另一进程对 同一表做select动作造成ora-8103 metalink资料 fact: Oracle Server - Enterprise Edition 8 symptom: Error performing a SELECT statement symptom: ORA-08103: object no longer exists symptom: Table is being truncated by other session symptom: Analyze table validate structure cascade returns no errors cause: This ORA-08103 occurs on the next block read after the truncate command. The LOCK TABLE IN EXCLUSIVE MODE does not prevent the table from being SELECTED from. Thus, when the query has started and while this query runs and the truncate occurs, this ORA-08103 may surface on the next block read. This is considered intended behavior. When a TRUNCATE occurs the DATAOBJ# in OBJ$ gets increased by one and thus may lead to this ORA-08103 object no longer exists fix: Possible solutions are: - Use DELETE instead of TRUNCATE - Use SELECT FOR UPDATE as this will try to lock the table 另ora-08103还有其他解释 Solution: ORA-8103: Object no longer exists When Insert Into External Table after Truncate With Storage Performed Applies to: Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 10.2.0.3 This problem can occur on any platform. Symptoms The following error can occur on an insert with SQL Loader into an external organized table after a truncate with storage option has been performed ORA-08103: object no longer exists
SQL insert /* PARALLEL(a, 8)*/ into iad_o_ast_new a select /* full(b) parallel(b,8)*/ * from iad_o_ast_ext b where rownum10000 ; into iad_o_ast_new a * ERROR at line 3: ORA-08103: object no longer exists . Changes The table was truncated with storage option before the insert . Cause The bitmap information is not correct after truncating with the storage option. The solutions update the bitmap information in the tablespace. Solution There are two known solutions at this time. 1. Add another datafile to increase the size of the tablespace for the insert. You will need to still use the correct truncate option next time you truncate the table. 2. Drop the table and recreate it. You will need to still use the correct truncate option next time you truncate the table. Do not truncate the table with the storage option.
Do not truncate the base table using: truncate ; truncate drop storage; Use the following instead: truncate reuse storage;
