LAE

Welcome to the LAE community!  Please feel free to start a discussion in the discussion tab or join in a conversation.

Discussions

Members

Resources

Events

 View Only
  • 1.  DB Store Node

    Employee
    Posted 03-25-2010 19:32

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: Rapkat

    This is an example of what I am trying to run, the static node data represents all the nodes to get the data I have in the static node. I run the DB Store Node get a green tick but all of the data is contained in the output node as errors.

    What am I doing wrong?

    2010-03-26 15:09:24; Level: 2; Type: 0; Desc: "statement is already locked"; File: "\src\brain_d\jigsaw\Code\Source\DB\ODBC\OdbcState ment.cpp"; Line: 445; Context: "OdbcStatement::getLock()"
    2010-03-26 15:09:24; Level: 2; Type: 0; Desc: "Error while commiting row: statement is already locked"; File: "\src\brain_d\jigsaw\Code\Source\DB\DBInsertLoader .cpp"; Line: 389; Context: "DBInsertLoader::CommitRow()"
    2010-03-26 15:09:24; Level: 2; Type: 0; Desc: "conversion exception"; File: "\src\brain_d\ra_dev\code\source\tableio\DBTableOu tput.cpp"; Line: 218; Context: ""
    Attachments:
    DB download.brg


  • 2.  RE: DB Store Node

    Employee
    Posted 03-29-2010 10:41

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: rboccuzzi

    I think this sounds like it might be a configuration issue or possibly a driver incompatible issue.

    If you can reach out and contact our support organization in a way best suited for you, I think that is the most prudent course of action to help you resolve this issue in an expedient manner.

    Cheers
    Rich


  • 3.  RE: DB Store Node

    Employee
    Posted 02-20-2013 06:19

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: Wizardous

    Hi,

    I have the same problem when i try to load results as a table to a teradata DB. Any suggestions?

    �zg�n

    2013-02-20 14:42:38.000; WARN: conversion exception
    id: 0 chain: 0 group: 0
    cppDetail: context: ..\io\DBTableOutput.cpp@217

    2013-02-20 14:42:38.000; WARN: statement is already locked
    id: 0 chain: 0 group: 0
    cppDetail: context: OdbcStatement::getLock() .\OdbcStatement.cpp@445

    2013-02-20 14:42:38.000; WARN: Error while commiting row: statement is already locked
    id: 0 chain: 0 group: 0
    cppDetail: context: DBInsertLoader::CommitRow() .\DBInsertLoader.cpp@394


  • 4.  RE: DB Store Node

    Employee
    Posted 02-21-2013 08:35

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: johnpelz

    This issue seemed to be related to using the ODBC client / drivers to connect to the Teradata database. Wizardous installed Teradata's own client drivers and switched from using ODBC and this issue was resolved. It is recommended that you use the Teradata client / drivers over ODBC when using the Database nodes in Lavastorm (DbQuery, DbStore, DbExecute).


  • 5.  RE: DB Store Node

    Employee
    Posted 06-05-2013 02:03

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: Feridun

    Hey guys,

    We had the same problem here. It was because of a not-nullable field that was somehow null in our graph. Just modifying the not-nullable to nullable solved the issue.

    FYI

    Feridun


  • 6.  RE: DB Store Node

    Employee
    Posted 12-15-2014 20:25

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: Jensen

    I faced the same problem.
    The cause in my case was due to a field name which is a reserved word, more specifically "Date".
    By changing the reserved word, I managed to get the data stored correctly into the database.