ADSM-L

[no subject]

2015-10-04 17:13:41
Hello
 
We tried to do a unloaddb this weekend to reorganise our database. It ran fine for 2 hours but then it seemed to stop after 157 million entries.
ANR4013I UNLOADDB: Dumped 157654872 database entries (cumulative).
 
But after this nothing happens, we could see I/O activity  in MVS for the task. After 6 hours we cancelled the job.
I've read on the ADSM list about unload times over 20 hours, is this a normal time?
 
q db
 
Available    Assigned    Maximum    Maximum    Page    Total          Used        Pct    Max.
Space       Capacity     Extension    Reduction    Size     Usable       Pages      Util    Pct
(MB)         (MB)          (MB)             (MB)           (bytes) Pages                                Util
-----------------------------------------------------------------------------------------------------------------------------------
   nbsp;  44,868   44,868         0                 6,216          4,096 11,486,208   9,737,492  84.8  84.8
                                                      
 
TSM 4.2.0 running on OS/390
 
 
 
 
MVH
Niklas Lundström
Föreningssparbanken IT
08-5859 5164
 
------_=_NextPart_001_01C1A256.A6D1F7B0-- ------=_NextPartTM-000-de3189fd-0dcd-11d6-8864-0003473bb2ae-- ------=_NextPartTM-000-de3189fd-0dcd-11d6-8864-0003473bb2ae-- =======================================================================
<Prev in Thread] Current Thread [Next in Thread>
  • [no subject], Unknown <=