Expiration Problems with 3.1.2.13
1999-02-10 10:32:42
Hi,
this morning I upgraded ADSM 3.1.1.3 on AIX to 3.2.1.13.
Everything seemed to be fine until I started expire inventory.
First interesting info in actlog is the following:
10.02.1999 15:28:41 ANR0104E imarins.c(1303): Error 2 deleting row from
table "Archive.Descriptions".
10.02.1999 15:28:41 ANR9999D imutil.c(1161): Error deleting object (0
18097336)
10.02.1999 15:28:41 ANR9999D imexp.c(1350): Error 8 deleting expired
10.02.1999 15:28:41 ANR9999D imexp.c(1350): Error 8 deleting expired
object (0 18097336) - deletion will be re-tried.
10.02.1999 15:28:41 ANR0104E imarins.c(1303): Error 2 deleting row from
table "Archive.Descriptions".
This looks very much like APAR IX79626 which I thought is fixed since
3.1.2.0. Could it be that it slipped in again?
What makes the situation worse is the fact that the expiration process
went into a loop. Cancelling the process did not work. The q proc
command shows "expiration Cancel in Progress".
What can I do?
Best regards
Gerhard
---
Gerhard Rentschler email:g.rentschler AT rus.uni-stuttgart DOT de
Gerhard Rentschler email:g.rentschler AT rus.uni-stuttgart DOT de
Regional Computing Center tel. ++49/711/685 5806
University of Stuttgart fax: ++49/711/682357
Allmandring 30a
D 70550
Stuttgart
Germany
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Expiration Problems with 3.1.2.13,
Gerhard Rentschler <=
|
|
|