Package Hang

[stevenlais]

Hi List,

Everytime I build a client package on the Deployment Server, the package will kind of hang or stop at updating parent package TAM file. All the spec file was successfully created.We had tried building ESU merged package and also some of our customized object but all faced the same problem.
Here is some sample of the BuildError log file:

Final size of spec files: count 34 size 2978648.
8/28/01 16:42:36 0 Check for compression Records.
8/28/01 16:42:37 0 Update Parent Package, PRODB733FC.
8/28/01 16:42:37 0 Create the backup directories under Parent Package, PRODB733FC.
8/28/01 16:42:37 0 Update Parent Package and Checkin location.
8/28/01 16:42:37 0 Copy bin32,obj and lib32 from Package Name directory to Parent directory.
8/28/01 16:42:37 0 Copy from \\JDEDEP\B733\PRODB733\package\JD11104CLI\ to \\JDEDEP\B733\PRODB733\package\PRODB733FC\.
8/28/01 16:42:37 0 Copy bin32,obj and lib32 from Package Name directory to Checkin location.
8/28/01 16:42:37 0 Copy from \\JDEDEP\B733\PRODB733\package\JD11104CLI\ to \\JDEDEP\B733\PRODB733\.
8/28/01 16:42:52 0 Build 'object' types from definition.
8/28/01 16:42:53 0 Updating parent package TAM file asvrhdr.
8/28/01 16:42:53 0 Updating parent package TAM file asvrdtl.
8/28/01 16:42:54 0 Updating parent package TAM file fdaspec.
8/28/01 16:46:58 0 Updating parent package TAM file fdatext.
8/28/01 16:48:20 0 Updating parent package TAM file jdeblc.
8/28/01 16:48:21 0 Updating parent package TAM file dstmpl.
8/28/01 16:48:22 0 Updating parent package TAM file smrttmpl.
8/28/01 16:48:22 0 Updating parent package TAM file gbrlink.
8/28/01 16:48:22 0 Updating parent package TAM file gbrspec.

Recently we had just upgraded to SP16 and I don't know whether the upgrade cause this problem.

Anyone had any idea to go around this ?

Thanks
Steven Lais
JDE One World B7332 SP16 Coexistence
AS400 V4R4 Win NT 4.0

 

[rgz]

I've seen this before on some sites. You'll need to rebuild your parent
package.

In the short term you have two options if you (desperately) need to get it
out before building a new parent package.
1. Build the update using a different parent package. FA, PA, or CRPB733FC
will work. I hope you understand the implications of this method.
2. Like you say, the package has built ok, it's just that the parent isn't
updated. You could SQL the F96021 to say it's completed successfully and
then deploy the update as normal.

Best advise is to rebuild the parent asap.

BTW... Forcing a package build to end can cause this hanging problem to
appear. I doubt the SP has anything to do with it.

 

[MSiebenschuh]

Ahhhhhh the joys of building packages. I had this exact problem. Spent 24
hours straight trying to figure it out with another poster - originally we
thought it had to do with the fact that it was the first parent package we
hadn't compressed. In the end it was a corrupt GBRSPEC in the parent
package. 2 solutions. First just build a new full package (probably the most
secure way to go) or second copy the GBRSPEC from a good client (we used one
of our Citrix servers) over to the deployment server. The second way is kind
of a hack and although that method got us through the day I still put out a
new full package the next day. If you have the time build a new full
package. Good luck.

Mark Siebenschuh
HP9000/Oracle 8.0.5/Base (distribution)/XE (financials)/lots of Citrix
servers