My BE 8.6 jobs "fail" almost every time. All it takes is an open file error or something dinky like that. I'm tired of explaining that the job isn't really failing, it just encountered some issues. Is there a way to adjust what will cause the job to fail?
I think there is no way around this annoying problem. I think Veritas left this in there program to make sure admins were aware when a file was open at a time that no one should have been in the building. I dont know if this is some sort of "security blanket" that veritas is providing, however I have been on the phone and posted many messages to their newsgroups with no answer to the same question.
BTW I am at version 8.6 Rev 3878 and I still get those problems.
That's a bummer. The whole "fail"/"successful" designation is pretty meaningless if a whole job is designated as failed because of one open file. I wonder if this might change in the next version.
We recently started using Veritas when we upgraded our servers from NT 4 to Windows 2000, and I am just beginning to learn about it, but our setup includes something called Open File Option (OFO), and having a file open doesn't necessarily result in a failure message. Maybe someone who is more familiar with Veritas can say more about this. We have had some failure notices on database files that are not only open but also are constantly changing, because verification of them doesn't work.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.