Home Page for the TeradataForum

Archives of the TeradataForum

Message Posted: Mon, 31 Oct 2005 @ 21:51:42 GMT

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

Subj:   Re: Multiload -- Logon Failed error
From:   Dieter Noeth

Anomy.Anom wrote:

  I run few multiload jobs on our production server. And all of my mload jobs succeeds everyday with no error or whatsoever, but the LogonOff table has recorded scores of "logon failed" (error??) messages. All instances of mload jobs have acquired all the requested sessions.  

  This is a big pain in our shop as any entry in the logonoff table other than a regular logon / logoff is viewed as a hack attempt by auditors and must be explained away by the person who (or whose id) caused the entries.  

  Has anyone experienced this situation before? Does anyone know the cause and a remedy to this?  

If you don't specify the number of session in your script, then MLoad uses a default of 1 session per AMP and tries to logon sessions in blocks of 16.

E.g. if you got 40 AMP, then there will be 3*16 = 40 "logon" and 8 "logon failed".

The solution is to specify the correct number of session, best place is probably the configuration file (mloadcfg.dat)

Btw, it's the same for FastLoad...


  <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: 15 Jun 2023