Problems faced during 10.1.3.4 SOA Suite Upgrade

Problem #1: Oracle BPEL Console does not show the contents of default domain.

Debug:
Observe the debug logs in %ORACLE_HOME%\opmn\logs\default_group~home~default_group~1.log

And the application logs located in 
%ORACLE_HOME%\j2ee\home\application-deployments\orabpel\home_default_group_1\application.log

Observation:
The following problem was observed:
Incorrect db schema version.
The database schema version "2.0.4" from the database does not match the version "10.1.3.4.0" expected by the server.
The database schema currently in place has probably been configured for a previous release; please re-install the database schema and try to start the server again.

Solution:
This means that the database schema was not upgraded to match the newer 10.1.3.4 version.

Execute the following scripts from your Installer directory
%SHIPHOME%\ias_windows_x86_101340\Disk1\install\soa_schema_upgrade\bpel\scripts
msql system/manager@jdbc:polite4@localhost:1531:orabpel @upgrade_10131_10134_olite.sql

%SHIPHOME%\ias_windows_x86_101340\Disk1\install\soa_schema_upgrade\esb\sql\other
msql system/any@jdbc:polite4@localhost:1531:oraesb @upgrade_10131_10134_olite.sql

Problem #2: Oracle Jdeveloper does not allow to deploy the Project, as it could not retrieve domain details.

Debugging:
Log on to enterprise manager console @ http://ics05-swapnils:8888/em/
Now go to Home > Applications, Inside applications, 
Expand All Applications > default > Middleware Services > BPEL > orabpel
 

Check the status of “deploy Service”.

Observation:
The service is STOPPED.

Solution:
Start the service and your JDeveloper should now be able to retrieve Domains, using right click on Project Name.