Monthly Archives: May 2015

How to resolve Oracle BIAPPS Errors – BIACM0085 – BIACM0080?

rencontre avec joe black Issue

Trying to submit the Load Plan from Oracle BI Applications Configuration Setup Manager and gets an error [BIACM0080] Cause: Application error: Failed to access the WSDL at: http://localhost:15001/oraclediagent/OdiInvoke?wsdl.

sites Error

[BIACM0085] Error executing load plan. Action: Correct the properties selected or entered and retry.

Error     

[BIACM0080] Cause: Application error: Failed to access the WSDL at: http://localhost:15001/oraclediagent/OdiInvoke?wsdl. It failed with: Tried all: ‘1’ addresses, but could not connect over HTTP to server: ‘localhost’, port: ‘15001’. Action: Contact your help desk or system administrator.

More Help Reason

The BIACSM is unable to contact the ODI Agent Webservice

dating sites spiritual uk Solution

Check if the ODI server is running. Otherwise start the ODI server and try submitting the Load Plan.

 

Adding WLS Managed Servers in E-Business12.2 Cluster

rencontre et amitié lescar Why Add Managed Servers?   Application Tier Vertical Scaling: To add additional services to the existing node for meeting load and user concurrency requirements.

http://szerencs.hu/trevel/1636 How to Add Managed Servers?

Managed Server creation is done through the script  ‘adProvisionEBS.pl’. Managed servers should not be created from the Web Logic Server Administration Console.

When you execute the ‘adProvisionEBS.pl’, this will create a managed server and add a new entry to the context file.Managed Server name must be of the form _server, for example oacore_server2. Execute the adProvisionEBS.pl on the run file system only when there is no active ADOP cycle.

Before you prepare, verify the free port numbers and unique across the RUN and PATCH file systems. No two managed servers across the run and patch file systems can have the same port number.

their website Command :

$ perl /patch/115/bin/adProvisionEBS.pl \
ebs-create-managedserver -contextfile= \
-managedsrvname= -servicetype= \
-managedsrvport= -logfile=

see post Usage to add additional OACORE Server:

$ perl /patch/115/bin/adProvisionEBS.pl \
ebs-create-managedserver -contextfile= \
-managedsrvname=oacore_server2 -servicetype=oacore \
-managedsrvport=7203 -logfile=/TXK/addMS_oacoreserver2.log

During the next ADOP prepare phase, the configuration change detector identifies that the new node has been added and managed servers are automatically synced up from run file system to the patch file system.

Start the newly added Managed Server ‘oacore_server2’
sh /admanagedsrvctl.sh start oacore_server2

Perform the below steps on all the  application tier nodes participating in the same cluster.

1. Source the run file system.
2. Run txkSetAppsConf.pl to add details of the newly added managed servers into the OHS configuration files mod_wl_ohs.conf and apps.conf on the current node
$ perl /patch/115/bin/txkSetAppsConf.pl -contextfile= \
-configoption=addMS -oacore=oragurus.com:7205
3. If Oracle HTTP server is enabled, restart as below

sh /adapcctl.sh stop
sh /adapcctl.sh start