Oracle Light Weight Availability Collection Tool FAQ

About the Oracle Lightweight Availability Collection Tool

Question:

What is the Oracle Lightweight Availability Collection Tool?

Answer:

The Oracle Lightweight Availability Collection Tool is what its name implies, a lightweight standalone availability collection solution that utilizes the existing Oracle Explorer Data Collector transport for transporting availability data back to Oracle. It is installed on each Solaris operating system instance and is enabled for SPARC x86 containers and zones. It replaces the Configuration and Service Tracker (CST) and the Oracle backend support architecture. This lightweight solution is less customer impacting than the average CST deployment. The Oracle Lightweight Availability Collection Tool allows the user to track system availability, such as boot, panic and halt events.

Question:

Why was the Oracle Lightweight Availability Collection Tool created?

Answer:

The Oracle Lightweight Availability Collection Tool was created to augment or replace Oracle's previou availability collection tools to accommodate the customer's unique site requirements and add additional hardware model support.

Question:

On what architecture or machines does the Oracle Lightweight Availability Collection Tool run?

Answer:

The Oracle Lightweight Availability Collection Tool currently runs on Solaris™ SPARC, and Solaris x86 architectures. It supports zones and containers.

Question:

Is the Oracle Lightweight Availability Collection Tool supported on Solaris and Fujitsu (SPARC 64)?

Answer:

Yes, it is the common code base that is compiled for SPARC and x64 platforms, thus the Oracle Lightweight Availability Collection Tool does work on both 32 and 64 bit processors.

Question:

What is the version of Oracle Explorer Data Collector required to collect Oracle Lightweight Availability Collection Tool data ?

Answer:

Oracle Explorer Data Collector 6.0 or higher is required to collect the datagrams of Oracle Lightweight Availability Collection Tool 3.0 or higher. Although, the previous versions of Oracle Explorer Data Collector & Oracle Lightweight Availability Collection Tool may work, but it is recommended that Explorer 6.0 or higher is used to collect the Oracle Lightweight Availability Collection Tool 3.0 (or higher) datagrams, otherwise Oracle may not be able to provide availability analysis based on older version Oracle Lightweight Availability Collection Tool datagrams.

Question:

Why is Configuration and Service Tracker (CST) being decommissioned?

Answer:

Voice of the Customer (VOC) indicates that CST is costly for both the customer and Oracle to manage and operate. Because of this, the adoption rate is very low and in some cases it is required by contract.