technonotes-hackerREPOSITORY
- WORK
- MASTER
- Work is always attached to Master. one to one relation.
- Master to work is One to Many.
Agent --> Once the Job needs to be executed , this agent will go from the Designer to Scheduler by the agent , and agent will ask details of the job from the Repo ( get the META DATA ) and then give to the Operator.
STUDIO PANEL
- Designer
- Operator
- Security
- Topology
STUDIO
TOPOLOGY
Physical Architecture
- How the Work Repository gets created at first ?
- JDBC connection is made to connect the Master and Work Repo.
- 40+ Technologies are used to get the Meta Data / Schema Eg. Oracle DB , File , etc
- If I have Oracle DB , then in TOPOLOGY add the the DB - here always referred to DATASERVER.
- For Eg., SOURCE & TARGET SCOTT --> This is the Table --> which as DATA --> connect in the DATARERVER in TOPOGOLY ( Physical Architecture )
- Data Server always as replacement for Target or Source.
- Once loaded , create a PHYSICAL SCHEMA.
- In Physical Schema , what is the difference between Schema and Work Schema ? Is it like Individual Schema you are trying to connect is referred as SCHEMA ? where this is WORK SCHEMA stored ?
- Data Server is nothing but YOU ARE SAYING , you have been connected to one ORACLE DB.
- WORK TABLE PREFIX --> this will help to identify where it failed and we can check the error in DB by using the PREFIX.
- Why $ is specified in those ?
- New Physical Schema is created under the DATASERVER.
CONTEXT
Logical Architecture
- Click ORACLE , it will show only to create LOGICAL SCHEMA.
- MAP the Logical Schema with the Physical Schema which is created against the GLOBAL CONTEXT. This Physical Schema name is " Complete Name " give to the PHYSICAL, not the schema and work schema.
- Below SS will show the connection of Physical & Logical Relation.
Therefor , hereafter LOGICAL schema will be referred in the DESIGNER tab. NO NEED TO TOUCH PHYSICAL SCHEMA.
Questions
- whether all PROD , DEV & UAT will have only one Master Repo?
- W1 To M1 But W1 To M2 is not possible.
Important Commands
- select * from v$instance; --> This will give the DB version.
