Académique Documents
Professionnel Documents
Culture Documents
Transition –
Known Issues
Collection of known issues and their resolution
Purpose of document
Solution Delete all database links and recreate using Data Pump export/import jobs. Templates should be
available in the WORK directory.
Detail The required privilege on the referenced table may be granted later in the migration sequence or not
at all if it had been removed on the source database at some time after the privilege had been
granted.
Environment Any
Solution Add privilege to grantor and rerun the failing SQL script (grant_priv_objects) manually (not from within
ATS). The missing privilege is:
Comment While users are granted SELECT ANY TABLE privilege in the preparation phase (cr_pmig) they are
missing the WITH ADMIN OPTION part which is required to prevent ORA-01720.
Solution Add option “exclude=statistics” to the import parameter file and restart the import. Check the undo
shell script is using “/ as sysdba”.
After the import is finished collect statistics for the schema using
exec dbms_stats.gather_schema_stats('<schema>',DBMS_STATS.AUTO_SAMPLE_SIZE);
Environment Any
Solution Remove parameter “exclude=index” from the par-file and rerun the failed import job.
Comment The schema import is excluding all indexes which are imported in the next step (index job). As the
ALTER TABLE ADD CONSTRAINT is referring to an index (USING INDEX) which does not yet exist it
will fail. You need to create the index first before you can create the constraint.
Environment Any
Comment For unknown reason some databases require additional select privilege on sys.user$ while others do
not. As of now ATS create the migration user with a limited set of privileges only. Need to check with
development.
Environment Any
Solution Drop extended statistics, create the index, create extended statistics and check for additional
commands in the job which are not executed due to this error.
Comment This example show how to implement the solution based on the index details above:
Environment Any
Solution For ctas and ctaslob jobs you may ignore this error as it is the last command in the job. For
imp_dp_tab jobs you must run the missing import step manually or change the job to ignore the error
and retry using the Scheduler. Otherwise the table will be created but no data imported.
Worldwide Headquarters
500 Oracle Parkway, Redwood Shores, CA 94065 USA
Worldwide Inquiries
TELE + 1.650.506.7000 + 1.800.ORACLE1
FAX + 1.650.506.7200
oracle.com
CONNECT W ITH US
Call +1.800.ORACLE1 or visit oracle.com. Outside North America, find your local office at oracle.com/contact.
Copyright © 2019, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the contents hereof are
subject to change without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed
orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any
liability with respect to this document, and no contractual obligations are formed either directly or indirectly by this document. This document may not be
reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under licens e and are trademarks or
registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks
of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. 0919
September 2019
Author: Wolfgang Pungartnik