error code 1047: ServiceOperation doesn't exist

Issue: error code 1047: ServiceOperation  doesn't exist

deployHellowordESB:

[GC 23496K->15396K(130176K), 0.0026974 secs]

[deployESBProjects] Deployment Attempt Response :

[deployESBProjects] <deploymentSummary>

[deployESBProjects]    <message>Entity Deployment Failed</message>

[deployESBProjects]    <errors>

[deployESBProjects]       <error code="1047" severity="5">

[deployESBProjects]          <description>Target of service "HellowordServices.Helloword.HellowordRS" ServiceOperation "" doesn't exist </descrip

tion>

[deployESBProjects]          <fix>Use existing service or service operation as t

arget.Contact Oracle Support if error not fixable.</fix>

[deployESBProjects]       </error>

[deployESBProjects]    </errors>

[deployESBProjects] </deploymentSummary>

BUILD FAILED

C:\Deployment\Services 1.0.0.1\DeploymentScripts\deploy

services.xml:84: The following error occurred while executing this line:

C:\ Deployment\Services 1.0.0.1\DeploymentScripts\deploy

services.xml:353: The following error occurred while executing this line:

C:\ Deployment\Services 1.0.0.1\DeploymentScripts\deploy

mentscripts\Helloword\deployHellowordService.xml:161: java.lang.Except

ion: Deployment attempt failed, please review deployment attempt response above

Total time: 6 minutes 5 seconds

Resolution:

    We found the reason why HelloworldESB deployment is failing with 1.0.0.1 build. This is a Build issue.have added a DB adapter in HelloworldESB service by consuming the DB function. When I added this DB adapter in ESB it generated an XSD file. This XSD file exists in SVN under promoted files and also in 1.0.0.1 Snapshot, but this XSD file is missing in the Helloword.zip which will get generated after build, which will get deployed as ESB. As the XSD file is missing in 1.0.0.1 build the Deployment is failing.

We need to do a build again and do deployment.


Approach 2:

1. Undeploy  manually the bpel service from Bpel Console.
2. Undeploy manually respective esb service from esb console.
3. Remove temp of  respective bpel and esb service.
4. Deploy the Service Using old build (existing successfully deployed)

5. Now deploy the service from current build and continue from there.