Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Aloha item data corrupt

Status
Not open for further replies.

alphaomega73

Technical User
Aug 12, 2007
4
US
After repairing damage to the system after a crash, the only problem is this: It runs fine,all items are visible to the servers, but in Aloha manager the item maintenance tab is empty of items. The menu and submenu subtabs are also wrong, they show hilighted buttons in the right configuration but they have no words on them. So my menu works but cannot be changed.
 
I have, no change but I'll try one more time from a day much further back. I also have a couple of errors in debout.txt that may be related, can't tell. they are:

CheckCDX: DBF file ********* does not exist in the depot.
This occurs for 13 different files. And:

Mnt4x: ReadFile: file id 29 not recognized
Error 22004 reading file 29
 
A little extra info, this system had a major crash. I took the system home and it took 4 days to rebuild. I wiped data and newdata and loaded them with files from a day about 2 weeks before the crash. Its been stable except for the errors stated above.
 
Copy all .dbf's from a couple days ago, place them in the NEWDATA directory, delete all .cdx and .tdx files from the NEWDATA directory, open Aloha Manager or run DBCONFIG to rebuild new index files(.cdx & .tdx), run a refresh.
 
I agree with Bigbloks suggestion. Whenever I restore sales history to the working directory-which is a perfectly legitimate tactic to solve problems like yours-I generally do two things:

1) I go back a FEW days before the corruption, just to be safe.

2) I grab all the dbfs from that day. For one thing, the error can look like one dbf is the problem, when really it's a different one (i.e. the item.dbf, even though it's reporting the error, is probably not the problem here). And secondly, mixing data from different days is do-able... it's sort of asking for trouble, IMO.

btw, just curious-you said there was major crash.. did you have to reinstall the Aloha software, and if so, was it a different version than what was there previously?

 
The CPU fan failed causing lockups. The people on duty said "it was acting funny", by the time I got there it had been locking up and rebooting for an entire day nonstop. No they didn't shut it off to stop the damage even thou it was unusable (don't get me going there). I took the entire system to my house, new fan a clean-up and 4 days of file repairs got me to this point. I'll try your suggestions and let you know, I manage a retail outlet and do this on the side, so it will be a couple of days. Thanks
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top