| Object Type |
Namespace |
Comments |
| DESTINATION |
1 |
A destination is a Scheduler object that defines a location for running a job.
Designate the locations where a job runs by specifying either a single destination or a destination group in the destination_name attribute of the job.
If you leave the destination_name attribute NULL, the job runs on the local host (the host where the job was created). |
| FUNCTION |
1 |
PL/SQL object that comes in two forms ... regular functions and pipelined table functions. |
| INDEXTYPE |
1 |
An object that specifies the routines that manage a domain (application-specific) index. It is a binding of an indextype name to an implementation type, which in turn
specifies and refers to user-defined index functions and procedures that implement the indextype. |
| JAVA CLASS |
1 |
- |
| JOB |
1 |
A job, scheduled or unscheduled, created with the DBMS_SCHEDULER built-in package. |
| JOB CLASS |
1 |
A classification of related jobs created with the DBMS_SCHEDULER built-in package. |
| LIBRARY |
1 |
A schema object associated with an operating-system shared library.
The name of this schema object can then be used in the call_spec of CREATE FUNCTION or CREATE PROCEDURE statements, or when declaring a function or procedure in a package or type,
so that SQL and PL/SQL can call to third-generation-language (3GL) functions and procedures. |
| MLE Language |
1 |
(new
21c)  |
| OPERATOR |
1 |
Binds overloads based on PL/SQL functions. |
| PACKAGE |
1 |
Also known as the Package specification. |
| PROCEDURE |
1 |
A program, written in PL/SQL or Java stored within the database. |
| PROGRAM |
1 |
Makes possible the creation of job scheduled programs, internal or external, by means of the DBMS_SCHEDULER built-in package |
| SCHEDULE |
1 |
A job schedule created with the DBMS_SCHEDULER built-in package. |
| SCHEDULER GROUP |
1 |
A grouping of schedules created with the DBMS_SCHEDULER built-in package. |
| SEQUENCE |
1 |
A database object from which multiple users may generate unique integers. Sequence objects are most often used to automatically generate surrogate keys. |
| SYNONYM |
1 |
An object alias that can be used to provide a simple name to replace schema_name plus object_name and/or object_name plus database link name |
| TABLE |
1 |
This single object type includes heap tables, global temporary tables, index organized tables, and partitioned tables
|
| TABLE PARTITION |
1 |
Partitions within a partitioned table |
| TABLE SUBPARTITION |
1 |
Subpartitions within a composite partitioned table |
| TYPE |
1 |
A user defined data type that may contain methods and functions |
| VIEW |
1 |
SQL statements stored within the database |
| WINDOW |
1 |
Scheduler Window |
| PACKAGE BODY |
2 |
The body containing working PL/SQL who's public interface defined by the corresponding package specification |
| TYPE BODY |
2 |
Use a type body to define or implement the member methods defined in an object type's specification. Contains the code for the methods that implement a type. |
| TRIGGER |
3 |
Five distinct trigger types exist in an Oracle database.
They are traditional table triggers, instead-of triggers on views,DDL event triggers, system event triggers, and editioning triggers. Links to all five types are the bottom of the page. |
| INDEX |
4 |
Oracle supports a variety of different index types but all of them serve one and only one purpose: To speed access to data that would otherwise be stored in a table. |
| INDEX PARTITION |
4 |
An index created such that the index is logically partitioned so as to correspond with the partitioning of table data segments: Referred to as a local index. |
| CLUSTER |
5 |
An object defined by a tablespace into which tables can be stored with unique changes to how they will be stored and accessed |
| LOB |
8 |
A large object: Used to refer to BFILES, BLOBs, and CLOBS. |
| LOB PARTITION |
8 |
A large object column in a partitioned table. |
| DIRECTORY |
9 |
A database object that maps a physical location in an operating system directory visible to the owner of the Oracle database binaries. |
| QUEUE |
10 |
An object addressed primarily by means of the DBMS_AQ Advanced Queuing built-in package. |
| JAVA SOURCE |
13 |
- |
| JAVA RESOURCE |
14 |
A pointer to a Java file. |
| CONTEXT |
21 |
A set of application-defined attributes that validates and secures an application created with the DBMS_SESSION built-in package. |
| RULE SET |
23 |
A set of defined fules. |
| CONSUMER GROUP |
24 |
A set of consumers defined by sharing, between the members of the group, an allocation of resources such as an cpu allocation. |
| RESOURCE PLAN |
24 |
A one to multi-level plan allocating resources such as cpu created with the DBMS_RESOURCE_MANAGER built-in package |
| XML SCHEMA |
25 |
An XML schema is a schema definition language written in XML. It may be used to describe the structure and semantics of conforming instance documents. |
| JAVA DATA |
32 |
- |
| RULE |
36 |
A database object that enables a client to perform an action when an event occurs and a condition is satisfied. A rule consists of the following components:
- Rule Condition
- Rule Evaluation Context (optional)
- Rule Action Context (optional)
Each rule is specified as a condition that is similar to the condition in the WHERE clause of a SQL query. Related rules can be grouped into rule sets. A rule can be in one rule set, multiple rule sets, or no rule sets.
Rule sets are evaluated by a rules engine, which is a built-in part of Oracle. Both user-created applications and Oracle features, such as Oracle Streams, can be clients of the rules engine. |
| EVALUATION CONTEXT |
38 |
DBMS_RULE_ADM.CREATE_EVALUATION_CONTEXT |
| UNDEFINED |
51 |
Undefined |
| UNDEFINED |
52 |
Undefined |
| EDITION |
64 |
A schema-less object providing a private environment that can be utilized to perform online redefinition of some database object types.
Edition-based redefinition enables upgrading application database objects while the application is in use minimizing or eliminating down time. |
| CONTAINER |
88 |
Container Database architecture object: CDB, Application Container, or PDB |
| UNIFIED AUDIT POLICY |
93 |
An audit policy that applies to multi-tenant CDBs. |
| LOCKDOWN PROFILE |
132 |
Only available in CDBs ... mechanism that restricts operations and functionalities. |
| MLE Language |
147 |
(new
21c) |
| DATABASE LINK |
unassigned |
A soft link from Oracle database to Oracle database. Some supported heterogeneous links are also possible. |
