Re: Table in use message -- MIDRANGE-L

Joblog (I added the message number after the ---->)

3 > ADDPFCST FILE(PFI520/SOLPUB_KSP) TYPE(*REFCST) KEY(CLIENTE)
CST(cliente_en
_addres) PRNFILE(B/ADDRES_NCL) PRNKEY(NCLIE) DLTRULE(*RESTRICT)
UPDRULE(*R
ESTRICT)
Está utilizándose el archivo ADDRES_NCL de la biblioteca B. ---->
CPF3202
La restricción no puede eliminarse del archivo SOLPUB_KSP. ----> CPD32B1
Se ha eliminado la
restricción. ----> CPI32B1
Recuperación satisfactoria de restricción de archivo físico. ----> CPF32B4
La restricción no puede a¦adirse al archivo SOLPUB_KSP.
----> CPF32B0

I get the same messages if I try to add the constraint from QSL.
We are at V7.1, and we have a machine at V5.3 and other at V5.2 using
the files via DDM.
________________________________________________________________________________________

I copy the dump below, but it may refer to the next constraint that did
work fine.

5770SS1 V7R1M0 041023 VOLCADO DE IBM i
001991/QSECOFR/QPADEV0002 27/10/11 17:18:35 PAGINA 1
PARÁMETROS DMPSYSOBJ
OBJ- QDBDBDROBJ* CONTEXT- PFI520
TIPO- 19 SUBTIPO-D4
TIPO OBJETO- ESPACIO
*DBRCVR
NOMBRE- QDBDBDROBJFPUBL_K_F_PFI520 TIPO- 19
SUBTIPO- D4
BIBLIOTECA- PFI520 TIPO- 04
SUBTIPO- 01
CREACIÓN- 14/09/11 11:20:51 TAMA#O- 0000002000
PROPIETARIO- QDBSHR TIPO- 08
SUBTIPO- 01
ATRIBUTOS- 0800 DIRECCIÓN- 21BAEDD32D
000000
ATRIBUTOS ESPACIO-
000000 00FFF000 00000074 19D4D8C4 C2C4C2C4 D9D6C2D1 C6D7E4C2
D36DD26D C66DD7C6 * 0 È MQDBDBDROBJFPUBL_K_F_PF*
000020 C9F5F2F0 40404040 E0020000 00000000 00001000 00100000
00000000 00000000 *I520 \ *
000040 00000000 00000000 0F804358 33000400 00000000 00000000
00000000 00000000 * äì *
000060 00000000 00000000 00000000 00000000
00FFF000 * 0 *
ESPACIO-
000000 00000000 00000000 12D70BFE 26001900 00000000 00000000
0F804358 33000400 * P Ú äì *
000020 D8C4C2D4 E5D9C6D9 40404700 01000000 00000000 00000000
00000000 00000000 *QDBMVRFR å *
000040 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 * *
LÍNEAS 000060 A 00017F IGUAL QUE ANTERIOR
000180 00000000 00000000 00000000 00000000 00000000 00000000
3A2D0900 E2001900 * S *
0001A0 C6D7E4C2 D36DD26D C66DC6D7 E4C2D36D D26DC640 C6D7E4C2
D36DD26D C640D7C6 *FPUBL_K_F_FPUBL_K_F FPUBL_K_F PF*
0001C0 C9F5F2F0 40404040 40404040 40404040 4040D7C7 D4C1C2C3
40404040 C6858388 *I520 PGMABC Fech*
0001E0 81A24081 4097A482 93898381 994081A5 89A296A2 406040D7
969940D2 A29740A8 *as a publicar avisos - Por Ksp y*
000200 40868583 88814040 40404040 4040D7C6 4040C4F0 F0F0F0F6
F0F0F0F0 F2F0F0F0 * fecha PF D0000600002000*
000220 F0F0F0F0 F0F0F2F6 F0F0F0F0 F0F0F0F0 F0F0F000 00004040
40404040 40404040 *0000002600000000000 *
000240 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 * *
000260 00000000 00000000 00000000 00000000 80000000 00000000
21BAEDD3 2D001290 * [ÒL °*
000280 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 * *
LÍNEAS 0002A0 A 000FFF IGUAL QUE ANTERIOR
.PUNTEROS-
000000 OBJETO DIRECCIONADO DESTRUIDO-
000010 SYP 04 01 PFI520 CONTEXTO
MAQUINA 0000 0000 *LIB
000190 OBJETO DIRECCIONADO DESTRUIDO-
000270 SPP 19 D4 QDBDBDROBJFPUBL_K_F_PFI520 04 01
PFI520 00000290 0000
DATOS OIR-
NINGUNO
FIN DE VUELCO

CRPence wrote:

On 27-Oct-2011 09:09 , Raul A. Jager W. wrote:

<<SNIP>> I know that it is not because of the "abnormal shut down",
and I was more carefull in the search for the problem. The message I
get before the (false) "object in use" is CPD32B1

<<SNIP; message details included here as symptom string & text:
msgCPD32B1 rc5 rc05 F/QDBRMVCT x/2C4D T/QDBARCFR x/0937
"Constraint CLIENTE_EN_ADDRES cannot be removed
from file SOLPUB_KSP in library PFI520
for TYPE value *REFCST, RMVCST value &5. ...
reason code: 05 - File is logically damaged.
recovery: 05 - Delete the file and create it again." >>

I did follow that advise, and the newly created file has the same problem.
Can it be a missing PTF?

What was the CL or SQL request that received the error? What
messages were logged from the start of that request until this message, and were any other messages following that? IOW, the full joblog of the
request is ideal; would also include release info which was omitted.
Regardless ...

What the symptom suggests is that, under database recovery, an
attempt was made to effect the equivalent of the request to "RMVPFCST
FILE(PFI520/SOLPUB_KSP) CST(cliente_en_addres) TYPE(*REFCST)". Usually that activity occurs as part of backing-out a request to "ADDPFCST
FILE(PFI520/SOLPUB_KSP) CST(cliente_en_addres) TYPE(*REFCST) ...", as a side-effect of an error that occurred during processing; at least in
part, why what errors precede the given, is relevant. This back-out
activity is part of "database recovery" processing which is something
the equivalent of having run the request under commitment control, and
seeing an implicit ROLLBACK.

The message more specifically means that there is a database recovery
object already associated with the file, and the pending activity
appears to the db recovery processing to be incompatible with or
unassociated with the current task\activity running under db recovery.
The scenario may not be nearly so simplistic, because constraint
activity requires accessing the entire db network [all related files]
rather than one file, and referentially that may be tying two existing
db networks into one, such that effectively there are two entire db
networks tied up in the processing [minimally for locks obtained].

Since the failure, the following request to dump the database
recovery objects for the library might confirm there is still pending
database recovery activity; i.e. the file is "logically damaged":
DMPSYSOBJ QDBDBDROBJ* PFI520 19 D4

Regards, Chuck