Here is a way to enable Trace file generation from a PLSQL
Enable trace - Alter session set sql_trace=true;
Enable timed statistics - Alter session set timed_statistics=true
Set an identifier to the trace file - ALTER SESSION SET tracefile_identifier=<<identifier>>
Disable trace - ALTER SESSION SET SQL_TRACE=FALSE;
Hi Sahan,
Thank you very much for the valuable information. When I tried to do it, got below error. Is there a way to create those tables from IEE too? I have seen that the tables can be created using a test window in PlSql developer. But it this scenario, I am using sql developer.
Best Regards, Nisansala
Hi NIsansala,
I haven’t encountered this before. Quick advance search showing there is an patch released for (app9 126474) case id G1623354.
In one case I found below findings:
“When you try to use Performance Analyzer on an environment where the Oracle Profiler Objects have not been deployed you receive the following error:
PerformanceAnalyze.PROFERRSTART: Unable to start performance analyzer. Check installation and run ORACLE_HOME\RDBMS\admin\proftab.sql as APPOWNER.
When checking the F1 documentation under https://wis.ifsworld.com/f1docs/apps10upd2/foundation1/050_development/050_development_tools/078_perf_analyzer/#Configuring_the_Analyzer it says the following though:
Run the script "<ORACLE_HOME >\Rdbms\Admin\Proftab.sql" as user SYS.
As you can see one says to deploy the script as IFSAPP and the other one as SYS. I think SYS is correct and as such the error message should be corrected to reflect this accordingly..”
Most probable this error occurs due to analyzer not been installed.
Hope this helps.
Open the Performance Profiler by choosing Debug > Performance Profiler (or Alt + F2). The tool shows each event in a list view.
Adding this for future references:
received the same error Nisansala mentioned I was able to resolve this by:
log into the plsql developer and open a test window and click on profiler button
This will ask to create relevant tables for the profiler. Press Ok
Retry the IEE steps in debug console (restart the IEE if needed)