Page 1 of 1

Issue with ODBC

Posted: Tue Apr 28, 2009 1:39 am
by rkdatastage
Hi

I am trying to load data to a sqlserver table using odbc and i am getting this error. Can some one share your ideas.


Message:
1: Failure during execution of operator logic.
2: Input 0 consumed 0 records.
3: Import complete; 189 records imported successfully, 0 rejected.
4: Failure during execution of operator logic.
5: Input 0 consumed 0 records.
6: Internal Error: (0): odbcwrite.C: 905
Traceback: Could not obtain stack trace; check that 'gdb' and 'sed' are installed and on your PATH
7: Player 6 terminated unexpectedly.
8: main_program: APT_PMsectionLeader(2, node2), player 6 - Unexpected exit status 1.
9: Internal Error: (0): odbcwrite.C: 905
Traceback: Could not obtain stack trace; check that 'gdb' and 'sed' are installed and on your PATH
10: node_node1: Player 6 terminated unexpectedly.
11:
{
main_program: APT_PMsectionLeader(1, node1), player 6 - Unexpected exit status 1.
APT_PMsectionLeader(2, node2), player 3 - Unexpected exit status 1.
APT_PMsectionLeader(2, node2), player 4 - Unexpected exit status 1.
APT_PMsectionLeader(1, node1), player 3 - Unexpected exit status 1.
APT_PMsectionLeader(1, node1), player 4 - Unexpected exit status 1.
APT_PMsectionLeader(2, node2), player 5 - Unexpected exit status 1.
APT_PMsectionLeader(1, node1), player 5 - Unexpected exit status 1.
}
12 : main_program: Step execution finished with status = FAILED.
13: Job xxx_test aborted.

There is another job which is loading data into database and i am working in the same environment.

Thanks in advance

Regards
RK

Posted: Tue Apr 28, 2009 1:42 am
by ray.wurlod
Start by dumping and examining the score, so you can figure out which operator player 6 is.

Search the forum for the exact message about the debugging utilities gdb and sed.

Posted: Tue Apr 28, 2009 2:14 am
by rkdatastage
Hi
I am bit confused from where to start debugging this issue. Can some guide me to some extent to resolve this issue

Regards
RK

Posted: Tue Apr 28, 2009 3:27 am
by Pagadrai
Hi,
As suggested above start with examining the score dumps.

Add the Environment Variable APT_DUMP_SCORE to your job and set this to TRUE. Observe the job log for details.

Then do a search in this forum as Ray mentioned.