Home Page for the TeradataForum
 
https:

Archives of the TeradataForum

Message Posted: Thu, 25 Sep 2008 @ 17:43:13 GMT


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


Subj:   Re: Error 3132: Access Logging step has failed
 
From:   Mistry, Jeetendra

Hi, I am not sure what would have caused this error, But I have this peice of Info which might give u some hint

- Jeetu


3132 Access Logging step has failed. The transaction was aborted.

Explanation: The user has been flagged for Access Logging and an Access Logging step has failed. The original AMP error code for the failed step is returned in the Info field of the Error or Failure parcel. The user's transaction has been aborted.

Generated By: Dispatcher.

For Whom: End User.

Remedy: Examine the Info field of the Error or Failure parcel to determine why the Access Log step failed, then decide on a course of action. If no Info field nor Failure parcel is attached to the error message (error message from Fastload or Multiload), resubmit the job.



     
  <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: 28 Jun 2020