Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Fri, 27 Feb 2009 @ 12:46:38 GMT


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


Subj:   Re: Creating alert for DB restart
 
From:   Anomy Anom

<-- Anonymously Posted: Fri, 27 Feb 2009 10:54 -->

ref below from teradata


SD1000DC566

Short Description: software_event_log not populated on LINUX/W2K/WS03


Probable Cause:

logd and logtpad are not ported from MP-RAS to OpenPDE.


Solution:

DR 116114 is open to fix this problem. Upgrade to the release or above at which the DR will be fixed.


Configuration Data:

PDE on LINUX and PDE on Windows.


Following DRs were open to fix this problem.

DR 85889 RFC: Add logging to SW_EVENT_LOG on W2K AND LINUX (all OPNPDE) DR 102835: Sw_event_log not populated on Linux/W2K/WS03

DR 85889 is closed as a duplicate of DR 102835.

DR 102835 is fixed in OpenPDE 12.0. But, this does not enable logtpad. If the system is already running on OpenPDE 12.0 and if logtpad is not running on the PDN node, as a workaround, add the following line in the /etc/opt/teradata/tdconfig/startup.txt on LINUX on all the nodes -

          start -v0 -p0 READY logtpad

Then restart the database.

If you don't have a startup.txt file in tdconfig directory then create startup.txt file in tdconfig directory. So that the settings in tdconfig startup.txt file remains even after the PDE version changes.

Do ps -ef | grep logtpad to check if logtpad is running.

To check if sw_event_log is populating, login to the database using bteq. You can view the contents of the log by submitting the query:

          SELECT * FROM DBC.Software_Event_Log ;


     
  <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: 27 Dec 2016