Archives of the TeradataForum

Message Posted: Fri, 06 May 2005 @ 20:59:02 GMT

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

According to the Tpump documention (copied below), you can use the -m option to keep the generated macros in the database. Has anyone done this? How does it work?

In general it make sense, I am just having a hard time understanding how to use it. You run tpump once with the -m option. How do you run it again and use the predefined macros? The documention says specifically, 'In order to use the SAME script after the -m parameter is used in the previous run, the EXEC MACRO command must be added to the script." Where does this EXEC MACRO command get added? To me, "Same script' means that I don't have to replace all my DML sql with an execute macro statement. If you do have to replace all your DML with macro commands, then what is the value of this option?

Anyone have any examples of this in use?

=== Excerpt from Teradata Parallel Data Pump Reference, for tpump -m ===

Invocation option to tell TPump to keep macros that were created during the job run. These macros can be used as predefined macros for the same job.

In order to use the same script after the -m parameter is used in the previous run, the EXEC MACRO command must be added to the script.

To avoid duplicate macro names, a random number from 1 to 99 is used in each macro name when the NAME command is not used. The format in which the macro is created is:

     MYYYYMMDD_HHMMSS_LLLLL_DDD_SSS

where

- LLLLL is the low order 5 digit of the logon sequence returned by the dbs from the .LOGON command.

- DDD is the .DML sequence (ordinal) number. This value is not reset to one for successive loads (.BEGIN LOAD) in a single job, but continues to be incremented.

- SSS is the SQL statement sequence (ordinal) number within the .DML group.

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