Discussions
Categories
- 385.5K All Categories
- 5.1K Data
- 2.5K Big Data Appliance
- 2.5K Data Science
- 453.4K Databases
- 223.2K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 47 Multilingual Engine
- 606 MySQL Community Space
- 486 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.2K ORDS, SODA & JSON in the Database
- 585 SQLcl
- 4K SQL Developer Data Modeler
- 188K SQL & PL/SQL
- 21.5K SQL Developer
- 46 Data Integration
- 46 GoldenGate
- 298.4K Development
- 4 Application Development
- 20 Developer Projects
- 166 Programming Languages
- 295K Development Tools
- 150 DevOps
- 3.1K QA/Testing
- 646.7K Java
- 37 Java Learning Subscription
- 37.1K Database Connectivity
- 201 Java Community Process
- 108 Java 25
- 22.2K Java APIs
- 138.3K Java Development Tools
- 165.4K Java EE (Java Enterprise Edition)
- 22 Java Essentials
- 176 Java 8 Questions
- 86K Java Programming
- 82 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
- 208 Java User Groups
- 25 JavaScript - Nashorn
- Programs
- 667 LiveLabs
- 41 Workshops
- 10.3K Software
- 6.7K Berkeley DB Family
- 3.6K JHeadstart
- 6K Other Languages
- 2.3K Chinese
- 207 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 474 Portuguese
12775220 DatabaseMetaData.getColumns() returns unexpected values in COLUMN_SIZE and DECIMAL_DIGITS

Hi All,
I posted a while ago asking about Bug 12775220
I just wanted to provide an update on this as I found a potential solution to the underlying problem that I facing (with NUMBER columns which lacked precision and scale). If you add the JVM argument -Doracle.jdbc.J2EE13Compliant=true it appears to resolve this problem.
Regards
Rod
Answers
-
This fix is in 11.2.0.4
-
Hi,
This is what I thought originally as it was 'reported' as fixed in Oracle Support but I tested it and the problem I was facing remains. This either means the the problem I am seeing is not exactly the same (and I am happy to be corrected if this is the case) or the core problem has not been fixed. To illustrate try compiling this and testing with JDBC 11.2.0.4 against an 11.2.0.4 database (ensuring the latest ojdbc6.jar is first in your CLASSPATH and adapt for your environment)
import java.sql.*; import java.sql.SQLException; import oracle.jdbc.pool.OracleDataSource; public class OracleDriverTest { /** * @param args the command line arguments * @throws java.sql.SQLException */ public static void main(String[] args) throws SQLException { Connection connection = getConnection(); Statement stmt; stmt = connection.createStatement(); DatabaseMetaData dmd = connection.getMetaData(); ResultSet rs = dmd.getColumns("", "SCOTT", "BONUS", "%")) while (rs.next()) { System.out.println("Column: " + rs.getString("COLUMN_NAME")); System.out.println("Data type: " + rs.getInt("DATA_TYPE")); System.out.println("Size: " + rs.getInt("COLUMN_SIZE")); System.out.println("Decimal digits: " + rs.getInt("DECIMAL_DIGITS")); } } public static Connection getConnection() throws SQLException { String username = "SCOTT"; String password = "password"; String thinConn = "jdbc:oracle:thin:@//localhost/ORCL"; OracleDataSource ods; ods = new OracleDataSource(); ods.setUser(username); ods.setPassword(password); ods.setURL(thinConn); Connection conn = ods.getConnection(); DatabaseMetaData dbmd = conn.getMetaData(); System.out.println("Database : " + dbmd.getDatabaseProductVersion()); System.out.println("JDBC Driver : " +dbmd.getDriverVersion()); conn.setAutoCommit(false); return conn; } }
When I run this against my database I see this
$ /opt/jdk1.6.0_38/bin/java OracleDriverTest
Database : Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
JDBC Driver : 11.2.0.4.0
Column: ENAME
Data type: 12
Size: 10
Decimal digits: 0
Column: JOB
Data type: 12
Size: 9
Decimal digits: 0
Column: SAL
Data type: 3
Size: 0
Decimal digits: -127
Column: COMM
Data type: 3
Size: 0
Decimal digits: -127
now compare the results when I use the oracle.jdbc.J2EE13Compliant=true argument
$ /opt/jdk1.6.0_38/bin/java -Doracle.jdbc.J2EE13Compliant=true OracleDriverTest
Database : Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
JDBC Driver : 11.2.0.4.0
Column: ENAME
Data type: 12
Size: 10
Decimal digits: 0
Column: JOB
Data type: 12
Size: 9
Decimal digits: 0
Column: SAL
Data type: 3
Size: 38
Decimal digits: 0
Column: COMM
Data type: 3
Size: 38
Decimal digits: 0
This illustrates both the problem I am facing and a potential workaround/solution. The question is - is this the same bug or something different?
Regards
Rod