Project

General

Profile

Actions

결함(Bug) #166

closed

[VOC-Bug] Wrong remaining allotment for this Hotel 886479 The Stay Classic Myeongdong

Added by Joseph Vo 10 months ago. Updated 8 months ago.

Status:
완료성공(Resolve)
Priority:
보통(Normal)
Assignee:
Target version:
Start date:
05/12/2025
Due date:
06/03/2025
% Done:

100%

Estimated time:
Spent time:
Part:
Build env.:
Prod

Description

Kindly check remaining allotment for this Hotel 886479 The Stay Classic Myeongdong.

886479 - The Stay Classic Myeongdong
Exclusive Rate : 105720 // 119660 - Deluxe Twin (H) No Parking
Period : 6/15-19


Files

image.png (12.3 KB) image.png Joseph Vo, 05/07/2025 03:05 AM

Related issues

Related to Ellis improvement - 결함(Bug) #495: [Issue] Validate concurrent booking and cancel in Channel API완료성공(Resolve)calvin dev06/04/202506/05/2025

Actions
Actions #1

Updated by Joseph Vo 10 months ago

@Vin Daniel Do run script to check and update all HardBlock hotel have different allotments

Actions #2

Updated by Daniel Do 10 months ago

  • Status changed from 신규(New) to 진행(Doing)
  • Start date set to 05/12/2025
Actions #3

Updated by Daniel Do 10 months ago

  • % Done changed from 0 to 50
Actions #4

Updated by Daniel Do 10 months ago

We haven't identified the root cause.
We'll need to monitor more cases in the future to see if it happens again.

SET @checkInFrom = '20250501';
SET @checkInTo = '20250430';

SELECT
RS.HOTEL_CODE,
RS.VENDOR_ROOM_TYPE_SEQ,
RS.APPLIED_DATE,
AL.ALLOTMENT_COUNT_SUM AS TOTAL_COUNT,
AL.LEFT_COUNT_SUM AS REMAIN_COUNT,
RS.CONFIRM_COUNT,
RS.CANCEL_COUNT,
RS.BOOKINGS,
AL.FIRST_INSERT_DATETIME,
AL.LAST_UPDATE_DATETIME
FROM VD_VENDOR_ROOM_ALLOTMENT AL
INNER JOIN (
SELECT DISTINCT
B.HOTEL_CODE,
B.HOTEL_CONTRACT_SEQ,
T.VENDOR_ROOM_TYPE_SEQ,
BR.APPLIED_DATE,
SUM THEN 1 ELSE 0 END) AS CONFIRM_COUNT,
SUM THEN 1 ELSE 0 END) AS CANCEL_COUNT,
GROUP_CONCAT(B.BOOKING_ITEM_CODE SEPARATOR ', ') AS BOOKINGS
FROM BK_BOOKING_HOTEL_ITEM B
INNER JOIN BK_BOOKING_ROOM_AMOUNT BR ON BR.BOOKING_ITEM_CODE = B.BOOKING_ITEM_CODE
INNER JOIN VD_VENDOR_ROOM_PLAN R ON B.HOTEL_CONTRACT_SEQ = R.HOTEL_CONTRACT_SEQ AND R.ROOM_PLAN_SEQ = (SUBSTRING_INDEX(SUBSTRING_INDEX(B.ROOM_PLAN_SEQ, '|',1),'^',1) + 0)
INNER JOIN VD_VENDOR_HOTEL_CONTRACT C ON R.HOTEL_CONTRACT_SEQ = C.HOTEL_CONTRACT_SEQ AND C.HOTEL_CONTRACT_TYPE_CODE = 'HOC01'
INNER JOIN VD_VENDOR_ROOM_TYPE T ON R.VENDOR_ROOM_TYPE_SEQ = T.VENDOR_ROOM_TYPE_SEQ AND T.HARD_BLOCK_YN = 'Y'
WHERE -- date(B.FIRST_INSERT_DATETIME) < date(B.CHECK_IN_DATE) -- remove booking un-sold
DATE IN (SELECT DATE_ADD(date(@checkInFrom), INTERVAL ID DAY) AS GEN_DATE FROM Z_ZID WHERE ID < 31)
-- AND B.BOOKING_ITEM_CODE = 'K25050710062H01'
AND B.HOTEL_CODE = 739324
-- AND T.VENDOR_ROOM_TYPE_SEQ = 1274597
-- AND B.BOOKING_STATUS_CODE IN ('BKS03', 'BKS06')
GROUP BY B.HOTEL_CONTRACT_SEQ, T.VENDOR_ROOM_TYPE_SEQ, BR.APPLIED_DATE

) RS ON AL.VENDOR_ROOM_TYPE_SEQ  = RS.VENDOR_ROOM_TYPE_SEQ AND AL.APPLIED_DATE = RS.APPLIED_DATE
WHERE AL.HOTEL_CONTRACT_SEQ = RS.HOTEL_CONTRACT_SEQ AND AL.LEFT_COUNT_SUM <> AL.ALLOTMENT_COUNT_SUM - RS.CONFIRM_COUNT
ORDER BY RS.APPLIED_DATE;
Actions #5

Updated by Daniel Do 10 months ago

  • Due date set to 05/14/2025
  • Status changed from 진행(Doing) to 완료(Done)
  • % Done changed from 50 to 100

Need more case happen in the future to check.

Actions #6

Updated by Daniel Do 10 months ago

  • Due date changed from 05/14/2025 to 05/16/2025
  • Status changed from 완료(Done) to 진행(Doing)
  • % Done changed from 100 to 50

Continue investigation

Actions #7

Updated by Daniel Do 10 months ago

Follow up to get more cases and investigation

Actions #8

Updated by Daniel Do 10 months ago

  • Due date changed from 05/16/2025 to 05/23/2025
Actions #9

Updated by Daniel Do 9 months ago

  • % Done changed from 50 to 80
Actions #10

Updated by Daniel Do 9 months ago

  • Due date changed from 05/23/2025 to 06/03/2025
  • Status changed from 진행(Doing) to 완료(Done)
  • % Done changed from 80 to 100

The root cause: the channels has sent the message cancel booking concurrent.
Alice rollback allotment 2 times.
Sollution: insert key with booking channel into database, got exception unique key to waiting and return status booking.
Calvin will fix it

Actions #11

Updated by Daniel Do 9 months ago

  • Build env. set to Staging
Actions #12

Updated by ziniy Kang 9 months ago

  • Assignee changed from Daniel Do to Tracy Tran
  • Target version set to v1.0.0
Actions #13

Updated by ziniy Kang 9 months ago

  • Related to 결함(Bug) #495: [Issue] Validate concurrent booking and cancel in Channel API added
Actions #14

Updated by Joseph Vo 9 months ago

  • Assignee changed from Tracy Tran to Anonymous

@Kyle ziniy Kang, Kyle will test it on API Channel

Actions #15

Updated by Anonymous 9 months ago

Hi a Joseph Vo, apologise for my late response on the ticket.

The test result of the ticket was mentioned from the resolved one http://redmine.ohmytrip.com/issues/495#note-18

Hence I will change status of the ticket into Resolved

Thanks

Actions #16

Updated by Anonymous 9 months ago

  • Status changed from 완료(Done) to 완료성공(Resolve)
  • Assignee changed from Anonymous to Daniel Do
Actions #17

Updated by ziniy Kang 9 months ago

  • Status changed from 완료성공(Resolve) to 완료(Done)
Actions #18

Updated by Daniel Do 8 months ago

  • Build env. changed from Staging to Prod
Actions #19

Updated by ziniy Kang 8 months ago

  • Status changed from 완료(Done) to 완료성공(Resolve)
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 50 MB)