Sunday, October 2, 2011

FLat Text File as Data Source In OBIEE

When we have a requirement like the data is from a Flat File how to import the metadata in Repository , the following steps describes how to import the flat file .

1. create the sample text file like given format.

 no,name,city,gender
1,rawan,Lanka,male
2,Rama,india,male
3,sita,india,female

Save the above formated data in text file and save the text file in c:\test.txt


Click on Finish.

Next up, you should see the ODBC Text Setup screen, click on the Options tab to expand the window.

It should look like this:
Uncheck the Use Current Directory checkbox (default is usually c:\windows\system32):


Then select the Select Directory button and navigate to your root folder, or the place where you saved the test.txt file. You should see your file, greyed out, in the left hand pane.




Now, at the bottom of the window, uncheck Default (*.*) which should enable the Define Format button
S


See F1 and F2? Those are your columns. Let's name them something meaningful so we can easily reference them later.

In the Name box, it says F1, enter in USERNAME and click on Modify (the button to the right):

Do the same thing for the F2 column, name it PASSWORD.

It should end up looking like this:
Select OK and then select OK again in the ODBC Text Setup screen. You should now see your new data source in the System DSN window.
OBI EE Admin Tool
Now, we need to pull this new data source into the RPD. Open up your RPD, go to File --> Import --> from Database

You'll see this window, go ahead and select your new data source:
You'll be prompted with the Import window, expand the c:\ drive and then find your file
Select Import (at the bottom), wait for it to complete and then close the window. In your physical layer you should see a new "database" with the name "text_test" (or whatever you named your data source). Go ahead and expand that to see what you've got:

To verify, right click on the table "test.txt" and select View Data.











Saturday, October 1, 2011

Dac

DAC stand for Datawarehouse  Administration Console

DAC stands for Data Warehouse Application Console.  It is an essential component of Oracle BI application architecture.
DAC serves the following purposes:
1. DAC is a metadata driven administration and deployment tool for ETL and data warehouse objects
2. Used by warehouse developers and ETL Administrator

3. Application Configuration
  • Manages metadata-driven task dependencies and relationships
  • Allows creating custom ETL execution plans
  • Allows for dry-run development and testing
4. Execution
  • Enables parallel loading for high performance ETL
  • Facilitates in index management and database statistics collection
  • Automates change capture for Siebel OLTP
  • Assists in capturing deleted records
  • Fine grain restartability
5. Monitoring
  • Enables remote admin and monitoring
  • Provides runtime metadata validation checks
  • Provides in-context documentation

DAC Running modes

Orange ->  Indicates Running  State
Red -> Indicates not Running 
Green ___> Executing ETL


DAC Life Cycle:



  1. Step: step db connections
  2.  set up ETL  processes
  3. setup email receipients
 Desing : -> define application objects
             -> design execution plans

Execution: Define scheduling parameters
              ->Access runtime controls to restart or stop 

Monitor: Monitor runtime Execution of DWH

DAC Object Hierarchy