Home Page for the TeradataForum

Archives of the TeradataForum

Message Posted: Tue, 29 Jan 2008 @ 12:40:00 GMT

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

Subj:   Re: MultiLoad - an unexplainable 'configuration
From:   Victor Sokovin

  Well - I am beyond that phase of playing around with parameters setting. I've already tried various settings of SESSION and others in the script body.  


What is your experience level with Teradata utilities? If you are just beginning with them there are lots of things to check!

For example:

     **** 18:15:39 UTY6210 Logtable 'MSTEST.MYTABLE' indicates
          that a restart is in progress.

This indicates that you restarted the previous job. Was it intentional? If not, then apply the following procedure before you test the next version of the script:

1. Release ML lock on the target table (read the manual on the details).

2. Identify and drop all temporary tables ML uses: log, 2 error table, work table etc.

3. Make modifications in the ML script, one at a time.

4. Start a new ML job and check that the ML log file does not mention any restart.

Debugging the script which is not working at all is easier when you start it in a clean situation without any previous history.

If Step 1 does not work it probably means that the ML lock is stale. In this case try to drop the target table and rebuild it again or you may need a help from DBA.

I also recommend to implement an example or two from the manual, just to see that ML loads are possible at all, and only then continue experiments with your own scripts.

Hope this helps.


  <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