DEV_MDS.MDS_INTERNAL_SHREDDED error

When we install SOA suite 11g, after server startup, many a times SOA_INFRA remains down. If we check admin server logs, we will find below error message:-

DEV_MDS.MDS_INTERNAL_SHREDDED

Solution:- In order to resolve this error, please follow below steps:-

1.)Open SQLDeveloper and make a connection with DEV_MDS Schema.
2.)Compile below packages
      a.)mds_internal_common

      b.)mds_internal_shredded

      c.)mds_internal_utils

After that restart the server..

Hope this blog will help you guys...

SOA_Server error AGENT_ERROR_TRANSPORT_INIT(197)

When we install soa suite 11g, sometimes while starting soa_server, we face below error:-

FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)

ERROR: transport error 202: bind failed: Address already in use

ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)

JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]

Starting WLS with line:

In Order to resolve this error, follow below steps:-

1.)Go to $MiddlewareHome\user_projects\domains\soa_domain\bin

      2.)  Open setDomainEnv.cmd

      3.)  Change ‘set debugFlag=true’  to ‘rem set debugFlag=true

      After that restart the server. 

     Enjoy......................

Error occurred during initialization of VM

Generally when we install SOA Suite 11g on windows platform, we face below error while starting admin server:-

Error occurred during initialization of VM

Could not reserve enough space for object heap

Could not create the Java virtual machine.

Stopping Derby server...

Derby server stopped.

We can see this on command prompt as below :-

Solution:-

Go to file <domain home>\bin\setSOADomainEnv.cmd/sh (depending on your platform) and modify the line:

set DEFAULT_MEM_ARGS=-Xms512m -Xmx1024m

to something like:

set DEFAULT_MEM_ARGS=-Xms512m -Xmx768m

After that , just restart the server...

Setting Up Node Manager in SOA 11g

This blog will explain how to set up Node Manager after SOA 11g server installation.
In order to setup node manager, Please follow below step:-

1.)   After server installation and domain configuration, Startup the NodeManager 

  a.)Go to $MiddlewareHome\wlserver_10.3\server\bin

  b.)Double click on StartNodeManager.cmd

  c.)After that go to path $MiddlewareHome\wlserver_10.3\common\nodemanager

  d.)Notice that one file named ‘nodemanager.properties’ will be created when we double clicked StartNodeManager.cmd

  e.)Open nodemanager.properties file and change default value of StartScriptEnabled from 'false’  to true & save it

2.)After that, again start NodeManager by repeating steps 1a & 1b

3.)Start Weblogic server by following below:-

   a.)Go to $MiddlewareHome\user_projects\domains\soa_domain\bin

   b.)Double click ‘startWebLogic.cmd’

    c.)Admin Server will come to running mode