Error messages are of two kinds. First, there are errors to assist in the revision of input data or the standardization files ( See Changing the Lexicons or Changing the Rules). These are logged in the file "REFERENCE_SHAPESET_NAME.err" ( See Build Error Log) for the build phase or "USER_ATTRIBUTE_TABLE_NAME.err" ( See Match Error Log) for the match phase.
In addition to these there are the general errors, sent to stderr. General errors may also appear in the error logs if they occur after a log is opened.
In addition to the following, other errors may be returned by BerkeleyDB or your system. Check the appropriate documentation if you encounter an error of this kind.
Aborting read of REFERENCE_SHAPESET_NAME. A system error of some kind has occured.
Can't find the address fields in your table. Probe doesn't work. Use a user order table. ( See User Order Table).
Can't open FILENAME. Check name, location and permissions for FILENAME.
Can't open REFERENCE_SHAPESET_NAME. Check name, location and permissions for REFERENCE_SHAPESET_NAME, where REFERENCE_SHAPESET_NAME is the file name provided with the -b switch. ( See Reference Shapeset).
Can't open SCHEMA_TABLE_NAME. Check name, location and permissions for SCHEMA_TABLE_NAME, where SCHEMA_TABLE_NAME is the file name provided with the -b switch. ( See Schema Table).
Can't read line from REFERENCE_SHAPESET_NAME.pgc. The rebuild configuration file is corrupted. Rebuild. ( See The PGC File).
Can't read number from REFERENCE_SHAPESET_NAME.cfg. The rebuild configuration file is corrupted. Rebuild. ( See The PGC File).
Cannot find configuration file for REFERENCE_SHAPESET_NAME. Check name, location and permissions for REFERENCE_SHAPESET_NAME.pgc. ( See The PGC File).
Configuration REFERENCE_SHAPESET_NAME lacks PGC signature. The rebuild configuration file is corrupted. Rebuild. ( See The PGC File).
Could not complete matching. Indicates that matching was aborted.
Could not create standardized table REFERENCE_SHAPESET_NAME.
Could not establish read order USER_ATTRIBUTE_TABLE_NAME. Indicates failure to establish a schema for the table. You will need to either reconfigure your data or your schema table. ( See User Order Table)
Could not find file: rules.txt. Place a copy of this file where PAGC can find it, either in your current working directory or the reference shapeset directory. ( See Rule Records)
Could not find file: gazeteer.csv.. Place a copy of this file where PAGC can find it, either in your current working directory or the reference shapeset directory. ( See lexicon records)
Could not find file: lexicon.csv.. Place a copy of this file where PAGC can find it, either in your current working directory or the reference shapeset directory. ( See lexicon records)
Could not open USER_ATTRIBUTE_TABLE_NAME. Check name, location and permissions for USER_ATTRIBUTE_TABLE_NAME, where USER_ATTRIBUTE_TABLE_NAME is the file name provided with the -m switch. ( See User Attribute Table).
Crucial fields not in reference table. The program requires at least one each of a HOUSE and a STREET attribute field in the reference attribute table. Check if these are present. If so, correct your schema table. ( See Schema Table).
Error: can't standardize your addressing format. A MICRO/MACRO conflict exists in your schema. Correct. ( See User Order Table).
Error: Could not open shape files. Check name, location and permissions for your shape sets.
Error in row N field ATTRIB: STRING is error. Use a valid POSTAL ATTRIBUTE name in the field ATTRIB of the user order table, row N. ( See User Order Table).
Error Rule File: 0 length rule #R. R is the rule number which appears to have no elements. Check, in the file rules.txt, the rule immediately before this rule number and correct it. ( See Rule Records)
Error: Missing record data for beta row NThe terminating symbol for the standardized reference record is missing. Either reduce the length of the data in your reference attribute table fields or recompile PAGC increasing the BETA_FIELD_SIZE.
Error: requires big endian. Match phase is run on a system that uses a different byte order from that used to do the build. ( See The PGC File).
Error: requires integers of size N. Match phase is run on a system that uses a different integer size from that used to do the build. ( See The PGC File).
Error: requires little endian. Match phase is run on a system that uses a different byte order from that used to do the build. ( See The PGC File).
Fatal error restoring configuration REFERENCE_SHAPESET_NAME. The file REFERENCE_SHAPESET_NAME.pgc is needed for rebuilding. ( See The PGC File).
Fatal error: Too many morphemes in input. Check your input to the standardizer and shorten it.
Fatal error: Too many nodes in gamma function. More rules have been added to the rules file (rules.txt) than have been provided for in the program. Recompile PAGC after appropriately increasing the numbers in the source file gamma.h. ( See Rule Records)
Fatal error: Too many rules in file. More rules have been added to the rules file (rules.txt) than have been provided for in the program. Recompile PAGC after appropriately increasing the numbers in the source file gamma.h. ( See Rule Records)
Fatal error: Too many rules for allocated memory. More rules have been added to the rules file (rules.txt) than have been provided for in the program. Recompile PAGC after appropriately increasing the numbers in the source file gamma.h. ( See Rule Records)
Field name conflict for attribute ATTRIBUTE. A schema table is needed. The table uses two field names associated with the attribute ATTRIBUTE. Use a schema table to resolve the conflict. ( See Schema Table).
Missing fields in order table USER_ORDER_TABLE_NAME.Add the missing fields. ( See User Order Table).
Insufficient Memory. Not enough memory for PAGC to run. Check your system resources.
Lexical entry lacks definition. Check your lexicon for entry errors. ( See lexicon records)
N is not a valid index number. This is a command line error. ( See Indices).
No index number specified. This is a command line error. ( See Indices).
No reference shapeset specified. This is a command line error. ( See Reference Shapeset).
No standardized data file specified. This is a command line error. ( See Indices).
No such field as FIELDNAME. (Followed by list of fields in table). Reconcile the user order table with the structure of the user attribute table. ( See User Attribute Table).
No user address source specified. This is a command line error. ( See User Attribute Table).
Order flag not valid without -m flag. This is a command line error. ( See User Order Table).
Order table USER_ORDER_TABLE_NAME is empty. Needs data to be entered. ( See User Order Table).
Order table USER_ORDER_TABLE_NAME is unavailable. Check name, location and permissions for USER_ORDER_TABLE_NAME.dbf ( See User Order Table).
Ref data may not safely fit into buffer. This is a warning that the safety margin is breached. However, it might work out okay. If not, either reduce the length of the data in your reference attribute table fields or recompile PAGC increasing the BETA_BUF_SIZE.
Reference data exceeds Beta field size. Either reduce the length of the data in your reference attribute table fields or recompile PAGC increasing the BETA_FIELD_SIZE.
Reference data exceeds Beta buffer sizeEither reduce the length of the data in your reference attribute table fields or recompile PAGC increasing the BETA_BUF_SIZE.
REFERENCE_SHAPESET_NAME is already built. The files produced by the previous build must be deleted if you wish to rebuild.
REFERENCE_SHAPESET_NAME has no records. The table needs to be populated with records. ( See Reference Shapeset).
Rule file: Bad Input Token N at rule R. N is a number that should be the token number of an input token but is not. See list of input tokens. R is the rule number (in the file rules.txt) in which it appears. This rule must be corrected or deleted. ( See Rule Records)
Rule File: Non-Token N in Rule #R. Rule number R in the file rules.txt contains, among the numbers denoting output tokens, one which is not. See the list of output tokens. This rule must be corrected or deleted. ( See Rule Records)
schema error in SCHEMA_TABLE_NAME: missing field ATTRIB in schema. Add the missing field to your schema table. ( See Schema Table).
schema error in SCHEMA_TABLE_NAME: missing field COMPARE in schema. Add the missing field to your schema table. ( See Schema Table).
schema error in SCHEMA_TABLE_NAME row R field ATTRIB: ATTRIBUTE is duplicated. Check the value in the schema table row and field given. ( See Schema Table).
schema error in SCHEMA_TABLE_NAME row R field ATTRIB: ATTRIBUTE is error. Check the value in the schema table row and field given. ( See Schema Table).
schema error in SCHEMA_TABLE_NAME row R field COMPARE: COMPARISON_TYPE is error. . Check the value in the schema table row and field given. ( See Schema Table).
schema error in SCHEMA_TABLE_NAME COLUMN_NAME is missing. Check the columns in your schema table and ensure that all are present. ( See Schema Table).
Schema error in SCHEMA_TABLE_NAME row R : wrong number of fields for comparison. Comparison type T needs N fields. And this was field X. Correct your schema table at row R. ( See Schema Table).
Schema error in SCHEMA_TABLE_NAME row R : wrong number of fields for comparison. Comparison type T needs N fields. And this was field X. . Correct your schema table at row R. ( See Schema Table).
schema error in SCHEMA_TABLE_NAME row R : wrong number of fields for comparison. Comparison type T needs N fields. And this was field X. . Correct your schema table at row R. ( See Schema Table).
schema error: CHAR_LEFT_RIGHT comparison for non-macro attribute ATTRIUTE in row R.. Check the value in the schema table row and field given. ( See Schema Table).
schema error: NUMBER comparison for non-HOUSE attribute ATTRIUTE in row R.. Check the value in the schema table row and field given. ( See Schema Table).
schema error: POSTAL comparison for non-postal attribute ATTRIUTE in row R.. Check the value in the schema table row and field given. ( See Schema Table).
schema error: weight N in row R out of range. Correct the weight noted to fall between 0 and 1. ( See Schema Table).
Schema flag not valid without -b flag. This is a command line error. ( See Schema Table).
Schema-specified field FIELDNAME not in reference table. Check the field names given in the Schema table against those in the reference attribute table. ( See Schema Table).
Statistics flag not valid without -b flag. This is a command line error. ( See the Statistics file).
Unsupported comparison type. Check the comparison type given in the schema table for the HOUSE attribute. ( See Schema Table).
Unsupported split field for STRING. Split fields supported only for the POSTAL attribute. Correct this row in the user order table ( See User Order Table).
USER_ATTRIBUTE_TABLE_NAME has no records. Add some records, why don't you? ( See User Attribute Table).
WORD is one too many lexemes. Check your input to the standardizer and shorten it.
WORD is way too long. Check your input to the standardizer and shorten it.