Oracle Error 17412
CommunityOracle User Group CommunityTopliners CommunityOTN Speaker BureauJava CommunityError: You don't have JavaScript enabled. This tool uses JavaScript and much of it will not work correctly without it enabled. Please turn JavaScript back on and reload this page. Please enter a title. You can not post a blank message. Please type your message and try again. More discussions in TopLink/JPA All PlacesFusion MiddlewareApplication ServerTopLink/JPA This discussion is archived 1 Reply Latest reply on Sep 29, 2004 2:32 PM by Mmacivor-Oracle getting Bigger type length than Maximum error in TopLink 412424 Aug 13, 2004 9:34 PM Hi, I got the ff exceptions: 13 Aug 2004,17:28:42 ERROR [ToplinkUtil.java:handleException():170] - class oracle.toplink.exceptions.DatabaseException 13 Aug 2004,17:28:42 ERROR [DebugLog.java:logError():151] - Exception Description: java.sql.SQLException: Bigger type length than Maximum Internal Exception: java.sql.SQLException: Bigger type length than Maximum Error Code: 17412 Local Exception Stack: Exception [TOPLINK-4002] (OracleAS TopLink - 10g (9.0.4.2) (Build 040311)): oracle.toplink.exceptions.DatabaseException Exception Description: java.sql.SQLException: Bigger type length than Maximum Internal Exception: java.sql.SQLException: Bigger type length than Maximum Error Code: 17412 at oracle.toplink.exceptions.DatabaseException.sqlException(DatabaseException.java:226) at oracle.toplink.internal.databaseaccess.DatabaseAccessor.executeCall(DatabaseAccessor.java:695) at oracle.toplink.threetier.ServerSession.executeCall(ServerSession.java:506) at oracle.toplink.internal.queryframework.CallQueryMechanism.executeCall(CallQueryMechanism.java:134) at oracle.toplink.internal.queryframework.CallQueryMechanism.executeCall(CallQueryMechanism.java:115) at oracle.toplink.internal.queryframework.CallQueryMechanism.executeSelectCall(CallQueryMechanism.java:197) at oracle.toplink.internal.queryframework.CallQueryMechanism.executeSelect(CallQueryMechanism.java:178) at oracle.toplink.queryframework.DataReadQuery.executeNonC
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > ORA-17412 "Bigger Type Length Than Maximum" Want to Advertise Here? Solved ORA-17412 "Bigger Type Length Than Maximum" Posted on 2006-01-23 Oracle https://community.oracle.com/thread/261698 Database 2 Verified Solutions 12 Comments 4,866 Views Last Modified: 2008-01-09 I have a java application using oracle 9i with path 2, and it is working fine but once in a while it goes bad. -------------------------------- Java Code (PaymentsInvoicing.java) ------------------------------------------ Line 305 >>>> String sql = "select CORRECTED_TRANSIT from TRANSIT where" + Line 306 >>>> https://www.experts-exchange.com/questions/21706791/ORA-17412-Bigger-Type-Length-Than-Maximum.html " CPY_CODE = " + db.getSQLFormattedValue(cpyCode) + Line 307 >>>> " and NODE_TYPE = " + nodeType + Line 308 >>>> " and NODE_CODE = " + db.getSQLFormattedValue(nodeCode) + Line 309 >>>> " and LOCATOR = " + locator; Line 310 >>>> Number corrected = (Number)db.getQuerySingleValue(transactionId, sql); -------------------------------- Java Code (PaymentsInvoicing.java) ------------------------------------------ In log file give me this error.... ------------------------------------------------------------------------ 16:50:57 23/01/06 WARNING Error executing query. SQL: select CORRECTED_TRANSIT from TRANSIT where CPY_CODE = '00' and NODE_TYPE = 401 and NODE_CODE = '001000307000009' and LOCATOR = 138741, TransName: null, IdConn:2 Error executing query. SQL: select CORRECTED_TRANSIT from TRANSIT where CPY_CODE = '00' and NODE_TYPE = 401 and NODE_CODE = '001000307000009' and LOCATOR = 138741, TransName: null, IdConn:2 16:50:57 23/01/06 WARNING *** DATABASE IS DOWN *** Bigger
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company http://stackoverflow.com/questions/2788030/exception-while-calling-stored-procedure-bigger-type-length-than-maximum Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Exception while calling stored procedure :Bigger type length than Maximum up vote 1 down vote favorite HI I am getting this exception oracle error when I am calling any stored procedure from my J2EE app. Exception while calling stored procedure :Bigger type length than Maximum I am having Oracle 9.1.0.7, JDK1.4 and using ojdbc14.jar running on Weblogic 8.1 Please advise what could be the root cause ? Below is the manifest of my ojdbc14.jar Manifest-Version: 1.0 Implementation-Version: "Oracle JDBC Driver version - 10.1.0.2.0" Specification-Title: "Oracle JDBC driver classes for use with JDK1.4" Specification-Version: "Oracle JDBC Driver version - oracle error 17412 10.1.0.2.0" Implementation-Title: "ojdbc14.jar" Created-By: 1.2.2 (Sun Microsystems Inc.) Implementation-Time: "Wed Jan 21 00:48:12 2004" Implementation-Vendor: "Oracle Corporation" Specification-Vendor: "Oracle Corporation". oracle9i jdbc sqlexception weblogic8.x share|improve this question edited May 12 '10 at 7:13 asked May 7 '10 at 11:09 Ravi Gupta 1,219103664 add a comment| 3 Answers 3 active oldest votes up vote 1 down vote accepted +100 It's a driver bug. Your version is already 6 years old. Download the latest and greatest from here. share|improve this answer answered May 16 '10 at 21:29 Hans Passant 656k819631609 add a comment| Did you find this question interesting? Try our newsletter Sign up for our newsletter and get our top new questions delivered to your inbox (see an example). Subscribed! Success! Please click the link in the confirmation email to activate your subscription. up vote 1 down vote See this post for a possible workaround. For possible causes, see this thread: There are bugs in different versions of the drivers and different versions of the database; most of them are fixed in later versions. For example, bugs produce the "Bigger type length than maximum" in Oracle database 8.1.7.2 or 9.0.1.1 for certain very specific operations using DB links; upgrading to 8.1.7.3 or 8.1.7.4 or 9.0.1.2 resolves those problems. For example, bugs produce the "Bigger type length than maximum" in Oracle database