Archives of the TeradataForum
Message Posted: Mon, 10 Nov 2003 @ 13:28:39 GMT
We had a problem with a job processing between the MVS mainframe and Teradata through an ESCON channel. It caused a tparestart loop, where a restart would occur, logons would be enabled, and another restart would initiate.
The alert messages indicated a "segmentation violation and did not have a handler for a SIGSEGV signal .... versionTask is exiting due to a segmentation violation.si_code".
Can someone explain: What a segmentation violation is? What causes them? How to prevent them?
We are on V2R3, and the problem may be associated with a Fastload job with a Time datatype field.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|