Test Data Manager

  • 1.  GT Datamaker - Actions on Tables while "Copy Remote Repository"

    Posted Sep 29, 2017 09:28 AM

    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



  • 2.  Re: GT Datamaker - Actions on Tables while "Copy Remote Repository"
    Best Answer

    Broadcom Employee
    Posted Oct 03, 2017 11:58 AM

    Hi Gladys,

     

    We need to get some context wrapped around this question. 

     

    Are you logged into the Repository you want to copy to?  This is important because you are copying from the remote Repository to your current Repository.  One of the instructions state "Connect to the repository to which you want to copy connection profiles from a remote repository."  So think of this as pulling from your source to this repository you are logged into.

     

    Here is the link to the docs:

    Copy Remote Repository

     

    I will confirm with Development, but by the looks of these tables, they are directly related to the remote copy function.  Therefore the rest of your projects and Repository will not be affected negatively. 

     

    As far as the rollback, it would appear that the connection did not work and this is the expected result.

     

    Cheers!

    Les



  • 3.  Re: GT Datamaker - Actions on Tables while "Copy Remote Repository"

    Broadcom Employee
    Posted Oct 03, 2017 12:02 PM

    Hi Gladys,

     

    If you are having problems, I would suggest you open a case.  We did get more information from the Developers:

     

    The dropping of those tables and procedures have nothing to do with remote copy repo.

     

    1. SQL Server 2008 does not include sequence objects. We therefore decided to use tables and procedures. We call them pseuso-sequences
    2. SQL Server 2012 and above know about sequences.
    3. When you restore a backed up repo, it will contain pseudo-sequences
    4. When you start Datamaker, it will check if we are using SQL Server 2012 and above (SELECT 1 FROM sys.objects WHERE object_id =OBJECT_ID ( N'[dbo].[seq_sul]' ) AND type =N'SO')
    5. When confirmed, Datamaker will then try to remove the pseudo-sequences (table like dbo.gtrep_seq_ba and procedure like dbo.seq_ba_nextval) and generate real sequenes
    6. If successful, all is fine Datamaker will only use real sequences with SQL Server 2012 and above
    7. If not then we roll back (Could not drop the pseudo sequences!... ROLLING BACK changes)

     

    Need investigating….

     

    Hope this helps.

    Cheers!
    Les