Start the Windows Event Viewer. When the Teradata DBS restarted, an error event with some diagnostic information should have been recorded in the application event log.
Hi Jim
Checked the event log and got this:
The following information is part of the event: Event number 33-10416-00 (severity 50, category 10), occurred on Thu Sep 24 21:06:48 2009, at 001-01 (Vproc 1, partition 11, task 5188) in system localhost in Module actmain, version PDE:12.00.00.10,TDBMS:12.00.00.10,RSG: 12.00.00.10,TGTW:12.00.00.10,TDGSS:12.00.00.10
Task aborted abnormally.
Exception dump:
Registers:
Context flags=0x0001003F
EAX = 0x00000000 - EBX = 0x0A17B2F0
ECX = 0x0B4AE384 - EDX = 0x0B4BEC4C
ESI = 0x0B49FFBC - EDI = 0x0B4BEC6C
EBP = 0x0B49FFA0 - ESP = 0x0B49FBF4
CS = 0x0000001B - EIP = 0x0B4BEC6C
DS = 0x00000023 - ES = 0x00000023
FS = 0x0000003B - GS = 0x00000000
SS = 0x00000023 - flags = 0x00010206
Exception record:
continuable
code 0xC0000005 (EXCEPTION_ACCESS_VIOLATION)
addr 0x0B4BEC6C
Proc/Fun File Line
------------------------------------------------------ ------------
pde.dll/syscalldriver+2a9 in syscall.c:255
pde.dll/syscalldriver+302 in syscall.c:303
fil1.dll/cylacqci+223 in cylacqci.c:266
pde.dll/syscalldriver+302 in syscall.c:303
fil1.dll/ftrfsglogsrb+7ed in ftrfsglog.c:499
and this:
The following information is part of the event: Event number 33-10416-00 (severity 70, category 10), occurred on Thu Sep 24 21:34:43 2009, at 001-01 (Vproc 0, partition 11, task 5564) in system localhost in Module actmain, version PDE:12.00.00.10,TDBMS:12.00.00.10,RSG: 12.00.00.10,TGTW:12.00.00.10,TDGSS:12.00.00.10
Task aborted abnormally.
Exception dump:
Registers:
Context flags=0x0001003F
EAX = 0x00000000 - EBX = 0x0A2CA530
ECX = 0x0B35C15C - EDX = 0x0B35E994
ESI = 0x0B343A34 - EDI = 0x0B35E9B4
EBP = 0x0B343878 - ESP = 0x0B3434CC
CS = 0x0000001B - EIP = 0x0B35E9B4
DS = 0x00000023 - ES = 0x00000023
FS = 0x0000003B - GS = 0x00000000
SS = 0x00000023 - flags = 0x00010216
Exception record:
continuable
code 0xC0000005 (EXCEPTION_ACCESS_VIOLATION)
addr 0x0B35E9B4
Proc/Fun File Line
------------------------------------------------------ ------------
*** UNABLE TO OBTAIN TRACEBACK FOR NOW ***
So in my case the faulting module is ACTMAIN. I don't know how much further forward this gets me.
BRgds
James
You may be running into the infamous Windows DEP feature. Check out this URL for a detailed explanation of DEP:
http://support.microsoft.com/kb/875352
In order to run Teradata, you will need to disable this feature.
Edit c:\boot.ini, look for "/noexecute=" and change the parameter value after "=" to "alwaysoff". The file should like something like this:
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=alwaysoff /fastdetect
Thanks, Jim - I'll give that a try when I get a little time to play.
Your help is appreciated. Thank you.
Hello all
(Sorry for the cross-post. Originally posted in Partner Apps forum by mistake).
Getting DBC restarts with fresh install of TDE 12 on Win2003 Server using both "out of the box" and updated (12.0.0.7) ODBC drivers (TDATA.DLL reports "Connection reset by peer").
DBC restarts happen when using BTEQWin, too - just had the database restart on me while executing a select against dbc.columns as a test in BTEQWin (to pinpoint ODBC as the problem). The test failed, so the problem is not necessarily ODBC-related. I seem to get a DBC restart (almost) every time I submit a query, from any client.
Teradata Service Control app. shows TD switching from "Running" to "RESET/STOPTASKS", then going into "START/NETCONFIG" etc... effectively restarting itself after some unexpected failure.
Is this a known bug? Is there a workaround? Or do I have to put it on XP for it to work reliably/at all?
TIA for any guidance.