getColDesc failed

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
keshav0307
Premium Member
Premium Member
Posts: 783
Joined: Mon Jan 16, 2006 10:17 pm
Location: Sydney, Australia

getColDesc failed

Post by keshav0307 »

main_program: Internal Error: (colDesc):orautils.C: 1653: getColDesc failed.
Traceback: Could not obtain stack trace; check that 'gdb' and 'sed' are installed and on your PATH
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Search is your friend. With over 100 posts you should know that by now.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
keshav0307
Premium Member
Premium Member
Posts: 783
Joined: Mon Jan 16, 2006 10:17 pm
Location: Sydney, Australia

Post by keshav0307 »

i tried but its doen't help me, so i put a new post
prabu
Participant
Posts: 146
Joined: Fri Oct 22, 2004 9:12 am

Post by prabu »

keshav0307 wrote:i tried but its doen't help me, so i put a new post

This error is due to the
ORCHESTRATE Oracle driver
not installed properly.

Please reinstall the drivers [should be in your ORCH_HOME/install dir]

Hope this helps

regards,
Prabu
keshav0307
Premium Member
Premium Member
Posts: 783
Joined: Mon Jan 16, 2006 10:17 pm
Location: Sydney, Australia

Post by keshav0307 »

Prabu , the database is Teradata. i only change the buffer to 64K and its working fine now.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Why would a Teradata issue trigger a call to what is apparently an Oracle utility? :?
-craig

"You can never have too many knives" -- Logan Nine Fingers
keshav0307
Premium Member
Premium Member
Posts: 783
Joined: Mon Jan 16, 2006 10:17 pm
Location: Sydney, Australia

Post by keshav0307 »

ooops. i was confused with the similar problem in my a job having Teradata stage.

problem in this job is because the oracle table has a column timestamp type. so the job is running fine in 7.5.2 and giving thsi problem in 7.5.1A.
lfong
Premium Member
Premium Member
Posts: 42
Joined: Fri Sep 09, 2005 7:48 am

Post by lfong »

keshav0307 wrote:ooops. i was confused with the similar problem in my a job having Teradata stage.

problem in this job is because the oracle table has a column timestamp type. so the job is running fine in 7.5.2 and giving thsi problem in 7.5.1A.
what paramater setting in the administrator was changed to fix this
Post Reply