My Oracle Support Banner

DBMS_METADATA.GET_DDL Output For Tablespace Inaccurate After Patch 10177856 Applied (Doc ID 1404474.1)

Last updated on FEBRUARY 28, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.2 to 11.2.0.3 [Release 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

DBMS_METADATA.GET_DDL output is corrupted when getting tablespace ddl.

For example:

SQL> set long 10000

SQL> SELECT DBMS_METADATA.get_ddl ('TABLESPACE', 'PSHARE') FROM DUAL

DBMS_METADATA.GET_DDL('TABLESPACE','PSHARE')
--------------------------------------------------------------------------------

CREATE TABLESPACE "PSHARE" DATAFILE
'' SIZE 104857600
AUTOEXTEND ON NEXT 104857600 MAXSIZE 10240M,
'' SIZE 104857600
AUTOEXTEND ON NEXT 104857600 MAXSIZE 10240M,
'/export/oradata/DB10TEST/data01/pshare_01.dbf' SIZE 104857600
AUTOEXTEND ON NEXT 104857600 MAXSIZE 10240M
LOGGING ONLINE PERMANENT BLOCKSIZE 8192
EXTENT MANAGEMENT LOCAL AUTOALLOCATE DEFAULT NOCOMPRESS SEGMENT SPACE MANAGEM
ENT AUTO



NOTE:
There 3 AUTOEXTEND clauses listed for one datafile

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
Cause
Solution
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.