GRC Is Cancelling Jobs Over 85.0% Of Memory Space (Doc ID 2135081.1)

Last updated on MAY 06, 2016

Applies to:

Oracle Transaction Controls Governor - Version 8.6.5 and later
Oracle Application Access Controls Governor - Version 8.6.5 and later
Information in this document applies to any platform.

Symptoms

On : 8.6.5.9182 version, Business Objects

ACTUAL BEHAVIOR
---------------
Before the 8.6.5.9182 upgrade, Transaction Synchronization (TCG ETL) was able to complete successfully. After the upgrade to 8.6.5.9182, TCG ETLs are getting cancelled automatically:

2015-11-26 14:30:21,283 ERROR [of WorkManager: 'default'] CancelRequest:37 [JOB 536 NEEDS TO BE CANCELED!] Memory usage of 49200.534288 MB is over 85.0% of 55834.574848 memory space
2015-11-26 14:30:21,296 DEBUG [of WorkManager: 'default'] AbstractSubJob:321 SCHDR Updated process with id: 536 with status CANCEL_REQUESTED
2015-11-26 14:30:21,297 DEBUG [of WorkManager: 'default'] Executor:334 Request CANCEL for groupId=7
2015-11-26 14:30:21,875 DEBUG [of WorkManager: 'default'] PeriodicCheckMonitorStrategy:88 SCHDR Job ID 536 is CANCEL_REQUESTED
2015-11-26 14:30:21,876 DEBUG [of WorkManager: 'default'] JobStatusMonitor:199 SCHDR notify listeners for job subjob [jobName=tcgetlsub 1448569821876, jobId=536, jobRunId=223, jobStatus=CANCEL_REQUESTED, jobType=SUB_ETL] with status CANCEL_REQUESTED
2015-11-26 14:30:21,876 DEBUG [of WorkManager: 'default'] PeriodicCheckMonitorStrategy:88 SCHDR Job ID 535 is CANCEL_REQUESTED
2015-11-26 14:30:21,876 DEBUG [of WorkManager: 'default'] Executor:334 Request CANCEL for groupId=7
2015-11-26 14:30:21,878 DEBUG [of WorkManager: 'default'] JobStatusMonitor:199 SCHDR notify listeners for job [jobName=tcgetl 1448560496936, jobId=535, jobRunId=223, jobStatus=CANCEL_REQUESTED, jobType=TCGETL] with status CANCEL_REQUESTED
2015-11-26 14:30:21,879 DEBUG [of WorkManager: 'default'] Executor:334 Request CANCEL for groupId=7
2015-11-26 14:30:51,844 DEBUG [ExecutorThread-10] Executor:204 Interrupt threadId: 461 and ID: 7 for CANCEL
2015-11-26 14:30:51,844 DEBUG [ExecutorThread-10] Executor:205 CANCEL: [7]

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Make sure Transactions Created As Of under Manage Application Configurations is date so there is large amount data available for Transaction Synchronization.
2. Make sure there are Transaction controls or models setup on the datasource to be synchronized.
3.From Manage Application Datasources , run Synchronize Transaction on the datasource.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot complete TCGETL.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms