Application team was running some upgrade and during that process, they got the below error. ORA-20101:

ERROR at line 1: ORA-20101: PGIDX is not a ASSM (Automatic Segment Space Management) tablespace,
cannot upgrade BLOB to securefile ORA-06512: at line 28, exiting


NOTE - > This solution contains steps, which may block transaction on the table during this activity and indexes might become unusable. For production please take necessary action accordingly.

From the error , it seems PGIDX is not ASSM. Lets check the status.

select tablespace_name,segment_space_management from dba_tablespaces where tablespace_name='PGIDX';

---------------            -----------
PGIDX                       MANUAL

So first problem is the tablespace is not ASSM,And it is not possible to convert it to ASSM.

So what we can do is find the objects for which we are facing the error.
In our case we are getting error for BLOB. So we searched for the LOB segments in this tablespace.

  1*  select owner,table_name,column_name,segment_name from dba_lobs where tablespace_name='PGIDX'
SQL> /

OWNER        TABLE_NAME                         COLUMN_NAME     SEGMENT_NAME
------------ ---------------------------------- --------------- ---------------------------------------------

So we have planned to move these objects to a new tablespace( Where ASSM is enabled).

create tablespace PGLOB datafile '/u01/data/plob.dbf' size 5g autoextend on;

Tablespace created. 

select tablespace_name,segment_space_management from dba_tablespaces where tablespace_name='PGLOB';

---------------            -----------
PGLOB                        AUTO

--- Move the LOB segments to a new tablespace 

SQL> alter table PGPLI.GST_PREVVE_CLOCK move lob ( CILEDATA) store as GST_PREVVE_CLOCK_LOB_SEG ( tablespace PGLOB);

Table altered.

SQL>  alter table PGPLI.GST_PREVVE_VERSIONS move lob ( CILEDATA) store as GST_PREVVE_VERSIONS_LOB_SEG  ( tablespace PGLOB);

Table altered.

SQL> alter table PGPLI.GST_DEQ_FENTEXTS move lob ( BONTEXT) store as GST_DEQ_FENTEXTS_LOB_SEG ( tablespace PGLOB);

Table altered.

Now if any indexes on these tablespace are unusable , then rebuild them.

select index_name,status,table_name from dba_indexes where table_name in ('GST_PREVVE_CLOCK','GST_PREVVE_VERSIONS','GST_DEQ_FENTEXTS') and status='UNUSABLE';

-- IF any index reports unusable. then rebuild them using 

alter index pgpli.pg_idx rebuild

Now application team ran the upgrade script and this error was not reported.


Related Topics

ORA-30034: Undo tablespace cannot be specified as temporary tablespace
TNS-01106: Listener using listener name has already been started
ORA-32773: operation not supported for smallfile tablespace
ORA-32771: cannot add file to bigfile tablespace
ORA-02304: invalid object identifier literal while import with CREATE TYPE OID
ORA-01536: space quota exceeded for tablespace
ORA-20101: TABLESPACE is not a ASSM (Automatic Segment Space Management) tablespace
TNS-12542: TNS:address already in use
ORA-32774: more than one file was specified for bigfile tablespace
ORA-16855: transport lag has exceeded specified threshold

You May Also Like

_use_adaptive_log_file_sync parameter in oracle
Deinstall Management Agents Oracle 12c cloud control
Unified audit trail in Oracle 12c
ENABLE_PARALLEL_DML hint in oracle 12c
Find user commits per minute in oracle database
How to recreate MGMT database in ORACLE 12C GRID
Open wallet automatically after starting the database
Add database as target oracle 12c cloud control
How to generate AWR report in RAC
Shell script to report failed login attempt in oracle

From This Website

How to use oratop tool for oracle database monitoring
LOG_CHECKPOINTS_TO_ALERT parameter in oracle
How to run expdp in pluggable database(PDB)
How to deinstall/cleanup standalone grid infrastructure
How to generate AWR report in RAC
How to add a tempfile in primary database in dataguard
TNS-01106: Listener using listener name has already been started
COMPRESSION in datapump oracle
How to flashback a Pluggable database ( PDB) in oracle 12.2