In Oracle11GR2RAC, modifying the location of the DATABASEspfile file is not the original $ ORACLE_HOMEdbsinitORACLE_SID.ora file. If we modify this file manually, it will still take effect when sqlplus is used to manually start the database, however, if we use the srvctl or crsctl tool to start data, it will not take effect.
In Oracle 11GR2 RAC, modifying the DATABASE spfile file is not the original $ ORACLE_HOME/dbs/initORACLE_SID.ora file. If we modify this file manually, it will still take effect when you use sqlplus to manually start the database, but it will not take effect if you use srvctl or crsctl tool to start data.
Modifying the location of the DATABASE spfile file in Oracle 11GR2 RAC is not the original $ ORACLE_HOME/dbs/init . Ora file. If we manually modify this file, it will still take effect when SQL plus is used to manually start the database, but if we use srvctl or crsctl tool to start data, it will not take effect. This is because the spfile file path has ended with the cluster. When $ ORACLE_HOME/dbs/init When the content in. ora is inconsistent with the content we see in srvctl, when you start the database using the srvctl tool, $ ORACLE_HOME/dbs/init will be modified by yourself. The content in the. ora file is the same as that in the file. In $ ORACLE_HOME/dbs/init After the first line of the. ora file, you can see # add by agent.
1. [oracle @ 11rac1 ~] $ Srvctl modify database-d power-p + DATA3/power/parameterfile/spfile.257.794161021 2. [Oracle @ 11rac1 ~] $ Srvctl config database-d power 3. database unique name: power 4. database name: power 5. oracle home:/u01/app/oracle/product/11.2.0/db_1 6. oracle user: oracle 7. spfile: + DATA3/power/parameterfile/spfile.257.794161021 8. domain: 9. start options: open 10. stop options: immediate 11. database role: PRIMARY 12. management policy: AUTOMATIC 13. server pools: power 14. database instances: power1, power2 15. disk Groups: DATA, ARCH, DATA3, ARCH1 16. mount point paths: 17. services: 18. type: RAC 19. database is administrator managed