RDBPROD: Rdb Verify Aborted
edited Jan 10, 2014 1:03PM in Rdb on OpenVMS, IBM zSeries and Oracle on OpenVMS (MOSC) 12 commentsAnswered ✓
I usually run the full verify in streams and never had an issue with disk space. As each separate stream completes, maybe some of the used disk space is released? When I tried running the verify as given here, I ran out of system disk space. I changed the method because of the dependency on the extracted VERIFY output seems more manual the method below seems more sure. Is the stream verify method more of a risk because it depends on this manual metadata extract?
rmu/verify/all/transaction=read -
/log/output=$1$DGA255:[ALLVERIFY]dbverify.log -
database
%SORT-E-WRITEERR, error writing SYS$SYSROOT:[SYSMGR.SCRATCH]SORTWORK1.TMP;2
0