Archives of the TeradataForum

Message Posted: Thu, 09 Oct 2003 @ 19:10:51 GMT

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

Using the disable logons from dbw means that you don't let any thing log into the database. That would also include the process that you are wishing to run. One way that you might be able to accomplish what you want is by the following.

Assumptions:

process is running from a lan host (unix, nt server)

multiple lan connects to your system with the same host id (at least 2 connections if a 2-node system - typical setup in small shops i think)

using dns to identify the teradata server (dbccop1.company.com) - not necessary but makes life easier

If you have multiple lan connections, you can split those up and create two host groups. This would require some changes to some configuration files on Teradata and a small reconfig to make the changes to Teradata. One host group would be the production host group that everyone uses. Everyone has the ability to access the system through this host group. The second host group would be the backdoor host group for when you need to access the system but keep your users off the system (stand alone backups, system issues, etc.) Once the host groups are setup you can run a couple of commands that will prevent users from being able to logon to that host group so that only the process/users you want to be able to access can access it. With this setup you can use gateway global to diable logons to any host group except the one you need to stay alive. This same setup can be used multiple ways to seperate out application groups and other things. You should probably get with your local support team and discuss how hard it would be to make this happen, or if your setup would even allow you to implement this.

There might be holes in my thinking, since it has been almost 2 years since I had to do anything like this.

Bill Grenwelge
Data Warehouse
Union Planters Bank

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