Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Fri, 25 Jan 2008 @ 13:08:48 GMT


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


Subj:   Re: Known issues with changing Teradata System
 
From:   Sanchez, Idrike

I have changed each of the accounts listed below over a year ago every 90 days. No impact to any Teradata tools to my knowledge.

The biggest impact was SYSTEMFE since the CSR needs to have it to do his\her work. The CRASHDUMPS user is logged in when a crash occurs, but it seems to not care what the password is; it logs in anyway. This ID is used for the system health check also without caring for the password.

You have ALL\DEFAULT\PUBLIC as "N"; but I think they are more like "NA - Pseudo User". I don't think you can change these passwords

You have SYS_CALENDAR as "N"; but I have changed this one since it is a USER.

I think you should include the databases SYSLIB and SYSUDTLIB in your list (We are on 6.2.2). However, it is a DATABASE so no password to change.

The only problem we had was when the TDWM user was changed. Early version of 6.2 caused a memory leak that restarted the database (DR113128). This was fixed. However, to my knowledge once this user is changed you still have to activate your TDWM rules again if not the TDWMlogging will stop working. I'm not sure when this will be fixed.


Kiki Sanchez
Data Warehouse Group
Technology Division
Continental Airlines



     
  <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: 23 Jun 2019