Case 4:23-cv-01147-ALM Document 62-6 Filed 11/12/24 Page 1 of 559 PageID #:
`3835
`
`EXHIBIT 1-5
`
`

`

`Case 4:23-cv-01147-ALM Document 62-6 Filed 11/12/24 Page 2 of 559 PageID #:
`3836
`
`CREATE INDEX
`
`CREATE INDEX
`
`Purpose
`
`Use the CREATE INDEX statement to create an index on:
`
`■ One or more columns of a table, a partitioned table, an index-organized table, or
`a cluster
`
`■ One or more scalar typed object attributes of a table or a cluster
`
`■ A nested table storage table for indexing a nested table column
`
`An index is a schema object that contains an entry for each value that appears in the
`indexed column(s) of the table or cluster and provides direct, fast access to rows.
`Oracle Database supports several types of index:
`
`■ Normal indexes. (By default, Oracle Database creates B-tree indexes.)
`
`■ Bitmap indexes, which store rowids associated with a key value as a bitmap
`
`■ Partitioned indexes, which consist of partitions containing an entry for each
`value that appears in the indexed column(s) of the table
`■ Function-based indexes, which are based on expressions. They enable you to
`construct queries that evaluate the value returned by an expression, which in
`turn may include built-in or user-defined functions.
`
`■ Domain indexes, which are instances of an application-specific index of type
`indextype
`
`See Also:
`
`■ Oracle Database Concepts for a discussion of indexes
`
`■ ALTER INDEX on page 10-88 and DROP INDEX on page 17-80
`
`To create an index in your own schema, one of the following conditions must be
`true:
`
`■ The table or cluster to be indexed must be in your own schema.
`
`■ You must have the INDEX object privilege on the table to be indexed.
`
`■ You must have the CREATE ANY INDEX system privilege.
`
`Prerequisites
`
`SQL Statements: CREATE CLUSTER to CREATE JAVA 14-75
`
`Cloudera Exhibit 1020 - Page 1123 of 1808
`
`Databricks R2 PA 00003259
`-
`-
`-
`
`

`

`Case 4:23-cv-01147-ALM Document 62-6 Filed 11/12/24 Page 3 of 559 PageID #:
`3837
`
`CREATE INDEX
`
`To create an index in another schema, you must have the CREATE ANY INDEX
`system privilege. Also, the owner of the schema to contain the index must have
`either the UNLIMITED TABLESPACE system privilege or space quota on the
`tablespaces to contain the index or index partitions.
`
`To create a domain index in your own schema, in addition to the prerequisites for
`creating a conventional index, you must also have the EXECUTE object privilege on
`the indextype. If you are creating a domain index in another user's schema, then the
`index owner also must have the EXECUTE object privilege on the indextype and its
`underlying implementation type. Before creating a domain index, you should first
`define the indextype.
`
`To create a function-based index, in addition to the prerequisites for creating a
`conventional index, if the index is based on user-defined functions, then those
`functions must be marked DETERMINISTIC. Also, you must have the EXECUTE
`object privilege on any user-defined function(s) used in the function-based index if
`those functions are owned by another user.
`
`See Also: CREATE INDEXTYPE on page 14-105
`
`Syntax
`
`create_index::=
`
`cluster _index_clause : :=
`
`(index_attributes::= on page 14-78)
`
`cluster _index_clause
`
`bitmap_join_index_clause
`
`14-76 SQL Reference
`
`Cloudera Exhibit 1020 - Page 11 24 of 1808
`
`Databricks R2 PA 00003260
`-
`-
`-
`
`

`

`Case 4:23-cv-01147-ALM Document 62-6 Filed 11/12/24 Page 4 of 559 PageID #:
`3838
`
`CREATE INDEX
`
`table_index_clause: :=
`
`cC schema~ ~
`
`)
`
`) ®
`
`)
`
`)
`
`index_properties
`
`(index_properties::= on page 14-78)
`
`bitmap_join_index_clause::=
`
`schema
`
`WHERE
`
`local_partitioned_index
`condition ,___ ________ ___,___.,
`
`index_attributes
`
`(local_partitioned_index::= on page 14-81 , index_attributes::= on page 14-78)
`
`index_expr::=
`
`column 1 - - - - - - . . .
`
`column_expression
`
`SQL Statements: CREATE CLUSTER to CREATE JAVA 14-77
`
`Cloudera Exhibit 1020 - Page 1125 of 1808
`
`Databricks R2 PA 00003261
`-
`-
`-
`
`

`

`Case 4:23-cv-01147-ALM Document 62-6 Filed 11/12/24 Page 5 of 559 PageID #:
`3839
`
`CREATE INDEX
`
`index_properties: :=
`
`global_partitioned_index
`
`local_partitioned_index
`
`(global_partitioned_index::= on page 14-79, local_partitioned_index::= on page 14-81,
`index_attributes::= on page 14-78, domain_index_clause::= on page 14-79)
`
`index_attributes: :=
`
`physical_attributes_clause 1 - - -~
`
`logging_clause 1 - - - - - - - -1
`
`ONLINE > - - - - - - - - - - - - - -<
`
`COMPUTE
`
`STATISTICS >--------<
`
`TABLESPACE
`
`key_compression >------------<
`
`parallel_clause 1 - - - - - - -_ /
`
`(physical_attributes_clause::= on page 14-79, logging_clause::= on page 14-79, key_
`compression::= on page 14-79, parallel_clause::= on page 14-83)
`
`14-78 SQL Reference
`
`Cloudera Exhibit 1020 - Page 1126 of 1808
`
`Databricks R2 PA 00003262
`-
`-
`-
`
`

`

`Case 4:23-cv-01147-ALM Document 62-6 Filed 11/12/24 Page 6 of 559 PageID #:
`3840
`
`CREATE INDEX
`
`physical_attributes_clause: :=
`
`storage_clause 1 - - - -~
`
`(storage_clause::= on page 8-60)
`
`logging_clause::=
`
`LOGGING
`
`key_compression::=
`
`integer
`COMPRESS t+<-----....,___
`
`NOCOMPRESS > - - - - -~
`
`domain_index_clause: :=
`
`INDEXTYPE
`
`indextype
`
`parallel_clause
`
`PARAMETERS
`
`ODCl_parameters
`
`(parallel_clause::= on page 14-83)
`
`global_partitioned_index: :=
`
`GLOBAL
`
`PARTITION
`
`HASH
`
`column_list
`
`RANGE
`
`index_partitioning_clause
`
`SQL Statements: CREATE CLUSTER to CREATE JAVA 14-79
`
`Cloudera Exhibit 1020 - Page 1127 of 1808
`
`Databricks R2 PA 00003263
`-
`-
`-
`
`

`

`Case 4:23-cv-01147-ALM Document 62-6 Filed 11/12/24 Page 7 of 559 PageID #:
`3841
`
`CREATE INDEX
`
`(index_partitioning_clause::= on page 14-80, individual_hash_partitions::= on
`page 14-80, hash_partitions_by_quantity::= on page 14-80)
`
`individual_hash_partitions::=
`
`(partitioning_storage_clause::= on page 14-80)
`
`partitioning_storage_clause::=
`
`TABLESPACE
`
`tablespace 1 - - - - - - - - - - - - - - - - - - - - - - - - - -~
`
`TABLESPACE
`
`TABLESPACE
`
`TABLESPACE
`
`tablespace
`
`hash_partitions_by _quantity::=
`
`OVERFLOW
`
`index_partitioning_clause::=
`
`partition
`
`segment_attributes_clause
`
`14-80 SQL Reference
`
`Cloudera Exhibit 1020 - Page 1128 of 1808
`
`Databricks R2 PA 00003264
`-
`-
`-
`
`

`

`Case 4:23-cv-01147-ALM Document 62-6 Filed 11/12/24 Page 8 of 559 PageID #:
`3842
`
`CREATE INDEX
`
`(segment_attributes_clause::= on page 14-82)
`
`local_partitioned_index: :=
`
`on_list_partitioned_table
`
`on_hash_partitioned_table
`
`on_comp_partitioned_table
`LOCAL f+L-----------~➔
`
`(on_range_partitioned_table::= on page 14-81, on_list_partitioned_table::= on
`page 14-81, on_hash_partitioned_table::= on page 14-82, on_comp_partitioned_table::=
`on page 14-82)
`
`on_range_partitioned_table::=
`
`segment_attributes_clause
`
`key_compression 1 - - - - -~
`partition f -+ -~ - - - - - - - - - -~~~
`
`(segment_attributes_clause::= on page 14-82)
`
`on_list_partitioned_table::=
`
`segment_attributes_clause
`
`key_compression - -~
`
`PARTITION f - r< - - - - - - - - - - - - - - - - - - -_ ,_~
`
`(segment_attributes_clause::= on page 14-82)
`
`SQL Statements: CREATE CLUSTER to CREATE JAVA 14-81
`
`Cloudera Exhibit 1020 - Page 1129 of 1808
`
`Databricks R2 PA 00003265
`-
`-
`-
`
`

`

`Case 4:23-cv-01147-ALM Document 62-6 Filed 11/12/24 Page 9 of 559 PageID #:
`3843
`
`CREATE INDEX
`
`segment_attributes_clause::=
`
`physical_attributes_clause
`
`logging_clause > - - - - - -
`
`(physical_attributes_clause::= on page 14-79, loggin~clause::= on page 14-79
`
`on_hash_partitioned_table: :=
`
`STORE
`
`PARTITION I -¥ - - - - - - - - - - - - - - - - -_ , .__ ,~
`
`tablespace
`
`on_comp_partitioned_table::=
`
`, f1STORE~ '
`
`segment_attribute_clause
`
`key_compression > - - - -
`index_subpartition_clause
`partition 1 -+ -~ - - - - - - - - - -~~ - r " ' - - - - - - - - - - -> - - - - . , .
`PARTITION , - , . . . . . . . - - - - - - - - - - - - - - - - - - - - - - - - - - - -~_ . .__ , ,
`
`(segment_attributes_clause::= on page 14-82, index_subpartition_clause::= on
`page 14-83)
`
`14-82 SQL Reference
`
`Cloudera Exhibit 1020 - Page 1130 of 1808
`
`Databricks R2 PA 00003266
`-
`-
`-
`
`

`

`Case 4:23-cv-01147-ALM Document 62-6 Filed 11/12/24 Page 10 of 559 PageID #:
`3844
`
`CREATE INDEX
`
`index_subpartition_clause: :=
`
`STORE
`
`parallel_clause: :=
`
`NOPARALLEL t - - - - -~
`
`TABLESPACE
`
`tablespace
`
`(storage_clause::= on page 8-60)
`
`Semantics
`
`UNIQUE
`Specify UNIQUE to indicate that the value of the column (or columns) upon which
`the index is based must be unique.
`
`Restrictions on Unique Indexes
`■ You cannot specify both UNIQUE and BITMAP.
`
`■ You cannot specify UNIQUE for a domain index.
`
`See Also:
`"Unique Constraints" on page 8-12 for information on
`the conditions that satisfy a unique constraint
`
`BITMAP
`Specify BITMAP to indicate that index is to be created with a bitmap for each
`distinct key, rather than indexing each row separately. Bitmap indexes store the
`rowids associated with a key value as a bitmap. Each bit in the bitmap corresponds
`to a possible rowid. If the bit is set, then it means that the row with the
`corresponding rowid contains the key value. The internal representation of bitmaps
`
`SQL Statements: CREATE CLUSTER to CREATE JAVA 14-83
`
`Cloudera Exhibit 1020 - Page 1131 of 1808
`
`Databricks R2 PA 00003267
`-
`-
`-
`
`

`

`Case 4:23-cv-01147-ALM Document 62-6 Filed 11/12/24 Page 11 of 559 PageID #:
`3845
`
`CREATE INDEX
`
`is best suited for applications with low levels of concurrent transactions, such as
`data warehousing.
`
`Note: Oracle does not index table rows in which all key columns
`are null except in the case of bitmap indexes. Therefore, if you want
`an index on all rows of a table, then you must either specify NOT
`NULL constraints for the index key columns or create a bitmap
`index.
`
`Restrictions on Bitmap Indexes
`■ You cannot specify BITMAP when creating a global partitioned index.
`
`■ You cannot create a bitmap secondary index on an index-organized table unless
`the index-organized table has a mapping table associated with it.
`
`■ You cannot specify both UNIQUE and BITMAP.
`
`■ You cannot specify BITMAP for a domain index.
`
`See Also:
`
`■ Oracle Database Concepts and Oracle Database Performance Tuning
`Guide for more information about using bitmap indexes
`
`■ CREATE TABLE on page 16-7 for information on mapping
`tables
`
`■
`
`"Bitmap Index Example" on page 14-103
`
`schema
`Specify the schema to contain the index. If you omit schema, then Oracle Database
`creates the index in your own schema.
`
`index
`Specify the name of the index to be created.
`
`See Also: "Creating an Index: Example" on page 14-98 and
`"Creating an Index on an XMLType Table: Example" on page 14-99
`
`14-84 SQL Reference
`
`Cloudera Exhibit 1020 - Page 1132 of 1808
`
`Databricks R2 PA 00003268
`-
`-
`-
`
`

`

`Case 4:23-cv-01147-ALM Document 62-6 Filed 11/12/24 Page 12 of 559 PageID #:
`3846
`
`CREATE INDEX
`
`cluster _index_clause
`Use the cluster_ index_ clause to identify the cluster for which a cluster index
`is to be created. If you do not qualify cluster with schema, then Oracle Database
`assumes the cluster is in your current schema. You cannot create a cluster index for
`a hash cluster.
`
`See Also: CREATE CLUSTER on page 14-2 and "Creating a
`Cluster Index: Example" on page 14-99
`
`table _index_ clause
`Specify the table on which you are defining the index. If you do not qualify table
`with schema, then Oracle Database assumes the table is contained in your own
`schema.
`
`You create an index on a nested table column by creating the index on the nested
`table storage table. Include the NESTED_TABLE_ID pseudocolumn of the storage
`table to create a UNIQUE index, which effectively ensures that the rows of a nested
`table value are distinct.
`
`See Also:
`
`"Indexes on Nested Tables: Example" on page 14-103
`
`You can perform DDL operations (such as ALTER TABLE, DROP TABLE, CREATE
`INDEX) on a temporary table only when no session is bound to it. A session
`becomes bound to a temporary table by performing an INSERT operation on the
`table. A session becomes unbound to the temporary table by issuing a TRUNCATE
`statement or at session termination, or, for a transaction-specific temporary table, by
`issuing a COMMIT or ROLLBACK statement.
`
`Restrictions on the table_index_clause
`If index is locally partitioned, then table must be partitioned.
`■
`
`■
`
`■
`
`If table is index-organized, this statement creates a secondary index. The
`index contains the index key and the logical rowid of the index-organized table.
`The logical rowid excludes columns that are also part of the index key. You
`cannot specify REVERSE for this secondary index, and the combined size of the
`index key and the logical rowid should be less than the block size.
`
`If table is a temporary table, then index will also be temporary with the same
`scope (session or transaction) as table. The following restrictions apply to
`indexes on temporary tables:
`
`■ The only part of index _properties you can specify is index_
`attributes.
`
`SQL Statements: CREATE CLUSTER to CREATE JAVA 14-85
`
`Cloudera Exhibit 1020 - Page 1133 of 1808
`
`Databricks R2 PA 00003269
`-
`-
`-
`
`

`

`Case 4:23-cv-01147-ALM Document 62-6 Filed 11/12/24 Page 13 of 559 PageID #:
`3847
`
`CREATE INDEX
`
`■ Within index_attributes, you cannot specify the physical_
`attributes_clause, theparallel_clause, the logging_clause, or
`TABLES PACE.
`
`See Also: CREATE TABLE on page 16-7 and Oracle Database
`Concepts for more information on temporary tables
`
`t_alias
`Specify a correlation name (alias) for the table upon which you are building the
`index.
`
`Note: This alias is required if the index_ expr references any
`object type attributes or object type methods. See "Creating a
`Function-based Index on a Type Method: Example" on page 14-100
`and "Indexing on Substitutable Columns: Examples" on
`page 14-103.
`
`index_expr
`For index_ expr, specify the column or column expression upon which the index
`is based.
`
`column Specify the name of one or more columns in the table. A bitmap index
`can have a maximum of 30 columns. Other indexes can have as many as 32
`columns. These columns define the index key.
`
`If the index is local nonprefixed (see local_partitioned_index), then the index key must
`contain the partitioning key.
`
`You can create an index on a scalar object attribute column or on the system-defined
`NESTED_TABLE_ID column of the nested table storage table. If you specify an
`object attribute column, then the column name must be qualified with the table
`name. If you specify a nested table column attribute, then it must be qualified with
`the outermost table name, the containing column name, and all intermediate
`attribute names leading to the nested table column attribute.
`
`Restriction on Index Columns You cannot create an index on columns or
`attributes whose type is user-defined, LONG, LONG RAW, LOB, or REF, except that
`Oracle Database supports an index on REF type columns or attributes that have
`been defined with a SCOPE clause.
`
`14-86 SQL Reference
`
`Cloudera Exhibit 1020 - Page 11 34 of 1808
`
`Databricks R2 PA 00003270
`-
`-
`-
`
`

`

`Case 4:23-cv-01147-ALM Document 62-6 Filed 11/12/24 Page 14 of 559 PageID #:
`3848
`
`CREATE INDEX
`
`column_expression Specify an expression built from columns of table,
`constants, SQL functions, and user-defined functions. When you specify column_
`expression, you create a function-based index.
`
`"Notes on Function-based Indexes" on page 14-87,
`See Also:
`"Restrictions on Function-based Indexes" on page 14-88, and
`"Function-Based Index Examples" on page 14-99
`
`Name resolution of the function is based on the schema of the index creator.
`User-defined functions used in column_ expression are fully name resolved
`during the CREATE INDEX operation.
`
`After creating a function-based index, collect statistics on both the index and its
`base table using the DBMS_ STATS package. Such statistics will enable Oracle
`Database to correctly decide when to use the index.
`
`See Also: PLISQL Packages and Types Reference for more
`information on the DBMS_ STATS package
`
`Notes on Function-based Indexes
`■ When you subsequently query a table that uses a function-based index, you
`must ensure in the query that is not null. However, Oracle Database will use a
`function-based index in a query even if the columns specified in the WHERE
`clause are in a different order than their order in the column_ expression that
`defined the function-based index.
`
`See Also:
`
`"Function-Based Index Examples" on page 14-99
`
`■
`
`■
`
`If the function on which the index is based becomes invalid or is dropped, then
`Oracle Database marks the index DISABLED. Queries on a DISABLED index fail
`if the optimizer chooses to use the index. DML operations on a DISABLED
`index fail unless the index is also marked UNUSABLE and the parameter SKIP_
`UNUSABLE INDEXES is set to true. Please refer to ALTER SESSION on
`page 11-59 for more information on this parameter.
`
`If a public synonym for a function, package, or type is used in column_
`expression, and later an actual object with the same name is created in the
`table owner's schema, then Oracle Database disables the function-based index.
`When you subsequently enable the function-based index using ALTER INDEX ...
`ENABLE or ALTER INDEX ... REBUILD, the function, package, or type used in
`the column_expression continues to resolve to the function, package, or
`
`SQL Statements: CREATE CLUSTER to CREATE JAVA 14-87
`
`Cloudera Exhibit 1020 - Page 1135 of 1808
`
`Databricks R2 PA 00003271
`-
`-
`-
`
`

`

`Case 4:23-cv-01147-ALM Document 62-6 Filed 11/12/24 Page 15 of 559 PageID #:
`3849
`
`CREATE INDEX
`
`type to which the public synonym originally pointed. It will not resolve to the
`new function, package, or type.
`
`■
`
`If the definition of a function-based index generates internal conversion to
`character data, then use caution when changing NLS parameter settings.
`Function-based indexes use the current database settings for NLS parameters. If
`you reset these parameters at the session level, then queries using the
`function-based index may return incorrect results. Two exceptions are the
`collation parameters (NLS _ SORT and NLS _ COMP). Oracle Database handles the
`conversions correctly even if these have been reset at the session level.
`
`Restrictions on Function-based Indexes
`■ Any user-defined function referenced in column_ expression must be
`DETERMINISTIC.
`
`■ For a function-based globally partitioned index, the column_expression
`cannot be the partitioning key.
`
`■ The column_ expression can be any form of expression except a scalar
`subquery expression.
`
`■ All functions must be specified with parentheses, even if they have no
`parameters. Otherwise Oracle Database interprets them as column names.
`
`■ Any function you specify in column_ expression must return a repeatable
`value. For example, you cannot specify the SYSDATE or USER function or the
`ROWNUM pseudocolumn.
`
`■ The column_expression cannot contain any aggregate functions.
`
`See Also: CREATE FUNCTION on page 14-61 and PVSQL User's
`Guide and Reference
`
`ASC I DESC
`Use ASC or DESC to indicate whether the index should be created in ascending or
`descending order. Indexes on character data are created in ascending or descending
`order of the character values in the database character set.
`
`Oracle Database treats descending indexes as if they were function-based indexes.
`As with other function-based indexes, the database does not use descending
`indexes until you first analyze the index and the table on which the index is
`defined. See the column_expression clause of this statement.
`
`Restriction on Ascending and Descending Indexes You cannot specify either of
`these clauses for a domain index. You cannot specify DESC for a reverse index.
`
`14-88 SQL Reference
`
`Cloudera Exhibit 1020 - Page 11 36 of 1808
`
`Databricks R2 PA 00003272
`-
`-
`-
`
`

`

`Case 4:23-cv-01147-ALM Document 62-6 Filed 11/12/24 Page 16 of 559 PageID #:
`3850
`
`CREATE INDEX
`
`Oracle Database ignores DESC if index is bitmapped or if the COMPATIBLE
`initialization parameter is set to a value less than 8.1.0.
`
`index_attributes
`Specify the optional index attributes.
`
`physical_attributes_clause Use the physical_attributes_clause to
`establish values for physical and storage characteristics for the index.
`
`If you omit this clause, then Oracle Database sets PCTFREE to 10 and INITRANS to
`2.
`
`Restriction on Index Physical Attributes You cannot specify the PCTUSED
`parameter for an index.
`
`See Also: physical_attributes_clause on page 8-54 and storage_clause
`on page 8-57 for a complete description of these clauses
`
`TABLESPACE For tablespace, specify the name of the tablespace to hold the
`index, index partition, or index sub partition. If you omit this clause, then Oracle
`Database creates the index in the default tables pace of the owner of the schema
`containing the index.
`
`For a local index, you can specify the keyword DEFAULT in place of tablespace.
`New partitions or subpartitions added to the local index will be created in the same
`tablespace(s) as the corresponding partitions or subpartitions of the underlying
`table.
`
`key_compression Specify COMPRESS to enable key compression, which
`eliminates repeated occurrence of key column values and may substantially reduce
`storage. Use integer to specify the prefix length (number of prefix columns to
`compress).
`
`■ For unique indexes, the valid range of prefix length values is from 1 to the
`number of key columns minus 1. The default prefix length is the number of key
`columns minus 1.
`
`■ For nonunique indexes, the valid range of prefix length values is from 1 to the
`number of key columns. The default prefix length is the number of key
`columns.
`
`Oracle Database compresses only nonpartitioned indexes that are nonunique or
`unique indexes of at least two columns.
`
`SQL Statements: CREATE CLUSTER to CREATE JAVA 14-89
`
`Cloudera Exhibit 1020 - Page 113 7 of 1808
`
`Databricks R2 PA 00003273
`-
`-
`-
`
`

`

`Case 4:23-cv-01147-ALM Document 62-6 Filed 11/12/24 Page 17 of 559 PageID #:
`3851
`
`CREATE INDEX
`
`Restriction on Key Compression You cannot specify COMPRESS for a bitmap
`index.
`
`See Also:
`
`"Compressing an Index: Example" on page 14-98
`
`NOCOMPRESS Specify NOCOMPRESS to disable key compression. This is the
`default.
`
`SORT I NOSORT By default, Oracle Database sorts indexes in ascending order
`when it creates the index. You can specify NOSORT to indicate to the database that
`the rows are already stored in the database in ascending order, so that Oracle
`Database does not have to sort the rows when creating the index. If the rows of the
`indexed column or columns are not stored in ascending order, then the database
`returns an error. For greatest savings of sort time and space, use this clause
`immediately after the initial load of rows into a table. If you specify neither of these
`keywords, then SORT is the default.
`
`Restrictions on NOSORT
`■ You cannot specify REVERSE with this clause.
`
`■ You cannot use this clause to create a cluster index partitioned or bitmap index.
`
`■ You cannot specify this clause for a secondary index on an index-organized
`table.
`
`REVERSE Specify REVERSE to store the bytes of the index block in reverse order,
`excluding the rowid.
`
`Restrictions on Reverse Indexes
`■ You cannot specify NOSORT with this clause.
`
`■ You cannot reverse a bitmap index or an index on an index-organized table.
`
`logging_clause Specify whether the creation of the index will be logged
`(LOGGING) or not logged (NOLOGGING) in the redo log file. This setting also
`determines whether subsequent Direct Loader (SQL*Loader) and direct-path
`INSERT operations against the index are logged or not logged. LOGGING is the
`default.
`
`If index is nonpartitioned, then this clause specifies the logging attribute of the
`index.
`
`If index is partitioned, then this clause determines:
`
`14-90 SQL Reference
`
`Cloudera Exhibit 1020 - Page 113 8 of 1808
`
`Databricks R2 PA 00003274
`-
`-
`-
`
`

`

`Case 4:23-cv-01147-ALM Document 62-6 Filed 11/12/24 Page 18 of 559 PageID #:
`3852
`
`CREATE INDEX
`
`■ The default value of all partitions specified in the CREATE statement, unless you
`specify the logging_ clause in the PARTITION description clause
`
`■ The default value for the segments associated with the index partitions
`
`■ The default value for local index partitions or subpartitions added implicitly
`during subsequent ALTER TABLE ... ADD PARTITION operations
`
`The logging attribute of the index is independent of that of its base table.
`
`If you omit this clause, then the logging attribute is that of the tablespace in which it
`resides.
`
`See Also:
`
`■
`
`Jogging_clause on page 8-47 for a full description of this clause
`
`■ Oracle Database Concepts and Oracle Data Warehousing Guide for
`more information about logging and parallel DML
`
`■
`
`"Creating an Index in NOLOGGING Mode: Example" on
`page 14-98
`
`ONLINE Specify ONLINE to indicate that DML operations on the table will be
`allowed during creation of the index.
`
`Restrictions on Online Index Building
`■ Parallel DML is not supported during online index building. If you specify
`ONLINE and then issue parallel DML statements, then Oracle Database returns
`an error.
`
`■ You cannot specify ONLINE for a bitmap index or a cluster index.
`
`■ You cannot specify ONLINE for a conventional index on a UROWID column.
`
`■ For a nonunique secondary index on an index-organized table, the number of
`index key columns plus the number of primary key columns that are included
`in the logical rowid in the index-organized table cannot exceed 32. The logical
`rowid excludes columns that are part of the index key.
`
`See Also: Oracle Database Concepts for a description of online
`index building and rebuilding
`
`In earlier releases, you could use this clause to start or
`COMPUTE STATISTICS
`stop the collection of statistics on an index. This clause has been deprecated. Oracle
`
`SQL Statements: CREATE CLUSTER to CREATE JAVA 14-91
`
`Cloudera Exhibit 1020 - Page 1139 of 1808
`
`Databricks R2 PA 00003275
`-
`-
`-
`
`

`

`Case 4:23-cv-01147-ALM Document 62-6 Filed 11/12/24 Page 19 of 559 PageID #:
`3853
`
`CREATE INDEX
`
`Database now automatically collects statistics during index creation and rebuild.
`This clause is supported for backward compatibility and will not cause errors.
`
`Restriction on COMPUTE STATISTICS Clause You cannot specify this clause for a
`domain index.
`
`parallel_clause
`Specify the parallel_clause if you want creation of the index to be parallelized.
`
`For complete information on this clause, please refer to parallel_clause on page 16-57
`in the documentation on CREATE TABLE.
`
`Index Partitioning Clauses
`Use the global_partitioned_indexclause and the local partitioned
`index clauses to partition index.
`
`The storage of partitioned database entities in tablespaces of different block sizes is
`subject to several restrictions. Please refer to Oracle Database Administrator's Guide
`for a discussion of these restrictions.
`
`See Also:
`
`"Partitioned Index Examples" on page 14-101
`
`global_partitioned_index
`The global _partitioned_ index clause lets you specify that the partitioning of
`the index is user defined and is not equipartitioned with the underlying table. By
`default, nonpartitioned indexes are global indexes.
`
`You can partition a global index by range or by hash. In both cases, you can specify
`up to 32 columns as partitioning key columns. The partitioning column list must
`specify a left prefix of the index column list. That is, if the index is defined on
`columns a, b, and c, then for the columns you can specify ( a , b, c) , or (a, b) , or (a,
`c) , but you cannot specify (b, c) or ( c) or (b, a). If you omit the partition names,
`then Oracle Database assigns names of the form SYS_ Pn.
`
`GLOBAL PARTITION BY RANGE Use this clause to create a range-partitioned
`global index. Oracle Database will partition the global index on the ranges of values
`from the table columns you specify in the column list.
`
`"Creating a Range-Partitioned Global Index: Example"
`See Also:
`on page 14-101
`
`14-92 SQL Reference
`
`Cloudera Exhibit 1020 - Page 1140 of 1808
`
`Databricks R2 PA 00003276
`-
`-
`-
`
`

`

`Case 4:23-cv-01147-ALM Document 62-6 Filed 11/12/24 Page 20 of 559 PageID #:
`3854
`
`CREATE INDEX
`
`GLOBAL PARTITION BY HASH Use this clause to create a hash-partitioned global
`index. Oracle Database assigns rows to the partitions using a hash function on
`values in the partitioning key columns.
`
`the CREATE TABLE clause hash_partitioning on
`See Also:
`page 16-50 for information on the two methods of hash partitioning
`and "Creating a Hash-Partitioned Global Index: Example" on
`page 14-101
`
`Restrictions on Global Partitioned Indexes
`■ The partitioning key column list cannot contain the ROWID pseudocolumn or a
`column of type ROWID.
`
`■ The only property you can specify for hash partitions is tablespace storage.
`Therefore, you cannot specify LOB or varray storage clauses in the
`parti tioning_storage_ clause of indi vidual_hash_parti tions.
`
`■ You cannot specify the OVERFLOW clause of hash_parti tions_by_
`quantity, as that clause is valid only for index-organized table partitions.
`
`If your enterprise has or will have databases using different
`Note:
`character sets, then use caution when partitioning on character
`columns. The sort sequence of characters is not identical in all
`character sets.
`
`See Also: Oracle Database Globalization Support Guide for more
`information on character set support
`
`index_partitioning_clause Use this clause to describe the individual index
`partitions. The number of repetitions of this clause determines the number of
`partitions. If you omit part i ti on, then Oracle Database generates a name with the
`form SYS Pn.
`
`For VALUES LESS THAN (value_list), specify the noninclusive upper bound for
`the current partition in a global index. The value list is a comma-delimited, ordered
`list of literal values corresponding to the column list in the global_
`parti tioned_index clause. Always specify MAXVALUE as the value of the last
`partition.
`
`SQL Statements: CREATE CLUSTER to CREATE JAVA 14-93
`
`Cloudera Exhibit 1020 - Page 1141 of 1808
`
`Databricks R2 PA 00003277
`-
`-
`-
`
`

`

`Case 4:23-cv-01147-ALM Document 62-6 Filed 11/12/24 Page 21 of 559 PageID #:
`3855
`
`CREATE INDEX
`
`If the index is partitioned on a DATE column, and if the date
`Note:
`format does not specify the first two digits of the year, then you
`must use the TO DATE function with a 4-character format mask for
`the year. The date format is determined implicitly by NLS _
`TERRITORY or explicitly by NLS_DATE_FORMAT. Please refer to
`Oracle Database Globalization Support Guide for more information on
`these initialization parameters.
`
`See Also:
`
`"Range Partitioning Example" on page 16-73
`
`local_partitioned_index
`The 1 ocal _partitioned_ index clauses let you specify that the index is
`partitioned on the same columns, with the same number of partitions and the same
`partition bounds as table. Oracle Database automatically maintains local index
`partitioning as the underlying table is repartitioned.
`
`on_range_partitioned_table This clause lets you specify the names and attributes
`of index partitions on a range-partitioned table. If you specify this clause, then the
`number of PARTITION clauses must be equal to the number of table partitions, and
`in the same order. If you omit partition, then Oracle Database generates a name
`that is consistent with the corresponding table partition. If the name conflicts with
`an existing index partition name, then the database uses the form SYS_ Pn.
`
`You cannot specify key compression for an index partition unless you have
`specified key compression for the index.
`
`on_list_partitioned_table The on list_parti tioned_ table clause is identical
`to on_range_partitioned_table on page 14-94.
`
`on_hash_partitioned_table This clause lets you specify names and tablespace
`storage for index partitions on a hash-partitioned table.
`
`If you specify any PARTITION clauses, then the number of these clauses must be
`equal to the number of table partitions. If you omit partition, then Oracle
`Database generates a name that is consistent with the corresponding table partition.
`If the name conflicts with an existing index partition name, then the database uses
`the form SYS_ Pn. You can optionally specify tablespace storage for one or more
`individual partitions. If you do