I have this error on my Concurrent log file after R12.1.1 fresh installation on RHEL4u8

After R12.1.1 fresh installation on Linux, Concurrent Managers dont be up, all Concurrent Manager’s target and actual status are 0

Even i started cm manualy,it doesnt work.While i was check CM log under $INST_TOP/logs/appl/conc/log i faced below error message in log file:

APP-FND-01564: ORACLE error 12899 in insert_icm_record

Cause: insert_icm_record failed due to ORA-12899: value too large for column “APPLSYS”.”FND_CONCURRENT_PROCESSES”.”NODE_NAME” (actual: 31, maximum: 30).

The SQL statement being executed at the time of the error was: INSERT   INTO FND_CONCURRENT_PROCESSES       (CONCURRENT_PROCESS_ID, LAST_UPDATE_DATE,        CREATION_DATE,         CREATED_BY,        LAST_UPDATED_BY,       ORACLE_PROCESS_ID,        QUEUE_APPLICATION_ID,  CONCURRENT_QUEUE_ID,        OS_PROCESS_ID,         SESSION_ID,        PROCESS_START_DATE,    PROCESS_STATUS_CODE,        MANAGER_TYPE,          NODE_NAME,        DB_NAME,               DB_DOMAIN,        SQLNET_STRING,         DB_INSTANCE,        Instance_Number) VALUES       (: cpid,                 SYSDATE,        SYSDATE,               : mgrusrid,        : mgrusrid2,            : opid,        : qappid,               :q id,        : ospid,                : osid,        SYSDATE,               ‘A’,        0,                     : node,        :dbname,               :dbdomain,        :dbinst, (Select instance_name from v$instance),        (Select instance_number from v$instance))  and was executed from the file &ERRFILE.

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.
…………………………………………………………………..

The SID_0903@SID internal concurrent manager has terminated with status 1 – giving up.

I checked  my hostname.domainname size and its more than 30 character. This issue already report on below metalink note:

Concurrent Managers Fail To Start After New Install of Release 12 [ID 413164.1]

I already opened SR for to can see is there any chance to fix this issue without chancing hostname, but Oracle support gave that answer:

According to:
Oracle® Applications
System Administrator’s Guide – Configuration
Release 12.1
Part No. E12893-02
page 7-35 this is not possible :

Note : Start your concurrent managers on machines with hostnames of 30 or fewer characters. Managers may fail to start on machines with longer hostnames.

For can change hostname please follow below notes:

How to change the hostname and/or port of the Database Tier using AutoConfig [ID 338003.1]
How to change the hostname of an Applications Tier using AutoConfig [ID 341322.1]

Advertisements