My Oracle Support Banner

Temp DB Usage For Historian (Doc ID 2878320.1)

Last updated on JUNE 22, 2022

Applies to:

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

Goal

The historian seems to fill up the tempdb without releasing it. This happened while Documaker was under charge.
As you can see below, once the tempdb reached its limit of 600Gb, Documaker stopped responding.

We had to reboot it and by doing so, it released all the tempdb. So obviously, some process in Documaker was holding sql server from releasing the tempdb.

Note that at some other time, when Documaker is not under heavy charge, the tempdb behaves correctly.

We use the complex historian setting and the historian schedule is displayed after the following screenshots.

Historian schedule :

Table Priority Schedule UTC Schedule eastern time

Tables live: 1 00,10 UTC 20h, 6h
PUBSHIST 3 00,10,16 UTC 20h, 6h, 12h Est
RCPSHIST 4 00,10,16 UTC 20h, 6h, 12h Est
TRNS 5 00,10,16 UTC 20h, 6h, 12h Est
BCHSHIST 5 00,10,16 UTC 20h, 6h, 12h Est
TRNSHIST 6 00,10,16 UTC 20h, 6h, 12h Est
TRNSLOG 7 00,10,16,21 UTC 20h, 6h, 12h, 17h Est
JOBSHIST 8 00,10,16 UTC 20h, 6h, 12h Est
BCHS_RCPSHIST 9 00,10,16 UTC 20h, 6h, 12h Est

LOGS 5 6 UTC, sam 2h Est, Saturday
ERRS 6 6 UTC, sam 2h Est, Saturday

Solution

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
Goal
Solution
References


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