Messages 20001 - 20600
EDA20001 DIMENSION %1 REPEATED FOR MDI %2
The field has been specified as a dimension for an MDI more than once. Remove repeated specifications.
EDA20002 NUMBER OF DIMENSIONS EXCEEDS SYSTEM LIMIT %1
The total number of dimensions must be less than the given limit. Eliminate dimensions belonging to MDIs that are not required for the application.
EDA20003 TOTAL DIMENSION LENGTH FOR MDI %1 EXCEEDED MAX LIMIT %2
The sum of the lengths of all dimensions in an MDI must not exceed the given limit. Reduce the lengths of the dimensions or remove some fields from the MDI.
EDA20004 MULTIPLE TARGETS %1 AND %2 DEFINED FOR MDI %3
An MDI cannot have more than one target class. Remove extra TARGET_OFs
EDA20005 THE WTIHIN FIELD %1 FOR DIMENSION %2 IN MDI %3 DOES NOT EXIST
The Dimension has a parent defined via the WITHIN keyword that is not declared as a FIELD. Add the parent as a dimension.
EDA20006 WITHIN FIELD %1 FOR DIMENSION %2 IN MDI %3 IS NOT A DIMENSION
A Dimension can only have another dimension as a parent. Ensure that the WITHIN field exists as a dimension for the same MDI.
EDA20007 THE WITHIN DIMENSION %1 OCCURS IN TWO HEIRARCHIES FOR MDI %2
A parent dimension cannot have more than one child dimension. Remove one of the hierarchies.
EDA20008 INTERNAL ERROR SETTING DEFINE FIELD AS A DIMENSION
An error occurred while trying to create a DEFINEd field as a dimension in an MDI.
EDA20009 MEMORY ALLOCATION ERROR
Unable to allocate sufficient memory to build the MDI.
EDA20010 NO DIMENSIONS SPECIFIED FOR MDI %1
The specified MDI has no dimensions defined for it in the Master File. Specify the dimensions.
EDA20011 MDI %1 NOT FOUND FOR MASTER %2
The MDI specified was not found in the master given. Check the Master for the Target Class and Dimensions.
EDA20012 NUMBER OF DIMENSIONS IN MDI %1 EXCEEDED SYSTEM LIMIT %2
An MDI may not have more than the above number of dimensions. Reduce the number of dimensions.
EDA20013 NUMBER OF PARTITIONS FOR MDI %1 EXCEEDED SYSTEM LIMIT %2
An MDI cannot be built over more than the above number of partitions. Reduce the number of partitions specified in the ACCESSFILE for the above MDI.
EDA20014 MDI INTERNAL ERROR %1
An Internal Error in the MDI system. Contact iWay.
EDA20015 MDI %1 FOR MASTER %2 HAS %3
The horizontal partitions for the above master specified in the ACCESSFILE are not the same as when the MDI was built.
EDA20016 THE DATA FOR MASTER %1 WAS MODIFIED AFTER MDI %2 WAS BUILT
One of the partitions for the Master was updated after the Index was built. REBUILD the MDI before querying it.
EDA20017 DUPLICATE PARTITION %3 IN MASTER %1 FOR MDI %2
There are duplicate entries in the ACCESSFILE entry for the above Master and MDI.
EDA20018 MDI %1 DOES NOT TARGET THE %2 DATABASE (%3
The MDI was not built against the given database. The database this MDI is actually targeting is the one specified in parenthesis.
EDA20019 INSUFFICIENT PARTITIONS TO BUILD MDI %2 AGAINST DATABASE %1
The number of partitions specified for the MDI in the given Master's ACCESSFILE is not enough. Add a few more and build the Index again.
EDA20020 UNABLE TO LOCATE PARTITION %2 FOR MDI %1
The physical file for the MDI could not be found. Ensure that the files exist as specified in the ACCESSFILE or in the current work area.
EDA20021 INSUFFICIENT PARTITIONS. MDI %1 WAS BUILT WITH %2 PARTITIONS
The partitions for the MDI that were specified in the ACCESSFILE are fewer in number than were used to build the MDI.
EDA20022 PHYSICAL PARTITION %2 FOR MDI %1 MISSING
A partition of the MDI specified in the ACCESSFILE does not exist.
EDA20023 INVALID NUMBER OF BINS FOR MDI : %1
The number of bins available for the MDI is invalid. Use SET MDIBINS to set the number to a valid one.
EDA20024 TARGET NOT FOUND FOR MDI %1
There was no TARGET class specified for the MDI.
EDA20025 MDI %1 SPANS MULTIPLE PATHS
An MDI may not span more than a single path across the database.
EDA20026 CANNOT FIND A HOST DATABASE %1 TO BUILD AN MDI %2
An attempt was made to build the MDI file but no host database was found in the ACCESSFILE or in user work area, check the case of host file name in your procedures.
EDA20027 MDI %1 CONTAINS ONLY ONE DIMENSION
A user may not build an MDI with only one dimension. Please specify additional dimensions before building the Index.
EDA20028 QUERY MDI INTERNAL ERROR
An Internal Error in the QMDI system. Contact iWay.
EDA20029 TARGET NOT FOUND IN MASTER FILE : %1
There was no TARGET class specified for the MDI.
EDA20030 MASTER FILE HAS NO MDI INFORMATION : %1
The master file does not contain any multi-dimensional index attribute.
EDA20031 SYNTAX ERROR FOR ? MDI
Syntax: ? MDI <mastername> "mdiname|*" "PCHOLD "AS <holdfile>]"
EDA20032 ERROR PARSING FILE %1
The master file does not exist or contains a syntax error. Run check file for more information.
EDA20033 TOO MANY PARAMETERS IN ? MDI
Syntax: ? MDI <mastername> "mdiname|*" "PCHOLD "AS <holdfile>]"
EDA20034 TOO FEW PARAMETERS IN ? MDI
Syntax: ? MDI <mastername> "mdiname|*" "PCHOLD "AS <holdfile>]"
EDA20035 MDI %1 CONTAINS AN ILLEGAL WITHIN CYCLE
The WITHIN structure specified in the MDI induces a cycle. Remove WITHIN <fieldname> from the one you designate as root.
EDA20036 UNABLE TO LOCATE DATABASE FOR : %1
No physical file could be located for the specified database.
EDA20037 THE SPECIFIED VERB OBJECT IS NOT PART OF ANY MDI : %1
You can retrieve encoded values only for fields that are dimensions of an MDI. Run < ? MDI > to determine the structure of your MDI(s).
EDA20038 MDI %1 NOT FOUND IN MASTER FILE.
To retrieve encoded values you have to specify a valid MDI name after the master file, in the TABLE request.
EDA20039 DIMENSIONS %1 AND %2 ARE NOT IN THE SAME HIERARCHY.
The specified dimensions are part of the same MDI but are not part of the same hierarchy. Run < ? MDI > to know the structure of your MDI(s).
EDA20040 AT LEAST ONE DIMENSION IS NOT PART OF THE MDI : %1
The verb is not a dimension for the specified MDI. Run < ? MDI > to determine the structure of your MDI(s).
EDA20041 NO MDI HAS BEEN SPECIFIED IN YOUR TABLE REQUEST
To retrieve encoded values, TABLE FILE must be followed by a Master File name, followed by a dot, followed by an MDI name.
EDA20042 DIMENSIONS ARE NOT IN THE SAME HIERARCHY.
The specified dimensions are part of the same MDI but are not part of the same hierarchy. Run < ? MDI > to determine the structure of your MDI(s).
EDA20043 MDI WITHIN INTERNAL ERROR. %1
An error occurred retrieving encoded values. MDI file might not match master file description.
EDA20044 MDI FILE NOT FOUND : %1
The physical name associated to the MDI cannot be found. Check the spelling, check ACCESSFILE if any.
EDA20045 THE SPECIFIED DIMENSION IS NOT ENCODED: %1
There are no encoded values for the specified dimension. Only dimensions involved in a WITHIN structure or with a MAXVALUES attribute are encoded. Run < ? MDI > to determine the structure of your MDI(s).
EDA20046 CANNOT ADD TO AN UNPARTITIONED MDI %2 FOR MASTER %1
The Access file only contains a single partition for the above MDI. The MDI Add option only works with partitioned MDIs.
EDA20047 MDI %1 DOES NOT SUPPORT ADDITIONS
The current MDI was built via an earlier release. In order to add to the MDI it must be rebuilt with the current release.
EDA20048 NO NEW PARTITIONS FOUND FOR MDI %1 IN MASTER %2
All current partitions of the above Master have already been indexed by the specified MDI. Add new partitions to the host database and execute the ADD again.
EDA20049 WARNING! LOW CARDINALITY FOR DIMENSION %1. (%2)
A limited number of unique values for a dimension affect its participation in the MDI. This may result in a performance penalty for queries that utilize the MDI.
EDA20050 MDI MODULE NOT LOADED
The feature invoked involves Fusion module MDI. This module has not been loaded or cannot be found.
EDA20051 MDI ERROR: NO RECORDS FROM HOST %1
The MDI Engine could not find any records to index. Check to see if there are any records in the database. Also, check if all the records were excluded by a WHERE clause in the REBUILD statement.
EDA20052 ILLEGAL TOKEN %1 IN MDI NAME %2
The above token may not be used in an MDI Name. Choose another name or remove the token.
EDA20053 PARTITION %2 OF MDI %1 IS CORRUPTED
The specified partition of multi-dimensional index is empty or corrupted. Use REBUILD/MDINDEX to re-create the MDI.
EDA20054 ERROR ACTIVATING ATTRIBUTRE MANAGER FOR MDI %1 IN HOST %2
The MDI engine failed to activate MDI Attribute Manager. This error is most likely caused by invalid MDI page format. Use REBUILD/MDINDEX command to rebuild the MDI.
EDA20055 MDI %1 IN HOST %2 IS INCOMPLETE. PLEASE REBUILD.
The specified MDI is not valid because its build has not been completed. Rebuild the MDI using NEW option of the REBUILD/MDINDEX command.
EDA20056 MDI %1 HAS MIXED PARTITION DATA TYPES
You can not build or use an MDI file agains multiple data partition types (i.e. FUSION or FOCUS or XFOCUS). You are only allowed to build an MDI against one of these types at a time.
EDA200xx - EDA20197 ERROR MESSAGE TEXT MISSING
EDA20198 FATAL ERROR IN DATABASE I/O. TERMINATING SESSION
A severe error was encountered in reading from or writing to the application data files. The system is unable to recover from this error; it is safer to return to the host environment.
EDA20199 ERROR MESSAGE TEXT MISSING
EDA20200 ERROR MESSAGE TEXT MISSING
EDA20201 BOTH DATASET AND ACCESS FILE NOT PERMITTED
A Master file cannot specify a DATASET and an ACCESS file at the same time.
EDA20202 MEMORY ALLOCATION ERROR
Access File Memory Failure.
EDA20203 ACCESS FILE %1 ( MASTER %2 ) NOT FOUND
The Access File specified in the Master could not be found. Check the spelling and/or the location of the Access File.
EDA20204 ACCESS FILE SYSTEM ERROR
The Access File system could not execute the Access File.
EDA20205 UNABLE TO OPEN ACCESS FILE %1
The Access File specified could not be opened. Check the permissions and/or the name of the Access File.
EDA20206 ACCESS FILE %1 HAS MULTIPLE ENTRIES FOR MASTER %2
No Access File may have two entries for a single master. Remove all duplicate entries from the Access File.
EDA20207 NO ENTRY FOUND FOR MASTER %1 IN ACCESS FILE %2
An Access File specified in the Master MUST have a corresponding MASTER name. Add a MASTER entry to the Access File, or remove the Access File from the Master.
EDA20208 UNABLE TO PARSE ACCESS FILE
An error occurred while trying to parse the Access File.
EDA20209 PARSER ERROR: %1
There is a grammatical and/or syntactical error in the Access File. If nn/ii/ll is shown then look at line nn, column ii, for a length of ll for the problem token.
EDA20210 FUSION: WHERE CLAUSES LOCATED IN USE COMMAND
Fusion Databases utilize Access Files which incorporate WHERE clauses for horizontal partitioning. Use Access Files instead.
EDA20211 UNABLE TO PARSE WHERE CLAUSE
The WHERE clause in the Access File could not be parsed. Check the clause and parse the Master again.
EDA20212 ACCESS FILE LOGICAL NAME LENGTH EXCEEDED : %1
Logical Names: Master File Name, External Location Names, and External Index Names Logical names may not exceed 8 characters.
EDA20213 ERROR MESSAGE TEXT MISSING
EDA20214 INDEX %1 NOT FOUND IN MASTER
Each Index entry in an Access file must have a definition in the corresponding Master file.
EDA215 ACCESS FILE SYSTEM ERROR FOR FILE : %1
Check the physical file name in the Access File.
EDA20216 TOO MANY PARTITIONS. PARTITION %1 FOR MASTER %2 EXCEEDS LIMIT.
There is a limit to the total number of physical partitions that may be used in a request. Delete partitions that are not needed from the Access File.
EDA20217 ACCESS FILE TOKEN %1 TOO LONG
The Token in the Access File is too long. No Token may be longer than 80 characters.
EDA20218 DUPLICATE CLASS LOCATION %1 IN PARTITION %2 IN ACCESS FILE
There are multiple entries for the given Class in the Access File. In a given horizontal partition, only one Class Location entry for a class may be defined.
EDA20219 PARTITION %2 IS MISSING AN ENTRY FOR LOCATION %1
If a location entry exists for a horizontal partition, it must be specified for all partitions.
EDA20220 DUPLICATE ENTRY FOR INDEX %1
There are duplicate entries for the given MDI in the Access file. Erase the duplicate entry. For a given master only one entry per index is permitted.
EDA20221 DUPLICATE PARTITION %1 FOR MDI %2 IN MASTER %3
The entry for an MDI for the given master has duplicate partitions defined. This is not permitted. All partitions must be unique.
EDA20222 ACCESS FILE : MDI %1 DOES NOT EXIST IN MASTER
An MDI entry has been found in an access file for a master, which does not have the corresponding MDI definitions.
EDA20223 %1
EDA20224 WHERE CLAUSE EXCLUDES ALL AVAILABLE PARTITIONS
The WHERE/IF clause in the current request does not match any of the WHERE clauses specified in the Access File. No partitions can be accessed.
EDA20225 UNABLE TO LOAD ACCFILE MODULE
The system is unable to find a required library.
EDA20226 DATASET SPECIFIED FOR MASTER %1 DOES NOT EXIST
The data set specified in the Master either has not been created or cannot be read. Verify the status of the specified physical file.
EDA20227 PARTITION No. %2 FOR DATABASE %1 DOES NOT EXIST
The partition specified in the Access File for the above Master either has not been created or cannot be read. Verify the status of the physical partition.
EDA20228 LOCATION %3 IN PARTITION No. %2 FOR DATABASE %1 DOES NOT EXIST
The physical file specified for the above LOCATION for the specified partition in the given database either does not exist or cannot be read. Verify the status of the file.
EDA20229 MASTER %1 - ACTIVE PARTITION=%2 : ACTUAL PARTITIONS=%3
The Active Partition has been set higher than the total number of partitions specified in the Access file for the above Master.
EDA20230 NO DESCRIPTION FOR PHYSICAL LOCATION OF %1 %2
Fusion Master Files must include either an ACCESSFILE or a DATASET definition to specify the physical location of the database. All LOCATION Classes, External Indices and MDIs must be specified in the ACCESSFILE.
EDA20231 ACCESS OR DATASET DEFINITION REQUIRED FOR FORMAT FUSION
HOLD FORMAT Fusion requires the specification of either a DATASET attribute or an ACCESS file. An ACCESS file may also be appended to using the DATANAME APPEND_TO ACCESS syntax.
EDA20232 VALUE MISSING FOR DATASET KEYWORD IN HOLD FORMAT FUSION
The DATASET keyword must have a value; the physical location of the HOLD file.
EDA20233 DATASET EXCEEDS MAXIMUM LENGTH : %1
The physical file name associated with the DATASET keyword in the HOLD FORMAT FUSION request is too long. The maximum length of the file name is limited to the number of characters specified above.
EDA20234 HOLD FORMAT FUSION SYNTAX ERROR: MISSING %1
The HOLD FORMAT FUSION specification for adding a data set to the entry in an Access File is DATANAME <filename> APPEND_TO ACCESS <Access File Name>.
EDA20235 INVALID PHYSICAL FILENAME %2 FOR MASTER %1
Only absolute file names are accepted by the Fusion Access File and the DATASET command.
EDA20236 - EDA20400 ERROR MESSAGE TEXT MISSING
EDA20401 OPTION MD_EXTERNAL IS VALID ONLY FOR FUSION FILES
Inside a TABLE...HOLD FORMAT <format> request, option MD_EXTERNAL can be specified only for FORMAT FUSION.
EDA20402 OPTION MD_EXTERNAL IS NOT ALLOWED FROM WITHIN HOT SCREEN
In HOT SCREEN mode, MD_EXTERNAL option is not supported, you can issue a TABLE HOLD with FORMAT FUSION and MD_EXTERNAL options.
EDA20403 OPTION MD_EXTERNAL HAS BEEN USED MORE THAN ONCE
You can create only one multi-dimensional index for the HOLD FUSION FILE.
EDA20404 OPTION INDEX HAS BEEN USED MORE THAN ONCE
In TABLE...HOLD FORMAT FUSION, option INDEX cannot be used more than once. To create an index on more than one field, use INDEX option keyword once followed by the list of the fields you want to index.
EDA20405 <LOCATION-NAME> IS MISSING
A Location Name is expected after keyword LOCATION.
EDA20406 DUPLICATED NAME- LOCATION NAME IS ALREADY USED AS A FIELDNAME:
Location name must be unique: in your TABLE ... HOLD FORMAT FUSION request, you cannot specify a location name that is also a FIELDNAME in the output master file.
EDA20407 RESERVED KEYWORD : %1
A reserved keyword has been used in your request. Replace it with a different word.
EDA20408 FUSION CATALOG: UNKNOWN KEYWORD %1
The master file contains a field name whose alias does not map to any of the accepted keywords. The unknown keyword could be part of the old master file description syntax.
EDA20409 NUMBER OF DIMENSIONS IS NOT WITHIN THE LIMITS TABLE
HOLD FORMAT FUSION has been specified and the number of dimensions after keyword MD_EXTERNAL is either smaller than the minimum required or larger than the maximum.
EDA20410 THE FIELD TO BE INDEXED IS NOT IN THE HOLD FILE:
You could have used NOPRINT option with the field you want to create an index on.
EDA20411 DUPLICATED DIMENSION FOR INDEX OR MD_EXTERNAL:
A FIELDNAME has been used more than once as an index in INDEX or MD_EXTERNAL.
EDA20412 THE FIELDNAME IS NOT RECOGNIZED:
The requested field to be indexed is not found in the hold file. The field is not indexed.
EDA20413 THE FIELDNAME IS NOT RECOGNIZED : %1
A word that is assumed to be the name of a data field does not appear on the list of names or aliases for the file. Check the spelling of the fielding.
EDA20414 YOUR REQUEST CANNOT BE COMPLETED
Your table... hold format fusion request violates some rule. None of the steps such as holding data, saving data, and creating files takes place.
EDA20415 MASTER FILE %1 ALREADY FOLLOWS THE FUSION SYNTAX
The file you want to migrate has a master file description that follows the Fusion syntax. You do not need to run migrate.
EDA20416 ERROR CREATING FUSION MASTER FILE %1
An error occurred while writing output on the fusion master file. Check if you have WRITE permission on EDASYN directory or SET EDASYN to a directory for which you have WRITE permission.
EDA20417 SYNTAX ERROR: UNABLE TO TRANSLATE THE ACCEPT-FIND CLAUSE %1
Your FOCUS master file contains an ACCEPT clause with FIND option THAT IS NOT SYNTACTICALLY CORRECT. MIGRATE IS UNABLE TO COMPLETE THE translation from FOCUS to FUSION syntax. Check the FOCUS master file.
EDA20418 SYNTAX ERROR: UNRECOGNIZED OPTION AFTER ACCEPT CLAUSE - %1
The option after ACCEPT is not recognized. MIGRATE is unable to COMPLETE THE TRANSLATION FROM FOCUS TO FUSION SYNTAX.
EDA20419 ERROR PARSING MASTER FILE %1
An error occurred during the parsing of the master file. The error type is specified by the error message issued by the parser before this message.
EDA20420 ERROR RETRIEVING CROSS REFERENCED FILE(S)
The parser could not find at least one of the cross referenced files. You have to migrate all cross referenced files before migrating any master file that contains cross references to those files.
EDA20421 %1 ALREADY EXISTS, PLEASE RENAME IT AND RERUN REBUILD MIGRATE
Your EDASYN directory already contains <filename>.mas. Rename or move it before running rebuild - migrate.
EDA20422 THE SPECIFIED FILE IS NOT AN EXTERNAL INDEX : %1
USE <FILENAME> WITH <DBNAME> requires <FILENAME> to be an external index file.
EDA20423 INDEX FIELD %1 AND TARGET FIELD %2 ARE ON DIFFERENT PATH
The field to be indexed and the target field have to be on the same path. Use a different target field.
EDA20424 EXTERNAL INDEX NOT FOUND : %1
When using REBUILD EXTERNAL INDEX with the ADD option, the index name must exist. Issue a USE-WITH or have it in your local directory.
EDA20425 AMBIGUITY FOUND IN EXTERNAL INDEX NAME : %1
The specified index name is already in also used to reference other files.
EDA20426 AMBIGUITY FOUND IN FIELD NAME : %1
The specified field name occurs more than once in master file. You need to fully qualify it: <class name>.<field name>.
EDA20427 %1 IS NOT A FOCUS DATABASE
Migrate can be used only to migrate FOCUS database to FUSION. The specified master file describes a NON FOCUS database.
EDA20428 MDI JOIN : TO FIELD %1 IS NOT A DIMENSION
When using an MDI Join, all the TO fields have to be Dimensions in an MDI. See the manual for further details.
EDA20429 MDI JOIN FORMAT MISMATCH FOR FIELD %1, DIM %2
In an MDI Join, all FROM Field and TO Dimension pairs must have identical formats.
EDA20430 CLASS %1 : SIZE OF CLASS DECREASES FROM PARTITION %2 TO %3
Schema Evolution is only permitted in the order the database partitions are defined in the Access File. As the partitions are traversed, the individual class sizes may only increase by the addition of fields.
EDA20431 CLASS %1 IN PARTITION %2 IS LARGER THAN DEFINITION IN MASTER
Schema Evolution requires that the Master File description of the database have the latest definitions. No partition of the database may have a class size larger than that defined in the master.
EDA20432 SCHEMA EVOLUTION MEMORY ERROR
The Schema Evolution subsystem has encountered an operating system error while trying to allocate memory.
EDA20433 CLASS %1 HAS SIZE ERRORS IN PARTITION %2
The size of the segment does not exactly match a set of fields as defined in the Master. The Master File may be incorrect, or the Access file may be pointing to incorrect partitions.
EDA20434 UNKNOWN CLASS %1 IN PARTITION %2 OF MASTER %3
The physical database partition has an entry for a class that could not be found in the Master File Description. Please check that the correct master is being used.
EDA20435 DUPLICATE ENTRY IN USE FOR THE EXTERNAL INDEX %1
The USE directory must contain only one entry for the external index. Multiple component indices are not allowed. Please, use ? USE to check the content of USE directory.
EDA20436 EXTERNAL INDEX: NOTHING IN USE FOR DATABASE %1
The USE directory must contain at least one entry for the database you are indexing. Please use ? USE command to check the current content of USE directory.
EDA20437 REBUILD MIGRATE: UNSUPPORTED KEYWORD %1
The master file contains a keyword that is not supported with FUSION databases.
EDA20438 FUSION MASTER ERROR: HOLDMAST NOT ALLOCATED
Features that create new Fusion Masters require that the Masters be created in the HOLDMAST directory. Please allocate HOLDMAST to a suitable location and try the request again.
EDA20439 REBUTIL INTERNAL ERROR: NLS INIT FAILED
Fatal error occurred while initializing NLS (National Language Support).
EDA20440 REBUTIL INTERNAL ERROR: MALLOC FAILED
Fatal error occurred while allocating memory.
EDA20441 JOIN FIELDS IN THE HOST FILE SPAN MULTIPLE PATHS
When doing a multi-field join the FROM fields in the host file must all belong in a single retrieval path.
EDA20442 EXTERNAL INDEX FORMAT IS OBSOLETE: %1
You are trying to use old (obsolete) external index file. System is currently supporting version 1 format only. Use ? FDT command to check index format.
EDA20443 UNRECOGNIZED EXTERNAL INDEX FORMAT: %1
External index has wrong format of the FDT page. Use ? FDT to check file format. Rebuild external index if necessary.
EDA20444 EXTERNAL INDEX: FIELD USED FOR INDEXED VIEW IS TOO LONG
If an external index had been built for a DEFINED field, and this index is used to create an indexed view, the length of the field must not exceed 36 bytes.
EDA20445 - EDA20600 ERROR MESSAGE TEXT MISSING