Application not started because all AMPs are in NewProc or Fatal State

Connectivity
N/A

Application not started because all AMPs are in NewProc or Fatal State

Hello all,

When attempting to connect to Teradata 14.10, I am receiving the following error message:

Warning: RDBMS Crashed or Sessions reset. Recovery in Progress

After ctrl-c'ing a coupe of times, I get sent back to the BASH prompt.

While attempting to connect, I tailed the messages log in /var/log....and found the following lines..

....

Apr 12 11:59:14 prteradata Teradata[5783]: INFO: Teradata: 13815 #Event number 33-13815-00 (severity 10, category 12)

Application not started because all AMPs are in NewProc or Fatal state.

Apr 12 12:08:11 prteradata Teradata[6555]: INFO: Teradata: 15070 #PDISK 1 has incorrect device number 0 in its tag

Apr 12 12:08:11 prteradata Teradata[6555]: INFO: Teradata: 15070 #PDISK 0 has incorrect device number 1 in its tag

So, I read somewhere to run vprocgdo...and received the following results...

Vpr:  VprocID Clq Type Movable NodeID Vdisk  CUA HGID Slot Status  Err

    0:      0   0    1    Y    001-01     0   -1   -1   -1 FATAL    E

    1:      1   0    1    Y    001-01     1   -1   -1   -1 FATAL    E

    2:  16383   0    2    Y    001-01 16383   -1    1   56 ONLINE   N

    3:   8192   0    3    N    001-01  8192   -1    1   56 ONLINE   N

    4:   9215   0    4    N    001-01  9215   -1    1   56 ONLINE   N

    5:  10237   0    5    Y    001-01 10237   -1   -1   -1 ONLINE   N

    6:  10238   0    5    Y    001-01 10238   -1   -1   -1 ONLINE   N

...df -h shows....

ilesystem            Size  Used Avail Use% Mounted on

/dev/sda2              14G  6.8G  6.4G  52% /

devtmpfs              873M  132K  873M   1% /dev

tmpfs                 873M  100K  873M   1% /dev/shm

/dev/sda5             2.0G  564M  1.4G  30% /var

/dev/sda7              41G  734M   38G   2% /var/opt/teradata

lx_share              466G  142G  325G  31% /media/sf_lx_share

Can anyone on the forum point me in the right direction on how to correct these fatals?

FYI. I come from a heavy Oracle/MySQL Administration background and am now trying to learn Teradata. So, these errors are not in a prod env, however, I would like to get past

these so that I can get acquainted with the internals of Teradata.

Thanks in advance,

pruiz

Tags (1)
1 REPLY
Teradata Employee

Re: Application not started because all AMPs are in NewProc or Fatal State

Can you shed some light on your setup of Teradata? Systems, versions, etc.?