Datastage to Teradata multiload
Teradata Teradata Discussion Forums Teradata.com Discussion Forum
Visit Teradata.com
Home       Guidelines    Member List
Welcome Guest ( Login | Register )
        


This online forum is for user-to-user discussions of Teradata products, and is not an official customer support channel for Teradata. If you require direct assistance, please contact Teradata support.


Datastage to Teradata multiload Expand / Collapse
Author
Message
Posted 8/28/2006 10:26:41 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: Forum Members
Last Login: 9/5/2006 9:43:00 PM
Posts: 2, Visits: 1
When using multiload, I am having performance issues.
========================================================================
= =
= MultiLoad Initial Phase =
= =
========================================================================
**** 06:04:16 UTY0829 Options in effect for this MultiLoad import task:
. Sessions: 16 session(s).
. Minimum of 16 load session(s) requested.
. Checkpoint: 2000000 records.
. Tenacity: 4 hour limit to successfully connect load sessions.
. Errlimit: No limit in effect.
. AmpCheck: In effect for apply phase transitions.
**** 06:04:16 UTY0817 MultiLoad submitting the following request:
Select NULL from scott.LOG_GFSTWB1 where (LogType = 125) and (Seq = 1)
and (MloadSeq = 0);
**** 06:04:16 UTY0817 MultiLoad submitting the following request:
Select NULL from scott.LOG_GFSTWB1 where (LogType = 120) and (Seq =
1);
**** 06:46:41 UTY0812 MLOAD session(s) requested: 16.
**** 06:46:41 UTY0815 MLOAD session(s) connected: 16.
==========================================================================
I am not sure why it took 42 min for logtype 120. I don't know what logtype 120 means?
Can somebody please explain what is happening here from logtype 125 to the last stmt.

Thanks a lot
Ravindra


Post #5007
Posted 8/29/2006 4:36:48 AM
Supreme Being

Supreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme Being

Group: Forum Members
Last Login: 2 days ago @ 3:41:05 AM
Posts: 522, Visits: 264
Hi Ravindra,

> . Minimum of 16 load session(s) requested.

MLoad can't logon with less than 16 sessions.

> . Tenacity: 4 hour limit to successfully connect load sessions.

If there are less than 16 sessions available (or too many load jobs already running) then retry the logon after SLEEP minutes, with a default of 6.

> **** 06:04:16 UTY0817 MultiLoad submitting the following request:
> Select NULL from scott.LOG_GFSTWB1 where (LogType = 120) and (Seq =
1);

There's no error with that, it's just the last successfull request.

> **** 06:46:41 UTY0812 MLOAD session(s) requested: 16.
> **** 06:46:41 UTY0815 MLOAD session(s) connected: 16.

> I am not sure why it took 42 min

MLoad retried 7 times before there were 16 sessions available:
If you check dbc.logonoff there should be some sessions (<16) logged on and immediately logged off for that job every 6 minutes...

Dieter
Post #5011
Posted 8/30/2006 12:41:52 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: Forum Members
Last Login: 9/5/2006 9:43:00 PM
Posts: 2, Visits: 1
Dieter--Thanks for taking time to explain. Really appreciate it.
Post #5027
« Prev Topic | Next Topic »


Reading This Topic Expand / Collapse
Active Users: 0 ( 0 guests, 0 members, 0 anonymous members )
No members currently viewing this topic.


All times are GMT -5:00, Time now is 5:29am

Powered By InstantForum.NET v4.1.4 © 2008
Execution: 0.063. 7 queries. Compression Disabled.