Error ORA-43853 When Using DataPump Export Or Import With DB_SECUREFILE=FORCE
(Doc ID 981846.1)
Last updated on FEBRUARY 03, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 11.1.0.7 and laterOracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
After setting parameter DB_SECUREFILE=FORCE, DataPump export or import under user SYSTEM fails with following errors:
DataPump Export:
ORA-31626: job does not exist
ORA-31633: unable to create master table "SYSTEM.SYS_EXPORT_SCHEMA_05"
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPV$FT", line 980
ORA-43853: SECUREFILE lobs cannot be used in non-ASSM tablespace "SYSTEM"
ORA-31633: unable to create master table "SYSTEM.SYS_EXPORT_SCHEMA_05"
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPV$FT", line 980
ORA-43853: SECUREFILE lobs cannot be used in non-ASSM tablespace "SYSTEM"
DataPump Import:
ORA-31626: job does not exist
ORA-31633: unable to create master table "SYSTEM.SYS_IMPORT_FULL_05"
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPV$FT", line 980
ORA-43853: SECUREFILE lobs cannot be used in non-ASSM tablespace "SYSTEM"
ORA-31633: unable to create master table "SYSTEM.SYS_IMPORT_FULL_05"
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPV$FT", line 980
ORA-43853: SECUREFILE lobs cannot be used in non-ASSM tablespace "SYSTEM"
Changes
Set parameter DB_SECUREFILE to FORCE.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |