Transitioning From Oracle® Solaris 10 to Oracle Solaris 11.2

Exit Print View

Updated: December 2014
 
 

Observability, Debugging, and Tuning Features

    Observability, debugging, and tuning feature changes include the following:

  • DTraces feature changes – DTrace feature changes include the following:

    • errexit option – An additional DTrace consumer option that specifies whether a DTrace script should exit upon encountering an error has been added. This enhancement changes the previous DTrace behavior, where an error is reported, but the script does not terminate.

    • llquantize() action – Support for a new linear-log quantize aggregating action has been added. This aggregating action enables you to collect data in linear-step buckets (similar to the existing lquantize() action) across multiple magnitudes simultaneously.

    • Scalability improvements – Internal processing for DTrace includes some scalability improvements that support better performance on larger systems.

    • Structure and bitfield enhancements – The expected behavior of user-defined structures and bitfields has been modified to adhere to the appropriate ABI specification for padding. This change might require you to remove any variables that were previously introduced as a workaround from your DTrace scripts.

    • tracemem() enhancements – This action includes an additional argument that specifies the number of bytes to display, which might be less than the number of bytes that was traced.

    For additional information, see Oracle Solaris 11.2 Dynamic Tracing Guide .

  • Observing users and processes – Use the –u option with the netstat to observe which users and processes are responsible for network connections. See netstat (1M) and Displaying User and Process Information in Administering TCP/IP Networks, IPMP, and IP Tunnels in Oracle Solaris 11.2 .

  • System tuning features – The following system tuning feature enhancements have been made: