"DEV_MDS.MDS_INTERNAL_SHREDDED" has errors while starting SOA Suite 11.1.1.5 server

I got below error while starting Oracle SOA Suite 11.1.1.5 server with on Oracle XE 10g  database.

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"

When this error happen SOA EM is not started and we can’t deploy any composites in SOA server.

Please follow below steps to resolve the issue.

1)      STOP SOA suite 11.1.1.5 server

2)      Drop the all SOA database schema using RCU.

once RCU drops the SOA database schemas like DEV_MDS connect to XE database using sqlplus command though command prompt.

• Connect sys as SYSDBA and provide a password for SYS user

alter system set sga_target=350M scope=spfile;

alter system set sga_max_size=350M scope=spfile;

shutdown immediate

startup

once XE database is started. Set RCU_JDBC_TRIM_BLOCKS=TRUE  environment variable and run RCU to create SOA schema again.

Also before running rcu.bat file in command prompt . please check RCU_JDBC_TRIM_BLOCKS set properly.

• Set RCU_JDBC_TRIM_BLOCKS=TRUE


• Echo % RCU_JDBC_TRIM_BLOCKS %   -- this has to return TRUE

Now run rcu.bat in same command prompt window and create required schemas.

Note : This issue will happen only on XE 10g database.

Now start the SOA suite and deploy composites. Enjoy SCA development.

Receive EMAIL using OSB ( Oracle Service BUS)

Most of the guys know, how to send a email using OSB(Oracle service bus)  when we want to send notifications in business flow. sometimes, we might need to start our  business process by receiving an email from legacy system.

Recently, I come across POC. Where, we can trigger a OSB proxy service by sending an email with messages as email body.  The below steps will explain. How to create a proxy service which can receive emails and execute.

1)   First step is to create a static service account type. It will have credentials for mailbox( mainly user name , password).

Since, I am using my own mail server. I created mailbox user with web logic as user name for testing.

2)     second step, we need to create a proxy service that can listen to mail box  and execute message flow, whenever new mail arrives.

1. Service type should be messaging service.


2. Other configuration details can be found in below screen shot.

3)     Save changes and activate session. Now open message flow or proxy service to insert report action. in report action, we will print body and we can check body in sbconsole.

Now , the service is ready and it can trigger  by sending an email.

OSB Internal Server Error - JMS Transaction rollback

This blog explain how to roll back a transaction in case of internal server errors in OSB. In general, if it gets any http response from the transport. There seem to be some ambiguity among product designers on interpreting http spec and they decided to treat any response as a success. This case transaction will not roll back and message will lost.

Scenario

JMS Queue -> OSB Proxy Service -> OSB  Business Service ->  Failing Service

To resolve the issues, please flow below steps in OSB proxy service.

1)      In Route node of routing options make  Quality of Service as ‘"Exactly Once”



2)      Enabled the Same Transaction for Response in the Proxy service which was listening to the JMS queue  –



3)      The Connection Factory used  to consume message from JMS queue should be  XA enable (XA connection factory).

4)      enabled XA required property for proxy service which is listening to JMS queue

5)      in JMS proxy Route Error handler do a raise error and Reply with Failure.



Once you make these necessary changes in proxy services. Activate changes and retest the flow. now you can observer the transaction will roll back in case of  ‘Internal server Error”  J

Hello world!

Welcome to WordPress.com. After you read this, you should delete and write your own post, with a new title above. Or hit Add New on the left (of the admin dashboard) to start a fresh post.

Here are some suggestions for your first post.

1. You can find new ideas for what to blog about by reading the Daily Post.


2. Add PressThis to your browser. It creates a new blog post for you about any interesting  page you read on the web.


3. Make some changes to this page, and then hit preview on the right. You can alway preview any post or edit you before you share it to the world.

OSB - Internal Server Error JMS Transaction rollback

This blog explain how to roll back a transaction in case of internal server errors in OSB. In general, if OSB proxy service gets any incorrect(404 HTTP Response) or there is an internal server error(500 HTTP response) from the transport the transaction will not roll back and message will lost. There seem to be some ambiguity among product designers on interpreting http spec and they decided to treat any response as a success.

Scenario

JMS Queue -> OSB Proxy Service -> OSB Business Service -> Failing Service

To resolve the issues, please flow below steps in OSB proxy service.

1) In Route node of routing options make Quality of Service as ‘"Exactly Once”

2) Enabled the Same Transaction for Response in the Proxy service which was listening to the JMS queue

3) The Connection Factory used to consume message from JMS queue should be XA enable (XA connection factory).

4) In JMS proxy Route Error handler do a raise error and Reply with Failure.

5) Enable XA required property for proxy service which is listening to JMS queue

Once you make these necessary changes in proxy services. Activate changes and retest the flow. now you can observer the transaction will roll back in case of ‘Internal server Error” J