Additional Targeted Threadpool In CCS (Doc ID 2903643.1)

Last updated on JUNE 10, 2024

Applies to:

Goal

On: 21C version, Environment Related

Additional Targeted Threadpool in CCS

As part of the default implementation in CCS, we do have a DEFAULT threadpool and NOCACHE threadpool which we can use for the client's batch schedule. We increased the allowable threads for both threadpools and now we do have a maximum of 108 threads for the DEFAULT and 45 for NOCACHE.

At the moment, all the batches in the schedule are running on the DEFAULT threadpool and we are using NOCACHE for CMA and Data Conversion batches.

With the current setup, we are noticing that we are having workload constraints, especially during the time of the day when the critical batches (i.e. BILLING, TBF, Periodic Batches, etc.) are running.

We wanted to know if it is possible to request a dedicated threadpool (i.e. PRIMARY/CRITICAL TPW) in our UAT/PROD environment so we can distribute the load evenly. We do understand that the NOCACHE threadpool will be decommissioned once the project goes-live so we wanted to have another threadpool that we can use current/post-go-live.

We do understand that implementing this has a financial cost/impact involved and we want to understand the process or engagements for this type of request. 

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.