Meta-schema Manager error messages

Unexpected error.

An unexpected error occurred.

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.

Cannot find codec.

The appropriate codec cannot be found to read a file.

Cannot find codec for encoding encoding.

The appropriate codec for encoding encoding cannot be found.

Error while creating new schema document.

The Meta-schema Manager failed to create a new document.

Dynamic property property not found for node node.

Failed to read dynamic property.

An error occurred while reading dynamic properties. The meta-schema file might be corrupted.

Schema file defined in GSTSCHEMANAMES cannot be found in FGLDBPATH.

The file cannot be found.

Failed to load file file.

An error occurred while loading the file file .

Failed to open file file for writing.

Check the file permissions and those of its owner directory.

Failed to open file file for reading.

Check the file permissions and those of its owner directory.

File already exists.

Check the filename and directory.

Failed to locate node.

The specified database object cannot be found in the schema.

Unexpected schema.

An unexpected schema object has been found in the 4db or 4dbx document. The schema file is corrupted and cannot be read.

Missing schema name.

The schema name cannot be found. This property is required and the loading of the schema file cannot continue.

Missing schema property property.

This property is required, but it cannot be found. The loading of the schema file cannot continue.

The schema property property has an invalid value. The loading of the schema file cannot continue.

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.

Empty schema file.

The schema document contains no information.

File is saved using a newer version of Genero Studio. Please upgrade Genero Studio.

Schema name is not lowercase, its use in 4GL source will generate errors.

The schema name contains uppercase characters. Using it in Genero programs might generate compilation errors. Use lowercase for the Schema name.

The usage of both CHAR/VARCHAR and NCHAR/NVARCHAR columns is not supported by all databases.

The schema contains columns with mutually exclusive types. For instance it contains both CHAR / VARCHAR and NCHAR / NVARCHAR columns.

Schema name is invalid, its use in BDL source will generate errors.

The schema name contains characters not supported by the Genero language.

Unexpected table.

An unexpected table object has been found in the 4db or 4dbx document. The schema file is corrupted and cannot be read.

Missing table name.

The table name cannot be found. This property is required and the loading of the schema file cannot continue.

Missing table property property.

The table property property is required but it cannot be found. The loading of the schema file cannot continue.

Invalid table property property.

The table property property has an invalid value. The loading of the schema file cannot continue.

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.

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.

Table contains no columns.

The table does not contain any columns.

Unexpected column.

An unexpected column object has been found in the 4db or 4dbx document. The schema file is corrupted and cannot be read.

Missing column name.

The column name cannot be found. This property is required and the loading of the schema file cannot continue.

Missing column property property.

The column property property is required but it cannot be found. The loading of the schema file cannot continue.

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.

Constraint or index index already contains a column column.

Foreign key key already contains a column column.

The document cannot contain two columns with the same name within the same foreign key.

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.

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.

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 BDL language.

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.

Missing foreign key name.

The foreign key name cannot be found. This property is required, and the loading of the schema file cannot continue.

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.

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.

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.

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.

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.

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.

Foreign key key does not contain any table column.

The foreign key does not contain any columns.

Foreign key key columns column and reference have different data types.

Unexpected constraint or index.

An unexpected index object has been found in the 4db or 4dbx document. The schema file is corrupted and cannot be read.

Missing constraint or index name.

The index name cannot be found. This property is required and the loading of the schema file cannot continue.

Missing constraint or index property property.

The index property is required but it cannot be found. The loading of the schema file cannot continue.

Table table already contains a constraint or index named 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.

Table table already contains a constraint or index named index. Renaming user-defined constraint or 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.

Constraint or index index is not found. Creating temporary constraint or index.

The index cannot be found in the table and it is required by another database object. A surrogate index will be created.

Column column is not found in table table for constraint or index index.

The column that the index refers to cannot be found in the table. The loading of the schema file cannot continue.

Table table contains more than one primary key.

The table contains more than one primary index. Only one primary index can be defined for a table.

Constraint or index index does not contain any table column.

The index does not contain any columns.

Column column allows null values but is referred by primary key primary key.

A column referred in a primary key doesn't have its NOT NULL flag set.

Unexpected column validation attributes.

An unexpected index object has been found in the 4db or 4dbx document. The schema file is corrupted and cannot be read.

Missing column name for validation attributes.

The column name cannot be found. This property is required and the loading of the schema file cannot continue.

Column 'column' already contains validation attributes.

Column validation attributes have already been defined for the column. The loading of the schema file cannot continue.

Column 'column' is not found in table 'table' for column validation attributes.

Column validation attributes refer to a non-existing column. The loading of the schema file cannot continue.

Unexpected column video attributes.

An unexpected index object has been found in the 4db or 4dbx document. The schema file is corrupted and cannot be read.

Missing column name for video attributes.

The column name cannot be found. This property is required and the loading of the schema file cannot continue.

Column 'column' already contains video attributes.

Video attributes have already been defined for the column. The loading of the schema file cannot continue.

Column 'column' is not found in table 'table' for column video attributes.

Column video attributes refer to a non-existing column. The loading of the schema file cannot continue.

Unexpected user attributes.

An unexpected user attribute has been found in the 4db or 4dbx document. The schema file is corrupted and cannot be read.

Missing user attribute name.

The user attribute name is required but cannot be found. The loading of the schema file cannot continue.

Missing user attribute property 'property'.

The user attribute property property is required but cannot be found. The loading of the schema file cannot continue.

Object already contains a user attribute 'attribute'.

A user attribute has already been defined for the database object. The loading of the schema file cannot continue.

Unexpected layout data section.

An unexpected layout section has been found in the 4db or 4dbx document. The schema file is corrupted and cannot be read.

Missing layout data property property.

The layout property property is required but it cannot be found. The loading of the schema file cannot continue.

Unexpected database data section.

An unexpected data section has been found in the 4db or 4dbx document. The schema file is corrupted and cannot be read.

Missing database data property property.

The data property property is required but it cannot be found. The loading of the schema file cannot continue.

Document already contains database value for identifier.

Database data has already been found in the 4db or 4dbx document. The document cannot contain twice data for the same identifier.

Document contains invalid identifier identifier for database value (value: value). Database value will be ignored and removed.

The database data identifier doesn't match any database object. The associated value is ignored and will be discarded upon save.

Unexpected dynamic property.

An unexpected dynamic property has been found in the 4db or 4dbx document. The schema file is corrupted and cannot be read.

Missing dynamic property attribute attribute.

The dynamic property attribute attribute is required but it cannot be found. The loading of the schema file cannot continue.

Object doesn't support dynamic property property.

A dynamic property has been read for a database object but this property is not defined for this object. Check the appropriate template is selected before opening the meta-schema.

Object already contains a dynamic property property.

A dynamic property has been defined twice for a database object.

Invalid model node info version.

Model node info for type type not found.

Failed to add property property to model node info: a dynamic property with this name already exists

Failed to add property property to model node info: a static property with this name already exists

Failed to add property property to model node info: a property with this name was not found

Information about model node is invalid.

Name cannot be empty.

The name of a database object is empty.

Same name cannot be applied to more than one table.

Two tables cannot have the same name in the meta-schema.

Same name cannot be applied to more than one column of same table.

Two columns of the same table cannot have the same name in the meta-schema.

Same name cannot be applied to more than one foreign key.

Two foreign keys cannot have the same name in the meta-schema.

Same name cannot be applied to more than one constraint or index of same table.

Two constraints or indexes of the same table cannot have the same name in the meta-schema.

Table name is invalid.

A table cannot be named with the provided name.

Column name is invalid.

A column cannot be named with the provided name.

Database object name contains invalid character(s).

The name of the database object contains invalid characters.

The name name has been converted to other name as database object name contains invalid character(s).

The original name of the database object contains invalid characters. The database object has been renamed to a new name.

Unexpected extraction options.

An unexpected extraction options section has been found in the 4db or 4dbx document. The schema file is corrupted and cannot be read.

Unexpected extraction settings.

An unexpected extraction settings section has been found in the 4db or 4dbx document. The schema file is corrupted and cannot be read.

Unexpected generation options.

An unexpected generation options section has been found in the 4db or 4dbx document. The schema file is corrupted and cannot be read.

Unexpected generation settings.

An unexpected generation settings section has been found in the 4db or 4dbx document. The schema file is corrupted and cannot be read.

The database object name has been newly added in schema.

The database object has been added to the schema and is not yet found in the database. Creating a database update script will generate SQL instructions to add this object to the database.

The database object name has been marked as removed from schema.

The database object has been removed from the schema and can still be found in the database. Creating a database update script will generate SQL instructions to remove this object from the database.

Name has been modified from name to other name.

The database object has been renamed in the schema and can still be found in the database. Creating a database update script will generate SQL instructions to update this object in the database.

Database object name has an invalid uuid. A new one has be generated (uuid).

The internal identifier of the database object is invalid and has been replaced with a new one.

Column type has been changed from type to other type.

The type of the column has been changed in the schema. Creating a database update script will generate SQL instructions to update the column in the database.

Not null property has been changed from value to other value.

The value of the 'Not null' property of the column has been changed in the schema. Creating a database update script will generate SQL instructions to update the column in the database.

Column column in table table uses Informix specific type: type.

The column uses an Informix® specific data type.

Invalid qualifiers for column 'column' in table 'table'.

DATETIME or INTERVAL qualifiers break the qualifiers rules for the data type. See the Genero Business Development Language User Guide for further details.

Constraint or index type has been changed from type to other type.

The type of the constraint has been changed in the schema. Creating a database update script will generate SQL instructions to update the constraint in the database.

Constraint or index columns of name has been changed from columns to other columns.

The columns of the constraint have been changed in the schema. Creating a database update script will generate SQL instructions to update the constraint in the database.

Indicates the order of columns in the foreign key is not the same as the one defined for the constraint or index.

Foreign key table has been changed from table to other table.

The table associated to the foreign key has been changed in the schema. Creating a database update script will generate SQL instructions to update the foreign key in the database.

Foreign key referenced table has been changed from table to other table.

The reference table associated to the foreign key has been changed in the schema. Creating a database update script will generate SQL instructions to update the foreign key in the database.

Foreign key columns of foreign key has been changed from columns to other columns.

The columns associated to the foreign key have been changed in the schema. Creating a database update script will generate SQL instructions to update the foreign key in the database.

Foreign key referenced columns of foreign key has been changed from columns to other columns.

The reference columns associated to the foreign key have been changed in the schema. Creating a database update script will generate SQL instructions to update the foreign key in the database.

Cascade delete property has been changed from value to other value.

The value of the 'Cascade delete' property of the foreign key has been changed in the schema. Creating a database update script will generate SQL instructions to update the foreign key in the database.

Foreign key name column order of column conflicts with column order of other column.

Constraints or indexes constraint and other constraint are defined on same set of columns.

Both constraints are defined on the same set of columns.

Foreign key foreign key references columns which are not part of primary key or unique constraint.

No primary key or secondary key is defined on the columns referenced by the foreign key.

Constraint cannot be placed on a BYTE or TEXT column.

A unique constraint has been defined on column of type BYTE or TEXT.

Non-unique index index conflicts with constraint constraint.

A non-unique index has been defined on the same set of columns has a unique constraint.

Foreign key references an inactive table.

The table referenced by the foreign key is flagged as inactive whereas the table associated to the foreign key is active.

Foreign key table is inactive.

The table associated to the foreign key is flagged as inactive whereas the table referenced by the foreign key is active.

Name has been modified to 'name' but matches value in database.

The property of the database object has been changed in both the meta-schema and the database with the same value. The change becomes useless and can be reverted.

Column type has been changed to 'column type' but matches value in database.

The property of the database object has been changed in both the meta-schema and the database with the same value. The change becomes useless and can be reverted.

Not null property has been changed to 'property' but matches value in database.

The property of the database object has been changed in both the meta-schema and the database with the same value. The change becomes useless and can be reverted.

Constraint or index type has been changed to 'value' but matches value in database.

The property of the database object has been changed in both the meta-schema and the database with the same value. The change becomes useless and can be reverted.

Constraint or index columns of 'property' has been changed to 'property' but matches value in database.

The property of the database object has been changed in both the meta-schema and the database with the same value. The change becomes useless and can be reverted.

Foreign key columns of 'property' has been changed to 'property' but matches value in database.

The property of the database object has been changed in both the meta-schema and the database with the same value. The change becomes useless and can be reverted.

Foreign key referenced columns of 'property' has been changed to 'property' but matches value in database.

The property of the database object has been changed in both the meta-schema and the database with the same value. The change becomes useless and can be reverted.

Cascade delete property has been changed to 'property' but matches value in database.

The property of the database object has been changed in both the meta-schema and the database with the same value. The change becomes useless and can be reverted.

Foreign key table has been changed to 'value' but matches value in database.

The property of the database object has been changed in both the meta-schema and the database with the same value. The change becomes useless and can be reverted.

Foreign key referenced table has been changed to 'value' but matches value in database.

The property of the database object has been changed in both the meta-schema and the database with the same value. The change becomes useless and can be reverted.

Unknown tag tag.

The meta-schema document contains unknown data. The schema file is corrupted and cannot be read.

Wrong line format.

The data contained in the file being imported to a meta-schema has an unsupported format. The data cannot be imported.

Can't convert type for column column of table table.

The type of the table column defined in the imported table is unsupported. The data cannot be imported.

Can't convert length for column column of table table.

The length of the table column defined in the imported table is invalid. The data cannot be imported.

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.

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.

The extraction process task can't be generated.

An error occurred while trying to create the database extraction process.

Database name can't be empty.

An empty database name has been found while trying to set up the database connection.

Schema filename can't be empty.

An empty filename has been found while trying to generate the schema document.

Preparing schema extraction...

This message indicates the schema extraction process is being set up.

Schema extraction started...

This message indicates the schema extraction process has started.

Merging extracted schema with existing one...

This message indicates the schema extraction process tries to merge the existing schema document with the extracted one.

Generating schema id...

This message indicates a new schema identifier is being generated.

Schema extraction successful.

Schema extraction failed.

The schema extraction process has failed at some point. Refer to other messages to get additional information.

Schema extraction aborted.

The schema extraction process has been aborted by the user.

Failed to move temporary schema file to destination.

An error occurred while trying to move the temporary schema file to its destination.

Failed to create schema backup file.

An error occurred while trying to create a backup of the schema file.

Failed to remove schema backup file.

An error occurred while trying to delete a backup of the schema file.

The connection test process task can't be generated.

An error occurred while trying to create the database connection test process.

Generating documentation for meta-schema...

This message indicates documentation for the schema is being generated.

Documentation generated at location

This message indicates documentation for the schema has been generated and is saved at the given location.

Invalid command line arguments

Check command line help for valid options. See The gsdbdoc command for more information.

Failed to generate documentation.

An error prevented the generation of the documentation. See The gsdbdoc command for more information.

Invalid log level.

Only VERBOSE is allowed. See The gsdbdoc command for more information.

Schema file is required.

The tool requires a database schema file. See The gsdbdoc command for more information.

Empty schema file path.

The provided path to the database schema is empty. See The gsdbdoc command for more information.

Schema file cannot be found.

The database schema file cannot be accessed. See The gsdbdoc command for more information.

Cannot access output path.

The provided output path cannot be accessed. See The gsdbdoc command for more information.

Style file not found.

The provided style file cannot be accessed. See The gsdbdoc command for more information.

Failed to copy style file.

The provided style file cannot be copied into the output directory. See The gsdbdoc command for more information.

Template directory not found.

The provided template directory cannot be accessed. See The gsdbdoc command for more information.

Failed to load template settings.

The settings from the provided template directory cannot be loaded. See The gsdbdoc command for more information.

Using template directory 'directory'.

Indicates which BAM template is used.

Template directory is relative, using builtin directory to locate it.

Indicates that the BAM template used is a built-in template.

No output path provided, defaulting to current directory.

Indicates that the documentation will be generated in the current directory.

No style path provided, using default styles.

Indicates that default styling will be used.

This is an informational message indicating the provided style file is located in the output directory, and no copy of the file is required.

error (error_code): error_message

The execution of the DB Explorer query failed. Refer to the error message for a detailed explanation.

Warning: no row affected.

The executed DB Explorer query did not affect any row.

Executed query: query

This message displays the executed DB Explorer query.

Success: number_of_rows row(s) affected.

This message displays the number of rows affected by the DB Explorer query.

Select execution successful : number_of_rows row(s) returned.

This message displays the number of rows returned by a SELECT statement by the DB Explorer.

Sql command successful

The DB Explorer query was successful.

Limit of number_of_rows row(s) reached.

The DB Explorer query has returned more rows than the limit set in the DB Explorer preferences.

Connection id: connection_information

This message displays the connection parameter used by the DB Explorer to connect to the database.

Failed to extract database meta data.

The extraction of the meta-schema has failed. Refer to the previous messages for more information.

Failed to connect to database.

The connection to the database has failed. Ensure the appropriate connection information has been provided.

Cannot instantiate database driver driver.

The database driver cannot be loaded. Check the driver name is correct and accessible.

Unsupported database database.

This database engine is not supported by the extraction tool.

The type type of column "table.column" is unsupported - table is ignored.

The data type of the table column is not supported by the extraction tool. The extraction of the table is canceled.

type column table.column is ignored.

The data type of the table column has been flagged to be ignored by the extraction tool. The table definition will not contain this column.

Foreign key foreign key is ignored due to missing table.

The foreign key references a table that was not found during extraction. The meta-schema will not contain this foreign key.

Failed to extract indexes for table "table".

A SQL error occurred while indexes were extracted for the table.

Failed to extract foreign keys.

A SQL error occurred while the foreign keys were extracted from the schema.

No column extracted for table "table" - table is ignored.

No table column has been extracted by the extraction tool. The extraction of the table is cancelled.

Database object "name" is ignored.

The database object has been ignored by the extraction tool. This usually happens with objects generated by the database. For further details, see Extract a meta-schema information from a database.

Table column "table.column" datatype [type] is unsupported and has been converted.

The data type of the table column is not supported by the extraction tool, but the tool converted it to a similar data type.

Unexpected conversion parameter.

The conversion method provided to the extraction tool is invalid.

Missing conversion method.

The conversion method is required by the extraction tool.

Missing auto-increment indicator.

The parameter required for the extraction of the table column is not found.

Missing charlen indicator.

The parameter required for the extraction of the table column is not found.

Missing column type indicator.

The parameter required for the extraction of the table column is not found.

Missing distinct types indicator.

The parameter required for the extraction of the table column is not found.

Missing identity indicator.

The parameter required for the extraction of the table column is not found.

Missing serial indicator.

The parameter required for the extraction of the table column is not found.

Missing datetime precision indicator.

No database connection.

The connection to the database is not found.

Table name is required.

The name of the extracted table is required by the extraction tool.

Column name is required.

The name of the extracted table column is required by the extraction tool.

Database schema is required.

The database schema / table owner is required by the extraction tool.

Missing database driver.

The database driver has not been provided to the extraction tool.

Missing output file parameter.

The meta-schema file has not been provided to the extraction tool.

Failed to read user password.

The password is unreadable.

Unsupported argument arg.

The argument arg provided to the command line is unsupported.

Unsupported argument arg.

The argument arg provided to the command line requires an additional parameter.

unexpected error

An unexpected error has been encountered. Refer to the error message for a detailed explanation.