OEM: 13.5 : Cluster Discovery Fails with "java.sql.SQLException: Inserted value too large for column"
(Doc ID 2924296.1)
Last updated on JANUARY 31, 2023
Applies to:
Enterprise Manager for Oracle Database - Version 13.5.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
On : 13.5.0.0.0 version, Target Database, Listener, ASM
Cluster discovery fails with below error complaining about the size of the hostname.
2022-09-18 18:47:25,010 [[ACTIVE] ExecuteThread: '103' for queue: 'weblogic.kernel.Default (self-tuning)'] ERROR crsdiscovery.CrsDiscoveryUtil logp.251 - Caught SQLException while fetching cluster targets from repos. It may result in failure of cluster discovery.
java.sql.SQLException: Inserted value too large for column: "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.domain.com"
at oracle.jdbc.oracore.OracleTypeCHAR.pickle81(OracleTypeCHAR.java:341)
at oracle.jdbc.oracore.OracleTypeCOLLECTION.pickle81(OracleTypeCOLLECTION.java:312)
at oracle.jdbc.oracore.OracleTypeADT.pickle81(OracleTypeADT.java:1874)
at oracle.jdbc.oracore.OracleTypeADT.linearize(OracleTypeADT.java:1514)
at oracle.sql.ArrayDescriptor.toBytes(ArrayDescriptor.java:670)
......
at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:655)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:420)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:360)
2022-09-18 18:47:25,026 [[ACTIVE] ExecuteThread: '103' for queue: 'weblogic.kernel.Default (self-tuning)'] ERROR crsdiscovery.CrsGuidedDiscoveryBean logp.251 - Caught SQLException while fetching member targets from reposfor cluster target shs64slorp01clu
java.sql.SQLException: Inserted value too large for column: "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.domain.com"
at oracle.jdbc.oracore.OracleTypeCHAR.pickle81(OracleTypeCHAR.java:341)
java.sql.SQLException: Inserted value too large for column: "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.domain.com"
at oracle.jdbc.oracore.OracleTypeCHAR.pickle81(OracleTypeCHAR.java:341)
at oracle.jdbc.oracore.OracleTypeCOLLECTION.pickle81(OracleTypeCOLLECTION.java:312)
at oracle.jdbc.oracore.OracleTypeADT.pickle81(OracleTypeADT.java:1874)
at oracle.jdbc.oracore.OracleTypeADT.linearize(OracleTypeADT.java:1514)
at oracle.sql.ArrayDescriptor.toBytes(ArrayDescriptor.java:670)
......
at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:655)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:420)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:360)
2022-09-18 18:47:25,026 [[ACTIVE] ExecuteThread: '103' for queue: 'weblogic.kernel.Default (self-tuning)'] ERROR crsdiscovery.CrsGuidedDiscoveryBean logp.251 - Caught SQLException while fetching member targets from reposfor cluster target shs64slorp01clu
java.sql.SQLException: Inserted value too large for column: "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.domain.com"
at oracle.jdbc.oracore.OracleTypeCHAR.pickle81(OracleTypeCHAR.java:341)
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 |