| # | Date | Where | Item | Comment |
|---|
| 7 | 06 Mar 2014 @ 10:49 PST | Tools | Data Mover User Pool | You should check for stale sessions on the COPY (target)side. Same ARC users being logged on to the source system will not give you the same user logged on to the dbs error" error.
... |
| 6 | 05 Mar 2014 @ 11:07 PST | Tools | Data Mover User Pool | When ARC jobs are run simultaneously with TPT jobs, then the ARC jobs can use the same user from the pool as the TPT jobs. This is OK becasue the "same user logged on to the dbs err... |
| 5 | 29 Jul 2013 @ 09:32 PDT | carrie's blog | Utility Session Management - It's Inside the Database in Teradata 13.10! (UPDATED) | Hi Carrie. Thanks for the clarification. To get a little more detail :
1. Is there a guideline on what number classifies as small number of amps and what classifies as large number of amps ? ... |
| 4 | 22 Jul 2013 @ 02:31 PDT | carrie's blog | Utility Session Management - It's Inside the Database in Teradata 13.10! (UPDATED) | Hi Carrie, Great article!!
You mention above that the default number of sessions is obtained using a formula that depends on the number of amps, Data Size etc.
From my understanding, if my ... |
| 3 | 29 Feb 2012 @ 11:25 PST | Tools | Data Mover User Pool | @TeraAbe - we have created a jira task (DM-10383 ) for the logon mechanism and account string being added to the user pool
@Vikrant - we have created a jira task (DM-10384) to set a timeout para... |
| 2 | 23 Feb 2012 @ 10:55 PST | Tools | Data Mover User Pool | Hi Vikrant
The earlier releases of DM (before 13.10.00.03) had an automatic timeout for ARC jobs waiting on the pool. I believe the timeout was 5 mins. But this timeout has been removed in the n... |
| 1 | 28 Jul 2011 @ 05:53 PDT | Tools | Introduction to Teradata Data Mover: Create your first job | If ARC is used then the table is replaced on the target system.
If TPTAPI/JDBC is used, rows from the target table are deleted and the source rows are inserted into the target table. This is done... |
|
|