MWA Dispatcher does Not Start In R12.2.3 Error: could not read config file


1.In one of our 12.2.3 instance we observed that the mwa dispatcher was not coming up ,When we have checked the log file we found the below segmentation faults errors
/TEST/app01/appl/fs2/inst/apps/TEST_test001/admin/scripts/mwactl.sh: line 237: 17932 Segmentation fault      ${MWA_TOP}/bin/MWADIS
2.We checked for the dispatcher port and it was available
[appltest@test001]$ netstat -anp |grep 10616
(Not all processes could be identified, non-owned process info
 will not be shown, you would have to be root to see it all.)
3. This issue is documented in Internal Bug 17459700  - MWACTL.SH START_DISPATCHER CAN NOT BE STARTED.
smwaenv.h has been rebuilt and sets the relative path of mwa.cfg to  "/admin/install/mwa.cfg"
4. Observed that patch is not applied in our instance

SQL> select bug_number,creation_date from apps.ad_bugs where bug_number='17459700';

no rows selected

SQL> select name from v$database;
NAME
---------
TEST

5.After applying the patch using adop we were able to start the MWA without any issues.

Comments

Post a Comment

Popular posts from this blog

Steps to run Autoconfig for patch File system 12.2

1.       To run Autoconfig from the patch file system you must disable trigger ebs_login prior to running autoconfig. SQL> show user; USER is "SYSTEM" SQL> alter trigger ebs_logon disable; Trigger altered. 2.       Now run autoconfig with the patch env sourced [appltest@test001]$ echo $FILE_EDITION [appltest@test001]$patch [appltest@test001]$ adautocfg.sh Make sure Autoconfig completes ok      3. Enable the login trigger “alter trigger ebs_logon enable”                  SQL> conn system/Oracle4u                  Connected.                SQL> SQL> alter trigger ebs_logon enable;                 Trigger altered.
Read more

ADOP fs_clone failing with ERROR: Managed Server's are not in sync between file system context and DB context

 adop fs_clone failing with below error. +++++++++++++++++++++++++ configProperty id = Server11 Count for NodeIterator nextNode = 3 ERROR: Managed Server's are not in sync between file system context and DB context ERROR: Update Moveplan Fail START: Inside exitClone.... Updating status INCOMPLETE for ApplywlsTechStack START: Updating status INCOMPLETE for action ApplywlsTechStack END: Updated status INCOMPLETE for action ApplywlsTechStack SOLUTION Please follow the solution in  Doc ID 2232990.1  and advise accordingly To resolve the issue test the following steps in a development instance and then migrate accordingly: 1. Unlock the configuration in the weblogic console via the following steps: A. Open a browser and enter the weblogic console URL eg: https ://localhost:port/console as the administrator. B. Navigate to the weblogic server administration Applications Configuration console. C. Unlock the weblogic server configuration by clicking 'Release Configuration' option.
Read more

txkCfgUtlfileDir.pl -mode=getUtlFileDir as per Cloning Oracle E-Business Suite Release 12.1 with Multitenant Database using Rapid Clone (Doc ID 2560690.1) errors with ERRORMSG: Invalid APPS database user credentials

 txkCfgUtlfileDir.pl -mode=getUtlFileDir as per Cloning Oracle E-Business Suite Release 12.1 with Multitenant Database using Rapid Clone (Doc ID 2560690.1) errors with ERRORMSG: Invalid APPS database user credentials validate_apps_password.log Pattern found... ================ EXIT STATUS: 1 Invalid APPS database user credentials. Solution Check  lsnrctl status <listener_name>,check files under $TNS_ADMIN,check environment,Check if case sensitive login is enabled and if enabled,disable it
Read more