High Memory Usage when Decoding Audit Trail Data with Script
(Doc ID 2570320.1)
Last updated on DECEMBER 03, 2019
Applies to:Siebel CRM - Version 16.13 [IP2016] and later
Information in this document applies to any platform.
High Memory usage of the siebmtshmw.exe process when decoding large amount of audit trail data using the scripts from Bookshelf 8.1 > Siebel Applications Administration Guide > Audit Trail > Decoding the Audit Log File.
The memory is not released even when the bs scripts is able to finish successfully.
For the case when bs scripts is not able to finish successfully, after processing 480 000 records, the siebmtshmw.exe process increased to about 1,5 gig. and it's stop with no crash call stack.
To prevent this behavior we had in the script : BC = null; BO = null; , but we still have the problem.
Memory usage of the siebmtshmw.exe process server should NOT get's bigger and bigger during the execution.
The issue can be reproduced at will with the following steps:
1. Invoke the script that decoding audit trail data
2. Note the memory use of the siebmtshmw.exe process on the server get's bigger and bigger during the execution.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document