] On Behalf Of
Prather, Wanda
Sent: Monday, April 07, 2014 3:42 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] V5-V6 conversion failed on INSERTDB with File system
full
Well, at base level 6.3.0 it was verboten, so that's probably what the tech
is referring to:
Restriction: You cannot upgrade your
.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Bill
Boyer
Sent: Thursday, April 03, 2014 5:59 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] V5-V6 conversion failed on INSERTDB with File system full
Added another 1TB file system to the database
this from AIX to Linux.
Bill
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Steven Langdale
Sent: Wednesday, April 02, 2014 2:43 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] V5-V6 conversion failed on INSERTDB with File system
full
Bill, what
Bill, what was the outcome?
On 1 April 2014 23:22, Bill Boyer bjdbo...@comcast.net wrote:
V5.5.7.0 on AIX converting over the network to V6.3.4.0 on Linux RedHat.
The V5 DB is 260GB at 90%.
The TSM DB is defined on 4x100GB file systems /tsmdb01 - /tsmdb04. Active
log is 32GB and
V5.5.7.0 on AIX converting over the network to V6.3.4.0 on Linux RedHat.
The V5 DB is 260GB at 90%.
The TSM DB is defined on 4x100GB file systems /tsmdb01 - /tsmdb04. Active
log is 32GB and archive log file system is 200GB.
The extractdb phase seems to complete successfully:
ANR0409I
