cancel
Showing results for 
Search instead for 
Did you mean: 

in TDSHL, exported files are located in different drives.

Former Member
0 Kudos
72

In our TDSHL project, we already successfully exported the source and now we are going to do post-processing steps before import.

Please see the attached for details.

However we face a situation that is the  e: drive is only 50GB but the total size of the exported files is about 80GB. Therefore during export I had to move generated  dump file (e.g. *.001, *.002, *.003, etc.) out of drive e: to avoid full.

My question is : can we execute above TDMS steps without moving above dump files back to e: drive where there is no space to extend?

I think it should be OK because if I use ftp option for export_monitor.bat , the generated files will be constantly moved to target.

Thanks a lot!

P.S. 80GB of shell dump files seems too big. But I repeated the export 2 times and the results are the same.

DDLDB2.TPL was indeed adapted to shell.

Accepted Solutions (1)

Accepted Solutions (1)

0 Kudos

Hi There,

I believe the question has already been discussed in one of the OSS message. As mentioned there also, you can go ahead with the further activities in the process tree.

I also believe that steps has already been done.

BR
Isha

Former Member
0 Kudos

Could you please kindly give that OSS note number?   Thanks!

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi!

Your shell system export is quite BIG probably you are exporting the cluster tables (Note 1727317 - Large client dependent table clusters not included in export) or you are not using the right   DDLDB2.TPL file in export_monitor_cmd.properties .

Anyway, feel free to share the solution with the TDMS community.

Cheers,

Fernando