DataPump Export and Import With Parameter METADATA_ONLY Do Not Take Scheduler Program Arguments
(Doc ID 459405.1)
Last updated on MARCH 11, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.1 to 11.2.0.3 [Release 10.2 to 11.2]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.
Symptoms
You defined a program (or job) with arguments using the package DBMS_SCHEDULER. Then, you either:
- exported the user using DataPump export (expdp) with parameter CONTENT=METADATA_ONLY and imported (impdp) the dump into a new schema, or:
- exported the user using DataPump export (expdp) with parameter CONTENT=ALL and imported (impdp) the dump with parameter CONTENT=METADATA_ONLY (or EXCLUDE=TABLE_DATA)
The fresh imported schema doesn't contain the program/job arguments anylonger.
Steps to reproduce the problem:
1. Create the objects into database
Changes
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 |