Strange Internal error(blockSizeActual >= v4BlockHeader)

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
Kbhujad
Participant
Posts: 10
Joined: Mon Jul 21, 2008 7:31 am
Location: Pune
Contact:

Strange Internal error(blockSizeActual >= v4BlockHeader)

Post by Kbhujad »

Hi,

I am getting a strange error in my job as below:

'Seql_ExtractForQNA,0: Internal Error: (blockSizeActual >= v4BlockHeader::size ()): datamgr/partition.C: 434
Traceback: Could not obtain stack trace; check that 'gdb' and 'sed' are installed and on your PATH'

Can someone guide me?

Thanks in Advance.

Regards,
Kshitija J.
rishi
Participant
Posts: 16
Joined: Thu Aug 03, 2006 3:05 am

Post by rishi »

If we add APT_DISABLE_COMBINATION environment parameter and set it to TRUE the job runs fine. Otherwise it aborts with these error messages -

FIMSCNSPC004.Aggr_22.DSLink83_Sort,3: Internal Error: (blockSizeActual >= v4BlockHeader::size ()): datamgr/partition.C: 434
Traceback: Could not obtain stack trace; check that 'gdb' and 'sed' are installed and on your PATH

Seql_ExtractForQNA,0: Internal Error: (blockSizeActual >= v4BlockHeader::size ()): datamgr/partition.C: 434
Traceback: Could not obtain stack trace; check that 'gdb' and 'sed' are installed and on your PATH

Appreciate any help.

Thanks
Rishi (Kshitija's teammate)
Subscribe to email notifications. Save paper!
Post Reply