Shulou(Shulou.com)06/01 Report--

As GridControl is not commonly used in our daily work of DBA, it is strange to report errors in some OEM, such as NMO not setuid-root (Unix-only). However, in the OCM exam, scenario 7 is the test for DG. If we choose to use GC to build DG, it will be easy if we are not careful enough in scenario 6.

When setting up the DG in scenario 7, the exception message was encountered when setting up the backup information of the main database:

What is the reason? Direct viewing is: ERROR:NMO not setuid-root (Unix-only). If you are confused when you meet for the first time, search Baidu for the reason.

There are many, there are oracle user information inconsistent, some host time zone is incorrect, and some even say to rebuild gc. But if DBA is not careful, there is no GC

When the agent end pushes and executes a root script, the problem cannot be solved.

The script that needs to be executed after the push on the agent side of gridcontrol is as follows:

After gridcontrol client push, use root to execute the script

After the gridcontrol client is pushed, the / u01/app/oracle/agent11g/root.sh script is executed, and then the creation of the DG is executed. The backup setting of the main database is fine.

In addition, in the OCM exam, there is an online redefinition of objects in scenario 5. If you use the EM created in scenario 1, you will easily encounter similar problems:

The reason is that it may be a temporary surprise for you by Oracle: the permission to store the EM script directory has been modified and the permission to store the script directory needs to be repaired manually.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.