Building full package, getting "Record Corrupt" error messages

Building full package, getting \"Record Corrupt\" error messages

Hello,
I am attempting to build a full package in OneWorld XE SP 23 on a new thick client. I am getting the following error messages in my BuildError log:

9/1/2006 14:52:28 0 Spec file GBRSPEC begun.
9/1/2006 14:52:28 0 RDB record count in GBRSPEC : 3359878
9/1/2006 14:52:34 8 TAM: Error Code 8, record is corrupt. See jde.log for more information.
9/1/2006 14:52:34 8 ERROR: Could not add record to GBRSPEC. Record: evseq: 239, esevsk: abdc17f1-b0a6-11d2-a13c-00105a1c00bb.

I am getting the following corresponding error in my jde.log:


1736/1580 Fri Sep 01 14:52:34 2006 JDETAM.C2062
tamfwrite: FAILED - The supplied user buffer is not valid for the requested operation. WinErrNum=1784. (\\sctpadep\b7333\pd7333\package\pd7333fa\spec\gbrspec.ddb)

I have tried to research these errors but haven't gotten very far.

I appreciate any help you can offer.

RE: Building full package, getting \"Record Corrupt\" error messages

You are building a Full Package on a Thick Client? Why? You should be
building it on the Deployment Server. This error looks like memory
problems. Not enough memory or hard drive space. Or maybe your drive
or page file is fraged.



Joy Fernandez, CNC System Administrator

Pedernales Electric Cooperative, Inc.

[email protected] <mailto:[email protected]>

830-868-5035

RE: Building full package, getting \"Record Corrupt\" error messages

Sorry for the confusion. I am running the full package build on a new thick client, but I am building it onto a deployment server.

I checked and the deployment server drive has plenty of free space.

Re: Building full package, getting \"Record Corrupt\" error messages

Hi Heather,

You can look up that hexadecimal string in the TAM specs using UTB to determine the object.

Search the Peoplesoft Online Support for solution 200783331 - you will find document OTM-01-0021 with instructions on how to do this.

Cheers,
JohnO

Re: Building full package, getting \"Record Corrupt\" error messages

I just wanted to note that I believe that deleting and recreating the SQLPKG QZDAPKG on our enterprise server fixed this issue.

Thanks for all your help.
Heather