Oracle Enterprise Manager Concepts Guide

Contents Index Home Previous Next

CHAPTER 11. Managing Schema Objects

This chapter describes how to use Schema Manager to administer schema objects in your database. This chapter assumes that you have read Chapter 7, "Overview of the Database Tools," and are familiar with the interface elements of the database tools.

With the Schema Manager, you can create, alter, or drop schema objects such as clusters, database links, execution plans, PL/SQL, sequences, snapshots, snapshot logs, synonyms, tables, and views. You can also create, alter, or drop schema objects using the SQL Worksheet.

The topics in this chapter are:

Starting the Schema Manager

To start the Schema Manager, click on the Schema Manager icon in the Launch palette or choose Schema Manager from the Tools menu.

Note: You can change the database connection with the Change Database Connection option in the File menu. For information, see "Application Menus" [*].

After the Schema Manager has successfully connected to a database, the schema tree list is displayed on the left side of the Schema Manager window. The tree list consists of a series of schema object containers, one for each type schema object contained in the main Schema Objects container. The name of the connected database is displayed next to the the Schema Objects container.

The display on the right side of the window is determined by the objects selected on the left side of the screen. The right side may contain a multi-column scrolling list, property sheet.

For general information about multi-column scrolling lists, see page 7 - 10. For general information about dialog boxes, see page 7 - 11. For general information about property sheets, see page 7 - 12. An example of a Schema Manager window is shown in Figure 11 - 1.

Figure 11 - 1. Schema Manager Window

Schema Menus

The Schema manager includes four standard menus, File, View, Log, and Help, plus the Object menu. The Object menu contains the following menu options:

Schemas and Schema Objects Container

The Schema Objects container contains all database objects pertinent to database schema. Specific schema object types are listed alphabetically under the Schema Object container.

Alternatively, you can view the tree list by schemas defined within the connected database. To view the tree list by defined schemas, select By Schema from the View menu. All schemas defined in the database are listed alphabetically in the tree list as containers. You expand the specific schema container in the tree list to view the complete list of schema object types defined for that schema.

Clusters Container

The Clusters container is comprised of information about clustered tables.

A cluster is a group of tables that share the same data blocks because they share common columns. Clustered tables are often joined in queries.

Clusters Multi-Column List

The Clusters multi-column list displays when the Clusters container is selected from the tree list. The Clusters multi-column list contains the following columns:

Schema Name of the schema to which the cluster belongs. This column is not shown when viewing a particular schema.
Cluster Name of the cluster.
Type Type of cluster (index or hash)
Tablespace Tablespace in which the cluster is stored.

Creating a Cluster

To create a new cluster, choose Create from the Object menu. The Create Object dialog box appears. Select Cluster from the Create Object list and click OK. The Create Cluster property sheet appears. This property sheet contains the following pages:

Cluster: General Page

The General page contains the following:

Cluster Name of the cluster being defined.
Schema Name of the schema containing the cluster. The drop-down list contains all schemas available in the current database.
Size An estimate of the total amount of space required to store the average number of rows associated with each cluster key value or hash value (kilobytes or megabytes)
Type: Index Cluster When selected, indicates that an index is specifically defined for the cluster.
Type: Hash Cluster When selected, indicates that related rows are stored in the same data block.
Hashkeys: Maximum number of unique hash values that can be generated by the hash function.
Hash Function: Specify that Oracle's internal hash function use the current function (Default) or bypass the Oracle internal hash function and specify a SQL expression.
Cluster Key Columns Column: Name of the column
Datatype: CHAR, VARCHAR2, NUMBER, LONG, RAW, LONG RAW, DATE, ROWID, MLSLABEL
New: Displays the Column Details dialog box.
Edit: Displays the Column Details dialog box for the cluster key column selected in the list.
Remove: Deletes a cluster key column that is selected in the list.

Create Cluster: Storage page

The Storage page contains the following information:

Tablespace Name of the tablespace that contains the database object being defined.
Extents Initial Size: Size of the object's first extent.
You can enter a value, the minimum being the size of two data blocks. The default value is the size of five data blocks.
Next Size: Size of the next extent to be allocated for the object.
The default value is the size of five data blocks. The smallest permissible value is the size of one data block.
Increase Size by: Percent by which each extent grows (after the second extent) compared to the previous extent. The default value is 50%.
Minimum Number: Total number of extents allocated when a segment is created.
The default value is one. You can enter a value of one or greater.
Maximum Number: Total number of extents, including the first, that an Oracle database can allocate for the object.
You can enter a value of one or greater. The default value varies based on the database platform.
Space Usage % Free: Percentage of space in each of the object's data blocks that is reserved for future updates to the object.
You can enter values from 0 to 99. The default value is 10.
% Used: Minimum percentage of used space that an Oracle database maintains for each data block of the object.
A block becomes a candidate for row insertions when its used space falls below the % Used value.
You can enter a value from 1 to 99. The default value is 40.
Number of Transactions Initial: Initial number of transaction entries allocated within each data block allocated to the object.
You can enter a value from 1 or 2 (for clusters and indexes) to 255.
Maximum: Maximum number of concurrent transactions that can update a data block allocated to the object.
You can enter a value from 1 to 255.
Freelists Lists: Number of free lists for each of the free list groups for the table, cluster, or index.
You can enter a value of one or greater. The default value is one.
Groups: Number of groups of free lists for a table, cluster, or index.
You can enter a value of one or greater. The default value is one.

Create Like Cluster

To create a cluster with parameters that are similar to an existing cluster, select a snapshot from the clusters multi-column list and then select Create Like from the Object menu. The Create Cluster property sheet appears with the appropriate parameters filled in.

Editing a Cluster

To edit an existing cluster, select a specific cluster in the tree list. A property sheet with the snapshot's current parameters is displayed.

Database Links Container

The Database Links container contains database links defined within the connected database.

A database link allows you to access a remote database. For information about database links, see the Oracle7 Server Concepts.

Database Links Multi-Column List

The Database Links multi-column list displays when the Database Links folder is selected in the tree list. The list contains information about the status of links defined within the connected database. For information about database links, see the Oracle7 Server Concepts.

The columns of the Database Links list are described below:

Schema The name of the schema containing the link. This column is not shown when viewing a particular schema.
Database Link The name of the database link.
Username The name of the user the database connects as when connecting to the remote database.
Host SQLNet connect string to the host.
Created Date on which the link was created.
If you view the tree list by schema, a Database Links container appears in an alphabetical list of all schema objects under each schema in the tree list. When the Database Links container is selected, the multi-column list is displayed.

Creating a Database Link

To create a new database link, choose Create from the Schema manager Object menu and select Database link from the list in the Create Object dialog box. Click OK. The Create Database Link property sheet appears. This property sheet consists of a single page:

Create Database Link: General Page

The General page contains the following information:

DB Link The name of the database link being defined.
When you create a database link, you can specify a valid Oracle identifier.
Public Specifies that the database link be available to all users (public) or only the owner (private).
The setting defaults to Private when creating a new database link.
Connection Details Username: Username used to connect to the remote database.
If the Username field is left blank during the creation process, the newly defined link acquires the username of the person accessing the remote database.
Password: Password used to connect to the remote database.
If the Password field is left blank, the database link uses the password of the person using the database link.
Service Name: Specifies the database specification of a remote database.
Test Checks the validity of the Username, Password, and Service Name when a database link is created. Only available when altering a database link.
Creation Date Displays the date of database link creation. By default, the current date is displayed.

Create Like Database Link

To create a database link with parameters that are similar to an existing database link, select a specific link from the database link multi-column list and then select Create Like from the Object menu. The Create Database Link property sheet appears with the appropriate parameters filled in.

Viewing a Database Link

To look at the parameters for an existing link, select a specific database link in the tree list. A property sheet with the link's current parameters is displayed in the Details view. The property sheet is nearly identical to the Create Database Link property sheet with the following exceptions:

Functions Container

The Functions container contains an alphabetical list of functions defined within the database.

A function is a PL/SQL subprogram that executes an operation and returns a value at the completion of the operation. A function can be either built-in or user-named. For information about functions, see Oracle7 Server Concepts.

Functions Multi-Column List

The Functions multi-column list displays when the Functions container is selected in the tree list. The list contains information about the status of links defined within the connected database. For information about database links, see the Oracle7 Server Concepts.

The columns of the Functions list are described below:

Schema Name of the schema containing the function. This column is not shown when viewing a particular schema.
Function Name of the function.
Created Date on which the function was created.
Last Modified SQL* Net connect string to the host.
Status Current status of the function (Valid or Invalid).

Creating a Function

To create a new function, choose Create from the Schema Manager Object menu and select Function from the list in the Create Object dialog box. The Create Function property sheet appears. The property sheet consists of a single page:

Create Function: General Page

The General page consists of the following information:

Name Name of the function being defined.
Schema Name of the schema containing function. The drop-down list contains all schemas available in the current database.
Recompile Recompile the PL/SQL source for the function so that it can be stored and executed from within the database.
Dates Created: Date the function was originally created.
Last Modified: Date the function was last modified.
Status Current status of the Function (valid or invalid).
Show Errors: Displays the Error Message dialog box listing the errors encountered while trying to compile the function source. This button is only enabled when the function status is invalid.
Source Function SQL statements or PL/SQL constructs.

Create Like Function

To create a function with parameters that are similar to an existing function, select a function from the function's multi-column list and then select Create Like from the Object menu. The Create Function property sheet appears with the appropriate parameters filled in.

Altering a Function

To alter an existing function, select a specific function in the tree view. A property sheet with the function's current parameters is displayed in the Details view. Click Apply after changing the desired parameters to recompile the function and save the changes. To change the parameters back to their origingal setting, click Revert.

The Indexes Container

The Indexes container contains table indexes defined within the database.

An index is an optional structure associated with a table, used by Oracle to locate rows of that table quickly and can be used to guarantee that every row is unique. For information about indexes, see the Oracle7 Server Concepts.

Indexes Multi-Column List

The Indexes multi-column list appears when you select the Indexes folder in the tree list. This multi-column list contains the following information:

Schema Name of the schema. This column is not shown when viewing a particular schema.
Index Name of the index.
Table Owner Owner of the table for which the index is created.
Table Table for which the index is created.
Table Type Type of table (table or cluster).
Status Status of the table (Valid or Invalid).
When you view the tree list by schema, an Indexes container appears listing all available schema in alphabetical order. Selecting the Indexes folder displays a multi-column list of indexes contained in the parent schema.

Creating an Index

To create a new index, choose Create from the Object menu and select Indexes from the list in the Create Object dialog box. The Create Index property sheets appear. The property sheet consists of two pages:

Create Index: General Page

The General page consists of the following information:

Index Name of the index.
When creating an index you can specify a valid Oracle identifier
Schema Schema in which the index will be defined.
The default schema for a new index is the user's default schema.
When creating an index link, you can also select any schema defined in the connected database from the Schema drop-down list.
Index On Drop-down list allowing you to specify whether the index is on a cluster or a table.
Schema: Schema to which the index belongs.
Cluster/Table: Table for which the index is created.
Columns in Cluster/Columns in Table: Scrolling list displaying all columns in the table.
Columns in Index: Scrolling list of columns on which the index is to be created.
To add or remove columns to be indexed, select the column entry in the desired list and click on << or >>. For example, if you select a column in the Column in Table list and then press >>, the column is added to the index list.
Options Specify whether the index is Unique, Sorted, or Recoverable.
Parallel Degree: The degree of parallelism when creating an index using the parallel query option.
Instances: Maximum number of instances allowed to participate in parallel query processing.

Create Index: Storage page

The Storage page contains the following information:

Tablespace Name of the tablespace that contains the database object being defined.
Extents Initial Size: Size of the object's first extent.
You can enter a value, the minimum being the size of one data block. The default value is the size of five data blocks.
Next Size: Size of the next extent to be allocated to the object.
The default value is the size of five datablocks. The smallest permissible value is the size of one datablock.
Increase Size by: Percent by which each extent grows (after the second extent) compared to the previous extent.
Minimum Number: Total number of extents allocated when a segment is created.
The default value is one. You can enter a value of one or greater.
Maximum Number: Total number of extents, including the first, that an Oracle database can allocate for the object.
You can enter a value of one or greater. The default value varies.
Space Usage % Free: Percentage of space in each of the object's data blocks that is reserved for future updates to the object.
You can enter values from 0 to 99.
Number of Transactions Initial: Initial number of transaction entries allocated within each data block allocated to the object.
You can enter a value from 1 or 2(for clusters and indexes) to 255.
Maximum: Maximum number of concurrent transactions that can update a data block allocated to the object.
You can enter a value from 1 to 255.
Freelists Lists: Number of free lists for each of the free list groups for the table, cluster, or index.
You can enter a value of one or greater. The default value is one.
Groups: Number of groups of free lists for a table, cluster, or index.
You can enter a value of one or greater. The default value is one.

Create Like Index

To create an index with parameters that are similar to an existing index, select select a index from the multi-column list and then select Create Like from the Object menu. The Create Index property sheet appears with the appropriate parameters filled in. Click on the Create button to close the property sheet and create the new index.

Altering an Index

To alter an existing index, select a specific index in the tree list. A property sheet with the index's current parameters is displayed in the Details view.

Package Bodies Container

The Package Bodies container consists of a list of package bodies defined within the connected database.

A package consists of two parts: the specification and the body. The package body defines all constructs (public and private) of the package while the specification declares all public constructs. For information about package bodies, see Oracle7 Server Concepts.

Package Bodies Multi-Column List

The Package Bodies multi-column list displays when the Package Bodies container is selected in the tree list. The list contains all package bodies defined within the connected database. For information about database links, see the Oracle7 Server Concepts.

The columns of the package bodies list are described below:

Schema Name of the schema containing the package body.
Package Body Name of the package body.
Created Date on which the package body was created.
Last Modified Date on which the package body was last modified.
Status Current status of the package body (Valid or Invalid).

Creating a Package Body

To create a new package body, choose Create from the Schema Manager Object menu and select Package Body from the list in the Create Object dialog box. The Create Package Body property sheet appears. The property sheet consists of a single page:

Create Package Body: General Page

The General page consists of the following information:

Name Name of the package body being defined.
Schema Name of the schema containing this package. The drop-down list contains all schemas available in the current database.
Recompile Recompile the PL/SQL source for the package body so that it can be stored and executed from within the database.
Package Source PL/SQL source code for the package body.
Status Current status of the package (valid or invalid).
Dates Created: Date the package body was originally created.
Last Modified: Date the package body was last modified.

Create Like Package Body

To create an package body with parameters that are similar to an existing one, select a package body from the multi-column list and then select Create Like from the Object menu.

Editing a Package Body

To edit an existing package body, select a package body from the multi-column list using the right mouse button. Choose Quick Edit from the context-sensitive menu. The Quick Edit Package Body property sheet appears.

Packages Container

The Package container consists of a list of all packages defined within the connected database.

A package is a group of related procedures and functions, together with cursors and variables they use, stored together in the database for continued use as a unit. For information about packages, see Oracle7 Server Concepts.

Packages Multi-Column List

The Packages multi-column list appears when the Packages folder is selected in the tree view. The list contains information about

Schema Name of the schema containing the package. This column is not displayed when viewing a particular schema.
Package Name of the package.
Created Date on which the package was created.
Last Modified Date on which the package was last modified.
Status Current status of the package (valid or invalid).

Creating a Package

To create a new package, choose Create from the Schema Manager Object menu and select Packages from the list in the Create Object dialog box. The Create Package property sheet appears. The property sheet consists of a single page:

Create Package: General Page

The General page consists of the following information:

Name Name of the package being defined.
Schema Name of the schema containing the package. The drop-down list contains all schemas available in the current database.
Recompile Recompile the PL/SQL source for the package so that it can be stored and executed from within the database.
Status Current status of the package (valid or invalid).
Dates Created: Date the package was originally created.
Last Modified: Date the package was last modified.

Create Like Package

To create an package with parameters that are similar to an existing one, select select a package from the packages's multi-column list and then select Create Like from the Object menu. The Create Package property sheet appears with the appropriate parameters filled in.

Editing a Package

To edit an existing package, select a specific package in the tree view. A property sheet with the package's current parameters is displayed.

Procedures Container

The Procedures container consists of a list of all procedures defined within the connected database.

A procedure groups a set of SQL and PL/SQL statements together to perform a specific task. For more information on procedures, see Oracle7 Server Concepts.

Procedures Multi-Column List

The Procedures multi-column list appears when the Procedures container is selected in the tree view. The list contains the following information:

Schema Name of the schema containing the procedure. This column is not shown when viewing a particular schema.
Procedure Name of the procedure.
Created Date the procedure was originally created.
Last Modified Date the procedure was last modified.
Status Current status of the procedure (Valid or Invalid).

Creating a Procedure

To create a new procedure, choose Create from the Schema Manager Object menu and select Procedure from the list in the Create Object dialog box. The Create Package property sheet appears. The property sheet consists of a single page:

Create Procedure: General Page

The General page consists of the following information:

Name Name of the procedure being defined.
Schema Name of the schema containing this procedure.
The drop-down list contains all schemas available in the current database.
Recompile Recompile the PL/SQL source for the procedure so that it can be stored and executed from within the database.
Package Source PL/SQL source code for the procedure.
Status Current status of the procedure (valid or invalid).
Show Errors: Displays the Error Message dialog box listing the errors encountered while trying to compile the function source. This button is only enabled when the function status is invalid.
Dates Created: Date the procedure was originally created.
Last Modified: Date the procedure was last modified.

Create Like Procedure

To create an procedure with parameters that are similar to an existing one, select select a procedure from the multi-column list and then select Create Like from the Object menu. The Create Procedure property sheet appears with the appropriate parameters filled in.

Altering a Procedure

To alter an existing procedure, select a specific procedure in the tree view. A property sheet with the procedure's current parameters is displayed in the Details view.

Refresh Groups Container

The Refresh Group container contains all refresh groups defined within the connected database.

A refresh group consolidates multiple snapshots and allows you to easily refresh two or more snapshots to a single point in time.

For information about refresh groups, see Oracle7 Server Distributed Systems, Volume II: Replicated Data.

Refresh Groups Multi-Column List

The Refresh Groups multi-column list appears when the Refresh Groups container is selected in the tree view. The list contains the following information:

Schema Name of the schema containing the refresh group. This column is not shown when viewing a particular schema.
Name Name of the refresh group.
Refresh group names must follow the same naming conventions as tables.
Number Number of snapshots contained in the refresh group.
Next Date Next date the refresh will occur.
Interval Function used to calculate the next time to refresh the snapshots in the group.

Creating a Refresh Group

To create a new refresh group, choose Create from the Object menu and select Refresh Group from the list in the Create Object dialog box. The Create Refresh Group property sheet appears. The property sheet consists of two pages:

Create Refresh Group: General Page

The General page consists of the following information:

Name Name of the Refresh group.
Schema Name of the schema containing the refresh group.
Refresh Refreshes the current refresh group immediately.
Broken When checked, marks a job as broken so Oracle will not attempt to execute the job.
Delete group when last member deleted Upon deleting the last refresh group member, the refresh group is automatically deleted.
Refresh Next Date: Next date that you want a refresh to occur.
Interval: Function used to calculate the next time to refresh the snapshots in the refresh group.
Continue refresh despite conflicts: Select this option if you want the refresh to proceed even if there are outstanding conflicts logged in the DefError table for the snapshot's master. Active for updatable snapshots only.
Push changes from snapshot to master before refresh: When selected, allows you to push changes from the snapshot to its associated master before refreshing the snapshot. Otherwise, these changes may appear to be temporarily lost. Active for updatable snapshots only. This option is selected by default.
Rollback Segment Use default rollback segment: When selected, the default rollback segment is used. Segment name and Segment Schema are greyed out.
Segment Name: Name of the rollback segment to use while refreshing snapshots.
Segment Schema: Name of the schema containing the rollback segment.

Create Refresh Group: Snapshot Page

The Snapshot page consists of the following information:

In Group Scrolling list containing all snapshots in the refresh group.
Available Scrolling list containing all available snapshots.
To add a a snapshot to the refresh group, select an item from the Available list and click Add. The snapshot appears in the In Group list. Click Apply.
To remove a snapshot from the refresh group, select an item in the In Group list and click Remove. Click Apply

Create Like Refresh Group

To create a refresh group with parameters that are similar to an existing one, select select a refresh group from the multi-column list and then select Create Like from the Object menu. The Create Refresh Group property sheet appears with the appropriate parameters filled in.

Altering a Refresh Group

To alter an existing refresh group, select a specific refresh group in the tree view. A property sheet with the refresh group's current parameters is displayed in the Details view.

Sequences Container

The Sequence container contains all sequences stored within the connected database.

A sequence is a database object used to generate a serial list of unique numbers for numeric columns of a database's tables. Sequences simplify data entry in a multi-user system by automatically generating unique numerical values for the rows of a single table or multiple tables. For information about sequences, see the Oracle7 Server Concepts and the Oracle7 Server Administrator's Guide.

Sequences Multi-Column List

The Sequences multi-column list displays when the Sequences container is selected in the tree list. The list contains sequences defined within the connected database. For information about database links, see the Oracle7 Server Concepts.

The columns of the Sequences multi-column list are described as follows:

Schema Name of the schema containing the sequence. This column is not shown when viewing a particular schema.
Sequence Name of the sequence.
Minimum Value Smallest permissible value for the sequence.
Maximum Value Largest permissible value for the sequence.
Interval Incremental value for the sequence (value may be positive or negative).
Recent Value Most recent value of the sequence.
Cycle Indicates whether or not the sequence should continue to generate values after reaching its minimum or maximum value (Yes or No).
Order Indicates whether or not the sequence numbers should be generated in order of request (Yes or No).
Cache Size Number of values to be preallocated and stored by the database.

Creating a Sequence

To create a new sequence, choose Create from the Schema Manager Object menu and select Sequence from the list in the Create Object dialog box. The Create Sequence property sheet appears. The property sheet consists of a single page:

The Create Sequence property sheet consists of a single page:

Create Sequence: General Page

The General page contains the following information:

Sequence Name of the sequence being defined.
During the Create operation, you can specify a valid Oracle identifier as the name of the sequence.
Schema Schema in which the sequence is defined.
The default schema for a new sequence is the user's default schema.
During the Create operation, you can choose a schema from those defined in the connected database from the drop-down list.
Type: Ascending When selected, sequence values increase from the initial value towards the maximum value.
This is the default setting when creating a sequence.
Type: Descending When selected, the sequence values decrease from the initial value towards the minimum value.
Values Minimum: Minimum allowed value of the sequence.
When creating a sequence, this field is initially blank.
If this field is blank when you select the Create button, a default value of one for an ascending sequence or -1026 for a descending sequence will be used.
Maximum: Maximum value of a sequence
When creating a sequence this field is initially blank. If left blank when the Create button is selected, a default value of 1027 for an ascending sequence and -1 for a descending sequence will be used.
Increment: Interval by which the sequence increases or decreases.
When creating a sequence, this field is initially blank. If left blank when the Create button is selected, a default value of 1 is used. Only positive integers are accepted in this field.
Decrement: Interval by which the sequence decreases.
When creating a sequence, this field is initially blank. If left blank when the Create button is selected, a default value of 1 is used. Only positive integers are accepted in this field.
Initial: The starting value of the sequence.
If the field is blank when the Create button is selected, a default value of the sequence's minimum will be used for an ascending sequence. For a descending sequence, a default value of the sequence's maximum value is used.
Recent: The most recent value of the sequence.
This field is active when altering an existing sequence.
Options Cycle Values: When checked, specifies that the sequence should continue to generate values after reaching its minimum or maximum value.
For ascending sequences, the minimum value is generated after the maximum is reached. For descending sequences, the maximum value is generated after the minimum is reached.
If Cycle Values is not checked, the sequence will stop generating values when it reaches its minimum or maximum. When creating a sequence, this checkbox is unchecked by default.
Order Values: When checked, specifies that the sequence numbers are to be generated in order of request.
When creating a sequence, this checkbox is unchecked by default.
Cache Size: Number of values to be pre-allocated and stored by the database.
Default: The default value is 20.
Size: The smallest acceptable value is 2. For sequences that cycle, this value must be less than the number of values in the cycle. If the maximum number of values the sequence can generate is less than the cache size, the cache size will be automatically changed to the maximum number of possible values.

Create Like Sequence

To create another sequence with parameters that are identical to an existing sequence, select an existing sequence from the tree list and then select Create Like from the Object menu. The Create Like property sheet is displayed.

Altering a Sequence

To alter an existing sequence, select a specific sequence in the tree view. A property sheet with the sequence's current parameters is displayed in the Details view. The property sheet is nearly identical to the Create Sequence property sheet with the following exceptions:

Snapshot Logs Container

The Snapshot Logs container contains a list of all snapshot logs created in the connected database.

A snapshot log is a table associated with the master table of a snapshot. The snapshot log contains information about changes made to its associated master table. The information in the snapshot log is used to refresh the snapshot. For information about snapshot logs, see Oracle7 Server Concepts.

Snapshot Logs Multi-Column List

The Snapshot Logs multi-column list displays when the Snapshots container is selected in the tree list. The list contains snapshots log information defined within the connected database. For information about database links, see the Oracle7 Server Concepts.

The columns of the Snapshots multi-column list are described as follows:

Schema Name of the schema containing the snapshot log. This column is not shown when viewing a particular schema.
Log Table Name of the table storing the ROWID and timestamp of rows updated in the master table.
Log Trigger Name of the AFTER ROW trigger on the master table.
Master Table Name of the table associated with the snapshot log.
Current Snapshots The number of snapshots associated with the snapshot log.

Creating a Snapshot Log

To create a new snapshot log, choose Create from the Schema Manager Object menu and select Snapshot Log from the list in the Create Object dialog box. The Create Snapshot Log property sheet appears. Fill in the requisite information and then click Create. The property sheet consists of two pages:

Snapshot Log: General Page

The General page contains the following:

On Master Table Schema: Name of the schema to which the master table belongs.
Table: Name of the master table.
Log Table Name of the table that stores the ROWID and timestamp of rows updated in the master table.
Log Trigger Name of the AFTER ROW trigger on the master table that tells Oracle to insert the ROWIDs and timestamps of inserted, updated, and deleted rows into the master snapshot log.
Current Snapshots: The number of snapshots associated with the snapshot log.

Snapshot Log: Storage page

The Storage page contains the following information:

Tablespace Name of the tablespace that contains the database object being defined.
Extents Initial Size: Size of the object's first extent (Kilobytes or Megabytes).
You can enter a value, the minimum being the size of one data block. The default value is the size of five data blocks.
Next Size: Size of the next extent to be allocated to the object (Kilobytes or Megabytes).
The default value is the size of five datablocks. The smallest permissible value is the size of one datablock.
Increase Size by: Percent by which each extent grows (after the second extent) compared to the previous extent.
Minimum Number: Total number of extents allocated when a segment is created.
The default value is one. You can enter a value of one or greater.
Maximum Number: Total number of extents, including the first, that an Oracle database can allocate for the object.
You can enter a value of one or greater. The default value varies.
Space Usage % Free: Percentage of space in each of the object's data blocks that is reserved for future updates to the object.
You can enter values from 0 to 99.
% Used: Minimum percentage of used space that an Oracle database maintains for each data block of the object.
A block becomes a candidate for row insertions when its used space falls below the % Used value.
You can enter a value from 1 to 99. The default value is 40.
Number of Transactions Initial: Initial number of transaction entries allocated within each data block allocated to the object.
You can enter a value from 1 or 2(for clusters and indexes) to 255.
Maximum: Maximum number of concurrent transactions that can update a data block allocated to the object.
You can enter a value from 1 to 255.
You can enter a value of one or greater. The default value is one.

Create Like Snapshot Log

To create a snapshot log with parameters that are similar to an existing log, select an existing snapshot log from the tree list and then select Create Like from the Object menu.

Altering a Snapshot Log

To alter an existing snapshot log, select a specific snapshot log in the tree list. A property sheet with the log's current parameters is displayed in the Details view.

Snapshots Container

The Snapshot container contains of a list of all snapshots defined within the database.

A snapshot is a read-only copy of a master table located on a remote node. It is periodically refreshed to reflect changes made to the master table. A snapshot can be queried, but not updated; only the master table can be updated.

Snapshots Multi-Column List

The Snapshots multi-column list displays when the Snapshots container is selected in the tree list. The list contains all snapshots defined within the connected database.

The columns of the snapshots list are described below:

Schema Name of the schema containing the snapshot. This column is not shown when viewing a particular schema.
Snapshot Name of the snapshot.
Master Owner Owner of the snapshot's master table.
Master Table Name of the master table.
Master Link Database link to the master site.
Last Refresh Date of the last refresh (at the master site).
Type Type of refresh for automatic refreshes: Complete, Fast, or Force.

Creating a Snapshot

To create a new snapshot, choose Create from the Schema Manager Object menu and select Snapshot from the list in the Create Object dialog box. The Create Snapshot property sheet appears. The property sheet consists of two pages:

Create Snapshot: General Page

The General page contains the following:

Snapshot Name of the snapshot being defined.
During the Create operation, you can specify a valid Oracle identifier as the name of the sequence.
Schema Name of the schema containing the snapshot. The drop-down list contains all available schemas within the connected database.
Refresh Type Type of refresh for automatic refreshes: Complete, Fast, or Force.
Start Date: Date snapshot refresh is to begin.
Next Date: Expression that calculates the interval at which the snapshot is updated.
Updatable When selected, indicates that the snapshot is updatable.
Snapshot Subquery Snapshot query executed by Oracle when you create the snapshot. Results of the query are placed in the snapshot. (Create only)
Cluster Cluster to which the snapshot belongs.
Column Name Name of the column to be used as part of the snapshot. Click Add to add the column name to the Snapshot Columns list.
Snapshot Columns Scrolling list of all columns added to the snapshot. Use the Up/Down buttons to reorder the list of columns (column order must match the order in the cluster).

Create Snapshot: Storage page

The Storage page contains the following information:

Use Cluster Parameters Indicates that the storage parameters for the table being defined will be obtained from the cluster to which the table belongs.
The setting of this control is automatically determined based on whether or not the table is a member of a cluster.
Tablespace Name of the tablespace that contains the database object being defined.
Extents Initial Size: Size of the object's first extent.
You can enter a value, the minimum being the size of one data block. The default value is the size of five data blocks.
Next Size: Size of the next extent to be allocated to the object.
The default value is the size of five datablocks. The smallest permissible value is the size of one datablock.
Increase Size by: Percent by which each extent grows (after the second extent) compared to the previous extent.
Minimum Number: Total number of extents allocated when a segment is created.
The default value is one. You can enter a value of one or greater.
Maximum Number: Total number of extents, including the first, that an Oracle database can allocate for the object.
You can enter a value of one or greater. The default value varies.
Space Usage % Free: Percentage of space in each of the object's data blocks that is reserved for future updates to the object.
You can enter values from 0 to 99.
% Used: Minimum percentage of used space that an Oracle database maintains for each data block of the object.
A block becomes a candidate for row insertions when its used space falls below the % Used value.
You can enter a value from 1 to 99. The default value is 40.
Number of Transactions Initial: Initial number of transaction entries allocated within each data block allocated to the object.
You can enter a value from 1 or 2(for clusters and indexes) to 255.
Maximum: Maximum number of concurrent transactions that can update a data block allocated to the object.
You can enter a value from 1 to 255.
Freelists Lists: Number of free lists for each of the free list groups for the table, cluster, or index.
You can enter a value of one or greater. The default value is one.
Groups: Number of groups of free lists for a table, cluster, or index.
You can enter a value of one or greater. The default value is one.

Create Like Snapshot

To create a snapshot with parameters that are identical to an existing snapshot, select an existing snapshot from the tree list and then select Create Like from the Object menu.

Editing a Snapshot

To edit an existing snapshot, select a specific snapshot in the tree list. A property sheet with the snapshot's current parameters is displayed in the Details view. This property sheet is similar to the Create Snapshot property sheet except that the Subquery entry field is replaced by the following information:

Updatable Trigger: Associated AFTERROW trigger on the master table.
Log: Associated snapshot log.
Can Log Whether or not the snapshot can be logged.
Last Refreshed Date the snapshot was last refreshed.
Ref. Group Associated refresh group.
Master Info Owner: Name of the schema to which the snapshot belongs.
Table: Name of the master table.
Link: Database link to the database where the master table resides.

Synonyms Container

The Synonyms container contains a list of all synonyms defined within the connected database.

A synonym is an alias for a table, view, sequence, procedure, function, package or another synonym. For information about tables, see Oracle7 Server Concepts.

Synonyms Multi-Column List

The Synonyms multi-column list displays when the synonyms container is selected in the tree list. The list summarizes information for synonyms defined within the connected database.

The columns of the Synonyms multi-column list are described as follows:

Schema Name of the schema containing the synonym. This column is not shown when viewing a particular schema.
Synonym Name of the synonym.
Object Owner Owner of the original database object.
Object Name of the original database object.
Link Database link to the the original schema object (e.g. table, view, snapshot).

Creating a Synonym

To create a new synonym, choose Create from the Schema Manager Object menu and select Synonym from the list in the Create Object dialog box. The Create Synonym property sheet appears. The property sheet consists of a single page:

Create Synonym: General Page

The General page consists of the following information:

Synonym Name of the synonym.
Schema Name of the schema containing the synonym. The drop-down list contains all available schemas within the connected database.
As Alias For Object Type: Original database object.
Schema: Name of the schema containing the original database object.
Object: Name of the original database object.

Create Like Synonym

To create another synonym with parameters that are identical to an existing synonym, select an existing synonym from the tree list and then select Create Like from the Object menu. The Create Like property sheet is displayed. Click Create after filling in the requisite parameters.

Altering a Synonym

To alter an existing synonym, select a specific synonym in the tree list. A property sheet with the original synonym's current parameters is displayed in the Details view. All fields are disabled.

Tables Container

The Tables container contains a list of all tables defined within the connected database.

As the basic unit of storage in a relational database management system, a table represents entities and relationships, and consists of one or more units of information (rows), each of which contains the same kinds of values (columns). For information about tables, see Oracle7 Server Concepts.

Tables Multi-Column List

The Tables multi-column list displays when the Tables container is selected in the tree list. The list summarizes information for tables defined within the connected database.

The columns of the Sequences multi-column list are described as follows:

Schema Name of the schema in which the table is defined. This column is not shown when viewing a particular schema.
Table Name of the table.
Tablespace Name of the tablespace to which the table belongs.
Rows Number of rows in the table. (Only shown if the cost-based optimizer is disabled.)
Backed Up Backup status for the table (Yes or No).

Creating a Table

To create a new table, choose Create from the Schema Manager Object menu and select Table from the list in the Create Object dialog box. The Create Table property sheet appears. The property sheet contains the following pages:

Create Table: General page

The General page contains the following information:

Table Name of the table being defined.
During the Create operation, you can specify a valid Oracle identifier as the name of the table.
Schema Schema in which the table is defined.
The default schema for a new table is the user's default schema. During the Create operation, you can choose a schema from those defined in the connected database.
Cluster Cluster to which the table belongs.
The default setting is <None>.
Columns A multi-column list of columns defined in the table.
The columns of this list consist of Column (name), Datatype, Default, Nulls? and Cluster Column.
New: Displays the Column Details dialog box for defining a column in the table.
This button is always enabled.
Edit: Displays the column details dialog box for modifying a column in the table.
This button is only enabled when an item is selected in the Columns list.
Note: This button is not enabled if altering a table and a clustered column is selected.
Remove: Removes a column from the table.
This button is only enabled when an item is selected in the Columns list.
Note: This button is not enabled when altering a table when a column that is already defined in the database is selected.
Statistics Table statistics: Total number of rows, the average row (data) length in bytes (characters), table size, and the current backup status. (Edit only)
Initial Data from Query Query to be used to populate the table.
When creating a table, you can enter a query in this field. A query does not have to be specified (Create only).

Create Table: Column Details Dialog Box

Note: This dialog box displays when you click on the New or Edit button.

Name Name of the table column being defined or edited.
You can specify a valid Oracle identifier as the name of the column. This field is disabled for columns that have already been defined in the database.
Datatype Column's Oracle datatype. See Oracle7 Server Administrator's Guide for specific information on Oracle datatypes.
You can select one of the following items: CHAR, VARCHAR2, NUMBER, LONG, RAW, LONG RAW, DATE, ROWID, MLSLABEL
Length: Number of bytes allowed for values defined in the column (for CHAR, VARCHARZ, NUMBER, RAW).
Precision (for NUMBER datatype): Number of digits to the right of the decimal point.
If CHAR is selected in the Datatype drop-down list, you may specify length. If VARCHAR2 or RAW is selected, you may specify a length. If NUMBER is selected, you may specify a length, a length and a precision, or neither.
Values Default: An expression that serves as the default value for this column in any rows for which the INSERT statement omits a value for the column.
No Nulls: When checked, indicates that the column being defined is not permitted to contain null values.
Is Cluster Column Drop-down list box allowing you to specify an associated column in the cluster key.
This drop-down list box is only enabled if a cluster has been selected on the Table General page.

Create Table: Storage page

The Storage page contains the following information:

Use Cluster Parameters Indicates that the storage parameters for the table being defined will be obtained from the cluster to which the table belongs.
The setting of this control is automatically determined based on whether or not the table is a member of a cluster.
Tablespace Name of the tablespace that contains the database object being defined.
Extents Initial Size: Size of the object's first extent.
You can enter a value, the minimum being the size of one data block. The default value is the size of five data blocks.
Next Size: Size of the next extent to be allocated to the object.
The default value is the size of five datablocks. The smallest permissible value is the size of one datablock.
Increase Size by: Percent by which each extent grows (after the second extent) compared to the previous extent.
Minimum Number: Total number of extents allocated when a segment is created.
The default value is one. You can enter a value of one or greater.
Maximum Number: Total number of extents, including the first, that an Oracle database can allocate for the object.
You can enter a value of one or greater. The default value varies.
Space Usage % Free: Percentage of space in each of the object's data blocks that is reserved for future updates to the object.
You can enter values from 0 to 99.
% Used: Minimum percentage of used space that an Oracle database maintains for each data block of the object.
A block becomes a candidate for row insertions when its used space falls below the % Used value.
You can enter a value from 1 to 99. The default value is 40.
Number of Transactions Initial: Initial number of transaction entries allocated within each data block allocated to the object.
You can enter a value from 1 or 2(for clusters and indexes) to 255.
Maximum: Maximum number of concurrent transactions that can update a data block allocated to the object.
You can enter a value from 1 to 255.
Freelists Lists: Number of free lists for each of the free list groups for the table, cluster, or index.
You can enter a value of one or greater. The default value is one.
Groups: Number of groups of free lists for a table, cluster, or index.
You can enter a value of one or greater. The default value is one.
Tablespace Name of the tablespace that contains the object being defined.
Number of Transactions Initial: Initial number of transaction entries allocated within each data block allocated to the object.
You can enter a value from 1 or 2(for clusters and indexes) to 255.
Maximum: Maximum number of concurrent transactions that can update a data block allocated to the object.
You can enter a value from 1 to 255.
% Free Percentage of space in each of the object's data blocks that is reserved for future updates to the object.
You can enter values from 0 to 99.
% Used Minimum percentage of used space that an Oracle database maintains for each data block of the object.
A block becomes a candidate for row insertions when its used space falls below the % Used value.
You can enter a value from 1 to 99. The default value is 40.
Initial Size Size of the object's first extent.
You can enter a value, the minimum being the size of one data block. The default value is the size of five data blocks.
Next Size Size of the next extent to be allocated to the object.
The default value is the size of five datablocks. The smallest permissible value is the size of one datablock.
Increase Size by Percent by which each extent grows (after the second extent) compared to the previous extent.
Minimum Number Total number of extents allocated when a segment is created.
The default value is one. You can enter a value of one or greater.
Maximum Number Total number of extents, including the first, that Oracle can allocate for the object.
You can enter a value of one or greater. The default value varies.
Freelists Number of free lists for each of the free list groups for the table, cluster, or index.
You can enter a value of one or greater. The default value is one.
Groups Number of groups of free lists for a table, cluster, or index.
You can enter a value of one or greater. The default value is one.

Create Table: Constraints Page

The Constraints page contains the following information:

Name Name of the table constraint being defined.
To define a new constraint, you can enter a valid Oracle identifier as the name of the constraint. If no name is entered, a default name will be assigned by the database. This field is disabled if the column has already been defined in the database.
New Create a new table constraint.
Remove Delete the constraint that is shown in the Name field.
Disable Indicates that the constraint should be disabled (checked) or enabled (not checked) when the constraint is created.
Columns and Constraints Lists all table columns for the table constraint being defined and the type of constraint (if any) defined on the column.
Unique: When selected, indicates that the selected column must contain unique values.
If multiple columns are defined to be unique during a single invocation of this property sheet, each column is part of a composite unique key for the table (there may be more than one).
Primary: When checked, indicates that the selected column is part of a primary key, or the primary key for the table.
If multiple columns are defined to be primary during a single invocation of this property sheet, each column is part of the composite primary key for the table (there can only be one).
Neither: Selected by default, this setting indicates that the column is neither unique nor part of a primary key.
Foreign Key: When checked, indicates that the column is a foreign key.
If multiple columns are defined to be foreign during a single invocation of this property sheet, each column is part of a composite foreign key for the table (there may be more than one).
Referenced Key Schema: Schema referenced by the foreign key in the constraint being defined.
Table: Table referenced by the column being defined.
Columns: Column that is referenced by the column being defined.
You can specify which columns are referenced by the column being defined in the child table.
Cascade on Delete: When checked, indicates that rows will automatically be removed from the child table if they reference values contained in the referenced key column of rows being removed from the parent table.
This control is disabled if a query is is defined at Create time or if the column has already been defined in the database.
Note: Controls in this group are only enabled if a foreign key is defined in the current constraint.
Check Check constraint to be included in the table constraint currently being defined.
You can enter the text of the check constraint in this text edit field or a valid expression. For more information see Oracle 7 Server SQL Reference.
Schema: Save Exception to Schema into which exceptions to the constraint are to be entered.
The first choice in this list is <Already Applied> when viewing an existing constraint when editing a table. This list is disabled if the constraint is to be created disabled.
Table: Table into which exceptions to the constraint are to be entered.
The first choice in this drop-down list is <None> or <Already Applied>. This list is disabled if the constraint is to be created disabled.
Note: All controls except Name, New, Remove, Disable, and the multi-column list are disabled when viewing a constraint already defined in the database. This is an issue only when editing a table.

Create Table: Status page

The Status page contains the following information:

Unique Constraint Do Not Change Status: Maintains existing unique constraint settings.
Enable: Enables unique constraint on specified columns.
Disable: Disables unique constraints on specified columns.
Drop: Indicates that the unique constraint should be dropped (on the specific columns).
This group is enabled when defining a unique constraint on the Constraint page.
Columns: Columns on which a unique constraint has been placed.
Schema: Save Exceptions to Schema to which exceptions to the unique/primary key constraints being enabled should be saved.
Table: Table to which exceptions to unique/primary key constraints being enabled should be saved.
These controls are enabled when the Enable radio button is selected.
Cascade When checked, indicates that the integrity constraints that depend on the specified integrity constraint should be disabled.
This control is only active when you disable or drop a constraint.
Do Not Change Status: Primary Key Constraint Maintains existing primary key constraint settings.
Enable: When selected, enables primary key constraint.
Disable: When selected, disables primary key constraint.
Drop: Indicates that the constraint should be dropped (checked) or not dropped (not checked) when created.
This group box is enabled when defining a unique constraint on the Constraint page.
Triggers Do Not Change Status: Maintains existing trigger settings.
Enable All: Enables all triggers defined in the table.
Disable All: Disables all triggers defined in the table.
This control is only enabled when editing a table.

Create Like Table

To create a new table with parameters that are identical to an existing table, select a table from the tree list and then select Create Like from the Object menu. The Create Table property sheet appears with all parameters filled in except Table(name), based on the values from the selected table. Click Create to create the table and close the property sheet.

Altering a Table

To alter an existing table, select a specific table in the tree list. A property sheet with the table's current parameters is displayed in the Details view. The property sheet is nearly identical to the Create Table property sheet with the following exceptions:

Triggers Container

The Triggers container contains a list of triggers defined within the connected database.

A trigger is a stored PL/SQL procedure that is implicitly executed when an INSERT, UPDATE, or DELETE statement is issued against the associated table. For more information about triggers, see Oracle7 Server Concepts.

Triggers Multi-Column List

The Triggers multi-column list displays when the Triggers container is selected in the tree list. The list summarizes information for all triggers defined within the connected database.

The columns of the Triggers multi-column list are described as follows:

Schema Name of the schema containing the trigger. This column is not shown when viewing a particular schema.
Trigger Name of the trigger
Type Trigger type (BEFORE EACH ROW, AFTER EACH ROW, or FOR EACH ROW)
Event Triggering statement (INSERT, UPDATE, DELETE).
Table Owner Owner of the table with which the trigger is associated.
Table Name of the table with which the trigger is associated.

Creating a Trigger

To create a new trigger, choose Create from the Schema Manager Object menu and select Trigger from the list in the Create Object dialog box. The Create Triggers property sheet appears. The Create Trigger property sheet appears. The property sheet consists of two pages:

Create Triggers: General page

The General page contains the following information:

Trigger Name of the trigger being defined.
Schema Schema in which the trigger is to be defined. The default schema for a new trigger is SYSTEM.
Trigger On Schema: Specifies the schema that contains the table.
Table: Specifies the schema and name of the table on which the trigger is to be created.
Triggers on SYS schema tables cannot be created.
Replace if Exists When selected, indicates that a trigger is to be recreated (if it already exists) without dropping, recreating and regenerating object privileges previously granted.
Enabled When checked, indicates that a trigger is enabled.
During a Create operation, this control is checked and disabled. It is not checked and enabled if a trigger is disabled.
Trigger Body Defines the PL/SQL block that Oracle executes to fire the trigger.

Create Triggers: Timing page

The Timing page contains the following information:

Fire Trigger Before/After: Indicates that Oracle fires the trigger before or after executing the triggering statement.
Insert: When checked, indicates that Oracle fire the trigger whenever an INSERT statement adds a row to a table.
Delete: When checked, indicates that Oracle fires the trigger whenever a DELETE statement removes a row from a table.
Update of Columns: Indicates that Oracle fires the trigger whenever an UPDATE statement changes a value in a column selected in the multi-select list. It is only enabled and populated when the Update checkbox is selected.
Trigger for Each Row When checked, designates the trigger to be a row trigger.
Oracle fires a row trigger once for each row that is affected by the triggering statement and meets the optional trigger constraint defined in the Condition field
When not checked, the trigger is a statement trigger and is fired only once when the triggering statement is issued (assuming the optional trigger constraint is met).
Old as/New as: Specifies correlation names.
You can use correlation names in the PL/SQL block and WHEN clause of a row trigger to refer specifically to old and new values of the current row. The default correlation names are OLD and NEW.
Condition: Specifies the trigger restriction.
The trigger restriction contains a SQL condition that must be satisfied for Oracle to fire the trigger. This condition must contain correlation names and not a query. You can only specify a trigger restriction for a row trigger. Oracle evaluates this condition for each row affected by the triggering statement. See the Oracle7 SQL Reference manual for more information.

Create Like Trigger

To create a new trigger with parameters that are similar to an existing trigger, select a trigger from the tree list and then select Create Like from the Object menu. The Create Trigger property sheet appears with all parameters filled in except Trigger (name), based on the values from the selected table.

Altering a Trigger

To alter an existing trigger, select a specific trigger in the tree list. The Alter Trigger property sheet with the selected trigger's current parameters is displayed in the Details view. The property sheet is nearly identical to the Create Sequence property sheet with the following exceptions:

Attention: Altering a trigger only affects values generated after the alter is performed.

Views Container

The Views container contains a list of all views defined within the connected database.

A view is a custom tailored presentation of the data in one or more tables and can also be thought of as a stored query. Views do not actually contain or store data; rather, they derive their data from the tables on which they are based, called base tables. Base tables can in turn be actual tables or can themselves be views. Views can be queried, updated, inserted into, and deleted from, with restrictions. All operations performed on a view actually affect the base tables of the view. For information about views, see Oracle7 Server Concepts.

Views Multi-Column List

The Views multi-column list displays when the Views container is selected in the tree list. The list summarizes information for tables defined within the connected database.

The columns of the Views multi-column list are described as follows:

Schema Name of the schema containing the view. This column is not shown when viewing a particular schema.
View Name of the view.
Status Current status of the view (Valid or Invalid).

Creating a View

To create a new view, choose Create from the Schema Manager Object menu and select View from the list in the Create Object dialog box. The Create View property sheet appears. The Create View property sheet consists of two pages:

Create View: General page

The General page contains the following information:

View Name of the view being defined.
During a Create operation, you can specify a valid Oracle identifier as the name of the view.
Schema Schema in which the view should be defined. The default schema for a new view is the user's default schema.
During a Create operation, you can choose a schema from those defined in the connected database.
Query Text Identifies columns and rows of the table(s) that the view is based on.
A view's query can be any SELECT statement without the ORDER BY or FOR UPDATE clauses. Its select list can contain up to 254 expressions.
Replace if Exists When checked, indicates that the view is to be recreated, if it already exists, without dropping, recreating, and regenerating object privileges previously granted on it.
Force When checked, indicates that the view is to be created regardless of whether the view's base tables exist or the owner of the schema containing the view has privileges on them.
Constraint Specifies the name assigned to the CHECK OPTION constraint.
With Check Option: When checked, specifies that inserts and updates performed through the view must result in rows that the view query can select.
The CHECK OPTION cannot make a guarantee if there is a subquery in the query of this view or any view on which this view is based.
If you omit this identifier, Oracle automatically assigns the constraint a name of the form: SYS_Cn, where n is an integer that makes the constraint name unique within the database.

Create View: Aliases page

The Aliases page consists of a scrolling list of all aliases for the view

Create Like View

To create a new view with parameters that are identical to an existing view, select a view from the tree list and then select Create Like from the Object menu. The Create View property sheet appears with all parameters filled in except View (name), based on the values from the selected view.

Altering a View

To alter an existing view, select a specific view in the tree list. A property sheet with the view's current parameters is displayed in the Details view. The property sheet is nearly identical to the Create View property sheet with the following exceptions:


Contents Index Home Previous Next

<Oracle Enterprise Manager Concepts GuideOracle Enterprise Manager Concepts Guide