The list below is a comprehensive list of features offered by Lighty For Oracle. You can carry out a free 30-day trial software in order to measure the extent possible.
Once the purchase order is made, the licenses are sent within 24 hours via email.
The license includes the name of the company or the user and the end date.
This data is included in a license file.
No, Lighty is only available online and downloadable from the site.
You must have at least 200 mb of free space on disk.
Regarding memory requirements, it is setting in the software options.
However a minimum of 256 MB of memory is required. For more comfort opt for 512MB.
No, no need oracle client.
The software will connect to databases using JDBC drivers supplied.
No, no need to be administrator of the position.
No, no need. The software is fully autonomous and works with a Java engine integrated during installation.
To install lighty, unzip the file lighty.zip.
The Uncompress proccess create ceates a directory where are all the libraries and utilities required for its operation are in.
The software launch is done by double-clicking the lighty.exe.
To uninstall Lighty,
On Windows, open the explorer and delete the Lighty directory (created during installation.)
On the Mac, go to Applications and then delete the Lighty directory.
The software is compatible with versions 10gR2, 11gR1, 11gR2 and 12C.
The software supports standard and enterprise editions.
You can log in with an account with DBA privilege
Connecting as SYSDBA gives you access to some reports not available for other types of account. These are the data of the datas cache, hidden parameters, the contents of the alert file.
Lighty allows you to specify for each connection, if the Diagnostic and Tuning Packs are licensed.
Some features of the software will thus inaccessible.
Yes, the software is able to extract data from a statspack repository to allow you to easily see activity statistics.
The support is provided by mail to firstname.lastname@example.org , Do not hesitate to contact us for any problems, bugs, suggestions, comments.
No, the trial version is fully functional.
A popup window appears each time you launch the software and indicate the number of days remaining for trial period.
By cons, you can not save more than 5 connections in Lighty.
Lighty is a supervision and monitoring software for oracle database performance.
The software is compatible with 10.2, 11.1, 11.2 and 12.1 oracle versions. It works with the Standard or Enterprise versions (with or without Diagnostic and Tuning Pack).
|View of the performance of multiple databases simultaneous|
|Vision of the activity in real time|
|Vision of past activity (based on L-ASH ASH or for standard versions)|
|Allows to easily explore the historical data in the AWR or Statspack|
|Allows viewing all major statistics related to SQLs and sessions orders|
|Easy navigation among the many information bases through SQLs reports|
Lighty works on Windows, Mac OSX and Linux Operating Systems.
An option is provided in the software to allow you to use more or less memory as needed. The minimum memory required is 256 MB with a maximum of 1024 MB. The default and recommended value is 512 MB.
The occupied disk space is about 200 MB
Lighty is distributed as a self-contained application in a compressed file (Zip Format) on windows platforms.
Just unzip the file to the desired location. A Lighty directory is created with a tree containing all the files required for its operation. Then start Lighty.exe
|A version of the JRE (Java Runtime Environment) is included (version 7 update 51)|
|You don't need an oracle client|
|You do'nt need to be administrator on your computer|
|The software does not create any object in the database|
The software update can be done in 2 ways. In 2 cases, your preferences will be preserved.
A window appears telling you if you use the latest version. If it doesn't, you can choose to automatically download and install the latest version. (An internet connection is required. For Internet access through a proxy, it may be necessary to set up access through software options.)
Removing the Lighty tree then decompressing the zip file.
The free trial version is fully functional. However, you can not declare more than 5 connections. When the evaluation period is over, only the monitoring multi bases remains accessible.
If you do not possedez licenses, we offer the alternative use of Light and Statspack ASH.
L-ASH (Lighty ASH) is a small utility to simulate functionalities of ASH. This utility takes a snapshot every 10 seconds of active sessions. These images are stored in a table in order to be viewed in Activity Viewer Screen
Connect to the database as sysdba
Run script installation.sql (ex : sqlplus sys/password@TNS_ALIAS as sysdba @installation.sql)
The script asks two parameters: the password and the default tablespace for the ASHSTAT account
The script creates the following items:
A user named ASHSTAT
L_ASH - Table containing sessions statistics
PARAMETERS - Parameters table
1 Package LIGHTY_PKG
LIGHTY_PKG.SET_RETENTION to change the retention statistics (by default, 7 days)
LIGHTY_PKG.SNAP to take a snapshot of active sessions
LIGHTY_PKG.PURGE to remove old data (retention stored in the PARAMETERS table)
ASHSTAT."L-ASH" - Runs every 10 seconds LIGHTY_PKG.SNAP
ASHSTAT."PURGE L-ASH" Executed once a day to perform the deletion of old data
sqlplus / as sysdba SQL*Plus: Release 18.104.22.168.0 Production on Tue Feb 4 20:15:49 2014 Copyright (c) 1982, 2011, Oracle. All rights reserved. Connected to: Oracle Database 11g Enterprise Edition Release 22.214.171.124.0 - Production With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP, Data Mining and Real Application Testing options SQL> @installation installation of L-ASH V1.0 www.orachrome.com ----------------------------------- Choose ASHSTAT user's password ----------------------------------- Enter value for ashstat_pwd: ashstat Choose the Default tablespace for the ASHSTAT user --------------------------------------------------- Enter value for default_tablespace: users ... Creating ASHSTAT user ... Installing required packages SQL> alter session set current_schema=ASHSTAT; Session altered. SQL> set echo off feedback on; ... Create table L_ASH Table created. 1 row created. 1 row created. Table created. Index created. ... Create Package Lighty_pkg l_pkg112 1 row selected. Package created. No errors. Package body created. No errors. ... Create Scheduler jobs "L-ASH" and "PURGE L-ASH" PL/SQL procedure successfully completed. PL/SQL procedure successfully completed. ... View Scheduler jobs "L-ASH" and "PURGE L-ASH" OWNER JOB_NAME STATE START_DATE REPEAT_INTERVAL NEXT_RUN_DATE RUN_COUNT -------------------- -------------------- --------------- -------------------- -------------------------------------------------- -------------------- ---------- ASHSTAT L-ASH SCHEDULED 02/04/2014 20:16:03 FREQ=SECONDLY;INTERVAL=10 02/04/2014 20:16:03 0 ASHSTAT PURGE L-ASH SCHEDULED 02/04/2014 20:16:03 FREQ=DAILY;BYHOUR=22;BYMINUTE=0;BYSECOND=0 02/04/2014 22:00:00 0 2 rows selected.
Statspack is a tool allowing you to take on a regular basis the statistics of your base. Less complete than the AWR, it remains an interesting solution.
There are several possible catch levels with statspack (the default is 5). The various levels and descriptions are visible by querying the table STATS$LEVEL_DESCRIPTION.
To fully benefit from Statspack with Lighty, it is recommended to pass the catch level 7 (includes among other statistics on segments).
You can directly update the table STATS$STATSPACK_PARAMETER. (Requires to have at least a snapshot by instance):
Rem Rem -------------------------------------------------------- Rem Rem Update Statspack Level to 7 Rem and sqls captured to 100 Rem Rem V1.0 Rem 15/09/2014 - Creation Rem Rem www.orachrome.com Rem -------------------------------------------------------- Rem update stats$statspack_parameter set SNAP_LEVEL=7,NUM_SQL=100 ; commit;
To take statspack snaposhots, you have to edit the statspack.snap from perfstat diagram at regular intervals (usually every hour).
On the RAC environments it is necessary to perform the procedure on each instance.
The PL / SQL following program allows to set up the programming snapshots statspack on standalone or RAC databases.
This PL/SQL code create a program and an execution job for instance. On databases in RAC mode, to avoid possible contentions, jobs are started sequentially
Thus, only the instance 1 job is scheduled to run at regular intervals. At the end of his performance, it triggers the release of the job on instance 2, which triggers the job is running on the instance 3, etc ...
Rem Rem -------------------------------------------------------- Rem Rem This PL/SQL will create a hourly job Rem to take a statspack snapshot Rem Rem RAC Aware Rem Rem V1.0 Rem 15/09/2014 - Creation Rem Rem www.orachrome.com Rem -------------------------------------------------------- Rem Rem Example of Dropping jobs and programs in a 2 instance Rac Database Rem exec dbms_scheduler.drop_job('STATSPACK_SNAP_1'); Rem exec dbms_scheduler.drop_job('STATSPACK_SNAP_2'); Rem exec dbms_scheduler.drop_program('PROG_STATSPACK_SNAP_1'); Rem exec dbms_scheduler.drop_program('PROG_STATSPACK_SNAP_2'); Rem -------------------------------------------------------- Rem Installing jobs and programs Rem -------------------------------------------------------- DECLARE newjob SYS.job_definition; newjobarr SYS.job_definition_array; cpt NUMBER := 0; name VARCHAR2(50); command VARCHAR2(80); jobenable BOOLEAN; cptinstances NUMBER := 0; repeatInterval varchar2(400); startDate date; BEGIN newjobarr := sys.job_definition_array(); select count(*) into cptinstances from gv$instance; newjobarr.extend(cptinstances); -- Add a job and a program for each instance FOR rec IN (select inst_id, max(inst_id) over () maxInstId,lead(inst_id,1,0) over (order by inst_id) nextInstId from gv$instance) LOOP name := 'STATSPACK_SNAP_' || rec.inst_id; command :=''; IF (rec.inst_id < rec.maxInstId) THEN command := 'dbms_scheduler.enable(''STATSPACK_SNAP_' || rec.nextInstid || ''');'; END IF; DBMS_SCHEDULER.CREATE_PROGRAM( program_name=> 'PROG_' || name, program_action=>'BEGIN perfstat.statspack.snap;' || command || ' end;', program_type=>'PLSQL_BLOCK', number_of_arguments=>0, comments=>'', enabled=>TRUE); IF (rec.inst_id =1) THEN jobenable := true; repeatInterval := 'FREQ=HOURLY'; startDate := trunc(sysdate,'HH')+1/24; ELSE jobenable := false; repeatInterval := null; startDate := null; END IF; -- Create a JOB_DEFINITION object type newjob := sys.job_definition(job_name => name, job_style => 'REGULAR', program_name => 'PROG_' || name, repeat_interval => repeatInterval, -- start_date => trunc(sysdate,'HH')+1/24, start_date => startDate, auto_drop => FALSE, enabled => jobenable, instance_id => rec.inst_id); -- Add it to the array cpt := cpt +1; newjobarr(cpt) := newjob; END LOOP; -- Call CREATE_JOBS DBMS_SCHEDULER.CREATE_JOBS(newjobarr, 'TRANSACTIONAL'); END;
You can also schedule a job for deleting old snapshots.
The following PL/SQL script create a daily job (launched every day at 11:00pm) to delete statspack snapshots. The snapshots history is defined like the L-ASH tool by the ASHSTAT.LIGHTY_PKG.SET_RETENTION package. (Default retention 7 Days).
Rem Rem -------------------------------------------------------- Rem Rem This PL/SQL will create a daily job (Runs every day at 11PM) Rem to purge the statspack snapshots Rem RAC Aware Rem Rem L-ASH must be installed Rem The retention is stored in the table ASHSTAT.PARAMETERS Rem Default : 7 Days Rem Rem V1.0 Rem 15/09/2014 - Creation Rem Rem www.orachrome.com Rem -------------------------------------------------------- Rem grant select on ashstat.parameters to perfstat; exec dbms_scheduler.drop_job('"PERFSTAT"."PURGE STATSPACK"'); BEGIN sys.dbms_scheduler.create_job( job_name => '"PERFSTAT"."PURGE STATSPACK"', job_type => 'PLSQL_BLOCK', job_action => 'DECLARE DAYS NUMBER := 7; BEGIN SELECT value INTO days FROM ashstat.parameters WHERE name=''retention''; FOR instances in (select sp.dbid,INSTANCE_NUMBER FROM stats$database_instance sp,v$database v WHERE sp.dbid=v.dbid) LOOP FOR snapshot_range IN (SELECT min(snap_id) MIN_SNAP_ID ,max(snap_id) MAX_SNAP_ID FROM stats$snapshot WHERE dbid=instances.dbid AND instance_number=instances.instance_number AND snap_time < trunc(sysdate)-DAYS) LOOP IF (SNAPSHOT_RANGE.MIN_SNAP_ID IS NULL) THEN EXIT; END IF; statspack.purge( i_begin_snap => snapshot_range.MIN_SNAP_ID , i_end_snap => snapshot_range.MAX_SNAP_ID , i_snap_range => true , i_extended_purge=> false , i_dbid => instances.dbid , i_instance_number => instances.instance_number); END LOOP; END LOOP; COMMIT; EXCEPTION WHEN OTHERS THEN RAISE_APPLICATION_ERROR(-20100,''PERFSTAT.STATSPACK PURGE Error'' || SUBSTR(SQLERRM, 1 , 1000)); END; ', repeat_interval => 'FREQ=DAILY;BYHOUR=23;BYMINUTE=0;BYSECOND=0', start_date => systimestamp, job_class => '"DEFAULT_JOB_CLASS"', comments => 'Purge statspack repository', auto_drop => FALSE, enabled => FALSE); sys.dbms_scheduler.set_attribute( name => '"PERFSTAT"."PURGE STATSPACK"', attribute => 'job_weight', value => 1); sys.dbms_scheduler.set_attribute( name => '"PERFSTAT"."PURGE STATSPACK"', attribute => 'auto_drop', value => TRUE); sys.dbms_scheduler.enable( '"PERFSTAT"."PURGE STATSPACK"' ); END; /
Rem Rem -------------------------------------------------------- Rem Rem Statspack Jobs Rem Rem V1.0 Rem 15/09/2014 - Creation Rem Rem www.orachrome.com Rem -------------------------------------------------------- Rem set lines 500 pages 40 head on col JOB_NAME for A20 col OWNER for A20 col REPEAT_INTERVAL for A50 col START_DATE for A20 col NEXT_RUN_DATE for A20 select OWNER,job_name,state,to_char(START_DATE,'MM/DD/YYYY HH24:MI:SS') START_DATE, REPEAT_INTERVAL, to_char(NEXT_RUN_DATE,'MM/DD/YYYY HH24:MI:SS') NEXT_RUN_DATE, run_count from dba_scheduler_jobs where regexp_like(job_name,'STATSPACK') /
In summary, the sequence of actions to perform to set up a complete management statspack (while logged sysdba and having first installed L-ASH):
To recognize these two utilities into the software, you must report them to the properties of a connection. To do this, open the properties of a connection, and select the check boxes.
This toolbar can be hidden. All options in the toolbar are also available in the menus or via keyboard shortcuts.
|Ctrl + G||Passage in multiple connections mode|
|Ctrl + I||Moving to single mode connection|
|Ctrl + M||Displays the connection configuration page|
|Ctrl + A||Adding a new connection|
|Ctrl + O||Displays the options window|
|Ctrl + N||Shows or hides the floating window connections|
|Ctrl + R||Shows or hides the floating window reports|
|Ctrl + Q||Shows or hides the floating window of the statistics of a SQL|
|Ctrl + S||Shows or hides the floating window statistical registration|
Lighty uses floating windows in its GUI. These windows can be grouped, displaced on one edge of the main window, resized, hidden. Some can be maximized by double clicking on the title bar or icon.
|Window||Can be maximized||Can Be Moved|
|List of SQL reports|
The dashboard allows through a single page to provide an overview of different activity statistics. Its management is done with the icons . This single page is organized into tabs. You can add a new tab from the button . Each tab can be named. You can also close a tab by the appropriate button. Within each tab, organize your table using predefined widgets. By default, the table has 3 columns dedicated to widgets. Decrease / increase the number of columns using the button . The gadgets available for the dashboard are visible by clicking on the . To integrate a widget to the dashboard, simply drag and drop the widget to the desired location using the mouse. Widgets are resizable (width and height). You can also customize or remove any gadget on the dashboard. A single gadget can be opened multiple times.
Some have options. In this case, the icon appears at the top right of the widget.
The principle of the dashboard is used in 2 screens (by default, pre-filled with some widgets) :
Hyperlinks allow you to easily navigate among the many dispobiles information. They are blue.
In the reporting screen, the history of your browsing is displayed at the top of the window allow you to return instantly to the desired information.
Filters are ubiquitous in different Windows on the software. They can isolate the desired information easily
There are 3 types of filters :
This component visually informs you of the activity of an identifier in a range of time.
The example below shows you the sql consumption in a time range (11:50 a.m. to 2:10 p.m.)
More information on a single component:
The implementing beaches
The type of activity
The activity time
Many screens offer the refreshing feature of displayed information.
In this case, the buttons allow you to manage this refresh.
For automatic refresh, select the check box and the frequency in the list (10s, 30s or 60s). A countdown is displayed.
To manually refresh, click the icon.
According to the type of information displayed, the export button allows various operations :
The addition is done through the , by the menu or the shortcut Ctrl + A.
Add Connection is done in 3 steps.
The connection name must be unique.
By default, a 10-session connection pool is proposed and used. You can increase or decrease this pool.
The type and application allow you to group your connections according to their functions.
You can easily identify the connections later (in the menu or in the Control Panel)
Set the user and password.
A connection as sysdba can view some special reports (data cache, hidden settings, log alert content ...)
The password can be saved (in encrypted format) so you do an entry for each connection.
The connection configuration can be done by entering the server name, port, and the name of the instance or service name. You can also enter a complete chain of connection (TNS Entry for example)
Choose here the packs used by the database. By default, since the 11G version, the parameter control_management_pack_access defines the use of Diagnostic and Tuning packs.
If you do not use these packages, you can install L-ASH (simulation tool for the ASH functionality). Then check the "L-ASH installed" option
You can also check the Statspack option if it is installed.
This window is accessible from the "Options" menu, with the icon or by the shortcut Ctrl + M
The window lists all defined connections. You can modify their configuration, or delete a connection.
You can list the connections via the "Connection List" menu or the Floating window of the same name.
The menu includes connections by type and application.
3 tabs helps to navigate among the statistics.
The tab "Activity Viewer" allows you to view the activity of a database. Based on data from the feature "Active Session History", this screen helps you in understanding the activity.
In the middle of this screen is the main graph.
This graph represents, over a range of time consumed, the activity of your database divided by class waiting and CPU consumption.
To help isolate the desired information, several options are available:
This is done using the buttons
You can also choose the exact date and time of start and end by clicking the "Custom" button and entering the debin/end date/time.
The text filter allows you to choose a sql id or a session id.
You can also show / hide the list of predefined filters using the button
These filters are configurable (button ) from a list of twenty items.
This is done using the mouse. Select a portion of the graph to display the corresponding statistics.
The buttons in the graphic (or right-click menu of the mouse) allow you to save, copy to clipboard, select the zoom, delete zoom, ...
This choice is made by selecting the check box .
Once selected, all data will be displayed only from the SGA and more precisely the ASH buffer.
The button allows you to see the retention, the number of lines and the size of that buffer (for instance).
|Widget||Details||Timeline Component||Possible Options|
|Graph||View the activity of a subset as a type of graph or pie chart history||
Pie chart or historical
Choice of Statistics (Server, program, user, customer identifier, module, action sql operation, sql, system event)
Fine-tune the information by posting SQLs for a session.
Fine-tune the information by posting the events for a SQL system. The execution plan is displayed next to the SQL. When there are several plans, the count of plans is shown. Possibility then to view the plans by clicking on the tree icon.
Fine-tune the information by posting SQLs for PL/SQL.
|Show activity by service, module, action||Grouping on one or more criteria|
|Machine, Program, User||Show activity per machine, program, user||Grouping on one or more criteria|
|Client Identifier||Show activity by customer ID|
|Waiting class, system event||Show activity per class waiting and/or system event|
|Instance, Service||Show activity by Instance and/or Service||Grouping on one or more criteria|
|Segments||Displays usage segments|
|PGA, Temporary Space Usage||Displays the PGA or the maximum temporary space used in the time interval||Grouping by SQL or by Session|
|Blocking sessions||Show blocking sessions and the sessions blocked in the time interval|
The control panel shows the activity of the database in real time .
It is organized as a dashboard allowing you to customize the layout.
|Some widgets show the instantaneous activity|
|The supervised SQLs|
|Long operations sessions|
|The use of temporary spaces, PGA|
|The blocking sessions|
|Some widgets show incremental statistics computed between 2 snapshots.|
|The system statistics|
|The "Latches" type locks|
|The event histograms|
|The segments used|
|Some widgets show incremental statistics computed between 2 snapshots.|
The tab "Reports" allows you to explore the statistics of your database. These reports are distributed by category and subcategory for simplicity.
|Db Informations||Db Information, Properties/Usage, Parameters, Memory Components, Alerts, Alert Log, FRA, Backups|
|Physical Design||Tablespaces, Db Files, Redo Logs, Archiving Activity|
|DB Statistics||Current Activity (ASH), Past Activity (AWR), Past Activity (Statspack), Db Statistics, Statistics/Optimizer|
|Sessions||Sessions, Blocking Sessions, Session Long Operations|
|SQLs||Running Sqls, Monitored SQLs, Top 100 SQLs, Not Shared Sqls|
|Segments/Tables||Objects by Schema, Tables / Indexes / ...|
|Locks / Transactions||Active Transactions, Transactions Recovering, Dictionary Cache Activity|
A Floating Window type is dedicated to statistics from SQL. It is automatically displayed when you click the SQL ID present on the screens.
You can also enter the SQL ID (Possibly the "child" number) to search manually.
|Find all the informations related to a SQL|
|The various execution plans (including those stored in the AWR repository or statspack)|
|The execution statistics from the AWR or statspack|
|The sql usage displayed in a timeline component|
|Runtime statistics in the cache (SQL Area)|
|The profiles, patches, and present baselines|
A Floating Window is dedicated to statistics for a session. It is automatically displayed when you click the SID of this session on the various screens.
You can also enter the SID to search manually.
|Find all the informations related to a session|
|The optimizer's environment|
|The statistics of the session(incremental and global)|
|The current transaction|
|The execution history of the Timeline form.|
You can import and export databases connections between Lighty softwares.
You can kill a session from the Lighty interface
You have the ability to export reports in CSV format
You can launch a snap Statspack / AWR and L-ASH/ASH (depending on the configuration of your bases) to perform analysis on the appropriate period
You can enable and disable a trace on a session from Lighty (the path of the generated log file is displayed in the software)
1.5.0 - 07 March 2017
1.4.6 - 25 January 2017
sqlplus / as sysdba Alter session set « _oracle_script »=true ; DROP USER ASHSTAT CASCADE ;
1.4.5 - 1 December 2016
1.4.4 - 02 June 2016
1.4.3 - 03 March 2016
1.4.2 - 18 June 2015
New way to manage user licenses.
1.4.1 - 15 April 2015
The main novelty is that Lighty now supports version 12C container mode.
It is now very easy to navigate through the "pluggable" dbs and see their activity.
When one connects to a container-type database, a dropdown list appears in the top right of Lighty.
This list display all dbs pluggable.
You can select a base to see its business. It is also possible to see the activity of all of the container base (this is by default)
New design with lighter colors, wider tabs, ...
A home page has been added to check the tips and articles on using Lighty (internet connection required)
Java Runtime Version 8u40
It is now possible to return to the default settings of the dashboard.
When seeking the execution plans for SQL, you can now also search the AWR or statspack repository.
Tab displaying the execution plan is compatible with the feature "adaptive design" of Oracle 12C.
Even more statistics displayed by SQL Child.
Over the course of the year