Did you just apply SP 19....Take a look at this document from Customer Connection (aka The Knowledge Garden)
Package Build Errors on GBRSPEC count after Service Pack 19
Details: Title: Package Build Errors on GBRSPEC count after Service Pack 19
------------------------------------------------------------------
Abstract: This document outlines an error that is reported on GBRSPEC duirng the build of a full client and server build after upgrading to Service Pack 19. The R9621 and R9622 package build reports will report that the package build ended in error due to a mismatch in the number of GBRSPEC's read and written.
Symptoms
Due to a restriction in how TAM files are handled (we can only read TAM files that are less than 2Gb in size), the way that the GBRSPEC tam files are created for use on enterprise servers had to be re-evaluated.
Prior to service pack 19, the package build process packs ALL records from the F98741 table for transfer to the Enterprise server. With effect from SP19, the gbrpsec.pak file that is created will filter out any gbrspec records that are not necessary for the enterprise server (i.e. you do not need APPL type records as you cannot run interactive applications on the server). This will ensure that the server-side GBRSPEC file will only have records for Table conversions and UBEs, therefore the GBRSPEC will be considerably smaller.
The RDB count for GBRSPEC will not match the attempted or succeeded count and this will trigger an error status on the R9622 server package build report and also the R9621 client package build report.
You will also notice the following new entries in the builderror.txt file from the moment any F98741 record has the field esfful populated (when a new report is checked in on SP19 or when an ESU that was built on SP19 is installed against the environment):
====================================
Begin of builderror.txt
====================================
Spec file GBRSPEC begun.
1 RDB record count in GBRSPEC : 2657127
Number of RDA records Packed: 173
Number of TC records Packed: 0
Number of Blank records Packed: 2656954
Number of FDA records NOT Packed : 0
Number of WF records NOT Packed: 0
Number of NER records NOT Packed: 0
Number of TER records NOT Packed: 0
Number of TAM records fetched: 2657127.
Number of TAMAdds Attempted: 2657127.
Number of TAMAdds succeeded: 2657127 failed: 0.
Number of records TAM says it has: 2657127.
Number of PAK records fetched: 2657127.
Number of PAK Adds Attempted: 2657127.
Number of PAK Adds succeeded: 2657127 failed: 0.
For server GBRSPEC, the RDB count will not match the attempted or succeeded count.
The Attempted and Succeeded count should match.
Only UBE and Table Conversion records get written to the pack table.
Also, the number of records Read and Written will not match in the history application because of only building UBE and RDA records.
Creating Indexes for table GBRSPEC.
Finished creating Indexes for table GBRSPEC.
Spec file GBRSPEC finished.
======================================
End of builderror.txt
======================================
The blank records refer to the number of F98741 table records that have no value in the essful field and therefore the build process cannot determine whether they should be filtered out or not. As the process cannot be sure they are automatically included.
Resolution
The package build RDB count validation process had been modified in service pack 20 to be aligned with the way that GBRSPEC is packed on service pack 19 and greater. This will ensure that the package build reports returns the correct status.
The server package can still be deployed if you are only getting errors on the package build process due to the GBRSPEC RDB count mismatch. Check the svrbuild.log, builderror.txt and buildlog.txt to verify that there are no other errors that could cause the package to report a "failed" status and deploy the server package.
If the client package is reporting an error due to the GBRSPEC count mismatch, modify the package_name.inf (located on the deployment server in the "package_inf" folder) to reflect that the build was "COMPLETED SUCCESSFULLY" and the package can then be deployed to the work stations.
Document ID: OTM-02-0026
Release: Xe
