Sage 100

 View Only

  • 1.  SY_TRANSLATEPVXTOSQL.PVC consistently errors in the same place on the log, when it hits what looks to be a 2 gig size limit

    Posted 03-02-2022 16:02
      |   view attached
    SY_TRANSLATEPVXTOSQL.PVC consistently errors in the same place on the log, when it hits what looks to be a 2 gig size limit

    Seems to be a 32bit 2gig limit to file allocation size.  Always stops at 2,097,152 KB, takes about 5 hours of conversion to get to this point.

    What are others doing to work around this?  We have a massive company converting from PVX to SQL and this has us at a standstill.

    ------------------------------
    Annette Egbert
    Acuity Solutions, LLC
    aegbert@acuitynv.com

    ------------------------------


  • 2.  RE: SY_TRANSLATEPVXTOSQL.PVC consistently errors in the same place on the log, when it hits what looks to be a 2 gig size limit

    Posted 03-02-2022 16:10
    I don't know this specific error, but did you run Rebuild Key Files / Rebuild Sort Files / Pre-Migration on the source data before starting?

    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------



  • 3.  RE: SY_TRANSLATEPVXTOSQL.PVC consistently errors in the same place on the log, when it hits what looks to be a 2 gig size limit

    Posted 03-02-2022 17:50
    Are you saying the log file itself, the one in MAS_XXX called "SQL Data Translation of XXX nn.log" is reaching 2 GB file limit? Or are you saying the pvx data file the log is pointing has reached that size?

    If the former it sounds like it's writing a ton of entries (probably errors) to the log file to reach that size. 2 thoughts:
    1. You could try migrating just that 1 company alone. I'm guessing same problem would occur though.
    2. Like Kevin said, run Rebuild Key Files on the pvx data file then migrate again. This is probably a good bet if a ton of errors are being logged.

    If the latter, it doesn't make sense because that problem was solved in v4.40. If you could send the START_UP file from \mas90\Home\ from both the Premium install and the non-Premium install source, I could verify it has the line necessary to support segmented files once the 2GB (technically it's 1.8 GB file) limit is reached.

    ------------------------------
    Alnoor Cassim

    Email: alnoor@asifocus.com
    Ph: 949-689-9887
    Orange County, CA
    ------------------------------

    Original Message


  • 4.  RE: SY_TRANSLATEPVXTOSQL.PVC consistently errors in the same place on the log, when it hits what looks to be a 2 gig size limit

    Posted 03-04-2022 11:05
    Hi Alnoor,
    We spent over 12 hours on the IM rebuild alone.  We rebuilt all modules.  Obviously a good idea.
    Remigrated again.
    Last night we were finally able to start the conversion again.  Same error SY_Translatepvstosql.pvc. The file "Data Translation to XXX001.log" size was 2,097,152.
    Restarted again for kicks and giggles.  
    Same error SY_Translatepvstosql.pvc. The file "Data Translation to XXX002.log" size was 2,097,152
    I am uploading the START_UP from each install as requested.
    Thanks,
    Annette

    ------------------------------
    Annette Egbert
    Acuity Solutions, LLC
    ------------------------------

    Original Message


  • 5.  RE: SY_TRANSLATEPVXTOSQL.PVC consistently errors in the same place on the log, when it hits what looks to be a 2 gig size limit

    Posted 03-04-2022 12:09
    Edited by Alnoor Cassim 03-04-2022 12:10
    @Annette Egbert - Got it. Thanks for the detail! I'm thinking your START_UP programs will be fine. Assuming that's the case, here is what I would do if it were me. Contact me privately if you want me to do this for you​.

    Modify the SY_TRANSLATEPVXTOSQL.pvc to:
    * Auto-create a new log file every time it writes say 100,00 entries. This way it will never reach 2Gb size.
    * Have it not run the Compare  / Verify routine to save some time. I've done this before having felt confident the SQL tables were being written correctly. Has nothing do with log files just speeds up things.

    Alternatively we could just have it stop in the middle of writing to the log just to see why is it writing so many entries. That's probably the 1st thing I would do infact.

    ------------------------------
    Alnoor Cassim

    Email: alnoor@asifocus.com
    Ph: 949-689-9887
    Orange County, CA
    ------------------------------

    Original Message


  • 6.  RE: SY_TRANSLATEPVXTOSQL.PVC consistently errors in the same place on the log, when it hits what looks to be a 2 gig size limit

    Posted 03-02-2022 19:56
    Hi Kevin,
    I agree.  And though we did spot rebuilds on most trafficked modules, no we did not do complete rebuilds of all modules.  I started that shortly after your reply and have them still running.
    Thanks,
    Annette

    ------------------------------
    Annette Egbert
    Acuity Solutions, LLC
    ------------------------------

    Original Message


Related Content