GUGGI for ORACLE User Guide
Version 1.4.7
Impact Solutions
LLC
Contact: info@impact-sol.com
Disclaimer:
This
product does not come with any warranty and is intended for use as is. Impact Solutions LLC and the developers of this product will not be
responsible for any direct, indirect, incidental, or any damage of any kind in
connection with the use of this product or use of this User Guide.
The information contained in this guide is subject to change without
any information. This product
does not come with any warranty for the use of this product for any particular
purpose.
This product is protected by copyright law and
international treaties. Unauthorized
reproduction or distribution may result in severe civil and criminal
penalties.
You can also download a PDF version
of Guggi for Oracle User Guide here.
Table
of Contents
-
Introduction.
-
Installation Instructions.
-
Analyze Manager
-
Application Options.
-
Backup Statistics Manager
-
Download Binary Data and View Image
-
Freespace Manager
-
Guggi SQL Editor
-
Input / Output Statistics Manager
-
Invalid Objects Manager
-
Latches, Locks, Waits and Stats
-
Lock Manager
-
Login Window
-
Object Level Space.
-
Oracle Parameters.
-
PL/SQL Editor
-
PL/SQL Profiler
-
PL/SQL Trace
-
Reverse Engineer
-
Rollback Segment Manager
-
Schema Browser
-
Sessions Manager
-
SQL Editor
-
SQL Statistics Manager
-
Temporary Objects
-
Upload Binary Data and View Image
-
User / Schema Role Manager
-
View Linked Data Manager
Guggi for Oracle is a comprehensive, robust and scalable
database development, administration, and analysis tool.
The tool comes with a variety of features that can be used by
developers and DBAs on a regular basis. Use
of Guggi for Oracle will lead to reduced development and turn-round time.
The user guide discusses how to use Guggi for Oracle in great
detail. There are various tools
that are built into Guggi Oracle and each tool is covered in great detail.
Users of Guggi for Oracle are encouraged to send their comments, questions,
bug reports and enhancement requests at info@impact-sol.com.
Users can also join the discussion forum at http://groups.yahoo.com/group/guggiusers
Installing Guggi for Oracle is a simple process.
The product comes as a zipped file.
- Unzip
Guggi.zip.
- Double-click
on Guggi.msi. The installer
will be launched.
- If
the installer detects a previous version of Guggi, it will ask whether you
want to remove or repair Guggi. Select
remove Guggi.
- Once
the previous version is removed, double-click on Guggi.msi again and it
will install the latest version. This
way the installation is always clean.
It is recommended that Oracle's
OLEDB, which is also the native driver to connect
to Oracle, be used.
OraOleDB is installed when you install Oracle Client on your PC.
You may need to download MDAC
ver 2.7 or 2.8 to connect to Oracle using
OLEDB made by Microsoft. MDAC
is available from www.microsoft.com
It is recommended that the ODBC
driver provided by Oracle be used to connect to Oracle if you want to use the
ODBC connection instead of OLEDB connection.
Connection as SYSDBA and SYSOPER is supported via ODBC connection using
ODBC driver made by Oracle
PLAN_TABLE is provided with the
download as a SQL script. Execute
the script to create the table. Explain
Plan cannot be used until the plan table exists.
Analyze Manager is a built-in tool to analyze database
objects such as tables and indexes. Statistics
of the analyzed objects can also be viewed using Analyze Manager.
The tool can be invoked by clicking on 
or by selecting Analyzing Manager
from Tools menu.
View analyze
statistics
1. Select a
schema.
2. Select
Table or Index
Analyze statistics will be displayed for the selected
object type in the grid.
Objects can be
analyzed as follows:
1. Select
the schema where you want to analyze the objects.
You must have appropriate privileges to analyze objects in a given
schema.
2. Select
the type of object (table or index) that need to be analyzed.
3. Select
the appropriate Analyze Option. The
possible options are Compute Statistics, Delete Statistics, and Estimate
Statistics.
4. If you
chose Estimate Statistics option, enter the Sample percent to be taken into
consideration for analysis.
5. Check the
Analyze All Tables checkbox if you want to analyze all tables or indexes.
Otherwise select the object from the grid by clicking on the appropriate
record in the grid.
6. Click the
Execute button to analyze the object(s).
7. The
information in the grid will be updated once the objects are analyzed.
Number of records in a given table can be compared with
the data shown in the Num Rows column by selecting the table from the grid and
clicking on 
. This comparison is quite useful
in determining if the object has been properly analyzed or not.
Global settings for the application can be set using the
Application Options tool. The
tool can be launched by selecting “Application Options” from View menu
option. Settings have been
categorized under four (4) sections.
1. Startup
– Set the variables that will take effect after the application is launched
- First
window after login – Define
the first window that you want to be opened after the login.
The choice is between Schema Browser and SQL Editor.
- Maximum
number of records – Set the number of records displayed when browsing
through the table, view or synonym data in the Schema Browser.
- Select
Application Language – Set the language for the application menu.
Current choices are English, French, German and Spanish.
- Use
DBA% views instead of ALL% views – Set the database dictionary view to
be used to display objects in the Schema Browser. Check the box to use DBA% views. You must have DBA privileges to use this option.
You can set the option and use it when the application is already
launched. This means that you
would not need to re-login for the setting to take effect.
Just refresh the browser after the setting changes are made.
2. SQL
Editor – Set the variables and parameters as they relate to the SQL editor
a.
Set Font Name – Set the font for the editor text
b.
Set Font size – Set the size of font for editor text
c.
SQL window background color – Set the background color of SQL Editor text
area
d.
SQL datagrid background color - Set the background color of SQL Editor
datagrid
e.
Number of SQL statements in buffer – Set the number of statement that the
SQL window buffer will hold for the given instance of the SQL editor.
The buffer is available within the open instance of the window and is
not available across windows if multiple SQL Editor windows are open.
3. Schema
Browser - Set the variables and parameters as they relate to the Schema
Browser
- Set
Grid Background Color – Set the background color of the grid displaying
the object properties
- Grid
Back Color – Set the color of the cells of the grid displaying object
properties
- Object
List Background Color – Set the background color of the left hand panel
that displays the object list.
- Grid
Font - Set the font of the data in cells of the grid displaying object
properties
- Size
of Left Pane – Set the size of the tabular panel that displays the
object list. Size of the
panel cannot be more than 40% of the screen width.
If a higher value is set then the panel size will be reset to 40%
of the screen width.
4. Connection
Setup – Set the connection preferences
- Connection
Driver – Set the connection driver to use when connecting to Oracle
during login. The choices are
Microsoft Oledb driver, Oracle Oledb driver or ODBC driver.
The setting can be over-ridden at the time of login by manually
choosing the setting. Oracle Oledb driver is the preferred setting.
- Save
password – This sets the option to save the password in the registry.
The passwords are retrieved when the user clicks on the list of
username/database name displayed in the login window.
The user may choose not to save passwords in the registry for
security reasons.
Details regarding current or previous backups can be
viewed using the Backup Statistics Manager.
Click on 
or select “Backup Statistics
Manager” from the Database and DBA menu option to access the Backup
Statistics Manager.
Using this tool you can view Backup Logs, Details on the
last backup and whether it was a hot or a cold backup, and the progress of
current backup.
The information on the screen can be refreshed by
clicking 
from the toolbar.
Data in form of binary files such as images, documents,
spreadsheets stored in the database as BLOB can be downloaded using the View
Image tool 
. You can view images if the
binary file is an image file. Currently,
gif, jpg, ico, and bmp image formats are supported by the image viewer.
Binary files can be downloaded using Guggi for Oracle as
follows:
1. Select
the schema and the table where the BLOB data is stored
2. Select
the BLOB column where the binary data is stored.
Records from the table will be displayed once the BLOB column is
selected.
3. Records
can be filtered by clicking on 
.
4. Click on
the Save Image button and enter a file name where the downloaded binary file
will be saved.
5. Select
the record from the grid displaying data.
6. Binary
file will be downloaded and displayed in the Image viewer if it is an image
file. If the file is not an image
file, it will still be saved on the local disk but will not be displayed in
the image viewer.
You can select other records and display more images
without having to enter the file name each time.
Each time you click on a record, the binary file will be downloaded and
saved as the file entered in step 4. It
is not necessary to enter a file extension as the image viewer will detect if
it is an image file or not. If it
is not an image file, you can rename the file (through command prompt or
windows explorer) with the appropriate extension after the file has been
downloaded.
Freespace in the database at the tablespace and datafile
level can be viewed using the Freespace Manager. Click on 
or select “Free Space” from
the Database and DBA menu option to access the Freespace Manager.
The tool displays the freespace for every datafile in the
top data grid and freespace for every tablespace in the bottom datagrid.
Click on 
to refresh the information on
freespace.
Guggi SQL Editor is a stand-alone tool to execute SQL
statements. This is an
application that runs out of Guggi for Oracle.
Guggi SQL Editor can be invoked by clicking on 
or by selecting Guggi SQL Editor
Application from Tools menu option. All
the features and functionality of this application are similar to that of the
SQL-Editor.
File and session input / output statistics and system
events can be viewed using the Input / Output Statistics Manager.
Click on 
or select “Input / Output Stats”
from the Database and DBA menu option to access the Input / Output Statistics
Manager.
Click on the File I/O tab to view the File input/out
statistics.
Click on the Session I/O tab to view the session output
statistics. Sessions can be
managed through sessions manager also.
Invalid Objects Manager is a built-in tool that presents
the users with a single view of invalid objects in a schema and compiles them.
The tool can be opened by clicking on 
from the main toolbar or by
selecting Invalid Objects Manager from the Tools menu option.
Invalid objects
can be viewed as follows:
1. Select
the schema whose invalid objects are to be viewed.
2. All the
invalid objects are displayed in the grid.
If you want to view invalid objects across all schemas
then check the checkbox “Show objects for all schemas” and click the
refresh button 
Compile invalid
objects
Select the object that you wish to compile from the grid
and click on 
. The object will be compiled
otherwise an error message will be displayed.
If the object cannot be compiled then you would need to load the object
definition in the PL/SQL editor and compile the definition.
This DBA tool allows DBAs to monitor the wait events,
latches, locks and statistics for instance, SGA and sessions.
Click on 
or select “Latches, Locks,
Waits and Stats” from the Database and DBA menu option to access the
Latches, Locks, Waits and Stats manager.
Click on the appropriate tab to view the wait events or
latches or locks. Locks can be
managed using the Lock Manager.
To view the detail of the statistics of a particular
session, select the session from the grid on the left-hand-side in the Session
Statistics section. Session
statistics details will be displayed in the right-hand-side grid.
The information displayed by this tool can be refreshed
by clicking on 
in the toolbar.
Details and definitions of various parameters is beyond
the scope of this book.
Locks in the database can be managed using the locking
manager. You need to have system
privileges to use the Lock manager. Click
on 
or select “Lock Manager” from
the Database and DBA menu option to access the Lock Manager.
Lock manager displays the details for the following:
1. All locks
2. DML Locks
3. DDL Locks
4. Waiting
and Holding Sessions
You can release a lock by terminating the session.
Sessions can be terminated by selecting a record from the display grid
and clicking the 
button.
This action will ask the user to confirm whether the session is to be
terminated. Click on Yes to end
the session or click on No to leave the session as it is. If you are in the Waiters window then the user will be asked
if the Holding session is to be terminated.
If you click on Yes then the holding session will be terminated, if you
click on No then waiting session will be terminated, and if you click Cancel
then none of the two sessions will be terminated and the action will be
canceled.
Click on 
to refresh the lock information.
- Click
the
on the main toolbar.
Alternatively, go to File menu option and select New Connection.
- A
login window opens up. Enter
the user name (database schema name), password and database (TNS Name) in
the appropriate boxes. You
can also select the database and login from the grid on the right
hand-side by clicking on the row. Passwords
by default are saved in the registry.
- Select
the driver to connect to the database.
Select from OLEDB connection (Microsoft Driver for Oracle or Oracle
Driver for Oracle) or ODBC Connection (DSN Connection).
All three methods require the use of TNS name.
You can connect as SYSDBA or SYSOPER also.
Currently, SYSDBA and SYSOPER connections are supported via ODBC.
Oracle ODBC for Oracle version 9.2.0.3 higher is required.
- Click
OK.
- The
schema browser window will open up. The
user name and database name will be displayed in the window caption.
This will tell you which database you are currently logged into.
A button will be added at the bottom of the window.
Depending on the driver used to connect to Oracle, the connection
button will display.
for Oracle OleDb driver
for Microsoft OleDb driver for Oracle
for ODBC DSN connection
-
You can swap between connections by clicking on the appropriate
button.
Double-click on the Login / Database combination on the
right hand side and you will be connected to the database. Or click once on the combination and then click OK to connect
to the database. Password will be
retrieved from the registry.
Space occupied by various database objects such as
tables, indexes, materialized views can be viewed using the Space by Object
tool. Select “Space by object”
from the Database and DBA menu option to access the tool.
To view free space
1. Select a
schema from the dropdown box.
2. Space
occupied by various objects will be displayed in the grid.
3. To view
space taken by all the objects in the database across all schemas, check the
“Show objects for all schemas” checkbox, and click the refresh button
.
In order to free up space, select the object and either
truncate it (in case of a table), or drop it (in case of index, materialized
view, or table).
To drop object
Select the object to be dropped and click on 
.
To truncate table
Select the object to be truncated and click on 
.
To refresh the information displayed on the screen
Click on the refresh button 
Oracle parameters set in the current instance of the
database can be displayed. The
parameters can be viewed by selecting Oracle Parameters from Database and DBA
menu option.
Oracle parameters display can be refreshed by clicking on
.
The window can be closed by clicking on 
The PL/SQL Editor is used to develop objects such as
functions, procedures, packages, types, triggers etc. The tool can be invoked using one of the two options:
1. Click on
in the main toolbar.
2. Select
PL/SQL Editor from the Tools menu option.
3. Select
PL/SQL Code from Create Object menu option
Following features can be accessed by using the buttons
on the toolbar
1. Click on
to compile the code
2. Click on
to convert to upper case or
select “Change to upper case” from SQL and PL/SQL menu
3. Click on
to convert to lower case or
select “Change to lower case” from SQL and PL/SQL menu
4. Click on
to convert to initcap or select
“Change to init cap” from SQL and PL/SQL menu
5. Click on
to search for the text
6. Click on
to comment the code or select “Comment”
from SQL and PL/SQL menu
7. Click on
to uncomment the code or select
“Uncomment” from SQL and PL/SQL menu
8. Click on
to undo changes (alternatively
press Ctrl-Z). – under development
9. Click on
to redo changes (alternatively
press Ctrl-Y). – under development
10. Click on
to display a list of schemas and
tables. Click on the table and it
will be added to the PL/SQL code
11. Click on
to display a list of schemas,
tables and columns. Click on the
column and it will be added to the PL/SQL code
12. Click on
to close the PL/SQL editor
How to Use PL/SQL Editor
It is very simple and straight-forward to compile PL/SQL
code in the PL/SQL editor. Just
write the code in the editor and hit the compile 
button.
The status of the compiled code will be displayed below as “VALID”
or “INVALID”. If the status
is “INVALID” then click on 
to scroll through (forward) the
errors. You will be taken to the
line where Oracle finds the error. You
can click 
to scroll backward in the error
list. After fixing the error
click on compile again and you will see the status change to “VALID”
assuming all the errors have been fixed.
The editor comes with some of the most advanced editing
features. Some of the highlights
of the PL/SQL editor are:
1. Syntax
highlighting is enabled in the editor.
2. Bracket /
brace matching
2. Built-in
intellisense will display the columns of a table , procedures of a package
etc.
3. The
editor has multi-level redo and undo.
4. You can
indent the text by selecting the text and pressing the Tab key.
4. Press
Ctrl-Q on an object in the code and its details will be displayed in a
separate window. Alternatively,
you can select “Display Object Details” from SQL and PL/SQL menu option.
5. Click on
in the main toolbar to load a
file into the editor or select Open File from File menu or press Ctrl+O
6. Click on
to save the file on the local
disk or select Save File As from File menu or press Ctrl+S.
7. Click on
to print the code or select Print
from File menu or press Ctrl+P
8. Click on
to copy text or select Copy from
Edit menu or press Ctrl+C
9. Click on
to paste text or select Paste
from Edit menu or press Ctrl+V
10. Click on 
to cut the text or select Cut
from Edit menu or press Ctrl+X
11. Click on
to initiate search or select Find
from Edit menu or press Ctrl+F
12. Select
Replace from Edit menu or press Ctrl+H to replace text
Short-Cut Keys in PL/SQL Editor
Alt c : Append copy
Alt Delete : Delete line
Alt l : Convert the case of the word to lower case
Alt s: Swap the case of the word
Alt u : Convert the case of the word to upper case
Alt x : Append cut
Ctrl ] : Find matching bracket
Ctrl a : Select All
Ctrl Alt u : Swap the case of selected text
Ctrl Backspace : Delete till the start of the word
Ctrl c : Copy selected text
Ctrl d : Insert date
Ctrl Delete : Delete till the end of the word
(opposite of Ctrl Backspace)
Ctrl Down : Scroll view up
Ctrl End : Go to End of Text
Ctrl f : Find dialog
Ctrl f3 Find
next word
Ctrl g : Go to line
Ctrl h : Replace dialog
Ctrl Home : Go to beginning to text (opposite of Ctrl
End)
Ctrl left arrow key: Go to previous word
Ctrl p : print
Ctrl pagedown : Scroll view left
Ctrl pageup : Scroll view right
Ctrl right arrow key : Go to next word
Ctrl s : Save file
Ctrl u: Convert the selection to lower case
Ctrl up : Scroll
view down
Ctrl v : Paste
Ctrl x : Cut
Ctrl y : Redo
Ctrl z : Undo
F3 : Find next
Shift Alt t : Swap lines
Shift Ctrl ] : Find matching bracket select
Shift Ctrl c : Copy line
Shift Ctrl d : Insert
time
Shift Ctrl delete : Delete word
Shift Ctrl End : Highlight the text from the cursor
position till the end of the entire text
Shift Ctrl F3 : Find
previous word
Shift Ctrl Home : Highlight the text from the cursor
position till the beginning of text
Shift Ctrl L
: Mark line
Shift Ctrl Left arrowkey : Highlight the word from the
cursor position till the beginning of the word
Shift Ctrl Right arrowkey : Highlight the word from the
cursor position till the beginning of the word
Shift Ctrl u : Change the selected text to upper case
Shift Ctrl w : Mark the word
Shift Ctrl x : Cut line
Shift Delete : Delete from the cursor position till the
end of line
Shift Down : Highlight the text from the cursor position
till the next line
Shift End : Highlight the text from the cursor position
till the end of line
Shift F3 : Find previous
Shift Home : Highlight the text from the cursor position
till the beginning of line
Shift Insert : Paste
Shift Left : Highlight the text from the cursor position
till the previous character
Shift Pagedown : Highlight the text from the cursor
position till one page down
Shift Pageup : Highlight the text from the cursor
position till one page up
Shift Right : Highlight the text from the cursor position
till the next character
Shift Tab : Tab
in reverse
Shift Up : Highlight the text from the cursor position
till the previous line
Inefficiencies in the PL/SQL code can be identified by
running the PL/SQL profiler against the package, procedure or function (PL/SQL
block). PL/SQL Profiler can be
invoked by clicking on 
or by selecting PL/SQL Profiler
from Tools menu.
Steps to run the PL/SQL Profiler
1. Type the
script to execute the procedure in the window named Test Script.
A sample script may look like
Begin
Test_procedure (‘input var’);
End;
2. Enter a
name of the profiler run in the box named Profiler Run Name.
3. Click
to start the profiler.
4. Once the
profiler run is done and the statistics have been collected, the run name will
appear in the tab / grid below called “Runs”.
Analyze Profiler Runs
1. Several
profiler runs are displayed in the tab called “Runs”.
2. Select a
run by clicking on the record in the Run grid.
The name of the run appears in the “Profiler Run Name” box.
3. Click on
the “Results Summary” tab. Detailed
statistics of the run are displayed in the grid.
4. Select a
particular line in the “Results Summary” grid and a new tab displaying the
code will open up above. The line
whose statistics have been collected will be displayed in the new tab.
Delete a Run
1. Select
the run in the “Runs” tab.
2. Click on
the 
to delete the run.
3. Click on
to make the delete permanent.
In order to use PL/SQL profiler, profiler tables and the
dbms_profiler package must already exist in the database.
Trace information can be collected for execution of
PL/SQL code. Combined with PL/SQL
profiler this information can give useful insight into the performance
bottlenecks in the PL/SQL code. PL/SQL
trace can be invoked by selecting PL/SQL Trace from Tools menu or clicking
from the main toolbar.
Steps to run the PL/SQL Trace
1. Type the
script to execute the procedure in the window named Test Script.
A sample script may look like
Begin
Test_procedure (‘input var’);
End;
2. Click on
to start the trace.
4. Once the
trace run is done and the statistics have been collected, the run will appear
in the tab / grid below called “Runs”.
Analyze Trace
1. Several
trace runs are displayed in the tab called “Runs”.
2. Select a
run by clicking on the record in the Run grid.
The name of the run ID appears in the “Run ID” box.
3. Click on
the “Results Summary” tab. Trace
of the run are displayed in the grid.
Delete a Run
1. Select
the run in the “Runs” tab.
2. Click on
to delete the run.
3. Click on
to make the delete permanent.
In order to use PL/SQL trace, trace tables and the
dbms_trace package must already exist in the database.
DDL of database objects can be reverse engineered and
saved into a file. The file can
later be executed in another schema to create the objects. Reverse engineering tool can be accessed by clicking on
in the main toolbar or by
selecting “Reverse Engineer” from Tools menu.
1. Select
schema from where you want to reverse engineer the objects.
2. Select
the database object types to be reverse engineered. You can select all the object types or some of the object
types.
3. Select a
file where the reverse engineered DDL will be saved.
Future Enhancements
1. Reverse
engineer each object type into its own file
2. Add more
objects
3. Add the
option to not reverse engineer storage parameters.
4. Reverse
engineer DDL for individual objects.
5. Display
reverse engineered objects as an ERD.
Rollback segments in the database can be analyzed using
the Rollback Segment Manager tool. The
tool can be opened by clicking on 
in the toolbar or by selecting
“Rollback Segment Manager” from Tools menu option.
Details about rollback segments such as hit ratio, size,
high water mark, number of times extended or wrapped or shrank etc. can be
viewed. Further details about the
sessions currently being supported by the rollback segment can be viewed
selecting the rollback segment from the grid.
The rollback segment can be selected by clicking on the appropriate
record in the grid. Any SQL
currently being executed on the rollback segment will also be displayed.
The screen can be refreshed by clicking on the 
button.
A new rollback segment can be created by clicking on the
button.
Create Rollback Segment window will open and you can enter appropriate
parameters to create the rollback segment.
Schema browser can be used to browse through several
database objects. Details of the
features and functionalities available for various objects in the Schema
Browser are given below.
The Schema Browser can be launched by any one of the
following methods:
1. Click
on the main tool bar
2. Select
Schema Browser from the Tools menu
3. Right-click
on the connection button at the bottom of the application and select Schema
Browser. There should be at least
one active window for the selected connection for the Schema Browser to open.
Following features can be accessed by using the buttons
on the toolbar
1. Click on
to refresh the contents of the
Schema Browser
2. Click on
to see additional objects
3. Click on
to close Schema Browser
4. Click on
to hide the Objects Pane and
maximize the Details Pane (Right Hand Side pane).
5. Click on
to display the Objects Pane
again.
6. Click on
to view the relationship of the
selected table with other tables in the same schema in an Entity Relationship
Diagram (ERD) format.
A list of all the clusters contained in the schema is
displayed.
These features can be accessed by using the buttons on
the toolbar
1. 
Create a cluster
2. 
Drop a cluster
Following information can be viewed for a given cluster
1. Details
of the cluster
A list of all the constraints contained in the schema is
displayed.
These features can be accessed by using the buttons on
the toolbar
1. 
Create a constraint
2. 
Drop a constraint
3. 
Enable constraint
4. 
Disable a constraint
5. 
Enable all constraints
6. 
Disable all constraints
Following information can be viewed for a given cluster
1. Details
of the constraint
2. Columns
of the constraint
A list of all the Consumer Groups defined in the database
is displayed.
These features can be accessed by using the buttons on
the toolbar
1.
Drop a Consumer Group
2. 
Create a Consumer Group
Following information can be viewed for a given Consumer
Group
1. Details of the Consumer
Group
2. Grants
A list of all the contexts defined in the database is
displayed.
Following information can be viewed for a given Context
1. Details of the Context
A list of all the database links contained in the
schema or in the database is displayed.
These features can be accessed by using the buttons on
the toolbar
Create a database link-
Drop a database link
Following information can be viewed for a given database
link
- Details
such as owner, connect user, target etc
A list of all the Dimensions contained in the selected
schema is displayed.
Following information can be viewed for a given Dimension
1. Details of the Dimension
2. Levels in the Dimension
3. Hierarchies in the Dimension
A list of all the directories contained in the
schema is displayed.
These features can be accessed by using the buttons on
the toolbar
Create a directory-
Drop a directory
Following information can be viewed for a given Directory
- Details
such as directory path, owner
A list of all the External Tables contained in the
selected schema is displayed.
Following information can be viewed for a given External
Table
1. Details
of the External Table
2. File
location of the External Table
A list of all the functions contained in the selected
schema is displayed. If the
function is valid then a green filled circle appears before the function name.
If the function name is invalid then a red filled circle appears before
the function name.
These features can be accessed by using the buttons on
the toolbar after selecting the view
Create a function-
Drop a function
Load the function code in
the PL/SQL editor window
Recompile a function
Following information can be
viewed for a given function
- PL/SQL
code
- Objects
used by the function
- Grant
on the function
A list of all the indexes contained in the selected
schema is displayed. If the index
is partitioned then 
appears before the index name.
These features can be accessed by using the buttons on
the toolbar
Create a new index-
Drop an index
Rebuild an index
Following information can be viewed for a given index
- Details
about the function
- Statistics
- Partitions
(for partitioned indexes)
- DDL
Script
A list of all the Index Types defined in the database is
displayed.
Following information can be viewed for a given Index
Type
1. Details of the Index Type
2. Operator
A list of all the Java Classes, Java Data, Java Resource,
Java Source contained in the selected schema is displayed.
These features can be accessed by using the buttons on
the toolbar
1. Filter on
Java Class, Data, Resource or Source
2.
Drop Java Class, Data,
Resource or Source
Following information can be viewed for Java Class, Data,
Resource or Source
1. Details
A list of all the Jobs defined in the database is
displayed.
Following information can be viewed for a given Job
1. Details of the Job
2. Currently running Job
A list of all the libraries contained in the schema
is displayed.
These features can be accessed by using the buttons on
the toolbar
Create a library-
Drop a library
Following information can be viewed for a given Operator
1. Details of the library such
as file spec, status etc
A list of all the materialized views contained in the
schema is displayed.
These features can be accessed by using the buttons on
the toolbar
1. 
Create a materialized
view
2.
Drop a materialized
vie
Following information can be viewed for a given
materialized view
- Columns
in the view
- Definition
of the view
- Data
in the view
- Grants
on a view
- Objects
used by the view
- Objects
that use the view
A list of all the operators contained in the schema is
displayed.
Following information can be viewed for a given Operator
Binding and Arguments details
A list of all the packages contained in the schema is
displayed. If the package is
valid then 
appears before the procedure
name. If the package is invalid
then 
appears before the procedure
name.
These features can be accessed by using the buttons on
the toolbar
Create a package-
Drop a package
Execute a
package
Load the code in the PL/SQL
editor
Recompile a package
Recompile all
packages
Following information can be viewed for a given package
- PL/SQL
code – package specification and package body. Search the procedure/function in the package
- Objects
used by the package
- Objects
that use the package
- Grants
A list of all the policies defined in the database is
displayed.
Following information can be viewed for a given Policy
1. Details of the policy
A list of all the procedures contained in the schema is
displayed. If the procedure is
valid then 
appears before the procedure
name. If the procedure is invalid
then 
appears before the procedure
name.
These features can be accessed by using the buttons on
the toolbar
