Database errors: Difference between revisions

From EnablerWiki
Jump to navigationJump to search
← Older editNewer edit →

Trevor (talk | contribs)

2 user groups
526 edits
mNo edit summary
No edit summary
Line 1: Line 1:
Created: 24 November 2008. Last Reviewed: 24 November 2008
Created: 24 November 2008. Last Reviewed: 24 April 2009


Need to determine whether the database (.dbf) or the index (.mdx) is corrupt:


# Look for dbf and .mdx
Database errors in Enabler, although not common, can occur for a variety of reasons. Below are some sample errors with suggested resolutions. With all database errors, unless you are 100% sure of the method for fixing the problem, it is strongly recommended that you contact Magenta Retail for assistance before proceeding.
# If no .mdx, find out what the file is
# Close all Enabler applications including Nibbler
# Delete bu-param.mdx (index)
# Re-index bu-param (x:\enabler>'''infoctrl indexlocal bu-param''')
# If the .mdx is created and no errors then all is okay
# If Database error re-occurs then the .dbf is corrupt
# If \enabler\local replace from another machine OR if \enabler\lantran retrieve from backup or discuss


'''<nowiki>--------------------------------------</nowiki>'''
= Database Error – Read Failure =
[[Image:]]


'''Type: Database Error'''
Need to determine whether the database (.dbf) or the index (.mdx) is corrupt:  


'''Date: 20060313'''
# Close all Enabler applications including Nibbler
# Delete the index relating to the error. In the above sample this is c:\enabler\local\posdiv.mdx.
# Re-index the database that experienced the error. In the above sample this is c:\enabler\local\posdiv.dbf so the reindex command would be c:\enabler>'''infoctrl indexlocal posdiv''')
# Start POS again.
# If Database error re-occurs then most likely the .dbf is corrupt.
# If the database is in the LOCAL folder, refer to “Enabler Database Files – LOCAL” for information about replacing or recovering the file.If the database is in the LANTRAN folder, refer to “Enabler Database Files – LANTRAN” for information about replacing or recovering the file. If the database is in the LANMNT folder, refer to “Enabler Database Files – LANMNT” for information about replacing or recovering the file. If unsure, please contact Magenta Retail for further advice.


'''Time: 13:38:27'''
= Required Database Missing =
While a missing index can often be corrected by Enabler automatically reindexing the database for the missing index, which re-creates the index, a missing database file cannot be repaired automatically in most cases.


'''Logical Address: 030501'''
[[Image:]]


'''Version: 04.29.13'''


'''help_idx: 0'''
To determine the best course of action, refer to the suggestions below.




'''Unable to open file'''
* If the database is in the LOCAL folder, refer to “Enabler Database Files – LOCAL” for information about replacing or recovering the file.
* If the database is in the LANTRAN folder, refer to “Enabler Database Files – LANTRAN” for information about replacing or recovering the file.
* If the database is in the LANMNT folder, refer to “Enabler Database Files – LANMNT” for information about replacing or recovering the file. If unsure, please contact Magenta Retail for further advice.


'''Function:DbaseTable :: use ()'''
= Unknown fieldname =
An unknown fieldname error message indicates an incompatibility between the database structures and the fields that Enabler is expecting to see in the database. This could occur if problems happened with an Enabler upgrade, or if a file was replaced from a different version of Enabler.


'''Message:Corrupt table/index header.'''
[[Image:]]


'''Filename:d:\enabler\local\bu-param.DBF'''
The first check to be done is to ensure every till in the store is on the same version of Enabler. They aren’t then all tills should be upgraded to the same version. The store server must ALWAYS be on the same or a higher version of Enabler as the tills.


'''Indexname:d:\enabler\local\bu-param.MDX'''
If all tills are on the same version, in most cases the error can be fixed by performing a migrate. The command for this would be:-


'''Database:LOCAL'''
Infoctrl migrate


'''Error Code:8961'''
which needs to be run from a command prompt in the folder where Enabler is installed, which in the above example would be c:\enabler. Ensure that all Enabler applications are closed before running this command.


'''Open:0'''


'''DBF:1'''
= Number is out of range =
A “Number is out of range” message will likely have a similar cause to the “Unknown Fieldname” message, and can often occur immediately after the “Unknown Fieldname” error.


'''PDX:0'''
[[Image:]]


'''Openmode:1'''
The first check to be done is to ensure every till in the store is on the same version of Enabler. They aren’t then all tills should be upgraded to the same version. The store server must ALWAYS be on the same or a higher version of Enabler as the tills.


'''Sharemode:1'''
If all tills are on the same version, in most cases the error can be fixed by performing a migrate. The command for this would be:-


'''Data Item 1:Trace 1: 19980114, 648'''
Infoctrl migrate


'''Trace 2: 19980114, 648'''
which needs to be run from a command prompt in the folder where Enabler is installed, which in the above example would be c:\enabler. Ensure that all Enabler applications are closed before running this command.


'''Trace 3: 19980114, 262'''
= See Also =
Enabler Database Files – LANMNT


'''Trace 4: 0, 0'''
Enabler Database Files – LANTRAN


Enabler Database Files – LOCAL


Need to determine whether the database (.dbf) or the index (.mdx) is corrupt. Please note that this error is occurring on the till (node) but it is the store server that has the corruption.


# Delete repairs.mdx (index)
Retrieved from "[http://192.168.2.6/wiki/index.php/Database_errors http://192.168.2.6/wiki/index.php/Database_errors]"
# Re-index repairs (x:\enabler>'''infoctrl indexlantran repairs''')
# If the .mdx is created and no errors then all is okay
# If Database error re-occurs then the .dbf is corrupt
# If \enabler\local replace from another machine OR if \enabler\lantran retrieve from backup or discuss.
# If lantran, and after discussion, replace with empty from upgbase and perform migrate (x:\enabler>infoctrl migrate)


'''<nowiki>--------------------------------------</nowiki>'''
Views[[Image:]][[Image:]][[Image:]][[Image:]][[Image:]][[Image:]]
 
'''Type: Database Error'''
 
'''Date: 20060207'''
 
'''Time: 14:59:59'''
 
'''Logical Address: 014002'''
 
'''Version: 04.27.00'''
 
'''help_idx: 0'''
 
 
'''Unable to open file'''
 
'''Function:DbaseTable :: use ()'''
 
'''Message:Corrupt file - other than header.'''
 
'''Filename:\\GOD-014001\enserver\enabler\lantran\repairs.DBF'''
 
'''Indexname:\\GOD-014001\enserver\enabler\lantran\repairs.MDX'''
 
'''Database:LANTRAN'''
 
'''Error Code:8962'''
 
'''Open:0'''
 
'''DBF:1'''
 
'''PDX:0'''
 
'''Openmode:0'''
 
'''Sharemode:0'''
 
'''Data Item 1:Trace 1: 20031030, 1'''
 
'''Trace 2: 20031030, 1'''
 
'''Trace 3: 19980114, 667'''
 
 
'''Message: Number is out of range'''
 
'''Filename: [//possrv/enserver/enabler/local/POSPROD.DBF \\possrv\enserver\enabler\local\POSPROD.DBF]
 
'''Indexname: [//possrv/ensever/enabler/local/POSPROD.MDX \\possrv\ensever\enabler\local\POSPROD.MDX]
 
 
Number out of range means data doesn’t fit
 
1. Check the version is the same an all machines
 
2. If the version is the same perform steps below.
 
3. If not upgrade machines to same versions and ensure upgrade applies fully.
 
4. If upgrade applied recently it may not have fully applied.
 
5. Reboot
 
6. Migrate
 
7. Re-index
 
 
'''Message: Table is read only'''
 
'''Filename: [//ct/enserver/enabler/lanmnt/comflg.DBF \\ct\enserver\enabler\lanmnt\comflg.DBF]
 
'''Indexname: [//ct/enserver/enabler/lanmnt/comflg.MDX \\ct\enserver\enabler\lanmnt\comflg.MDX]
 
 
Replace comflg.DBF with copy located in upgrade file.
 
 
'''Missing Database'''
 
'''d:\enabler\lantran\salesum3.DBF'''
 
 
# Look for salesum3.DBF and salesum3.MDX
# Reindex to create .MDX that is missing
# What is contained in file?
# Replace .DBF from upgbase
# Reindex and Migrate
 
'''No associated index.'''
 
'''d:\enabler\lantran\taxhist.DBF'''
 
'''d:\enabler\lantran\taxhist.MDX'''
 
 
# Close Nibbler
# Delete taxhist.MDX
# Reindex
# If file not created or locked, reboot.

Revision as of 06:24, 24 April 2009

Created: 24 November 2008. Last Reviewed: 24 April 2009


Database errors in Enabler, although not common, can occur for a variety of reasons. Below are some sample errors with suggested resolutions. With all database errors, unless you are 100% sure of the method for fixing the problem, it is strongly recommended that you contact Magenta Retail for assistance before proceeding.

Database Error – Read Failure

[[Image:]]

Need to determine whether the database (.dbf) or the index (.mdx) is corrupt:

  1. Close all Enabler applications including Nibbler
  2. Delete the index relating to the error. In the above sample this is c:\enabler\local\posdiv.mdx.
  3. Re-index the database that experienced the error. In the above sample this is c:\enabler\local\posdiv.dbf so the reindex command would be c:\enabler>infoctrl indexlocal posdiv)
  4. Start POS again.
  5. If Database error re-occurs then most likely the .dbf is corrupt.
  6. If the database is in the LOCAL folder, refer to “Enabler Database Files – LOCAL” for information about replacing or recovering the file.If the database is in the LANTRAN folder, refer to “Enabler Database Files – LANTRAN” for information about replacing or recovering the file. If the database is in the LANMNT folder, refer to “Enabler Database Files – LANMNT” for information about replacing or recovering the file. If unsure, please contact Magenta Retail for further advice.

Required Database Missing

While a missing index can often be corrected by Enabler automatically reindexing the database for the missing index, which re-creates the index, a missing database file cannot be repaired automatically in most cases.

[[Image:]]


To determine the best course of action, refer to the suggestions below.


  • If the database is in the LOCAL folder, refer to “Enabler Database Files – LOCAL” for information about replacing or recovering the file.
  • If the database is in the LANTRAN folder, refer to “Enabler Database Files – LANTRAN” for information about replacing or recovering the file.
  • If the database is in the LANMNT folder, refer to “Enabler Database Files – LANMNT” for information about replacing or recovering the file. If unsure, please contact Magenta Retail for further advice.

Unknown fieldname

An unknown fieldname error message indicates an incompatibility between the database structures and the fields that Enabler is expecting to see in the database. This could occur if problems happened with an Enabler upgrade, or if a file was replaced from a different version of Enabler.

[[Image:]]

The first check to be done is to ensure every till in the store is on the same version of Enabler. They aren’t then all tills should be upgraded to the same version. The store server must ALWAYS be on the same or a higher version of Enabler as the tills.

If all tills are on the same version, in most cases the error can be fixed by performing a migrate. The command for this would be:-

Infoctrl migrate

which needs to be run from a command prompt in the folder where Enabler is installed, which in the above example would be c:\enabler. Ensure that all Enabler applications are closed before running this command.


Number is out of range

A “Number is out of range” message will likely have a similar cause to the “Unknown Fieldname” message, and can often occur immediately after the “Unknown Fieldname” error.

[[Image:]]

The first check to be done is to ensure every till in the store is on the same version of Enabler. They aren’t then all tills should be upgraded to the same version. The store server must ALWAYS be on the same or a higher version of Enabler as the tills.

If all tills are on the same version, in most cases the error can be fixed by performing a migrate. The command for this would be:-

Infoctrl migrate

which needs to be run from a command prompt in the folder where Enabler is installed, which in the above example would be c:\enabler. Ensure that all Enabler applications are closed before running this command.

See Also

Enabler Database Files – LANMNT

Enabler Database Files – LANTRAN

Enabler Database Files – LOCAL


Retrieved from "http://192.168.2.6/wiki/index.php/Database_errors"

Views[[Image:]][[Image:]][[Image:]][[Image:]][[Image:]][[Image:]]

Retrieved from "https://theoracle.magentaretail.com.au/index.php?title=Database_errors&oldid=245"