The Database instance will look for the following in their respective order:

• 1. SP File
• 2. P File
• 3. init.ora file

Once located, it will use that information within that file and not be concerned about the other file. If neither are located, you will receive an ERROR: LRM-00109: could not open parameter file /opt/oracle/112/dbs/initorcl.ora error.

Some of you may know that the Oracle database initially looks for the SPFile (server parameter file) for the configuration settings. If it's not there, the oracle database will then try to locate the PFile. I did blog about ORA-00205: error in identifying control file, check alert log for more info to modify the control files within the SPFile.

Because of the constant changes for database tuning, this may not be the ideal approach. My proposal would be to create an initSERVICE_NAME.ora file by simply creating a copy of the init.ora file, making the necessary changes, then creating a SPFile by using the PFile I did a quick video on how to create a SPFile, from a PFile, from an init.ora for the OIM deployment

To create an SPFILE from a PFILE, I used the following command within SQLPLUS

CREATE SPFILE FROM PFILE='/opt/oracle/112/dbs/initorcl.ora';

The first issue (ERROR: LRM-00109: could not open parameter file /opt/oracle/112/dbs/initorcl.ora) I came across was the fact that the Oracle database instance would not start. The quick solution here was to create a SPFILE by using the initial parameter file (init.ora), creating a PFile (initorcl.ora), then creating a SPFile for the Oracle database startup (SPinitorcl.ora).

OK, now the instance was up but idling. I then came across the error ORA-48140: the specified ADR Base directory does not exist [/opt/oracle/112/dbs/ORACLE_BASE] followed with ORA-48108: invalid value given for the diagnostic_dest init.ora parameter. The solution here was to modify the init.ora file and to override the ORACLE_BASE value within the file.

Then there was the memory allocation constraint what with trying to deploy this on a VM with 7GB. I altered to database instance to avoid the Error creating connection pool "oimOperationsDB" whilst trying to startup the OIM managed server error. Moving away from the database memory allocation instance for a second, I also altered the minimal working memory Allocation for Weblogic Managed Servers of OIM and SOA. To ensure the OIM instance can be bought up without issues.

Whilst working with control files was also a factor once I made alterations to the PFile. I also created a youtube video, which demonstrates the required alterations.

About the author