[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

Title:	OLD ALL-IN-1 (tm) Support Conference
Notice:	Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:	IOSG::PYE

Created:	Thu Jan 30 1992
Last Modified:	Tue Jan 23 1996
Last Successful Update:	Fri Jun 06 1997
Number of topics:	4343
Total number of notes:	18308

414.0. "Error RECORD BUCKED/LOCKED with K536 and V2.3" by TLSE01::COURCOUX () Mon Apr 06 1992 12:22

Hello,

I have one customer with the following configuration:

A cluster of three 6000-xxx.
VMS V5.4-2.
ALL-IN-1 V2.3, patched by k501-K513 and  K536.
1500 ALL-IN-1 accounts.

When he run the TRM procedure, with the new file OA$SM_FCVR.EXE, he get some
error messages " RECORD BUCKET/LOCKED", that he had already experienced without
the patch K536.

The message occurs only for 50 accounts, and we are sure that the users was not
logged during the time the procedure ran.

Is there any solution to avoid this problem (i.e. use of image OA$SM_FCVR.EXE
from ALL-IN-1 V2.4) ?

Thank you for your help.

Best regards,

Didier COURCOUX, SPS Toulouse .


Mail address:  TLSE01::COURCOUX  Dtn: 7858-5562

T.R	Title	User	Personal Name	Date	Lines
414.1	Have you checked for open files?	AIMTEC::PORTER_T	Terry Porter, ALL-IN-1 Support, Atlanta CSC	`Mon Apr 06 1992 16:18`	11
	It looks like something external to ALL-IN-1 has the files open. If it's specific to some users then it's probably the DOCDB or PDAF that are open. Have you tried using SHOW DEVICE/FILES on the disk(s) those users are on to see if anything has the files open. It may be that those files are only opened externally to ALL-IN-1 at certain times (some overnight housekeeping procedure?) so you may have to do the check at the time you would expect TRM to be running. HTH Terry
414.2	Check of open files.	TLSE01::COURCOUX		`Mon Apr 06 1992 17:52`	8
	My customer don't believe the DOCDB could be opened, but he his going to modify the command file executed by the procedure ( OA$LIB:OA$SM_FCVR_SCHEDULE.COM ) to add a SHOW DEVICE/FILE just before and after the call to OA$SM_FCVR.EXE. The test will be done at the end of the week, because TRM takes at least about 6 hours.
414.3	Wrong OA$SM_FCVR.EXE?	IOSG::CHAPLIN	Andy Chaplin	`Tue Apr 07 1992 21:37`	6
	This problem has been seen after a 2.4 upgrade due to the fact that the 504 and 536 patches had a tendancy to put the new OA$SM_FCVR.EXE into OA$SITE_LIB_LLV rather than OA$LIB_SHARE. Although you're on 2.3 its worth checking the OA$LIB directories to make sure that you are running the right version. Andy
414.4	correct version of image!	TLSE01::COURCOUX		`Mon Apr 13 1992 17:26`	7
	I'm sure we use the right version of OA$SM_FCVR.EXE, the site file has been renamed to SDC directory, and the customer always use version 2.3 I'm waiting for the next execution of TRM to have more informations. Regards, Didier Courcoux