{"id":2284,"date":"2018-08-03T10:10:28","date_gmt":"2018-08-03T13:10:28","guid":{"rendered":"https:\/\/zmsolution.laraclaud.com.br\/?p=2284"},"modified":"2018-08-03T10:10:28","modified_gmt":"2018-08-03T13:10:28","slug":"error-occurred-while-waiting-for-icm-to-go-down","status":"publish","type":"post","link":"http:\/\/zmsolution.com\/error-occurred-while-waiting-for-icm-to-go-down\/","title":{"rendered":"Error occurred while waiting for ICM to go down"},"content":{"rendered":"
Em alguns momentos quando realizamos o\u00a0procedimento de Cutover<\/strong> no EBS 12.2<\/strong>, podemos nos deparar com algum tipo de problema, um deles\u00a0 \u00e9 o erro abaixo:<\/p>\n Esse erro pode ocorrer se o gerenciador de concurrent estiver fora ou se tivermos algum problema na configura\u00e7\u00e3o do arquivo\u00a0.dbc no diret\u00f3rio\u00a0$FND_SECURE<\/strong><\/p>\n para a resolu\u00e7\u00e3o do problema sera necess\u00e1rio primeiro avaliar se o\u00a0 gerenciador de concurrent est\u00e1 no ar, se o gerenciador estiver funcionando corretamente , valide se o valor do campo\u00a0APPL_SERVER_ID<\/strong> no arquivo .dbc<\/strong> na estrutura de RUN<\/strong> e PATCH<\/strong><\/p>\n . EBSapp. env\u00a0 run<\/strong><\/p>\n . EBSapp. env\u00a0\u00a0patch<\/strong><\/p>\n Verifiquei o valor da coluna\u00a0APPL_SERVER_ID<\/strong>\u00a0 na tabela\u00a0applsys.fnd_nodes<\/p>\n entre no diret\u00f3rio\u00a0$FND_SECUR<\/strong>E na estrutura de patch<\/strong> e run<\/strong> e altere o valor do campo\u00a0APPL_SERVER_ID<\/strong>\u00a0 para o valor que tivemos no resultado da consulta.<\/p>\n salve as altera\u00e7\u00f5es e\u00a0teste novamente.<\/p>\n <\/p>\n","protected":false},"excerpt":{"rendered":" Em alguns momentos quando realizamos o\u00a0procedimento de Cutover no EBS 12.2, podemos nos deparar com algum tipo de problema, um deles\u00a0 \u00e9 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[…]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_mi_skip_tracking":false,"_exactmetrics_sitenote_active":false,"_exactmetrics_sitenote_note":"","_exactmetrics_sitenote_category":0},"categories":[20],"tags":[],"jetpack_featured_media_url":"","_links":{"self":[{"href":"http:\/\/zmsolution.com\/wp-json\/wp\/v2\/posts\/2284"}],"collection":[{"href":"http:\/\/zmsolution.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/zmsolution.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/zmsolution.com\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"http:\/\/zmsolution.com\/wp-json\/wp\/v2\/comments?post=2284"}],"version-history":[{"count":0,"href":"http:\/\/zmsolution.com\/wp-json\/wp\/v2\/posts\/2284\/revisions"}],"wp:attachment":[{"href":"http:\/\/zmsolution.com\/wp-json\/wp\/v2\/media?parent=2284"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/zmsolution.com\/wp-json\/wp\/v2\/categories?post=2284"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/zmsolution.com\/wp-json\/wp\/v2\/tags?post=2284"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Waiting for ICM to go down...\r\n[UNEXPECTED]Error while trying to find the status of ICM\r\n[UNEXPECTED]Error occurred while waiting for ICM to go down\r\n[UNEXPECTED]Cutover phase completed with errors\/warnings. Please check logfiles\r\n[STATEMENT] Please run adopscanlog utility, using the command<\/pre>\n
[applzmuser@zmsolution ~]$ adop phase=cutover\r\n\r\nEnter the APPS password:\r\nEnter the SYSTEM password:\r\nEnter the WLSADMIN password:\r\n\r\nValidating credentials...\r\n\r\nInitializing...\r\nRun Edition context : \/ebs\/fs1\/inst\/apps\/ebszm_ebszm\/appl\/admin\/ebszm_ebszm.xml\r\nPatch edition context: \/ebs\/fs2\/inst\/apps\/ebszm_ebszm\/appl\/admin\/ebszm_ebszm.xml\r\nPatch file system freespace: 92.56 GB\r\n\r\nValidating system setup...\r\nNode registry is valid.\r\n\r\nChecking for pending adop sessions...\r\nContinuing with existing session [Session id: 159]...\r\nSession Id : 159\r\nPrepare phase status : COMPLETED\r\nApply phase status : COMPLETED\r\nCutover phase status : NOT COMPLETED\r\nAbort phase status : NOT COMPLETED\r\nSession status : FAILED\r\n\r\n===========================================================================\r\nADOP (C.Delta.6)\r\nSession ID: 159\r\nNode: ebsqa\r\nPhase: cutover\r\nLog: \/ebs\/fs_ne\/EBSapps\/log\/adop\/159\/adop_20180802_150633.log\r\n===========================================================================\r\n\r\nValidating configuration on node: [ebszm]...\r\nLog: \/ebs\/fs_ne\/EBSapps\/log\/adop\/159\/cutover_20180802_150633\/ebsqa_ebsqa\r\n\r\nChecking if finalize required...\r\nFinalize phase steps are not required\r\n\r\nSubmitting request for ICM shutdown...\r\ncp wait parameter passed with value: N\\n\r\n\r\nYou are running adcmctl.sh version 120.19.12020000.4\r\n\r\nShutting down concurrent managers for ebsqa ...\r\nORACLE Password:\r\nSubmitted request 87111032 for CONCURRENT FND SHUTDOWN\r\nadcmctl.sh: exiting with status 0\r\nadcmctl.sh: check the logfile \/ebs\/fs1\/inst\/apps\/ebszm_ebszm\/logs\/appl\/admin\/log\/adcmctl.txt for more information ...\r\n\r\nCancelling ADZDPATCH concurrent request\r\n\r\nWaiting for ICM to go down...\r\n[UNEXPECTED]Error while trying to find the status of ICM\r\n[UNEXPECTED]Error occurred while waiting for ICM to go down\r\n[UNEXPECTED]Cutover phase completed with errors\/warnings. Please check logfiles\r\n[STATEMENT] Please run adopscanlog utility, using the command\r\n\r\n\"adopscanlog -latest=yes\"\r\n\r\nto get the list of the log files along with snippet of the error message corresponding to each log file.\r\n\r\nfiles<\/pre>\n
$FND_TOP\/bin\/FNDSVCRG STATUS\r\nInternal Concurrent Manager is Active.<\/pre>\n
$FND_TOP\/bin\/FNDSVCRG STATUS\r\nCannot complete applications logon. You may have entered an invalid applications password, or there may have been a database connect error.\r\nInternal Concurrent Manager status could not be determined.<\/pre>\n
sqlplus apps\r\n\r\nSQL*Plus: Release 10.1.0.5.0 - Production on Fri Aug 3 08:43:49 2018\r\n\r\nCopyright (c) 1982, 2005, Oracle. All rights reserved.\r\n\r\nEnter password:\r\n\r\nConnected to:\r\nOracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production\r\nWith the Partitioning, Real Application Clusters, Automatic Storage Management, Oracle Label Security,\r\nOLAP, Data Mining and Real Application Testing options\r\n\r\nSQL> select server_id from applsys.fnd_nodes;\r\n\r\nSERVER_ID\r\n----------------------------------------------------------------\r\nSECURE\r\n\r\n722E8412DCAB8F63E0538D01708F028D24162238051198027825100192524733\r\n\r\nSQL><\/pre>\n
cd $FND_SECURE\r\n\r\nvi ebszm.dbc\r\n\r\n#DB Settings\r\n#Tue Jul 24 15:03:22 BRT 2018\r\nGUEST_USER_PWD=GUEST\/ORACLE\r\n#APPL_SERVER_ID=71BE0D7E66478D75E0538D01708F8FDB21425765111287829683284799685973\r\nAPPL_SERVER_ID=722E8412DCAB8F63E0538D01708F028D24162238051198027825100192524733\r\nFND_JDBC_BUFFER_DECAY_INTERVAL=300\r\nAPPS_JDBC_DRIVER_TYPE=THIN\r\nFND_JDBC_BUFFER_MIN=1\r\nGWYUID=APPLSYSPUB\/PUB\r\nFND_JDBC_BUFFER_MAX=5\r\nAPPS_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)))\r\nFND_JDBC_STMT_CACHE_SIZE=100\r\nTWO_TASK=ebszm\r\nJDBC\\:oracle.jdbc.maxCachedBufferSize=358400\r\nJDBC\\:processEscapes=true\r\nFND_MAX_JDBC_CONNECTIONS=500\r\nFND_JDBC_USABLE_CHECK=false\r\nFNDNAM=APPS\r\nFND_JDBC_PLSQL_RESET=false\r\nDB_PORT=1521\r\nFND_JDBC_CONTEXT_CHECK=true\r\nFND_JDBC_BUFFER_DECAY_SIZE=5\r\nDB_HOST=zmsolution.unimedfortaleza.com.br<\/pre>\n
$FND_TOP\/bin\/FNDSVCRG STATUS\r\nInternal Concurrent Manager is Active.<\/pre>\n
$FND_TOP\/bin\/FNDSVCRG STATUS\r\nInternal Concurrent Manager is Active.<\/pre>\n