Moving out of Obiee and starting power bi journey

Here is a guide to the key differences, challenges, and a recommended starting point for your Power BI journey:

---

## 🚀 Phase 1: Power BI Learning Roadmap

As an experienced OBIEE professional, focus your learning on these core areas where the tools differ significantly:

### 1. **Data Modeling & Transformation**

| OBIEE Concept | Power BI Equivalent/Skill | Key Focus |

| :--- | :--- | :--- |

| **RPD (Physical, BMM, Presentation Layers)** | **Power BI Data Model** | You'll rebuild the logic (joins, measures, hierarchies) directly in Power BI Desktop. The RPD structure doesn't have a direct one-to-one migration. Focus on **Star Schema** design, which is key to Power BI's performance (VertiPaq engine). |

| **Oracle SQL/SQL in Filters** | **M Language (Power Query)** | M is for **data transformation and ingestion**. It handles the "E" and "T" of ETL, similar to OBIEE's Physical/BMM layers. |

| **RPD Calculation Measures/Expressions** | **DAX (Data Analysis Expressions)** | DAX is the **calculation language** for measures, calculated columns, and calculated tables. This is critical for complex logic. *This is one of the most important new skills to master.* |

### 2. **Architecture and Deployment**

| OBIEE Concept | Power BI Equivalent/Skill | Key Focus |

| :--- | :--- | :--- |

| **OBIEE Server / WebLogic** | **Power BI Service (Cloud)** | Learn about **Workspaces**, **Gateways** (for on-premises data sources), **Dataflows** (for reusable ETL logic), and **Deployment Pipelines**. |

| **iBots / Agents** | **Data Alerts / Subscriptions** | Power BI handles scheduled report refreshes and alert notifications differently. |

| **Catalog / Presentation Services** | **Power BI Reports / Dashboards** | Reports are multi-page, interactive canvases. Dashboards are single-page collections of visuals from multiple reports. |

| **Security (Users/Groups/Application Roles)** | **Row-Level Security (RLS) & Workspace Roles** | RLS is defined using DAX expressions in the data model. User/Group management is often integrated with **Azure Active Directory (AAD)**. |

---

## 🛠️ Phase 2: Migration Best Practices

If your job involves migrating existing OBIEE content, here are the strategic steps:

### 1. **Assessment and Planning**

* **Audit Usage:** Don't migrate everything! Use OBIEE usage tracking logs to identify the **high-value, high-usage reports** and subject areas to prioritize. Decommission the rest.

* **Proof of Concept (PoC):** Start with one simple subject area to build your first Power BI model. This helps establish an internal standard and learn the process.

### 2. **Technical Migration Focus**

* **Rebuild the Model:** Manually recreate your RPD's business logic, joins, and aggregates natively in a Power BI data model, focusing on the star schema pattern.

* **Convert Logic:** You will need to **re-write** complex OBIEE filters and SQL logic into **M** (in Power Query) and your measures/calculations into **DAX**. This is the biggest technical effort.

### 3. **User Adoption & Governance**

* **Phased Rollout:** Run OBIEE and Power BI in **parallel** for a testing and validation period (**User Acceptance Testing - UAT**).

* **Training:** Provide targeted training to both business users (self-service analytics and new interface) and your IT/BI team (DAX, M, and Power BI Service administration).

---

## 💡 Quick Tips to Get Started

1. **Download Power BI Desktop:** It's free and the main development environment.

2. **Start with Microsoft Learn:** They have excellent, structured learning paths for the **Power BI Data Analyst Associate** certification. This will give you a solid foundation in M, DAX, and data modeling.

3. **Learn DAX:** There are many free resources, but mastering DAX is the key to unlocking the true power of your models.

Would you like me to find some **highly-rated online courses or specific Microsoft Learn paths** for Power BI data modeling and DAX to help kick off your training?

please close following process devenv

 When I close Visual Studio 2022 by pressing the close button on the IDE, the devenv.exe process keeps running in background between 3-5 minutes, after that time, it closes automatically, really strange.

I discovered this issue because I was trying to install an extension automatedly using DTE .

Resolution:

use task till to kill alls individail pid 

taskkill /F /PID (PID)

Oracle Time conversion from One Time zone to other

NEW_TIME

The NEW_TIME function converts a date and time from one time zone to another.

Return Value

DATETIME

Syntax

NEW_TIME(datetime-exp this_zone new_zone)

Arguments

this_zone

A text expression that indicates the time zone from which you want to convert datetime-exp. It must be a valid time zone, as listed in the following table.

new_zone

A text expression that indicates the time zone into which you want to convert datetime-exp. It is the time zone of the return value. It must be a valid time zone, as listed in Table 8-1, "Time Zones".

Table 8-1 Time Zones

AST	Atlantic Standard Time
ADT	Atlantic Daylight Time
BST	Bering Standard Time
BDT	Bering Daylight Time
CST	Central Standard Time
CDT	Central Daylight Time
EST	Eastern Standard Time
EDT	Eastern Daylight Time
GMT	Greenwich Mean Time
HST	Alaska-Hawaii Standard Time
HDT	Alaska-Hawaii Daylight Time
MST	Mountain Standard Time
MDT	Mountain Daylight Time
NST	Newfoundland Standard Time
PST	Pacific Standard Time
PDT	Pacific Daylight Time
YST	Yukon Standard Time
YDT	Yukon Daylight Time

Examples

Example 8-33 Using the Current Time of day

The SYSDATE function returns the current date and time to the NEW_TIME function.

SHOW new_time(SYSDATE 'EST' 'PST')

When the date and time in Eastern Standard Time are October 20, 2000, at 1:20 A.M., then the date in Pacific Standard Time, which is three hours earlier, is October 19, 2000. Because SYSDATE uses the format specified by NLS_DATE_FORMAT, which by default only shows the date, the time is not displayed.

19-OCT-00

Example 8-34 Specifying the Time of day

In the following example, the TO_DATE function converts a text string to a valid date and time. The TO_CHAR function includes a date format that temporarily overrides the date format specified by the NLS_DATE_FORMAT option.

SHOW TO_CHAR(NEW_TIME(TO_DATE('11-27-00 22:15:00', 'MM-DD-YY HH24:MI:SS'), -
   'HST' 'PST') 'MM-DD-YY HH24:MI:SS')

This statement converts November 27 at 10:15 P.M. (22:15:00) Alaska-Hawaii Standard Time to November 28 at 12:15 A.M. (00:15:00) Pacific Standard Time. The date format specified in the TO_CHAR function allows the time to be displayed along with the date.

11-28-00 00:15:00

Alternatively, you can change the value of NLS_DATE_FORMAT.

NLS_DATE_FORMAT = 'MM-DD-YY HH24:MI:SS'

Then this statement produces the same result, without requiring the use of TO_CHAR.

SHOW NEW_TIME(TO_DATE('11-27-00 22:15:00', 'MM-DD-YY HH24:MI:SS'), -
   'HST' 'PST')

Save System-Wide Column Formats in Oracle BI EE Answers Not Available for Admin User

Issue:
After the OBIEE Patch upgrade the Admin user cannot save column properties as a system-wide default for the catalog.

Rootcause:
BI Administrator Role is not granted the Save System-Wide Column Formats privilege.

Follow the steps below to fix the issue:

1. Login to the Analytics page as Administrator user.
2. Navigate to Administration, then Manage Privileges.
3. In the Formatting section, assign 'BI Administrator Role' to the 'Save System-Wide
Column Formats' privilege, and remove any existing entries starting with "Denied:
4. Logout and login to Analytics.

OBIA CURRENT_DAY Variable Defaults To A Static Value Instead of a Dynamic Value

Configure the value of the CURRENT_DAY variable to have the Default Initializer
set to VALUEOF("LAST_REFRESH_DT").

This can done by double clicking the CURRENT_DAY repository variable under
the option Manage, then Variables, then Static.

Performance Issue with PLP_GLBALANCEAGGRBYACCTSEGCODS

Modify the override SQL for session PLP_GLBalanceAggrByAcctSegCodes, to add hint

/*+ OPT_PARAM('_GBY_HASH_AGGREGATION_ENABLED', 'true')
USE_HASH(W_GL_BALANCE_F, W_GL_ACCOUNT_D) */

this will improve the performance.

ETL Process

ETL is an acronym for a three step process to extract data from source systems and load the data to a data warehouse. The three steps of the ETL process are:

1. Extract and load Staging Tables: Extracts and consolidates data from one or more source systems and loads into the data warehouse staging tables.
   
2. Transforms the data: Transforms data in the staging tables and computes calculated values in preparation for the load.
   
3. Load Dimension and Fact Tables: Generates and maintains data warehouse surrogate keys and loads target dimension and fact tables.
   

ETL processes are further refined to two types of mappings:

1. Source Dependent Extract (SDE) mappings – extracts the data from the transactional systems and loads to the data warehouse staging tables. SDE mappings are designed with respect to the source’s unique data model.

Source System Databases

2. Source Independent Load (SIL) mappings – extracts and transforms data from the staging tables and loads to the data warehouse target tables. SIL mappings are designed to be universal with any source.