Oracle SOA/OSB - OSB Kernel:398034]Two operations expect the same incoming message, you must use a selector different than message body

This error can be fixed, by selecting a different "Operation Selection Configuration". This can be done by selecting your proxy-service and select the "Operation" tab sheet in Eclipse Workshop. Here you determine how algorithm of the operations are handled. In our case select 'SOAPAction Header'.
http://orasoa.blogspot.com/2008/11/handle-multiple-operations-in-osb.html

Oracle SOA/BPEL - MDS- oracle.mds.exception.MDSException: MDS-00054: The file to be loaded oramds:/soa/configuration/default/workflow-identity-config.xml does not exist.

(SOA 11g) The source of the problem for us was that it was deployed to both the admin server (mistake!) and the soa server (correct) and we were accessing it on the admin server port (7001) rather than the soa server port (8001) which was correct.

ie. For us

http://hostname:7001/integration/SOADemoCommunity/DemoCommunitySeedServlet (failed and gave the error mentioned)
http://hostname:8001/integration/SOADemoCommunity/DemoCommunitySeedServlet (worked)

Oracle SOA - Unable to find SOA server on Jdeveloper during BPEL process deployement

Check whether your managed server soa_server1 is running or not. If not then start it . Make sure your weblogic server should be running.

To start managed server go to  ORACLE_HOME\user_projects\domains\{ur_dimain}\bin   folder and run this command

startManagedWebLogic.cmd  soa_server1  t3://localhost:7001

Oracle SOA - Weblogic - java.sql.SQLException: JDBC LLR weblogic.transaction.loggingresource.LoggingResourceException: java.sql.SQLException: JDBC LLR, table verify failed for table 'WL_LLR_ADMIN SERVER', row 'JDBC LLR Domain//Server' record had unexpected value 'soa_domain//AdminServer' expected 'soabpel//AdminServer'*** ONLY the or iginal domain and server that creates an LLR table may access it ***

SQL Test=SELECT 1 FROM SYS.SYSTABLES

If  database is Oracle 11g, then test SQL should be SELECT 1 FROM DUAL

This error comes when datasource not configured for Oracle DB, rather it is pointing to Derby database.

Make sure that while creating/extending the domain, on "Configure JDBC Component Schema" screen, you are selecting the checkbox against "OSB JMS Reporting Provider" and you are selecting "Oracle" as vendor. By default, "Derby" remains selected. Provide the connection details and click on next. On next screen, you test should be successful, and you should see lines similar to below -

Component Schema=OSB JMS Reporting Provider
Driver=oracle.jdbc.OracleDriver
URL=jdbc:oracle:thin:@localhost:1521:XE
User=DEV_SOAINFRA
Password=********
SQL Test=SELECT 1 FROM DUAL

CFGFWK-20850: Test Successful!

Oracle SOA - OSB -Problem during creating OSB domain Insufficient data while reading from the network - expected a minimum of 6 bytes and received only 0 bytes

SQL Test=SELECT 1 FROM SYS.SYSTABLES

If your database is Oracle 11g, then test SQL should be SELECT 1 FROM DUAL

I think you have not configured the datasource for Oracle DB, rather it is pointing to Derby database.

Make sure that while creating/extending the domain, on "Configure JDBC Component Schema" screen, you are selecting the checkbox against "OSB JMS Reporting Provider" and you are selecting "Oracle" as vendor. By default, "Derby" remains selected. Provide the connection details and click on next. On next screen, you test should be successful, and you should see lines similar to below -

Component Schema=OSB JMS Reporting Provider

Driver=oracle.jdbc.OracleDriver

URL=jdbc:oracle:thin:@localhost:1521:XE

User=DEV_SOAINFRA

Password=********

SQL Test=SELECT 1 FROM DUAL

CFGFWK-20850: Test Successful!

Oracle SOA - MDS- oracle.mds.exception.MDSExceptionList: MDS-01329: unable to load element "persistence-config" MDS-01370: MetadataStore configuration for metadata-store-usage "OWSM_TargetRepos" is invalid. ORA-04063: package body "DEV_MDS.MDS_INTERNAL_SHREDDED" has errors ORA-06508: PL/SQL: could not find program unit being called: "DEV_MDS.MDS_INTERNAL_SHREDDED" ORA-06512: at line 1

Open the  MDS packages in Oracle SQL Developer and recompile them, you should get rid of the MDS SHREDDED bla error message

Oracle SOA - RCU-6107:DB Init Param Prerequisite failure for: processes Current Value is 40. It should be greater than or equal to 200.

Perform following steps on your database


SQL> alter system reset sessions scope=spfile sid='*';
SQL> alter system set processes=300 scope=spfile;
SQL> shutdown immediate
SQL> startup