Installation Troubleshooting

PROCESSIT Installer

Domain Edit Lock when installing to WebLogic

If WebLogic believes there are pending changes, it will not allow the PROCESSIT installer to deploy any components to the WebLogic server. Clearing the lock will allow the installer to deploy the components.

Log on to the WebLogic console [http://weblogic:7001/console]
Click the Activate Changes button.
If the Activate Changes button is still visible, click the Undo All Changes button.
Continue with install

Error reading WSDL when deploying a BPEL component

Caching can cause the WSDL being read to differ from the definition expected. Restarting SOA Suite should clear this error

Stop SOA Suite
Start SOA Suite
Continue with install

Database Link Name conventions

To accommodate the PROCESSIT Installer, the PROCESSIT Database Name should not contain global name. No FQDN is required. When the Database Link is created, it should have the name EBSDB. If global name is used, the Database Link is named EBSDB.[domain] and the PROCESSIT installer fails.

If you insist on using a global name for the PROCESSIT database, you should set the database parameter GLOBAL_NAME to FALSE.

Oracle SOA server

Increasing expirationAgent Threads

Having an insufficient amount of expirationAgent threads configured can occasionally cause some issues with BPEL wait timers. An issue can occur where they fail to repsond to the BPEL process at the correct time. Increasing the number of expirationAgent threads may help.

Stop the SOA Suite
Edit the file [as.root]/bpel/domains/services/config/resources-quartz.properties
Look for the property com.oracle.bpel.expirationAgent.threadCount and change it from its default value of 10 to 100.
Restart the SOA Suite

Known errors with ESB

ESB Design Time Repository Fails To Start When It Is In Same Container As BPEL [ID 752385.1]

When you log into ESB console, click on DefaultSystem and click on Apply (without changing anything), you get the following error:

				An unhandled exception has been thrown in the ESB system.  
				The exception reported is: "oracle.tip.esb.console.exception.ConsoleTransactionException: File repository not initialized.  
				May be ESB bootstrap failed Please review ESB prameters for their correctness.  
				at oracle.tip.esb.console.XMLConsoleManagerImpl.commit(XMLConsoleManagerImpl.java:2292)  
				at oracle.tip.esb.console.XMLConsoleManagerImpl.updateSystemInRepository(XMLConsoleManagerImpl.java:879 )  
				at oracle.tip.esb.console.XMLConsoleManagerImpl.updateSystemFromElement(XMLConsoleManagerImpl.java:575)  
				at oracle.tip.esb.console.XMLConsoleManagerImpl.updateSystem(XMLConsoleManagerImpl.java:553)  
				at oracle.tip.esb.configuration.servlet.command.UpdateSystemCommand.execute(UpdateSystemCommand.java:61 )  
				at oracle.tip.esb.configuration.servlet.CommandServlet.doJob(CommandServlet.java:109)  
				at oracle.tip.esb.configuration.servlet.CommandServlet.doPost(CommandServlet.java:76)  
				at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)

When you register ESB project from JDeveloper, you get the following error:

				error code: 0 : 10 summary: An unhandled exception has been thrown in the ESB system.  
				The exception reported is: "oracle.tip.esb.console.exception.ConsoleTransactionException: File repository not initialized.  
				May be ESB bootstrap failed Please review ESB prameters for their correctness.  
				at oracle.tip.esb.console.XMLConsoleManagerImpl.commit(XMLConsoleManagerImpl.java:2292)  
				at oracle.tip.esb.configuration.deployment.JDevDeploymentManager.deploy(JDevDeploymentManager.java:223)  
				at oracle.tip.esb.configuration.deployment.DeploymentServlet.doPost(DeploymentServlet.java:120)  
				at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)

ESB container log.xml has following entry:

You can also see from logs that ESB hangs before initializing (bootstrap) itself. Thread dump shows most threads are in object.wait waiting on condition.

				<MSG_TEXT>Unable to get connection to Repository Ensure repository is accessible</MSG_TEXT>    
				<MSG_TEXT>WSDL parsing failed :unknown protocol: esb</MSG_TEXT>    
				<SUPPL_DETAIL><![CDATA[java.net.MalformedURLException: unknown protocol: esb    
				at java.net.URL.<init>(URL.java:574)    
				at java.net.URL.<init>(URL.java:464)    
				at java.net.URL.<init>(URL.java:413)    
				at oracle.tip.esb.model.entity.Service.loadWSDLOperations(Service.java:128)    
				at oracle.tip.esb.model.entity.ServiceOperation.getFaults(ServiceOperation.java:161)    
				at oracle.tip.esb.console.util.XMLGenerator.buildOperationXML(XMLGenerator.java:602)

This issue is as a result of ESB DT, RT and BPEL being in same container as part of SOA advanced install. The error 'java.net.MalformedURLException: unknown protocol: esb' is as a result of BPEL(orabpel) loading before ESB and trying to access the ESB WSDLs which are not yet available, as the ESB has not yet initialized itself successfully.ESB server itself is not starting up successfully because the URL ping gets over before it could initialize itself.

This issue can be solved by:

Version 10.1.3.3: Apply at least MLR #15 and then follow the guide below.
Version 10.1.3.4: The fix is already available, so just follow the guide below.

Set appropriate values for following parameters in esb_config.ini or orion-application.xml file. Default is 15 for both values. PingInterval is measured in seconds.

PingCount = 30 PingInterval = 30

The orion-application.xml that needs to be updated are in the RT and DT applications:

$OH/j2ee/oc4j_soa/application-deployments/esb-dt/orion-application.xml
$OH/j2ee/oc4j_soa/application-deployments/esb-rt/orion-application.xml
The esb_config.ini is in $OH/integration/esb/config/esb_config.ini

Oracle BPEL error on increased load

For this error in a service:

exception on JaxRpc invoke: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Message send failed: Premature EOF encountered

Change opmn.xml in the opmn/conf directory of your Oracle Application Server. Set the startup parameter for the SOA suite to -DHTTPClient.disableKeepAlives=true

Callback Skipped in Audit Trail

If some BPEL services are not working (for example INBOUND_TRANSFORMATION) and in the BPEL console audit trail you find a callback skipped message where an asynchronous service call was supposed to call back.

This is due to the BPEL callback URL in BPELAdmin being incorrect. You can solve this by:

Open BPELAdmin.
Make sure that the hostname in the following properties matches exactly the hostname used in the configuration properties file used during installation:
- clusterName
- jndiProviderURL
- soapCallbackUrl
- soapServerUrl
Restart the SOA server.

For example, if the hostname used in the installation configuration properties file was soa.vm.net:7777 then the hostname in the above properties must match this exactly. Be sure to only replace the hostname and leave the rest of the URL intact.

Checking patch inventory

The patch level for the SOA server should be consistent with the supported level of PROCESSIT. To confirm your patch level, the following should match:

					
[oracle@processit OPatch]$ ./opatch lsinventory

	Oracle Interim Patch Installer version 11.2.0.1.9
	Copyright (c) 2011, Oracle Corporation.  All rights reserved.


	Oracle Home       : /oracle/as/product/10.1.3.1/OracleAS_1
	Central Inventory : /oracle/db/app/oraInventory
	   from           : /oracle/as/product/10.1.3.1/OracleAS_1/oraInst.loc
	OPatch version    : 11.2.0.1.9
	OUI version       : 10.2.0.5.0
	Log file location : /oracle/as/product/10.1.3.1/OracleAS_1/cfgtoollogs/opatch/opatch2012-03-26_12-36-20PM.log

	Lsinventory Output file location : /oracle/as/product/10.1.3.1/OracleAS_1/cfgtoollogs/opatch/lsinv/lsinventory2012-03-26_12-36-20PM.txt

	--------------------------------------------------------------------------------
	Installed Top-level Products (3):

	Oracle Application Server PatchSet                                   10.1.3.5.0
	Oracle Application Server SOA Suite                                  10.1.3.1.0
	Oracle Installation Products                                         10.2.0.5.0
	There are 3 products installed in this Oracle Home.


	Interim patches (3) :

	Patch  12351139     : applied on Sat Mar 24 10:02:31 EDT 2012
	Unique Patch ID:  13650247
	   Created on 12 Apr 2011, 13:53:11 hrs
	   Bugs fixed:
		 10377697, 10115299, 12333903, 10222198
	   This patch overlays patches:
		 9841044
	   This patch needs patches:
		 9841044
	   as prerequisites

	Patch  9841044      : applied on Sat Mar 24 09:44:31 EDT 2012
	Unique Patch ID:  13212929
	   Created on 11 Aug 2010, 00:39:37 hrs PST8PDT
	   Bugs fixed:
		 8993412, 9205098, 8971200, 8969141, 8927114, 8793834, 9408668, 8852540
		 9239826, 9313628, 9732670, 8616966, 9717723, 8859664, 8648362, 9050404
		 8868559, 8897339, 8926178, 9404745, 8978615, 6172404, 8838612, 8325764
		 8739266, 9274887, 8261686, 8675546, 8266337, 8766089, 9051428, 8887792
		 9728585, 9300961, 9665739, 8921814, 9668283, 8889031, 8655511, 8744094
		 8995312, 9285095, 9494939, 9907403, 9018555, 8744456, 8466286, 9397839
		 8718723, 9068677, 9280227, 8397236, 8925453, 9017030, 9569587, 9213052
		 9378247, 9441269, 9172277, 9497125, 9138380, 9008072, 9251016, 9406930
		 8766098, 9218575, 9460287, 9283425, 8898000, 7616012, 8947380, 9180947
		 9343006, 8703955, 8517559, 9201769, 8608385, 10010053, 8799953, 8589810
		 9565232, 9373384, 9219019, 8979866, 9630501, 9439284, 8943177, 6160552
		 9180448, 8830424, 8692187, 9558166, 8627696, 8789547, 8690658, 8925397
		 8808768, 9115164, 8715542, 9315108, 8796047, 9478480, 8944845, 8813808
		 9151169, 9294147, 9789210, 9335867, 9039402, 9437831, 9563641, 9456560
		 8515530, 9149685, 9008596, 9279417, 9024342, 7344498, 9068048, 9371433
		 8486557, 8924025, 9480987, 8758385, 9558829, 8798884, 8775004, 8563198
		 8463690, 8527559, 8979232, 9910874, 9211331, 8813964, 8976472, 9460162
		 9172371, 8692419, 8508180, 9923475, 9320888, 9356858, 8807119, 8856650
		 8932129, 9910805, 8785284, 9027408, 8894329, 8208097, 9845104, 9342162
		 9479590, 8848924, 8652931, 8472594, 9618275, 9007669, 8918056, 8731314
		 8811148, 8859565, 9382012, 8663573, 8678784, 8519043, 9445948, 8421966
		 8829263, 7697054, 8786019, 9279722, 9548645, 8831615, 9817854, 8800153
		 9294317, 9548212, 8734730, 8913481, 9136317, 8873937, 8825348, 8523075
		 9193005, 8871613, 8790266, 8660893, 8880363, 8716883, 8887629, 8865349
		 8975331, 8680421, 8713762, 9023934, 8786533, 8621058, 9085566, 8286429
		 8607120, 8765990, 8934610, 8765991, 8339008, 8683620, 9348930, 9096494
		 8967823, 8892963, 9369338, 8827391, 9681189, 10010465, 8803364, 8743132
		 9131247, 8935562, 8512885, 8579522, 8967109

	Patch  8555288      : applied on Fri Mar 23 21:45:29 EDT 2012
	Unique Patch ID:  11437032
	   Created on 18 Jun 2009, 04:26:45 hrs US/Eastern
	   Bugs fixed:
		 8555288

Error after applying latest patch

As noted earlier, the SOA Server must be installed with Oracle SOA Suite 10.1.3.5.0 and patched to latest MLR# level. Applying these patches can render the BPEL Console inoperable. In this case, the following exception is displayed when viewing the BPEL Console:

Oracle BPEL Server version 10.1.3.4.0

                    Build: 0

                    Build time: Thu Oct 23 22:09:00 PDT 2008

                    Build type: release

                    Source tag: PCBPEL_10.1.3.4.0MLR2_GENERIC_RELEASE

                    Exception Message:

                    [javax.servlet.ServletException]

                    com.collaxa.cube.ejb.impl.BPELProcessManagerBean.getDefaultRevision(com.oracle.bpel.client.BPELProcessId, com.oracle.bpel.client.auth.DomainAuth)

The fix is in the Oracle forums: http://forums.oracle.com/forums/thread.jspa?threadID=829300

Invoice import to Oracle E-Business Suite is stuck

If an invoice is not imported to the Oracle E-Business Suite after a long time and has not failed with any error then it may be stuck in a BPEL wait. It can occur that an otherwise normal invoice is stuck during the import process due to a corruption of the BPEL alarm table.

To free the stuck invoice so it can continue on the import process:

Log on to the BPEL console
Select services from the jump to domain drop-down box in the top-right corner of the page
Click the Administration tab
Click the Actions link
Click the Refresh Alarm Table button

The invoice should now continue importing without further problems. If this issue occurs frequently then increasing the number of expirationAgent threads may help. Please see above for instructions.

BPEL processes not loading or deploying due to memory setting PermGen Space

Edit the file $SOA_HOME/opmn/opmn.xml - remember to make a backup of the file.
Increase the value for MaxPermSize to 768M or 1024M

For instance, in this example, the value is 512 and should be raised:


	<process-type id="oc4j_soa" module-id="OC4J" status="enabled">
	   <module-data>
		  <category id="start-parameters">
<data id="java-options" value="-server -XX:MaxPermSize=512M -ms2048M -mx4096M
-Djava.security.policy=$ORACLE_HOME/j2ee/oc4j_soa/config/java2.policy -Djava.awt.headless=true -Dhttp.webdir.enable=false -Doraesb.home=/oracle/as/product/10.1.3.1/OracleAS_1/integration/esb -Dhttp.proxySet=false -Doc4j.userThreads=true -Doracle.mdb.fastUndeploy=60 -Doc4j.formauth.redirect=true -Djava.net.preferIPv4Stack=true -Doc4j.formauth.redirect=true -Djava.net.preferIPv4Stack=true -Dorabpel.home=/oracle/as/product/10.1.3.1/OracleAS_1/bpel -Xbootclasspath^/p:/oracle/as/product/10.1.3.1/OracleAS_1/bpel/lib/orabpel-boot.jar -Dhttp.proxySet=false -Dstdstream.rotatetime=23:59 -Dstdstream.filenumber=30"/>
<data id="oc4j-options" value="-out $ORACLE_HOME/opmn/logs/default_group~oc4j_soa~default_group.log -err $ORACLE_HOME/opmn/logs/default_group~oc4j_soa~default_group.log"/>
                  </category>

Oracle SOA database

Cannot log into database via listener

Oracle database 10g and above should automatically register itself with the listener process on startup. If this does not occur, this will be seen as the inability to login to the database and the command lsnrctl status returns that the listener supports no services. If this occurs, login to the database server as the user that installed the database (usually oracle) and run "sqlplus / as sysdba". At the SQL> prompt execute:

alter system set local_listener='(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=<dbhostname>)(PORT=<dbport>)))' scope=both;

<dbhostname> is the name or ip address of the database server and <dbport> is the port the database should listen on.

Upon restarting the database and listener, the database should allow connection normally.

Often this is caused by change of hostname, and you can remedy the situation in this way:

Modify listener.ora #substitute host processit with <newhostname>
cd $ORACLE_HOME/network/admin
vi listener.ora #substitue host 'processit' with your hostname, in this example pit01vmdkserv
lsnrctl start
sqlplus /as sysdba
startup #Database starts
sudo service weblogic start
sudo service soa start

Client computers

PROCESSIT console does not render correctly

By default Internet Explorer treats all URLs without a full domain name (.com, .net, .dk, etc) as part of the intranet security zone. For some unknown reason, this can ruin ADF structure and stylesheets so the page content do not render correctly. To fix this problem, you must force Internet Explorer to treat PROCESSIT as part of the internet security zone instead. Follow the instructions below.

Open security properties via Tools → Internet Options → Security (tab)
Click Sites
De-select automatically detect intranet network and include all local (intranet) sites not listed in other zones check-boxes.
Click OK, then OK again.
Refresh the page and the problem should be solved

Other Errors

Could not initialize class sun.awt.X11GraphicsEnvironment

You risk receiving the error java.lang.NoClassDefFoundError: Could not initialize class sun.awt.X11GraphicsEnvironment. The error occurs because some servers try to incorrectly initialize the x11 environment, which does not work on a server.

The solution is to add a java option to the Weblogic server startup to tell it to not do that.

Edit the startWeblogic.sh file (generally located at /oracle/middleware/user_projects/domains/d4/bin)
Find that line with content very similar to: JAVA_OPTIONS="${SAVE_JAVA_OPTIONS} ${SECURITY_OPTIONS} ${GC_OPTIONS} ${HEADLESS} ${HA_TEST_OPTIONS} ${KRB5_OPTIONS} ${KRB5_DEBUG}" - note that not all tese options necessarily occur.
Insert this line aboce the located JAVA_OPTIONS line: HEADLESS="-Djava.awt.headless=true"
On the JAVA_OPTIONS line add ${HEADLESS} to the end as it is whoen in the example. Make sure to add it inside the quotes.
Restart the WebLogic server.