PxPlus User Forum

Twitter Twitter Twitter

Author Topic: Odd Error 106  (Read 1082 times)

John Spencer

  • Member
  • **
  • Posts: 7
    • View Profile
Odd Error 106
« on: November 16, 2020, 12:03:20 PM »
Several times this year we have received an error 106 on a remove from a file and have reason to believe it is not hardware related as from our understanding to what an error 106 is. The file is a basic data file, external key size of 45 and defined record size of 512. The file is used during our payroll process, it has records written to it and then removed at the end of the process. The files has been in use for over 20 years in this process and I am sure has had millions and millions of records pass through it. We have not had an issue with it until this year.

Back in March of this year we had the error 106 on this file on a remove statement for the second time. At that time we ran the file rebuild utility on it. In the evening when no users were on the system, we completely removed the file from our system and defined it fresh in a different filesystem, there were no records in it at that time.

In May of this year it happened again, we took the same course of action as above.

In June we went through a system upgrade. We left the old physical hardware, upgraded to a Hyper-V virtual server, upgraded the operating system to Linux RedHat 7.6 and Pxplus v15.1

On 10/27 the error 106 returned in the same file in the same remove statement. Again, traditionally we would think this is hardware related but cannot see how that is possible based on it being the same file, having been redefined several times and now on a completely different platform.

Is there any insight that can be provided on why a file would be receiving an error 106 on a basic REMOVE (2,KEY=K$) that does not appear to be hardware related at all?

Thank you.

Mike King

  • Diamond Member
  • *****
  • Posts: 3811
  • Mike King
    • View Profile
    • BBSysco Consulting
Re: Odd Error 106
« Reply #1 on: November 17, 2020, 10:12:19 AM »
John,

Is it possible you are using a fairly large EFF file, if so the issue may be the shadow page caching is overflowing.  EFF files attempt to maintain prior images of page updates to handle file restoration in case a rollback is requested.  We have seen instances where this can cause problems if you update a significant number of records between forced commits.

If it is an EFF file and you are not using COMMIT/ROLLBACK logic we strongly suggest you switch to using a VLR file and enable the 'XK' system parameter,  Not only will this avoid the shadow page limitations, but processing speed will increase and often disc space usage will be reduced due to better key table utilization.  Your application logic itself will not be impacted unless you actually implemented COMMIT/ROLLBACK logic in your application.
Mike King
President - BBSysco Consulting
eMail: mike.king@bbsysco.com

John Spencer

  • Member
  • **
  • Posts: 7
    • View Profile
Re: Odd Error 106
« Reply #2 on: November 17, 2020, 06:35:03 PM »
Thank you very much Mike.

We will implement that change and see what happens.