Who's On?

	Membership:
	Latest: jlrobinson
	Past 24 Hours: 0
	Prev. 24 Hours: 0
	Overall: 5213

	People Online:
	Visitors: 371
	Members: 0
	Total: 371

Name	Points
Greg Moeller	4184
David Williams	3349
Kat V	2984
Woozy	1973
Jimmy Chiu	1883
Kwane McNeal	1437
Ragu Raghavan	1377
Roger French	1315
mark.cook	1244
Chesca	1042

storedbrec - no key change + BSI errors

5 Replies

0 Subscribed to this topic

69 Subscribed to this forum

Sort:

Author

Messages

nbrogdon

New Member

Posts: 0

6/20/2007 9:30 PM

We are on LSF9.0.0.2 with 803 apps and TaxFactory 7.0k. Has anyone seen the errors we are getting on PA100?

BEGIN: Job Submitted: Wed Jun 20 09:02:57 2007

Step 1: PA100 Started. . . . . .: Wed Jun 20 09:02:57 2007
Token Command. . . . . .: /lawson8/law/prod/obj/PA100.gnt
Executable Command . . .: /lawson8/gen/bin/lacobrts lacobrts /lawson8/law/prod/obj/PA100.gnt prod jamonte PA100JJPRD 1
Process ID . . . . . . .: 13712
Program Messages:
** Creating .prt and .dtl files
Processing PA100 (Action Update)
File PROD/PAEMPLOYEE.
tsStoreDBRec error is Key change not allowed (32).
Wed Jun 20 09:03:05 2007: Tfxiface7:GetBsiFunction7(): child process failure on first pipe read

Elapsed Time . . . . . .: 00:00:08

ERROR: Stopped On Exit 1.

Any help/ideas/suggestions are greatly appreciated!

Nicole Brogdon

John Henley

Posts: 3364

New Poster

Engaged Reader

Avid Reader

6/21/2007 11:18 AM

Do you have any custom indexes on PAEMPLOYEE?
What platform / database are you running?
Have you experienced any other TXF-related errors? Or has this been working correctly before, and this is the first error?

nbrogdon

New Member

Posts: 0

6/21/2007 2:52 PM

Hi John -

We are running on HP-UX with an Oracle 10g database.

This is one of the main errors we are experiencing. We recently migrated to the LSF9 environment, and have been receiving these errors since doing so.

We have 2 custom indices on the table.
*One is company, locat_code, employee and it is a unique constraint.
*The other is company, maiden_lst_nm, employee and it is also a unique constraint.

John Henley

Posts: 3364

New Poster

Engaged Reader

Avid Reader

6/21/2007 4:14 PM

Make sure that you have the 'Key Change' option set to YES in dbdef for these custom indexes.

nbrogdon

New Member

Posts: 0

6/21/2007 4:18 PM

I am actually testing that now!

Thanks a ton for your response :-)

Nicole

PS - I'll post my testing outcome in a few ;-)

nbrogdon

New Member

Posts: 0

6/21/2007 6:44 PM

John - you are my hero! Our programs are no longer getting that hokey error!

Thank you so very, very much!
-Nicole