How do I narrow my search results?
After you submit your search query:
- On the Refine Search results page, select one or more categories of products or services from the left sidebar.
- Then for a category with search results, click Select to choose your product and release filters, and then click OK.
For search queries that contain multiple words, surround the query with quotes, and then resubmit your query. Example: "database cloud service"
How do I find the documentation for my product or service?
From the home page, click the technology categories for your products or services. If you do not know which category to pick, try the following features:
- Click the Find a product tab and search for your product or service.
- Click Browse All Products & Services at the bottom of the home page to view an alphabetical listing of products and services.
- Apple Safari: Version 6
- Google Chrome: Version 29 and later
- Mozilla Firefox: Version 24 and later
- Microsoft Internet Explorer: Version 9 and later
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
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:
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
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.
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
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
Determining Differences Between Replicated Tables → optionally rectify, the differences between two tables when both sites are Oracle release 7.3 or higher.
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
Analyzing the Relationships Between Labels → This section describes relationships between labels. It contains these topics: Dominant and
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
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
Using Subqueries Instead of Explicit Cursors → You need not declare a cursor because PL/SQL lets you substitute a subquery. The following cursor FOR loop calculates a bonus, then inserts the result into a database table: DECLARE bonus REAL; BEGIN FOR emp_rec IN (SELECT empno, sal, comm FROM emp) LOOP bonus:= (emp_rec.sal * 0.05) + (emp_rec.comm * 0.25); INSERT INTO bonuses VALUES (emp_rec.empno, bonus); END LOOP; COMMIT; END;
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.
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
Restrictions on Cursor Variables → Currently, cursor variables are subject to the following restrictions: You cannot declare cursor variables in a package. For example, the following declaration is not allowed:CREATE PACKAGE emp_stuff AS TYPE EmpCurTyp IS REF CURSOR RETURN emp%ROWTYPE; emp_cv EmpCurTyp; -- not allowed END emp_stuff; Remote subprograms on another server cannot accept the values of cursor variables. Therefore, you cannot
Defining Autonomous Transactions → To define autonomous transactions, you use the pragma (compiler directive) AUTONOMOUS_TRANSACTION. The pragma instructs the PL/SQL compiler to mark a routine as autonomous (independent). In this context, the term routine includes Top-level (not nested) anonymous PL/SQL blocks Local, standalone, and packaged functions and procedures Methods of a SQL object type Database triggers You can code the pragma
Using Autonomous Triggers → Among other things, you can use database triggers to log events transparently. Suppose you want to track all inserts into a table, even those that roll back. In the example below, you use a trigger to insert duplicate rows into a shadow table. Because it is autonomous, the trigger can commit inserts into the shadow table whether or not you commit inserts into the main table. -- create a main table
Using Cursor FOR Loops → Using Cursor Variables
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,
Controlling Autonomous Transactions → The first SQL statement in an autonomous routine begins a transaction. When one transaction ends, the next SQL statement begins another transaction. All SQL statements executed since the last commit or rollback make up the current transaction. To control autonomous transactions, use the following statements, which apply only to the current (active) transaction: COMMIT ROLLBACK [TO savepoint_name]