Copyright © Cloud Software Group, Inc. All Rights Reserved |
Secondary index cannot be defined and built on fields with syntax W and F.Do not use SIXBUILD on fields with syntax W or F.The table definition is too large to be processed. Possible reasons are:
• The Data Object Broker parameter CTABLESIZE is too smallIncrease the Data Object Broker parameter CTABLESIZE from 8 to 16 to double the CTABLE size to 16 KB. The Data Object Broker must be shut down and restarted with the new parameter.The source of a parameter (PRM) table must be a TDS table.Online use of SIXBUILD is restricted by the size of the table, for performance and operation reasons.Use S6BBRSIX to build a secondary index when the table has more than 3000 data pages.The input field name is not one of the defined fields for the table.Verify the field name and repeat the operation.The secondary index was not built, but was expected.Call SIXBUILD (online) or S6BBRSIX (offline) to build the secondary index and repeat the operation.You tried to build a secondary index when it already exists.You used SIXBUILD (to build a secondary index) on a field whose length is greater than maximum allowed.Do not use SIXBUILD on a field with a length greater than 127.Certain database operations, such as SIXBUILD and CLRTAB, are applicable only to TDS tables.Do not use SIXDELETE or CLRTAB on non-native tables (i.e., tables other than TDS tables). Do not use SIXBUILD on non-TDS tables.You tried to build an index (SIXBUILD) or delete an index (SIXDELETE) on a primary key.Do not use SIXBUILD or SIXDELETE on a primary key field.The maximum number of fields allowed in a composite key is 16.Reduce the number of fields in the composite key.The requested table has not been defined yet.No occurrence for the table is in the FIELDS table, but an occurrence exists in the TABLES table.Use the Table Definer to define fields for the table.The name of a source table was not provided when required.The calculated row length (based on the sum of field lengths) exceeds 4051 bytes.The field number must be an integer greater than 0.Edit the occurrences of the FIELDS table to ensure that all NUMBER values are greater than 0 and consecutive.Stored ordering must either be A (for ascending) or D (for descending).Edit the occurrences of the ORDERING table for this table to ensure that the order is A or D.For TDS tables, the primary key field must be the first field.Edit the occurrence for the table in the FIELDS table to ensure that the field where NUMBER=1 is the primary key.The only type of key supported for an IDgen table is one with binary syntax (B) and a length of 4.Use the Table Definer to either set IDgen=N or define the primary key correctly.The table definition is too large to be processed. Possible reasons are:
• The Data Object Broker parameter CTABLESIZE is too smallIncrease the Data Object Broker parameter CTABLESIZE from 8 to 16 to double the CTABLE size to 16 KB. The Data Object Broker must be shut down and restarted with the new parameter.For a field with a semantic type of logical (L), its LENGTH must be 1.Either change the field type or field length to avoid error.For a field with binary syntax (B), only lengths of 2 and 4 are currently supported.Zero DECIMAL required with type/syntax specified forUnless a field is defined with packed decimal syntax (P), the DECIMAL field must be 0.Either make SYNTAX=P or set DECIMAL=0 for the indicated field.For a field of floating point syntax (F), only three places of precision are supported.The combination of semantic type and syntax is not supported.Refer to the Managing Data manual for the permitted syntaxes for each semantic type.The syntax for the indicated field is not permitted for its semantic type.Refer to the Managing Data manual for the permitted syntaxes for each semantic type.The semantic type for the indicated field is not permitted for its syntax.Refer to the Managing Data manual for the permitted syntaxes for each semantic type.The screen name is not found in the table SCREENS.The screen has no corresponding screen table.Use the Screen Painter to define at least one screen table.Every screen table must have at least one field.Use the Screen Table Painter to create at least one field for the named screen table.An error was encountered in building a CTABLE for the screen table while building a CTABLE for the screen.Check that all the field definitions for the indicated screen table are correct or contact TIBCO Support.No screen field is defined for the indicated screen table.Use the Screen Table Painter to define at least one field for the screen table.Too many screen fields or too many screen tables are defined for the screen.Change the Data Object Broker parameter XTABLESIZE from 16 KB (the default size) to an appropriate value, or reduce the number of screen tables and screen fields.The reference table name provided in the REFERENCE field of the FIELDS table does not exist.Set the REFERENCE field to null or provide a valid table name.The reference table named in the REFERENCE field of the FIELDS table cannot be a screen table or an export table.Set the REFERENCE field to null or provide a valid table name.Composite primary key must be defined over contiguous fields.Redefine the table using Table Definer. Rearrange the order of defined fields such that the primary key fields are contiguous.Window ctable build error encountered in definition tableAn inconsistency has been detected in the definition table. For example, the table instance for the window may be empty, or a graphical object mapping a screen field (given by @DATAMAPPING) may not exist in the window. This could have resulted from editing the definition table without knowing the dependencies involved.For a nonexistent graphical object as an occurrence in @DATAMAPPING, either add the graphical object through the Window Builder or remove the occurrence from @DATAMAPPING. Contact TIBCO Support.The requested table is not in @IDMSTABLES.No occurrence was found in the table @IDMSTABLES for the requested IDM table.Delete the table definition for the given table (by using the Table Editor) and redefine the table with the CA-IDMS manager system.The IDMSACCESS page retrieved is not a data page.The subschema definition for the given table does not exist in TIBCO(r) Object Service Broker.Load the subschema definition with the CA-IDMS manager system.Record name not found in table IDMSRECORDSThe requested record was not found in the subschema definition.Use the CA-IDMS manager system to reload the subschema.Delete and redefine the CA-IDMS table definition.FIELDS(tablename) and @IDMSFIELDS(tablename) do not match.Delete and redefine the CA-IDMS table definition.The requested field was not found in the subschema definition.The requested element name was not found in the @IDMSELEMENTS table for the given subschema and record.The IDM table definition has exceeded the maximum allowed.Increase the XTABLESIZE= parameter in the Data Object Broker startup.No definition could be found for the indicated report.Check that you have specified the correct report name.No component report tables exist for the indicated report.Use the Report Definer to define the report tables you want to include in the indicated report.There are no report fields defined for the indicated report table.Define some report fields for the indicated report table, or remove the report table name from the report definition.The table definition for the indicated report table cannot be found.If the Data Object Broker parameters CTABLESIZE and XTABLESIZE are both set to 31, the definition of the indicated report is too complex. In other words, there are too many report tables, report fields, or literals for this report.Ensure the Data Object Broker Parameters CTABLESIZE AND XTABLESIZE are set to 31. If the problem still occurs, decrease the number of report fields and literals for this report.The length of a Unicode field cannot be an odd number.
Copyright © Cloud Software Group, Inc. All Rights Reserved |