Articles in this section

See more

Migration Instruction (for Migration from Dr. Sum EA 4.1 or 4.2 to Dr. Sum 5.1)

Avatar
GSS Japan
  • Updated
Follow

13/Aug/2019

We found a critical issue when rolling back from Dr. Sum Ver. 5.1 to Dr. Sum EA Ver. 4.1 or 4.2, which results in database connection error (see this article for detail). This article describes revised migration instruction in Dr. Sum 5.1 System Migration Guide to avoid the error.

 Upgrade and migration from Dr. Sum 4.1 or 4.2 to 5.1 should be done in following order:

 I. Install Dr. Sum 5.1 

  1. Stop Dr. Sum EA 4.1 or 4.2 Server service if it's in-place upgrade (upgrade on the same server).

  2. Install Dr. Sum 5.1 server, Administrative tool (and Development kit if necessary). Activate the server and complete initial settings. For detail, refer to Chapter 1 Install Dr. Sum in Dr. Sum Setup Guide.

     Note: Ensure you have installed the latest patch on Dr. Sum 5.1 before migration. Otherwise, you may fail to migrate the data. Contact us for the latest version of patch.

  3. Go to Windows Start menu and click Start service under Dr. Sum 5.1 to stop Dr. Sum 5.1 Server service.

  4. Start Dr. Sum EA 4.1 or 4.2 Server service.  

II. Migrate files and data

  1. Stop Dr. Sum EA 4.1 or 4.2 Server service.

  2. Copy following files from Dr. Sum EA 4.1 or 4.2 to Dr. Sum 5.1 manually. They should be copied from source server to destination server even if it's in-place upgrade. Ensure that folder structure under Dr. Sum installation folder is identical between source and destination servers.
    • Database file (*1) 
    • Virtual table file (*2) 
    • Excel Extractor configuration file
    • Excel template file
      (*1) path can be found in Directory in Database Properties in Enterprise Manager
      (*2) path can be found in Virtual Table Root Directory in General in Server Settings in Enterprise Manager

  3. Start Dr. Sum EA 4.1 or 4.2 Server service.

  4. Migrate system information and user information with batch command. 
    1. Open command prompt as administrator.

    2. Move to "<Dr. Sum 5.1 Installation Folder>\cmd\ENG" folder

    3. Run following command:

      "dwsys_convert <source server name> <source port number> <source Dr. Sum 4.1 or 4.2 user ID>" <password> <value for environment variables "DW_TEXT_SYSTEM_PATH" on source server>

      Refer to "2-14 dwsys_convert (convert system information)" in  Dr. Sum Server Command Reference for detail about command arguments.

  5. Stop Dr. Sum EA 4.1 or 4.2 Server service.

  6. Copy the common folder from source to destination server. Path for the common folder can be found in Common Folder Root in General tab in Server Settings in Enterprise Manager.

  7. Click Start service under Dr. Sum 5.1 in Windows Start menu to start Dr. Sum 5.1 Server service.

III. Migrate DSQL alias files

If you use the DSQL alias file "DWALIAS.ini" included in the Administrative Tools, copy it from Dr. Sum EA 4.1 or 4.2 to Dr. Sum 5.1 server manually. You can skip this step If you've not created it on Dr. Sum EA 4.1 or 4.2 DSQL alias files are archived as follows:  

 Dr. Sum EA 4.1   C:\Users\<Windows user name>\AppData\Local\DWODS41Apps\DSQL 
 Dr. Sum EA 4.2  C:\Users\<Windows user name>\AppData\Local\DWODS42Apps\DSQL
 Dr. Sum 5.1  C:\Users\<Windows user name>\AppData\Local\DWODS51Apps\DSQL

 

 IV. Create ODBC data source 

If you use ODBC driver included in the Development kit on Dr. Sum EA 4.1 or 4.2, you need to create ODBC data source on Dr. Sum 5.1 as well. You can skip this step if you've not created it on Dr. Sum EA 4.1 or 4.2. Settings in ODBC Data source can be found as follows:  

  1. Click Windows Administrative tool in Windows Start menu and click ODBC Data Source Administrator (32-bit or 64 bit).

  2. Click System DSN tab.

  3. Click Add if you create new data source for Dr. Sum 5.1 and name "Dr.Sum 5.1 ODBC Driver".  

Note: if you have existing ODBC data source for Dr. Sum EA 4.x and create a new data source with the same name, old data source will be overwritten.  

V. Post-migration settings  

  • If you use any security software, exclude following folders from monitoring target.
    • Virtual Table Root and Common Folder Root in General tab in Server Settings in Enterprise Manager.
    • Import Temporary Directory in Import tab in Server Settings in Enterprise Manager.
    • Database archive folder
    • "C:\Users\<Windows user name>\AppData\Local\DWODS51Apps"

  • If you use any batch commands on Dr. Sum EA 4.x, ensure to change folder location for command file and their arguments. if you change computer name and IP address for the Dr. Sum 5.1 Server, you need to reflect the changes in the batch commands accordingly. 
Command File Location
dwdb_convert
dwsys_convert
dwvtb_convert
dwvtb_utils
dwsvc_ctrl		    <Dr.Sum Server Installation folder>\cmd\eng   
Other commands <Administrative Tools Installation folder>\cmd\eng

 

  • If you use any compound key which includes "TIME", "TIMESTAMP" or "INTERVAL" type of precision, you need to create the compound key again and update search index and join index since the precision is changed from second to micro-second in Dr. Sum 5.1. If you are not sure you need to create it or not, run following command as administrator in the command prompt:
  1. Go to <Administrative Tool Installation folder>\RecreateCompoundkeySql\bin\eng on destination server.

  2. Run following command:
    "dwrecreate_compoundkey_sql <destination server name> <destination port number> <destination Dr. Sum user ID> <password>" 
    Note: "destination Dr. Sum user ID" needs to belong to the Administrators group.

  3. If you see following message, you don't need to create the compound key: "Execution of the DSQL command is unnecessary."

    I    f you see following message, you need to create the compound key: "Searching for compound key successfully".  

    If you see following message, any error occurred: "Searching for compound key failed." Dr. Sum server service may not start or there are any invalid arguments configured in the compound key. Fix them and run the tool again. 

    How to recreate compound key: 
    1. Open "recreate_compoundkey.dsql" in text editor, change password in it  (see bold string below) and save it in UTF-8 without BOM. 

login Administrator/PASSWORD@localhost:6001

 

-- Database test start

connect test ;

drop index if exists rindex ;

drop join index if exists jindex ;

alter table master drop constraint m_cp1 ;

alter table master add constraint compound key m_cp1 (code, datetime) not null unique ;

alter table data drop constraint d_cp1 ;

alter table data add constraint compound key d_cp1 (code, datetime)  ;

create index rindex on data(d_cp1) ;

create join index jindex on master(m_cp1) references data(d_cp1);

close ;

-- Database test end

 

logout


2. Move to the folder where "recreate_compoundkey.dsql" is archived and run the following command to recreate a compound key, search index and join index. 

"<Administrative Tools Installation Folder>\bin\DWCMDW recreate_compoundkey.dsql"

 

Related articles

Comments

0 comments

Please sign in to leave a comment.

Powered by Zendesk