

There are a number of trials courts, including many courts of limited jurisdiction such as a specific family court. Oracle specific metric.The judicial system of Louisiana is slightly more complex than some other states. These parameters control the maximum number of user processes, sessions created by users on the system, and transactions allowed on the system at one time. Its value is determined by parameters such as SHARED_POOL_SIZE, PROCESSES, SESSIONS, and TRANSACTIONS at startup. The installed Oracle products and options determine the fixed size, which changes only if the installed products are altered or removed. Total size for the SGA (System Global Area).

Maximum size for the SGA (System Global Area).
#DISKTIVITY FREE#
Oracle SGA Pool Wastage - large pool free percentage Oracle SGA Pool Wastage - Java pool free percentage Oracle SGA Pool Wastage - shared pool free percentage
#DISKTIVITY FULL#
The database Dump Full metrics mapping information is available below: It gives an instance overview of all processes that logged on. Total number of logons from the time when the instance started. Long tables can be defined as tables that do not meet the short table criteria as described in table scans (short tables). Try increasing the size of the initialization parameter SORT_AREA_SIZE. Sorts that require I/O to disk are quite resource-intensive. Number of sort operations that required at least one disk write. Redo blocks written divided by this statistic equals the number of blocks per write. Total number of writes by LGWR to the redo log files.
#DISKTIVITY PLUS#
This number equals the value of physical writes direct plus all writes from buffer cache. Total number of data blocks written to disk. A soft parse is a check on an object already in the shared pool, to verify that the permissions on the underlying object have not changed. Total number of parse calls (hard and soft). Total number of calls (user and recursive) that executed SQL statements. Number of times a CURRENT block was requested.
#DISKTIVITY UPDATE#
Number of times a consistent read was requested for a block.Ĭlosely related to "consistent changes", this statistic counts the total number of changes that were part of an update or delete operation applied to all blocks in the SGA. Workloads that produce a great deal of consistent changes can consume a great deal of resources. Number of times a user process applied rollback entries to perform a consistent read on the block. This number equals the value of physical reads direct plus all reads into buffer cache. Total number of data blocks read from disk. Rate at which full table scans of long tables occur. The database ArchFull metrics mapping information is available below: The total amount of free space on the physical disk, in bytes. The total amount of used space on the physical disk, in bytes The database space not yet allocated for data, logs and control files The amount of used space within the allocated space The amount of free space the total allocated data can grow on. The file system metrics mapping information is available below:įree space available for data files (DB Data Allocated Size - DB Data Used Size). The average number of physical IO write requests per second for this disk The average Bytes per second written to this disk device during the interval. The average number of physical IO read requests per second for this disk The average Bytes per second read from this disk device during the interval. The average time spent by I/O requests into the queue. The average service time for I/O requests that were issued to the device. The average number of physical I/O requests per second for this disk. The percentage of time in which this disk device was busy transferring data during the interval. The disk activity metrics mapping information is available below: The percentage of utilization of the swap space. The number of pages scanned per second by the VMM during the interval. The subobject specifies the CPU id.ĭisk Average Service Time aggregated by host Percentage of time the CPU was in system mode during the interval for each CPU of the system. Sum of the physical memory sizes of the data and stack regions for processes that are currently on the run queue or processes that have executed recently, in percentage over physical memory The percentage of physical memory in use during the interval. The percentage of time the CPU was in user mode during the interval. Percentage of time the CPU was not idle during the interval. BMC TrueSight Capacity Optimization metric
