Debug Database Issue

Compare COE and MyJKKN databases to report data inconsistencies.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/Jicate-Solutions/MyJKKN-Library --skill debug-database-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Debug Database Issue
Source: https://github.com/Jicate-Solutions/MyJKKN-Library/tree/main/.claude/skills/debug-db
Command: npx skills add https://github.com/Jicate-Solutions/MyJKKN-Library --skill debug-database-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of identifying and reporting discrepancies between the COE and MyJKKN databases, ensuring data integrity.

Core Features & Use Cases

  • Database Comparison: Automatically check the relevant tables in both databases.
  • Data Verification: Confirm the status of data (Pending vs Published).
  • Reporting: Provide a clear report on which database contains what data.
  • Use Case: When a discrepancy is reported, use this Skill to quickly determine which database has the correct information.

Quick Start

Run the debug-db skill to check the consistency of the 'institutions' table between COE and MyJKKN databases.

Frequently Asked Questions about Debug Database Issue

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check data synchronization discrepancies between COE and MyJKKN databases?

To check data synchronization discrepancies between COE and MyJKKN databases, run a database comparison to automatically verify relevant tables and identify data inconsistencies. You receive a clear report on which database contains what data.

What is the best way to verify Pending versus Published data status across two databases?

The best way to verify Pending versus Published data status across two databases is to perform an automated data verification check. This process compares the relevant tables to confirm data status and reports any inconsistencies between the systems.

How do I detect data integrity issues in the institutions table after a sync failure?

To detect data integrity issues in the institutions table after a sync failure, execute a targeted database comparison. This discrepancy detection process checks the consistency of the institutions table between both databases and reports any mismatched records.

Do I need direct database access and query capabilities to run a database comparison?

Yes, you need direct database access and basic query capabilities to run a database comparison. The discrepancy detection process requires executing queries against the relevant tables in both the COE and MyJKKN databases to verify data synchronization.

Why does one database show different records when data synchronization should match?

One database shows different records when data synchronization should match due to data integrity discrepancies. Running a database comparison identifies these inconsistencies and generates a report detailing which database contains the correct information.

Can I use this database comparison for systems other than COE and MyJKKN?

This database comparison is specifically designed to verify data synchronization between COE and MyJKKN systems. It checks the consistency of specific tables like the institutions table and reports data inconsistencies for IT professionals managing these environments.