6000 to 6050

Data Dictionary Status Codes

This section lists the status codes that pertain to the data dictionary files. These codes often relate to errors involving referential integrity.

6002: Invalid Column

The column name cannot be used. The name may contain invalid characters or the name may be a duplicate name. See Naming Conventions in the online Pervasive PSQL Programmer's Guide, which is part of the Pervasive PSQL Software Developer's Kit (SDK).

6003: Foreign Key Not Found

The column to which the foreign key is to be associated does not exist in the primary table.

6005: Column Not Nullable

This column cannot be made null. Certain data types, such as identity and small identity, cannot be null. Check the data type of the column. See Data Types in SQL Engine Reference for a list of the Pervasive PSQL data types.

6006: Invalid Data Type

The number for the data type is not within the valid ranges. The current range is 0 to 30. See Data Types in SQL Engine Reference for a list of the Pervasive PSQL data types.

6007: Invalid Index Number

The index number is less than zero. Negative numbers are not allowed as index numbers.

6008: Too Many Segments

The number of index segments is greater than the maximum allowed. Note that the maximum number of keys is 119 for all file versions. The number of key segments can vary but must be within the limits shown by the following table.

The number of index segments that you may use depends on the file's page size.


Page Size (bytes)	Maximum Key Segments by File Version
Page Size (bytes)	8.x and prior	9.0	9.5
512	8	8	rounded up2
1,024	23	23	97
1,536	24	24	rounded up2
2,048	54	54	97
2,560	54	54	rounded up2
3,072	54	54	rounded up2
3,584	54	54	rounded up2
4,096	119	119	119 or 2043
8,192	n/a1	119	119 or 4203
16,384	n/a1	n/a1	119 or 4203
1"n/a" stands for "not applicable" 2"rounded up" means that the page size is rounded up to the next size supported by the file version. For example, 512 is rounded up to 1,024, 2,560 is rounded up to 4,096, and so forth. 3The maximum number of index segments that can be used with the relational interface is 119. For the transactional interface, the maximum number is 204 for a page size of 4,096, and 420 for page sizes 8,192 and 16,384.

See status codes 26: The number of keys specified is invalid and 29: The key length is invalid for related information about index segments and the transactional interface.

See also Choosing a Page Size and Segmentation in the Pervasive PSQL Programmer's Guide, which is part of the Pervasive PSQL Software Developer's Kit (SDK).

6009: Index Name Duplicate

The index name is already being used a column. Use a unique index name. See Naming Conventions in the online Pervasive PSQL Programmer's Guide, which is part of the Pervasive PSQL Software Developer's Kit (SDK).