Abnormal termination of a Stored Procedure stage

[atan003]

Abnormal termination of a Stored Procedure stage

When a sequence called a job (Allow Multiple Instance, and named "sp_make_id")
to execute a stored procedure, it is aborted with log message
"Abnormal termination of stage sp_make_id.account.sp_etl_makeId detected"

Could anyone tell me why?

----------------- the primary log message -----------------
Item #: 405
Event ID: 404
Timestamp: 2007-01-17 19:17:37
Type: Warning
User Name: TWD|taiyou
Message: Abnormal termination of stage sp_make_id.account.sp_etl_makeId detected

Item #: 406
Event ID: 405
Timestamp: 2007-01-17 19:17:37
Type: Control
User Name: TWD|taiyou
Message: Job sp_make_id.account aborted.

----------------- the detailed log message -----------------

Item #: 401
Event ID: 400
Timestamp: 2007-01-17 19:17:35
Type: Info
User Name: TWD|taiyou
Message: Environment variable settings:
ALLUSERSPROFILE=C:\Documents and Settings\All Users
APT_MONITOR_MINTIME=10
BELL=^G
ClusterLog=C:\WINDOWS\Cluster\cluster.log
CommonProgramFiles=C:\Program Files\Common Files
COMPUTERNAME=ETLSVR
ComSpec=C:\WINDOWS\system32\cmd.exe
DSIPC_OPEN_TIMEOUT=30
DSPackagePath=C:\Ascential\DataStage\Package
DS_ENABLE_RESERVED_CHAR_CONVERT=0
DS_OPERATOR_BUILDOP_DIR=buildop
DS_OPERATOR_WRAPPED_DIR=wrapped
DS_TDM_PIPE_OPEN_TIMEOUT=720
DS_TDM_TRACE_SUBROUTINE_CALLS=0
FLAVOR=-1
FP_NO_HOST_CHECK=NO
Include=C:\Sybase\INCLUDE
Lib=C:\sybase\ADO.NET\dll;C:\Sybase\LIB
NUMBER_OF_PROCESSORS=2
OS=Windows_NT
Path=C:\sybase\JS-12_5\bin;C:\sybase\ADO.NET\dll;C:\sybase\OLEDB;C:\sybase\ODBC;C:\sybase\OCS-12_5\lib3p;C:\sybase\OCS-12_5\dll;C:\sybase\OCS-12_5\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Ascential\ODBCdrivers
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH
PROCESSOR_ARCHITECTURE=x86
PROCESSOR_IDENTIFIER=x86 Family 15 Model 4 Stepping 3, GenuineIntel
PROCESSOR_LEVEL=15
PROCESSOR_REVISION=0403
ProgramFiles=C:\Program Files
SYBASE=C:\sybase
SYBASE_JRE=C:\sybase\shared-1_0\JRE-1_3
SYBASE_OCS=OCS-12_5
SystemDrive=C:
SystemRoot=C:\WINDOWS
TEMP=C:\WINDOWS\TEMP
TERM=console
TMP=C:\WINDOWS\TEMP
UNIVERSE_CONTROLLING_TERM=1
UNIVERSE_PARENT_PROCESS=464
USER=TWD\taiyou
USERPROFILE=C:\Documents and Settings\Default User
WHO=BISETL
windir=C:\WINDOWS
DS_USERNO=-4188


Item #: 402
Event ID: 401
Timestamp: 2007-01-17 19:17:35
Type: Info
User Name: TWD|taiyou
Message: sp_make_id.account: Set NLS locale to TW-CHINESE,TW-CHINESE,TW-CHINESE,TW-CHINESE,TW-CHINESE

Item #: 403
Event ID: 402
Timestamp: 2007-01-17 19:17:35
Type: Info
User Name: TWD|taiyou
Message: sp_make_id.account.sp_etl_makeId: DSD.StageRun Active stage starting, tracemode = 0.

Item #: 404
Event ID: 403
Timestamp: 2007-01-17 19:17:35
Type: Info
User Name: TWD|taiyou
Message: sp_make_id.account.sp_etl_makeId: Set NLS locale to TW-CHINESE,TW-CHINESE,TW-CHINESE,TW-CHINESE,TW-CHINESE

Item #: 405
Event ID: 404
Timestamp: 2007-01-17 19:17:37
Type: Warning
User Name: TWD|taiyou
Message: Abnormal termination of stage sp_make_id.account.sp_etl_makeId detected

Item #: 406
Event ID: 405
Timestamp: 2007-01-17 19:17:37
Type: Control
User Name: TWD|taiyou
Message: Job sp_make_id.account aborted.

Item #: 407
Event ID: 406
Timestamp: 2007-01-17 19:17:37
Type: RunJob
User Name: TWD|taiyou
Message: (C01_BeforeCalc_Water) <- sp_make_id.account: Job under control finished.

[chulett]

As with all 'abnormal termination' errors, you need to reset the job from the Director and let us know if an entry labelled 'From previous run...' is logged. If it does, post the contents.

[atan003]

Hi, Chulett,

Excuse me, I don't catch your meaning.

Is your meaning that I post the previous run log of the job to you.

Thanks

Atan Chen

Email: atan003@163.com
MSN: atan003@163.com
Skype: atan003

[DSguru2B]

It means, to reset the job from director. Some more messages will pop up in your log file. Post them here.

[atan003]

It is urgent to resolve, so I have recompiled the job and run OK.
Now, I can't reset it and can not get the reset messages.

This error happened first time.
It run OK all the previous run.

[DSguru2B]

What changed between yesterday and today? Maybe the database wasnt available. For now its just a guessing game. When the error occurs again, reset the job for more information.

[ray.wurlod]

Reset is different from recompile. By recompiling you have destroyed any preserved diagnostic information from the previous run. Get in the habit of resetting aborted jobs, and scanning the log for an entry titled "From previous run...".