My Oracle Support Banner

DataPump Leagacy Mode: TOUSER Creates A Schema User With An Extra Space (Doc ID 2133590.1)

Last updated on MARCH 27, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.1 to 11.2.0.1 [Release 11.2]
Information in this document applies to any platform.

Goal

NOTE: The document content below, the user information and data used represents fictitious data from the Oracle sample schema(s) or Public Documentation delivered with an Oracle database product. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.

When using TOUSER parameter in datapump legacy mode an unnecessary white space is appended to the schema name as shown in the example below:

> impdp super/<PASSWORD> fromuser=testuser touser=testuser directory=dpdir dumpfile=testuser.dmp

Import: Release 11.2.0.1.0 - Production on Wed Mar 3 14:56:06 2010

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

Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Legacy Mode Active due to the following parameters:
Legacy Mode Parameter: "file=testuser.dmp" Location: Command Line, Replaced with: "dumpfile=testuser.dmp"
Legacy Mode Parameter: "fromuser=testuser" Location: Command Line, Replaced with: "remap_schema"
Legacy Mode Parameter: "log=testuser_imp.log" Location: Command Line, Replaced with: "logfile=testuser_imp.log"
Master table "SUPER"."SYS_IMPORT_FULL_01" successfully loaded/unloaded
Starting "SUPER"."SYS_IMPORT_FULL_01": SUPER/********
remap_schema=testuser:testuser directory=dpdir dumpfile=testuser.dmp logfile=testuser_imp.log
Processing object type SCHEMA_EXPORT/USER
Processing object type SCHEMA_EXPORT/SYSTEM_GRANT
Processing object type SCHEMA_EXPORT/ROLE_GRANT
Processing object type SCHEMA_EXPORT/DEFAULT_ROLE
Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
Processing object type SCHEMA_EXPORT/TABLE/TABLE
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
. . imported "testuser "."TAB1" 5.007 KB 1 rows <=== a spurious white space appended to the schemaname

Job "SUPER"."SYS_IMPORT_FULL_01" successfully completed at 14:56:12

Why a database user of spurious schema name is created ?

Solution

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
Goal
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.