Because GridControl is not commonly used in our DBA's daily work, it is relatively unfamiliar with some OEM errors, such as: NMO not setuid-root (Unix-only). However, in the OCM exam, scenario 7 is an exam for DG. If we choose to use GC to build DG, if we are not careful enough in scenario 6, it will be easy
When setting up a DG in Scenario 7, the exception message was encountered when setting the backup information of the main library:
what is the reason? Direct viewing is: ERROR: NMO not setuid-root (Unix-only), if it is the first time you encounter it, you will be confused, search for the reason on Baidu
There are many cases, including inconsistent oracle user information, incorrect host time and time zone, and some even rebuild gc. However, if the DBA is not careful, there is no GC
A root script needs to be executed after the agent side pushes, then the problem cannot be solved.
The script that needs to be executed after the agent side of gridcontrol pushes is as follows:
After the gridcontrol client is pushed, 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 DG is created. The main library backup setting is no problem.
In addition, in the OCM exam, there is also an online redefinition of the objects of scenario 5. If you use the EM created in scenario 1, you are also prone to encounter similar problems:
The reason is that Oracle may give you a temporary surprise: the permissions of the directory storing EM scripts have been modified, and you need to manually repair the permissions of the directory storing scripts.