Forum Discussion
Oracle connection, Sessions per user Limit
Gateway doesn’t release the connections after refreshing datasets. In your scenario, go to Task Manager and kill the process "Microsoft.PowerBI.DataMovement.PersonalGateway.exe", then check if the connections are killed. After that, relaunch the "On-premises data gateway (personal mode)" configurator, and retry configuration.
However, if the issue still persists, I would recommend you use on-premises gateway to refresh your dataset, and periodically run the following script to restart gateway service to force Power BI on-premises gateway to flush out its connections after refreshing.
net stop PBIEgwService
Taskkill /IM EnterpriseGatewayConfigurator.exe /F
timeout /t 30
net start PBIEgwService
" C:\Program Files\On-premises data gateway\ EnterpriseGatewayConfigurator.exe "
Exit
There is also a similar thread for your reference.
http://community.powerbi.com/t5/Integrations-with-Files-and/On-Premises-Gateway-utilizing-many-Oracle-database-connections/td-p/153324
Regards,
Lydia
Apparently, the Power BI team doesn't care to investigate this DEFECT. It is a clear and distinct issue. Power BI Desktop in Direct Query mode creates Oracle sessions, uses them, then creates still more Oracle sessions, until it exceeds the user's defined SESSIONS_PER_USER limitation. Why does Power BI Desktop not RE-USE existing Oracle sessions??
Is this an issue that Microsoft plans on fixing? Either reusing existing connections, or even disconnecting so that it doesn't hit the session limit.
I resolved my problem, putting the data to my data warehouse and connecting the power bi on data warehouse.
Flow:
CUSTOMER DATABASE >> ETL >> DATABASE(DATA WAREHOUSE) >> POWER BI