| Purge Concurrent Requests [message #110660] |
Wed, 09 March 2005 09:28  |
alanm
Messages: 284
Registered: March 2005
|
Senior Member |
|
|
hi all,
i have run the following 2 scripts and get the associated results.
select count(*) from apps.fnd_concurrent_requests;
COUNT(*)
----------
26651
select count(*) from apps.fnd_concurrent_processes;
COUNT(*)
----------
37436
As I understand it performance degradation will occur if the result of the scripts is greater than 5000 rows. Can someone please explain what these tables do and why they should be purged.
best regards
Alan
|
|
|
|
| Re: Purge Concurrent Requests [message #110782 is a reply to message #110660] |
Thu, 10 March 2005 05:41  |
adragnes
Messages: 241
Registered: February 2005
Location: Oslo, Norway
|
Senior Member |
|
|
This particular area is also well described in the System Administrator's Guide in the chapter Managing Concurrent Processing.
But generally, the electronic Technical Reference Manuals are a good source when you wonder what a particular table, view or other database object in the E-Busines Suite is used for. It is available for free under Top Tech Docs on Metalink.
From eTRM for FND_CONCURRENT_REQUESTS:
| Quote: |
FND_CONCURRENT_REQUESTS stores information about individual concurrent requests.
[...]
You need one row for each concurrent request. Though you should occasionally delete from this table, you should not modify any of its data. Oracle Application Object Library uses this information to run concurrent requests, and automatically updates it as requests change their status.
|
From eTRM for FND_CONCURRENT_PROCESSES:
| Quote: |
FND_CONCURRENT_PROCESSES stores information about concurrent managers. Each row includes values that identify the ORACLE process, the operating system process, and the concurrent manager (QUEUE_APPLICATION_ID and CONCURRENT_QUEUE_ID). You need one row for each instance of a running concurrent manager (each process), as well as one row for the Internal Concurrent Manager. Oracle Application Object Library uses this table to keep a history of concurrent managers. You should never update this table manually.
You can use the Purge Concurrent Request and/or Managers Data program to delete history information periodically.
|
The reason why performance might deteriorate is that when searching for a particular concurrent request using criteria such that no index can be used (or no criteria at all) it takes a long time to go through all the records in the table.
--
Aleksander Dragnes
|
|
|
|
|
|
|
|
| Re: Purge Concurrent Requests [message #110948 is a reply to message #110823] |
Fri, 11 March 2005 07:00 |
adragnes
Messages: 241
Registered: February 2005
Location: Oslo, Norway
|
Senior Member |
|
|
The "dirty" little secrete of the Oracle E-Business Suite is that it is actually quite batch-oriented. The fashion is for event driven and online systems, but doing things using batches has its advantages. You can for instance run resource intensive jobs during the night when nobody is using the system.
In the Oracle E-Business Suite batches are called concurrent programs and they are planned and runned by the Concurrent Manager. The tables in question are used for tracking and logging information about batches. As you run batches the tables will fill up, hence the need for purging them from time to time.
Be aware though that when you do purge you lose information of what has been run when and by whom, so make sure that you comply with your organisation's policies on auditing.
If you are going to work as Apps DBA for some time I would urge you to read at least the following manuals (freely available from Metalink):
- Oracle Applications Concepts
- Oracle Applications System Administrator's Guide
- Oracle Applications Flexfields Guide
Depending on whether you have in-house developers or whether you will do some customizations yourself, you might also want to have a look at the Oracle Applications Developer's Guide.
If you work on an multi-org instance you should also read Multiple Organizations in Oracle Applications. And if you have to deal with multiple reporting currencies, take a look at Multiple Reporting Currencies in Oracle Applications.
--
Aleksander Dragnes
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
