Tag Archives: db2

DB2 (Reason code = “18”.. SQLCODE=-30090, SQLSTATE=25000)

By | February 8, 2017

In a setup having an enterprise application depending on a database instance where some tables are defined as nicknames to tables from a federated database, it can happen to get this very cryptic DB2 error. I already had a post related to this case when the setup uses access to a federated database https://blog.voina.org/db2-sql-error-30090-caused-by-read-only-table-nickname-to-a-federated-database/. You… Read More »

Advertisements

DB2 + Websphere : Feature is not implemented: PreparedStatement.setBinaryStream

By | February 8, 2017

From a very strange reason after updating the hibernate4 from version 4.1.4 to 4.2.5 there was suddenly a weird behaviour of the EJB3.1 enterprise application I am working on. A piece of code that commits to the database an object (ProcessingStatus) containing a BLOB was throwing the following: [1/31/16 23:37:15:922 EET] 000000eb AbstractBatch Z org.hibernate.engine.jdbc.batch.internal.AbstractBatchImpl… Read More »

DB2: Inline LOBS

By | February 8, 2017

LOBS is the DB2 way of dealing with big data. In db2 you can have a table that contains a column defined as LOB where one can dump large binary data (images, compressed text files, video or audio). The problem is the way this LOBS are stored by DB2. By default they are stored “offline”… Read More »

DB2: (SQL Error: -30090) caused by XA access to a nickname to a federated database

By | February 8, 2017

In a setup having an enterprise application depending on a database instance where some tables are defined as nicknames to tables from a federated database, it can happen to get this very cryptic DB2 error. [12/10/15 18:06:54:895 IST] 00000073 SqlExceptionH Z org.hibernate.engine.jdbc.spi.SqlExceptionHelper logExceptions SQL Error: -4229, SQLState: null [12/10/15 18:06:54:903 IST] 00000073 SqlExceptionH Z org.hibernate.engine.jdbc.spi.SqlExceptionHelper… Read More »

DB2 Sqlcode: -964, Sqlstate: 57011 (transaction log for the database is full)

By | February 8, 2017

I got this error while doing some performance tests on a high volume system using DB2. This is the usual unintuitive error that IBM likes to give to the users 🙂 IN plain English this means that “The transaction log for the database is full.” This appears when you have to execute UPDATE or INSERT… Read More »