Target Servers Missing from Datasource Testing Tab

Posted on by Ramesh Poonati

When we get errors related to datasource in weblogic, first thing we do is go to datasource Monitoring -> Testing tab and test datasource. Sometimes, targets might be missing from this tab. DurING server startup, server tries to load datasource and create connections to database. If there is any underlying issue with database like password change, password expiry, unavailability of database, it doesn’t load the datasource and we see missing targets in testing tab. Some of the errors, we can see are:

####<Apr 21, 2022 3:44:12,251 AM PDT> <Info> <JDBC> <orasoa-test12-w2> <WLS_SOA2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <d47e58ce-a023-4de2-acb7-24391c8056df-0000000a> <1650537852251> <[severity-value: 64] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-001508> <Destroying data source connection pool TestDS.>
####<Apr 21, 2022 3:44:12,264 AM PDT> <Error> <Deployer> <orasoa-test12-w2> <WLS_SOA2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <d47e58ce-a023-4de2-acb7-24391c8056df-0000000a> <1650537852264> <[severity-value: 8] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-149205> <Failed to initialize the application "TestDS" due to error weblogic.application.ModuleException: weblogic.common.resourcepool.ResourceSystemException:
 Could not create connection for datasource 'TestDS'.

 The returned message is: ORA-01017: invalid username/password; logon denied

WLS_SOA2.log:####<Apr 21, 2022 3:10:48,140 AM PDT> <Error> <Deployer> <orasoa-test12-w2> <WLS_SOA2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <e6afa167-8b1d-444f-9ee4-47ff11eea5ff-0000000b> <1650535848140> <[severity-value: 8] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-149205> <Failed to initialize the application "TestDS" due to error weblogic.application.ModuleException: java.sql.SQLException: ORA-28001: the password has expired

Solution to this problem is fixing underlying database/user related issue and removing target and adding target again. We need to activate the sessions after removing and adding targets.

Created a script to monitor this special case and regular datasource monitoring. It is available at:
https://github.com/RameshPoonati/oracleMiddlewareScripts/tree/master/dataSourceMonitoring

Related Post