Formats and Sizes

Global Parameters relating to logfiles

The following Database sp083_system_parameters apply to the FRU Process, the API Agent and the Gantt Router:

update sp083_system_parameters.value = <0/1> where name = glob_trace_cycle_enabled;

select component_id, sp400.trace_mask_no, sp412.description from sp400, sp412
where sp400.trace_mask_no = sp412.trace_mask_no(+);

Select sp083.value, sp412.description from sp083, sp412
where sp083.value = sp412.trace_mask_no
and name = ‘glob_trace_mask_no’;

Select sp083_system_parameters.value from sp083_system_parameters where name = ‘glob_trace_max_file_size’;

Select component_id, max_log_file_size from sp400_components;

Whereabouts

Log files are created in <SPHOME>/<instance>/log where 

Naming

In either mode of working,  there will be at least two files created for each process. The first is a 'header' file that will include all the start up information for that process and will have a name of the form <filename>.h.

If glob_trace_cycle_enabled is set true this means that once the size of the log file reaches this limit, it "wraps around" and starts writing again from the start of the file. So only 1 further file will be created.

If glob_trace_cycle_enabled is set false 

this means that, once the size of the log file reaches its limit, the file is closed and a new file is opened. The naming convention used for each new file is <filename>.1, <filename>.2 etc

This second form of logging has been provided so that it is possible to work in a mode where no logging is lost, which can be helpful when Support are trying to identify the cause of a specific error. However, it should be noted that creating new files will mean that filestore will be used up at a fairly rapid rate and hence some form of monitoring and archiving of the files off to another area may be required to prevent the system running out of space.

Content and Trace Levels

All entries are timestamped

• The timestamp used is the time according to the host machine on which the process is running. 
• Timestamps are also used to form some file names. The timestamp used is the time according to the host machine on which the master system monitor is running.
• Timestamps are always expressed in the SP default timezone (reference sp083_system_parameters value 'tz_Default') (see Time Zones).

Differing levels of information may be written to the log (also known as the "trace level"), and these levels may be set on a per component basis. The default level is held in the Database sp083_system_parameters table. Setting Trace Levels gives further details.

The levels of information can be configured at runtime by ServicePower personnel but this facility is not available as a third-party Support function.

When ServiceOptimizer is first set up, the logging level is set to what is considered a ‘default’ level (up to ‘DEBUG1’).  For approximately 95% of the time this level is good. However, for detailed call information, the ‘SOAP’ level tracing may be switched on for the APIAgent.