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
Distinct Classes for Each LOB Type → Unlike OCI which uses a common API for operations on BLOBs, CLOBs, and BFILEs, OCCI has distinct
Distinct Values → Number of unique values in the column.
ORA-01415 too many distinct aggregate functions → Cause: The query contains more distinct aggregates than can be processed. The current limit is 255 … . Action: Reduce the number of distinct aggregate functions in the query.
PLS-01471 The keyword DISTINCT must be present in a COUNT(DISTINCT sim_expr) → Cause: The keyword DISTINCT must be present in a COUNT(DISTINCT sim_expr). Action: Refer to ANSI document ANSI X3.135-1992 for details.
QSM-02054 DISTINCT clause in select list in materialized view → Cause: The capability in question is not supported when the materialized view uses the DISTINCT … clause in the select list. Action: Re-phrase the query to avoid the use of the DISTINCT clause.
QSM-02084 DISTINCT clause on a duplicate sensitive aggregate function → Cause: The capability in question is not supported when the materialized view uses the DISTINCT … clause in this context. Action: Re-phrase the query to avoid the use of the DISTINCT clause.
ORA-13347 the coordinates defining an arc are not distinct → of the arc, ensuring that three distinct coordinate values are used.
ORA-14011 names assigned to resulting partitions must be distinct → distinct. Action: Rename resulting partition(s) to ensure that their names are distinct and
QSM-02002 DISTINCT aggregate measure in SELECT list → Cause: The capability in question is not supported when the materialized view uses the DISTINCT … qualifier on an aggregate function. Action: Remove the DISTINCT qualifier.
ORA-01446 cannot select ROWID from view with DISTINCT, GROUP BY, etc. → Cause: A SELECT statement attempted to select ROWIDs from a view containing columns derived from functions or expressions. Because the rows selected in the view do not correspond to underlying physical records, no ROWIDs can be returned. Action: Remove ROWID from the view selection clause, then re-execute the statement.
ORA-30480 DISTINCT option not allowed with GROUP BY CUBE or ROLLUP → ORA-30481 GROUPING function only supported with GROUP BY CUBE or ROLLUP
ORA-02014 cannot select FOR UPDATE from view with DISTINCT, GROUP BY, etc. → functions, SELECT DISTINCT, CONNECT BY clause, or set operation, UNION, INTERSECT, or MINUS. Action: Do not use SELECT... FOR UPDATE on this view.
PLS-01472 In a set_function_specification, if DISTINCT is present, the expression must be a column_specification → Cause: In a set_function_specification, if DISTINCT is present, the expression must be a
ORA-01472 cannot use CONNECT BY on view with DISTINCT, GROUP BY, etc. → and rows of the underlying table. Action: Remove the DISTINCT or GROUP BY from the view or move the CONNECT BY clause into the view.
numkeys (OUT) → The number of distinct keys stored in memory.
Notes → Each hierarchy in a thesaurus represents a distinct, separate branch, corresponding to the four
Unique Identifiers → Unique identifiers are specified for one distinct record in a dimension table. Artificial unique
SQL Features Where LOBs Cannot be Used → Used SQL Feature Example for CLOB Columns SELECT DISTINCT SELECT DISTINCT clobCol from... SELECT