Testing the aw_inc_update Procedure's Return Time from the Database

Document ID : KB000089380
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
Testing the aw_inc_update Procedure's Return Time from the Database
Resolution:

Symptoms

The aw_inc_update procedure in Applications Manager should not take longer than about 30 seconds to return from the database after it is called. If it takes longer than that you may be experiencing slowness. In the past when we have seen issues where aw_inc_update was slow to return, the root of the issue was that Oracle needed to be tuned.

 

 

 


 

 

Resolution

In order to verify that this may be your problem, place the attached SQL script (test_pipe_inc_update.sql) in Applications Manager's sql subdirectory where the Master is installed.

Login to SQL Plus as Applications Manager's Oracle user and execute the script. Results should look similar to this:

SQL> @test_pipe_inc_update

statement 1
statement 2
starting aw_inc_update
In set_aw_jq_activity
Commited. commit_aw_hard called from set_aw_jq_activity 1
Leaving set_aw_jq_activity
aw_inc_update awake at 12:30:00
aw_inc_update setting sleep time to 1
aw_inc_update exiting loop at 12:30:01
In set_aw_jq_activity
Commited. commit_aw_hard called from set_aw_jq_activity 1
Leaving set_aw_jq_activity
at 1
at 2
at 3
In set_aw_jq_activity
Commited. commit_aw_hard called from set_aw_jq_activity 1
Leaving set_aw_jq_activity
at 4
PL/SQL procedure successfully completed.

Elapsed: 00:00:06.92

Note in the above example it took only 6 seconds for the aw_inc_update procedure to run.

Since tuning Oracle relates to Oracle and not to your Applications Manager configuration, you would need to contact Oracle for specific settings to tune your system. We do have a technical white paper available for tuning this procedure in Oracle 10g/11g that you may want to reference. See KB0178055.

 


 

 

File Attachments:
test_pipe_inc_update.sql