Skip to content

Double Pool Check

Description

You have received an email notification titled "Check for double pool on [HOST]". This email is generated by an automated script on Gaia designed to detect instances where multiple 'pool' definitions exist for the exact same flight segment and associated pool characteristics within the flightallotment table. Such duplicates can lead to incorrect capacity reporting, booking errors, and data inconsistencies. This notification requires immediate attention to maintain data integrity.

Script location:

/quintessence-gaia-custom/custom/[CUSTOMER]/apps/qc/gaia/extensions/scripts/

Impact

This is a High Priority alert. Duplicate pool entries can lead to:

  • Overbooking/Underbooking: Inaccurate available capacity being reported or allocated.
  • Revenue Loss: Incorrectly managed inventory.
  • Operational Disruptions: Confusion for booking agents and passengers.
  • Reporting Inaccuracies: Skewed business intelligence.

Resolution Steps

Check ticketing status: If PNR already ticketed, check with customer on preferred actions. As corrections need to be made not only on our application, but on external booking system too (Amadeus, Newskies etc.)

Removing the duplicate

WARNING: Modifying data in a production system, especially flightallotment records, can have severe consequences if not done carefully. Always ensure you have appropriate permissions, understand the impact, and follow any internal change management procedures. Never delete records with active bookings without a robust migration plan for those bookings.

  1. Backup: If you are performing direct database manipulation, ensure you have a backup or a way to roll back changes.

  2. Identify: Based on your investigation pinpoint the lngid of the flightallotment record(s) that are erroneous or should be removed.

  3. Delete: The erroneous entries must be removed from flightallotment table with mysql statement.

    Please use precaution as deleting from production database. Make sure that there are no allotments on the entry to be deleted. Use a limit for your delete statement.

  4. Verify: After making changes, re-check the affected flight in flightdeck and/or database to confirm that only one valid flightallotment record (for the given pool characteristics) now exists.

    If necessary, manually re-run the doublepoolcheck script or wait for its next scheduled execution to confirm that the problematic entry no longer appears in subsequent notifications.