If you don’t plan to install the 11gR2 database software after a 18.104.22.168 clusterware installation, I guess there is no need for you to read this post.
I just want to share the issue I got and the way you could workaround it. The purpose of this post is just to save your time, in case of.
So, after a 22.214.171.124 clusterware installation (on a 2 nodes RAC cluster), I decided to install the 126.96.36.199 database software. I launched the runInstaller, followed the install process until the Step 4:
I see a lot of questions on shared file systems that can be used when people move from single instance to Oracle RAC database and Grid Infrastructure. The most common question is the following: “Should I place archive logs in OCFS2 or ASM or ACFS of 11g?” I’ll try to clarify this topic below.
First we need to understand a separation between Oracle database files and non-database files.
Database files belong to an Oracle database and include control files, data files, archived logs, online redo logs, etc. Oracle ASM is the preferred storage manager for all database files. It has been specifically designed and optimized to provide the best performance for database file types. The file list supported by Oracle ASM becomes longer with every new version and it includes nowadays also spfile, RMAN backupsets and some other file types. You can however use other shared cluster file systems, including OCFS2 to store Oracle RAC database files.
Non-database files are everything that does not belong to database files including Oracle binaries (ORACLE_HOME, etc.). Oracle ACFS is the preferred file manager for non-database files. It is optimized for general purpose files and can be shared across the RAC cluster. You can use both ACFS or local file system, like Ext3 to store Oracle databasebinaries (ORACLE_HOME).
There are many ways to convert a single database to RAC. Using database template, rconfig or the manual method. This post shows the steps for manual method of converting a single instance database to RAC (tested for both 188.8.131.52 and 184.108.40.206). The single database is running out of a non-rac oracle home. Backup of this would be restored using a rac enabled oracle home and then converted to a RAC database.
The database is called “asanga” and will retain the same name when converted to RAC.
1. Create a pfile of the single instance database. The pfile entries are shown below
I have received several emails asking help with why oracle does not write information into the alert log files during database startup failures.. Due to practice we tend to look for instance or database related information in our standard log directories such as $ORACLE_BASE/admin/…/bdump or $ORACLE_HOME/network/log directories. This causes panic and anxiety, searching Google, open entries on OTN forums or open an SR with Oracle support. The Oracle documentation has also not done a good job in this area.
Entries are not found in the alert log because the database/instance was not started using SQL*Plus entries are not added to the db alert log. Depending on what we are trying to look for, what area of the stack is being examined, or at what state of the application is running under, there are different kinds and flavors and locations where you could find logs.
Note: This is not a complete list, but a start for the beginners to navigate their way through the troubleshooting process.