Sql error 12899 sqlstate 72000

‘ORA-12899 — SQLState: 72000’ Causes Continuous Retrying of Transaction Persistence, Resulting in Loss of the Next Set of Transactions (Doc ID 1519656.1)

Last updated on JUNE 07, 2021

Applies to:

Symptoms

When attempting to insert a record with a longer response than accepted into «TR_LTM_CHK_TND».»ID_AJD_CHK», the following error occurs and the application does not handle the exception.В This causes loss of transaction data for subsequent transactions.

«ERROR 2012-12-04 19:57:42,093 51418562 (RMI TCP Connection(11460)-10.192.68.1:com.extendyourstore.domain.arts.JdbcSaveTenderLineItems):

[com.extendyourstore.domain.arts.JdbcSaveTenderLineItems.insertCheckTenderLineItem(JdbcSaveTenderLineItems.java:1857)]

Class: com.extendyourstore.foundation.manager.data.DataException(Revision $Revision: /main/10 $) @12460173: SQLState: 72000

Error generated from Oracle: user requested cancel of current operationSource Exception: java.sql.SQLException: ORA-12899: value too large for column «POS_OWNER».»TR_LTM_CHK_TND».»ID_AJD_CHK» (actual: 22, maximum: 20)

Transaction Name:

Error code: [15] [An error occurred while executing the command]

Error code (extended): [12899]

Description: [SQLState: 72000

Error generated from Oracle: user requested cancel of current operationSource Exception: java.sql.SQLException: ORA-12899: value too large for column «POS_OWNER».»TR_LTM_CHK_TND».»ID_AJD_CHK» (actual: 22, maximum: 20)«

Steps to Reproduce:

1. Introduce a transaction with a response for the check approval longer than 20 characters.
2. POS does not move the transaction to the QueueException folder, nor is it retried for persistence.

The transaction is just lost (as well as the subsequent transactions) in the FileQueue.

Changes

Cause

To view full details, sign in with your My Oracle Support account.

Don’t have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.

Oracle offers a comprehensive and fully integrated stack of cloud applications and platform services. For more information about Oracle (NYSE:ORCL), visit oracle.com. пїЅ Oracle | Contact and Chat | Support | Communities | Connect with us | | | | Legal Notices | Terms of Use

Источник

A «value too large for column» SQL exception occurs for the LSW_USR_GRP_XREF table for IBM Business Process Manager (BPM)

Troubleshooting

Problem

After upgrading from IBM Business Process Manager V7.5.1 Fix Pack 1 to Fix Paxck 2, you receive an error message. The message indicates that a value for the GROUP_NAME column in the LSW_USR_GRP_XREF table is too large when it tries to create a snapshot for an application.

Symptom

You see an error message that is similar to the following text. The following example is seen with an Oracle database. Error messages for other databases might differ slightly.

[7/122/14 15:14:29:281 CEST] 0000208a wle E Exception while creating the snapshot com.lombardisoftware.client.delegate.
BusinessDelegateException: PreparedStatementCallback; uncategorized SQLException for SQL [insert into LSW_USR_GRP_XREF (GROUP_ID,GROUP_NAME, DISPLAY_NAME,GROUP_TYPE,DESCRIPTION,GROUP_STATE,PARENT_GROUP_ID) values (. )]; SQL state [72000]; error code [12899]; ORA-12899: value too large for column «BPMDB».»LSW_USR_GRP_XREF».»GROUP_NAME» (actual: 102, maximum: 101) ; nested exception is java.sql.SQLException: ORA-12899: value too large for column «BPMDB».»LSW_USR_GRP_XREF».»GROUP_NAME» (actual: 102, maximum: 101)

Cause

This error is seen in version 7.5.1 Fix Pack 1, when the short name of an assigned group exceeds 25 characters.The length of the GROUP_NAME column in the LSW_USR_GRP_XREF table is limited to 101 characters or 404 bytes.

The GROUP_NAMEs are structured as follows:
(Short name of group)_T/S_BPD-ID.Snapshot-ID

The string after the short name of the group consumes 76 characters, which leaves 25 characters for the user to specify for the short name of the group.

In V7.5.1 Fix Pack 2, the length for the GROUP_NAME column is increased to 256 characters, which leaves 180 characters for the user to specify the short name of a group

Источник

Sql State 72000 Error Code 12899 Ora-12899

We have collected for you the most relevant information on Sql State 72000 Error Code 12899 Ora-12899, as well as possible solutions to this problem. Take a look at the links provided and find the solution that works. Other people have encountered Sql State 72000 Error Code 12899 Ora-12899 before you, so use the ready-made solutions.

‘ORA-12899 — SQLState: 72000’ Causes Continuous Retrying .

https://support.oracle.com/knowledge/More%20Applications%20and%20Technologies/1519656_1.html

Jul 08, 2020 · ‘ORA-12899 — SQLState: 72000’ Causes Continuous Retrying of Transaction Persistence, Resulting in Loss of the Next Set of Transactions (Doc ID 1519656.1) Last updated on JULY 08, 2020

oracle — SQL Error: ORA-12899: value too large for column .

https://stackoverflow.com/questions/4347888/sql-error-ora-12899-value-too-large-for-column

This answer still comes up high in the list for ORA-12899 and lot of non helpful comments above, even if they are old. The most helpful comment was #4 for any professional trying to find out why they are getting this when loading data. Some characters are more than 1 byte in length, especially true on SQL Server.

How To Fix Sql State 72000 Error Code 12899 Hibernate (Solved)

http://serol.org/sql-state-72000-error-code-12899-hibernate.html

Sql State 72000 Error Code 12899 Could Not Execute Jdbc Batch Update in the windshield of some piper aircraft for? Atlassian Home Forum Spring Projects Batch Why does Deep Ora 12899 Value Too Large For Column Actual Maximum This forum is now a read-only archive.

Getting error «ORA-12899: value too large for column» in .

https://support.adeptia.com/hc/en-us/articles/360055102531-Getting-error-ORA-12899-value-too-large-for-column-in-Kernel-log

2020-10-20 22:53:54 java.sql.SQLException: ORA-12899: value too large for column «LOG_DB».»AU_SPAZIOLOG».»AU_TRANSACTION_PID» (actual: 61, maximum: 30) When a SPAZIO activity is executed, Adeptia saves its generated log details in the AU_SPAZIOLOG table along with its Transaction_PID.

How To Resolve the Error «ORA-12899: value too large for .

https://support.oracle.com/knowledge/PeopleSoft%20Enterprise/1965631_1.html

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.

ORA-12899: Value too Large for Column

http://www.dba-oracle.com/t_ora_12899_value_too_large_for_column.htm

Answer: To diagnose any error, you start by using the oerr utility to display the ORA-12899 error: ORA-12899: value too large for column string (actual: string, maximum: string) Cause: An attempt was made to insert or update a column with a value which is too wide for the width of the destination column.

ORA-12899: value too large for column length while .

https://collaborate.pega.com/discussion/ora-12899-value-too-large-column-length-while-performing-rules-upgrade-step-after-rules

Skip to main content Pega-wide Utility. Pega.com; Academy; Pega Community; More. PegaWorld; Pega Blog; Product Design

SQL state [72000]; error code [12899]зљ„й”™иЇЇ — д»Јз Ѓе¤©ењ°

https://www.codetd.com/article/1184289

и°ѓз”Ёзі»з»џпјљ org.springframework.orm.hibernate3.HibernateJdbcException: JDBC exception on Hibernate data access: SQLException for SQL [update MEMBER_ACCOUNT set VERSION=?,

Question on ORA-12899: value too large — Ask TOM

https://asktom.oracle.com/pls/apex/f?p=100:11:0. P11_QUESTION_ID:9533233800346995570

Question on ORA-12899: value too large Hi Tom,We have a migration project which from Sybase SQL Anywhere to Oracle. And there is an issue we still have no perfect solution. In Sybase, When insert/update to a target column, the source string will be auto truncate if the length more than the target column definition. For example. whe

Sql State 72000 Error Code 12899 Ora-12899 Fixes & Solutions

We are confident that the above descriptions of Sql State 72000 Error Code 12899 Ora-12899 and how to fix it will be useful to you. If you have another solution to Sql State 72000 Error Code 12899 Ora-12899 or some notes on the existing ways to solve it, then please drop us an email.

Источник

Confluence Support

Get started

Knowledge base

Products

Jira Software

Project and issue tracking

Jira Service Management

Service management and customer support

Jira Work Management

Manage any business project

Confluence

Bitbucket

Git code management

Resources

Documentation

Usage and admin help

Answers, support, and inspiration

System Status

Cloud services health

Suggestions and bugs

Feature suggestions and bug reports

Marketplace

Billing and licensing

Frequently asked questions

Viewport

Confluence

Not able to access Confluence page with the error: ‘ORA-12899: value too large for column «CONFDB».»LINKS».»DESTPAGETITLE»‘

Related content

Still need help?

The Atlassian Community is here for you.

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the server and data center platforms .

Problem

Users are not able to access a Confluence page with the error: value too large for column «CONFLUENCE».»LINKS».»DESTPAGETITLE»

The following appears in the atlassian-confluence .log

Diagnosis

Diagnostic Steps

• There are Linking Plugin by ServiceRocket plugin links inside the page

Источник

Исправление ошибок ЕИС 15.09.2017

Администратор

Исправлена ошибка «JDBC exeption on Hibernate data access: SQLExeption for SQL [insert into CRYPTO_SIGN (ATTACHMENT_ID _и другие поля_) values (?, ?, ? . ) ]; SQL state [72000]; error code [12899]; Could not execute JDBC batch update . JDBC exeption on Hibernate data access: SQLExeption for SQL [insert into CRYPTO_SIGN (ATTACHMENT_ID _и другие поля_) values (?, ?, ? . ) ]; SQL state [72000]; error code [12899]; Could not execute JDBC batch update . » возникающая у некоторых пользователей при попытке подписания изменений перечня организаций по которым проводится оценка соответствия.

Исправлена ошибка, в результате которой у некоторых пользователей положительный результат контроля по ч.5. Ст. 99 44-ФЗ мог не дойти до реестра контрактов и остаться в статусе «На контроле».

Исправлена ошибка, в результате которой суммы в полях «Фактически оплачено» и «Фактически оплачено заказчиком (в российских рублях)» на вкладке «Информация об исполнении (расторжении) контракта» могли отличаться.

Исправлена ошибка, в результате которой у некоторых пользователей при формировании исполнения контракта при типе документа «Платежный документа» мог некорректно сработать контроль на обязательность прикрепления документа.

Исправлена ошибка, в результате которой у пользователя после передачи полномочий и изменении привязки к органу контроля, при направлении плана закупок на проверку в орган контроля, документы могли поступать на проверку в личный кабинет старого органа контроля, у которого в перечне субъектов контроля организация-Заказчик не отображается.

Исправлена ошибка, в результате которой у некоторых реестровых записей планов- графиков, прошедших контроль в соответствии с ч. 5 ст. 99, могла не отображаться пиктограмма об успешном прохождении контроля.

Исправлена ошибка, в результате которой в карточке плана-графика на вкладке «Особые закупки» некоторые ИКЗ особых закупок могли не соответствовать ИКЗ в ЛК Заказчика.

Исправлена ошибка, в результате которой в карточке плана-графика на вкладке «Описание объекта закупки» в таблице с ТРУ «Описание объекта закупки» количества ТРУ могли отображаться для другого года планирования, отличного от года, установленного в ЛК Заказчика.

Исправлена ошибка, в результате которой в результатах расширенного поиска, при поиске по параметру «Заказчик», могли отображаться не все отчеты, соответствующие установленным параметрам поиска.

Источник

Troubleshooting

I have a CourseOffering object defined in my application. It has for primary key Semester, CourseNo, and Section which are strings.

I have another object called Faculty whose primary key is fac_id which is an integer.

Now I created an association between Faculty and CourseOffering and placed that association within CourseOffering.

@ManyToMany(cascade = CascadeType.ALL)
@JoinTable(name=»TAUGHT_BY», joinColumns = {@JoinColumn(name = «SEMESTER», nullable = false, updatable = false),
@JoinColumn(name = «COURSE_NO», nullable = false, updatable = false),
@JoinColumn(name = «SECTION», nullable = false, updatable = false)
},
inverseJoinColumns = { @JoinColumn(name = «FAC_ID», nullable = false, updatable = false) }

)

The join table is TAUGHT_BY which has a primary key as (SEMESTER_ID, COURSE_NO, SECTION and FAC_ID).

public Set<Faculty> getFaculty(){
return this.faculties;
}

public void setFaculty(Set<Faculty> faculties){
this.faculties = faculties;
}

I have also created a TaughtBy entity object in my application.

ISSUE
——-

Now the issue is this, as I am saving my CourseOffering object. I set the CourseOffering.setFaculty and update the object.

The UPDATE QUERY FIRES and the resulting query is this:
update
KARYN.COURSE_OFFERING
set
COURSE_TITLE=?,
COURSE_TOTAL=?,
COURSE_TYPE=?,
DATE_ENTERED=?,
DATE_UPDATED=?,
DISPLAY_FAC_NAME=?,
ENTERED_BY=?,
EVALREQD=?,
MIDEVAL=?,
MINI_NO=?,
NO_RATERS=?,
ONLINEEVAL=?,
PROJCOURSE=?,
RATING=?,
SEM_ORDER=?,
UNITS=?,
UPDATED_BY=?
where
COURSE_NO=?
and SECTION=?
and SEMESTER=?

16:22:12,730 INFO [STDOUT] Hibernate:
delete
from
TAUGHT_BY
where
SEMESTER=?
and COURSE_NO=?
and SECTION=?

16:22:12,730 INFO [STDOUT] Hibernate:
insert
into
TAUGHT_BY
(SEMESTER, COURSE_NO, SECTION, FAC_ID)
values
(?, ?, ?, ?)

16:22:12,746 INFO [STDOUT] Hibernate:
insert
into
TAUGHT_BY
(SEMESTER, COURSE_NO, SECTION, FAC_ID)
values
(?, ?, ?, ?)

16:22:12,746 INFO [STDOUT] Hibernate:
insert
into
TAUGHT_BY
(SEMESTER, COURSE_NO, SECTION, FAC_ID)
values
(?, ?, ?, ?)

16:22:12,746 INFO [STDOUT] Hibernate:
insert
into
TAUGHT_BY
(SEMESTER, COURSE_NO, SECTION, FAC_ID)
values
(?, ?, ?, ?)

while it is inserting into TAUGHTBY, maybe my relationship mapping is wrong.

I get the following error.

SQL Error: 12899, SQLState: 72000
value too large for column «KARYN».»TAUGHT_BY».»SEMESTER» (actual: 6, maximum: 3).

I verified that the SEMESTER in all the tables is of size 3. So what is happening.

P.S: THERE is 1 UPDATE QUERY AND 4 INSERT QUERIES since I am inserting 4 faculty objects into the DB.
Please let me know the solution.

Hi,

I am running a two-node cluster using JBoss 6.0.0.Final. I have problems serializing my timers to a MSSQL- or ORALE-database.

I migrated from JBoss 4.2.2GA. There the timers worked for single and clustermode. The timers are still running with JBoss 6 if I use the same JBoss in single-mode with the default configuration and hsql-database.

The problem seems to be that the column «INFO» in the JBoss-table «TIMER» is to small. It is mapped as a «RAW» Type with just 255 characters. I need «BLOB» which has 4000.

My Java-Code is as following:

public static void enableTimer(SessionPrincipal sessionPrincipal, TimerService timerService, long period)
{
        if (timerService.getTimers().size() == 0)
        {
            //This call crashes
            Timer timer =
                timerService.createTimer(period, period, new Object[] { sessionPrincipal, new Long(period) });
        }//...
}

The Oracle-message is:

ORA-12899: Wert zu groß für Spalte «MYAPP».»TIMER».»INFO» (aktuell: 1077, maximal: 255)

SQL Error: 12899, SQLState: 72000

I tried the following:

1. Set the dialect in the serveralldeployMY-ds.xml

2. I also set the dialect in serveralldeployersejb3.deployerMETA-INFjpa-deployers-jboss-beans.xml

3. I added a mapping for java.io.Serializable in serverallconfstandardjbosscmp-jdbc.xml

4. I tried with and without all the properties in my commondeployjboss-ejb3-timerservice-mk2.jarMETA-INFjboss-ejb3-timerservice-mk2-jboss-beans.xml

<persistence xmlns="http://java.sun.com/xml/ns/persistence"   
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
   xsi:schemaLocation="http://java.sun.com/xml/ns/persistence
   http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"
   version="1.0">
   <persistence-unit name="timerdb">
      <jta-data-source>java:/DefaultDS</jta-data-source>
      <class>org.jboss.ejb3.timerservice.mk2.persistence.TimerEntity</class>
      <properties>
          <property name="hibernate.dialect" value="org.hibernate.dialect.Oracle10gDialect"/>
          <property name="hibernate.transaction.factory_class" value="org.hibernate.ejb.transaction.JoinableCMTTransactionFactory"/>
          <property name="hibernate.transaction.manager_lookup_class" value="org.hibernate.transaction.JBossTransactionManagerLookup"/>
          <property name="hibernate.hbm2ddl.auto" value="update"/>
      </properties>
   </persistence-unit>
</persistence>

I am running out of ideas. Any suggestions?

Thanks in advance.

У меня возникла небольшая проблема – настройка кодов ошибок Oracle DB.

Я думаю, что можно сопоставить мои коды ошибок с помощью:

• добавление “CustomSQLErrorCodesTranslation”

• добавление “SQLErrorCodes”, который регистрирует “CustomSQLErrorCodesTranslation”

• добавить “SQLErrorCodeSQLExceptionTranslator” и установить мои “SqlErrorCodes”

и получить объект “SQLErrorCodeSqlExceptionTranslator” с помощью DI,
вызовите метод translate (String task, String sql, SQLException ex).

Здесь моя работа.

<bean id="sqlExceptionTranslator" class="org.springframework.jdbc.support.SQLErrorCodeSQLExceptionTranslator">
<property name="sqlErrorCodes" ref="OracleSqlErrorCodes" />
</bean>

<bean id="OracleSqlErrorCodes" class="org.springframework.jdbc.support.SQLErrorCodes">
<property name="badSqlGrammarCodes">
<value>900,903,904,917,936,942,17006</value>
</property>
<property name="invalidResultSetAccessCodes">
<value>17003</value>
</property>
<property name="duplicateKeyCodes">
<value>1</value>
</property>
<property name="dataIntegrityViolationCodes">
<value>1400,1722,2291,2292</value>
</property>
<property name="dataAccessResourceFailureCodes">
<value>17002,17447</value>
</property>
<property name="cannotAcquireLockCodes">
<value>54</value>
</property>
<property name="cannotSerializeTransactionCodes">
<value>8177</value>
</property>
<property name="deadlockLoserCodes">
<value>60</value>
</property>
<property name="customTranslations">
<list>
<bean id="oracleCustomTranslations" class="org.springframework.jdbc.support.CustomSQLErrorCodesTranslation">
<property name="errorCodes" value="12899" />
<property name="exceptionClass" value="com.musicovery.bookervery.db.exception.SampleException" />
</bean>
</list>
</property>
</bean>

в области JAVA,

@Test(expected=SampleException.class)
public void addMemberWithLongValue(){
memberCommand1.setName("very very very very very very very very very long text");

try{
memberService.addMember(memberCommand1);
}catch(DataAccessException e){


SQLException sqlEx = new SQLException(e);

DataAccessException dae = sqlExceptionTranslator.translate("task? what is it?", null, sqlEx);
System.err.println("Derived from DataAccessException : " + dae.getClass().getName());

throw dae;
}

}

При запуске этого кода отображается redbar

Ничем не отличается от того, добавлена ​​ли ошибка в код сопоставления или нет.

При вставке данных с слишком большим значением в Oracle DB возвращается код ошибки 12899.

Caused by: java.sql.SQLException: ORA-12899: value too large for column "MUSICOVERY"."MEMBERS"."NAME" (actual: 54, maximum: 12)

Я хочу сопоставить код ошибки 12899 с конкретным классом исключений.

Любая идея?

Спасибо заранее.

Кроме того, я сожалею, что мой английский не очень хорош.

ниже содержимое добавляется периодически, чтобы помочь вам найти правильный ответ.

/////////////////////////////////
SampleException
/////////////////////////////////

package com.musicovery.bookervery.db.exception;
import org.springframework.dao.DataAccessException;

public class SampleException extends DataAccessException{
private static final long serialVersionUID = 1L;

public SampleException(String msg, Throwable cause) {
super(msg, cause);
System.out.println("SampleException initialized");
}
}

/////////////////////////////////
Изменить – printStackTrace
/////////////////////////////////

org.springframework.jdbc.UncategorizedSQLException: task? what is it?; uncategorized SQLException for SQL []; SQL state [null]; error code [0]; org.springframework.jdbc.UncategorizedSQLException:
### Error updating database.  Cause: java.sql.SQLException: ORA-12899: value too large for column "MUSICOVERY"."MEMBERS"."NAME" (actual: 54, maximum: 12)

### The error may involve com.musicovery.bookervery.dao.MemberDao.addMember-Inline
### The error occurred while setting parameters
### Cause: java.sql.SQLException: ORA-12899: value too large for column "MUSICOVERY"."MEMBERS"."NAME" (actual: 54, maximum: 12)

; uncategorized SQLException for SQL []; SQL state [72000]; error code [12899]; ORA-12899: value too large for column "MUSICOVERY"."MEMBERS"."NAME" (actual: 54, maximum: 12)
; nested exception is java.sql.SQLException: ORA-12899: value too large for column "MUSICOVERY"."MEMBERS"."NAME" (actual: 54, maximum: 12)
; nested exception is java.sql.SQLException: org.springframework.jdbc.UncategorizedSQLException:
### Error updating database.  Cause: java.sql.SQLException: ORA-12899: value too large for column "MUSICOVERY"."MEMBERS"."NAME" (actual: 54, maximum: 12)

### The error may involve com.musicovery.bookervery.dao.MemberDao.addMember-Inline
### The error occurred while setting parameters
### Cause: java.sql.SQLException: ORA-12899: value too large for column "MUSICOVERY"."MEMBERS"."NAME" (actual: 54, maximum: 12)

; uncategorized SQLException for SQL []; SQL state [72000]; error code [12899]; ORA-12899: value too large for column "MUSICOVERY"."MEMBERS"."NAME" (actual: 54, maximum: 12)
; nested exception is java.sql.SQLException: ORA-12899: value too large for column "MUSICOVERY"."MEMBERS"."NAME" (actual: 54, maximum: 12)

at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:83)
at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:80)
at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:80)
at com.musicovery.bookervery.serviceTest.MemberServiceTest.addMemberWithLongValue(MemberServiceTest.java:87)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
at org.junit.internal.runners.statements.ExpectException.evaluate(ExpectException.java:21)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
at org.springframework.test.context.junit4.statements.RunBeforeTestMethodCallbacks.evaluate(RunBeforeTestMethodCallbacks.java:74)
at org.springframework.test.context.junit4.statements.RunAfterTestMethodCallbacks.evaluate(RunAfterTestMethodCallbacks.java:83)
at org.springframework.test.context.junit4.statements.SpringRepeat.evaluate(SpringRepeat.java:72)
at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:231)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
at org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61)
at org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:71)
at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:174)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)
Caused by: java.sql.SQLException: org.springframework.jdbc.UncategorizedSQLException:
### Error updating database.  Cause: java.sql.SQLException: ORA-12899: value too large for column "MUSICOVERY"."MEMBERS"."NAME" (actual: 54, maximum: 12)

### The error may involve com.musicovery.bookervery.dao.MemberDao.addMember-Inline
### The error occurred while setting parameters
### Cause: java.sql.SQLException: ORA-12899: value too large for column "MUSICOVERY"."MEMBERS"."NAME" (actual: 54, maximum: 12)

; uncategorized SQLException for SQL []; SQL state [72000]; error code [12899]; ORA-12899: value too large for column "MUSICOVERY"."MEMBERS"."NAME" (actual: 54, maximum: 12)
; nested exception is java.sql.SQLException: ORA-12899: value too large for column "MUSICOVERY"."MEMBERS"."NAME" (actual: 54, maximum: 12)

at com.musicovery.bookervery.serviceTest.MemberServiceTest.addMemberWithLongValue(MemberServiceTest.java:85)
... 30 more
Caused by: org.springframework.jdbc.UncategorizedSQLException:
### Error updating database.  Cause: java.sql.SQLException: ORA-12899: value too large for column "MUSICOVERY"."MEMBERS"."NAME" (actual: 54, maximum: 12)

### The error may involve com.musicovery.bookervery.dao.MemberDao.addMember-Inline
### The error occurred while setting parameters
### Cause: java.sql.SQLException: ORA-12899: value too large for column "MUSICOVERY"."MEMBERS"."NAME" (actual: 54, maximum: 12)

; uncategorized SQLException for SQL []; SQL state [72000]; error code [12899]; ORA-12899: value too large for column "MUSICOVERY"."MEMBERS"."NAME" (actual: 54, maximum: 12)
; nested exception is java.sql.SQLException: ORA-12899: value too large for column "MUSICOVERY"."MEMBERS"."NAME" (actual: 54, maximum: 12)

at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:83)
at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:80)
at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:80)
at org.mybatis.spring.MyBatisExceptionTranslator.translateExceptionIfPossible(MyBatisExceptionTranslator.java:71)
at org.mybatis.spring.SqlSessionTemplate$SqlSessionInterceptor.invoke(SqlSessionTemplate.java:346)
at com.sun.proxy.$Proxy14.insert(Unknown Source)
at org.mybatis.spring.SqlSessionTemplate.insert(SqlSessionTemplate.java:231)
at org.apache.ibatis.binding.MapperMethod.execute(MapperMethod.java:59)
at org.apache.ibatis.binding.MapperProxy.invoke(MapperProxy.java:38)
at com.sun.proxy.$Proxy18.addMember(Unknown Source)
at com.musicovery.bookervery.service.MemberServiceImpl.addMember(MemberServiceImpl.java:17)
at com.musicovery.bookervery.serviceTest.MemberServiceTest.addMemberWithLongValue(MemberServiceTest.java:82)
... 30 more
Caused by: java.sql.SQLException: ORA-12899: value too large for column "MUSICOVERY"."MEMBERS"."NAME" (actual: 54, maximum: 12)

at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:70)
at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:133)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:206)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:455)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:413)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:1034)
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:194)
at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:953)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1222)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3387)
at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3488)
at oracle.jdbc.driver.OraclePreparedStatementWrapper.execute(OraclePreparedStatementWrapper.java:1374)
at org.apache.ibatis.executor.statement.PreparedStatementHandler.update(PreparedStatementHandler.java:22)
at org.apache.ibatis.executor.statement.RoutingStatementHandler.update(RoutingStatementHandler.java:51)
at org.apache.ibatis.executor.SimpleExecutor.doUpdate(SimpleExecutor.java:29)
at org.apache.ibatis.executor.BaseExecutor.update(BaseExecutor.java:88)
at org.apache.ibatis.executor.CachingExecutor.update(CachingExecutor.java:43)
at org.apache.ibatis.session.defaults.DefaultSqlSession.update(DefaultSqlSession.java:121)
at org.apache.ibatis.session.defaults.DefaultSqlSession.insert(DefaultSqlSession.java:110)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.mybatis.spring.SqlSessionTemplate$SqlSessionInterceptor.invoke(SqlSessionTemplate.java:338)
... 37 more

Я проверил, какой код ошибки имеет исключение.

SQLException sqlEx = new SQLException(e);
System.out.println("sqlEx error code : " + sqlEx.getErrorCode());

Консоль:

sqlEx error code : 0

Почему это 0? он должен быть 12899.

Я развиваюсь с помощью MyBatis. Я прочитал начальную документацию
И эти API вроде бы не бросают никаких исключений. поэтому я предполагаю, что код ошибки sql равен 0.

Скажите, пожалуйста, любой источник, который вы хотите, я отредактирую эту статью.