How to troubleshoot ETL failures (NETIQKB72769)

  • 7772769
  • 20-Jan-2011
  • 20-Jan-2011

Environment

NetIQ Analysis Center 2.x

Situation

How to troubleshoot ETL failures

Resolution

To troubleshoot ETL in Analysis Center 2.6 or earlier:

1.      Open SQL Enterprise Manager.
2.      Go to Management Folder | SQL Server Agent | Jobs.
3.      Right-click the failing ETL package job and select Properties.
4.      Click the Steps tab.
5.      Double-click the first step.
6.      Highlight and copy the entire Command contents.
7.      Open a command prompt.
8.      Paste the command and hit Enter.  (This process manually runs the command and will show any errors that are encountered.)
         To pipe the results out to a text file, at the end of the command enter "| c:\results.txt" and it will create that file with results.
9.      Repeat Steps 5 - 8 for the next step in the ETL package job until an error is generated.  From there, you should have a better idea of what the problem or error is.
10.  If no error is generated after executing all steps in the ETL package, then you have basically re-initialized all steps.  Please right click the ETL Package Job in SQL Enterprise Manager and select Start Job.  Let the job run and see if it gives an error again or not.

To troubleshoot ETL in Analysis Center 2.7 or later:

  1.  In SQL Server Management Studio, expand the server > SQL Server Agent > Jobs
  2.  Right-click on the failing ETL job and select Disable
    (If you are having consistent failures in the ETL, you should always disable the job until the issue is resolved)
  3.  Right-click on the failing ETL job and select Properties
  4.  Click Steps
  5.  Click on the failing step and then click Edit
  6.  Select the contents in the Command window and copy it
  7.  From a CMD prompt, paste the command and hit Enter 
     To pipe the results out to a text file, at the end of the command enter "| c:\results.txt" and it will create that file with results.
  8.  Send the results in to Tech Support

Additional Information

Formerly known as NETIQKB72769

Feedback service temporarily unavailable. For content questions or problems, please contact Support.