In case of Form performance problems, performanceissue

Performance issues are complicated. performanceteam is generally responsible for the query, but it is common that the view defined by INVteam is poor, resulting in poor query performance. this must be solved by the product group and performanceteam. in case of performance problems, several common analysis methods are as follows: First, you must find SQL statements with poor performance.

Performance issues are complicated. generally, the performance team is responsible for the query performance, but the common situation is that the view defined by our INV team is poor. this must be solved by the product group and performance team. in case of performance problems, several common analysis methods are as follows: First, you must find SQL statements with poor performance.

Performance issues are complicated. generally, the performance team is responsible for the query performance, but the common situation is that the view defined by our INV team is poor. this must be solved by the product group and performance team.

There are several common analysis methods for performance problems:

First, you need to find the SQL statement with poor performance. This will collect the SQL trace and convert it to the tkprof file.

Put the SQL statement in pl/SQL developer to view the execution plan. Most of the time the problem is that the index is not used, but the full table is scanned.

Follow the steps below to connect to sqlplus and execute it step by step to generate the SQL trace and tkprof files. More detailed information will be displayed.

1. alter session set max_dump_file_size='UNLIMITED';2. alter session set tracefile_identifier='APPSPERF';3. alter session set events '10046 trace name context forever, level 12';4. alter session set statistics_level = 'ALL';5. declare binds like below   variable B1 number;   variable B2 number;   variable B3 number;   variable B4 varchar2(50);   variable B5 number;   variable B6 number;   6. Assign values to binds   begin   :B1 := 2666;   :B2 := 2666;   :B3 := 2666;   :B4 := 'VENDOR';   :B5 := 8617;   :B6 := 639187;   end;   /7. Execute the test_SQL.sql WITH BIND VARIABLES (with :B1, :B2) 8. exec dbms_session.reset_package;9. exit completely from the sqlplus prompt.10. once the step 9 is done then Pickup the trace file from udump (ls *APPSPERF*) --generated recently    directory: "SELECT value FROM v$parameter WHERE name ='user_dump_dest'"11. Generate the tkprof of the trace generated with explain option.12. provide TRACE,TKPROF and SQLTXTRACT(215187.1) to review it further. 

Finally, mail to performance team: appsperf_us@oracle.com.