Company: Link Technologies
Case No: L09043. Project: 09.40: LinkSOFT Version 9.4
Logged By: Aarti Pooja Gayaneshwar (Link Business Solutions) on 10 Jan 2018 09:48AM
Priority: High
Product: Point of Sale
Group: Software Defect
Time Taken: 5.50 (Weight: 5.50)
Version: 9.496.1128
Assigned To: Sanjay (Link Technologies)
Circulation: Aarti Pooja Gayaneshwar, Alvis, Development, Rashna, Sanjay
Resolve By: Thursday, 11 January 2018 12:00 AM [2296 days since logged date]
Status: Closed
Subject: Removed replication triggers before starting upgrade as this is causing problems with new replication model
Summary:    

Hi Sanjay,

While upgrading MY Transport Linksoft database, the following is received:

The database is setup in QA4 as Linksoft

The database is being upgraded from 819 to 829

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

8190-LINKSOFT Upgrade to 8200.sql

Invalid object name 'LT_REPL_CONTROL_OUT'.

--Data migration scripts
UPDATE LT_SYS_StationConfiguration SET Value = 'Reports\POS-PS154-Receipt80mm.rpt' WHERE Module = 'POS' and Flag = 'ReportNameQuote' AND Value NOT LIKE '%A4.rpt'
UPDATE LT_SYS_StationConfiguration SET Value = 'Reports\POS-PS154-Receipt80mm.rpt' WHERE Module = 'POS' and Flag = 'ReportNameLayby' AND Value NOT LIKE '%A4.rpt'
UPDATE LT_SYS_StationConfiguration SET Value = 'Reports\POS-PS154-Receipt80mm.rpt' WHERE Module = 'POS' and Flag = 'ReportNameCredit' AND Value NOT LIKE '%A4.rpt'
UPDATE LT_SYS_StationConfiguration SET Value = 'Reports\POS-PS154-Receipt80mm.rpt' WHERE Module = 'POS' and Flag = 'ReportNameReceipt' AND Value NOT LIKE '%A4.rpt'
UPDATE LT_SYS_StationConfiguration SET Value = 'Reports\POS-PS154-Receipt80mm.rpt' WHERE Module = 'POS' and Flag = 'ReportNameReturns' AND Value NOT LIKE '%A4.rpt'

UPDATE LT_SYS_StationConfiguration SET Value = 'Reports\POS-PS155-ReceiptA4.rpt' WHERE Module = 'POS' and Flag = 'ReportNameQuote' AND Value LIKE '%A4.rpt'
UPDATE LT_SYS_StationConfiguration SET Value = 'Reports\POS-PS155-ReceiptA4.rpt' WHERE Module = 'POS' and Flag = 'ReportNameLayby' AND Value LIKE '%A4.rpt'
UPDATE LT_SYS_StationConfiguration SET Value = 'Reports\POS-PS155-ReceiptA4.rpt' WHERE Module = 'POS' and Flag = 'ReportNameCredit' AND Value LIKE '%A4.rpt'
UPDATE LT_SYS_StationConfiguration SET Value = 'Reports\POS-PS155-ReceiptA4.rpt' WHERE Module = 'POS' and Flag = 'ReportNameReceipt' AND Value LIKE '%A4.rpt'
UPDATE LT_SYS_StationConfiguration SET Value = 'Reports\POS-PS155-ReceiptA4.rpt' WHERE Module = 'POS' and Flag = 'ReportNameReturns' AND Value LIKE '%A4.rpt'

UPDATE LT_SYS_StationConfigurationBase SET Value = 'Reports\POS-PS154-Receipt80mm.rpt' WHERE Module = 'POS' and Flag = 'ReportNameQuote'
UPDATE LT_SYS_StationConfigurationBase SET Value = 'Reports\POS-PS154-Receipt80mm.rpt' WHERE Module = 'POS' and Flag = 'ReportNameLayby'
UPDATE LT_SYS_StationConfigurationBase SET Value = 'Reports\POS-PS154-Receipt80mm.rpt' WHERE Module = 'POS' and Flag = 'ReportNameCredit'
UPDATE LT_SYS_StationConfigurationBase SET Value = 'Reports\POS-PS154-Receipt80mm.rpt' WHERE Module = 'POS' and Flag = 'ReportNameReceipt'
UPDATE LT_SYS_StationConfigurationBase SET Value = 'Reports\POS-PS154-Receipt80mm.rpt' WHERE Module = 'POS' and Flag = 'ReportNameReturns'
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Audit Notes:
10 Jan 201807:44AM Comment 1 by Alvis (Link Technologies) Case 9043 added to project 8.3
10 Jan 201809:48AM Comment 2 by Rashna (Edge Business Solutions) Assigned To: Development Followup Date: 10-01-2018 09:48 AM Time Taken: 1.00

Development meeting January 2018 Sanjeet, Vineet, Alvis, Rashna and Sanjay

The cause of the problem is that old triggers of replication was not removed why the upgrade process.

Solution: The upgrade process should all old replication triggers as version 8.2.9 creates new triggers 


16 Jan 201802:41PM Comment 3 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 16-01-2018 02:41 PM Time Taken: 1.00

The following have been completed:

  1. Upgrade scripts have been changed to remove replication triggers before starting the upgrade process. These triggers are re-created after the upgrade is complete.

06 Feb 201811:28AM Comment 4 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 06-02-2018 11:28 AM
Hi Rashna, this change is ready for UAT in LinkSOFT Versio 8.3.000 which is on our FTP site at this address: \\10.0.0.9\ftp\LinkSoftware\LinkSOFT\83  

08 Feb 201803:07PM Comment 5 by Rashna (Edge Business Solutions) Assigned To: Alvis (Link Technologies) Followup Date: 09-02-2018 12:00 AM Time Taken: 1.00
QA Results
Step 1 - Developer will perform test based on test cases provided
Step 2 - Product expert to complete Product QA based on test cases.

Test cases are provided on the case header before the case is approved for development.

Test Results Summary

Table 1 - Summarised list of issues
NoTest Description Pass/Fail 
1
 Upgrade client database  Upgrade should be successful without errors. 

 Failed.

Upgrade from version 819 to 8.30 (MY Transport)

Upgrade from version 8.11 to 8.30 (PAFCO)


QA Environment Details

  1. OS version:Windows 7
  2. Application version:8300.00
  3. Database (Demo/New/Client): CLIENT_PAFCO_LINKSOFT and CLIENT_MY_LINKSOFT on QA4.

Steps to reproduce failed scenarios:

  1. Attached is a notepad with the full error.

    09 Feb 201802:29PM Comment 6 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 09-02-2018 02:29 PM Time Taken: 1.00

    Hi Rashna,

    The issue was caused by the LT_REPL_RULE table update. This has been corrected in beta 2.

    regards
    Alvis


    13 Feb 201811:52AM Comment 7 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 13-02-2018 11:52 AM Time Taken: 0.50
    System test complete. Please proceed with UAT.

    13 Feb 201802:14PM Comment 8 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 13-02-2018 02:14 PM Time Taken: 1.00
    QA Results
    Step 1 - Developer will perform test based on test cases provided
    Step 2 - Product expert to complete Product QA based on test cases.

    Test cases are provided on the case header before the case is approved for development.

    Test Results Summary

    Table 1 - Summarised list of issues
    NoTest Description Pass/Fail 
    1
    		Upgrade client database  Upgrade should be successful without errors 
     
    		Pass, database upgraded without errors.

    QA Environment Details

    1. OS version: Windows 7
    2. Application version: 8.3.2
    3. Database (Demo/New/Client): Client - CLIENT-MY-LINKSOFT

    Steps to reproduce failed scenarios:



      09 Oct 201908:14AM Comment 9 by Sanjay (Link Technologies) Quality control status: Pass. QC Not required - This case was created before quality check was implemented in version 11 on 30/06/2019
      Attachments:
      General Documents - Case: 9043:MY8300UpgradeError.txt
      If you have any queries regarding this support incident, please email admin@linktechnologies.com.au and include the Case No: L09043 in the subject line of all emails regarding this issue.

      Document size: 12.6 KB
      For call complaints, please contact the Managing Director of the company using this form.