My Oracle Support Banner

How to resolve UDI-00014: invalid value for parameter, 'transform' errors with Datapump Import (Doc ID 1597389.1)

Last updated on FEBRUARY 13, 2020

Applies to:

Oracle Database - Enterprise Edition - Version and later
Oracle Database Cloud Schema 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
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.

NOTE: In the images and/or the document content below, the user information and data used represents fictitious data .Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.


This note helps you in resolving UDI-00014: invalid value for parameter, 'transform' errors when using DataPump Import's query based import.

The import log can report the following errors:

$ impdp test/<password> directory=mydir dumpfile=vk.dmp transform=table_compression_clause:"COMPRESS BASIC" remap_schema=scott:testing

Import: Release - Production on Wed Aug 28 10:03:53 2013

Copyright (c) 1982, 2013, Oracle and/or its affiliates.  All rights reserved.

Connected to: Oracle Database 12c Enterprise Edition Release - 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options
UDI-00014: invalid value for parameter, 'transform'

The impdp transform clause on 12c does not seem to be working correctly. This version of the clause works:

$ impdp test/<password> directory=mydir dumpfile=vk.dmp transform=table_compression_clause:"compress" remap_schema=scott:testing

which would default to compress basic. However, this does not work:

$ impdp test/<password> directory=mydir dumpfile=vk.dmp transform=table_compression_clause:"compress basic" remap_schema=scott:testing

The documentation seems to infer that compress basic would be the correct clause (and compress advanced) as seen here (from 12c utilities guide):

TABLE_COMPRESSION_CLAUSE:[NONE | compression_clause]

If NONE is specified, the table compression clause is omitted (and the table gets the default compression for the tablespace). Otherwise the value is a valid table compression clause (for example, NOCOMPRESS, COMPRESS BASIC, and so on). Tables are created with the specified compression. See Oracle Database SQL Language Reference for information about valid table compression syntax.

If the table compression clause is more than one word, it must be contained in single or double quotation marks.

Specifying this transform changes the type of compression for all tables in the job, including tables that provide storage for materialized views.  


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

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