My guess would be that since you told ADSM to skip open files it didn't
consider this a "failure".




ADSM-L AT vm.marist DOT edu on 03/04/99 06:00:01 AM
Please respond to ADSM-L AT vm.marist DOT edu @ INTERNET
To: ADSM-L AT vm.marist DOT edu @ INTERNET
cc:
Subject: Failed schedules display completed.

Hi All,

After doing some D/R it was found that ADSM had not got a complete
backup of our Oracle database. The was because the d/b was not down,
files were changing and therefore skipped. This has now been resolved.
My question is why the schedule displayed "completed successfully" when
in fact it finished with failures. Is this a known problem or is ADSM
displaying the correct message?

Total number of objects inspected:   16,974
Total number of objects backed up:      584
Total number of objects updated:          0
Total number of objects rebound:          0
Total number of objects deleted:        613
Total number of objects failed:           2
******
Total number of bytes transferred:      1.3 GB
Data transfer time:                1,260.69 sec
Data transfer rate:                1,141.84 KB/sec
Average file size:                  8,097.5 KB
Compression percent reduction:           86%
Elapsed processing time:           02:24:53
Scheduled event 'OFORAC_INC' completed successfully.    ******


Thanks,

Katie.

______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com