Hi Steve,
#1 check if TD is running: "pdestate -a" in a terminal window should return
PDE state is RUN/STARTED.
DBS state is 5: Logons are enabled - The system is quiescent
#2 try to connect from within the VMWare using BTEQ and ".logon 127.0.0.1/dbc"
If this works you have a problem connecting to the VMWare.
What network type do you use: NAT/host/bridged?
Dieter
Hi Steve.
Difficult to say without knowing the errors you get, but first place to look at is the network configuration in the VM.
If you want others machines accesing the VM, you should have configured it 'bridged' (it can be done NAT too...). Then the network settings: better fixed IP, no dhcp. Then check if the firewalls are blocking the communications.
I'm assuming your problems are communication ones, not starting the DB (if this is the case, follow Dieter's advices).
I got it done:
http://carlosal.wordpress.com/2011/03/19/teradata-13-10-sobre-suse-linux-enterprise-server-en-vmware/
http://carlosal.wordpress.com/2011/03/30/teradata-13-10-sobre-suse-linux-enterprise-server-en-vmware-y-2/
HTH.
Cheers.
Carlos.
@Dieter - I have done all those things with no success in connecting from TBIO, TD Studio Express or even the old TD Administrator. I can open VMWare player and see the DB. I can see that it's started through both means you suggest. I have tried both NAT and Bridged in the VMWare player.
Oddly.....at one point it was working for about a day or two. Then POOF...NOTHING.
@Carlos - I'm not sure how to check the network settings you suggest. Can you describe in more detail? I don't have those options in my VMWare player. I do have a Trend Micro Officescan firewall running. Should that come down do you suppose?
Thanks to you both for your help. I appreciate it. I will be very happy to get this silly thing working again.
Steve
Steve:
If you configured the VM network as NAT (VMware Player-> Virtual Machine-> Virtual Machine Settings-> Network adapter ) the other machines(PC's) in your network won't have access to it (unless you use the port forwarding/redirection feature). You should configure it BRIDGED.
Then you should configure the network adapter inside the VM: logging in and giving a fixed IP to the virtual network adapter that fits with your LAN settings (IP range, subnet mask...). You should also disable the firewall (if enabled).
Once you have done this, you should be able to ping other machines in the LAN and vice-versa.
From here is all downhill...
HTH.
Cheers.
Carlos.
Carlos, I don't know what you mean by configuring the network adapter inside the VM. I don't have that option. Here is what I see when I go to the VM settings inside the VM when the Linux connection is open.
Device Status: Connected or Connect at power on (both checked)
Network Connection: Bridged (checked) with a sub-selection (not checked) to replicate physical network connection state
NAT: Used to share the host's IP Address (not checked)
Host-only: A private network shared with the host (not checked)
then two buttons for LAN Segments and Advanced. In the advanced button, it only speaks to incoming and outgoing transfer information as well as a MAC address.
Steve
Steve:
That's OK on the VMware player side.
Om the VM side: logon to the SuSE linux (as root) and go to computer->control center->Network card and configure there the network settings: IP static, IP address, network mask, etc...
HTH.
Cheers.
Carlos.
I also wanted this information now i have got thanks for the sharing , i want to more about the linux.
Actually I've ended up having a similar problem. I think it's less of a Teradata DB thing within the VMware image, and more of a SLES apache2 issue. I'm not a networking specialist but I've done all the checks suggested by Dieter. The DB is working, pdestate -a returns happily. a bteq statement within the command prompt logs me in and works fine. however when I jump onto my native windows 7 host computer, I can't ping the system (setup on 192.168.47.128).
Carlos, it was and has been working fine using the basic installation of NAT without any changes. But it has been flaking and fallen off the cliff every so often.
--------------------------------------------------------------------------------- guest os
TDExpress14.0_Sles10:~ # ping 192.168.47.128
PING 192.168.47.128 (192.168.47.128) 56(84) bytes of data.
64 bytes from 192.168.47.128: icmp_seq=1 ttl=64 time=0.033 ms
64 bytes from 192.168.47.128: icmp_seq=2 ttl=64 time=0.036 ms
64 bytes from 192.168.47.128: icmp_seq=3 ttl=64 time=0.034 ms
--- 192.168.47.128 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 0.033/0.034/0.036/0.005 ms
TDExpress14.0_Sles10:~ #
------------------------------------------------------------------------------------- host os
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\RB186032>ping 192.168.47.128
Pinging 192.168.47.128 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.47.128:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\RB186032>ping 192.168.47.128
Pinging 192.168.47.128 with 32 bytes of data:
Request timed out.
Request timed out.
Ping statistics for 192.168.47.128:
Packets: Sent = 2, Received = 0, Lost = 2 (100% loss),
Control-C
^C
C:\Users\RB186032>
Oh funny. Okay, it seems the teradata employee windows VPN somehow conflicted with the NAT networking. (a problem that the externals might have if they are porting into their respective workplaces).
Once this was turned off, I could ping, the guest from the host - happy days!
Addendum for good measure I did a /etc/init.d/tpa stop, /etc/init.d/tpa start for good measure, because the PDE fell over again (or did I do tpareset -f restarting? can't remember) either way I had to because I checked pdestatus -a and I discovered it had landed on it's face again.
I am encountering a problem getting TD13.10 instance setup using either VMWare Player or VMWare Server. I cannot ping the instance. TD starts up fine and within the SUSE image all is fine access DB. But I can not ping the instance from my laptop. It appears looking at a working VMWare server 2.2 TD instance that the network adaptors VMNet1 and VMNet8 are not getting completely setup. They appear in all of my Virtural Network Editor windows but -> Host Virtual Adaptors. I cannot add them either, I get an error message that an error is occurring while updating the virtual network settings, Error Code 183. Only the Bridged adaptor is available for SLSE image.
I am assuming that the VMWare player install has the same issue as I could not ping it either when I first set it up. This is latest VMWare player and VMWare Server 2.2. Another person has the VMWare server version 2.2 working on his laptop.
Good Morning All,
I'm hoping that ANYONE can help me figure this out. I have been unable - for the last few days - to connect ANY application to the TDExpress DB's in either version 13.10 or 14.00 on VMWare. As an aside, it did work once....so I know it's possible.
I get request time out errors, 10060 and 10065 WSA E errors, database crashed errors, and just about every other error you can think of.
I use Windows 7. It's 64 bit. I use the VMWare player. I tried both the 13.10 drivers and the 14.00 drivers. I've researched all the errors on Google and in the forum here. I've tried all the suggestions - with moderate success on the DB, but zero on connectivity.
The bottom line is that I can't do my job if I can't connect any application to the DB, and I need some help. No matter what hostname from the SUSE Linux (hostname) command I use, no matter what IP address I use, no matter what I put in the hosts file on both Linux and Windows, the connection fails. I've tried being logged into TD's network, logged out of TD's network, and nothing is working.
If anyone has been able to successfully connect the Teradata Administrator, Studio Express, TBIO to either DB....or even if you are able to ping the DB....please let me know your configuration information and how you came up with it.
Thanks,
Steve Gross