Case 3: DB_SECUREFILE = FORCE
The option FORCE for the DB_SECUREFILE parameter forces all LOB columns to be
created as SecureFiles only, irrespective of file type specification. Now since
SecureFiles can reside on ASSM tablespace only, non ASSM tablespace cannot be
specified for LOB creation in any way. For non ASSM tablespace, system raises
exception. Check this in the below illustration.
Sample Code
----Set the DB_SECUREFILE parameter as ALWAYS----
SQL> ALTER SYSTEM SET DB_SECUREFILE=FORCE;
System altered.
----Create table with SecureFile column on ASSM tablespace----
SQL> CREATE TABLE FORCE_SECUREFILE_1
2 (DOC BLOB)
3 LOB(DOC) STORE AS SECUREFILE
4 TABLESPACE USERS
5 /
TABLE created.
----Create table with SecureFile column on non ASSM tablespace----
SQL> CREATE TABLE FORCE_SECUREFILE_2
2 (DOC BLOB)
3 LOB(DOC) STORE AS SECUREFILE
4 TABLESPACE SYSTEM
5 /
CREATE TABLE FORCE_SECUREFILE_2
*
ERROR at line 1:
ORA-43853: SECUREFILE lobs cannot be used IN non-ASSM tablespace "SYSTEM"
----Create table with BasicFile column on ASSM tablespace----
SQL> CREATE TABLE FORCE_BASICFILE_1
2 (DOC BLOB)
3 LOB(DOC) STORE AS BASICFILE
4 TABLESPACE USERS
5 /
TABLE created.
----Create table with BasicFile column on non ASSM tablespace----
SQL> CREATE TABLE FORCE_BASICFILE_2
2 (DOC BLOB)
3 LOB(DOC) STORE AS BASICFILE
4 TABLESPACE SYSTEM
5 /
CREATE TABLE FORCE_BASICFILE_2
*
ERROR at line 1:
ORA-43853: SECUREFILE lobs cannot be used IN non-ASSM tablespace "SYSTEM"
Copyright exforsys.com
Now, check whether the SecureFile feature has been enabled for the above
tables or not.

Observe that SecureFile has been enabled for both the tables, which are
created on ASSM tablespace. For the rest, Oracle strictly prevents the creation
of BasicFile columns.
Case 4: DB_SECUREFILE = NEVER
This mode works as reverse of ALWAYS and FORCE mode. It prevents the creation
of SecureFile LOBs and all of them shall be treated as BasicFiles only. The
SECUREFILE keyword is a passive or obsolete specification under this mode.
Oracle doesnt minds even specifying a non ASSM tablespace with SecureFile LOB
column.
Sample Code
----Set the DB_SECUREFILE parameter as ALWAYS----
SQL> ALTER SYSTEM SET DB_SECUREFILE=NEVER;
System altered.
----Create table with SecureFile column on ASSM tablespace----
SQL> CREATE TABLE NEVER_SECUREFILE_1
2 (DOC BLOB)
3 LOB(DOC) STORE AS SECUREFILE
4 TABLESPACE USERS
5 /
TABLE created.
----Create table with SecureFile column on non ASSM tablespace----
SQL> CREATE TABLE NEVER_SECUREFILE_2
2 (DOC BLOB)
3 LOB(DOC) STORE AS SECUREFILE
4 TABLESPACE SYSTEM
5 /
TABLE created.
----Create table with BasicFile column on ASSM tablespace----
SQL> CREATE TABLE NEVER_BASICFILE_1
2 (DOC BLOB)
3 LOB(DOC) STORE AS BASICFILE
4 TABLESPACE USERS
5 /
TABLE created.
----Create table with BasicFile column on non ASSM tablespace----
SQL> CREATE TABLE NEVER_BASICFILE_2
2 (DOC BLOB)
3 LOB(DOC) STORE AS BASICFILE
4 TABLESPACE SYSTEM
5 /
TABLE created.
Copyright exforsys.com
Checking the results in the USER_LOBS view, all the above tables have non
SecureFile column.

This tutorial is part of a Oracle 11g Tutorial tutorial series. Read it from the beginning and learn yourself.
H I D E