GET_SM_INFO Failed Due to ORA-01422: Exact Fetch Returns More Than Requested Number of Rs

GET_SM_INFO Failed Due to ORA-01422: Exact Fetch Returns More Than Requested Number of Rs [ID ow289817.1]
  Modified 28-DEC-2009     Type PROBLEM     Status ARCHIVED

Checked for relevance on 28-DEC-2009
Applications Install - 11.5.8 to 11.5.10

SYMPTOMS:
=========

Starting the Concurrent Managers with profile option 'Concurrent:GSM Enabled'set to'Y'
generates the following error:

ORACLE error 1422 in get_sm_info

Cause:  get_sm_info failed due to ORA-1422: exact fetch returns more than
requested number of rows.

The SQL statement being executed at the time of the error was: select
FND_CONCURRENT_PROCESSES_S.nextval
Could not initialize the Service Manager FNDSM__prod. Verify
that  has been registered for concurrent processing.
ORACLE error 1427 in cleanup_node

Cause:  cleanup_node failed due to ORA-1427: single-row subquery returns more
than one row
ORA-6512: at "APPS.FND_CP_FNDSM", line 29
ORA-6512: at line 1.

Routine AFPEIM encountered an error while starting concurrent manager
FNDLIBR101 with library /proda/mtaprod/mtaprodappl/fnd/11.5.0/bin/FNDLIBR.

Check that your system has enough resources to start a concurrent manager
process.

CAUSE:
======

SQL> select concurrent_queue_name, node_name from fnd_concurrent_queues where
     manager_type=6;

CONCURRENT_QUEUE_NAME          NODE_NAME
------------------------------ ------------------------------
FNDSM_SYSADMIN-SUN             SYJONES-SUN
FNDSM_AOLESC2-SUN              SYJONES-SUN
FNDSM_SYJONES-SUN              SYJONES-SUN

There is more than one FNDSM Concurrent Queue defined to run
on Node SYJONES-SUN.

This is a result of performing a clone from SYSADMIN-SUN & AOLESC2-SUN
to SYJONES-SUN and carrying over the Source machine names as
FNDSM concurrent queues.


SOLUTION:
=========

SQL> EXEC FND_CONC_CLONE.SETUP_CLEAN;
     COMMIT;
     EXIT;


Re-run AutoConfig.