Event Propagation Between Queues → You can use Streams to configure event propagation between two queues, which may reside in … different databases. Streams uses job queues to propagate events. A propagation is always between a source … queue and a destination queue. Although propagation is always between two queues, a single queue may … . However, only one propagation
Differences Between Documentation Formats → As a result of publishing deadlines, the online versions of manuals in this library may contain updates or corrections that are not included in the printed books. Additionally, the HTML version of a manual may contain minor updates or corrections that do not appear in the PDF version.
Transporting Tablespaces Between Databases → This section describes how to transport tablespaces between databases, and contains the following … Transportable Tablespaces Transporting Tablespaces Between Databases: A Procedure Object Behaviors Using Transportable Tablespaces
oracle.ultrasearch.query Class Between → DETAIL: FIELD | CONSTR | METHOD oracle.ultrasearch.query Class Between java.lang.Object … | +--oracle.ultrasearch.query.Between public class Between extends java.lang.Object implements Query Find … documents that has an attribute value within a range. Between can be applied to Date attribute, or Number … attribute. Since:
Mapping Between WF_EVENT_T and OMBAQ_TEXT_MSG → messages between systems. OMB queues require messages to be stored in a structure defined by a Java … called WF_EVENT_OMB_QH which you can use to translate between the standard Workflow WF_EVENT_T message
Determining Differences Between Replicated Tables → optionally rectify, the differences between two tables when both sites are Oracle release 7.3 or higher.
Transport of Tablespaces Between Databases → the tablespace between databases, or you can unplug a tablespace from one Oracle database and plug … it into another Oracle database, moving the tablespace between databases on the same platform … transport tablespaces only between Oracle databases that use the same character set and that run on
Converting Between Different LOB Types → Is Implicit LOB Conversion Between Different LOB Types Allowed? Question There are no implicit LOB … conversions between different LOB types? For example, in PL/SQL, I cannot use: INSERT INTO t VALUES
JPublisher Compatibility Between JDK Versions → of.sqlj files that are completely compatible between JDK 1.1.x and JDK 1.2.x or higher. (With this … i JPublisher default behavior, and is what makes translated.java code incompatible between JDK 1.1
Analyzing the Relationships Between Labels → This section describes relationships between labels. It contains these topics: Dominant and
Example: Relation Between Two Dimensions → between them to associate each city with the state that it is in. Assume that the state.city relation was
Overview of SQL Support in PL/SQL → Managing Cursors Separating Cursor Specs and Bodies with Packages
Overview of Explicit Cursors → The set of rows returned by a query can consist of zero, one, or multiple rows, depending on how many rows meet your search criteria. When a query returns multiple rows, you can explicitly declare a cursor to process the rows. Moreover, you can declare a cursor in the declarative part of any PL/SQL block, subprogram, or package. You use three commands to control a cursor: OPEN, FETCH, and CLOSE. First,
Using Cursor Attributes → Every explicit cursor and cursor variable has four attributes: %FOUND, %ISOPEN %NOTFOUND, and %ROWCOUNT. When appended to the cursor or cursor variable, these attributes return useful information about the execution of a data manipulation statement. You can use cursor attributes in procedural statements but not in SQL statements.
Ending Transactions → A good programming practice is to commit or roll back every transaction explicitly. Whether you issue the commit or rollback in your PL/SQL program or in the host environment depends on the flow of application logic. If you neglect to commit or roll back a transaction explicitly, the host environment determines its final state. For example, in the SQL*Plus environment, if your PL/SQL block does not
Calling Autonomous Functions from SQL → A function called from SQL statements must obey certain rules meant to control side effects. (See \"Controlling Side Effects of PL/SQL Subprograms\".) To check for violations of the rules, you can use the pragma RESTRICT_REFERENCES. The pragma asserts that a function does not read or write database tables or package variables. (For more information, See Oracle9i Application Developer's Guide - Fundamentals.)
Using Cursor Attributes → Using Cursor Expressions
SQL Pseudocolumns → PL/SQL recognizes the following SQL pseudocolumns, which return specific data items: CURRVAL, LEVEL, NEXTVAL, ROWID, and ROWNUM. Pseudocolumns are not actual columns in a table but they behave like columns. For example, you can select values from a pseudocolumn. However, you cannot insert into, update, or delete from a pseudocolumn. Also, pseudocolumns are allowed in SQL statements, but not in procedural
Using Cursor Variables → pass cursor variables back and forth between an application and server through remote procedure calls (RPCs).
Cursor Variable Example: Master Table and Details Tables → Consider the stored procedure below, which searches the database of a main library for books, periodicals, and tapes. A master table stores the title and category code (where 1 = book, 2 = periodical, 3 = tape) of each item. Three detail tables store category-specific information. When called, the procedure searches the master table by title, uses the associated category code to pick an OPEN-FOR statement,