E1: PKG: Update Package Errors Reaching a Spec Database Size Limit - PKGMSC0012 / PKGSPC0003 Failed to Attach / Create Spec Repository Errors
(Doc ID 758526.1)
Last updated on JULY 17, 2017
Applies to:JD Edwards EnterpriseOne Tools - Version 8.98 and later
Information in this document applies to any platform.
In this case here, customer on EnterpriseOne 8.12 TR 22.214.171.124.
Recently when building update packages for their DV812 pathcode, customer found the following errors on the Client package build log file - ClientPkgBuild.log:
Wed Dec 10 16:41:00 - pkgSpec.cpp:277 PKGSPC0003 ERROR: Failed to create spec repository on the build machine.
When looking into the error, it appears that the issue may be caused by the Full Parent Package that the update package is based on, the spec database file reaching its limit of 4 GB.
For the parent package (in this case, Package Name DV150908F) under its /pkgspec folder, the spec database files sizes are 4,098 MB for the SPEC_DV150908F.mdf data file and 11 MB for the SPEC_DV150908F.ldf for the log file.
As customer is running Tools Release 126.96.36.199, they have on their deployment server and web development clients a full copy of the MS SQL 2005 EE(Enterprise Edition) database system installed. However, as the database file size is limited to 4 GB in size, it seems that spec database on our deployment server for this full/parent package has reached its limit.
Is there a way customer can find out what has caused the spec database for this full package build (DV120908F) to reach the limit of the database size that is supported under MS SQL 2005 EE?
Are there are workarounds customer can apply to prevent a spec database from hitting the datasize limit of MS SQL 2005 EE? What impact on their JDE EnterpriseOne system will this type of error will cause?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document