Oracle Monitoring service does not start automatically after server reboot solution

Recently, it has been a problem, that is, after the server power outage restart, the Oracle monitoring service does not automatically start (the monitoring service has been set to self-booting).

Specifically, the monitoring service is set to boot, the Oracle database service is set to boot delay start, according to the reason this should be in line with the "start listening, after starting the database service" condition, but every time the power is restarted after the database service started normally, the monitoring service failed to start.

Look up, there are two of statements, it feels quite reasonable:

1, generally set up the start-up service to manual, basically is the registry inconsistency caused;

2. Login account is not the same as the account you installed Oracle, do not have permission to start.

For the above two statements, decide to use Windows Scheduled tasks to resolve (tasks are established as Administrator):

Reference: W?i?n?d?o? w?s?? S?e?r?v?e?r, 2?0?0?8, Tim???????

1. Create a new Windows scheduled task, set to start 5 minutes after the execution (Oracle TNS monitoring Service);

2. Create a new Windows scheduled task that is set to execute after 6 minutes (Oracle Service service).

Test Problem Solving