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
Jump to Full-Text Indexing → You can create a full-text index on file content using PL/SQL package DBMS_XDBT. This lets queries apply function jcr:contains to property jcr:data of a jcr:content node. Full-text indexes on other properties
Jump to Indexing with a CONTEXT Index → This section contains these topics: Introduction to CONTEXT Indexes Effect of a CONTEXT Index on CONTAINS CONTEXT Index Preferences Introduction to Section Groups
Jump to 4.2.3 Indexing Data → The most efficient time to create indexes is after data has been loaded. In this way, space management becomes simpler, and no index maintenance takes place for each row inserted. SQL*Loader automatically
Jump to Indexing → functionality with these differences: Integer indexing is not supported for ore.vector objects … . Negative integer indexes are not supported. Row order is not preserved. This
Jump to Presorting Data for Faster Indexing → You can improve the performance of direct path loads by presorting your data on indexed columns. Presorting minimizes temporary storage requirements during the load. Presorting also enables you to take
Jump to Parallel Indexing → Parallel indexing can improve index performance when you have multiple CPUs. To create an index in
Jump to 3.7 Indexing GeoRaster Data → : Function-based indexes on metadata objects using the Oracle XMLType or Oracle Text document indexing
Jump to D.2.3.1 Theme Indexing → Enables the indexing and subsequent querying of document concepts with the ABOUT operator with
Jump to 12.6 Servers and Indexing → Manager in Oracle Enterprise Manager. See Also: Chapter 3, " Indexing with Oracle Text" for more information about indexing and index synchronization
Jump to 1.7.1 R-Tree Indexing → A spatial R-tree index can index spatial data of up to four dimensions. An R-tree index approximates each geometry by a single rectangle that minimally encloses the geometry (called the minimum bounding
Jump to D.2 Indexing → The following sections describe the multilingual indexing features: Multilingual Features for Text
Jump to 7.3 Indexing of LRS Data → If LRS data has four dimensions (three plus the M dimension) and if you need to index all three non-measure dimensions, you must use a spatial R-tree index to index the data, and you must specify PARAMETERS('sdo_indx_dims=3')
Jump to 1.7 Indexing of Spatial Data → The introduction of spatial indexing capabilities into the Oracle database engine is a key feature … available. The following sections explain the concepts and options associated
Jump to 7.8 Frequently Asked Questions About Indexing Performance → This section answers some of the frequently asked questions about indexing performance.
Jump to 7.8.1 How long should indexing take? → Answer: Indexing text is a resource-intensive process. The speed of indexing will depend on the … power of the hardware involved. Indexing speed
Jump to 7.8.5 Can parallel indexing improve performance? → Answer: Parallel indexing can improve index performance when you have a large amount of data, and … the index with up to three separate indexing processes depending
Jump to 7.8.3 How much disk overhead will indexing require? → Answer: The overhead, the amount of space needed for the index tables, varies between about 50% of the original text volume and 200%. Generally, the larger the total amount of text, the smaller the overhead,
Jump to 7.8.4 How does the format of my data affect indexing? → 500MB, because there is ten times as much plain text in the latter set. Indexing time is less clear-cut
Jump to 7.8.7 How can I tell how much indexing has completed? → Answer: You can use the CTX_OUTPUT.START_LOG procedure to log output from the indexing process
Jump to Example 3-2 Creating, Indexing, Storing, and Querying ST_GEOMETRY Data → CREATE TABLE cola_markets ( mkt_id NUMBER PRIMARY KEY, name VARCHAR2(32), shape ST_GEOMETRY); INSERT INTO cola_markets VALUES( 1, 'cola_a', ST_GEOMETRY( SDO_GEOMETRY( 2003, -- two-dimensional polygon