Misc general SQL-tool scripts
COMP.TXT
Just another (but short) way to generate a compile script.
LOCKS.TXT Show
information on locking session, locked object and locked mode.
DYN_SQL.TXT
A simple procedure to generate dynamic SQL.
Script
to show errors and their exact location
The script SHOWERR.TXTwill
create error messages showing the position of errors in
procedures, functions and packages. It might be practical
to append this script to any
procedure- or function-creating script to get an immediate
description and
information of the location of the errors. Example
of output
Foreign
keys (referencing & referenced)
The script FOK.TXT
will extractDDL to create foreign keys for any table owner, table name
and foreign key constraint name.
The script PRIK.TXT
will extractDDL to createprimary keys for any table owner and table name.
Abstract datatypes
(queues, stacks) using tables
QUEUE.TXT Implementation
of queues with synchronized restricted section
executable code using standard standard
Oracle tables.
Session-related
scripts
PRV_SESS.TXT OK,
you're logged in and have a session on the Oracle server.
Your job is to update some seldom used
table. You don't want to stop other
users from using the system, but if
they mess with your table (having triggers
disabled), they surely should be forced
to rollback their transactions.
Lock-related scripts
LOCKS.TXT
WILL SHOW SESSION, OBJECT, LOCKING MODE FOR CURRENTLY LOCKED
OBJECTS.
Tuning and Optimization
SLOWSTAT.TXT CURSOR1.TXT
Storage scripts
Object scripts
Other scripts
SQL executed on the server
(v$sqlarea)
SQL_SPY1.TXT
AND SQL_SPY2.TXT SHOWS
WHAT IS HAPPENING ON THE
ORACLE SERVER. RUN SQL_SPY1.TXT FIRST,
START ANY PROGRAM,
AND THEN VIEW SQL-STATEMENTS ISSUED
WITH SQL_SPY2.TXT
Avoiding mutating trigger
DEFRWTRG.TXT
SHOWS HOW TO AVOID MUTATING TRIGGERS BY DEFERRING
THE ROW LEVEL ACTIONS FROM ROW
LEVEL TRIGGER TO THE STATEMENT
TRIGGER WITH THE USE OF A PACKAGE
AND PL/SQL TABLES.
Code
generating scripts
CRE_INS.TXT
AND CRE_UPD.TXT ARE
SCRIPTS TO HELP IN CODING E G
TRIGGERS WHERE ONE OFTEN HAVE TO
WRITE TEDIOUS INSERT- AND UPDATE-STATEMENTS
FOR TABLES HAVING A LOT OF (SAY
120) COLUMNS.
|