Ok thanks for your feed back.
Heinrich, Tilo wrote:
Hello,
Ok this has gone far enough, so I sat down and created the medium again
to do the backup. And it worked. This is the problem.
:), always nice to have that kind of problem.
When you create the medium and haven't done a backup and double click
on the medium you will get the error, file/io error which is in a sense
quite correct since the backup hasn't been done yet.
Thank you for clearing up the exact steps. I could reproduce it :). The DBMGUI is indeed always checking the label of a file-medium, if you double-click on such a medium. If it fails, it silently assumes, that the backup does not exist, does not report any error and displays an empty label for that
medium. Unfortunately it leaves nasty error messages in knldiag and dbm.prt. The solution will be to provide the DBMGUI a proper way of testing if the backup exists on disk or not. Until then I would ask you to ignore those error messages in the log files, as long as DBMGUI does not complain.
The solution for me is to start the backup and stop complaining about
a non-existant bug :)
I'm glad I never said it is non-existing.
but in some cases where I had the file I/O error problem, I could not start the
backup at all. Haven't been able to replicate it again yet so I'll keep
quite for a while now and try and recreate it,
Looking forward to that.
sorry if I caused a panic to the developers.
Don't worry, no panic in sight.
Best Regards,
Tilo Heinrich
SAP Labs Berlin
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
