File name reference guide

[lesliekirk]

Is there any sort of file name reference guide to help me decipher a few file names and potentially figure out if the can be safely thrown away.

affsess.dbf00000009
aff_sid.mvx0000003F
aff_cod.mvx0000003F

There are 13 GB worth of iterations of these files with another 2 GB in the not saved version of the file.

The store owner hasn't been able to pack the store in years. What started out as a 504 Gateway Timeout error, when the host investigated they said "It just ends abruptly" (and provided some other data with it). Now if the pack is attempted it winds up in a 500 error.

I want to guess that these are some sort of Affiliate Sessions?

[Kent Multer]

The ".dbf" and ".mvx" extensions are used for the old type of database files that Miva Merchant used in version 4 and earlier. I think the newer versions still use a few of these files. But .. how old is this store? What version of Merchant is it running?

I think the files with all those digits at the end of the extension are temporary ones that the store created while packing (or attempting to pack) the databases. If you look at the creation dates, I bet you'll find that most of them are quite old, left-overs from previous timeouts, and can be deleted without causing any problems.

(But just to be clear, I must admit that I'm only about 99.9% certain about the above.)

[ILoveHostasaurus]

Leslie, the time is soon approaching where such stores become incompatible with continuing service. We're talking about software that was released 15 years ago and where countless changes in web application security and encryption have occurred since that era. Support of any type for versions older than 9 has been discontinued.

[lesliekirk]

The ".dbf" and ".mvx" extensions are used for the old type of database files that Miva Merchant used in version 4 and earlier. I think the newer versions still use a few of these files. But .. how old is this store? What version of Merchant is it running?

I think the files with all those digits at the end of the extension are temporary ones that the store created while packing (or attempting to pack) the databases. If you look at the creation dates, I bet you'll find that most of them are quite old, left-overs from previous timeouts, and can be deleted without causing any problems.

(But just to be clear, I must admit that I'm only about 99.9% certain about the above.)

Understood - that's why I posted in the Miva Merchant 4 and Older forum. The store is an uncompiled v4.12 - talk about a trip back in time. It's got some of Luray's stuff in it and some really interesting Copernicus modules.

Once I was able to access the admin (I had just been looking at files via FTP) I looked at the OpenMaintenance™AffiliateSession and it shows 3552539 records in the Merchant2/00000001/affsess.dbf file. When I try to pack that file using the OpenMaintenance™I get a 500 Error. I did go back in look at the files via FTP and I do see files with the time stamp around the time of my attempts. Just to confirm, I can I delete those "attempt" files. YAAY! That's what I thought I remembered could be done.


ILoveHostasaurus - I understand what you are saying. I'm trying to help clean up this older site the best I can. I know that Miva doesn't support this far back (and the site isn't hosted with them). I don't know what lies in the future for this particular store but I'd hope that maybe, just maybe, a store that has been using Miva for 15 plus years might get a little love, encouragement and help so that maybe it can move forward.

[ILoveHostasaurus]

I understand what you are saying. I'm trying to help clean up this older site the best I can. I know that Miva doesn't support this far back (and the site isn't hosted with them). I don't know what lies in the future for this particular store but I'd hope that maybe, just maybe, a store that has been using Miva for 15 plus years might get a little love, encouragement and help so that maybe it can move forward.

Supporting that store, by you, Miva, or any third party, is doing any customer of that store a great disservice. That software has encryption capabilities somewhere between none and what was current fifteen years ago; it is not secure and not protecting the data of those customers. It has no auditing, logging, or any other security-related feature that has come about in the past 15 years. It needs to be taken offline.