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

`

`Case 4:23-cv-01147-ALM Document 62-5 Filed 11/12/24 Page 2 of 543 PageID #:
`3293
`
`logging_clause
`
`DDL:
`
`■
`
`■
`
`CREATE TABLE ... AS SELECT
`
`CREATE TABLE ... LOB_storage_clause ... LOB_parameters ... NOCACHE I
`CACHE READS
`
`■ ALTER TABLE ... LOB_storage_clause ... LOB_parameters ... NOCACHE
`CACHE READS (to specify logging of newly created LOB columns)
`
`■ ALTER TABLE ... modify_LOB_storage_clause ... modify_LOB_
`parameters ... NOCACHE I CACHE READS (to change logging of existing LOB
`columns)
`
`■ ALTER TABLE ... MOVE
`
`■ ALTER TABLE ... [all partition operations that involve data movement]
`
`■ ALTER TABLE ... ADD PARTITION (hash partition only)
`
`■ ALTER TABLE ... MERGE PARTITIONS
`
`■ ALTER TABLE ... SPLIT PARTITION
`
`■ ALTER TABLE ... MOVE PARTITION
`
`■ ALTER TABLE ... MODIFY PARTITION ... ADD SUBPARTITION
`
`■ ALTER TABLE ... MODIFY PARTITION ... COALESCE SUBPARTITION
`
`■ ALTER TABLE ... MODIFY PARTITION ... REBUILD UNUSABLE INDEXES
`
`■
`
`CREATE INDEX
`
`■ ALTER INDEX ... REBUILD
`
`■ ALTER INDEX ... REBUILD PARTITION
`
`■ ALTER INDEX ... SPLIT PARTITION
`
`For objects other than LOBs, if you omit this clause, then the logging attribute of
`the object defaults to the logging attribute of the tablespace in which it resides.
`
`For LOBs, if you omit this clause:
`
`■
`
`■
`
`If you specify CACHE, then LOGGING is used (because you cannot have CACHE
`NO LOGGING).
`
`If you specify NOCACHE or CACHE READS, then the logging attribute defaults to
`the logging attribute of the tables pace in which it resides.
`
`Common SQL DDL Clauses 8-49
`
`Cloudera Exhibit 1020 - Page 58 1 of 1808
`
`Databricks R2 PA 00002717
`-
`-
`-
`
`

`

`Case 4:23-cv-01147-ALM Document 62-5 Filed 11/12/24 Page 3 of 543 PageID #:
`3294
`
`logging_clause
`
`NOLOGGING does not apply to LOBs that are stored inline with row data. That is, if
`you specify NOLOGGING for LOBs with values less than 4000 bytes and you have
`not disabled STORAGE IN ROW, then Oracle ignores the NOLOGGING specification
`and treats the LOB data the same as other table data.
`
`See Also: Oracle Database Concepts and Oracle Database
`Administrator's Guide for more information about logging and
`parallel DML
`
`8-50 SQL Reference
`
`Cloudera Exhibit 1020 - Page 582 of 1808
`
`Databricks R2 PA 00002718
`-
`-
`-
`
`

`

`Case 4:23-cv-01147-ALM Document 62-5 Filed 11/12/24 Page 4 of 543 PageID #:
`3295
`
`parallel_clause
`
`parallel_ clause
`
`Purpose
`
`The par al 1 el_ clause lets you parallelize the creation of a database object and
`set the default degree of parallelism for subsequent queries of and DML operations
`on the object.
`
`You can specify the parallel_ clause in the following statements:
`
`■
`
`CREATE TABLE: to set parallelism for the table (see CREATE TABLE on
`page 16-7).
`
`■ ALTER TABLE (see ALTER TABLE on page 12-2):
`
`To change parallelism for the table
`
`To parallelize the operations of adding, coalescing, exchanging, merging,
`splitting, truncating, dropping, or moving a table partition
`
`CREATE CLUSTER and ALTER CLUSTER: to set or alter parallelism for a cluster
`(see CREATE CLUSTER on page 14-2 and ALTER CLUSTER on page 10-6).
`
`CREATE INDEX: to set parallelism for the index (see CREATE INDEX on
`page 14-75).
`
`■
`
`■
`
`■ ALTER INDEX (see ALTER INDEX on page 10-88):
`
`To change parallelism for the index
`
`To parallelize the rebuilding of the index or the splitting of an index
`partition
`
`■
`
`CREATE MATERIALIZED VIEW: to set parallelism for the materialized view (see
`CREATE MATERIALIZED VIEW on page 15-5).
`
`■ ALTER MATERIALIZED VIEW (see ALTER MATERIALIZED VIEW on
`page 11-2):
`
`To change parallelism for the materialized view
`
`To parallelize the operations of adding, coalescing, exchanging, merging,
`splitting, truncating, dropping, or moving a materialized view partition
`
`To parallelize the operations of adding or moving materialized view
`sub partitions
`
`Common SQL DDL Clauses 8-51
`
`Cloudera Exhibit 1020 - Page 583 of 1808
`
`Databricks R2 PA 00002719
`-
`-
`-
`
`

`

`Case 4:23-cv-01147-ALM Document 62-5 Filed 11/12/24 Page 5 of 543 PageID #:
`3296
`
`parallel_clause
`
`■
`
`CREATE MATERIALIZED VIEW LOG: to set parallelism for the materialized view
`log (see CREATE MATERIALIZED VIEW LOG on page 15-33).
`
`■ ALTER MATERIALIZED VIEW LOG (see ALTER MATERIALIZED VIEW LOG on
`page 11-21):
`
`To change parallelism for the materialized view log
`
`To parallelize the operations of adding, coalescing, exchanging, merging,
`splitting, truncating, dropping, or moving a materialized view log partition
`
`■ ALTER DATABASE ... RECOVER: to recover the database (see ALTER DATABASE
`on page 10-11).
`
`■ ALTER DATABASE ... standby_database_clauses: to parallelize operations
`on the standby database (see ALTER DATABASE on page 10-11).
`
`Syntax
`
`parallel_clause: :=
`
`NOPARALLEL 1 - - - - -~
`
`integer
`PARALLEL I -+ " - - - - - - - ' . , _ /
`
`Semantics
`
`This section describes the semantics of the parallel_clause. For additional
`information, refer to the SQL statement in which you set or reset parallelism for a
`particular database object or operation.
`
`Note: The syntax of the parallel_clause supersedes syntax
`appearing in earlier releases of Oracle. Superseded syntax is still
`supported for backward compatibility but may result in slightly
`different behavior from that documented.
`
`NOPARALLEL Specify NO PARALLEL for serial execution. This is the default.
`
`PARALLEL Specify PARALLEL if you want Oracle to select a degree of parallelism
`equal to the number of CPUs available on all participating instances times the value
`of the PARALLEL_ THREADS_ PER_ CPU initialization parameter.
`
`8-52 SQL Reference
`
`Cloudera Exhibit 1020 - Page 584 of 1808
`
`Databricks R2 PA 00002720
`-
`-
`-
`
`

`

`Case 4:23-cv-01147-ALM Document 62-5 Filed 11/12/24 Page 6 of 543 PageID #:
`3297
`
`parallel_clause
`
`PARALLEL integer Specification of integer indicates the degree of parallelism,
`which is the number of parallel threads used in the parallel operation. Each parallel
`thread may use one or two parallel execution servers. Normally Oracle calculates
`the optimum degree of parallelism, so it is not necessary for you to specify
`integer.
`
`Common SQL DDL Clauses 8-53
`
`Cloudera Exhibit 1020 - Page 585 of 1808
`
`Databricks R2 PA 00002721
`-
`-
`-
`
`

`

`Case 4:23-cv-01147-ALM Document 62-5 Filed 11/12/24 Page 7 of 543 PageID #:
`3298
`
`physical_attributes_clause
`
`physical_attributes_ clause
`
`Purpose
`
`The physical_attributes_clause lets you specify the value of the PCTFREE,
`PCTUSED, and IN I TRANS parameters and the storage characteristics of a table,
`cluster, index, or materialized view.
`
`You can specify the physical_attributes_clause in the following statements:
`
`■
`
`■
`
`CREATE CLUSTER and ALTER CLUSTER: to set or change the physical attributes
`of the cluster and all tables in the cluster (see CREATE CLUSTER on page 14-2
`and ALTER CLUSTER on page 10-6).
`
`CREATE TABLE: to set the physical attributes of the table, a table partition, the
`OIDINDEX of an object table, or the overflow segment of an index-organized
`table (see CREATE TABLE on page 16-7).
`
`■ ALTER TABLE: to change the physical attributes of the table, the default
`physical attributes of future table partitions, or the physical attributes of
`existing table partitions (see ALTER TABLE on page 12-2). The following
`restrictions apply:
`
`You cannot specify physical attributes for a temporary table.
`
`You cannot specify physical attributes for a clustered table. Tables in a
`cluster inherit the physical attributes of the cluster.
`
`■
`
`CREATE INDEX: to set the physical attributes of an index or index partition (see
`CREATE INDEX on page 14-75).
`
`■ ALTER INDEX: to change the physical attributes of the index, the default
`physical attributes of future index partitions, or the physical attributes of
`existing index partitions (see ALTER INDEX on page 10-88).
`
`■
`
`CREATE MATERIALIZED VIEW: to set the physical attributes of the materialized
`view, one of its partitions, or the index Oracle Database generates to maintain
`the materialized view (see CREATE MATERIALIZED VIEW on page 15-5).
`
`■ ALTER MATERIALIZED VIEW: to change the physical attributes of the
`materialized view, the default physical attributes of future partitions, the
`physical attributes of an existing partition, or the index Oracle creates to
`maintain the materialized view (see ALTER MATERIALIZED VIEW on
`page 11-2).
`
`8-54 SQL Reference
`
`Cloudera Exhibit 1020 - Page 586 of 1808
`
`Databricks R2 PA 00002722
`-
`-
`-
`
`

`

`Case 4:23-cv-01147-ALM Document 62-5 Filed 11/12/24 Page 8 of 543 PageID #:
`3299
`
`physical_attributes_clause
`
`■
`
`CREATE MATERIALIZED VIEW LOG and ALTER MATERIALIZED VIEW LOG: to
`set or change the physical attributes of the materialized view log (see CREATE
`MATERIALIZED VIEW LOG on page 15-33 and ALTER MATERIALIZED
`VIEW LOG on page 11-21).
`
`Syntax
`
`physical_attributes_clause: :=
`
`storage_clause ,___
`
`(storage_clause::= on page 8-60)
`
`Semantics
`
`This section describes the parameters of the physical_attributes_ clause. For
`additional information, refer to the SQL statement in which you set or reset these
`parameters for a particular database object.
`
`PCTFREE integer
`Specify a whole number representing the percentage of space in each data block of
`the database object reserved for future updates to rows of the object. The value of
`PCTFREE must be a value from O to 99. A value of O means that the entire block can
`be filled by inserts of new rows. The default value is 10. This value reserves 10% of
`each block for updates to existing rows and allows inserts of new rows to fill a
`maximum of 90% of each block.
`
`PCTFREE has the same function in the statements that create and alter tables,
`partitions, clusters, indexes, materialized views, and materialized view logs. The
`combination of PCTFREE and PCTUSED determines whether new rows will be
`inserted into existing data blocks or into new blocks.
`
`Restriction on the PCTFREE Clause When altering an index, you can specify this
`parameter only in the modify_index_default_attrs clause and the split_
`partition_ clause.
`
`Common SQL DDL Clauses 8-55
`
`Cloudera Exhibit 1020 - Page 587 of 1808
`
`Databricks R2 PA 00002723
`-
`-
`-
`
`

`

`Case 4:23-cv-01147-ALM Document 62-5 Filed 11/12/24 Page 9 of 543 PageID #:
`3300
`
`physical_attributes_clause
`
`PCTUSED integer
`Specify a whole number representing the minimum percentage of used space that
`Oracle maintains for each data block of the database object. A block becomes a
`candidate for row insertion when its used space falls below PCTUSED. PCTUSED is
`specified as a positive integer from O to 99 and defaults to 40.
`
`PCTUSED has the same function in the statements that create and alter tables,
`partitions, clusters, materialized views, and materialized view logs.
`
`PCTUSED is not a valid table storage characteristic for an index-organized table.
`
`The sum of PCTFREE and PCTUSED must be equal to or less than 100. You can use
`PCTFREE and PCTUSED together to utilize space within a database object more
`efficiently.
`
`Restrictions on the PCTUSED Clause You cannot specify this parameter for an
`index or for the index segment of an index-organized table.
`
`See Also: Oracle Database Performance Tuning Guide for
`information on the performance effects of different values of
`PCTUSED and PCTFREE
`
`INITRANS integer
`Specify the initial number of concurrent transaction entries allocated within each
`data block allocated to the database object. This value can range from 1 to 255 and
`defaults to 1, with the following exceptions:
`
`■
`
`■
`
`The default INITRANS value for a cluster is 2 or the default INITRANS value of
`the tablespace in which the cluster resides, whichever is greater.
`
`The default value for an index is 2.
`
`In general, you should not change the INITRANS value from its default.
`
`Each transaction that updates a block requires a transaction entry in the block. The
`size of a transaction entry depends on your operating system. This parameter
`ensures that a minimum number of concurrent transactions can update the block
`and helps avoid the overhead of dynamically allocating a transaction entry.
`
`The INITRANS parameter serves the same purpose in the statements that create and
`alter tables, partitions, clusters, indexes, materialized views, and materialized view
`logs.
`
`8-56 SQL Reference
`
`Cloudera Exhibit 1020 - Page 588 of 1808
`
`Databricks R2 PA 00002724
`-
`-
`-
`
`

`

`Case 4:23-cv-01147-ALM Document 62-5 Filed 11/12/24 Page 10 of 543 PageID #:
`3301
`
`physical_attributes_clause
`
`MAX.TRANS Parameter
`In earlier releases, the MAXTRANS parameter determined the maximum number of
`concurrent update transactions allowed for each data block in the segment. This
`parameter has been deprecated. Oracle now automatically allows up to 255
`concurrent update transactions for any data block, depending on the available
`space in the block.
`
`Existing objects for which a value of MAXTRANS has already been set retain that
`setting. However, if you attempt to change the value for MAXTRANS, Oracle ignores
`the new specification and substitutes the value 255 without returning an error.
`
`storage_ clause
`The storage_ clause lets you specify storage characteristics for the table, object
`table O1D index, partition, LOB data segment, LOB index segment, or
`index-organized table overflow data segment. This clause has performance
`ramifications for large tables. Storage should be allocated to minimize dynamic
`allocation of additional space. Please refer to the storage_clause on page 8-58 for
`more information.
`
`Common SQL DDL Clauses 8-57
`
`Cloudera Exhibit 1020 - Page 589 of 1808
`
`Databricks R2 PA 00002725
`-
`-
`-
`
`

`

`Case 4:23-cv-01147-ALM Document 62-5 Filed 11/12/24 Page 11 of 543 PageID #:
`3302
`
`storage_clause
`
`storage_clause
`
`Purpose
`
`The storage_ clause lets you specify how Oracle Database should store a
`database object. Storage parameters affect both how long it takes to access data
`stored in the database and how efficiently space in the database is used.
`
`See Also: Oracle Database Performance Tuning Guide for a
`discussion of the effects of the storage parameters
`
`When you create a cluster, index, materialized view, materialized view log, rollback
`segment, table, or partition, you can specify values for the storage parameters for
`the segments allocated to these objects. If you omit any storage parameter, then
`Oracle uses the value of that parameter specified for the tablespace in which the
`object resides.
`
`Note: The specification of storage parameters for objects in locally
`managed tablespaces is supported for backward compatibility. If
`you are using locally managed tablespaces, you can omit these
`storage parameter when creating objects in those tablespaces.
`
`When you alter a cluster, index, materialized view, materialized view log, rollback
`segment, table, or partition, you can change the values of storage parameters. The
`new values affect only future extent allocations.
`
`The storage_clause is part of the physical_attributes_clause, so you can
`specify this clause in any of the statements where you can specify the physical
`attributes clause (see physical_attributes_clause on page 8-54). In addition, you can
`specify the storage_clause in the following statements:
`
`■
`
`■
`
`■
`
`CREATE CLUSTER and ALTER CLUSTER: to set or change the storage
`characteristics of the cluster and all tables in the cluster (see CREATE CLUSTER
`on page 14-2 and ALTER CLUSTER on page 10-6).
`
`CREATE INDEX and ALTER INDEX: to set or change the storage characteristics
`of an index or index partition (see CREATE INDEX on page 14-75 and ALTER
`INDEX on page 10-88).
`
`CREATE MATERIALIZED VIEW and ALTER MATERIALIZED VIEW: to set or
`change the storage characteristics of a materialized view, one of its partitions, or
`
`8-58 SQL Reference
`
`Cloudera Exhibit 1020 - Page 590 of 1808
`
`Databricks R2 PA 00002726
`-
`-
`-
`
`

`

`Case 4:23-cv-01147-ALM Document 62-5 Filed 11/12/24 Page 12 of 543 PageID #:
`3303
`
`storage_clause
`
`the index Oracle generates to maintain the materialized view (see CREATE
`MATERIALIZED VIEW on page 15-5 and ALTER MATERIALIZED VIEW on
`page 11-2).
`
`CREATE MATERIALIZED VIEW LOG and ALTER MATERIALIZED VIEW LOG: to
`set or change the storage characteristics of the materialized view log (see
`CREATE MATERIALIZED VIEW LOG on page 15-33 and ALTER
`MATERIALIZED VIEW LOG on page 11-21).
`
`CREATE ROLLBACK SEGMENT and ALTER ROLLBACK SEGMENT: to set or
`change the storage characteristics of a rollback segment (see CREATE
`ROLLBACK SEGMENT on page 15-81 and ALTER ROLLBACK SEGMENT on
`page 11-53).
`
`CREATE TABLE and ALTER TABLE: to set the storage characteristics of a LOB
`data segment of the table or one of its partitions or subpartitions (see CREATE
`TABLE on page 16-7 and ALTER TABLE on page 12-2).
`
`CREATE TABLESPACE and ALTER TABLESPACE: to set or change the default
`storage characteristics for objects created in the tablespace (see CREATE
`TABLESPACE on page 16-80 and ALTER TABLESPACE on page 12-105).
`
`constraint: to specify storage for the index (and its partitions, if it is a
`partitioned index) used to enforce the constraint (see constraint on page 8-5).
`
`■
`
`■
`
`■
`
`■
`
`■
`
`Prerequisites
`
`To change the value of a STORAGE parameter, you must have the privileges
`necessary to use the appropriate CREATE or ALTER statement.
`
`Common SQL DDL Clauses 8-59
`
`Cloudera Exhibit 1020 - Page 591 of 1808
`
`Databricks R2 PA 00002727
`-
`-
`-
`
`

`

`Case 4:23-cv-01147-ALM Document 62-5 Filed 11/12/24 Page 13 of 543 PageID #:
`3304
`
`storage_clause
`
`Syntax
`
`storage_clause: :=
`
`STORAGE
`
`Semantics
`
`NEXT
`
`MIN EXTENTS
`
`MAXEXTENTS
`
`FREELISTS
`
`FREELIST
`
`integer f - - - - - - - - - - - l
`
`integer,___ ____ _____,
`
`NULL>-------~
`OPTIMAL 1 -+ " - - - - - - - - - - - - - - - - " - - - l
`
`BUFFER_POOL
`
`KEEP
`
`DEFAULT
`
`This section describes the parameters of the storage_clause. For additional
`information, refer to the SQL statement in which you set or reset these parameters
`for a particular database object.
`
`8-60 SQL Reference
`
`Cloudera Exhibit 1020 - Page 592 of 1808
`
`Databricks R2 PA 00002728
`-
`-
`-
`
`

`

`Case 4:23-cv-01147-ALM Document 62-5 Filed 11/12/24 Page 14 of 543 PageID #:
`3305
`
`storage_clause
`
`Note: The storage_clause is interpreted differently for locally
`managed tablespaces. At creation, Oracle ignores MAXEXTENTS and
`uses the remaining parameter values to calculate the initial size of
`the segment. For more information, see CREATE TABLESPACE on
`page 16-80.
`
`See Also:
`page 8-66
`
`"Specifying Table Storage Attributes: Example" on
`
`INITIAL
`Specify in bytes the size of the first extent of the object. Oracle allocates space for
`this extent when you create the schema object. Use Kor M to specify this size in
`kilobytes or megabytes.
`
`The default value is the size of 5 data blocks. In tablespaces with manual
`segment-space management, the minimum value is the size of 2 data blocks plus
`one data block for each free list group you specify. In tablespaces with automatic
`segment-space management, the minimum value is 5 data blocks. The maximum
`value depends on your operating system. Please refer to FREELIST GROUPS on
`page 8-63 for information on freelist groups for more information.
`
`In dictionary-managed tablespaces, if MINIMUM EXTENT was specified for the
`tablespace when it was created, then Oracle rounds the value of INITIAL up to the
`specified MINIMUM EXTENT size if necessary. If MINIMUM EXTENT was not specified,
`then Oracle rounds the INITIAL extent size for segments created in that tablespace
`up to the minimum value (see preceding paragraph), or to multiples of 5 blocks if
`the requested size is greater than 5 blocks.
`
`In locally managed tablespaces, Oracle uses the value of INITIAL in conjunction
`with the size of extents specified for the tablespace to determine the first extent of
`the object. For example, in a uniform locally managed tablespace with SM extents, if
`you specify an INITIAL value of lM, then Oracle creates five lM extents.
`
`Restriction on INITIAL You cannot specify INITIAL in an ALTER statement.
`
`NEXT
`Specify in bytes the size of the next extent to be allocated to the object. Use Kor M to
`specify the size in kilobytes or megabytes. The default value is the size of 5 data
`blocks. The minimum value is the size of 1 data block. The maximum value
`depends on your operating system. Oracle rounds values up to the next multiple of
`
`Common SQL DDL Clauses 8-61
`
`Cloudera Exhibit 1020 - Page 593 of 1808
`
`Databricks R2 PA 00002729
`-
`-
`-
`
`

`

`Case 4:23-cv-01147-ALM Document 62-5 Filed 11/12/24 Page 15 of 543 PageID #:
`3306
`
`storage_clause
`
`the data block size for values less than 5 data blocks. For values greater than 5 data
`blocks, Oracle rounds up to a value that minimizes fragmentation, as described in
`Oracle Database Administrator's Guide.
`
`If you change the value of the NEXT parameter (that is, if you specify it in an ALTER
`statement), then the next allocated extent will have the specified size, regardless of
`the size of the most recently allocated extent and the value of the PCT INCREASE
`parameter.
`
`See Also: Oracle Database Administrator's Guide for information on
`how Oracle minimizes fragmentation
`
`PCTINCREASE
`Specify the percent by which the third and subsequent extents grow over the
`preceding extent. The default value is 50, meaning that each subsequent extent is
`50% larger than the preceding extent. The minimum value is 0, meaning all extents
`after the first are the same size. The maximum value depends on your operating
`system.
`
`Oracle rounds the calculated size of each new extent to the nearest multiple of the
`data block size.
`
`If you change the value of the PCT INCREASE parameter (that is, if you specify it in
`an ALTER statement), then Oracle calculates the size of the next extent using this
`new value and the size of the most recently allocated extent.
`
`If you wish to keep all extents the same size, you can
`Suggestion:
`prevent the SMON background process from coalescing extents by
`setting the value of PCTINCREASE to 0. In general, Oracle
`recommends a setting of O as a way to minimize fragmentation and
`avoid the possibility of very large temporary segments during
`processing.
`
`Restriction on PCTINCREASE You cannot specify PCTINCREASE for rollback
`segments. Rollback segments always have a PCTINCREASE value of 0.
`
`MIN EXTENTS
`Specify the total number of extents to allocate when the object is created. This
`parameter lets you allocate a large amount of space when you create an object, even
`if the space available is not contiguous. The default and minimum value is 1,
`meaning that Oracle allocates only the initial extent, except for rollback segments,
`
`8-62 SQL Reference
`
`Cloudera Exhibit 1020 - Page 594 of 1808
`
`Databricks R2 PA 00002730
`-
`-
`-
`
`

`

`Case 4:23-cv-01147-ALM Document 62-5 Filed 11/12/24 Page 16 of 543 PageID #:
`3307
`
`storage_clause
`
`for which the default and minimum value is 2. The maximum value depends on
`your operating system.
`
`If the MINEXTENTS value is greater than 1, then Oracle calculates the size of
`subsequent extents based on the values of the INITIAL, NEXT, and PCT INCREASE
`storage parameters.
`
`When changing the value of MINEXTENTS (that is, in an ALTER statement), you can
`reduce the value from its current value, but you cannot increase it. Resetting
`MINEXTENTS to a smaller value might be useful, for example, before a TRUNCATE ...
`DROP STORAGE statement, if you want to ensure that the segment will maintain a
`minimum number of extents after the TRUNCATE operation.
`
`Restriction on MIN EXTENTS You cannot change the value of MINEXTENTS for an
`object that resides in a locally managed tablespace.
`
`MAXEXTENTS
`Specify the total number of extents, including the first, that Oracle can allocate for
`the object. The minimum value is 1 except for rollback segments, which always
`have a minimum of 2. The default value depends on your data block size.
`
`Restriction on MAX.EXTENTS You cannot change the value of MAXEXTENTS for an
`object that resides in a locally managed tablespace.
`
`UNLIMITED Specify UNLIMITED if you want extents to be allocated automatically
`as needed. Oracle recommends this setting as a way to minimize fragmentation.
`
`Do not use this clause for rollback segments. Doing so allows the possibility that
`long-running rogue DML transactions will continue to create new extents until a
`disk is full.
`
`Caution: A rollback segment that you create without specifying
`the storage_clause has the same storage parameters as the
`tablespace in which the rollback segment is created. Thus, if you
`create a tablespace with MAXEXTENTS UNLIMITED, then the
`rollback segment will have this same default.
`
`FREELIST GROUPS
`Specify the number of groups of free lists for the database object you are creating.
`The default and minimum value for this parameter is 1. Oracle uses the instance
`
`Common SQL DDL Clauses 8-63
`
`Cloudera Exhibit 1020 - Page 595 of 1808
`
`Databricks R2 PA 00002731
`-
`-
`-
`
`

`

`Case 4:23-cv-01147-ALM Document 62-5 Filed 11/12/24 Page 17 of 543 PageID #:
`3308
`
`storage_clause
`
`number of Real Application Clusters instances to map each instance to one free list
`group.
`
`Each free list group uses one database block. Therefore:
`
`■
`
`■
`
`If you do not specify a large enough value for INITIAL to cover the minimum
`value plus one data block for each free list group, then Oracle increases the
`value of INITIAL the necessary amount.
`
`If you are creating an object in a uniform locally managed tablespace, and the
`extent size is not large enough to accommodate the number of freelist groups,
`then the create operation will fail.
`
`Oracle ignores a setting of FREEL I ST GROUPS if the tablespace in which the
`object resides is in automatic segment-space management mode. If you are
`running your database in this mode, please refer to the FREEPOOLS parameter
`of the LOB_storage_clause on page 16-41.
`
`Restriction on FREELIST GROUPS You can specify the FREEL I ST GROUPS
`parameter only in CREATE TABLE, CREATE CLUSTER, CREATE MATERIALIZED
`VIEW, CREATE MATERIALIZED VIEW LOG, and CREATE INDEX statements.
`
`See Also: Real Application Clusters Administration for information
`on associating instances with free list groups
`
`FREELISTS
`For objects other than tablespaces and rollback segments, specify the number of free
`lists for each of the free list groups for the table, partition, cluster, or index. The
`default and minimum value for this parameter is 1, meaning that each free list
`group contains one free list. The maximum value of this parameter depends on the
`data block size. If you specify a FREELISTS value that is too large, then Oracle
`returns an error indicating the maximum value.
`
`Oracle ignores a setting of FREELISTS if the tablespace in which the object resides
`is in automatic segment-space management mode. If you are running your database
`in this mode, please refer to the FREE POOLS parameter of the LOB_storage_clause on
`page 16-41.
`
`Restriction on FREELISTS You can specify FREELISTS in the storage_clause
`of any statement except when creating or altering a tablespace or rollback segment.
`
`8-64 SQL Reference
`
`Cloudera Exhibit 1020 - Page 596 of 1808
`
`Databricks R2 PA 00002732
`-
`-
`-
`
`

`

`Case 4:23-cv-01147-ALM Document 62-5 Filed 11/12/24 Page 18 of 543 PageID #:
`3309
`
`storage_clause
`
`BUFFER_POOL
`The BUFFER_ POOL clause lets you specify a default buffer pool or cache for a
`schema object. All blocks for the object are stored in the specified cache.
`
`■
`
`If you define a buffer pool for a partitioned table or index, then the partitions
`inherit the buffer pool from the table or index definition unless overridden by a
`partition-level definition.
`
`■ For an index-organized table, you can specify a buffer pool separately for the
`index segment and the overflow segment.
`
`Restrictions on the BUFFER_POOL Parameter
`■ You cannot specify this clause for a cluster table. However, you can specify it for
`a cluster.
`
`■ You cannot specify this clause for a tablespace or a rollback segment.
`
`KEEP Specify KEEP to put blocks from the segment into the KEEP buffer pool.
`Maintaining an appropriately sized KEEP buffer pool lets Oracle retain the schema
`object in memory to avoid 1/0 operations. KEEP takes precedence over any
`NOCACHE clause you specify for a table, cluster, materialized view, or materialized
`view log.
`
`RECYCLE Specify RECYCLE to put blocks from the segment into the RECYCLE
`pool. An appropriately sized RECYCLE pool reduces the number of objects whose
`default pool is the RECYCLE pool from taking up unnecessary cache space.
`
`DEFAULT Specify DEFAULT to indicate the default buffer pool. This is the default
`for objects not assigned to KEEP or RECYCLE.
`
`See Also: Oracle Database Performance Tuning Guide for more
`information about using multiple buffer pools
`
`OPTIMAL
`The OPTIMAL keyword is relevant only to rollback segments. It specifies an optimal
`size in bytes for a rollback segment. Use K or M to specify this size in kilobytes or
`megabytes. Oracle tries to maintain this size for the rollback segment by
`dynamically deallocating extents when their data is no longer needed for active
`transactions. Oracle deallocates as many extents as possible without reducing the
`total size of the rollback segment below the OPTIMAL value.
`
`The value of OPTIMAL cannot be less than the space initially allocated by the
`MINEXTENTS, INITIAL, NEXT, and PCTINCREASE parameters. The maximum
`
`Common SQL DDL Clauses 8-65
`
`Cloudera Exhibit 1020 - Page 597 of 1808
`
`Databricks R2 PA 00002733
`-
`-
`-
`
`

`

`Case 4:23-cv-01147-ALM Document 62-5 Filed 11/12/24 Page 19 of 543 PageID #:
`3310
`
`storage_clause
`
`Example
`
`value depends on your operating system. Oracle rounds values up to the next
`multiple of the data block size.
`
`NULL Specify NULL for no optimal size for the rollback segment, meaning that
`Oracle never deallocates the extents of the rollback segment. This is the default
`behavior.
`
`Specifying Table Storage Attributes: Example The following statement creates a
`table and provides storage parameter values:
`
`CREATE TABLE divisions
`(d iv_no
`NUMBER(2),
`div name
`VARCHAR2(14),
`)
`location VARCHAR2(13)
`50K
`STORAGE
`INITIAL l00K NEXT
`MINEXTENTS 1 MAXEXTENTS 50 PCTINCREASE 5);
`
`Oracle allocates space for the table based on the STORAGE parameter values as
`follows:
`
`■ The MINEXTENTS value is 1, so Oracle allocates 1 extent for the table upon
`creation.
`
`■ The INITIAL value is 100K, so the size of the first extent is 100 kilobytes.
`
`■
`
`■
`
`If the table data grows to exceed the first extent, then Oracle allocates a second
`extent. The NEXT value is 50K, so the size of the second extent will be 50
`kilobytes.
`
`If the table data subsequently grows to exceed the first two extents, then Oracle
`allocates a third extent. The PCTINCREASE value is 5, so the calculated size of
`the third extent is 5% larger than the second extent, or 52.5 kilobytes. If the data
`block size is 2 kilobytes, then Oracle rounds this value to 52 kilobytes.
`
`If the table data continues to grow, then Oracle allocates more extents, each 5%
`larger than the previous one.
`
`■ The MAXEXTENTS value is 50, so Oracle can allocate as many as 50 extents for
`the table.
`
`8-66 SQL Reference
`
`Cloudera Exhibit 1020 - Page 598 of 1808
`
`Databricks R2 PA 00002734
`-
`-
`-
`
`

`

`Case 4:23-cv-01147-ALM Document 62-5 Filed 11/12/24 Page 20 of 543 PageID #:
`3311
`
`9
`SQL Queries and Subqueries
`
`This chapter describes SQL queries and subqueries.
`
`This chapter contains these sections:
`
`■
`
`■
`
`■
`
`■
`
`■
`
`■
`
`■
`
`■
`
`■
`
`■
`
`About Queries and Subqueries
`
`Creating Simple Queries
`
`Hierarchical Queries
`
`The UNION [ALL], INTERSECT, MINUS Operators
`
`Sorting Query Results
`
`Joins
`
`Using Subqueries
`
`Unnesting of Nested Subqueries
`
`Selecting from the DUAL Table
`
`Distributed Queries
`
`About Queries and Subqueries
`A query is an operation that retrieves data from one or more tables or views. In this
`reference, a top-level SELECT statement is called a query, and a query nested
`within another SQL statement is called a subquery.
`
`This section describes some types of queries and subqueries and how to use them.
`The top level of the syntax is shown in this chapter. Please refer to SELECT on
`page 19-4 for the full synt