Group items tagged

OBIEE 11G configuration’s Maximum Limits

Be careful when you are setting the Cache attribute values. For implementations under significant stress increase this value to 1000 or a higher value as mentioned below. The main factor that affects its size is the memory consumption. Maximum range of Global Cache storage size (in Megabytes) to use when BI Server cache is enabled – 9,999 Maximum number of cache entries; used to tune cache performance – 99,999 Maximum size (in Megabytes) for individual server cache entries – 9,999 Data Display/Download: The Maximum no.of rows that we can set to display/download in the Table/Pivot views. But keep in mind OBIEE is NOT meant to be a tool to extract huge amounts of information. Maximum number of rows of data to include in Table views – 9,999,999 Maximum number of rows of data to include in delivered emails – 9,999,999 Maximum number of rows to export to excel – 9,999,999

In OBIEE 11G, The instanceconfig.xml file stores the OBI PS configuration settings. Many configuration settings are available in EM and those should be controlled within EM only unless if we disabled centralConfigurationEnabled option. If any particular setting is not available in EM then we should make changes directly in instanceconfig.xml file. There are many situations where we need to change the default OBI configuration settings to a new value.

First observation: Dice. I’m trying to be cautiously optimistic, but it seems as Business Intelligence market in general is picking up.

OBIEE 11g skills, both in terms of new functionality (mapping, analyses, KPIs and Scorecards etc) and new infrastructure (WebLogic, EM, OPSS etc) A smattering of Essbase skills, focused mainly on the integration with OBIEE and Essbase (and the many workarounds and gotchas) Good ODI skills, both in terms of the basics, but also being able to write knowledge modules, integrate with OBIEE, deployment and migration Solid database skills – OBIEE gave the illusion through aggregates etc that database tuning was redundant, but time has shown it’s by far the biggest success factor in a project – get the database design and optimisation wrong, and your project is toast. You need to know partitioning, materialized views, index types, and increasingly, you need to get yourself on an Exadata project as customers are buying the technology but you can’t teach it to yourself at home BI Apps skills, but watch out for everything changing when BI Apps 11g comes out, and be prepared to learn the Fusion Apps and JDeveloper if you want to stay in the game Looking to the future, keep an eye on technologies such as in-memory (TimesTen), mid-tier caching (Coherence), plus technologies such as Business Activity Monitoring (BAM), “big data” (Hadoop, large data sets, NoSQL), complex event processing and maybe products such as Qlikview, just in case Oracle buys them, or at least to know what the competition are up to, or more importantly pitching to your boss

The other thing to bear in mind of course, if you’re an Oracle BI developer, is that you need to have great business, communication and data modeling skills.

OBIEE, at the BI Server level. lets you define query limits that either warn or stop users from exceeding certain elapsed query times or number of rows returned. Assuming you define a “standard” group for most OBIEE users, you might want to stop them from displaying reports (requests) that return more than 50,000 rows, whilst you might want to warn them if their query takes over five minutes to run.

OBIEE Cache Purge/Seed utility

So, one alternative to installing a QlikView platform is to build QlikView-style displays with QlikView-style performance directly within OBIEE.

OBIEE Prompting on Non-Conformed Dimensions

The best practice in business intelligence delivery is always to build a data warehouse.

Pure transactional reporting is problematic. There are, of course, the usual performance issues. Equally troublesome is the difficulty in distilling a physical model down to a format that is easy for business users to understand. Dimensional models are typically the way business users envision their business: simple, inclusive structures for each entity. The standard OLTP data model that takes two of the four walls in the conference room to display will never make sense to your average business user.