Import Scenarios FAQS
- Where
do I import scenarios in Oracle Data Integrator?
- Scenarios
can be imported through the Operator Navigator by selecting the Scenarios
panel, right-clicking, and choosing Import > Import Scenario.
- What
import types are available when importing scenarios?
- There
are several import types available, and you can choose the one
that fits your needs. For more details on these import types, refer to
the section Exporting and Importing.
- Can
I import schedules along with scenarios?
- Yes,
when importing scenarios, you can check the Import schedules
option to import any schedules that were exported along with the
scenarios.
- What
is the "File Import Directory"?
- The
File Import Directory is the location where the exported scenarios
are saved. You need to specify the directory from which to import the
scenario files.
- What
happens to the imported scenarios in the work repository?
- The
imported scenarios will be placed in the work repository and will
appear in the Scenarios tree of Operator Navigator.
- Do
imported scenarios get attached to existing objects?
- If
the work repository is a development repository, the
imported scenarios will automatically be attached to their
respective Package, Mapping, Procedure, or Variable.
- Can
I import multiple scenarios at once?
- Yes,
you can import one or more scenarios by selecting them from the
list of available files to import.
- What
happens if I don’t select the “Import schedules” option?
- If
you don’t select the Import schedules option, only the scenarios
will be imported, and their associated schedules will not be included.
- Is
there a specific repository required for importing scenarios?
- Scenarios
can be imported into any work repository, but if it is a development
repository, the imported scenarios will also be linked to their
relevant Packages, Mappings, Procedures, or Variables.
- What
is the next step after importing scenarios?
- After
importing, you can work with the scenarios directly in Operator
Navigator or make adjustments as needed for the development or
execution environment.
No comments:
Post a Comment