Archives of the TeradataForum

Message Posted: Mon, 24 Feb 2003 @ 18:42:31 GMT

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

We use ESP as a scheduler package for our Production mainframe environment, so when we run batch jobs against our Production Teradata server, be it FASTLOAD, MULTILOAD, or BTEQ stuff, the scheduler logs on to Teradata using an ID of APOLIDB. On the Teradata server, APOLIDB basically has all authority to access all application databases. The problem is that our production support area doesn't police/examine jobs that are put into production, thus if someone created a job, had it put into production and then run through the scheduler as a production job, it could basically do anything on the Teradata server. How do other shops handle production support, batch job wise? Do you have one department that only that departments production jobs can use APOLIDB? Do you have multiple application areas creating batch jobs against Teradata? How do you control areas, to prevent databases from being corrupted/ dropped etc.

Thanks,

Anthony S. Howe
Certified Teradata Professional
Teradata/DB2 Database Administrator
Highmark Blue Cross/Blue Shield

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