We had this problem back in August. Our DB systems programmer reported the
problem to IBM. They recommend applying the latest DB2/6000 fix pak.
This seems to have fixed the problem.
(Embedded
image moved nrussell @ BTV.IBM.COM
to file: 12/16/97 01:11 PM
PIC15804.PCX)
Please respond to ADSM-L AT VM.MARIST DOT EDU
To: ADSM-L @ VM.MARIST.EDU
cc: (bcc: Julie Konkle/AAL)
Subject: SQL2025N (RC157)
Hi Everyone,
From time to time, I have ADSM clients backing up DB2 databases to
my ADSM Server (AIX 414 ADSM 2.1.0.13) that receive in their log file
the message: SQL2025N An I/O error "157" occurred on media "ADSM".
No error message comes out in the activity log on the server side.
The API return code for 157 simply says the server encountered an
error and will abort the transaction.
This occurs at the very beginning of the backup as if the server
looks at the size of the database being backed up, and the size of the
disk backup pool (7.6G with max threshold at 5G) and somehow decides
that the pool is not large enough. The disk backuppool does have a value
for next storage pool specified.
Has anyone seen this error and return code, or offer any suggestion
as to what might be happening?
Thanks,
Norm
------------------------------------------------------------------------
Norm Russell, IBM Microelectronics, Distributed Computing Services
Norm Russell, IBM Microelectronics, Distributed Computing Services
IBM e-mail: nrussell AT btv.ibm DOT com Internet e-mail: nrussell AT vnet.ibm
DOT com
Tel: 802-769-4088 (tie: 446), Fax: 802-769-4253 (tie: 446)
------------------------------------------------------------------------
--0__=SGJnK6q9laZFHVhNBshoeVfP2bQFCpjc4UAav0mJ3ZSOSnL9cHVr1rbf
|