Archives of the TeradataForum

Message Posted: Sat, 03 Apr 2010 @ 20:45:07 GMT

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

<-- Anonymously Posted: Tuesday, March 30, 2010 10:37 -->

We are moving our production system this weekend. Normally we DISABLE LOGONS / ENABLE LOGONS from CNSTERM 6 before and after system shutdown.

This weekend we will have an 8 hour window after we DISABLE LOGONS where we will be backing up the system. I want to individually grant logons to my backup job IDs.

The TD Knowledge Base & 12.0 Documentation shows the following sql to be run from BTEQ as an option to DISABLE LOGONS:

     REVOKE LOGON ON ALL AS DEFAULT;
     GRANT LOGON ON ALL TO backupuser;

The sql executes successfully, but logons are still enabled (no changes take place).

I ve tried running the REVOKE LOGON ON ALL AS DEFAULT sql only in BTEQ and logons are still enabled (output below).

I ve tried DISABLE LOGONS from CNSTERM 6 (this works) then GRANT LOGON ON ALL TO backupuser from BTEQ (this does not work).

Our 12.0 release and version are shown below. Am I missing something or do I need to follow up with the GSC?

     BTEQ 12.00.00.02 Tue Mar 30 10:24:13 2010
     +---------+---------+---------+---------+---------+----
     .logon tstedwdb/dbc,
     *** Logon successfully completed.
     *** Teradata Database Release is 12.00.02.02
     *** Teradata Database Version is 12.00.02.02
     *** Transaction Semantics are BTET.
     *** Character Set Name is 'ASCII'.
     *** Total elapsed time was 3 seconds.
     +---------+---------+---------+---------+---------+----
     revoke LOGON ON ALL AS DEFAULT;
     *** Logon has been revoked.
     *** Total elapsed time was 1 second.
     +---------+---------+---------+---------+---------+----
     .logoff;
     *** You are now logged off from the DBC.
     +---------+---------+---------+---------+---------+----
     .quit;

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