- 3,728,153 Users
- 2,245,559 Discussions
- 7,853,357 Comments
Forum Stats
Discussions
Howdy, Stranger!
Categories
- 380.6K All Categories
- 16 Data
- 362.2K Big Data Appliance
- 7 Data Science
- 2.4K Databases
- 697 General Database Discussions
- 3.7K Java and JavaScript in the Database
- 32 Multilingual Engine
- 499 MySQL Community Space
- 10 NoSQL Database
- 7.7K Oracle Database Express Edition (XE)
- 2.8K ORDS, SODA & JSON in the Database
- 426 SQLcl
- 69 SQL Developer Data Modeler
- 185.2K SQL & PL/SQL
- 21.1K SQL Developer
- 2.8K Development
- 3 Developer Projects
- 32 Programming Languages
- 136K Development Tools
- 18 DevOps
- 3K QA/Testing
- 388 Java
- 16 Java Learning Subscription
- 14 Database Connectivity
- 72 Java Community Process
- 3 Java 25
- 14 Java APIs
- 141.2K Java Development Tools
- 15 Java EE (Java Enterprise Edition)
- 153K Java Essentials
- 135 Java 8 Questions
- 86.2K Java Programming
- 79 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 18 Java SE
- 13.8K Java Security
- 4 Java User Groups
- 22 JavaScript - Nashorn
- 18 Programs
- 159 LiveLabs
- 36 Workshops
- 13 Software
- 7 Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 4 Deutsche Oracle Community
- 19 Español
- 1.9K Japanese
- 4 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.
