<img height="1" width="1" style="display:none;" alt="" src="https://px.ads.linkedin.com/collect/?pid=8366258&amp;fmt=gif">
Skip to content

Blog

    Grid View active list View inactive

    by Veera Reddy Ramidi

    This blog introduces and explains the detailed step by step process for executing the Domain Load to Business...

    Learn More Right Arrow

    by Sharath Venkataranga

    The most common question faced by any ETL developer or a Data Warehouse project implementer is always related to...

    Learn More Right Arrow

    The BI Apps from Oracle present customers with a nice head start to getting their BI environment up and running. But for many customers,...

    Learn More Right Arrow

    by Kurt Wolff

    When you duplicate a table, you create a new physical table with a new name. If this table is involved in a query, the SQL...

    Learn More Right Arrow

    What is Business Intelligence? Listen to a brief history of BI, where we've been, where we are now, and where we are going...

    Learn More Right Arrow
    Grid View inactive list View active

    by Veera Reddy Ramidi

    This blog introduces and explains the detailed step by step process for executing the Domain Load to Business Analytics Warehouse. Here, we are illustrating for the Student information Analytics data using the new OBIA 11g which is supported only for PeopleSoft 9.0 Campus Solutions. This blog can be used similarly for any other Analytics using OBIA 11g.

    by Sharath Venkataranga

    The most common question faced by any ETL developer or a Data Warehouse project implementer is always related to performance. Whatever the tool may be, and however fast the job may be running, the end user will always desire something which is a little faster and quicker.

    The BI Apps from Oracle present customers with a nice head start to getting their BI environment up and running. But for many customers, their user community demands lighting-fast speeds while running dashboards, reports and ad-hoc queries. 

    by Kurt Wolff

    When you duplicate a table, you create a new physical table with a new name. If this table is involved in a query, the SQL FROM clause will list this table. If the table does not exist in the database, then an error will occur.

    Creating an alias creates a copy of the metadata table object that will be referenced in SQL with a new alias name. The alias name in SQL, as it is for all tables, will be derived its metadata ID.

    To see the table IDs in OBIEE metadata, use the Oracle BI Query Repository utility. Here are some physical tables (and aliases) in a repository that I’ve created. It’s the last five digits of the ID that will be used to create the table aliases in SQL.

    What is Business Intelligence? Listen to a brief history of BI, where we've been, where we are now, and where we are going...

    kpi-top-up-button