Publishing from Extract files to DataMart tables. What is the easiest way to accomplish this? Where do I look in case of errors?

Document ID : KB000011809
Last Modified Date : 14/02/2018
Show Technical Document Details
Introduction:

Data movement is a subject that we all need to explore now and then.  What is the best way to accomplish moving data from one area to another?  We rarely need to look at log files.  But when we do, we need to know where they are quickly.

Question:

Publishing from Extract files to DataMart tables.  What is the easiest way to accomplish this?  Where do I look in case of errors?

Environment:
TDM, Subsetting, Javelin in 3.8
Answer:

What is the easiest way to get data from a Subset extract file into a DataMart table? 

May not be EXACTLY the easiest way (you have to know Javelin) but the fastest way to transfer is to save the extract as a Javelin XML from Subset, and then do a bulk copy from Javelin. I refer you to our Documentation that specifies how to accomplish this since there are options that you need to specify depending on your specific environment.

You will find "Generate Scripts to Move Data".  "You can generate scripts to move the data depending on the RDBMS you are connected to. Database Actions screen consists of various tabs where script options can be set, dependent on the type of script generation chosen." 

Next, you can look at Javelin Visual work flow elements - Database activities and skip to the Bulk Copy section where it starts with "The Bulk Copy functions automate the bulk copy of data into a database. You can use these functions to automate the copy of a Data Subset extract into its target database. Following are available functions:"  Follow the documentation to perform a bulk copy.

Your other question about knowing where the logs can be found is answered in this KB article, TEC1431183, where location of logs is cataloged at length. 

Here is an excerpt for your convenience: 

FDM logs are written to %appdata%\Grid-Tools\Fastdatamasker\logs by default – this can be overridden by setting the path in the options file, you can also set how verbose the log is in the options. 

GTSubset itself does not write to a log file, the scripts it generates produce log files when run. 
If you run GTSubset from a command line, additional messages are written to the command window. 

java -jar GTSubset.exe


Datamaker: logs are in %appdata%/Grid-Tools/DM_logs. Each Datamaker session will have its own log stamped with the a Date and a unique GUID. 

TestMatch: logs are in %appdata%/Grid-Tools/Testmatch 

TDoD service: logs located under Grid-Tools\TDoD\TDoD_Service\logs and can be configured using GTWCFHOST.exe.config (log4net). 

RemotePublish: logs located under Grid-Tools\RemotePublish\logs and can be configured using DMBatch.exe.config (log4net) 

HPALMService: logs located under Grid-Tools\GTHPALMService\logs and can be configured using GTHPALMServiceConsole.exe.config 

GroupJobProcessor: logs located under Grid-Tools\GTHPALMService\logs and can be configured using GTHPALMServiceConsole.exe.config 

GroupJobProcessor: logs located under Grid-Tools\GTGroupJobProcessor\logs and can be configured using gtgroupjobexecutor.exe.config