Last updated on AUGUST 03, 2014
Applies to:Siebel System Software - Version 22.214.171.124  to 126.96.36.199 SIA [Release V7 to V8]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 188.8.131.52 
Database: Oracle 9i
Application Server OS: Microsoft Windows 2000 Advanced Server SP 3
Database Server OS: IBM AIX 5L 5.1
This document was previously published as Siebel SR 38-1568596161.
***Checked for relevance on 14-Feb-2013***
*** Checked for Relevance on 03-AUG-2014 ***
From my understanding there is one parameter that can be set at the Enterprise level or the Component level to roll-over the Siebel log directory to the Siebel LogArchive. The LogArchive parameter apparently is supposed to dictate how many log folders are kept in the Archive.
In our current development and testing environments we are running Siebel 184.108.40.206, we have noticed that the Log folder does not get rolled over to the Log Archive directory after a restart of Siebel.
In some environments only the ddlsync, imprep and exprep folders are making it into the Siebel LogArchive and the actual logs are not there.
I would like to understand what parameters are necessary to ensure that we are cleaning the Siebel log directory after a restart and what parameter/s control log archiving. After exploring the few that I believe are possibilities. I have found tweaking these parameter/s is not working.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms