Data Sources File Can Be Corrupted When Using Ascontrol In 10.1.3 To Edit a Connection Pool
(Doc ID 802283.1)
Last updated on FEBRUARY 14, 2025
Applies to:
Enterprise Manager for Fusion Middleware - Version 10.1.3.1.0 and laterOracle Containers for J2EE - Version 10.1.3.1.0 and later
Information in this document applies to any platform.
Symptoms
Problem Statement:
When using the ascontrol interface to update the data sources configuration, often the data-sources.xml configuration file becomes empty (0 bytes), and it is no longer possible to start the OC4J instance.
Restoring a copy of the file allows the instance to be restarted as normal. The only workaround to this is manually editing the file.
Steps To Reproduce:
Business Impact:
Administration of JDBC resources becomes dangerous and unstable as the data-sources.xml
configuration file can be easily corrupted
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |