View Full Version: Finddbrec Error Is Duplicate Index - Stumped!

LawsonTalk > Coding, Program Errors and Bugs > Finddbrec Error Is Duplicate Index - Stumped!



Title: Finddbrec Error Is Duplicate Index - Stumped!


Cindy - July 17, 2008 04:23 PM (GMT)
In testing our upgrade to LSF9 (env only - still using 8.0.3 apps), we are getting an error in several of our online forms, and in at least one batch job - and these are all custom programs.

In portal, we get this error:

INCIDENT_ID#1216307806554-0067 An error occurred outside of IOS while accessing Lawson Application

In LID we get this error:

File PROD/VLCOMMENT1
FindDBRec error is Duplicate index is not allowed for this operation (132).

The named table in the above error (VLCOMMENT1) is different for the batch job, but is is the same error. We've checked the data and can find no duplicate index or data problems. And I don't see any errors in the LADB log either - which I would have expected to see for a DB related error. The KB has no useful information on this error, and we're rather stumped. This same code works flawlessly in 8.0.3.7. Does anyone have any ideas on where to look next?

Cindy - July 17, 2008 08:29 PM (GMT)
Update, for anyone else that has this problem. We have a custom table with an index that allows dupes, which is okay. But the 840-FIND-INDEX was being used with that index, and that won't work in LSF9. I could not find that change documented anywhere, but it definitely is a change is LSF9.

mthedford - July 22, 2008 02:57 PM (GMT)
From what I've been told, the 8.0.3 ENV allowed or did not enforce certain programing structures to occur that were not exactly correct. LSF9 is a lot tighter in adhering to the correct use of the API's and their rules.

BSmith - November 6, 2008 08:12 PM (GMT)
We just built a new productline in our 9.x LSF env with 8.1.x apps. We are getting similar errors.

----------snippet starts--------------------
com.lawson.ios.agent.SystemRuntimeException: 2008-11-06 15:06:00 : INCIDENT_ID#1226001960982-0006 An error occurred outside of IOS while accessing Lawson Application
at com.lawson.tesla.exec.LatmWrapper.invoke(LatmWrapper.java:79)
at com.lawson.tesla.exec.Tesla.createCrtioBuffer(Tesla.java:1106)
at com.lawson.tesla.exec.Tesla.invoke(Tesla.java:278)
at com.lawson.tesla.agent.ErpTransactionAgent.processRequest(ErpTransactionAgent.java:177)
at com.lawson.ios.agent.container.AgentContainerImpl$AgentWrapper.processRequest(AgentContainerImpl.java:467)
at com.lawson.tesla.broker.TransactionBroker.processRequest(TransactionBroker.java:80)
------------snippet ends---------------


The horror of this msg goes on with more java junk....BUT
Does anyone have a fix? or a workaround?? (Laughingly asking if there is a patch)


Thanks,

Brad

area51 - November 6, 2008 08:57 PM (GMT)
Brad,
Check this KB 5088797 article to start researching your issue. I know I had similar issue but I don't remember my exact resolution. But it might have had to do with the Cobol environment variables - we had Lawson PS do the upgrade test and unfortunately I think person didn't set the right directories. Check your WAS settings and lawson environment settings.

wallaced - November 7, 2008 12:37 PM (GMT)
I have found that in 9.xx apps, dupes within an index are no longer allowed. When creating additional indexes beyond XXXSET1, which must be unique, other indexes need to have enough fields added to make them unique also. If I need to find a value with less than the full key, I define as many values as I can and use an 850-FIND-BEGRNG-XXXSETY. I then use the FOUND/NOTFOUND(treating the return as if I had used an 840-FIND) and forget looking for a NEXT record.

Hope that helps.

Dan




Hosted for free by InvisionFree