Discoverer responsibility errors out with Empty Input (Or Null) Is Not Allowed error

We had first cutover after 12.2 patching in production instance  , After the cutover, When instance is released to client, Client was getting the below error while accessing discoverer using the responsibility from EBS.




We observed that the both the discoverer URL and EBS URL are in different domain which caused the issue
1. We changed the discoverer profile options in EBS and also updated the context file with the updated discoverer urls
From -
ICX: Discover Launcher – http://test001.test.com:8090/discoverer/plus?Connect=[APPS_SECURE]
ICX :Discover Viewer Launcher http://test001.test.com:8090/discoverer/viewer?Connect=[APPS_SECURE]

To –

ICX:Discoverer Launcher - http://test001.testnet.com:8090/discoverer/plus?Connect=[APPS_SECURE]
ICX :Discover Viewer Launcher http://test001.testnet.com:8090/discoverer/viewer?Connect=[APPS_SECURE]

Update the below context file entry to new URL
-bash-4.1$ grep  s_disco $CONTEXT_FILE
         <disco_url oa_var="s_disco_url">http://test001.testnet.com:8090</disco_url>

2. After changing the context file entry,Bring down application services and run autoconfig
3. Also Added below lines related to virtual host  to /app01/oracle/fmw/asinst_1/config/OHS/ohs1/httpd.conf on test001
 
NameVirtualHost \*:8090
<VirtualHost *:8090>
   ServerName http://test001.testnet.com
    RewriteEngine On
    RewriteOptions inherit
    UseCanonicalName On
</VirtualHost>
 
4. Restarted opmn on discoverer server and we are able to access discoverer.

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

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

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