Specifications

Chapter 6: Programming
Tests and Error Messages
Page 6-16 Mitel
®
5000 Installation Manual – Issue 3.0, October 2008
Enumerations
Each enumeration field has a set of values that are valid. An error is detected if the field has a
value that is out of this range. For a summary of possible error messages, see Ta bl e 6-5 .
Extension Conflicts
This test checks for extension conflicts. For a summary of possible error messages, see
Table 6-6.
Table 6-5. DB Test and Repair Error Messages for Enumerations
Error Message Indication
Invalid table <table name> This is only a warning. It indicates that it was
looking for a table named, but could not find it in the
database. This can happen if a new table is added
in a later version of a major release. If the test is
being run on the older version, this warning will
appear. For example, if Table A was added in v1.1,
running this test on databases previous to v1.1 will
produce a warning that Table A could not be found.
Invalid column <table name>:<column
name>
This is only a warning. It indicates that it was
looking for a column named, but could not find it in
the database. This can happen if a new column is
added in a later version of a major release. If the
test is being run on the older version, this warning
will appear. For example, if Column A was added in
v1.1, running this test on databases previous to v1.1
will produce a warning that Column A could not be
found.
<table name>/<column name> contains
an invalid enumeration value [<invalid
value>]
The table has an incorrect value in the indicated
column. This corruption is repaired by changing the
field to a correct value. The Repair Status will be
Value Set to <value> where <value> is the new
contents for the field.
Table 6-6. DB Test and Repair Error Messages for Extension Conflicts
Error Message Indication
Found blank extension, device type
<device type>
In this case, a device was found with a blank
extension. The extension is changed to P#XXX
where XXX can be from 000 to 999. The Repair
Status will be Set to Extension <new extension>.
Found conflict with extension
<extension number>, device types
<device type 1>, <device type 2>
Two devices have the same extension number, and
the two device types are not compatible. This
corruption is repaired by changing the extension
number of the second device <device type 2> to
P#XXX where XXX can be from 000 to 999. The
Repair Status will be Set to Extension <new
extension>. Only 1000 extension conflicts can be
resolved at a time because there are only 1000
possible extensions in the P#XXX framework.
Therefore, starting at the 1001 extension, the
Repair Status shows Not Repaired. Once an
extension is set to P#XXX, you can go into DB
Programming and change the extension to a valid
number.