Re: Strange SAS teradata message #3
The ideal way to deliver data from a server is usually to have the server
name recorded on the network Domain Name Server so that a request against
MYTERROR is translated into an ip address from the most authoritative
source. For a variety of reasons, including server security, procedural
limitations and delays in updating the DNS, the work-around is sometimes
made that the server name is translated into an ip address in the HOSTS file
on the client PC.
Your alternatives are to have the server name recorded in the DNS (which may
not be possible), replace the server name in your library state...Re: Strange SAS teradata message #2
You're missing the appropriate entry from your "hosts" file. Assuming
WinXP, this file will be located at:
If you open that file in notepad on your two machines, you'll see an entry
on the laptop that corresponds to the SERVER you specified in your LIBNAME;
you need to paste that line into the hosts file on the workstation and save
it. You need admin rights to edit that file, so you'll probably have to
On Tue, 10 Jul 2007 08:02:56 -0700, ssegall@GMAIL.COM wrote:
>Not really sure if that many people in here ...Re: Strange SAS teradata message #4
Maybe I had, but that wasn't the solution. You needed a similar line in
your hosts file that referenced the server and its ip address.
However, subsequent postings suggest you had a variation on the problem and
that it is resolved now.
From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU]On Behalf Of
Sent: Friday, 13 July 2007 3:19 AM
Subject: Re: Strange SAS teradata message
On Jul 12, 7:44 am, d...@dkvj.biz (David Johnson) wrote:
> The ideal way to deliver data from a server is usually ...Strange SAS teradata message
Not really sure if that many people in here define Libraries in
Teradata using SAS, but I'd figure I'd give it a shot. May be an
error that shows up using other more popular databases.
I am using the following script that I have always used to define the
libname XXXXX teradata server=XXXXXXX user=XXXXXX password=XXXXXXXX
When I entered this I get the following error.
ERROR: Teradata connection: MTDP: EM_NOHOST(224): name not in HOSTS
file or names database. .
ERROR: Error in the LIBNAME statement.
I have no clue what this means.
I have run...Re: Error message from SAS. Re: Transpose columns to rows in SAS?
That is a V8 limitation not a V9 limitation.
1 Data One ;
2 Array aaa (1000000) ;
3 Retain AAA: 0 ;
4 Run ;
NOTE: The data set WORK.ONE has 1 observations and 1000000 variables.
NOTE: DATA statement used (Total process time):
real time 2:52.48
cpu time 2:37.24
To sensible men, every day is a day of reckoning. ~John W. Gardner
The important thing is this: To be able at any moment to sacrifice that
which we are for what we could become. ~Charles DuBois
Don't get your knickers in a knot. Nothing is solved and i...RE : RE : sas to teradata insertion error
Hum, yes yes yes, I remember this error....when I got the v9 (again) :-))
I'm sure it's a compatibility problem between the SAS9 and the teradata
client which worked fine with the v8 but not very well with v9 (as a old
post in relation to Oracle, the RDBMS client have to change when you upgrade
I used insert values statement and I changed to :
infile datalines dsd dlm='|';
input SCORE_DESC_1 $3. +1 LIB_DESC_1 : $50. ;
connect to teradata (user ="&__user3" password="&__pass3"
schema="...Re: What does the SAS message mean?
In my experience, this means t\tou have more than one SAS session running
at the same time. The first one locks the registry and the second puts out
this warning message, usually at startup time. Look at thhe very beginning
of you session log. It could also be due to some other process on your
system locking the registry, but this less likely. In most cases, you can
ignore the message although I am not familiar with SurveySelect.
On 10/17/05, Xu Libin <Libin.Xu@irs.gov> wrote:
> Dear SAS-lers,
> When I ran the following syntax:
> proc surveyme...Re: Strange SAS behavior!
Duck-Hye Yang <dyang@CHAPINHALL.ORG> wrote:
> These days I noticed one weird thing.
> Even though I specified a variable name to be analyzed (for example,
> for proc univariate), I found that the VERY FIRST variable in the
> in a data was used.
> Have any of you experienced this kind of thing ?
This would be a strange SAS behavior.
Perhaps you should write back (to the list, not to me personally)
and demonstrate some simple SAS code, with log and output, demonstrating
this behavior, so that we can see what is actually happening. Make
the SAS code as short as ...Re: strange error message
> From: Jonathan Woodring
> I get this message now when I run a program today that has
> been running bug free for months:
> ERROR: A lock is not available for
> EXPORTS.KPCUSTOMERSQL.DATA, lock held by another process
this is the result of two sessions or jobs
trying to read/write/access a dataset,
KPCUSTOMERSQL, in the same libref.
kill the first job/session
Ron Fehd the batch maven CDC Atlanta GA USA RJF2 at cdc dot gov