Today, a customer called to say that their OEM was out of service. The OEM had to be said many times, but he had never played it. The following is a bit of fun in your test environment, and an error is returned. Environment: OS :.
Today, a customer called to say that their OEM was out of service. The OEM had to be said many times, but he had never played it. The following is a bit of fun in your test environment, and an error is returned. Environment: OS :.
Today, a customer called to say that their OEM was out of service and could not afford to use it. The OEM had to be said many times, and the server space had never been used. The following is a bit of fun in your test environment, and an error is returned.
Environment: OS: RHEL 5.6 X86_64 DB: 11.2.0.2 RAC
1. Configure an OEM for a Hong Kong VM
2. view the listening message
It is found that the asm listener runs on the LISTENER and is not registered to the LISTENER_SCAN1 server in Hong Kong, while the OEM uses the LISTENER_SCAN1 LISTENER.
3. Manually register the listener and view the status
4. Configure OEM again
Successfully is displayed, indicating that the operation is successful.
5. view the running status.
Everything is normal. The OEM configuration is successful.
This article is from the "seriously lose" blog. Please keep this source