dp打完patch之后,发现schedule无法正常执行,已经正确的设置了schedule,且尝试重启重启服务,reset schedule,重启cell manager主机,都无法正常的运行schedule的作业,但是手工start backup却是可以的。
检查dp的debug log:
C:\Program Files\OmniBack\log
1 2 3 4 5 6 7 8 |
2008-1-8 9:15:06 OMNIB.4528.4456 ["cli/omnibackup.c /main/dp51/10":3143] A.05.10 b209 [Process] CanBackup failed! 2008-1-8 9:30:06 OMNIB.3240.5488 ["cli/omnibackup.c /main/dp51/10":3143] A.05.10 b209 [Process] CanBackup failed! 2008-1-8 9:45:06 OMNIB.3684.5196 ["cli/omnibackup.c /main/dp51/10":3143] A.05.10 b209 [Process] CanBackup failed! |
根据hp技术论坛上的解答:
the CanBackup Failed error means that the omnitrig service account (root), is not alowed to execute DP admin operations !!
The CRS service needed to be started under a user account rather than start under a system service 。
登录db,检查其users条目,admin组中各个成员的权限
发现ADMINISTRATOR用户的domain是cell manager主机,权限不够大,尝试开大权限为Any,
结果发现再次登录dp都无法登录了-_-!!
找到users的配置文件进行修改:
C:\Program Files\OmniBack\Config\users
1 2 3 4 |
"" "ADMINISTRATOR" "<Any>" * "admin" "WebReporting" "java" "applet" webreporting "admin" "" "oracle" "dba" * "admin" "" "root" * * "admin" |
改成
1 2 3 4 |
"" "ADMINISTRATOR" * * "admin" "WebReporting" "java" "applet" webreporting "admin" "" "oracle" "dba" * "admin" "" "root" * * "admin" |
此时dp能够再次登录上去了。且在界面显示为Any(幸好。。。。幸好。。。。不然就出大事了!)
检查CRS的服务,发现其登录账户为使用本地系统账户,尝试改成制定账户用administrator,还是不行,尝试用大写的ADMINISTRATOR,搞定!schedule回复正常作业!
总结:由于在unsers条目admin组里面的用户ADMINSTRATOR是大写,必须在CRS服务中配置对应的也是大写。