Discussions
Categories
- 197.2K All Categories
- 2.5K Data
- 546 Big Data Appliance
- 1.9K Data Science
- 450.8K Databases
- 221.9K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 552 MySQL Community Space
- 479 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.1K ORDS, SODA & JSON in the Database
- 555 SQLcl
- 4K SQL Developer Data Modeler
- 187.2K SQL & PL/SQL
- 21.4K SQL Developer
- 296.3K Development
- 17 Developer Projects
- 139 Programming Languages
- 293K Development Tools
- 110 DevOps
- 3.1K QA/Testing
- 646.1K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 158 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.2K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 19 Java Essentials
- 162 Java 8 Questions
- 86K Java Programming
- 81 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 205 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 468 LiveLabs
- 39 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 175 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 233 Portuguese
ORA-12152: TNS:unable to send break message on database link to an autonomous database
Hi! I have a Oracle 18XE DB running on an Oracle Enterprise Linux server in Azure (Virginia). I also have an autonomous database running in the Oracle Cloud in Ashburn (also Virginia). I crated a DB link from the XE to the autonomous database. Most of the time the link works great but sometimes it just grounds to a halt, queries freeze and eventually fail with ORA-12152: TNS:unable to send break message. These are simple, normally sub second queries.
Any tips to help troubleshoot is greatly appreciated.
Answers
-
Product Manager, Kris B. has been notified.
-
Is your autonomous DB in the shared service?
-
Thank you for your response. I assume so it is on the free tier. But I have not actually seen this issue again in the past week so it may have just magically gone away.
