Database errors - Revision history

Luke at 00:13, 30 July 2019

2019-07-30T00:13:34Z

← Older revision		Revision as of 00:13, 30 July 2019
Line 63:		Line 63:

	[[Anti-virus_software\|Anti Virus Software]]		[[Anti-virus_software\|Anti Virus Software]]


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

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

Trevor at 03:36, 14 January 2013

2013-01-14T03:36:43Z

← Older revision		Revision as of 03:36, 14 January 2013
Line 20:		Line 20:

	[[Image:Database_errors_Figure_2.jpg]]		[[Image:Database_errors_Figure_2.jpg]]


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

Trevor at 04:31, 16 March 2012

2012-03-16T04:31:04Z

← Older revision		Revision as of 04:31, 16 March 2012
Line 62:		Line 62:

	[[Enabler_Database_Files_-_LOCAL]]		[[Enabler_Database_Files_-_LOCAL]]

			[[Anti-virus_software\|Anti Virus Software]]

Trevor at 06:39, 24 April 2009

2009-04-24T06:39:24Z

← Older revision		Revision as of 06:39, 24 April 2009
Line 57:		Line 57:

	= See Also =		= See Also =
	[[~~Enabler Database Files – LANMNT~~]]		[[Enabler_Database_Files_-_LANMNT]]

	[[~~Enabler Database Files – LANTRAN~~]]		[[Enabler_Database_Files_-_LANTRAN]]

	[[~~Enabler Database Files – LOCAL~~]]		[[Enabler_Database_Files_-_LOCAL]]

Trevor at 06:35, 24 April 2009

2009-04-24T06:35:43Z

← Older revision		Revision as of 06:35, 24 April 2009
Line 57:		Line 57:

	= See Also =		= See Also =
	Enabler Database Files – LANMNT		[[Enabler Database Files – LANMNT]]

	Enabler Database Files – LANTRAN		[[Enabler Database Files – LANTRAN]]

	Enabler Database Files – LOCAL		[[Enabler Database Files – LOCAL]]

Trevor at 06:30, 24 April 2009

2009-04-24T06:30:57Z

← Older revision		Revision as of 06:30, 24 April 2009
Line 5:		Line 5:

	= Database Error – Read Failure =		= Database Error – Read Failure =
	[[Image:~~Database errors_Figure_1~~.jpg]]		[[Image:Database_errors_Figure_1.jpg]]

	Need to determine whether the database (.dbf) or the index (.mdx) is corrupt:		Need to determine whether the database (.dbf) or the index (.mdx) is corrupt:
Line 19:		Line 19:
	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.		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:~~Database errors_Figure_2~~.jpg]]		[[Image:Database_errors_Figure_2.jpg]]


Line 32:		Line 32:
	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.		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:~~Database errors_Figure_3~~.jpg]]		[[Image:Database_errors_Figure_3.jpg]]

	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.		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.
Line 46:		Line 46:
	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.		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:~~Database errors_Figure_4~~.jpg]]		[[Image:Database_errors_Figure_4.jpg]]

	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.		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.

Trevor at 06:28, 24 April 2009

2009-04-24T06:28:13Z

← Older revision		Revision as of 06:28, 24 April 2009
Line 5:		Line 5:

	= Database Error – Read Failure =		= Database Error – Read Failure =
	[[Image:]]		[[Image:Database errors_Figure_1.jpg]]

	Need to determine whether the database (.dbf) or the index (.mdx) is corrupt:		Need to determine whether the database (.dbf) or the index (.mdx) is corrupt:
Line 19:		Line 19:
	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.		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:]]		[[Image:Database errors_Figure_2.jpg]]


Line 32:		Line 32:
	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.		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:]]		[[Image:Database errors_Figure_3.jpg]]

	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.		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.
Line 46:		Line 46:
	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.		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:]]		[[Image:Database errors_Figure_4.jpg]]

	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.		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.

Trevor at 06:24, 24 April 2009

2009-04-24T06:24:32Z

Show changes

Trevor at 02:10, 22 April 2009

2009-04-22T02:10:04Z

← Older revision		Revision as of 02:10, 22 April 2009
Line 1:		Line 1:
			Created: 24 November 2008. Last Reviewed: 24 November 2008

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

Lucy: New page: Need to determine whether the database (.dbf) or the index (.mdx) is corrupt: # Look for dbf and .mdx # If no .mdx, find out what the file is # Close all Enabler applications including N...

2008-11-24T07:19:43Z

New page: Need to determine whether the database (.dbf) or the index (.mdx) is corrupt: # Look for dbf and .mdx # If no .mdx, find out what the file is # Close all Enabler applications including N...

New page

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

# Look for dbf and .mdx
# 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>'''

'''Type: Database Error'''

'''Date: 20060313'''

'''Time: 13:38:27'''

'''Logical Address: 030501'''

'''Version: 04.29.13'''

'''help_idx: 0'''

'''Unable to open file'''

'''Function:DbaseTable :: use ()'''

'''Message:Corrupt table/index header.'''

'''Filename:d:\enabler\local\bu-param.DBF'''

'''Indexname:d:\enabler\local\bu-param.MDX'''

'''Database:LOCAL'''

'''Error Code:8961'''

'''Open:0'''

'''DBF:1'''

'''PDX:0'''

'''Openmode:1'''

'''Sharemode:1'''

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

'''Trace 2: 19980114, 648'''

'''Trace 3: 19980114, 262'''

'''Trace 4: 0, 0'''

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)
# 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>'''

'''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.