Em alguns momentos quando realizamos o procedimento de Cutover no EBS 12.2, podemos nos deparar com algum tipo de problema, um deles é o erro abaixo:
Waiting for ICM to go down... [UNEXPECTED]Error while trying to find the status of ICM [UNEXPECTED]Error occurred while waiting for ICM to go down [UNEXPECTED]Cutover phase completed with errors/warnings. Please check logfiles [STATEMENT] Please run adopscanlog utility, using the command
Esse erro pode ocorrer se o gerenciador de concurrent estiver fora ou se tivermos algum problema na configuração do arquivo .dbc no diretório $FND_SECURE
[applzmuser@zmsolution ~]$ adop phase=cutover Enter the APPS password: Enter the SYSTEM password: Enter the WLSADMIN password: Validating credentials... Initializing... Run Edition context : /ebs/fs1/inst/apps/ebszm_ebszm/appl/admin/ebszm_ebszm.xml Patch edition context: /ebs/fs2/inst/apps/ebszm_ebszm/appl/admin/ebszm_ebszm.xml Patch file system freespace: 92.56 GB Validating system setup... Node registry is valid. Checking for pending adop sessions... Continuing with existing session [Session id: 159]... Session Id : 159 Prepare phase status : COMPLETED Apply phase status : COMPLETED Cutover phase status : NOT COMPLETED Abort phase status : NOT COMPLETED Session status : FAILED =========================================================================== ADOP (C.Delta.6) Session ID: 159 Node: ebsqa Phase: cutover Log: /ebs/fs_ne/EBSapps/log/adop/159/adop_20180802_150633.log =========================================================================== Validating configuration on node: [ebszm]... Log: /ebs/fs_ne/EBSapps/log/adop/159/cutover_20180802_150633/ebsqa_ebsqa Checking if finalize required... Finalize phase steps are not required Submitting request for ICM shutdown... cp wait parameter passed with value: N\n You are running adcmctl.sh version 120.19.12020000.4 Shutting down concurrent managers for ebsqa ... ORACLE Password: Submitted request 87111032 for CONCURRENT FND SHUTDOWN adcmctl.sh: exiting with status 0 adcmctl.sh: check the logfile /ebs/fs1/inst/apps/ebszm_ebszm/logs/appl/admin/log/adcmctl.txt for more information ... Cancelling ADZDPATCH concurrent request Waiting for ICM to go down... [UNEXPECTED]Error while trying to find the status of ICM [UNEXPECTED]Error occurred while waiting for ICM to go down [UNEXPECTED]Cutover phase completed with errors/warnings. Please check logfiles [STATEMENT] Please run adopscanlog utility, using the command "adopscanlog -latest=yes" to get the list of the log files along with snippet of the error message corresponding to each log file. files
para a resolução do problema sera necessário primeiro avaliar se o gerenciador de concurrent está no ar, se o gerenciador estiver funcionando corretamente , valide se o valor do campo APPL_SERVER_ID no arquivo .dbc na estrutura de RUN e PATCH
. EBSapp. env run
$FND_TOP/bin/FNDSVCRG STATUS Internal Concurrent Manager is Active.
. EBSapp. env patch
$FND_TOP/bin/FNDSVCRG STATUS Cannot complete applications logon. You may have entered an invalid applications password, or there may have been a database connect error. Internal Concurrent Manager status could not be determined.
Verifiquei o valor da coluna APPL_SERVER_ID na tabela applsys.fnd_nodes
sqlplus apps SQL*Plus: Release 10.1.0.5.0 - Production on Fri Aug 3 08:43:49 2018 Copyright (c) 1982, 2005, Oracle. All rights reserved. Enter password: Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production With the Partitioning, Real Application Clusters, Automatic Storage Management, Oracle Label Security, OLAP, Data Mining and Real Application Testing options SQL> select server_id from applsys.fnd_nodes; SERVER_ID ---------------------------------------------------------------- SECURE 722E8412DCAB8F63E0538D01708F028D24162238051198027825100192524733 SQL>
entre no diretório $FND_SECURE na estrutura de patch e run e altere o valor do campo APPL_SERVER_ID para o valor que tivemos no resultado da consulta.
cd $FND_SECURE vi ebszm.dbc #DB Settings #Tue Jul 24 15:03:22 BRT 2018 GUEST_USER_PWD=GUEST/ORACLE #APPL_SERVER_ID=71BE0D7E66478D75E0538D01708F8FDB21425765111287829683284799685973 APPL_SERVER_ID=722E8412DCAB8F63E0538D01708F028D24162238051198027825100192524733 FND_JDBC_BUFFER_DECAY_INTERVAL=300 APPS_JDBC_DRIVER_TYPE=THIN FND_JDBC_BUFFER_MIN=1 GWYUID=APPLSYSPUB/PUB FND_JDBC_BUFFER_MAX=5 APPS_JDBC_URL=jdbc\:oracle\:thin\:@(DESCRIPTION\=(ADDRESS_LIST\=(LOAD_BALANCE\=YES)(FAILOVER\=YES)(ADDRESS\=(PROTOCOL\=tcp)(HOST\=zmsolution.unimedfortaleza.com.br)(PORT\=1527)))(CONNECT_DATA\=(SERVICE_NAME\=ebszm))) FND_JDBC_STMT_CACHE_SIZE=100 TWO_TASK=ebszm JDBC\:oracle.jdbc.maxCachedBufferSize=358400 JDBC\:processEscapes=true FND_MAX_JDBC_CONNECTIONS=500 FND_JDBC_USABLE_CHECK=false FNDNAM=APPS FND_JDBC_PLSQL_RESET=false DB_PORT=1521 FND_JDBC_CONTEXT_CHECK=true FND_JDBC_BUFFER_DECAY_SIZE=5 DB_HOST=zmsolution.unimedfortaleza.com.br
salve as alterações e teste novamente.
$FND_TOP/bin/FNDSVCRG STATUS Internal Concurrent Manager is Active.
$FND_TOP/bin/FNDSVCRG STATUS Internal Concurrent Manager is Active.