After Fresh Install Starting Concurrent Manager Fail With ERROR "usdipe: error inserting data: ORA-3114" (Doc ID 1080386.1)

Last updated on APRIL 29, 2016

Applies to:

Oracle Application Install - Version 12.0.0 to 12.1 [Release 12]
Information in this document applies to any platform.
***Checked for relevance on 22-Feb-2013***


Symptoms


After fresh install of R12, when attempting to start the concurrent manager, it fails with the following error:

In Event Viewer:

FNDLIBR Stopped(1)


In concurrent manager log file:

The ICM has lost its database connection and is shutting down.
Spawning reviver process to restart the ICM when the database becomes available again.

usdipe: error inserting data: ORA-3114

usdsop: Error inserting into FND_CONC_NT_PROCESSES:
The operation completed successfully.


Unable to spawn reviver process.
The ICM will need to be restarted manually when the database becomes available again.
Cannot delete the file TempFileName1.

Check that you have privileges to delete files in the file directory. Contact your system administrator to obtain delete privileges. If your file contains secure data, be sure to delete it manually, fr
List of errors encountered:
.............................................................................

_ 1 _
Routine AFPCMT encountered an ORACLE error. ORA-01012: not logged on.

Review your error messages for the cause of the error. (=<POINTER>)

_ 2 _
Routine AFPCSQ encountered an ORACLE error. ORA-12705: invalid or
unknown NLS parameter value specified
.

Review your error messages for the cause of the error. (=<POINTER>)
.............................................................................


APP-FND-01388: Cannot read value for profile option CONC_GSM_ENABLED in routine &ROUTINE.

List of errors encountered:
.............................................................................

_ 1 _
Routine AFPCAL received failure code while parsing or running your
concurrent program CPMGR

Review your concurrent request log file for more detailed information.
Make sure you are passing arguments in the correct format.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms