4 Oracle Light Weight Availability Collection Tool Use Cases and Cause Codes

This chapter describes the Oracle Lightweight Availability Collection Tool use cases and explains how to setup the cause codes.

Cause-Code

You can set the cause-codes for the outages post event. This enables the user to have more control in maintaining the availability metrics for the host. There are two modes you can use for a cause code: interactive and non-interactive.

Note:

The following cause code example is the same in both the interactive and non-interactive modes.

Interactive Mode

In interactive mode, a list of all available cause codes for that level is displayed from which you can choose the appropriate code. The following shows the information displayed on the screen when using the Interactive mode.

## Interactive mode##
$logtime -M 2
 
Level-1 Cause Codes
- - - - - - - - - -
   0) - Undefined
   1) - Planned
   2) - Unplanned
 
Section? 1
 
Level-2 Cause Codes
- - - - - - - - - -
   0) - Undefined
   1) - System Management
   2) - System Hardware
   3) - System Software
    4) - Application
   5) - Network
   6) - Environmental
 
Selection? 4
 
Level-3 Cause Codes
- - - - - - - - - -
   0) - Undefined
   1) - Patch Installation
   2) - Application Upgrade
   3) - Dabase Maint
   4) - App/Db Schema Mgnt
   5) - Configuration
   6) - Batch Processing
   7) - Application Install
   8) - Application Removal
   9) - Other
 
Selection ? 8
Modification of event was successful.

Non-interactive Mode

In non-interactive mode, you can set the cause codes using the CLI by invoking logtime. The following shows the command line display when using the non-interactive mode:

## Non-Interactive mode##
## Same functionality of setting the codes L1=1, L2=4, L3=8 is achieved by 
non-interactive invocation of logtime##
 
$ logtime -M 2,1,4,8
<Modification of event was Successful.

For example, you should mark a weekly planned upgrade or a planned power outage as a Planned outage with the appropriate reason behind it. In such cases, you can use the logtime utility to modify the originally logged outage event and attach a suitable cause code to it. You can attach up to three levels of cause codes for an outage event.

You can modify any outage event that has already occurred by invoking the logtime as shown:

logtime -M <event# that has to be modified> <L1,L2,L3 causecodes>

This can be done interactively or non-interactively, as described above.
There is also another invocation of logtime with -L option. This allows you to modify the cause code for the last occurred outage.

logtime -M -L <L1, L2, L3 cause codes>
You can get a list of all permissible cause codes for each level by invoking the logtime as shown:

logtime -M

ltreport

You can use the CLI ltreport to generate simple availability reports and view them locally for a single host. It can also be used to generate and view availability reports of other hosts' data using the -i option for one host at a time. Thus, this utility facilitates an offline reporting mechanism. The following are examples of various invocations of the ltreport:

bash-3.00# ltreport -v
 
     Hostname: bs6-s0 Hostid: 8325cb1    Zone:global
     -----------------EVENTS-----------------
     Event[  0]: epoch    Thu Apr 24 08:36:44 2008 -06:00
     Event[  1]: boot   Thu Apr 24 08:36:44 2008 -06:00
Availability: 100.000% (total) 100.000% (adjusted)
   Monitored: 00d-00-00m-00      Since: Thu Apr 24 08:36:44 2008 -06:00s
      Uptime: 00d-00-00m-00
    Downtime: 00d-00h-00m-00s
           Planned: 00d-00h-00m-00s
         Unplanned: 00d=00h-00m-00s
         Undefined: 00d-00h-00m-00s
 
bash-3.005# ltreport -x
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<single_system_availability_results>
    <systemInfo>
       <hostName>bs06-s0</hostName>
       <hostId>83254cb1</hostId>
       <zoneName>global</zoneName>
       <timeZone>US/Mountain</timeZone>
       <sysSerialNumber>3254CB1\uffff</sysSerialNumber>
       <OSName>SunOS</OSName>
       <OSVersion>5.10</OSVersion>
       <cpuArchitecture>sparc</cpuArchitecture>
       <productType>Serverblade1</productType>
       <lwactVersion>3.1</lwactVersion>
     </systemInfo>
  <event type="epoch" utc="1209047804" timeStamp="Thu Apr  24 08:36:44 2008 -06:00" 
    up="0" dwnPlnd="0" dwnUnplnd="0" dwnUndef="0" cksum="1448" />
  <event type="boot" utc="1209047804" timeStamp="Thu Apr  24 08:36:44 2008 -06:00" 
    up="556" dwnPlnd="0" dwnUnplnd="0" dwnUndef="0" cksum="143d" />
   <event type="time" utc="1209048360" timeStamp="Thu Apr  24 08:36:44 2008 -06:00" 
up="556" dwnPlnd="0" dwnUnplnd="0" dwnUndef="0" elapsed="556" 
totAvail="100.000" adjAvail="100.000" cksum="1c0e" />
</single_system_availability_results>
bash-2.05# ltreport -i
bash-2.05# cp /var/log/83cde40d.lwact.xml  /tmp/myhost.xml
bash-2.05# ltreport -i /tmp/myhost.xml
 
        Hostname: noyal Hostid: 83cde40d
 
    Availability: 100.000% (total) 100.000% (adjusted)
       Monitored: 02d-20h-28m-03s  Since: Tue Apr  1 04:32:39 2008 -25200 ..isdst=1
          Uptime: 02d-20h-28m-03s
        Downtime: 00d-00h-00m-00s
               Planned: 00d-00h-00m-00s
             Unplanned: 00d-00h-00m-00s
             Undefined: 00d-00h-00m-00s