DOYENSYS Knowledge Portal




We Welcome you to visit our DOYENSYS KNOWLEDGE PORTAL : Doyensys Knowledge Portal




Wednesday, June 14, 2017

Cause: cleanup_node failed due to ORA-01427

Scenario:
------------

The concurrent requests are going to Error in R12.2.5 and cannot view the log files as well.


Error:
------

Cause: cleanup_node failed due to ORA-01427: single-row subquery returns more than one row
ORA-06512: at "APPS.FND_CP_FNDSM", line 91
ORA-06512: at line 1.

The SQL statement being executed at the time of the error was: begin fnd_cp_fndsm.mark_killed_fndsm(:nn); end;  and was executed from the file &ERRFILE.
Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /test/app/fs2/EBSapps/appl/fnd/12.0.0/bin/FNDLIBR.

Check that your system has enough resources to start a concurrent manager process. Contact your system : 13-JUN-2017 22:28:18
Starting STANDARD Concurrent Manager               : 13-JUN-2017 22:28:18

Could not initialize the Service Manager FNDSM_DOYSER_DEV. Verify that DOYSER has been registered for concurrent processing.
An error occured in client-side routine afpsmcsm for Service Manager FNDSM_DOYSER_DEV.  The routine returned code 126.

Check for preceding errors and as well as the service manager log file for further details."

ORACLE error 1427 in cleanup_node


Cause:
---------

After clone the node is not cleaned up which has the old values.

Solution:
----------

1. Shutdown the apps node.
2. login to db node and run the following.

sqlplus apps/apps

sql>exec fnd_conc_clone.setup_clean;

commit;

sql>@cmclean.sql

3. Run autoconfig in db tier.
4. Run autoconfig in the apps tier and start the services.

This should be fixed.

1 comment:

sunitha vishnu said...

It is amazing and wonderful to visit your site.Thanks for sharing this information,this is useful to me...
Android Training in Chennai
Ios Training in Chennai