Getting error "ORA-12899: value too large for column" in Kernel log

Issue:

We are getting the Value too large for column AU_SpazioLog.AU_TransactionPID errors in the Kernel logs while using Spazio activity. Below is the error excerpt:

ERROR [ActiveMQ Session Task-130] Event com.adeptia.indigo.services.transport.spazio.topic.SpazioTopicLogMessageReceive.insertDataToSpazioLogTable(SpazioTopicLogMessageReceive.java:500) - ||||null|||||null|Error in inserting log record for Spazio MFT/s; error code: 12899; SQL state: 72000[ORA-12899: value too large for column "GHIBLI"."AU_SPAZIOLOG"."AU_TRANSACTION_PID" (actual: 61, maximum: 30)
2020-10-20 22:53:54 ]|10.101.139.198||null
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. In Parent-child Process Flows, the Transaction_PID will be the combination of Parent & Child process flow ID and this error occur due to the limitation of column size.

 

Solution:

In the Adeptia Log Database, the default size of column AU_TRANSACTION_PID is 30 and it works fine with a standalone process flow. But with the Parent-child process flow, the column size should be large. Following is the query that needs to be run on the LOG Database for AU_SPAZIOLOG table to increase the size of the column.

ALTER TABLE AU_SPAZIOLOG
MODIFY AU_TRANSACTION_PID VARCHAR2 (70);

or

ALTER TABLE AU_SPAZIOLOG
MODIFY COLUMN AU_TRANSACTION_PID VARCHAR2 (70);

Note: The column size has to be increased by more than 70 if more than 1 child process flows are involved.

Have more questions? Submit a request

0 Comments

Article is closed for comments.