Database is currently being upgraded (Yes, another thread)

SOLVED

Good day folks,

I'm experiencing the error message in the subject line and after doing some forum research I found this thread which is pretty much the exact same issue I'm having.  

I've looked up the instructions referenced in that thread and have them at hand. However i did have a question I wanted to run by the community first just in case it might be feasible.

I originally got this error on my new test system and had been somewhat focused there until I thought i would go and check the existing production system and see if it actually exists there as well. I found out that it does but I don't get the error when I open the Purchase Order section like I do in the test system. 

After searching, I found the POIVData files and took a look, there are two that are in the "in progress" state, however, there are two identical folders that reflect that they have been successfully upgraded. (Refer to the image to see what I'm talking about.) 

My question here is, would I be safe in just deleting those two "in progress" folders, performing the data migration again and see if that works? It's just a thought, I guess I'm just being lazy.  Big Smile

Parents
  • 0
    verified answer

    Hi Steven,

    The hilighted folders are not being actively used by the software and can likely be safely removed.  Just to be safe I would recommend keeping a backup around for a period of time just in case, but the POIVData folder is where the active data related to Purchasing and Inventory resides within each company data folder.

    When a data upgrade is initiated within PO or IV, this POIVData folder is renamed to 0000xPOIV, where x is a numerically incremented value, an empty set of baseline data files (.DAT files) are then created within a brand new instance of the POIVData folder and records are processed from the renamed 0000xPOIV folder into the new folder successively and alphabetically by file name.  After all files have been processed, the renamed folder is supposed to be deleted.  The folders you have highlighted appear to have been manually renamed by someone at some point in the past.

    Data upgrades are not always needed for POIVData with each version change.  There has been no database changes requiring a data upgrade between versions 9.8 and 13.1, and though a slight processing will take place with initial load of the 14.1 version, there is currently no full data upgrade planned at that stage either.

    If you have upgraded from a version prior to 9.8, be sure that you initiate the data upgrade of POIVData while at the file server, and not from a workstation.

    Hope that helps, and it may be a good idea to call into support and speak with a PO/IV analyst for more information or for more details that are specific to your scenario.

    Scott Haines

    Customer Care CS Specialist, Construction & Real Estate Solutions

    Sage Business Solutions

  • 0 in reply to Scott H.

    Thanks for the input Scott.

    I'll still call in but it sounds like what i'm thinking will work. Those two folders (that I'll back up) are whats holding up our migration. Since those other two are identical, it should work if I remove those two that were "in progress" perform the migration again and see what that does on a fresh system.

  • 0 in reply to StevenHulse
    SUGGESTED

    No problem Steven, I'm happy to help.

    Those two folders aren't actually causing the error message when opening PO.  In fact, the application is completely ignoring those two folders altogether because the have been renamed.

    Re-migrating the data will likely resolve the issue though, unless you are upgrading from a version prior to 9.8.

    One additional detail about data upgrades for Purchasing and Inventory is a file located in the POIVData folder named db.ver.  This file is viewable with any text editor, and normally will contain the current version of the data.  Whenever PO or IV are opened, this file is scanned to compare its contents with the currently installed version in order to determine whether or not a data upgrade should take place.  When a data upgrade is initiated, the contents of this file are modified to indicate that the upgrade is in process, and then when the upgrade is compeleted it populates the file with the appropriate data version.

    The error you are seeing is most likely due to the fact that a data upgrade was initiated but never completed, and this file likely contains text indicating who initiated the data upgrade and when.  Manually modifying the contents of this file is sometimes appropriate, but it is best to have an analyst take a look to make that determination, as each case is unique.  Removal of that file and then opening PO at the server will also force a prompt for data upgrade, and will populate the file with the appropriate information after the upgrade is complete, but sometimes data upgrades can be lengthy so if you have not upgraded from a version prior to 9.8 it will likely save considerable time to have someone take a look.

    Please let me know if you have any questions or if I can be of further assitance.

    Scott Haines

    Customer Care CS Specialist, Construction & Real Estate Solutions

    Sage Business Solutions

  • 0 in reply to Scott H.

    Yea, we're going from v9.7 to v13.1. The odd thing is that there are two folders, one (the renamed one thats highlighted) contains a db.ver file that shows it's in the middle of upgrading and says who initiated it. The other one shows it was successfully upgraded. This is where it seemed odd to me and the thought of removing the renamed folder might resolve it.

Reply
  • 0 in reply to Scott H.

    Yea, we're going from v9.7 to v13.1. The odd thing is that there are two folders, one (the renamed one thats highlighted) contains a db.ver file that shows it's in the middle of upgrading and says who initiated it. The other one shows it was successfully upgraded. This is where it seemed odd to me and the thought of removing the renamed folder might resolve it.

Children
No Data