c_plan.sql

	This script prints execution plan for SQL which
	is already been explained in the PLAN_TABLE.

	It will list all available SQL statement ID from PLAN_TABLE
	and prompt you for the one you need to pring the explain plan for.

	To actually create an EXPLAIN PLAN for a SQL stmnt use the following:
	   SQL> explain plan
	   SQL> set statement_id = ``
	   SQL> for
	   SQL> 
	Before using explain plan you need to create PLAN_TABLE
	use ORACLE provided script for your platform ... RDBMS/ADMIN/UTLXPLAN.SQL

c_plan_script.sql

	Creates execution plan for a given SQL script

c_ses.sql

	Reports all sessions [ PID PROCESS IDLE MACHINE OSUSER ]
     allows tracing optionally calling
		SYS.DBMS_SYSTEM.SET_SQL_TRACE_IN_SESSION

c_user_rbs.sql

	Shows active (in progress) transactions

c_user_trace_all.sql

	Enables SQL TRACING for all sessions for a given USERNAME
	TIMED_STATISTICS should be set to TRUE

c_user_trace_me.sql

	Turns SQL_TRACE ON for your session, displays TRACE filename of your session

s_all_ratios_7.sql

	Oracle V7 performance tuning script
	REPORTS MANY RATIOS and other INFO as well.

s_locked_obj.sql

	            *** QUICK ***
	Reports the following:
	-  object locks from V$LOCKED_OBJECT
	   using PL/SQL loops since join of DBA_OBJECTS
	   and V$LOCKED_OBJECT is extremly slow
	- blocked objects from V$LOCK and SYS.OBJ$
	- blocked sessions from V$LOCK

s_sga_pga_used.sql

	Reports SID`s PGA usage
	some platforms have a limitation on maximum
	PGA you can have (32bit AIX - 256m)
	If SID`s PGA usage goes above this maximum
	session can get disconnected with the following error:
	  "ORA-3113: end-of-file on communication channel"

s_sga_sql_area.sql

	Dump stats and text of recent expensive	SQL
	m_timestamp has	been defined when this script is called
	--
	You can	adjust the constants in	the WHERE clause to suit your
	definition of what is expensive	on your	system.
	--
	The script tries to highlight code on the basis	of absolute cost,
	and on cost per	execution.
	--
	Spot the little	trick for avoiding divide by zero errors.  This
	can crop up very easily, especially if someone does an:
	   alter system flush shared pool,
     The SQL can stay in the pool but with the set back to zero.

s_top_cpu_usage.sql

	Reports TOP CPU usage by session

s_user_events.sql

	Reports minutes in wait per event for a SID

s_user_long_ops.sql

	Reports long running processes

s_user_redos.sql

	Reports sessions with highest redo sizes
     takes total redo size as denominator

s_user_ses_IO.sql

	Reports session IO with 10 sec interval

s_user_ses_trace.sql

	Reports Various Session Information
	usefull for runaway process tracing.

s_user_sql.sql

	This script reports SQL TEXT from v$sqltext
    

s_user_wait.sql

	Prints time waited per event for a specific SID

s_waiters.sql

	This script reports sessions that are currently waiting
	output DECODED locking information from v$lock and v$sessions
    

s_waitt.sql

	This script reports details from v$session_wait
	where wait_time = 0
	and seconds_in_wait >