STACK TRACE ERROR

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
tomengers
Participant
Posts: 167
Joined: Tue Nov 19, 2002 12:20 pm
Location: Key West

STACK TRACE ERROR

Post by tomengers »

Hi Folks ...

We are getting the following error on a first-time write to a new SQL Server table:

odbc_DIM_VOUCHER,0: Internal Error: (0): odbcupsert.C: 1328
Traceback: Could not obtain stack trace; check that 'gdb' and 'sed' are installed and on your PATH

The error occurs immediately, so it is not a volume issue.

Any suggestions most appreciated.

... tom
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

I know we've seen that gdb/sed message posted here before - do an Exact search for "check that 'gdb' and 'sed' are installed" and see if any of those posts help.
-craig

"You can never have too many knives" -- Logan Nine Fingers
tomengers
Participant
Posts: 167
Joined: Tue Nov 19, 2002 12:20 pm
Location: Key West

STACK TRACE ERROR

Post by tomengers »

Problem resolved: was using Surrogate Key Generator and did not notice that datatype generated for surrogate column was BigInt Unsigned - and that was being mapped into the target column which was Integer 10. Compile was clean, but execution was not.

Thanks for the help ...

... tom
Post Reply