AnsweredAssumed Answered

GT Datamaker - Actions on Tables while "Copy Remote Repository"

Question asked by grsollinger on Sep 29, 2017
Latest reply on Oct 3, 2017 by dovle01

While trying to copy a remote repository (Copy Remote Repository - CA Test Data Manager - 4.2 - CA Technologies Documentation ), I set up the debug log in GT Datamaker and I realized that some tables are being dropped, and I would like to ask about this behavior.

I will describe the executed steps:

1. Login to GT Datamaker as "administrator"

2. I set up the debug log in GT Datamaker

Settings Menu -> Options

Click on "Log all Connections" and "Enable debug messages"

Click on the OK button.

3. On the Maintain Project Window, I select a project, right click

A new menu is displayed and I select "Remote actions from different repository" and I select "Connect Remote Repository"

As my execution failed, I took a look at the log and I found the following trace:

 

29-09-2017 14:22:59 - Title: sql server
Message: sql server native client 11.0
Detail:
29-09-2017 14:23:10 - SQLLOG - Remote Repository: select db_name (), rtrim (CONVERT(varchar(254), SERVERPROPERTY ('servername')))
29-09-2017 14:23:10 - SQLLOG - Remote Repository: SELECT 1 FROM sys.objects WHERE object_id =OBJECT_ID ( N'[dbo].[seq_sul]' ) AND type =N'SO'
29-09-2017 14:23:10 - SQLLOG - Repository: DROP TABLE dbo.gtrep_seq_pc
DROP PROCEDURE dbo.seq_pc_nextval
29-09-2017 14:23:10 - SQLLOG - Repository: DROP TABLE dbo.gtrep_seq_ba
DROP PROCEDURE dbo.seq_ba_nextval
29-09-2017 14:23:10 - SQLLOG - Repository: DROP TABLE dbo.gtrep_seq_bl
DROP PROCEDURE dbo.seq_bl_nextval
29-09-2017 14:23:10 - SQLLOG - Repository: DROP TABLE dbo.gtrep_seq_cc
DROP PROCEDURE dbo.seq_cc_nextval
29-09-2017 14:23:10 - SQLLOG - Repository: DROP TABLE dbo.gtrep_seq_exl
DROP PROCEDURE dbo.seq_exl_nextval
29-09-2017 14:23:10 - SQLLOG - Repository: DROP TABLE dbo.gtrep_seq_ld
DROP PROCEDURE dbo.seq_ld_nextval
29-09-2017 14:23:10 - SQLLOG - Repository: DROP TABLE dbo.gtrep_seq_lod
DROP PROCEDURE dbo.seq_lod_nextval
29-09-2017 14:23:10 - SQLLOG - Repository: DROP TABLE dbo.gtrep_seq_lof
DROP PROCEDURE dbo.seq_lof_nextval
29-09-2017 14:23:10 - SQLLOG - Repository: DROP TABLE dbo.gtrep_seq_pj
DROP PROCEDURE dbo.seq_pj_nextval
29-09-2017 14:23:10 - SQLLOG - Repository: DROP TABLE dbo.gtrep_seq_pja
DROP PROCEDURE dbo.seq_pja_nextval
29-09-2017 14:23:10 - SQLLOG - Repository: DROP TABLE dbo.gtrep_seq_prog
DROP PROCEDURE dbo.seq_prog_nextval
29-09-2017 14:23:10 - SQLLOG - Repository: DROP TABLE dbo.gtrep_seq_rel
DROP PROCEDURE dbo.seq_rel_nextval
29-09-2017 14:23:10 - SQLLOG - Repository: DROP TABLE dbo.gtrep_seq_se
DROP PROCEDURE dbo.seq_se_nextval
29-09-2017 14:23:10 - SQLLOG - Repository: DROP TABLE dbo.gtrep_seq_smh
DROP PROCEDURE dbo.seq_smh_nextval
29-09-2017 14:23:10 - SQLLOG - Repository: DROP TABLE dbo.gtrep_seq_su
DROP PROCEDURE dbo.seq_su_nextval
29-09-2017 14:23:10 - SQLLOG - Repository: DROP TABLE dbo.gtrep_seq_sul
DROP PROCEDURE dbo.seq_sul_nextval
29-09-2017 14:23:10 - SQLLOG - Repository: DROP TABLE dbo.gtrep_seq_tc
DROP PROCEDURE dbo.seq_tc_nextval
29-09-2017 14:23:10 - SQLLOG - Repository: DROP TABLE dbo.gtrep_seq_tcd
DROP PROCEDURE dbo.seq_tcd_nextval
29-09-2017 14:23:10 - SQLLOG - Repository: DROP TABLE dbo.gtrep_seq_td
DROP PROCEDURE dbo.seq_td_nextval
29-09-2017 14:23:10 - SQLLOG - Repository: DROP TABLE dbo.gtrep_seq_tfc
DROP PROCEDURE dbo.seq_tfc_nextval
29-09-2017 14:23:10 - SQLLOG - Repository: DROP TABLE dbo.gtrep_seq_tfca
DROP PROCEDURE dbo.seq_tfca_nextval
29-09-2017 14:23:10 - SQLLOG - Repository: DROP TABLE dbo.gtrep_seq_tig
DROP PROCEDURE dbo.seq_tig_nextval
29-09-2017 14:23:10 - SQLLOG - : DROP TABLE dbo.gtrep_seq_tr
DROP PROCEDURE dbo.seq_tr_nextval
29-09-2017 14:23:10 - SQLLOG - Repository: DROP TABLE dbo.gtrep_seq_vf
DROP PROCEDURE dbo.seq_vf_nextval
29-09-2017 14:23:10 - SQLLOG - Repository: DROP TABLE dbo.gtrep_seq_wl
DROP PROCEDURE dbo.seq_wl_nextval
29-09-2017 14:23:10 - SQLLOG - Repository: DROP TABLE dbo.gtrep_seq_vtdm
DROP PROCEDURE dbo.seq_vtdm_nextval
29-09-2017 14:23:10 - SQLLOG - Repository: SELECT getdate ( ) FROM gtrep_system
29-09-2017 14:23:10 - SQLLOG - Repository: INSERT INTO gtrep_error_log ( el_session_guid , el_vm_id , el_timestamp , el_db_session_id , el_su_id , el_type , el_code , el_spec_code , el_message , el_severity ) VALUES ( ? , ? , ? , ? , ? , 'MESSAGE' , 0 , 0 , ? , 0 )
29-09-2017 14:23:10 - Title: Sequence Update Error
Message: Could not drop the pseudo sequences!... ROLLING BACK changes

 

Why are these tables being drop? I approach you this question, because we expect not to harm the repository while performing this action.

 

Thanks for your help

Outcomes