Loading ...
Sorry, an error occurred while loading the content.
 

Re: check for source availability:

Expand Messages
  • petplacething
    ... In your installation setup in items 5 and 4 following, you said check for source availability of all required sources and check for access privileges on
    Message 1 of 10 , May 5, 2005
      --- In OracleWarehouseBuilder@yahoogroups.com, "petplacething"
      <petplacething@y...> wrote:
      > Hello,

      In your installation setup in items 5 and 4 following, you
      said "check for source availability of all required sources" and
      check for "access privileges on their respective sources" where and
      how exactly do you do these?
      Thanks,

      >
      >
      >
      > --- In OracleWarehouseBuilder@yahoogroups.com, CRS
      > <shankarappa_cr@y...> wrote:
      > >
      > > --- CRS <shankarappa_cr@y...> wrote:
      > >
      > > > HI....ALL....
      > > > THIS IS VERY USEFULL FOR OWB BEGINNERS.....ENJOY....
      > > >
      > > > INSTALLING AND SETUP:
      > > > 1. Install OWB Client & Runtime components
      > > > 2. Create Design-Repository (eg: design_user)
      > > > 3. Create Runtime-Repository (eg: runtime_owner)
      > > > 4. Create Connect users for this runtime repository
      > > > (Eg: connect_user)
      > > > 5. Check for source availability of all required
      > > > sources - OLTP Schemas, Flatfiles...
      > > > 4. Create all the target Schemas through "Runtime
      > > > assistant" (eg: wh_staging, wh_ent_model,
      > > > wh_Target).
      > > > cHECK FOR ACCESS PRIVILEGES ON THEIR RESPECTIVE
      > > > SOURCES... (wh_staging should have 'select' access
      > > > on
      > > > source schemas (eg: vintners_ltd and vintners_vine);
      > > > wh_ent_model should have 'select' access on
      > > > wh_staging
      > > > and so on...
      > > >
      > > > DESIGN PHASE: IN OWB DESIGN CLIENT: Designing
      > > > Logical
      > > > Warehousing options
      > > > 1. create source module with a location attached.
      > > > - create metadata database link and import source
      > > > table's metadata
      > > > 2. Create Flatfile modules, one per source location
      > > > (if any)
      > > > - Sample the files required from that path
      > > > 3. Create Target Module (say, staging)
      > > > - Create the tables required for holding staging
      > > > data
      > > > - Create any
      > > > transformations(functions/procedures/packages
      > > > created
      > > > by user) as required for manipulating the data
      > > > - create the mappings to design data flow from
      > > > source module to target module(staging, in this
      > > > case)
      > > > Note: When including tables from multiple modules
      > > > (source and staging), OWB automatically creates a
      > > > connector between their respective locations. Verify
      > > > this.
      > > > -- validate the mapping to check for completeness
      > > > -- Set operator properties of TARGET object (table
      > > > or
      > > > dimension):
      > > > - 'Loading Type (like INSERT, TRUNCATE/INSERT
      > > > etc)
      > > > ; Staging tables recommended to have TRUNCATE/INSERT
      > > > and other will have UPDATE/INSERT
      > > > - 'Match by Constraints' for updation options
      > > > -- Configure the mapping to include any code
      > > > specific
      > > > settings (IF the map includes a flatfile, need to
      > > > specify Source Data File.)
      > > > -- Revalidate after configuring to check for
      > > > incorrect options or incompatibilities
      > > > -- generate the mapping for any code checking if
      > > > required.
      > > >
      > > > Note: The steps defined here are top-down approach.
      > > > It
      > > > creates metadata for all required objects before
      > > > proceeding to design the mapping.
      > > > We can start creating a mapping and create required
      > > > objects(like tables) within the mapping itself and
      > > > do
      > > > a "Reconcile Outbound" from there to transfer the
      > > > metadata details of the objects from the mapping to
      > > > the design repository.
      > > > When you follow the second approach, after doing a
      > > > 'reconcile outbound' from the mapping, check if you
      > > > have the objects appropriate grouping within the
      > > > project (say tables available under "Tables" group)
      > > >
      > > > Create other target modules as required- eg:
      > > > Enterprise warehouse and Datamart:
      > > > Enterprise warehouse module creation is similar to
      > > > Staging module creation. Mappings define data flow
      > > > from staging module to warehouse module.
      > > >
      > > > Datamart target module:
      > > > - Define Dimensions
      > > > - levels
      > > > - level attributes
      > > > - hierarchies
      > > > - Define Cubes
      > > > - Attach the foreign keys refering to Primary key
      > > > of
      > > > each dimension
      > > > - Define measures to be stored in the cube.
      > > > - Define mappings to load data from
      > > > warehouse(source
      > > > designated for the datamart) to the datamart
      > > > dimensions
      > > > - Define mapping to load data into cubes
      > > >
      > > > Once all designing is done, create a "Runtime
      > > > Repository Connection" specifying the Runtime
      > > > repository(eg: runtime_owner) and access user (eg:
      > > > connect_1)
      > > >
      > > > IMPLEMENTATION PHASE: IN DEPLOYMENT MANAGER:
      > > > Transiting from Logical to Physical:
      > > > 1. Login to Deployment manager using the "Runtime
      > > > Repository Connection"
      > > > 2. Register all the Locations
      > > > 3. Generate & Deploy all the connectors
      > > > 4. Generate & Deploy all the objects (tables,
      > > > sequences, dimensions, cubes, views etc...) -- This
      > > > step creates all the
      > > > database objects
      > > > 5. Generate & Deploy all the transformations (custom
      > > > functions/procedures/packages) -- This step creates
      > > > and compiles all the
      > > > stored procedure codes to be called from the
      > > > mappings
      > > > 6. Generate & Deploy all mappings -- Each mapping
      > > > translates to a pls package which is created and
      > > > compiled in the target
      > > > when generate/deploy operation is performed.
      > > > 7. Execute the mappings in this order: -- Executing
      > > > the created stored procedures.
      > > > - Staging module's mappings
      > > > - Warehouse module's mappings
      > > > - Data mart Dimension's mappings
      > > > - Datamart Cube's mappings
      > > >
      > > > TESTING PHASE: Check if the rows are loaded properly
      > > > without errors
      > >
      > > REGARDS.....
      > > SHANKARAPPA.....
      > >
      > >
      > > >
      > > >
      > > > --- petplacething <petplacething@y...> wrote:
      > > > > Thanks, basically that is the thing. How do I
      > > > > import the tables you
      > > > > are talking about? The tables and dimensions were
      > > > > created in a user
      > > > > tablespace in oracle. So how do I get them to the
      > > > > project
      > > > > environment?
      > > > >
      > > > > Thanks,
      > > > >
      > > > > --- In OracleWarehouseBuilder@yahoogroups.com,
      > > > > Sudipta Chatterjee
      > > > > <sudipta_cht@y...> wrote:
      > > > > > Hi,
      > > > > > I think you can begin by importing the tables
      > > > and
      > > > > MVs
      > > > > > metadata in your project and go ahead and create
      > > > > > mappings, process flows, etc.
      > > > > >
      > > > > > Sudipta
      > > > > >
      > > > > >
      > > > > > --- petplacething <petplacething@y...> wrote:
      > > > > > ---------------------------------
      > > > > > Hi all,
      > > > > > I have followed the cookbook to the point that I
      > > > > am in
      > > > > > MY PROJECT
      > > > > > window box. Here is where I get confused...
      > > > > >
      > > > > > I have my dimensions in Oracle 9i
      > > > > > I have the materialized views too created with
      > > > > Oracle
      > > > > > Enterprise
      > > > > > Manager.
      > > > > >
      > > > > > My question is...
      > > > > >
      > > > > > How do I begin realistically design the data
      > > > mart?
      > > > >
      > > > > > Starting from the
      > > > > > MY PROJECT in Oracle Warehouse Builder. I want
      > > > > simple
      > > > > > procedure for a
      > > > > > beginner please.
      > > > > >
      > > > > > Thank you,
      > > > > >
      > > > > >
      > > > > >
      > > > > >
      > > > > >
      > > > > > Join
      > > > > > http://www.smartgroups.com/groups/Datawarehouse
      > > > > >
      > > > > >
      > > > > >
      > > > > > ---------------------------------
      > > > > > Yahoo! Groups Links
      > > > > >
      > > > > > To visit your group on the web, go to:
      > > > > >
      > > > >
      > > >
      > > === message truncated ===
      > >
      > >
      > >
      > >
      > > __________________________________
      > > Do you Yahoo!?
      > > Yahoo! Small Business - Try our new resources site!
      > > http://smallbusiness.yahoo.com/resources/
    Your message has been successfully submitted and would be delivered to recipients shortly.