How to debug PAKTOTAM error?

timallen

timallen

Well Known Member
(OneWorld Xe XU7, SP22, E/S RS6000/AIX, Oracle 8.1.7)

I'm doing a full package for the Enterprise Server. The client package build went fine, but when I get to the E/S, I get an error-- specifically, PAKTOTAM gets an error when processing GBRSPEC. PAKTOTAM fails after about 15 minutes of processing. Here is the GBRSPEC.STS status log:

OneWorld paktotam Status Log
----------------------------
process id: 42380
copy status: S (stopped with error)
spec type: gbrspec

read count: 2447574
write count: 2447573
error count: 0

Here is the GBRPSPEC.TXT file that gets fed into PAKTOTAM:
SpecType=16
PackedLocation=/ow/jdedwardsoneworld/b7333/packages/DV7333F001/pack/
TargetLocation=/ow/jdedwardsoneworld/b7333/packages/DV7333F001/spec/
BuildType=F
StatusFile=/ow/jdedwardsoneworld/b7333/packages/DV7333F001/text/gbrspec.sts
StopOnError=N
RemoteCodeSet=1252
RemoteOSType=5
LocalCodeSet=1252
LocalOSType=3

But I can't find any error log to look at to determine what went wrong. What *could* go wrong, anyway? I mean, I'm pretty much just unzipping a compressed file, aren't I? Is there some workaround for this? Are there command line parameters for PAKTOTAM, or extra options for the GBRSPEC.TXT file? Can I just copy the GBRSPEC tam files over from the Deployment Server? I understand from some of the older messages that a procedure similar to this was used by some of the card wallopers in the old days before indoor plumbing ;)

Thanks in advance.
 
Tim,

does the created gbrspec.ddb file have exactly 1024x1024x1024 bytes (1Gb)?
In case, check if your AIX filesystem permits files bigger then 1G.

I think the command is "ulimit" run as the JDE user.

Thanks, Gerd
 
Gerd, you are one smart CNC. The file size is exactly 1GB. We had the limits set too low. I was able to reset the upper limit for the jde user using smit to unlimited (-1). Now to see if the build can be done! Thanks. -tim
 
Maybe not that smart, but I have been around awhile and seen a lot of sssstuff.
Brazilians call that "macaco velho".

I would set the limit to "unlimited" for JDE. You will be safe for ERP9 and all updates to come. Your package will work now, I am sure.

Cheers, Gerd
 
Macaco velho ?

This is my boss... :)

Regards,
Adriano

a lot of sssstuff.
fe for ERP9 and all updates to come. Your package will work no
w, I am sure.
Cat=&Board=OW&Number=59867

Abraços,
Adriano Atanasio
Consultor de Tecnologia


---
Acabe com aquelas janelinhas que pulam na sua tela.
AntiPop-up UOL - É grátis!
http://antipopup.uol.com.
 
Gerd,
The build went perfectly-- here are the numbers:
GBRSPEC.DDB - 1.191.133.155 (1,1GB!)
GBRSPEC.XDB - 225.547.264
So I was *just* overrunning the 1GB limit. Ah well, if that hadn't happened I wouldn't have learned a useful lesson.

BTW, on the RS6000, the GBRSPEC processing took just 40 minutes-- pretty good.

Thanks again, you saved the day, macaco velho. Oddly enough, I don't know that the Spanish have a term like this-- perhaps because here experience is not regarded as highly as youth (and willingness to work cheaply ;) ) -tim
 
Back
Top