Issues when initiating Oracle Database whilst installing OIM11gR2PS2

I came across so many issues when trying to pack OIM 11gR2PS2 on my 7.5GB VM image. One alteration I had constantly manipulate was the control file.
August 10, 2014
OIMOIM11gR2PS2Oracle-Database11g

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';


Further Issues I encountered

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

Daniel is a Technical Manager with over 10 years of consulting expertise in the Identity and Access Management space.
Daniel has built from scratch this blog as well as technicalconfessions.com
Follow Daniel on twitter @nervouswiggles

Comments

Other Posts

HOW TO provision AD group membership from OpenIDM

OpenIDMICFAD-connector

June 15, 2018
Created by: Daniel Redfern
For what I see, there's not too many supportive documentations out there that will demonstrate how provision AD group membership with the ICF connector using OpenIDM. The use of the special ldapGroups attribute is not explained anywhere in the Integrators guides to to the date of this blog. This quick blog identifies the tasks required to provision AD group membership from OpenIDM to AD using the LDAP ICF connector. However this doesn't really explain what ldapGroups actually does and there's no real worked example of how to go from an Assignment to ldapGroups to an assigned group in AD. I wrote up a wiki article for my own reference: AD group memberships automatically to users This is just my view, others may disagree, but I think the implementation experience could be improved with some more documentation and a more detailed example here.
Read More...

ForgeRock OpenIDM - InvalidCredentialException: Remote framework key is invalid

ICFIDMOpenIDMOpenICF

November 8, 2017
Created by: Daniel Redfern
In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.
Read More...

org.forgerock.script.exception.ScriptCompilationException: missing ; before statement

IDMsync.confforgerockopenidm

November 8, 2017
Created by: Daniel Redfern
org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...

ForgeRock IDM - org.forgerock.script.exception.ScriptCompilationException: missing ; before statemen

OpenIDMsync.confForgeRock

September 17, 2017
Created by: Daniel Redfern
ForgeRock IDM - org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...

Caused by: org.forgerock.json.resource.BadRequestException: Target does not support attribute groups

OpenIDMForgeRockICFConnector

September 17, 2017
Created by: Daniel Redfern
When performing the attempt of a reconciliation from ForgeRock IDM to Active Directory, I would get the following error
Read More...

ForgeRock OpenIDM - InvalidCredentialException: Remote framework key is invalid

OpenIDMForgeRockICFConnectorAD

September 17, 2017
Created by: Daniel Redfern
In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.
Read More...

ERROR Caused by com.google.api.client.auth.oauth2.TokenResponseException 400 Bad Request - invalid_g

OpenIDMIDMGoogleGoogle-AppsICFreconciliation

September 12, 2017
Created by: Daniel Redfern
During the reconcilation from OpenIDM to the ICF google apps connector, the following error response would occur. ERROR Caused by com.google.api.client.auth.oauth2.TokenResponseException 400 Bad Request - invalid_grant
Read More...

forgerock-openidm-encryptedjwt-error

OpenIDMIDMForgeRockJWTIAM

August 29, 2017
Created by: Daniel Redfern
Received the JWT error
Read More...

Unexpected character ('¾' (code 190)): expected a valid value

ForgeRock-OpenIDMOpenIDMIDMKeystore

June 25, 2017
Created by: Daniel Redfern
Unexpected character occurred when the IP addresses changes and the virtual instance was migrated into a separate network subnet.
Read More...

OpenDJ Error - Connect Error Result Code: 91 (Connect Error)

OpenDJLDAPldapsearchForgeRock

June 5, 2017
Created by: Daniel Redfern
When trying to connect, I would then receive the following error "Connect Error Result Code: 91 (Connect Error)"
Read More...