Problem : SOA and OSB managed servers failed to start. Status updated as Admin.
Reason : Data Sources configured are not able to create initial connection during server start up.
Steps to Simulate issue:
- Configured a data source by providing DB details of target system here for example target as Oracle EBS system
- Data source target set to SOA and OSB managed servers.
- Initial Capacity is greater than 0, here for example set to 1
- After configuration done, keep target data base shutdown so that data source wont be able to connect.
- Restart managed servers. it will go to ADMIN state instead of RUNNING
During server start it tries to bring all component up. As the Data Source Initial Capacity set to 1 during start up it will attempt to create one connection with target database however as the target DB is down it will fail.
Failed to create data source connection, managed server will start to ADMIN state instead of RUNNING.
If number of data source are failed to create connection during startup and sever goes to ADMIN state, after resuming managed server from ADMIN state node manager will shutdown all managed server.
Solution : Change Initial Capacity to 0 on all data source then start managed servers.
Server will start now normally.
I Love Cooking Too, Please visit my Cooking Channel on YouTube: https://www.youtube.com/c/priyashreefoodfashion
Please do Subscribe on YouTube if you are a foodie too 🙂
Oracle SOA Tutorials and Solutions 
so is it application started without making any connections to the database?
also just curious to know how clusters for two applications can be clubbed in a single application(not mentioned though)
LikeLike
Thats right, but not applications rather weblogic DataSources configured. Applications only access these Datasources in runtime directly or via connection pool. On 2nd question I am clear what you are looking for. Can you be specific or give some examples ?
LikeLike