I have an EC2 instance of the Teradata Developer single-node DB, which was set up with the Teradata-recommended Security Group (ports 22 and 1025 open). I can ssh to it but PDE is down:
> sudo pdestate -a
PDE state: DOWN/HARDSTOP
I tried stopping/restarting TPA, and although It says the Initiator service was started, PDE state is still down.
I tried rebooting and starting/stopping the EC2 intance, PDE is still down.
Nov 4 00:43:15 ip-172-31-13-100 reconsh: DEGRADED: TdatTools: 29003 # running version dependency failures (ON NODE: localhost, *** TDBMS running (15.10.00.00) depends on TGTW running (15.10.02.01) being MAINT_MINIMALLY_SAME (NOT MET); )
Nov 4 00:43:15 ip-172-31-13-100 recond: DEGRADED: TdatTools: 29003 #critical reconsh.exe "startup" rule set failure. Posting PdeMain to stop.
Nov 4 00:43:15 ip-172-31-13-100 recond: DEGRADED: TdatTools: 29003 #A920_Terminate: PdeMain NOT started
I haven't seen any similar errors on Google. Can anyone tell me what is going on?
Please check the Control (ctl) utility to find what TDBMS version is set to.
:~ # ctl
> screen version
I think the Running DBS / Desired DBS would be 15.10.00.00
Please set it to 15.10.02.XX release and write to save it. Then perform a /etc/init.d/tpa start to bring database up and running.
> 1=? /* This will list all the TDBMS releases that are installed */
> 1=15.10.02.XX /* Set TDBMS version to 15.10.02.XX
:~ # /etc/init.d/tpa start
:~# pdestate -a
I believe datbaase should come up fine.
If this is a new instance that has never been started you may need to run tdc-init or tdc-start to do the initial configuration and startup of the database. This will wipe out everything in the database and start up the database. If the database is not new and has been working in the past then please do not run tdc-init or tdc-start.
Page 92 of the Teradata AWS Getting Started guide:
If you can SSH to your Teradata Database instance, but you cannot log on with BTEQ or Teradata Studio,
try either of the following options:
• Change the dbc password by running tdc-start to enable port 1025, which is used by ODBC and CLI
• Check your inbound ports to make sure port 1025 is opened for your
Thanks, teh problem was that I was using the default security group isnteadf of the "Teradata" securiy group, which opens port 1025.
Thanks, the problem was that I was using the default security group isntead of the "Teradata" securiy group, which opens port 1025.
Looks like there may be other issues with provisioning, requiring the end-user to run "tdc-init" anyways.
After a new provision from the marketplace, I logged into SSH and ran "pdestate -a", which returned "Down/Hardstop". I tried running "/etc/init.d/tpa start" which failed with these errors in /var/log/messages:
Jan 12 10:04:06 ip-10-55-21-196 recond: INFO: TdatTools: 29001 #TPA START: "recond -S", NODE UPTIME: 0 Days, 16 Hours, 12 Minutes, 33 Seconds Jan 12 10:04:06 ip-10-55-21-196 recond: INFO: TdatTools: 29001 #pnet_lockset() failed: -2 Jan 12 10:04:06 ip-10-55-21-196 recond: file: pnetfileunx.c Jan 12 10:04:06 ip-10-55-21-196 recond: line 644 Jan 12 10:04:09 ip-10-55-21-196 recond: CRITICAL: TdatTools: 29003 #pnet_lockset() fail: -2(recond: unable to create lock file), getLastErrorMessage(): Permission denied
I looked at "ctl" "screen version" and there was no version set for PDE, DBS, TGTW, TCHN, TDGSS, PDEGPL.
I went ahead and set the versions to 15.10.02.06 (or latest) for the DBS component, then issued a tpa start again.
I got further errors with a missing Vconfig GDO, so resorted to the "tdc-init" as suggested above.
Hope this helps other users who know what their way around a Teradata system.