In some cases, simply evaluating the job logs and error tables does not provide enough information to adequately define the required corrective action. In other cases, the corrective action is in place, but the job still doesn’t run correctly. In these cases, Teradata PT provides two additional levels of debugging:
For example, on Solaris running on a SPARC system, use the following commands to get the values:
/usr/sbin/sysdef -i | grep SHMMAX
/usr/sbin/sysdef -i | grep SHMSEG
/usr/sbin/sysdef -i | grep SEMMNI
/usr/sbin/sysdef -i | grep SEMMNS
tbuild -t -f <filename>
TraceLevel = ‘all’
a ps -ef | grep tbuild (if Coordinator, or Executor).
b Find the processid for the problem component.
c truss -f -o /tmp/trussout -p <processid>.