Database Crashes after few seconds - Teradata 13 on SLES VM image

Teradata Express Software
Formerly this board name was Cloud Computing. The name was changed to better represent the product areas covered.
Enthusiast

Database Crashes after few seconds - Teradata 13 on SLES VM image

Hello,

We have downloaded the Teradata 13 1TB VM image and brought it online under VMWare running on RH Linux.

The database crashes after few seconds. Please help me in locating the log files which I can check to identify the issue.

Appreciate your help.

vsuteradev02:/dev # uname -a

Linux vsuteradev02 2.6.16.53-0.8.PTF.328697.0-smp #1 SMP Fri Aug 31 13:07:27 UTC 2007 x86_64 x86_64 x86_64 GNU/Linux

vsuteradev02:~ # pdestate -a

PDE state: DOWN/HARDSTOP

vsuteradev02:~ # /etc/init.d/tpa start

Teradata Database Initiator service is starting...

Teradata Database Initiator service started successfully.

vsuteradev02:~ # pdestate -a

PDE state is RESET/KILLTASKS.

vsuteradev02:~ # pdestate -a

PDE state is START/GDOSYNC.

vsuteradev02:~ # pdestate -a

PDE state is RESET/KILLTASKS.

vsuteradev02:~ # pdestate -a

PDE state is START/GDOSYNC.

vsuteradev02:~ # pdestate -a

PDE state is DOWN/SHUTDOWN.

Below are the details of virtual disks from the VM:

-rw------- 1 root root  38654705664 Jun 26 16:02 Disk_sda-s001_full-flat.vmdk   ß- disk sda

-rw------- 1 root root          534 Jun 26 15:07 Disk_sda-s001_full.vmdk

-rw-r--r-- 1 root root   2809724928 Jun 20 17:16 Disk_sda-s001.vmdk

-rw-r--r-- 1 root root   2809724928 Jul 15  2010 Disk_sda-s001.vmdk.orig

-rw------- 1 root root          388 Jun 20 16:00 Disk_sda.vmdk

-rw------- 1 root root  38654705664 Jun 21 14:50 Disk_sdb-s001_full-flat.vmdk ß- disk sdb

-rw------- 1 root root          512 Jun 21 14:50 Disk_sdb-s001_full.vmdk

-rw-r--r-- 1 root root    228982784 Jun 20 17:30 Disk_sdb-s001.vmdk

-rw-r--r-- 1 root root    228982784 Jul 15  2010 Disk_sdb-s001.vmdk.orig

-rw------- 1 root root          388 Jun 20 16:00 Disk_sdb.vmdk

-rw------- 1 root root  38654705664 Jun 26 16:02 Disk_sdc-s001_full-flat.vmdkß- disk sdc

-rw------- 1 root root          534 Jun 26 15:07 Disk_sdc-s001_full.vmdk

-rw-r--r-- 1 root root   4056678400 Jun 20 17:26 Disk_sdc-s001.vmdk

-rw-r--r-- 1 root root   4056678400 Jul 15  2010 Disk_sdc-s001.vmdk.orig

-rw------- 1 root root          388 Jun 20 16:00 Disk_sdc.vmdk

-rw------- 1 root root  38654705664 Jun 26 16:02 Disk_sdd-s001_full-flat.vmdkß- disk sdd

-rw------- 1 root root          534 Jun 26 15:07 Disk_sdd-s001_full.vmdk

-rw-r--r-- 1 root root   1439760384 Jun 20 17:32 Disk_sdd-s001.vmdk

-rw-r--r-- 1 root root   1439760384 Jul 15  2010 Disk_sdd-s001.vmdk.orig

-rw------- 1 root root          388 Jun 20 16:01 Disk_sdd.vmdk

-rw------- 1 root root   1610612736 Jun 26 15:07 sles10-d22e21ae.vswp

-rw------- 1 root root         8684 Jun 26 15:07 sles10.nvram

-rw-r--r-- 1 root root            0 Jun 21 14:40 sles10.vmsd

-rw-r--r-- 1 root root         3756 Jun 26 15:07 sles10.vmx

-rwxr-xr-x 1 root root         2902 Jun 20 15:43 sles10.vmx.20120620_154308

-rw-r--r-- 1 root root         2587 Jun 21 14:41 sles10.vmx.20120621_144100

-rw-r--r-- 1 root root         2587 Jun 21 14:41 sles10.vmx.20120621_144155

-rw-r--r-- 1 root root          261 Jun 26 15:06 sles10.vmxf

-rw-r--r-- 1 root root         3676 Jun 21 16:30 sles10.vmx.noTeraPDisk

-rw-r--r-- 1 root root         3628 Jun 21 16:16 sles10.vmx.ok

-rwxr-xr-x 1 root root         3222 Jun 20 17:53 sles10.vmx.origdisks

-rw------- 1 root root 107374182400 Jun 21 17:10 Teradata PDisk-flat.vmdk   ß- disk sde

-rw------- 1 root root          481 Jun 26 15:04 Teradata PDisk.vmdk

-rw-r--r-- 1 root root         2612 Jun 20 16:05 Xsles10.vmx.clean

From vsuteradev02 itself:

vsuteradev02:/home/ieddf01 # fdisk -l

Disk /dev/sda: 38.6 GB, 38654705664 bytes

255 heads, 63 sectors/track, 4699 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System

/dev/sda1   *           1          13      104391   83  Linux

/dev/sda2              14        4699    37640295   83  Linux

Disk /dev/sdb: 38.6 GB, 38654705664 bytes

255 heads, 63 sectors/track, 4699 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System

/dev/sdb1               1        1074     8626873+  82  Linux swap / Solaris

/dev/sdb2            1075        4699    29117812+  83  Linux

Disk /dev/sdc: 38.6 GB, 38654705664 bytes

255 heads, 63 sectors/track, 4699 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System

/dev/sdc1               1        4699    37744686   83  Linux

Disk /dev/sdd: 38.6 GB, 38654705664 bytes

255 heads, 63 sectors/track, 4699 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System

/dev/sdd1               1        4699    37744686   83  Linux

Disk /dev/sde: 107.3 GB, 107374182400 bytes

255 heads, 63 sectors/track, 13054 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sde doesn't contain a valid partition table

vsuteradev02:/home/ieddf01 # df -k

Filesystem           1K-blocks      Used Available Use% Mounted on

/dev/sda2             37051428   2051724  33494096   6% /

udev                    739200       116    739084   1% /dev

/dev/sda1               101086     30220     65647  32% /boot

/dev/sdc1             37152364   3361216  32281364  10% /usr

/dev/sdd1             37152364    901224  34741356   3% /var

I don’t know how the database app knows what disk to use for its data disk (/dev/sde in our case) nor whether there is other configuration steps required.

Thanks,

Murali

2 REPLIES
Junior Supporter

Re: Database Crashes after few seconds - Teradata 13 on SLES VM image

Hi Murali:

It seems that /var/log/messages is a good place to start looking...

HTH.

Cheers.

Carlos.

Enthusiast

Re: Database Crashes after few seconds - Teradata 13 on SLES VM image

Thank you Carlos.

I see below in the /var/log/messages file:

Jun 28 05:25:10 vsuteradev02 recond[9477]: INFO: TdatTools: 29001 #Current Working Directory set: /var/opt/teradata/tddump

Jun 28 05:25:10 vsuteradev02 recond[9477]: INFO: TdatTools: 29001 #TPA START: "recond -S", NODE UPTIME: 0 Days, 15 Hours, 47 Minutes, 2 Seconds

Jun 28 05:25:10 vsuteradev02 recond[9477]: INFO: TdatTools: 29001 #A910_Start_PDEMAIN: PdeMain started

Jun 28 05:25:10 vsuteradev02 recond[9477]: INFO: TdatTools: 29001 #master(localhost, 33) expected 1 node replies, and received 1 (elapse time: 00.090)

Jun 28 05:25:10 vsuteradev02 kernel: ablx: module not supported by Novell, setting U taint flag.

Jun 28 05:25:10 vsuteradev02 kernel: lxab_module_init: /var/lib/dkms/pdedrvgpl/13.00.00.19/build/ablx/lxab_mod.c 122

Jun 28 05:25:10 vsuteradev02 kernel: pdesys: module not supported by Novell, setting U taint flag.

Jun 28 05:25:10 vsuteradev02 kernel: init_module

Jun 28 05:25:10 vsuteradev02 kernel: PDE_MAJOR = 252

Jun 28 05:25:10 vsuteradev02 Teradata[9569]: SCH_MINOR=61, TRUSTED=42

Jun 28 05:25:10 vsuteradev02 kernel: proftime: module not supported by Novell, setting U taint flag.

Jun 28 05:25:10 vsuteradev02 kernel: tvsaext: module not supported by Novell, setting U taint flag.

Jun 28 05:25:10 vsuteradev02 kernel: tvsaext:   tvsa_init May  4 2010 at 15:20:29

Jun 28 05:25:10 vsuteradev02 kernel: tvsaext:   tvsa_init_module(1312) major 251

Jun 28 05:25:11 vsuteradev02 Teradata[9503]: INFO: Teradata: 13018 #Event number 33-13018-00 (severity 0, category 11) 1 node online.

Jun 28 05:25:14 vsuteradev02 PDE[9661]: exception info for program name: tvsa_agent

Jun 28 05:25:14 vsuteradev02 PDE[9661]:   signal: 6 SIGABRT

Jun 28 05:25:14 vsuteradev02 PDE[9661]:   code:   -6

Jun 28 05:25:14 vsuteradev02 PDE[9661]:   addr:   00000000000025bd

Jun 28 05:25:14 vsuteradev02 PDE[9661]:   registers:

Jun 28 05:25:14 vsuteradev02 PDE[9661]:     rip 00002aaaab8f5b95  eflags 00000206

Jun 28 05:25:14 vsuteradev02 PDE[9661]:     rsp 00007fffffffc578  rbp 00002aaaac275240

Jun 28 05:25:14 vsuteradev02 PDE[9661]:     rax 0000000000000000  rbx 00007fffffffc620

Jun 28 05:25:14 vsuteradev02 PDE[9661]:     rcx ffffffffffffffff  rdx 0000000000000006

Jun 28 05:25:14 vsuteradev02 PDE[9661]:     rdi 00000000000025bd  rsi 00000000000025bd

Jun 28 05:25:14 vsuteradev02 PDE[9661]:     r8  0000000000000009  r9  00007fffffffc5b0

Jun 28 05:25:14 vsuteradev02 PDE[9661]:     r10 0000000000000008  r11 0000000000000206

Jun 28 05:25:14 vsuteradev02 PDE[9661]:     r12 0000000000000027  r13 00007fffffffc8a0

Jun 28 05:25:14 vsuteradev02 PDE[9661]:     r14 00007fffffffc740  r15 00002aaaab9d0ef8

Jun 28 05:25:14 vsuteradev02 Teradata[9503]: INFO: Teradata: 13895 #PDE: TPA restart initiated by this node, 001-01, for event 10416.

Jun 28 05:25:14 vsuteradev02 Teradata[9503]: INFO: Teradata: 13895 #PDE: TPA restart requested by node 001-01 for event 10416.

Jun 28 05:25:14 vsuteradev02 Teradata[9661]: DEGRADED: Teradata: 10416 #Event number 33-10416-00 (severity 50, category 10), occurred on Thu Jun 28 05:25:14 2012, at 001-01 (Vproc 10237, partition 32, task 9661) in system s10-1300 in Module tvsa_agent, version PDE:13.00.00.19,TDBMS:13.00.00.19,PDEGPL:13.00.00.19,TGTW:13.00.00.00,TDGSS:13.00.00.00

Jun 28 05:25:14 vsuteradev02 Teradata[9661]:  Task aborted abnormally.

Jun 28 05:25:14 vsuteradev02 Teradata[9661]:   si_code:0xfffffffa  si_errno:0x0  si_addr:00000000000025bd

Jun 28 05:25:14 vsuteradev02 Teradata[9661]: rip: 0x00002AAAAB8F5B95 - rax: 0x0000000000000000 - rcx: 0xFFFFFFFFFFFFFFFF

.

.

.

.

From Teradata documentation I can see below and it does not make any sense to me.

033-10416-00 TSKQNL lock not valid.

Explanation: The lock requested by the unlock service

call does not have an owner. This typically indicates

the lock has been unlocked already.

Generated By: PDE task management services.

For Whom: System Support Representative.

Notes: Remedy: Contact the Global Support Center.

Thanks,

Murali