• Welcome to the upgraded JDELIST forum and thank you for your patience.
    Please restrict discussions and issues regarding the new forum software to the Off Topic forum. We will be monitoring that forum for issues.
    If you have trouble logging in, please reset your password using the forgotten password form: https://www.jdelist.com/community/index.php?lost-password/
    If you are unable to successfully reset your password, please contact us: Click here!
    We hope that you enjoy the upgraded forum.
  • Introducing Dark Mode! Switch by clicking on the lightbulb icon next to Search or by clicking on Default style at the bottom left of the page!

Unable to check out P4310

sunnyind

Member
Hi List,

This is a problem related to ERP 9 with Update 0 and SP2 and oneoff C1. The environment is on Win 2K server with Oracle 9i (9.2.0.4)

I am able to check out most of the vanila objects but not the P4310.
Its very strange the jde.log is clean. I have attached the jdedebug.log from the point of check out.

It would be very kind of you to take a look at it and help me.

Thanks a million times for your help.
 

Attachments

It looks to me like your specs are hosed on the server for that object.

OMWSpecFetch() failed for the table JDESPECTYPE_GBRSPEC, in the data source, , location, JDESPECLOC_LOCALUSER, with the JdeSpec error of, Specified record does not exist!.

I'm not sure if the fix is the same for ERP9 as it was with XE, but on XE we would build a new full package. I know that you can just build a package for the GBRSPEC file, but a full would clear up any other issues that may be looming out there.
 

sunnyind

Member
Dan,

thanks for your responce.
I am not too sure..why but inspite of the same message (OMWSpecFetch() failed for the table ....) i am able to check out the P4210.

Attached is the log for the same.

Thanks a million times once again.
 

Attachments

sunnyind

Member
Hi,

Adding some more light to the issue..

W4310J (media object form) is the form ..where i guess the error could come as

From the OMW log

Log Seq :- 29
Log Data Item :- 129S (Memory allocation error)
upon double clicking the entry "Memory allocation failure for DSTR in ."

In the JDEDEBUG.log (attached in my earlier post)

Jan 29 15:54:20.375 - 2176/1316 SELECT COUNT(*) FROM DV9.F98743 WHERE ( DTOBNM = 'W4310J' )
Jan 29 15:54:20.375 - 2176/1316 ORACLE DBFetch: Invoke OCI Fetch fetchNumRows = 1
Jan 29 15:54:20.375 - 2176/1316 SpecEncapsulation : jdeSpecSelectKeyed completed OK.
Jan 29 15:54:20.375 - 2176/1316 Entering JDB_InsertTable(Table F98211)
Jan 29 15:54:20.375 - 2176/1316 ORACLE DBRsetReq conn=073129E8 requ=0C5C18A0 AGRE (AGRJDE)
Jan 29 15:54:20.375 - 2176/1316 INSERT INTO SY9.F98211 (LDLOGKEY, LDLOGSEQ, LDOMWLDTAI, LDOMWLDATA, LDOMWDFS1, LDOMWDFS2, LDOMWDFS3, LDOMWDFD1, LDOMWDFD2, LDOMWDFD3, LDOMWDFN1, LDOMWDFN2, LDOMWDFN3, LDPID, LDMKEY, LDUSER, LDUPMJ, LDUPMT, LDTIMEZONES, LDDSAVNAME) VALUES ('5a9e9593-8f6e-484e-a842-b765e3a4fc25',2,'154C','W4310J|',' ',' ',' ',0,0,0,0.000000,0.000000,0.000000,'P98220','ROHITN','NS1',104029,155420.000000,' ',' ')
Jan 29 15:54:20.375 - 2176/1316 Exiting JDB_InsertTable with Success(Table F98211)
Jan 29 15:54:20.375 - 2176/1316 Entering JDB_CloseTable
Jan 29 15:54:20.375 - 2176/1316 Entering JDB_CloseTable(Table = F98743)
Jan 29 15:54:20.375 - 2176/1316 Entering JDB_ClearSequencing
Jan 29 15:54:20.375 - 2176/1316 Exiting JDB_ClearSequencing with Success
Jan 29 15:54:20.375 - 2176/1316 Entering JDB_ClearSelection
Jan 29 15:54:20.375 - 2176/1316 Exiting JDB_ClearSelection with Success
Jan 29 15:54:20.375 - 2176/1316 ORACLE DBFreeReq conn=07422C98 requ=0C602138 DROP
Jan 29 15:54:20.375 - 2176/1316 Entering JDB_ClearBuffers
Jan 29 15:54:20.375 - 2176/1316 Exiting JDB_ClearBuffers with success.
Jan 29 15:54:20.375 - 2176/1316 Exiting JDB_CloseTable(Table = F98743) with Success
Jan 29 15:54:20.375 - 2176/1316 Exiting JDB_CloseTable with Success
Jan 29 15:54:20.375 - 2176/1316 SpecEncapsulation : Close completed.
Jan 29 15:54:20.375 - 2176/1316 SpecEncapsulation : Close completed.
Jan 29 15:54:20.375 - 2176/1316 This transaction has failed -- all future calls to end this transaction successfully will always fail. This transaction will fail.
Jan 29 15:54:20.375 - 2176/1316 Failed transaction end -- decermenting transaction reference count to 1.
Jan 29 15:54:20.375 - 2176/1316 Adding the value, 0xf776fc0 at the OMWATTRS parameter key, 723, in the parm object, 0xf7769ac.
Jan 29 15:54:20.375 - 2176/1316 Adding the value, 0 at the OMWATTRS parameter key, 773, in the parm object, 0xf7769ac.
Jan 29 15:54:20.375 - 2176/1316 Adding the value, DV9 at the OMWATTRS parameter key, 709, in the parm object, 0xf7769ac.
Jan 29 15:54:20.375 - 2176/1316 Adding the value, DV9 at the OMWATTRS parameter key, 710, in the parm object, 0xf7769ac.
Jan 29 15:54:20.375 - 2176/1316 Retrieving the value, 0xf776fc0 at the OMWATTRS parameter key, 723, in the parm object, 0xf7769ac.
Jan 29 15:54:20.375 - 2176/1316 Retrieving the value, 0 at the OMWATTRS parameter key, 773, in the parm object, 0xf7769ac.
Jan 29 15:54:20.375 - 2176/1316 Retrieving the value, DV9 at the OMWATTRS parameter key, 710, in the parm object, 0xf7769ac.


Please update me on ur views..Thanks a million times in advance.
 
Have you tried building a new full package yet?

Also, have you ever been successful in checking out this object in the past?
 

sunnyind

Member
Thanks Dan,

I have recently build a full package after SP2 and SP2_C1.

I am able to check out most of the objects. I guess the problem could be related to media objects. Not to sure though.

Thanks again..

:((
 
The beauty of a standard "packaged" bug is that it applies uniformly to all environments.

In fact, this form was originally (mistakingly?) removed and did not exist in vanilla ERP9 (although a similar one existed before), and then it was re-added under a different name - must have been delivered in Update0, but without the FI DS.

If you have access to any other ERP9 sites, I'm sure they would have exact same issue...

Regards,
Alexander Pastuhov
http://www.pastuhov.com.au/index.htm
 

tomtom

Member
Hi,

I'm having the same problem; unable to check out P4310. Can you tell me if there is anymore news on this issue and/or SAR7005779? - especially since the status is: "08 - Returned-Could not Duplicate".

Thanks a lot, Tom
 

sunnyind

Member
Hi List,

PS has provided an ESU for the issue PF964.

I am still working on it..initial working (get and open FDA) has no issues.
:))
 

tomtom

Member
PS has provided the PF1144 for this (and other) P4310 issues. We're still working on it as well. If it isn't succesful we'll use a fix which can be installed using Boomerang software.
 

sab

Member
Not only P4310

There are 6 APPLs else with the same problem:
P07OTO1
P08710
P09E150T
P980014W
P98305

Anybody knows the reason?

PS
I have the same configuration except the RDBA - MS SQL Server 2000 SP3a
 
Top