Meta-schema Manager / Meta-schema Manager Reference |
Number | Description |
---|---|
GS-11000 |
Unexpected error. An unexpected error occurred. |
GS-11001 |
Error while reading file schema: description. An error occurred while reading the file file. The details about the error can be found in the description part of the message. |
GS-11002 |
Cannot find codec. The appropriate codec cannot be found to read a file. |
GS-11003 |
Cannot find codec for encoding encoding. The appropriate codec for encoding encoding cannot be found. |
GS-11004 |
Error while creating new schema document. The Meta-schema Manager failed to create a new document. |
GS-11050 |
Schema file defined in GSTSCHEMANAMES cannot be found in FGLDBPATH. The file cannot be found. |
GS-11051 |
Failed to load file file. An error occurred while loading the file file . |
GS-11052 |
Failed to open file file for writing. Check the file permissions and those of its owner directory. |
GS-11053 |
Failed to open file file for reading. Check the file permissions and those of its owner directory. |
GS-11100 |
Failed to locate node. The specified database object cannot be found in the schema. |
GS-11101 |
Unexpected schema object. An unexpected schema object has been found in the 4db or 4dbx document. The schema file is corrupted and cannot be read. |
GS-11102 |
Missing schema name. The schema name cannot be found. This property is required and the loading of the schema file cannot continue. |
GS-11103 |
Missing schema property property. This property is required, but it cannot be found. The loading of the schema file cannot continue. |
GS-11104 | Invalid schema property
property. The schema property property has an invalid value. The loading of the schema file cannot continue. |
GS-11105 |
Schema contains no table or column. No valid tables have been found in the schema. A valid table is a table in which is not flagged has been removed and which contains at least one column in which is not flagged has been removed. |
GS-11106 |
Empty schema file. The schema document contains no information. |
GS-11107 | File is saved using a newer version of Genero Studio. Please upgrade Genero Studio. The schema document has been saved with a newer version of Genero Studio. You will need to upgrade Genero Studio to be able to open it. |
GS-11108 |
Schema name is not lowercase, its use in 4GL source will generate errors. The schema name contains uppercase characters. Using it in 4GL programs might generate compilation errors. Use lowercase for the Schema name. |
GS-11109 |
Schema cannot contain both type and other type type columns. The schema contains columns with mutually exclusive types. For instance it contains both CHAR / VARCHAR and NCHAR / NVARCHAR columns |
GS-11111 |
Unexpected table. An unexpected table object has been found in the 4db or 4dbx document. The schema file is corrupted and cannot be read. |
GS-11112 |
Missing table name. The table name cannot be found. This property is required and the loading of the schema file cannot continue. |
GS-11113 |
Missing table property property. The table property property is required but it cannot be found. The loading of the schema file cannot continue. |
GS-11114 |
Invalid table property property. The table property property has an invalid value. The loading of the schema file cannot continue. |
GS-11115 |
Schema already contains a table table. The table has already been found in the 4db or 4dbx document. The document cannot contain two tables with the same name. |
GS-11116 |
Table table is not found. Creating temporary table. The table cannot be found, and it is required by another database object. A surrogate table will be created. |
GS-11117 |
Table contains no columns. The table does not contain any columns. |
GS-11121 |
Unexpected column. An unexpected column object has been found in the 4db or 4dbx document. The schema file is corrupted and cannot be read. |
GS-11122 |
Missing column name. The column name cannot be found. This property is required and the loading of the schema file cannot continue. |
GS-11123 |
Missing column property property. The column property property is required but it cannot be found. The loading of the schema file cannot continue. |
GS-11124 |
Table table already contains a column column. The column has already been found in the table. The document cannot contain two columns with the same name within the same table. |
GS-11125 | Index index already contains a column column. The column has already been found in the index. The document cannot contain two columns with the same name within the same index. |
GS-11126 |
Foreign key key already contains a column column. The document cannot contain two columns with the same name within the same foreign key. |
GS-11127 |
Column column is not found in table table. Creating temporary column. The column cannot be found in the table and it is required by another database object. A surrogate column will be created. |
GS-11128 |
Column column in table table has unsupported type: type. The type is not supported for column within table. An unsupported type is of form encoded=(type, length), and can be generated while extracting database schemas. |
GS-11129 |
Column column in table table has invalid type: type. The type is invalid for column within table. An invalid type is not handled by the 4GL language. |
GS-11130 |
Column name is of type type. Related to error GS-11109. One message will be generated per column involved in error GS-11109. |
GS-11131 |
Unexpected foreign key. An unexpected foreign key object has been found in the 4db or 4dbx document. The schema file is corrupted and cannot be read. |
GS-11132 |
Missing foreign key name. The foreign key name cannot be found. This property is required, and the loading of the schema file cannot continue. |
GS-11133 |
Missing foreign key property property. The foreign key property property is required, but it cannot be found. The loading of the schema file cannot continue. |
GS-11134 |
Schema already contains a foreign key key. The foreign key has already been found in the 4db or 4dbx document. The document cannot contain two foreign keys with the same name. |
GS-11135 |
Schema already contains a foreign key key. Renaming user-defined foreign key to name. The foreign key has already been found in the 4db or 4dbx document. The document cannot contain two foreign keys with the same name. The foreign key will be renamed to name. |
GS-11136 |
Foreign key key is not found. Creating temporary foreign key. The foreign key key cannot be found, and it is required by another database object. A surrogate foreign key will be created. |
GS-11137 |
Table table is not found for foreign key key. The table the foreign key refers to cannot be found. The loading of the schema file cannot continue. |
GS-11138 |
Column column is not found in table table for foreign key key. The column the foreign key refers to cannot be found in the table. The loading of the schema file cannot continue. |
GS-11139 |
Foreign key key does not contain any table column. The foreign key does not contain any columns. |
GS-11140 | Foreign key key columns column and reference have different data types. The foreign key columns have mismatching data types. |
GS-11141 |
Unexpected index. An unexpected index object has been found in the 4db or 4dbx document. The schema file is corrupted and cannot be read. |
GS-11142 |
Missing index name. The index name cannot be found. This property is required and the loading of the schema file cannot continue. |
GS-11143 |
Missing index property property. The index property is required but it cannot be found. The loading of the schema file cannot continue. |
GS-11144 |
Table table already contains an index index. The index has already been found in the table table. The document cannot contain two indexes with the same name within the same table. |
GS-11145 |
Table table already contains an index index. Renaming user-defined index to name. The index has already been found in the table. The document cannot contain two indexes with the same name within the same table. The index will be renamed to name. |
GS-11146 |
Index index is not found. Creating temporary index. The index cannot be found in the table and it is required by another database object. A surrogate index will be created. |
GS-11147 |
Column column is not found in table table for index index. The column that the index refers to cannot be found in the table. The loading of the schema file cannot continue. |
GS-11148 |
Table table contains more than one primary index. The table contains more than one primary index. Only one primary index can be defined for a table. |
GS-11149 |
Index index does not contain any table column. The index does not contain any columns. |
GS-11151 |
Unexpected column validation attributes. An unexpected column validation object has been found in the 4db or 4dbx document. The schema file is corrupted and cannot be read. |
GS-11152 |
Missing column name for validation attributes. The column name that the validation attributes refer to cannot be found. This property is required and the loading of the schema file cannot continue. |
GS-11323 | Constraint or index name column order of
name conflicts with column order of foreign key.
Indicates the order of columns in the foreign key is not the same as the one defined for the constraint or index. |
GS-11330 | Foreign key name column order of column conflicts with column order of other column. Several columns are defined in the foreign key with the same order. The order of the column is automatically updated to solve the issue. |
GS-11553 |
Can't convert order for column column of table table. The column has an unsupported order value. The import of the sch file cannot continue. |
GS-11600 |
Compilation generated an empty sch file. The compilation of the schema document generated an empty sch file. This can happen when no valid table columns have been found in the document. |
GS-11650 |
The extraction process task can't be generated. An error occurred while trying to create the database extraction process. |
GS-11651 |
Database name can't be empty. An empty database name has been found while trying to set up the database connection. |
GS-11652 |
Schema file name can't be empty. An empty file name has been found while trying to generate the schema document. |
GS-11653 |
Preparing schema extraction... This message indicates the schema extraction process is being set up. |
GS-11654 |
Schema extraction started... This message indicates the schema extraction process has started. |
GS-11655 |
Merging extracted schema with existing one... This message indicates the schema extraction process tries to merge the existing schema document with the extracted one. |
GS-11656 |
Generating schema id... This message indicates a new schema identifier is being generated. |
GS-11657 | Schema extraction successful. This message indicates the schema extraction process has successfully completed. |
GS-11658 |
Schema extraction failed. The schema extraction process has failed at some point. Refer to other messages to get additional information. |
GS-11659 |
Schema extraction aborted. The schema extraction process has been aborted by the user. |
GS-11660 |
Failed to move temporary schema file to destination. An error occurred while trying to move the temporary schema file to its destination. |
GS-11661 |
Failed to create schema backup file. An error occurred while trying to create a backup of the schema file. |
GS-11700 |
The connection test process task can't be generated. An error occurred while trying to create the database connection test process. |