Private corporate batches, live online cohorts and 1-on-1 mentoring in Oracle Business Intelligence Enterprise Edition — RPD modelling, analyses, dashboards and BI administration — taught by a practitioner who runs it in production.
20 years across DevOps, SRE and Security · 10,000+ engineers trained · Trained teams at JPMorgan Chase, Verizon, Nokia and the World Bank
Principal DevOps Engineer & Architect
Rajesh teaches OBIEE from the repository outward rather than from the dashboard inward — physical layer joins and connection pools, then the business model and mapping layer where logical table sources, fact calculations and dimension hierarchies determine every query the engine generates, and only then the presentation layer and the front end. Sessions include reading generated physical SQL from the query log to explain why a report is slow or a number is wrong, which is the diagnostic skill the platform actually demands. Security is taught as repository and data-level filters alongside catalog permissions, and administration covers RPD deployment, catalog backup and cache management as operational routine rather than as an appendix.
Twenty years across DevOps, SRE and Security, in principal and architect roles at PayPay, SoftwareAG, ServiceNow, JDA Software, Intuit, Adobe and others. He has trained engineers at JPMorgan Chase, Verizon, Nokia, the World Bank, VMware, Oracle, Mercedes-Benz and Airbus — more than 10,000 people personally. He teaches what he runs, not what he reads.
You are booked with a named engineer, and that is who turns up. Marketplaces and larger providers rotate whoever is free, so the person who sold you the agenda is rarely the person teaching it.
The same trainer is available for the next engagement, which matters when a team builds on what it learned last time.
Your batch is assigned a named trainer before it starts, and that is who teaches it. See the full faculty.
Engagements are matched on the tool, not the calendar. For OBIEE that means a trainer who has run it in production — Oracle Business Intelligence Enterprise Edition — RPD modelling, analyses, dashboards and BI administration — rather than whoever is free that week. You are told who is teaching before you commit, and that person is on the discovery call that shapes the agenda.
Where a batch is large enough to need a second trainer, the pairing is declared up front. The lead trainer stays accountable for the syllabus and the assessment either way.
Principal DevOps Engineer & Architect
Twenty years across DevOps, SRE and Security in principal and architect roles at PayPay, SoftwareAG, ServiceNow, JDA Software, Intuit, Adobe, IBM/Emptoris, Ness, MindTree and Accenture. He has trained more than 10,000 engineers personally, at organisations including JPMorgan Chase, Verizon, Nokia, the World Bank, VMware, Oracle, Mercedes-Benz and Airbus. He teaches what he runs, not what he reads.
Teams of 8–30
Custom agenda, your timezone, onsite or online, NDA-friendly.
Request a quoteIndividual engineers
A private instructor and a curriculum built around your goal.
₹99,999Individuals who want peers
Scheduled batch, max 8 to 10 hours of live instruction.
₹34,999A private batch starts with a discovery call. We look at the stack you actually run — the CI system, the cloud, the constraints — and map the agenda onto it, so examples use your topology rather than a generic one.
Delivery is onsite at your premises, live online, or hybrid, scheduled around your release calendar rather than ours. Batches run 8 to 30 engineers.
Every attendee leaves with recordings, slides, lab repositories and a completion certificate. You receive an attendance and assessment report. Invoicing supports PO and GST.
Talk to us about a private OBIEE batchOBIEE — Oracle Business Intelligence Enterprise Edition — is an enterprise reporting and analytics platform that puts a single business-friendly model in front of one or more physical data sources. Its defining component is the repository, the RPD, built in the BI Administration Tool across three layers: a physical layer describing tables, connection pools and joins as they exist in the database; a business model and mapping layer where those tables become logical fact and dimension objects with calculations, hierarchies and multiple logical table sources; and a presentation layer that exposes only the subject areas and column names business users should see.
That separation is the point. Because a user selects presentation columns rather than writing SQL, OBIEE's query engine decides which physical tables to hit, which aggregate to use, and how to federate across sources. Getting the business model right is therefore what determines whether reports are fast, consistent and trustworthy — and almost every serious OBIEE problem traces back to the RPD rather than the front end.
The web tier is where consumption happens. Analyses combine filters, prompts, tables, pivot tables and graphs; dashboards assemble those into pages with dashboard prompts and variables driving them; Agents (Delivers) push results on a schedule or condition; and the presentation catalog holds it all with its own permission model. OBIEE 12c added Visual Analyzer, data mashup from spreadsheet uploads, and BI Ask for ad-hoc exploration. Underneath, WebLogic Server, Enterprise Manager and the RPD and catalog deployment tooling are what an administrator actually operates.
A large installed base of Oracle Business Intelligence still runs the operational and financial reporting that organisations depend on, and it is rarely replaced quickly. Migrations to Oracle Analytics Cloud, Power BI or Tableau take years, run in parallel with the existing platform, and need people who can explain what the current RPD actually does before any of it can be reproduced elsewhere.
That produces steady demand for two overlapping skills. The first is maintaining and extending the existing platform — new subject areas, security changes, performance work, upgrades and catalog management. The second is migration analysis: reading a mature RPD, identifying the business logic embedded in logical table sources, calculations and hierarchies, and mapping it onto a target semantic model without silently changing a number.
The scarce part is the modelling. Building an analysis is a short lesson; designing a business model that federates sources, handles slowly changing dimensions, computes correctly at every level of a hierarchy, and enforces data-level security is the work that organisations struggle to hire for.
The context before the tool. What a data warehouse is for, star and snowflake schemas, facts and dimensions, grain and additivity — then where OBIEE sits in that picture, how its architecture is assembled, and how the product line evolved through 10g, 11g and 12c into Oracle Analytics.
Topics: Data warehouse modelling: star and snowflake schemas · Facts, dimensions, grain, additivity and conformed dimensions · OBIEE architecture: BI Server, Presentation Services, WebLogic · The three-layer repository concept and why it exists · OBIEE history: 10g, 11g, 12c and the path to Oracle Analytics · Comparison with other BI tools and where OBIEE still wins · Terminology map for people arriving from other platforms
Getting a working environment and knowing what each URL is for. Database prerequisites and the RCU schemas, the OBIEE installation and domain creation, then the three web entry points every administrator uses daily — WebLogic Console, Enterprise Manager and Analytics — and what belongs in each.
Topics: Database installation and prerequisites for the BI platform · Repository Creation Utility schemas and what they hold · OBIEE installation, domain creation and configuration · Start and stop sequence, and diagnosing a component that will not start · WebLogic Console: servers, data sources, users and groups · Enterprise Manager: BI instance configuration, availability, logging · Analytics: the end-user entry point and catalog structure · Log files that matter: nqserver, nqquery, sawlog
The foundation of every query the BI Server generates. Importing metadata, connection pools and their settings, physical joins including complex joins, aliases and why they are non-negotiable, and the physical model patterns that later cause or prevent problems in the business model.
Topics: BI Administration Tool: online and offline modes · Importing metadata and connection pool configuration · Connection pool settings: call interface, connections, isolation · Physical joins: foreign key and complex joins · Aliases and why every table should be aliased · Opaque views and when they are justified · Multiple data sources in one physical layer · Consistency checking the physical layer
Where the actual modelling happens and where most OBIEE careers are made. Logical tables and their sources, mapping multiple logical table sources onto one logical table, aggregation rules and fact calculations, logical dimensions with levels and level-based measures, and the content settings that decide which source the engine picks.
Topics: Logical tables, logical columns and logical joins · Logical table sources: multiple sources on one logical table · Content tab: aggregation content, fragmentation, WHERE clauses · Aggregation rules and calculation measures in the BMM layer · Fact calculations: physical versus logical calculations and the difference · Logical dimensions, hierarchies and levels · Level-based measures, shares and time-series functions (AGO, TODATE) · Aggregate navigation across summary tables
Turning a technical model into something a business user can navigate, and proving the model returns correct numbers before anyone builds a report on it. Subject area design and naming, folder structure, then the testing loop: query the model, read the generated physical SQL, and confirm the engine did what you expected.
Topics: Subject areas, presentation tables, columns and hierarchies · Naming, ordering and hiding columns for usability · Multiple presentation layers over one business model · Consistency check errors and warnings, and how to resolve them · Testing the repository from Answers and from nqcmd · Reading generated physical SQL in nqquery.log · Common modelling errors and the symptoms they produce · Version control and multi-user development environments
The three administrative subjects that decide whether a deployment is safe and fast. Repository and session variables driven by initialisation blocks, the security model from authentication through application roles to data-level filters, and BI Server caching with seeding, purging and event polling.
Topics: Repository variables: static and dynamic, initialisation blocks · Session variables, system session variables and row-wise initialisation · Presentation variables and where they differ from the rest · Authentication providers and Active Directory integration · Application roles, permissions and role hierarchy · Object-level security in the repository and the catalog · Data-level security with filters driven by session variables · Cache: enabling, seeding, purging, event polling tables, cache hit analysis
The front-end work, done properly. Criteria and results, column formulas and filters, the view types and when each communicates best, pivot tables with calculated items, graphs, conditional formatting, and the selection steps and hierarchical column behaviour that people usually discover by accident.
Topics: Creating analyses: criteria, filters, column formulas, sorting · Filters, prompts and filter types including saved filters · Table, pivot table, graph, gauge, narrative and other views · Pivot table calculated items, calculated measures and totals · Graph types, axis configuration and formatting · Conditional formatting and column selectors · Selection steps and hierarchical columns · Master-detail linking between views · Advanced features: union, direct database request, logical SQL view
Assembling analyses into something people use every morning. Dashboard pages and layout, dashboard prompts driving multiple reports through presentation variables, conditional sections, then Agents to deliver content on schedule or on condition, and action links that connect reports to other systems.
Topics: Dashboard creation, pages, sections and layout · Dashboard prompts, scope and prompt-to-report binding · Presentation variables driving titles, filters and formulas · Conditional sections and guided navigation · Dashboard properties, saved customisations and default pages · Action links, navigation between analyses and to URLs · Agents (Delivers): schedules, conditions, delivery devices · Briefing books and print or export behaviour
The self-service half of 12c and where it genuinely helps versus where it creates a governance problem. Visual Analyzer projects and visualisations, uploading spreadsheet data sets, blending uploaded data with governed subject areas, and BI Ask for keyword-driven exploration.
Topics: Visual Analyzer projects, canvases and visualisation types · Creating data sets from files and from subject areas · Data mashup: blending uploaded data with governed data · Data preparation and column enrichment in Visual Analyzer · BI Ask and ad-hoc exploration · Governance implications of user-uploaded data · Where Visual Analyzer fits alongside classic analyses · The upgrade path towards Oracle Analytics
Operating the platform over time. RPD deployment between environments, catalog backup and restore, Catalog Manager for bulk operations and object surgery, usage tracking, performance investigation, patching and upgrade, and the migration questions that eventually arrive.
Topics: RPD deployment: online updates, datamodel.sh, environment promotion · Multi-user development, projects, merges and conflict resolution · Catalog backup, archive and restore procedures · Catalog Manager: bulk edits, XML surgery, permissions reporting · Usage tracking and identifying reports nobody runs · Performance investigation across database, BI Server and Presentation Services · Patching, upgrade and environment refresh procedures · Migration analysis towards Oracle Analytics Cloud or another platform
We rebuild the agenda around the tools you actually run.
Request a custom agendaImport a star schema, alias and join the physical layer, build the business model with a full hierarchy, and expose a clean subject area that passes consistency check.
Add a summary table as a second logical table source with correct content settings, then prove from the query log that the BI Server picks it at the right grain.
Implement application roles, object permissions and a session-variable data filter so two accounts see different data from the same analysis.
Build a dashboard where a single set of prompts drives four analyses through presentation variables, with conditional sections and guided navigation.
Take a slow analysis, read the generated physical SQL, identify whether the fault is model, database or cache, and prove the fix with timings.
Take an RPD and catalog change from development through test to production with backup, rollback plan and no downtime, documenting every step.
Billed yearly at ₹9,996
Max 8 to 10 hours of live instruction
Full program, private instructor
8–30 engineers · custom agenda · onsite or online · PO and GST invoicing
Refunds. If we cancel or postpone a cohort, you get a full refund within 15 days. There is no money-back guarantee otherwise.
Terms. Course material remains licensed to the attendee. Read the terms.
Your data. We don't share it with third parties. Privacy policy.
Certificate of completion
The Rundeck developer session was excellent and highly engaging. I appreciated how well the session was structured, with the theoretical concepts explained clearly and in simple terms. What stood out most to me was the demo — it was both informative and enjoyable. I especially liked how Rajesh walked us through not only the happy path but also the sad path, showcasing common issues and sharing practical troubleshooting tips.
Rajesh's experience and knowledge are exceptional and we learnt invaluable practical knowledge which we can apply in our production environment. Incredibly friendly and gave us a fantastic insight both in-depth and at a high level of the Rundeck product.
Great learning experience from a very knowledgeable instructor with well-prepared course notes. The lab exercises on AWS instance work well to learn the hands-on side of the course.
Rajesh is a very good trainer I have experienced in DevSecOps training. The number of contents in different topics he has posted on the DevOpsSchool public website are amazing and user friendly for beginners and experienced professionals.
The trainer (Rajesh) provided very good sessions on SRE profession. Not only hands-on learning on the tools but also SRE mindset.
Very good training session. Well explained from the basics to the complex concepts. Also tried to cover practicals and demos within the 3 hour sessions. The learning content and videos are of a great deal of help.
| What matters | YouTube + blogs | Generic online course | Freelance marketplace | DevOpsSchool |
|---|---|---|---|---|
| Named practitioner | No | Rarely | Varies per booking | Yes — same trainer each time |
| Production experience | Unknown | Unknown | Unverified | 20 years, named employers |
| Custom agenda | No | No | Sometimes | Built from your stack |
| Onsite delivery | No | No | Sometimes | Yes |
| Lab environment | None | Sandbox that expires | Varies | Your own cloud — skill goes with you |
| Assessment | None | Quiz | Rarely | Assignments + capstone per module |
| Per-attendee certificates | No | Sometimes | Rarely | Yes |
| Corporate invoicing | No | Limited | Varies | PO and GST |
| Post-training support | None | Forum, time-limited | None | Lifetime forum access |
Tell us the team, the stack and the timeline. You'll get a straight answer, not a sales sequence.
Talk to an advisorPrefer to call or email?
More ways to reach us on the contact page.