Oracle BI EE (OBI) Repository and Configuration

Option A (True) is correct: OBI EE Server can host multiple repository files simultaneously. This allows flexibility in managing different BI applications and configurations on the same server instance.

Option B (False) is correct: The Oracle BI Cluster controller manages BI Server instances for load balancing and failover, not BI Presentation Services. Presentation Services have their own clustering mechanism. The statement incorrectly attributes control functionality.

Option C is correct: The analytics plugin uses SAWTCP protocol to communicate with BI Presentation Services. Options A (TCP) and B (UDP) are incorrect protocols. Option D (HTTP) is used for web browser communication, not plugin communication.

Option A (True) is correct: The HashUserHomeDirectories parameter must be set greater than 2 to support more than 4000 users accessing the OBI presentation catalog. This configuration increases hash map capacity for user directory caching.

Option A (True) is correct: A single connection pool can connect to multiple database schemas within the same database instance. This is useful when data is distributed across schemas but resides in the same database.

Option B (False) is correct: Oracle BI Repository does not support Oracle Long Objects (LOB, BLOB, CLOB). These large object data types cannot be directly mapped or used in the repository physical layer. Alternative approaches like storing references or using VARCHAR2 with size limits are needed.

Option B (False) is correct: The statement is false because OBI servers can create far more than 50 database connections. Connection limits are configurable and typically much higher (in the hundreds or thousands) depending on system resources and configuration settings.

The physical layer in OBI EE repository can use any schema structure - normalized, denormalized, or star schema. It's not required to be a star schema; that's a design choice for performance, not a requirement. The Business Model and Mapping (BMM) layer is where dimensional modeling happens.

The BMM (Business Model and Mapping) layer is specifically designed to present a dimensional view of data. It should always use star schema or dimensional data modeling patterns with fact tables, dimension tables, and hierarchies to enable business-friendly querying.

The physical layer should use simple joins based on primary-foreign key relationships. Complex joins (those using SQL expressions with OR, CASE, etc.) belong in the BMM layer where they can be reused and optimized. Physical joins should mirror actual database relationships.

A complex join in OBI EE is defined using a logical SQL expression in a WHERE clause (using AND, OR, CASE, etc.) rather than simple key-based relationships. It's not based on PK-FK, PK-CK, or CK-FK relationships alone - those describe simple foreign key joins.

In OBI EE hierarchy design, the Grand Total level typically contains exactly 1 element (the 'All' member). Statement B claims it's greater than 1, which is false. The other statements are generally true: all levels should have keys, and hierarchies should end at the same granularity level.

OBI EE supports various data types like BIT, TINYINT, and UNIT. LONGUNIT is not a valid data type in the system, making it the correct answer.

In Oracle Business Intelligence Enterprise Edition, the VARCHAR data type has a maximum length of 100 million characters (100,000,000). This is a platform-specific limit for string columns in the repository.

In the physical layer, a single database table can have multiple aliases with different primary key definitions. This is useful when the same table plays different roles in a dimensional model (e.g., a Date table used for both Order Date and Ship Date). Each alias can define its own primary key context.

A logical column in the BMM layer can map to multiple physical sources through logical table sources. This enables features like fragmentation (splitting data across sources), federation (combining sources), or handling time-variance. The logical column abstracts the underlying physical complexity.

In OBI EE architecture, a presentation catalog maps to exactly ONE business model. The relationship is 1:1 - each presentation catalog (presentation layer) exposes exactly one BMM layer. To present multiple business models, you create separate catalogs. This is a fundamental architectural constraint.

Oracle BI EE repository supports column-level security through the object permissions in the Administration Tool. You can control which users or groups can view specific columns in a table, implementing fine-grained access control at the column level within the security framework.

Static variables in OBI EE are defined once in the repository and don't require initialization blocks - their values are set at design-time. Dynamic variables, system session variables, and non-system session variables all require initialization blocks to populate their values at runtime.

A presentation catalog typically has a specific relationship with repositories and cannot connect to an unlimited number. The architecture limits connections for performance and governance reasons.