Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Mon, 18 Nov 2003 @ 04:26:45 GMT


     
  <Prev Next>   <<First <Prev
Next>
Last>>
 


Subj:   Re: Fully qualified domain names and Teradata utilities
 
From:   Dennis Calkins

On Mon, 17 Nov 2003 19:19:07 -0500, Jim Downey wrote:

  I could not get the entry to work so I changed testdbccop1 to be dbccop1and received this message:  


  0003 .Logon dbccop1\Downeyj,;
**** 19:17:01 UTY1007 RDBMS error: 3004, User identification is not authorized.
 



Hi,

You never specify the 'cop1' part of the alias name to the utilities. the utilites will automatically append 'cop1'.

In your example above, the utility would have looked for

dbccop1cop1


which it didn't find.

Also I keep saying COP1. However you can can have Cop2 and Cop3 and Cop4 ... One for each node your system if you want to allow the application to randomly choose which TPA node on your system to connect through. The numbers must be sequential and represent differnt nodes of the the same Teradata system.

if you have a 4 node system you can define in your hosts file

abc.def.ghi.jkl node1 boxcop1 node1cop1
abc.def.ghi.jkm node2 boxcop2 node2cop1
abc.def.ghi.jkn node3 boxcop3 node3cop1
abc.def.ghi.jko node4 boxcop4 node4cop1


If you specify

.logon box/....


The utilities will randomly pick 1 of the 4 COPS to log you on through.

if you specify

.logon node3/....


the utility will always send your request to the node3 Ip address.

One other note.

boxname


must be 8 or fewer characters. a name like

systemtestcop1


will fail because when you specify the follwoing to the utilities

.logon systemtest/....


will truncate the name to 8 characters add the cop1 and search for

systemtecop1


which again it probably won't find on your network..



     
  <Prev Next>   <<First <Prev
Next>
Last>>
 
 
 
 
 
 
 
 
 
  
  Top Home Privacy Feedback  
 
 
Copyright for the TeradataForum (TDATA-L), Manta BlueSky    
Copyright 2016 - All Rights Reserved    
Last Modified: 15 Jun 2023