Ethan,
Have you installed CP APAR VM63978?
APAR Identifier ...... VM63978 Last Changed ........ 06/06/28
DB2 VM DATASPACES STORAGE CORRUPTION WITH MAPMDISK
Symptom ...... AB ABEND Status ........... CLOSED PER
Severity ................... 2 Date Closed ......... 06/06/27
Component .......... 568411202 Duplicate of ........
Reported Release ......... 520 Fixed Release ............ 999
Component Name VM CP Special Notice ATTENTION
Current Target Date ..06/05/27 Flags
SCP ...................
Platform ............ PERVASIVE
Status Detail: SHIPMENT - Packaged solution is available for
shipment.
PE PTF List:
PTF List:
Release 520 : UM31822 available 06/06/28 (1000 )
Release 440 : No PTF planned
Release 510 : No PTF planned
Parent APAR:
Child APAR list:
ERROR DESCRIPTION:
ARI0040E A database manager system error occurred - ARIYD06 26
is possible when running DB2 on z/VM R520 with VM data spaces
(VMDSS). The results are unpredictable once the situation is
encountered: there could be possible data corruption or other
DB2 error messages, such as ARIYI36 05 or 07.
> -----Original Message-----
> From: The IBM z/VM Operating System
> [mailto:[EMAIL PROTECTED] On Behalf Of Ethan Lanz
> Sent: Saturday, July 08, 2006 4:12 PM
> To: IBMVM@LISTSERV.UARK.EDU
> Subject: DB2/VM dataspace problem on zVM 5.20 (was Re:
> Attention DB2/VM users)
>
> Is this issue resolved?
>
> Last night we moved from a z800 (2066?) to a z9 (2096). We
> had been running DB2/VM 7.4 utilizing dataspaces on zVM5.2
> for several weeks on the old box, but since moving to the z9,
> the databases are abending with ARI0040E ... ARISIIO 05 which
> indicates directory corruption.
>
> I have a call in to IBM, but thought I would see what info I
> could gather from the list while I wait for a call-back.
>
> Ethan Lanz
>
> VM/ESA and z/VM Discussions <VMESA-L@LISTSERV.UARK.EDU> wrote on
> 2006-01-31 16:02:52:
>
> > Hi Ed, it does not matter what release of DB2/VM. It is the
> dataspaces
> > support in z/VM 5.20 seems to cause this problem. I know of,
> > DB2/VSE&VM Support is working closely with VM development trying to
> > identify/resolve this problem. They are advising user to temporary
> > take the DB2/VM database off from dataspaces support. Yes, it is a
> > toss up between performance and database corruption! *SIGH*
> >
> > I hope this help.
> >
> > Regards,
> >
> > ...Roland
> >
> > Ed Zell <[EMAIL PROTECTED]> wrote:
> > >> Hi all, Please be adviced that you shouold do more
> frequent archive
> > >> of your DB2/VM database if you are using dataspace
> support and is
> > >> running under z/VM 5.20.
> >
> > > I don't know if this is related, but we just got bit with
> DB2 server
> > > hard down. We installed z/VM 5.2.0 on a 2084 this weekend and DB2
> > > came up OK at 6am Sunday and ran until 11pm.
> >
> > I was curious what version of DB2 for VM this was, or does
> that even
> > matter if the problem is with VM dataspaces?
> >
> > This reminds me of a MAP MDISK problem with VM/ESA 1.2 that we ran
> > into back in 1993 on SQL/DS 3.3.0. We had to turn off dataspace
> > support for several months until it was resolved.
> > Not a pleasant experience at all.
> >
> > Ed Zell
> > (309) 674-8255 x-107
> > [EMAIL PROTECTED]
> >
> > .
> >
> > CONFIDENTIAL NOTICE: This communication, including any
> attachments, is
> > intended only for the use of the individual or entity to
> which it is
> > addressed and contains information which may be
> confidential. If you
> > are not the intended recipient, any distribution or copying of this
> > communication is strictly prohibited. If you have received this
> > communication in error, notify the sender immediately, delete the
> > communication and destroy all copies. Thank you for your compliance.
> >
> > With best regards,
> >
> > ...Roland Chung
> > Senior Technical Specialist (S/390,VM/VSE,DB2/VSE&VM) MAXC
> Consultants
> > Inc.
> > Voice/Fax: 416-469-3280 (If busy, call: 416-469-2268)
> > 197 Hastings Ave., Toronto, Ontario, Canada. M4L 2L6
> >
> > ** Life is short. Stop once in a while and smell the roses. **
>
