ODI12c Regenerating and Generating Groups of Scenarios FAQS

1. What does regenerating a scenario mean?

·        Replaces an existing scenario with the same name and version

·        Updates the scenario to reflect the current state of the source object

·        Preserves schedules attached to the scenario

2. How do you regenerate a scenario?

·        Select the scenario in Projects accordion

·        Right-click → Regenerate… → Click OK

Caution:

·        Regeneration cannot be undone. For critical scenarios, consider creating a new version instead.

3. What is generating a group of scenarios?

·        Compiles multiple objects (Packages, Mappings, Procedures, Variables) under a Project or Folder

·        Produces scenarios for all selected objects in one operation

4. How do you generate a group of scenarios?

·        Select the Project or Folder

·        Right-click → Generate All Scenarios…

·        In the Scenario Generation dialog, choose Generation Mode:

Generation Modes:

o   Replace → Overwrites last scenario version; deletes sessions, scenario reports, schedules; creates version 001 if no scenario exists

o   Re-generate → Overwrites last scenario version; preserves schedules, sessions, reports; does not create scenario if none exists

o   Creation → Creates a new scenario version automatically; version number increments if numeric, else set to current date; creates version 001 if no scenario exists

5. How are scenario names and versions determined?

·        Names follow the Scenario Naming Convention (Tools → Preferences → ODI → System → Scenarios)

·        Version numbers increment automatically if numeric; otherwise, current date is used

6. Can you filter which objects are included in group generation?

·        Objects to Generate → Select types of objects (Package, Mapping, Procedure, Variable)

·        Marker Filter → Optional filtering based on marker groups

7. How are variables handled in group scenario generation?

·        Scenario Variables dialog allows setting which variables become parameters:

o   Use All → All variables are parameters

o   Use Selected → Only selected variables are parameters

8. Why is group scenario generation useful?

·        Efficiently generates scenarios for multiple objects at once

·        Ensures consistent versioning and parameterization

·        Preserves schedules and execution information if using Re-generate mode

 

ODI12c Generating Scenarios FAQS

1. What does generating a scenario mean?

·        Compiles the code of a component (Package, Mapping, Procedure, or Variable) for deployment and execution in production

·        Produces a frozen, versioned executable

2. How do you generate a scenario for a component?

·        Open Designer Navigator

·        Double-click the component (Package, Mapping, Procedure, Variable) → opens the Object Editor

·        Go to the Scenarios tab → Click Generate Scenario

3. What information is required when generating a scenario?

·        Name → Uppercased automatically; special characters replaced with underscores

·        Version → Auto-incremented if the latest version is numeric; else set to current date

4. What happens if no previous scenario exists for the component?

·        The first version of the scenario is automatically created

·        Name follows the Scenario Naming Convention (set in ODI Preferences → Tools → ODI → System → Scenarios)

5. How are variables handled when generating a scenario?

·        The Scenario Variables dialog allows defining which variables are considered as parameters:

o   Use All → All variables become parameters

o   Use Selected → Only selected variables become parameters

o   None → No variables used as parameters

6. Where does the generated scenario appear?

·        On the Scenarios tab of the component

·        Under the Scenarios node of the source object in the project

7. Why is scenario generation important?

·        Creates a production-ready, versioned executable

·        Ensures stable, reproducible behavior regardless of future changes to the component

·        Allows parameterization via scenario variables for flexible execution