DataPump 10.2 is truncating lengthy views and triggers
(Doc ID 976627.1)
Last updated on AUGUST 01, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.4 to 10.2.0.4 [Release 10.2]Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
HP OpenVMS Alpha
Symptoms
===================
-- Problem Statement:
When using DataPump to export from a 10.2 database and import into a 10.2 database, the DDL for lengthy views and triggers is truncated. The source database has a block size of 2048 (db_block_size = 2048). The target database has a block size of 8192.
Example:
DBMS_METADATA.GET_DDL('VIEW','TABXX','<USERNAME>')
------------------------------------------------------------------------------
CREATE OR REPLACE FORCE VIEW "<USERNAME>"."TABXX" ("TABXX_SESSION_NUMBER",
"TABXX_USER", "TABXX_END_DATE","TABXX_ZZZ_DOC_CODE",
"TABXX_ACTIVITY_DATE", "TABXX_ZZZ_DATE", "TABXX_TRAN_NUMBER", "TABXX_NUMBER", "TABXXX_DETAIL_CODE", "TABXX_DESC", "TABXX_DCAT_CODE", "TABXX_AMOUNT", "TABXXX_NAME", "TABXX_ID", "TABXX_SRCE") AS
Using the classic Export and Import on the same source and target databases works correctly, with no truncation of lengthy views or triggers.
The same triggers and views are extracted correctly with DataPump if the source database has a larger block size such as 8192.
The same triggers and views are extracted correctly with the DBMS_METADATA package if the source database has a larger block size such as 8192.
Changes
None.
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 |