Discussions
Categories
- 381.9K All Categories
- 2.1K Data
- 207 Big Data Appliance
- 1.9K Data Science
- 447.4K Databases
- 220.8K General Database Discussions
- 3.7K Java and JavaScript in the Database
- 23 Multilingual Engine
- 516 MySQL Community Space
- 464 NoSQL Database
- 7.8K Oracle Database Express Edition (XE)
- 2.9K ORDS, SODA & JSON in the Database
- 471 SQLcl
- 3.9K SQL Developer Data Modeler
- 185.9K SQL & PL/SQL
- 20.9K SQL Developer
- 292.7K Development
- 7 Developer Projects
- 124 Programming Languages
- 289.4K Development Tools
- 95 DevOps
- 3K QA/Testing
- 645.5K Java
- 23 Java Learning Subscription
- 36.9K Database Connectivity
- 150 Java Community Process
- 104 Java 25
- 22.1K Java APIs
- 137.8K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 16 Java Essentials
- 143 Java 8 Questions
- 85.9K Java Programming
- 79 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.2K Java SE
- 13.8K Java Security
- 197 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 243 LiveLabs
- 35 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.8K Other Languages
- 2.3K Chinese
- 166 Deutsche Oracle Community
- 1.2K Español
- 1.9K Japanese
- 225 Portuguese
Oracle 12.2 64bit Pro*C Random Exceptions when calling / executing SQLCA
Hello,
I have some Pro*C code that is randomly failing when I try to make the sqlca call to execute the SQL statement.
Execution #1 fails on SQLCA call - Program Crashes
Execution #2 - the same call that failed in Execution #1 will return and the program continues.
Nothing was re-compiled between Execution #1 and Execution #2.
It's a fairly simple select getting user information with nothing crazy for the query statement.
I need to be able to track down why it will fail sometimes and not other times
Best Answer
-
Upgraded projects to use a newer version of Oracle client, specifically Oracle 19 client and issue went away. All that was done was point to the new *.dll and executables for Oracle Client.
No Pro*C changes were required!!
Answers
-
finally move to Oracle 19 client and issue is resolved
-
Upgraded projects to use a newer version of Oracle client, specifically Oracle 19 client and issue went away. All that was done was point to the new *.dll and executables for Oracle Client.
No Pro*C changes were required!!