My Oracle Support Banner

Historian Complex Retention (Doc ID 2883381.1)

Last updated on JULY 18, 2022

Applies to:

Oracle Documaker - Version 12.6 and later
Information in this document applies to any platform.


The historian seems to fill up the tempdb without releasing it. This happened while Documaker was under charge.
Once the tempdb reached its limit of 600Gb, Documaker stopped responding. We had to reboot to release all the tempdb.

So obviously, some process in Documaker was holding SQL Server from releasing the tempdb.

Note: When Documaker is not under heavy charge, the tempdb behaves correctly.

We use the complex historian setting.


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

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