An alias table is a physical table with the type of alias, it is reference to a logical table source, and mainly it is useful

for reuse existing table more than once in your physical layer, to set up multiple alias tables, each with different keys, name, or joins. Alias tables are critical in the process of converting er schemas to dimensional schemas. 1. If you delete a column in the source table the column is automatically removed from the alias table. 2. In online mode if a source table or column is checked out all its alias tables and columns will be checked out, if an alias table or column is checked out, its source table and column will be checked out. 3. The deletion fails if an alias exists on the physical table. 4. It is generally safe to change a non null able value to a null able value in a physical column. 5. Specify a primary key for physical tables in the physical table properties click the keys tab specify keys. 6. set up unbalanced hierarchies in the physical layer by changing the hierarchy type 7. A catalog contains the entire schema for a database object; a schema contains only the metadata information for a particular user or application. 8. You would initialize a session variable named client, for example that could be used to set the name for the catalog object dynamically when a user signs on to the oracle bi server. 9. When you import keys in a physical schema, the primary key-foreign key joins are automatically defined. 10. Multi database joins will be significantly slower than joins between tables withing the same database. 11. Fragmented data is data from a single domain that is split between multiple tables, for example a database might store sales data for customers with last names beginning with the letter a through m in one table and last names from n through z in another table, you need to define all of the join conditions between each fragment and all the tables it relates to. 12. A primary key and foreign key relationship defines a one to many relationship between two tables, a foreign key is column or a set of columns in one table that references the primary key columns in another table. 13. complex joins in physical later of the repository , complex joins are joins over non foreign key and primary key columns you can specify expressions and the specific columns on which to create the join , complex join in BMM layer expressions are not necessary. 14. An opaque view is a physical layer table that consists of a select statement., you deploy an opaque view in the physical database using the deploy views utility. 15. The business model and mapping layer of the administration tool defines the business or logical model of the data and specifies the mapping between the business model and the physical layer schemas. 16. When you work in a repository in offline mode remember to save your repository from time to time. You can save a repository in offline mode even though the business models may be inconsistent.

17. Logical tables exist in the business model and mapping layer, the logical schema defined in each business model needs to contain at least two logical tables sources, and configure the logical keys (primary and foreign) 18. After creating tables in the business model and mapping layer , you specify a primary key for each table, logical dimension tables must have a logical primary key ,logical keys can be composed of one or more logical columns. 19. Logical keys are optional for logical fact tables, do no specify logical keys for logical fact tables. 20. Default aggregation rule is count distinct. 21. Level based measures allow a single query to return data at multiple levels of aggregation. 22. NQSConfig.INI file tells allows the oracle bi server t load the repository into memory upon startup, if errors occur in the file you might not be able to restart the server you can review the log messages in the log nqserver.log at the oraclebi\server\log, 23. start in nqsconfig.ini file is logical name is the name end-users have to configure when configuring a dsn in the oracle bi odbc setup wizard. 24.