We are currently deploying a new user interface and navigational structure on our Community. These design changes align with our new Teradata Access portal and provide a more cohesive experience for our users.
I have asked this before, but have never received an answer. So, I will try again.
Our production load jobs are abending with this message:
**** 23:13:34 UTY4015 Access module error '34' received during 'read' operation on record number '5789498': 'pmunxRBuf: fread error (Invalid argument)'
What is causing this to occur? When I restart the job, it will sometime complete successfully, with no changes being made, or it abends with a different record being flagged. This is large file 6+ million recs, but this error seems to randomly appear. Is it space related? Server space issues? Is this a Teradata issue?
What can I do to prevent this error from happening in the future?