Collecting Siebel Diagnostic Data

Collecting Siebel Environment Data

This chapter describes how to collect Siebel environment information (such as setup, configuration, and logging information) for diagnostic and troubleshooting purposes using the Siebel Diagnostic Collector (SDDC) command-line utility. This chapter includes the following topics:

About Siebel Diagnostic Data Collector

The Siebel Diagnostic Data Collector (SDDC) is a command-line utility that resides in the binary (bin) subdirectory of the Siebel Server, Siebel Gateway, and Siebel Application Interface root directory as the executable siebsnap.exe under Microsoft Windows or as binaries under UNIX. When run, the Siebel Diagnostic Data Collector (SDDC) utility collects information individually for Siebel Servers or the Siebel Gateway. The utility stores the collected data in output files. These files are available for immediate review, or can be sent to Oracle Global Customer Support if required by creating a service request (SR) on My Oracle Support. For information about using SDDC to collect environment data, see Process of Collecting Siebel Environment Data Using SDDC.

SDDC creates output files after each execution. These files document environment information for each specific entity. For details on the location and type of collected information, see About Reviewing Siebel Environment Data.

Note: To run an environment data collection, make sure you have all necessary executables or binaries available. For more information, see About SDDC Executables and Binaries.

About SDDC Executables and Binaries

The Siebel Diagnostic Data Collector (SDDC) utility uses the following executables or binaries to collect environment data comprehensively. The SDDC does not require all executables and binaries to run; however, the SDDC collects the most information when all are present. The executables and binaries are listed for each operating system and platform.

Windows Executables

odbcsql
osql (if using MS SQL)
netstat
sqlplus (if using Oracle Database)
db2level (if using db2)

UNIX Binaries (Common)

The SDDC uses the following 31 binaries on all UNIX platforms.

/usr/bin/cp
/bin/find
/bin/hostname
/usr/bin/ls
/bin/touch
/bin/uname
/bin/tar
/bin/echo
/bin/netstat
/bin/mv
/bin/sum
/etc/system
/bin/compress
/bin/wc
/usr/sbin/ndd
/bin/mkdir
/bin/head
/dev/tcp
/bin/rm
/bin/coreadm
db2level
/bin/chmod
/bin/sed
/usr/bin/ipcs
/bin/grep
/bin/awk
db2
/bin/cat
/bin/date
sqlplus
what

UNIX Binaries for Oracle Solaris

psrinfo
sysdef
prtconf
ifconfig
CC
/bin/isainfo
/bin/ulimit -a
/sbin/prtdiag

UNIX Binaries for AIX

lscfg
instfix
lsattr
lsps
lsfs
lspv
lsvg
no
ifconfig
/bin/oslevel
/bin/getconf
/bin/lslpp
/etc/security/limits
/bin/errpt
/etc/inittab

UNIX Binaries for HP-UX

sysdef
aCC
swlist
ioscan
/bin/getconf
/usr/lib/libCsup2
/etc/system

UNIX Binaries for Linux

gcc
getconf
/sbin/ifconfig
/proc/cpuinfo
/sbin/sysctl

Process of Collecting Siebel Environment Data Using SDDC

You run Siebel Diagnostic Data Collector (SDDC) to collect environment setup, configuration settings, and logging information about the system. For more information about SDDC, see About Siebel Diagnostic Data Collector.

Run SDDC separately for the Siebel Servers or the Siebel Gateway to collect information specific to that entity. The kinds of tasks you can perform are similar for both Microsoft Windows and UNIX, but there is additional preparation for UNIX before you can begin collecting data.

To collect Siebel environment data using SDDC, perform the following tasks:

(UNIX only) Do Preparing the UNIX Environment to Run SDDC.
Do one of the following:
- Run SDDC to collect data for the Siebel Server.
  For more information, see Running SDDC to Collect Siebel Server Data.
- Run SDDC to collect data for the Siebel Gateway.
  For more information, see Running SDDC to Collect Siebel Gateway Data.

Preparing the UNIX Environment to Run SDDC

Perform the following procedure to prepare the UNIX environment to run Siebel Diagnostic Data Collector (SDDC).

To prepare the UNIX environment to run SDDC

Run a database-specific script to set database environment variables.
Run the siebenv.sh or siebenv.csh scripts to set Siebel environment variables.
For more information about these scripts, see Siebel Installation Guide for UNIX.
Change the permissions to execute SDDC.

You are now ready to collect data using SDDC using one of the following procedures:

Running SDDC to Collect Siebel Server Data

This topic provides procedures for collecting Siebel Server data using Siebel Diagnostic Data Collector (SDDC) for Microsoft Windows and UNIX.

The following table shows additional optional parameters available for use in collecting data for Microsoft Windows. These parameters apply to both Siebel Server and Siebel Gateway.

Parameter	Description
`/c siebsnap.cfg`	Include this parameter to reference a particular configuration file. Use this parameter if Oracle Global Customer Support provides a configuration file. For more information, see Configuring SDDC Content Under Microsoft Windows.
`/h`	Use this parameter with the siebsnap.exe command to list help information on SDDC and its parameters.
`/l`	Indicates the preferred language.

The following table shows additional optional parameters available for use in collecting data for UNIX. These parameters apply to Siebel Server and Siebel Gateway.

Parameter	Description
`-c siebsnap.ini`	Include this parameter to reference a particular configuration INI file. For more details, see Configuring SDDC Content Under UNIX.
`-help`	Use this parameter with the siebsnap command to list help information on SDDC and its parameters.
`-ouput`	Use this parameter to configure a different SDDC output location. For more details, see SDDC Output Under UNIX.

Running SDDC to Collect Siebel Server Data for Microsoft Windows

Use the following procedure to collect Siebel Server data for Microsoft Windows.

To run SDDC to collect Siebel Server data for Microsoft Windows

Navigate to the binary (bin) subdirectory within the Siebel Server root directory.
Run siebsnap.exe using the /s flag, as shown, and, as necessary, additional parameters listed in the table in Running SDDC to Collect Siebel Server Data:
```
siebsnap.exe /s
```
Review the collected information in the siebsnap output directory, which is created by the SDDC utility under the SIEBSRVR_ROOT directory.

Running SDDC to Collect Siebel Server Data for UNIX

Use the following procedure to collect Siebel Server data for UNIX.

To run SDDC to collect Siebel Server data for UNIX

Do Preparing the UNIX Environment to Run SDDC.
Enter the siebsnap command using the -s flag, as shown, and, as necessary, additional parameters listed in Running SDDC to Collect Siebel Server Data:
```
siebsnap -s siebel_server_name
```
Note: Alternatively, use -s this_server.
Review the collected information in the siebsrvr_computer-name_server-name output directory.

Running SDDC to Collect Siebel Gateway Data

This topic provides procedures for collecting Siebel Gateway data using Siebel Diagnostic Data Collector (SDDC) for Microsoft Windows and UNIX.

Running SDDC to Collect Siebel Gateway Data for Microsoft Windows

Use the following procedure to collect Siebel Gateway data for Microsoft Windows.

To run SDDC to collect Siebel Gateway data for Microsoft Windows

Navigate to the binary (bin) subdirectory within the Siebel Gateway root directory.
Run siebsnap.exe using the /g flag, as shown, and, as necessary, additional parameters listed in the table in Running SDDC to Collect Siebel Server Data:
```
siebsnap.exe /g
```
Review the collected information in the siebsnap output directory, which is created by the SDDC utility under the gtwysrvr directory.

Running SDDC to Collect Siebel Gateway Data for UNIX

Use the following procedure to collect Siebel Gateway data for UNIX.

To run SDDC to collect Siebel Gateway data for UNIX

Do Preparing the UNIX Environment to Run SDDC.
Enter the siebsnap command using the -g flag, as shown, and, as necessary, additional parameters listed in the table in Running SDDC to Collect Siebel Server Data:
```
siebsnap -g siebel_gateway_name
```
Note: Alternatively, use -g this_server.
Review the collected information in the computer-name_gateway output directory.

Examples of SDDC Commands

This topic provides examples of Siebel Diagnostic Data Collector (SDDC) commands for Microsoft Windows and UNIX.

Examples of SDDC Commands for Microsoft Windows

Some examples of Microsoft Windows SDDC commands are:

siebsnap.exe /c siebsnapw32.cfg -g
This command retrieves Siebel Gateway information using a configuration file named siebsnapw32.cfg.
siebsnap.exe /s
This command retrieves Siebel Server information.
siebsnap.exe /c siebsnapw32.cfg /s
This command retrieves Siebel Server information using a configuration file named siebsnapw32.cfg.

Examples of SDDC Commands for UNIX

Some samples of UNIX SDDC commands are:

siebsnap -s this_server -u sadmin -p sadmin
This command retrieves Siebel Server information using a username and password.
siebsnap -g gtway1
This command retrieves Siebel Gateway information with a Siebel Gateway name of gtway1.

About Reviewing Siebel Environment Data

The Siebel Diagnostic Data Collector (SDDC) utility creates output files and directories, as necessary, after each execution of the utility. Manually access these files to review the Siebel environment data, or send the output files to Oracle Global Customer Support for review by creating a service request (SR) on My Oracle Support.

The output files document the environmental setup information, application configurations, and log files if specified. For more information about collecting data using SDDC, see Process of Collecting Siebel Environment Data Using SDDC.

About SDDC Output

The SDDC Microsoft Windows utility creates output in the format of a root directory with additional subdirectories and files. For details on SDDC Microsoft Windows output file information and locations, see SDDC Output Under Microsoft Windows.

The SDDC utility on UNIX creates output in the format of compressed files. For details on SDDC output file information and locations on UNIX, see SDDC Output Under UNIX.

SDDC uses the following naming convention for the creation of the root directory and filenames:

ss_{GS|SS}yyyy-mm-dd_hh_mm_ss

where:

ss is siebsnap.
GS|SS is the Siebel Gateway or Siebel Server.
yyyy-mm-dd is the year, month, and day.
hh_mm_ss is the hour, minute, and second based on a 24-hour clock.

For example, the directory or filename ss_SS2017-05-08_17_10_30 represents information collected for a Siebel Server on 8 May at approximately 5:00 P.M. The directory or filename ss_GS2017-05-07_14_18_58 represents information collected for the Siebel Gateway on 7 May at approximately 2:00 P.M.

Common SDDC Output Files and Directories

The output from a Siebel Diagnostic Data Collector (SDDC) execution for a Siebel Server or the Siebel Gateway contains common directories and files. The following table provides further descriptions of the information collected in these files and directories.

Files and Subdirectories	Description
ReadMe file	Provides a snapshot of the files copied and directories created during the SDDC execution.
siebsnap log file	Provides a detailed log file of information collected during the SDDC execution. This file is available for SDDC only under Microsoft Windows.
Configuration file	Copies the configuration file used if one is specified during the SDDC execution. This file is only available for SDDC under Microsoft Windows.
siebel_info directory	Directory for Siebel environment information. This directory contains further subdirectories, which contain log files and details on the Siebel environment.
system_info directory	Directory for system information. This directory contains text files containing information on hardware, network statistics, operating system, and registry keys.
db_info directory	Directory for database version information. This directory contains text files containing details on the database version.

SDDC Output Under Microsoft Windows

Siebel Diagnostic Data Collector (SDDC) output under Microsoft Windows consists of files stored within a directory structure created by the utility. If a configuration file is not specified, then the default directory for the SDDC output under Microsoft Windows is the siebsnap directory under the Siebel Server root. To configure a different SDDC output location, update the OutputDirectory parameter in the SDDC configuration file. For information about configuring this parameter and other parameters in the SDDC configuration file, see Configuring SDDC Content Under Microsoft Windows.

SDDC creates additional directories within the siebsnap directory (or the configured output directory) based on whether SDDC collects data for a Siebel Server or the Siebel Gateway. For details on the time-sensitive directory naming convention for these root directories, see About Reviewing Siebel Environment Data.

For locations of the output contents produced for these entities, see:

For descriptions of the files and directory content of the SDDC output, some of which are common between each entity, see Common SDDC Output Files and Directories.

Siebel Server SDDC Output Under Microsoft Windows

With a Siebel Server Siebel Diagnostic Data Collector (SDDC) execution, the utility creates the root Siebel Server output directory, in the format ss_SSyyyy-mm-dd_hh_mm_ss, within the siebsnap directory (or configured output directory). Within this directory, the utility creates a directory of the format siebsrvr_server_name, where server_name represents the name of the Siebel Server profiled by the utility. The directory structure and contents appear as follows:

ss_SSyyyy-mm-dd_hh_mm_ss\
	siebsrvr_enterprise-name_server-name\
		Readme file
		Siebsnap log file
		Configuration file
		system_info\
		siebel_info\
		db_info\

Siebel Gateway SDDC Output Under Microsoft Windows

With a Siebel Gateway Siebel Diagnostic Data Collector (SDDC) execution, the utility creates the root Siebel Gateway output directory in the format ss_GSyyyy-mm-dd_hh_mm_ss within the siebsnap directory (or configured output directory). Within this directory, the utility creates a directory named gateway, which collects information on the Siebel Gateway. The directory structure and contents appear as follows:

ss_GSyyyy-mm-dd_hh_mm_ss\
	gateway\
		Readme file
		Siebsnap log file
		Configuration file
		system_info\
		siebel_info\

SDDC Output Under UNIX

On UNIX, Siebel Diagnostic Data Collector (SDDC) output consists of files compressed within a directory structure created by the utility. The default directory for the compressed files is the directory from which SDDC is run. To configure a different SDDC output location, use the -o parameter during the SDDC execution. For details on running the SDDC utility under UNIX, see Process of Collecting Siebel Environment Data Using SDDC.

The compressed output files have the extension .tar.z appended to the filename created by SDDC using the SDDC output naming convention. For a description of this naming convention, see About Reviewing Siebel Environment Data. The extensions .logarchive.tar.z, asserts.tar.z, and logarchive_asserts.tar.z also apply based on the log parameters specified during execution.

For descriptions of the output for each entity see:

For descriptions of the files and directory content of the SDDC output, some of which are common between each entity, see Common SDDC Output Files and Directories.

Siebel Server SDDC Collector Output Under UNIX

With a Siebel Server Siebel Diagnostic Data Collector (SDDC) execution, the utility creates the compressed file in the format ss_SS_yyyy-mm-dd_hh_mm_ss.tar.Z in the default output directory (or configured output directory). The information collected by the SDDC utility varies based on the parameter settings in the siebsnap.ini file. For information about configuring the siebsnap.ini file, see Configuring SDDC Content Under Microsoft Windows.

By default, the Siebel Server SDDC execution collects system information (system_info), database version information (database_info), and Siebel environment information (Siebel_info). For descriptions of the files and directory content, see Common SDDC Output Files and Directories.

Siebel Gateway SDDC Output Under UNIX

When Siebel Diagnostic Data Collector (SDDC) executes on a Siebel Gateway, it creates the compressed file in the format ss_GS_yyyy-mm-dd_hh_mm_ss.tar.Z in the default output directory (or configured output directory). The information collected by the SDDC utility varies based on the parameter settings in the siebsnap.ini file. For information about configuring the siebsnap.ini file, see Configuring SDDC Content Under Microsoft Windows.

By default, when SDDC executes on a Siebel Gateway it collects system information (system_info) and Siebel environment information (Siebel_info). For descriptions of the files and directory content, see Common SDDC Output Files and Directories.

Configuring SDDC Content Under Microsoft Windows

On Microsoft Windows, Siebel Diagnostic Data Collector (SDDC) can be configured to modify or enhance the amount of information collected during an SDDC execution. A Microsoft Windows SDDC configuration file is required by SDDC to modify any configurations to the output. The configuration file is referenced during the SDDC execution. By default, a configuration file is not included with the SDDC utility. It is recommended that you contact Oracle Global Customer Support before using configuration files by creating a service request (SR) on My Oracle Support. Oracle Global Customer Support provides configuration files based on the specific information you require. For information about SDDC configurations under UNIX, see Configuring SDDC Content Under UNIX.

The SDDC configuration file is divided into sections that can be used to configure the type of information and log files collected by the utility. Edit the configuration file with a text editor. The following table provides the SDDC configuration file parameters.

Section	Parameter	Specifies
[Main]	OutputDirectory	Specifies the directory location for the creation of the SDDC directory and output files.
	CollectLog	Specifies whether log files are collected.
	CollectLogArchive	Specifies whether log archive files are collected.
	CollectCrash	Specifies whether failure files are collected.
	CollectStderrFiles	Specifies whether standard error files are collected.
	CollectDump	Specifies whether back-up system files are collected.
	CollectAssert	Specifies whether assert and prefer files are collected.
	SiebelBinDir	Specifies the directory location of the `SIEBSRVR_ROOT` binary (`bin`) directory.
[Registry]	Key01	Specifies a registry key for collection.
	Key02	Specifies a registry key for collection.
	Key03	Specifies a registry key for collection.
[CrashFiles]	StartDate	Specifies the start date for a range of process failure files to collect.
	EndDate	Specifies the end date for a range of process failure files to collect.
	MatchingFiles	Specifies the process failure file extensions to collect. You can specify the collection of Siebel Flight Data Recorder (FDR) files in this section by identifying the extension FDR (for example, `*.fdr`).
[StderrFiles]	StartDate	Specifies the start date for a range of standard error files to collect.
	EndDate	Specifies the end date for a range of standard error files to collect.
	MatchingFiles	Specifies the standard error file extensions to collect.
[ProcessDump]	StartDate	Specifies the start date for a range of dump files to collect.
	EndDate	Specifies the end date for a range of dump files to collect.
	MatchingFiles	Specifies the dump file extensions to collect.
[AssertFiles]	StartDate	Specifies the start date for a range of assert files to collect.
	EndDate	Specifies the end date for a range of assert files to collect.
	MatchingFiles	Specifies the assert file extensions to collect.
[LogFiles]	StartDate	Specifies the start date for a range of log files to collect.
	EndDate	Specifies the end date for a range of log files to collect.
	MatchingFiles	Specifies the log file extensions to collect. You can specify the collection of Siebel Application Response Measurement (Siebel ARM) files in this section by identifying the file extension SARM (for example, `*.sarm`).
[LogArchive]	NumArchives	Specifies that SDDC collects log archive files from the `NumArchives` directory.
[LogArchive]	MatchingArchiveDir	Specifies the archive directories for collection.
[SiebelServer]	LogDir	Specifies the Siebel Server log directory in the case of not being able to connect to the Siebel Gateway.
[SiebelServer]	LogArchiveDir	Specifies the Siebel Server log archive directory in the case of not being able to connect to the Siebel Gateway.
[GatewayServer]	LogDir	Specifies the Siebel Gateway in the case the directory name is different than the default.

About SDDC Parameter Configuration

The StartDate, EndDate, and MatchingFiles parameters, which appear in several Siebel Diagnostic Data Collector (SDDC) configuration file sections, have common configuration details as shown in the following table.

Common Parameters Configuration Details

Common Parameters	Configuration Details
StartDate, EndDate	Set these parameters to specify collection of data between the two dates. If StartDate and EndDate are set, then do not set the MaxNumFiles parameter. Configure the dates in the following format: `dd-Month_Acronym-yyyy` where: dd is the integer of the date ranging from 01 to 31. Month_Acronym is the three-letter month acronym as follows: Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec. yyyy is the integer of the year. Another valid configuration selection for the StartDate and EndDate parameters is NONE. If NONE is entered for StartDate and a valid date is entered for EndDate, then files prior to the end date are collected. If NONE is entered for EndDate and a valid date is entered forStartDate, then files from the start date to the current date are collected.
MatchingFiles	Set this parameter to collect multiple file formats using a comma-delimited list. Wildcard characters are also applicable. For example, to collect files containing `siebmtsh` in the filename with the extension .dmp and files of the type siebmtshmw5409.dmp, enter: MatchingFiles=siebmtsh*.dmp,siebmtshmw5409.dmp

StartDate, EndDate

Set these parameters to specify collection of data between the two dates. If StartDate and EndDate are set, then do not set the MaxNumFiles parameter. Configure the dates in the following format:

dd-Month_Acronym-yyyy

where:

dd is the integer of the date ranging from 01 to 31.
Month_Acronym is the three-letter month acronym as follows: Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec.
yyyy is the integer of the year.

Another valid configuration selection for the StartDate and EndDate parameters is NONE. If NONE is entered for StartDate and a valid date is entered for EndDate, then files prior to the end date are collected. If NONE is entered for EndDate and a valid date is entered forStartDate, then files from the start date to the current date are collected.

MatchingFiles

Set this parameter to collect multiple file formats using a comma-delimited list. Wildcard characters are also applicable. For example, to collect files containing siebmtsh in the filename with the extension .dmp and files of the type siebmtshmw5409.dmp, enter:

MatchingFiles=siebmtsh*.dmp,siebmtshmw5409.dmp

Example of a Microsoft Windows SDDC Configuration File

The following listing is an example of a Microsoft Windows Siebel Diagnostic Data Collector (SDDC) configuration file. For parameter descriptions and configuration details, see Configuring SDDC Content Under Microsoft Windows.

[Main]
OutputDirectory=D:\siebel\SiebelAI\siebsnap
CollectLog=TRUE
CollectLogArchive=TRUE
CollectCrash=TRUE
CollectStderrFiles=TRUE
CollectDump=TRUE
CollectAssert=TRUE
SiebelBinDir = D:\siebel\SiebelAI\bin

[Registry]
Key01 = HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Tag
Key02 = HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Version
Key02 = 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\MaxHashTableSize
Key03 = 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\MaxFreeTcbs
Key04 = 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\MaxUserPort

[CrashFiles]
StartDate=05-May-2017
EndDate=10-May-2017
MatchingFiles = crash*.txt

[StderrFiles]
StartDate=05-May-2017
EndDate=10-Jun-2017
MatchingFiles = stderrout_*.txt

[ProcessDump]
StartDate=05-May-2017
EndDate=10-Dec-2017
MatchingFiles = *.dmp

[AssertFiles]
StartDate=05-Dec-2017
EndDate=10-Dec-2017
MatchingFiles=siebel_prefer*,siebel_assert*

[LogFiles]
StartDate=05-Dec-2017
EndDate=10-Dec-2017
MatchingFiles=*.log

[LogArchiveFiles]
StartDate=05-Dec-2017
EndDate=24-Dec-2017
MatchingFiles=*.log

[SiebelServer]
LogDir=M:\siebel\log
LogArchiveDir=M:\siebel\logarchive

[GatewayServer]
LogDir=M:\siebel\log

Configuring SDDC Content Under UNIX

You can configure the execution of Siebel Diagnostic Data Collector (SDDC) under UNIX to enhance the amount of information collected during an SDDC execution. Modify the SDDC INI file to record any configuration changes to the SDDC UNIX output.

The SDDC INI file, siebsnap.ini, is in the binary (bin) subdirectory of the Siebel Server root directory. To modify this file, open with a UNIX text editor.

For information about SDDC configurations under Microsoft Windows, see Configuring SDDC Content Under Microsoft Windows.

To configure SDDC to collect enhanced diagnostic information

With a text editor, open the siebsnap.ini file located in the binary (bin) subdirectory of the Siebel Server root directory.
Set specific parameters in the siebsnap.ini file based on how much information you require.
For details and descriptions of SDDC INI file parameters, see the following table.

Save the siebsnap.ini file.

INI File Parameter	Description	Default
OutputDirectory	Set this parameter to send the SDDC output to a different file location than the default.	The directory from which SDDC runs.
CollectLog	Set this parameter to TRUE to collect log file information.	TRUE
CollectLogArchive	Set this parameter to TRUE to collect log archive information.	TRUE
CollectCrash	Set this parameter to TRUE to collect process failure file information.	TRUE
CollectDump	Set this parameter to TRUE to collect dump file information.	TRUE
CollectAssert	Set this parameter to TRUE to collect assert file information. For more information about assert files, see About Other Siebel Server Log Files.	TRUE
CollectFDR	Set this parameter to TRUE to collect Flight Data Recorder (FDR) file information. For more information about these log files, see About Flight Data Recorder Log Files.	TRUE
CollectSARM	Set this parameter to TRUE to collect Siebel Application Response Measurement (Siebel ARM) information. For more information about these Siebel ARM files, see Siebel Performance Tuning Guide.	FALSE
CollectQuickFix	Set this parameter to TRUE to collect the following quick fix files if they are present: upgrade.txt, obsolete.txt, incompatible.txt, and log.txt.	TRUE
FileRetention	Set this parameter to the number of .tar.z files that you want to retain. It is useful to retain snapshots of the system in regular intervals and compare them. Once SDDC reaches the value set by the FileRetention parameter, it overwrites the oldest file.	2
StartDate, EndDate	Set these parameters to allow the SDDC utility to collect files between a range of dates. Configure the date values in the following format: `dd-Month_Acronym-yy` where: dd is the integer of the date ranging from 01 to 31. Month_Acronym is a three-letter month acronym as follows: Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec. yy is the integer of the last two digits of the year. If no value is set for EndDate, then all files are collected for the current date.	EndDate =Current Date
StartTime, EndTime	Set these parameters in conjunction with the StartDate and EndDate parameters to further refine the range of files collected by the SDDC utility. Configure the time values in the 24-hour clock format. If no values are set, then the default start time is 00:00 and the default endtime is 23:59.	StartTime =00:00, EndTime =23:59

Example of a UNIX SDDC Configuration INI File

The following listing is an example of the contents of a UNIX Siebel Diagnostic Data Collector (SDDC) configuration INI file. For parameter descriptions and configuration details, see Configuring SDDC Content Under UNIX.

OutputDirectory=
CollectLog=TRUE
CollectLogArchive=TRUE
CollectCrash=TRUE
CollectDump=TRUE
CollectAssert=TRUE
CollectFDR=TRUE
CollectSARM=FALSE
CollectQuickFix=TRUE
FileRetention=2
StartDate=01-May-17
StartTime=00:00
EndDate=20-May-17
EndTime=12:59