You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@trafodion.apache.org by db...@apache.org on 2018/01/04 19:23:28 UTC
[1/2] trafodion git commit: [TRAFODION-2865] Update Messages Guide
for some messages in range 1300-1430
Repository: trafodion
Updated Branches:
refs/heads/master ff6ce5af2 -> 9b53555e3
[TRAFODION-2865] Update Messages Guide for some messages in range 1300-1430
Project: http://git-wip-us.apache.org/repos/asf/trafodion/repo
Commit: http://git-wip-us.apache.org/repos/asf/trafodion/commit/ba0c83fc
Tree: http://git-wip-us.apache.org/repos/asf/trafodion/tree/ba0c83fc
Diff: http://git-wip-us.apache.org/repos/asf/trafodion/diff/ba0c83fc
Branch: refs/heads/master
Commit: ba0c83fc4471da7fa025c490bb52b237a043a2fc
Parents: 51935dc
Author: Dave Birdsall <db...@apache.org>
Authored: Wed Jan 3 20:09:43 2018 +0000
Committer: Dave Birdsall <db...@apache.org>
Committed: Wed Jan 3 20:09:43 2018 +0000
----------------------------------------------------------------------
core/sql/bin/SqlciErrors.txt | 136 ++--
core/sql/sqlcomp/CmpDDLCatErrorCodes.h | 121 ++--
.../src/asciidoc/_chapters/ddl_msgs.adoc | 701 +++++++++++++++++--
3 files changed, 752 insertions(+), 206 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/trafodion/blob/ba0c83fc/core/sql/bin/SqlciErrors.txt
----------------------------------------------------------------------
diff --git a/core/sql/bin/SqlciErrors.txt b/core/sql/bin/SqlciErrors.txt
index ffc6043..be528cd 100644
--- a/core/sql/bin/SqlciErrors.txt
+++ b/core/sql/bin/SqlciErrors.txt
@@ -295,37 +295,37 @@
1297 ZZZZZ 99999 BEGINNER MAJOR DBADMIN --- unused ---
1298 ZZZZZ 99999 BEGINNER MINOR DBADMIN Schema $0~SchemaName could not be altered. $0~String0
1299 ZZZZZ 99999 BEGINNER MAJOR DBADMIN You cannot specify some columns with just the name and others with name & data attributes.
-1300 ZZZZZ 99999 ADVANCED MAJOR DIALOUT Catman generated unknown Exception for procedure $0~TableName.
-1301 ZZZZZ 99999 BEGINNER MAJOR DBADMIN NO ACTION referential action for $0~string0 clause is not yet supported as specified by ANSI SQL99 standard. To alter the behavior, set an appropriate value for the REF_CONSTRAINT_NO_ACTION_LIKE_RESTRICT default.
-1302 01000 99999 BEGINNER MAJOR DBADMIN NO ACTION referential action for $0~string0 clause behaves like RESTRICT referential action. To alter the behavior, set the appropriate value for the REF_CONSTRAINT_NO_ACTION_LIKE_RESTRICT default.
-1303 ZZZZZ 99999 UUUUU UUUUUUUU UUUUU --- unused as of 5/7/12 ---
-1304 ZZZZZ 99999 BEGINNER CRTCL DIALOUT SQL could not obtain the location of the system schema tables.
-1305 ZZZZZ 99999 BEGINNER MAJOR DBADMIN The specified schema location $0~string0 is already in use by schema $1~SchemaName.
-1306 ZZZZZ 99999 ADVANCED MAJOR DIALOUT SQL was not able to generate a unique schema location for schema $0~SchemaName.
-1307 ZZZZZ 99999 BEGINNER MAJOR DBADMIN The schema location $0~string0 is reserved for SQL metadata.
-1308 ZZZZZ 99999 UUUUUUUU UUUUU UUUUUUU ----- Msg not currently used -----
-1309 ZZZZZ 99999 BEGINNER MAJOR DBADMIN Object type for $0~string0 is not valid for the current operation.
-1310 ZZZZZ 99999 BEGINNER MAJOR DBADMIN The CREATE SCHEMA statement does not support the creation of triggers.
-1311 ZZZZZ 99999 BEGINNER MAJOR DBADMIN Unable to $0~string0 constraint $1~ConstraintName due to the above errors.
-1312 ZZZZZ 99999 BEGINNER MAJOR DBADMIN Unable to $0~string0 $1~TableName due to the above errors.
+1300 ZZZZZ 99999 ADVANCED MAJOR DIALOUT --- unused ---
+1301 ZZZZZ 99999 BEGINNER MAJOR DBADMIN --- unused ---
+1302 01000 99999 BEGINNER MAJOR DBADMIN --- unused ---
+1303 ZZZZZ 99999 UUUUUUUU UUUUU UUUUUUU --- unused ---
+1304 ZZZZZ 99999 BEGINNER CRTCL DIALOUT --- unused ---
+1305 ZZZZZ 99999 BEGINNER MAJOR DBADMIN --- unused ---
+1306 ZZZZZ 99999 ADVANCED MAJOR DIALOUT --- unused ---
+1307 ZZZZZ 99999 BEGINNER MAJOR DBADMIN --- unused ---
+1308 ZZZZZ 99999 UUUUUUUU UUUUU UUUUUUU --- unused ---
+1309 ZZZZZ 99999 BEGINNER MAJOR DBADMIN --- unused ---
+1310 ZZZZZ 99999 BEGINNER MAJOR DBADMIN --- unused ---
+1311 ZZZZZ 99999 BEGINNER MAJOR DBADMIN --- unused ---
+1312 ZZZZZ 99999 BEGINNER MAJOR DBADMIN --- unused ---
1313 ZZZZZ 99999 BEGINNER MAJOR DBADMIN The referential integrity constraint $0~string0 has been created with the NOT ENFORCED attribute and will not be enforced during INSERT, UPDATE, OR DELETE statements.
-1314 ZZZZZ 99999 BEGINNER MAJOR DBADMIN The create privilege has been turned off for catalog $0~CatalogName. The $1~string0 cannot be performed for $2~TableName.
-1315 ZZZZZ 99999 BEGINNER MAJOR DBADMIN Catalog $0~CatalogName does not have an associated definition schema. The ALTER operation fails.
-1316 ZZZZZ 99999 ADVANCED MAJOR DBADMIN Specified synonym $0~TableName does not reference a system view for object $1~String0.
-1317 ZZZZZ 99999 ADVANCED MAJOR DBADMIN No DBA role has been identified.
-1318 ZZZZZ 99999 ADVANCED MAJOR DBADMIN Synonym name $0~TableName which contains $1~int0 bytes is too long. Synonym name must be less than $2~int1 bytes.
-1319 ZZZZZ 99999 ADVANCED MAJOR DBADMIN Mismatch of privileges specified for PUBLISH or UNPUBLISH on object $0~TableName. Select column level privileges cannot be specified with table level privileges.
-1320 ZZZZZ 99999 ADVANCED MAJOR DBADMIN Mismatch of privileges specified for PUBLISH or UNPUBLISH on object $0~TableName. Select column level privileges cannot be specified with either update or references column level privileges.
-1321 ZZZZZ 99999 ADVANCED MAJOR DBADMIN The public schema has not been specified. Cannot PUBLISH or UNPUBLISH the requested privileges for object $0~TableName.
-1322 ZZZZZ 99999 ADVANCED MAJOR DBADMIN The synonym $0~String0 is referencing view $1~String1 which is not related to object $2~String2. The referenced view is related to $3~String3.
+1314 ZZZZZ 99999 BEGINNER MAJOR DBADMIN --- unused ---
+1315 ZZZZZ 99999 BEGINNER MAJOR DBADMIN --- unused ---
+1316 ZZZZZ 99999 ADVANCED MAJOR DBADMIN --- unused ---
+1317 ZZZZZ 99999 ADVANCED MAJOR DBADMIN --- unused ---
+1318 ZZZZZ 99999 ADVANCED MAJOR DBADMIN --- unused ---
+1319 ZZZZZ 99999 ADVANCED MAJOR DBADMIN --- unused ---
+1320 ZZZZZ 99999 ADVANCED MAJOR DBADMIN --- unused ---
+1321 ZZZZZ 99999 ADVANCED MAJOR DBADMIN --- unused ---
+1322 ZZZZZ 99999 ADVANCED MAJOR DBADMIN --- unused ---
1323 ZZZZZ 99999 ADVANCED MAJOR DBADMIN Unable to grant privileges while creating $0~Tablename.
-1324 ZZZZZ 99999 ADVANCED MAJOR DBADMIN You are not allowed to exercise trigger $0~String0.
-1325 ZZZZZ 99999 ADVANCED MAJOR DBADMIN The WITH GRANT OPTION privilege has been disabled. You are not allowed to perform the request.
-1326 42000 99999 BEGINNER MAJOR DBADMIN This operation is not supported on inMemory objects.
-1327 42000 99999 BEGINNER MAJOR DBADMIN An inMemory DDL statement cannot be used on regular objects.
+1324 ZZZZZ 99999 ADVANCED MAJOR DBADMIN --- unused ---
+1325 ZZZZZ 99999 ADVANCED MAJOR DBADMIN --- unused ---
+1326 42000 99999 BEGINNER MAJOR DBADMIN --- unused ---
+1327 42000 99999 BEGINNER MAJOR DBADMIN --- unused ---
1328 ZZZZZ 99999 BEGINNER MINOR DBADMIN The $0~String0 privilege(s) cannot be specified for $1~String1 $2~TableName.
-1329 ZZZZZ 99999 ADVANCED MAJOR LOGONLY Cannot create metadata views because of server failure.
-1330 ZZZZZ 99999 BEGINNER MINOR DBADMIN Cannot revoke role $0~String0 from authorization ID $1~String1. Role has been granted to another authorization ID.
+1329 ZZZZZ 99999 ADVANCED MAJOR LOGONLY --- unused ---
+1330 ZZZZZ 99999 BEGINNER MINOR DBADMIN Cannot revoke role $0~String0 from authorization ID $1~String1. Role has been granted to another authorization ID.
1331 ZZZZZ 99999 BEGINNER MINOR DBADMIN User $0~String0 does not exist in the directory service.
1332 ZZZZZ 99999 BEGINNER MAJOR DBADMIN Error while communicating with the directory service.
1333 ZZZZZ 99999 BEGINNER MINOR DBADMIN User $0~String0 does not exist.
@@ -336,53 +336,53 @@
1338 ZZZZZ 99999 ADVANCED MAJOR DBADMIN Role $0~string0 is not defined in the database.
1339 ZZZZZ 99999 BEGINNER MINOR DBADMIN $0~string0 is not a grantable role.
1340 ZZZZZ 99999 BEGINNER MINOR DBADMIN $0~string0 is not a user.
-1341 ZZZZZ 99999 BEGINNER MINOR DBADMIN Cannot unregister user. User owns one or more catalogs.
-1342 ZZZZZ 99999 BEGINNER MINOR DBADMIN Cannot unregister user. User owns one or more schemas.
-1343 ZZZZZ 99999 BEGINNER MINOR DBADMIN Cannot unregister user. User owns one or more objects.
-1344 ZZZZZ 99999 BEGINNER MINOR DBADMIN Cannot unregister user. User is the grantee of one or more schema privileges.
-1345 ZZZZZ 99999 BEGINNER MINOR DBADMIN Cannot unregister user. User is the grantee of one or more table privileges.
-1346 ZZZZZ 99999 BEGINNER MINOR DBADMIN Cannot unregister user. User is the grantee of one or more column privileges.
-1347 ZZZZZ 99999 BEGINNER MINOR DBADMIN Cannot unregister user. User owns one or more roles.
-1348 ZZZZZ 99999 BEGINNER MINOR DBADMIN Cannot drop role. Role is granted to one or more users.
-1349 ZZZZZ 99999 BEGINNER MINOR DBADMIN Cannot unregister user. User granted one or more roles.
-1350 ZZZZZ 99999 BEGINNER MINOR DBADMIN Role $0~String0 is not granted to $1~String1.
+1341 ZZZZZ 99999 BEGINNER MINOR DBADMIN --- unused ---
+1342 ZZZZZ 99999 BEGINNER MINOR DBADMIN --- unused ---
+1343 ZZZZZ 99999 BEGINNER MINOR DBADMIN Cannot unregister user. User owns one or more objects.
+1344 ZZZZZ 99999 BEGINNER MINOR DBADMIN --- unused ---
+1345 ZZZZZ 99999 BEGINNER MINOR DBADMIN --- unused ---
+1346 ZZZZZ 99999 BEGINNER MINOR DBADMIN --- unused ---
+1347 ZZZZZ 99999 BEGINNER MINOR DBADMIN Cannot unregister user. User owns one or more roles.
+1348 ZZZZZ 99999 BEGINNER MINOR DBADMIN Cannot drop role. Role is granted to one or more users.
+1349 ZZZZZ 99999 BEGINNER MINOR DBADMIN Cannot unregister user. User granted one or more roles.
+1350 ZZZZZ 99999 BEGINNER MINOR DBADMIN --- unused ---
1351 ZZZZZ 99999 BEGINNER MINOR DBADMIN Role $1~String0 appears multiple times in list.
1352 ZZZZZ 99999 BEGINNER MINOR DBADMIN User $1~String0 appears multiple times in list.
-1353 ZZZZZ 99999 BEGINNER MINOR DBADMIN WITH GRANT OPTION is not allowed for roles.
-1354 ZZZZZ 99999 BEGINNER MINOR DBADMIN Granting schema privileges to roles is not allowed.
+1353 ZZZZZ 99999 BEGINNER MINOR DBADMIN --- unused ---
+1354 ZZZZZ 99999 BEGINNER MINOR DBADMIN --- unused ---
1355 ZZZZZ 99999 BEGINNER MINOR DBADMIN Granting a role to PUBLIC or _SYSTEM is not allowed.
1356 ZZZZZ 99999 BEGINNER MINOR DBADMIN Cannot create the component privilege specified. Component privilege code $0~String0 for the component already exists.
1357 ZZZZZ 99999 BEGINNER MINOR DBADMIN Cannot create the component privilege specified. Component privilege name $0~String0 for the component already exists.
-1358 ZZZZZ 99999 BEGINNER MINOR DBADMIN Component privilege $0~String0 not found.
+1358 ZZZZZ 99999 BEGINNER MINOR DBADMIN --- unused ---
1359 ZZZZZ 99999 BEGINNER MINOR DBADMIN Specified invalid privilege $0~String0 for GRANT/REVOKE.
-1360 ZZZZZ 99999 BEGINNER MINOR DBADMIN Cannot $0~String0. Dependent component privileges exist for the user/role.
+1360 ZZZZZ 99999 BEGINNER MINOR DBADMIN --- unused ---
1361 ZZZZZ 99999 BEGINNER MAJOR DBADMIN Library $0~TableName does not exist.
-1362 ZZZZZ 99999 BEGINNER MAJOR DBADMIN $0~string0 is not a library.
-1363 ZZZZZ 99999 BEGINNER MINOR DBADMIN Library $0~TableName already exists.
+1362 ZZZZZ 99999 BEGINNER MAJOR DBADMIN --- unused ---
+1363 ZZZZZ 99999 BEGINNER MINOR DBADMIN --- unused ---
1364 ZZZZZ 99999 BEGINNER MINOR DBADMIN Cannot revoke role $0~String0. Object $1~String1 depends on privileges on object $2~String2.
-1365 ZZZZZ 99999 BEGINNER MINOR DBADMIN Unable to obtain necessary lock for user/role number $0~Int0.
-1366 ZZZZZ 99999 BEGINNER MINOR DBADMIN Request failed. One or more dependent procedures exist.
-1367 ZZZZZ 99999 BEGINNER MINOR DBADMIN Procedure uses a library object, EXTERNAL PATH cannot be altered.
-1368 ZZZZZ 99999 BEGINNER MINOR DBADMIN The library must be defined in the same catalog.
-1369 ZZZZZ 99999 BEGINNER MINOR DBADMIN Only UPDATE and USAGE privileges are supported for a library.
+1365 ZZZZZ 99999 BEGINNER MINOR DBADMIN --- unused ---
+1366 ZZZZZ 99999 BEGINNER MINOR DBADMIN Request failed. One or more dependent procedures exist.
+1367 ZZZZZ 99999 BEGINNER MINOR DBADMIN --- unused ---
+1368 ZZZZZ 99999 BEGINNER MINOR DBADMIN --- unused ---
+1369 ZZZZZ 99999 BEGINNER MINOR DBADMIN --- unused ---
1370 ZZZZZ 99999 BEGINNER MINOR DBADMIN The authorization name "$0~String0" contains one or more invalid characters. A valid name can only contain these characters: [a-zA-Z_0-9-@./]
-1371 ZZZZZ 99999 BEGINNER MINOR DBADMIN Only INSERT and SELECT privileges are supported for table $0~String0.
-1372 ZZZZZ 99999 BEGINNER MINOR DBADMIN Unable to alter table $0~String0 because of dependent object $1~String1 with object type $0~String3.
-1373 ZZZZZ 99999 BEGINNER MINOR DBADMIN AUDITLOG: Value for column $0~int0 ($1~String0) must be either Y or N.
-1374 ZZZZZ 99999 BEGINNER MINOR DBADMIN AUDITLOG: $0~String0 is an unrecognized or unsupported audit log type.
-1375 ZZZZZ 99999 BEGINNER MINOR DBADMIN AUDITLOG: Input strings limited to $0~Int0 characters each.
-1376 ZZZZZ 99999 BEGINNER MINOR DBADMIN AUDITLOG: Column numbers must be in the range 1 - $0~Int0.
-1377 ZZZZZ 99999 BEGINNER MINOR DBADMIN AUDITLOG: Audit configuration alter failed due to SQL error $0~Int0.
-1378 ZZZZZ 99999 BEGINNER MINOR DBADMIN AUDITLOG: Audit refresh time must be 0 to $0~Int0 seconds.
-1379 ZZZZZ 99999 BEGINNER MINOR DBADMIN AUDITLOG: Audit aging days must be 0 to $0~Int0.
-1380 ZZZZZ 99999 BEGINNER MINOR DBADMIN AUDITLOG: Audit threshold must be a percentage from 0 to 100.
-1381 ZZZZZ 99999 BEGINNER MINOR DBADMIN AUDITLOG: Column/value pair mismatch.
+1371 ZZZZZ 99999 BEGINNER MINOR DBADMIN --- unused ---
+1372 ZZZZZ 99999 BEGINNER MINOR DBADMIN --- unused ---
+1373 ZZZZZ 99999 BEGINNER MINOR DBADMIN --- unused ---
+1374 ZZZZZ 99999 BEGINNER MINOR DBADMIN --- unused ---
+1375 ZZZZZ 99999 BEGINNER MINOR DBADMIN --- unused ---
+1376 ZZZZZ 99999 BEGINNER MINOR DBADMIN --- unused ---
+1377 ZZZZZ 99999 BEGINNER MINOR DBADMIN --- unused ---
+1378 ZZZZZ 99999 BEGINNER MINOR DBADMIN --- unused ---
+1379 ZZZZZ 99999 BEGINNER MINOR DBADMIN --- unused ---
+1380 ZZZZZ 99999 BEGINNER MINOR DBADMIN --- unused ---
+1381 ZZZZZ 99999 BEGINNER MINOR DBADMIN --- unused ---
1382 ZZZZZ 99999 BEGINNER MINOR DBADMIN JAR or DLL file $0~String0 not found.
-1383 ZZZZZ 99999 BEGINNER MAJOR DBADMIN User management operations have been disabled. $0~string0 cannot be performed for $1~TableName.
-1384 ZZZZZ 99999 BEGINNER MINOR DBADMIN Unable to perform 1-to-1 mapping of $0~int0 partitions to $1~int1 disks for $2~TableName. Since there are more partitions than available disks, $3~int2 partitions have been created on each disk.
-1385 ZZZZZ 99999 BEGINNER MAJOR DBADMIN Mapping of disk pools for $0~TableName during CREATE failed. The number of partitions is $1~int0, the expected number of disks is $2~int1 and the actual number of disks is $3~int2.
-1386 ZZZZZ 99999 BEGINNER MINOR DBADMIN The call to run_script failed. $0~string0.
-1387 ZZZZZ 99999 BEGINNER MINOR DBADMIN Use of blob datatype in a PRIMARY KEY is not allowed.
+1383 ZZZZZ 99999 BEGINNER MAJOR DBADMIN --- unused ---
+1384 ZZZZZ 99999 BEGINNER MINOR DBADMIN --- unused ---
+1385 ZZZZZ 99999 BEGINNER MAJOR DBADMIN --- unused ---
+1386 ZZZZZ 99999 BEGINNER MINOR DBADMIN --- unused ---
+1387 ZZZZZ 99999 BEGINNER MINOR DBADMIN --- unused ---
1388 ZZZZZ 99999 BEGINNER MINOR DBADMIN Object $0~TableName does not exist in hive metadata.
1389 ZZZZZ 99999 BEGINNER MINOR DBADMIN Object $0~String0 does not exist in Trafodion.
1390 ZZZZZ 99999 BEGINNER MINOR DBADMIN Object $0~String0 already exists in Trafodion.
@@ -392,10 +392,10 @@
1394 ZZZZZ 99999 BEGINNER MINOR DBADMIN Trafodion needs to be reinitialized on this system due to missing or corrupted metadata objects. Do 'initialize trafodion, drop' followed by 'initialize trafodion' to reinitialize Trafodion. This will delete all metadata and user objects from the Trafodion database and recreate metadata.
1395 ZZZZZ 99999 BEGINNER MINOR DBADMIN Trafodion needs to be upgraded on this system due to metadata version mismatch. Do 'initialize trafodion, upgrade' to upgrade metadata. Or do 'initialize trafodion, drop' followed by 'initialize trafodion'. Be aware that the second option will delete all metadata and user objects from Trafodion database.
1396 ZZZZZ 99999 BEGINNER MINOR DBADMIN Trafodion needs to be reinitialized on this system due to data format version mismatch.
-1397 ZZZZZ 99999 BEGINNER MINOR DBADMIN Software version of objects being used is different than the version of software running on the system. Make sure that objects being used are built with the same version as that running on the system. Version of Trafodion software is picked from file sqenvcom.sh.
-1398 ZZZZZ 99999 BEGINNER MINOR DBADMIN Error $0~Int0 occured while accessing the hbase subsystem. Fix that error and make sure hbase is up and running. Error Details: $0~String0.
+1397 ZZZZZ 99999 BEGINNER MINOR DBADMIN Software version of objects being used is different than the version of software running on the system. Make sure that objects being used are built with the same version as that running on the system. Version of Trafodion software is determined by file sqenvcom.sh.
+1398 ZZZZZ 99999 BEGINNER MINOR DBADMIN Error $0~Int0 occured while accessing the HBase subsystem. Fix that error and make sure HBase is up and running. Error Details: $0~String0.
1399 ZZZZZ 99999 BEGINNER MINOR DBADMIN Metadata has already been upgraded. No action is needed.
-1400 ZZZZZ 99999 BEGINNER MINOR LOGONLY The default value of column $0~ColumnName contains characters that cannot be converted to $1~String0.
+1400 ZZZZZ 99999 BEGINNER MINOR LOGONLY --- unused ---
1401 ZZZZZ 99999 BEGINNER MINOR DBADMIN The default value of column $0~ColumnName contains characters that cannot be converted to character set $1~String0.
1402 ZZZZZ 99999 BEGINNER MINOR DBADMIN Unique index $0~TableName could not be created with the DIVISION LIKE TABLE option. Only non-unique indexes are supported with this option.
1403 ZZZZZ 99999 BEGINNER MINOR DBADMIN This ALTER command is not allowed on a reserved system schema object.
http://git-wip-us.apache.org/repos/asf/trafodion/blob/ba0c83fc/core/sql/sqlcomp/CmpDDLCatErrorCodes.h
----------------------------------------------------------------------
diff --git a/core/sql/sqlcomp/CmpDDLCatErrorCodes.h b/core/sql/sqlcomp/CmpDDLCatErrorCodes.h
index a8e9033..dd6b241 100644
--- a/core/sql/sqlcomp/CmpDDLCatErrorCodes.h
+++ b/core/sql/sqlcomp/CmpDDLCatErrorCodes.h
@@ -284,43 +284,36 @@ enum CatErrorCode { CAT_FIRST_ERROR = 1000
// unused = 1297
, CAT_UNABLE_TO_ALTER_SCHEMA = 1298
- // Restrict and No Action referential action Messages.
- , CAT_REF_CONSTRAINT_NO_ACTION_NOT_SUPPORTED = 1301
- , CAT_REF_CONSTRAINT_NO_ACTION_LIKE_RESTRICT = 1302
-
- // Anchor file access error
- , CAT_ANCHOR_FILE_ERROR = 1304
-
- // Schema subvol error/warnings
- , CAT_DUP_SCHEMA_SUBVOL_SPECIFIED = 1305
- , CAT_DUP_SCHEMA_SUBVOL_GENERATED = 1306
- , CAT_METADATA_SCHEMA_SUBVOL = 1307
- , CAT_INVALID_OBJECT_TYPE = 1309
- , CAT_TRIGGER_UNSUPPORTED_IN_COMPOUNDCREATE = 1310
-
- , CAT_UNABLE_TO_XXX_CONSTRAINT_DUE_TO_ERRORS = 1311
- , CAT_UNABLE_TO_XXX_DUE_TO_ERRORS = 1312
+ // unused = 1301
+ // unused = 1302
+
+ // unused = 1304
+ // unused = 1305
+ // unused = 1306
+ // unused = 1307
+ // unused = 1309
+ // unused = 1310
+
+ // unused = 1311
+ // unused = 1312
, CAT_NOT_ENFORCED_RI_CONSTRAINT_WARNING = 1313
- // Alter catalog, disable creates
- , CAT_CREATE_OPERATION_DISABLED = 1314
- , CAT_NO_DEFINITION_SCHEMA = 1315
-
- // Publish/unpublish errors
- , CAT_PUBLISH_NOT_SYSTEM_VIEW = 1316
- , CAT_PUBLISH_NO_DBA_USER_DEFINED = 1317
- , CAT_PUBLISH_SYNONYM_NAME_TOO_LONG = 1318
- , CAT_PUBLISH_MISMATCH_COLUMN_TABLE_PRIVS = 1319
- , CAT_PUBLISH_MISMATCH_COLUMN_COLUMN_PRIVS = 1320
- , CAT_PUBLISH_NO_PUBLIC_SCHEMA = 1321
- , CAT_PUBLISH_VIEW_NOT_REFERENCING_OBJECT = 1322
+ // unused = 1314
+ // unused = 1315
+ // unused = 1316
+ // unused = 1317
+ // unused = 1318
+ // unused = 1319
+ // unused = 1320
+ // unused = 1321
+ // unused = 1322
, CAT_UNABLE_TO_GRANT_PRIVILEGES = 1323
- , CAT_NO_SCHEMA_WGO_ALLOWED = 1325
-
- , CAT_REGULAR_OPERATION_ON_INMEMORY_OBJECT = 1326
- , CAT_INMEMORY_OPERATION_ON_REGULAR_OBJECT = 1327
+ // unused = 1324
+ // unused = 1325
+ // unused = 1326
+ // unused = 1327
, CAT_INVALID_PRIV_FOR_OBJECT = 1328
- , CAT_UNABLE_TO_CREATE_METADATA_VIEWS = 1329
+ // unused = 1329
, CAT_ROLE_IS_GRANTED_NO_REVOKE = 1330
, CAT_LDAP_USER_NOT_FOUND = 1331
, CAT_LDAP_COMM_ERROR = 1332
@@ -332,55 +325,55 @@ enum CatErrorCode { CAT_FIRST_ERROR = 1000
, CAT_ROLE_NOT_EXIST = 1338
, CAT_IS_NOT_A_ROLE = 1339
, CAT_IS_NOT_A_USER = 1340
- , CAT_NO_UNREG_USER_OWNS_CATALOG = 1341
- , CAT_NO_UNREG_USER_OWNS_SCHEMA = 1342
+ // unused = 1341
+ // unused = 1342
, CAT_NO_UNREG_USER_OWNS_OBJECT = 1343
- , CAT_NO_UNREG_USER_HAS_SCHEMA_PRIVS = 1344
- , CAT_NO_UNREG_USER_HAS_TABLE_PRIVS = 1345
- , CAT_NO_UNREG_USER_HAS_COLUMN_PRIVS = 1346
+ // unused = 1344
+ // unused = 1345
+ // unused = 1346
, CAT_NO_UNREG_USER_OWNS_ROLES = 1347
, CAT_ROLE_IS_GRANTED_NO_DROP = 1348
, CAT_NO_UNREG_USER_GRANTED_ROLES = 1349
- , CAT_ROLE_NOT_GRANTED_TO_USER = 1350
+ // unused = 1350
, CAT_DUPLICATE_ROLES_IN_LIST = 1351
, CAT_DUPLICATE_USERS_IN_LIST = 1352
- , CAT_NO_ROLE_WGO_ALLOWED = 1353
- , CAT_NO_ROLE_SCHEMA_GRANT_ALLOWED = 1354
+ // unused = 1353
+ // unused = 1354
, CAT_NO_GRANT_ROLE_TO_PUBLIC_OR_SYSTEM = 1355
, CAT_COMPONENT_PRIVILEGE_CODE_EXISTS = 1356
, CAT_COMPONENT_PRIVILEGE_NAME_EXISTS = 1357
- , CAT_COMPONENT_PRIVILEGE_NOT_FOUND = 1358
+ // unused = 1358
, CAT_INVALID_PRIVILEGE_FOR_GRANT_OR_REVOKE = 1359
- , CAT_DEPENDENT_COMPONENT_PRIVILEGES_EXIST = 1360
+ // unused = 1360
, CAT_LIBRARY_DOES_NOT_EXIST = 1361
- , CAT_NOT_A_LIBRARY = 1362
- , CAT_LIBRARY_EXISTS = 1363
+ // unused = 1362
+ // unused = 1363
, CAT_DEPENDENT_ROLE_PRIVILEGES_EXIST = 1364
- , CAT_COULDNT_LOCK_PARTICIPATING_AUTH_ID = 1365
+ // unused = 1365
, CAT_DEPENDENT_ROUTINES_EXIST = 1366
- , CAT_ROUTINE_USES_LIBRARY = 1367
- , CAT_LIBRARY_MUST_BE_IN_SAME_CATALOG = 1368
- , CAT_ONLY_UPDATE_OR_USAGE_PRIV_FOR_LIBRARY = 1369
+ // unused = 1367
+ // unused = 1368
+ // unused = 1369
, CAT_INVALID_CHARS_IN_AUTH_NAME = 1370
- , CAT_ONLY_SELECT_OR_INSERT_FOR_TABLE = 1371
- , CAT_ALTER_TABLE_INSERT_ONLY_FAILED = 1372
- , CAT_AUDIT_NOT_A_VALID_BOOL_VALUE = 1373
- , CAT_AUDIT_NOT_A_VALID_LOG_TYPE = 1374
- , CAT_AUDIT_INPUT_TOO_LARGE = 1375
- , CAT_AUDIT_INVALID_COLUMN_NUMBER = 1376
- , CAT_AUDIT_ALTER_CONFIG_FAILED = 1377
- , CAT_AUDIT_REFRESH_RANGE = 1378
- , CAT_AUDIT_AGING_RANGE = 1379
- , CAT_AUDIT_THRESHOLD_RANGE = 1380
- , CAT_AUDIT_COLUMN_VALUE_COUNT_MISMATCH = 1381
+ // unused = 1371
+ // unused = 1372
+ // unused = 1373
+ // unused = 1374
+ // unused = 1375
+ // unused = 1376
+ // unused = 1377
+ // unused = 1378
+ // unused = 1379
+ // unused = 1380
+ // unused = 1381
, CAT_JAR_NOT_FOUND = 1382
- , CAT_DISABLE_AUTHNAME_CHANGES = 1383
- , CAT_POS_UNEQUABLE_DISK_POOL_DEFINED = 1384
- , CAT_POS_DISK_POOL_MAPPING_FAILED = 1385
+ // unused = 1383
+ // unused = 1384
+ // unused = 1385
, CAT_OBJECT_DOES_NOT_EXIST_IN_TRAFODION = 1389
, CAT_TRAFODION_OBJECT_EXISTS = 1390
- , CAT_SHOWDDL_UNABLE_TO_CONVERT_COLUMN_DEFAULT_VALUE = 1400
+ // unused = 1400
, CAT_UNABLE_TO_CONVERT_COLUMN_DEFAULT_VALUE_TO_CHARSET = 1401
, CAT_UNIQUE_INDEX_COLS_NOT_IN_DIV_EXPRS = 1402
, CAT_ALTER_NOT_ALLOWED_IN_SMD = 1403
http://git-wip-us.apache.org/repos/asf/trafodion/blob/ba0c83fc/docs/messages_guide/src/asciidoc/_chapters/ddl_msgs.adoc
----------------------------------------------------------------------
diff --git a/docs/messages_guide/src/asciidoc/_chapters/ddl_msgs.adoc b/docs/messages_guide/src/asciidoc/_chapters/ddl_msgs.adoc
index 03ee310..0a44ba2 100644
--- a/docs/messages_guide/src/asciidoc/_chapters/ddl_msgs.adoc
+++ b/docs/messages_guide/src/asciidoc/_chapters/ddl_msgs.adoc
@@ -2433,134 +2433,647 @@ invalid state. The <reason> gives more details concerning this invalid state.
use CLEANUP on certain objects in the schema, then resubmit the ALTER SCHEMA statement.
<<<
-[[SQL-1301]]
-== SQL 1301
+[[SQL-1313]]
+== SQL 1313
```
-NO ACTION referential action for <referential-triggered-action> clause is not yet supported as specified by ANSI SQL-99 standard. To alter the behavior, set an appropriate value for the REF_CONSTRAINT_NO_ACTION_LIKE_RESTRICT default.
+The referential integrity constraint <constraint-name> has been created with the NOT ENFORCED attribute and will not be enforced during INSERT, UPDATE, OR DELETE statements.
```
-Where <referential-triggered-action> can either be ON DELETE or ON
-UPDATE.
+Where <constraint-name> is the name of the constraint you specified.
-*Cause:* NO ACTION referential action is specified in the referential
-integrity definition, and the CONTROL QUERY DEFAULT value for
-REF_CONSTRAINT_NO_ACTION_LIKE_RESTRICT is 'OFF.'
+*Cause:* You created a table with a referential constraint but specified NOT ENFORCED for that constraint. NOT ENFORCED is commonly
+used when specifying a constraint for documentation purposes only.
-*Effect:* The NO ACTION referential action cannot be defined.
+*Effect:* This is a warning message only. The DDL succeeds, however the constraint named is not enforced at run time.
-*Recovery:* To alter the behavior of NO ACTION referential action, set
-the appropriate value for the REF_CONSTRAINT_NO_ACTION_LIKE_RESTRICT
-default.
+*Recovery:* None needed.
-[[SQL-1302]]
-== SQL 1302
+[[SQL-1323]]
+== SQL 1323
```
-NO ACTION referential action for <referential-triggered-action> clause behaves like RESTRICT referential action. To alter the behavior, set the appropriate value for the REF_CONSTRAINT_NO_ACTION_LIKE_RESTRICT default.
+Unable to grant privileges while creating <object-name>.
```
-Where <referential-triggered-action> can either be ON DELETE or ON
-UPDATE.
+Where <object-name> is the name of a {project-name} object.
-*Cause:* NO ACTION referential action is specified in the referential
-definition and the CONTROL QUERY DEFAULT value for
-REF_CONSTRAINT_NO_ACTION_LIKE_RESTRICT is 'SYSTEM.'
+*Cause:* While creating the given object, {project-name} encountered an error when setting the privileges for that object. This error
+is usually accompanied by other error messages that give details on the cause.
-*Effect:* The NO ACTION referential action has RESTRICT referential
-action semantics. It is recorded as NO ACTION in the metadata table.
+*Effect:* The operation fails.
-*Recovery:* To alter the behavior of the NO ACTION referential action,
-set the appropriate value for the REF_CONSTRAINT_NO_ACTION_LIKE_RESTRICT
-default.
+*Recovery:* Recovery depends on the specific cause of the error, as described in the accompanying error messages.
<<<
-[[SQL-1305]]
-== SQL 1305
+[[SQL-1330]]
+== SQL 1330
```
-The specified schema location <directory> is already in use by schema <schema>.
+Cannot revoke role <role-name> from authorization ID <user-name>. Role has been granted to another authorization ID.
```
-Where <directory> is the {project-name} platform subvolume name specified in
-the LOCATION clause of the CREATE SCHEMA command.
+Where <role-name> is the role name you specified.
-Where <schema> is the ANSI name of an existing schema that already uses
-<directory> as a schema subvolume.
+Where <user-name> is the user name you specified.
-*Cause:* In a CREATE SCHEMA command, you specified <directory> in the
-LOCATION clause; however, this subvolume is already being used as schema
-subvolume by <schema>.
+*Cause:* While executing a REVOKE ROLE command to revoke the given role from the given user, {project-name} discovered that
+the user had granted that role to yet another user.
-*Effect:* The statement fails unless it includes the optional REUSE
-clause to allow reuse of the same schema subvolume name. If the REUSE
-clause is used, this is a warning message and the schema is created
-successfully. The warning can be issued repeatedly for a single CREATE
-SCHEMA command if multiple schemas already exist with <directory> as the
-schema subvolume.
+*Effect:* The operation fails.
-*Recovery:* Only schemas that are RDF replicated to another node should
-have the same subvolume names as their corresponding schemas on the
-other node. To create these, use the optional REUSE clause in the CREATE
-SCHEMA statement. All other schemas should have unique subvolume names.
-Schemas that are, or will be, related as RDF primary and backup schemas
-must have identical schema names and subvolumes on the primary and
-backup nodes.
+*Recovery:* Have the user revoke the role, then resubmit.
-[[SQL-1307]]
-== SQL 1307
+[[SQL-1331]]
+== SQL 1331
```
-The schema location <directory> is reserved for {project-name} metadata.
+User <directory-service-user-name> does not exist in the directory service.
```
-Where <directory> is the {project-name} platform subvolume name specified in
-the LOCATION clause of the CREATE SCHEMA command.
+Where <directory-service-user-name> is a directory service user name that you specified.
-*Cause:* In a CREATE SCHEMA command, you specified subvolume in the
-LOCATION clause, however subvolume names with the format
-ZSD<digit><anything> are reserved for {project-name} database software
-metadata schemas.
+*Cause:* You attempted a REGISTER USER or ALTER USER EXTERNAL NAME statement, but the directory service user name
+does not exist in the directory service.
*Effect:* The operation fails.
-*Recovery:* Specify a subvolume name using the format
-ZSD<letter><anything> in the LOCATION clause, and resubmit.
+*Recovery:* Correct the directory service user name and resubmit.
<<<
-[[SQL-1309]]
-== SQL 1309
+[[SQL-1332]]
+== SQL 1332
```
-Object type for <object-name> is not valid for the current operation.
+Error while communicating with the directory service.
```
-Where <object-name> is the name of the object.
+*Cause:* You attempted a REGISTER USER or ALTER USER EXTERNAL NAME statement, but the directory service is unavailable.
+
+*Effect:* The operation fails.
+
+*Recovery:* Restore availability of the directory service, then resubmit.
+
+[[SQL-1333]]
+== SQL 1333
+
+```
+User <user-name> does not exist.
+```
-*Cause:* You specified an object for an SQL operation that does not
-support its object type.
+Where <user-name> is the name of the user you specified.
+
+*Cause:* You specified an UNREGISTER or ALTER USER statement for a user that does not exist.
*Effect:* The operation fails.
-*Recovery:* Specify an object of valid object type and retry the
-operation.
+*Recovery:* Correct the user name and resubmit.
-[[SQL-1310]]
-== SQL 1310
+<<<
+[[SQL-1334]]
+== SQL 1334
```
-The CREATE SCHEMA statement does not support the creation of triggers.
+User or role <user-or-role-name> already exists.
```
-*Cause:* You specified creation of triggers in the CREATE SCHEMA
-statement.
+Where <user-or-role-name> is the name of the user or role you specified.
+
+*Cause:* You specified a REGISTER statement for a user or role that already exists.
+
+*Effect:* The operation fails.
+
+*Recovery:* Correct the user or role name and resubmit.
+
+[[SQL-1335]]
+== SQL 1335
+
+```
+Directory service user <directory-service-user-name> already defined in the database.
+```
+
+Where <directory-service-user-name> is a directory service user name that you specified.
+
+*Cause:* You specified a directory service user name in a REGISTER statement or in
+the EXTERNAL NAME clause of an ALTER USER statement, and the directory service user name
+already is defined in the {project-name} instance.
+
+*Effect:* The operation fails.
+
+*Recovery:* Correct the external user name and resubmit.
+
+<<<
+[[SQL-1337]]
+== SQL 1337
+
+```
+<user-name> is a reserved authorization identifier.
+```
+
+Where <user-name> is a user name that you specified.
+
+*Cause:* The <user-name> you specified in a REGISTER, ALTER USER or UNREGISTER statement
+is a reserved identifier. For example, "PUBLIC" is reserved; an attempt to REGISTER or
+UNREGISTER "PUBLIC" will fail with this error.
+
+*Effect:* The operation fails.
+
+*Recovery:* Correct the user name and resubmit.
+
+[[SQL-1338]]
+== SQL 1338
+
+```
+Role <role-name> is not defined in the database.
+```
+
+Where <role-name> is a role name that you specified.
+
+*Cause:* You specified a role name in a GRANT, REVOKE or DROP ROLE statement that
+does not exist in the database.
+
+*Effect:* The operation fails.
+
+*Recovery:* Correct the role name and resubmit.
+
+<<<
+[[SQL-1339]]
+== SQL 1339
+
+```
+<role-name> is not a grantable role.
+```
+
+Where <role-name> is a role name that you specified.
+
+*Cause:* You attempted to grant a role that is not grantable. For example, "PUBLIC" is not a grantable role.
+
+*Effect:* The operation fails.
+
+*Recovery:* Correct the role name and resubmit.
+
+[[SQL-1340]]
+== SQL 1340
+
+```
+<user-name> is not a user.
+```
+
+Where <user-name> is a user name that you specified.
+
+*Cause:* You specified a name in a GET PRIVILEGES FOR USER statement that cannot be
+a user name. For example, GET PRIVILEGES FOR USER "PUBLIC" will generate this error.
+
+*Effect:* The operation fails.
+
+*Recovery:* Correct the user name and resubmit.
+
+<<<
+[[SQL-1347]]
+== SQL 1347
+
+```
+Cannot unregister user. User owns one or more roles.
+```
+
+*Cause:* You specified an UNREGISTER command, but the user name specified owns one
+or more roles.
+
+*Effect:* The operation fails.
+
+*Recovery:* Correct the user name and resubmit.
+
+[[SQL-1348]]
+== SQL 1348
+
+```
+Cannot drop role. Role is granted to one or more users.
+```
+
+*Cause:* You attempted a DROP ROLE statement but the role you are attempting to
+drop is granted to one or more users.
+
+*Effect:* The operation fails.
+
+*Recovery:* Revoke the role from any users, then resubmit.
+
+<<<
+[[SQL-1349]]
+== SQL 1349
+
+```
+Cannot unregister user. User granted one or more roles.
+```
+
+*Cause:* You specified an UNREGISTER command, but the user name specified has been granted one
+or more roles.
+
+*Effect:* The operation fails.
+
+*Recovery:* Revoke the roles from the user, then resubmit.
+
+[[SQL-1351]]
+== SQL 1351
+
+```
+Role <role-name> appears multiple times in list.
+```
+
+Where <role-name> is one of the role names you specified.
+
+*Cause:* You specified a list of role names in a GRANT ROLE or REVOKE ROLE statement, but
+the given role name appears more than once in the list.
+
+*Effect:* The operation fails.
+
+*Recovery:* Correct the role name list (for example, removing the duplication), then resubmit.
+
+<<<
+[[SQL-1352]]
+== SQL 1352
+
+```
+User <user-name> appears multiple times in list.
+```
+
+Where <user-name> is one of the user names you specified.
+
+*Cause:* You specified a list of user names in a GRANT ROLE or REVOKE ROLE statement, but
+the given user name appears more than once in the list.
+
+*Effect:* The operation fails.
+
+*Recovery:* Correct the user name list (for example, removing the duplication), then resubmit.
+
+<<<
+[[SQL-1355]]
+== SQL 1355
+
+```
+Granting a role to PUBLIC or _SYSTEM is not allowed.
+```
+
+*Cause:* You attempted to grant a role to PUBLIC or _SYSTEM in a GRANT ROLE statement.
+
+*Effect:* The operation fails.
+
+*Recovery:* Correct the statement, then resubmit.
+
+[[SQL-1356]]
+== SQL 1356
+
+```
+Cannot create the component privilege specified. Component privilege code <privilege-code> for the component already exists.
+```
+
+Where <privilege-code> is the privilege code you specified.
+
+*Cause:* You attempted to create a component privilege (CREATE COMPONENT PRIVILEGE statement),
+but the privilege code you specified is already defined.
+
+*Effect:* The operation fails.
+
+*Recovery:* Correct the statement, then resubmit.
+
+<<<
+[[SQL-1357]]
+== SQL 1357
+
+```
+Cannot create the component privilege specified. Component privilege name <privilege-name> for the component already exists.
+```
+
+Where <privilege-name> is the privilege name you specified.
+
+*Cause:* You attempted to create a component privilege (CREATE COMPONENT PRIVILEGE statement),
+but the privilege name you specified is already defined.
+
+*Effect:* The operation fails.
+
+*Recovery:* Correct the statement, then resubmit.
+
+[[SQL-1364]]
+== SQL 1364
+
+```
+Cannot revoke role <role-name>. Object <object-name-1> depends on privileges on object <object-name-2>.
+```
+
+Where <role-name> is the role name you specified in a REVOKE ROLE statement.
+
+Where <object-name-1> and <object-name-2> are objects in the database.
+
+*Cause:* You attempted to revoke a role from a particular user, but this is not allowed because the object <object-name-1>
+owned by that user depends on an object <object-name-2>, and the user has access to the latter object through the role
+privileges. This can happen, for example, if the user created a schema, then in that schema, created a view that references
+an object not owned by the user, but accessible to the user through the role.
*Effect:* The operation fails.
-*Recovery:* Remove the creation of triggers from the CREATE SCHEMA
-statement and resubmit. Create triggers in separate statements.
+*Recovery:* Drop the dependent object <object-name-1>. Then resubmit the REVOKE ROLE statement.
<<<
+[[SQL-1366]]
+== SQL 1366
+
+```
+Request failed. One or more dependent procedures exist.
+```
+
+*Cause:* You attempted to drop a library (DROP LIBRARY statement), but there is a user-defined function or procedure
+that references this library.
+
+*Effect:* The operation fails.
+
+*Recovery:* Drop any functions or procedures that reference this library. Then resubmit the DROP LIBRARY statement.
+
+[[SQL-1370]]
+== SQL 1370
+
+```
+The authorization name "<authorization-name>" contains one or more invalid characters. A valid name can only contain these characters: [a-zA-Z_0-9-@./]
+```
+
+Where <authorization-name> is the user name you specified.
+
+*Cause:* You attempted to execute a REGISTER USER command, but the user name you specified contains characters that
+are not permitted.
+
+*Effect:* The operation fails.
+
+*Recovery:* Correct the user name and resubmit.
+
+<<<
+[[SQL-1382]]
+== SQL 1382
+
+```
+JAR or DLL file <file-name> not found.
+```
+
+Where <file-name> is the file name you specified.
+
+*Cause:* You attempted to execute a CREATE LIBRARY statement, but the library file does not exist.
+
+*Effect:* The operation fails.
+
+*Recovery:* Correct the file name and resubmit.
+
+[[SQL-1388]]
+== SQL 1388
+
+```
+Object <hive-object-name> does not exist in hive metadata.
+```
+
+Where <hive-object-name> is the name of an Apache Hive object.
+
+*Cause:* You specified the name of a Hive object in a {project-name} DML statement, but that Hive object
+is not defined in the Hive metadata.
+
+*Effect:* The operation fails.
+
+*Recovery:* Correct the object name and resubmit.
+
+<<<
+[[SQL-1389]]
+== SQL 1389
+
+```
+Object <object-name> does not exist in Trafodion.
+```
+
+Where <object-name> is the name of a {project-name} object.
+
+*Cause:* You specified the given object name in a DML or DDL statement, but the object does not
+exist in the {project-name} database.
+
+*Effect:* The operation fails.
+
+*Recovery:* Correct the object name and resubmit.
+
+[[SQL-1390]]
+== SQL 1390
+
+```
+Object <object-name> already exists in Trafodion.
+```
+
+Where <object-name> is the name of a {project-name} object.
+
+*Cause:* You specified the given object name in a CREATE statement, but the object already
+exists in the {project-name} database.
+
+*Effect:* The operation fails.
+
+*Recovery:* Correct the object name and resubmit.
+
+<<<
+[[SQL-1391]]
+== SQL 1391
+
+```
+<object-name> is a <object-kind> object and cannot be updated.
+```
+
+Where <object-name> is the name of a {project-name} object that you specified.
+
+Where <object-kind> is a description of what kind of an object it is (e.g. "metadata").
+
+*Cause:* You attempted an INSERT, UPDATE, DELETE or other write DML statement on a table
+where that is not allowed.
+
+*Effect:* The operation fails.
+
+*Recovery:* Correct the object name and resubmit.
+
+[[SQL-1392]]
+== SQL 1392
+
+```
+Trafodion is already initialized on this system. No action is needed.
+```
+
+*Cause:* You attempted an INITIALIZE TRAFODION statement on a {project-name} instance that has already been initialized.
+
+*Effect:* The operation does nothing.
+
+*Recovery:* None needed; the instance is already initialized. If your intent was to re-initialize the instance, first
+perform INITIALIZE TRAFODION, DROP to destroy the old instance, then INITIALIZE TRAFODION to initialize the new instance. Note that
+destroying your old instance destroys all data in the instance.
+
+<<<
+[[SQL-1393]]
+== SQL 1393
+
+```
+Trafodion is not initialized on this system. Do 'initialize trafodion' to initialize it.
+```
+
+*Cause:* You attempted a SQL statement on a {project-name} instance that has not yet been initialized.
+
+*Effect:* The operation fails.
+
+*Recovery:* Execute INITIALIZE TRAFODION to initialize the instance, then resubmit.
+
+[[SQL-1394]]
+== SQL 1394
+
+```
+Trafodion needs to be reinitialized on this system due to missing or corrupted metadata objects. Do 'initialize trafodion, drop' followed by 'initialize trafodion' to reinitialize Trafodion. This will delete all metadata and user objects from the Trafodion database and recreate metadata.
+```
+
+*Cause:* The metadata objects do not have the structure that {project-name} expects. This may be due to corruption. Another possibility
+is an older release of {project-name} software has been installed and brought up. At this time {project-name} does not support downgrade.
+
+*Effect:* The operation fails.
+
+*Recovery:* The recovery depends upon the cause and on whether there is a desire to keep the data in the instance. If corruption has happened
+it may be possible to manually restore the metadata tables. This may be difficult, however; contact the {project-name} dlist for help.
+If it is due to the improper installation of software, installing the correct version and restarting the instance may solve the problem.
+If there is no need to keep data from the instance, you can do INITIALIZE TRAFODION, DROP followed by INITIALIZE TRAFODION.
+
+<<<
+[[SQL-1395]]
+== SQL 1395
+
+```
+Trafodion needs to be upgraded on this system due to metadata version mismatch. Do 'initialize trafodion, upgrade' to upgrade metadata. Or do 'initialize trafodion, drop' followed by 'initialize trafodion'. Be aware that the second option will delete all metadata and user objects from Trafodion database.
+```
+
+*Cause:* A new version of the {project-name} software has been installed, and a metadata upgrade is required as a result.
+
+*Effect:* The operation fails.
+
+*Recovery:* Perform INITIALIZE TRAFODION, UPGRADE to upgrade the metadata. Note: {project-name} supports upgrade only in single release
+increments. So, if you desire to upgrade your instance by multiple release increments, you will need to install each of the intervening
+releases serially and do a metadata upgrade on each. If you do not care about keeping your data, you can instead drop the metadata using INITIALIZE TRAFODION, DROP and then do an INITIALIZE TRAFODION. Please note though that all data in your instance will be lost if you choose this option.
+
+[[SQL-1396]]
+== SQL 1396
+
+```
+Trafodion needs to be reinitialized on this system due to data format version mismatch.
+```
+
+*Cause:* A new version of the {project-name} software has been installed, and that version uses a different data format. Note: The
+data format has never yet changed in {project-name}, so this error should never be seen.
+
+*Effect:* The operation fails.
+
+*Recovery:* Contact the {project-name} dlist.
+
+<<<
+[[SQL-1397]]
+== SQL 1397
+
+```
+Software version of objects being used is different than the version of software running on the system. Make sure that objects being used are built with the same version as that running on the system. Version of Trafodion software is determined by file sqenvcom.sh.
+```
+
+*Cause:* This error is most likely to be seen in a {project-name} development environment at the beginning of a new release
+development cycle. The
+software version information in the built objects differs from that in sqenvcom.sh. This can happen, for example, if you have
+created a new branch in which sqenvcom.sh has been updated, but you bring up software that was built on the previous branch.
+
+*Effect:* The operation fails.
+
+*Recovery:* Assuming this is a development environment, rebuild the {project-name} software to get the correct software version numbers.
+If this is not a development environment, contact the {project-name} dlist.
+
+[[SQL-1398]]
+== SQL 1398
+
+```
+Error <error-number> occured while accessing the HBase subsystem. Fix that error and make sure HBase is up and running. Error Details: <HBase-diagnostics>.
+```
+
+Where <error-number> is an internal {project-name} error code.
+
+Where <HBase-diagnostics> is a Java exception stack trace from HBase, which indicates the cause of the error.
+
+*Cause:* An error occurred when {project-name} attempted an HBase access. The HBase diagnostics may give an indication of the cause.
+
+*Effect:* The operation fails.
+
+*Recovery:* Take action as indicated by the HBase diagnostics. Insure that the HBase subsystem is up and running correctly.
+
+<<<
+[[SQL-1399]]
+== SQL 1399
+
+```
+Metadata has already been upgraded. No action is needed.
+```
+
+*Cause:* You executed an INITIALIZE TRAFODION, UPGRADE statement but the metadata version is already up-to-date.
+
+*Effect:* The operation does nothing.
+
+*Recovery:* None needed.
+
+[[SQL-1401]]
+== SQL 1401
+
+```
+The default value of column <column-name> contains characters that cannot be converted to character set <character-set-name>.
+```
+
+Where <column-name> is a column name you specified.
+
+Where <character-set-name> is the character set of the column you specified.
+
+*Cause:* In a CREATE TABLE or ALTER TABLE ADD COLUMN statement, you specified a default value for the given column that
+cannot be converted to that column's character set.
+
+*Effect:* The operation fails.
+
+*Recovery:* Correct the DEFAULT clause literal and resubmit.
+
+<<<
+[[SQL-1402]]
+== SQL 1402
+
+```
+Unique index <index-name> could not be created with the DIVISION LIKE TABLE option. Only non-unique indexes are supported with this option.
+```
+
+Where <index-name> is an index name you specified.
+
+*Cause:* You specified both UNIQUE and DIVISION LIKE TABLE in a CREATE INDEX statement. {project-name} does not support unique indexes
+with the DIVISION LIKE TABLE option.
+
+*Effect:* The operation fails.
+
+*Recovery:* Either remove UNIQUE or remove DIVSION LIKE TABLE from the CREATE INDEX statement and resubmit.
+
+[[SQL-1403]]
+== SQL 1403
+
+```
+This ALTER command is not allowed on a reserved system schema object.
+```
+
+*Cause:* You specified an ALTER INDEX statement on an index in a reserved schema (e.g. the metadata schema).
+
+*Effect:* The operation fails.
+
+*Recovery:* Correct the index schema name and resubmit.
+
+<<<
+[[SQL-1404]]
+== SQL 1404
+
+```
+Column <column-name> cannot be altered. Reason: <reason>
+```
+
+*Cause:* You specified an ALTER TABLE ALTER COLUMN statement, but the column cannot be altered. The reason gives details on why.
+
+*Effect:* The operation fails.
+
+*Recovery:* Correct the statement and resubmit.
+
[[SQL-1420]]
== SQL 1420
@@ -2574,6 +3087,7 @@ Column <column-name> cannot be dropped or altered as it is part of the table's p
*Recovery:* Correct the column name or table name as appropriate and resubmit.
+<<<
[[SQL-1421]]
== SQL 1421
@@ -2716,4 +3230,43 @@ reserved by {project-name} for internal use.
*Recovery:* Correct the statement and resubmit.
+<<<
+[[SQL-1431]]
+== SQL 1431
+
+```
+Object <object-name> exists in HBase. This could be due to a concurrent transactional ddl operation in progress on this table.
+```
+
+Where <object-name> is an object name you specified.
+
+*Cause:* You attempted to create an object, but the object already exists in HBase. It may be the case that the object is being created
+(or dropped) in another concurrent transaction.
+
+*Effect:* The operation fails.
+
+*Recovery:* Check to see if the object exists. If not, resubmit the statement again. If the transaction is long-running, you may need
+to attempt this multiple times.
+
+[[SQL-1432]]
+== SQL 1432
+
+```
+Input LOB type <storage-type-1> does not match column's storage type: <storage-type-2> Column name: <column-name> .
+```
+
+Where <storage-type-1> is the storage type of an input LOB value you specified.
+
+Where <storage-type-2> is the storage type of the target LOB column.
+
+Where <column-name> is the name of the target LOB column.
+
+*Cause:* You attempted to store a LOB value into a LOB column, but the storage type of the LOB value and the target column are not
+compatible. For example, you may have attempted
+
+*Effect:* The operation fails.
+
+*Recovery:* Consult the Trafodion SQL Large Objects Guide for more information about LOB storage types. Correct the statement
+and resubmit.
+
[2/2] trafodion git commit: Merge [TRAFODION-2865] PR 1366 Update
Messages Guide for msgs 1300-1432
Posted by db...@apache.org.
Merge [TRAFODION-2865] PR 1366 Update Messages Guide for msgs 1300-1432
Project: http://git-wip-us.apache.org/repos/asf/trafodion/repo
Commit: http://git-wip-us.apache.org/repos/asf/trafodion/commit/9b53555e
Tree: http://git-wip-us.apache.org/repos/asf/trafodion/tree/9b53555e
Diff: http://git-wip-us.apache.org/repos/asf/trafodion/diff/9b53555e
Branch: refs/heads/master
Commit: 9b53555e3ad0fe07d854f2187f666a4de0611cab
Parents: ff6ce5a ba0c83f
Author: Dave Birdsall <db...@apache.org>
Authored: Thu Jan 4 19:21:49 2018 +0000
Committer: Dave Birdsall <db...@apache.org>
Committed: Thu Jan 4 19:21:49 2018 +0000
----------------------------------------------------------------------
core/sql/bin/SqlciErrors.txt | 136 ++--
core/sql/sqlcomp/CmpDDLCatErrorCodes.h | 121 ++--
.../src/asciidoc/_chapters/ddl_msgs.adoc | 701 +++++++++++++++++--
3 files changed, 752 insertions(+), 206 deletions(-)
----------------------------------------------------------------------