Most likely your "oradim" is incorrect on the Standby Server
It should be :
You should be able to confirm this by reviewing you current Service.
oradim -NEW -SID boston -INTPWD password -STARTMODE manual
For addition information see - Data Guard Concepts and Administration
Set Up the Environment to Support the Standby Database - Create a Windows-based service.
Please consider closing some of your old questions.
We are having a problem with active dataguard (real-time query) being enabled after a switchover or a reboot of the standby. We are not licensed for it and have no intention of using it, but we cannot seem to avoid it. Is anyone else having this problem?
Oracle DB 184.108.40.206
Grid Ctrl 220.127.116.11
64 bit windows 2008 R2
This happens when you have set value for parameter ORA_SID_AUTOSTART to TRUE in regedit
So either you can disable it as FALSE or you can edit the service using oradim
So that whenever your service restarts or server reboots, you have to start it manually to Mount status else it will put in OPEN status.
738517 probably wants his standby to autostart.
This is a "feature"/trap in Windows. ORADIM -STARTMODE AUTO, attempts to open the database. If it's a Data Guard standby, DG broker gets hold of and resets it to OPEN READ ONLY state, which is Real Time Query/Active Data Guard and requires an additional licence.
Oracle should add a new option to ORADIM so database -startmode AUTO can be set to -openmode MOUNT. Otherwise customers might be tempted to think they deliberately left this "defect" in place to try and entrap some customers into paying for a potentially expensive feature - list US$10,000 per CPU - they have not decided to use.
If you set -startmode MANUAL, on Windows 2008 you can setup a scheduler task that's actually triggered on system startup.
The Action can be set to something like:
C:\Windows\System32\cmd /c "sqlplus /@YOURDB as sysdba @c:\scripts\startupmount.sql >>c:\scripts\log\startupMOUNT.log"
Where startupmount.sql does STARTUP MOUNT.