claude-code - 💡(How to fix) Fix [Bug] Claude edits files despite explicit instruction not to and auto-edit disabled [1 comments, 2 participants]

[{"error":"McpToolCallError: Error calling tool 'execute_query': 002003 (02000): SQL compilation error:\nDatabase 'STUBHUB_FINTECH' does not exist or not authorized.\n at uL7 (/$bunfs/root/src/entrypoints/cli.js:4736:63)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-23T16:58:37.621Z"},{"error":"McpToolCallError: Error calling tool 'execute_query': 002003 (02000): SQL compilation error:\nSchema 'FINTECH_DW.TAX' does not exist or not authorized.\n at uL7 (/$bunfs/root/src/entrypoints/cli.js:4736:63)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-23T16:58:52.896Z"},{"error":"McpToolCallError: Error calling tool 'execute_query': 002003 (02000): SQL compilation error:\nSchema 'FINTECH_DW.EZRA' does not exist or not authorized.\n at uL7 (/$bunfs/root/src/entrypoints/cli.js:4736:63)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-23T16:59:45.851Z"},{"error":"McpToolCallError: Error calling tool 'execute_query': 002003 (42S02): SQL compilation error:\nObject 'FINTECH_DW.CORE.DIM_FX_DAILY' does not exist or not authorized.\n at uL7 (/$bunfs/root/src/entrypoints/cli.js:4736:63)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-23T17:01:42.305Z"},{"error":"McpToolCallError: Error calling tool 'execute_query': 000939 (22023): SQL compilation error: error line 1 at position 1,454\ntoo many arguments for function [IFF(J.MATCH_TYPE = 'v1_only', J.COUNTRY_CODE, J.INTEREST_ACCOUNTING_PERIOD, J.TAX_ACCOUNTING_PERIOD, J.V1_INTEREST, J.V2_INTEREST, J.MATCH_TYPE, SYS_VW.COUNTRY_CODE_1, SYS_VW.ACCOUNTING_PERIOD_0, SYS_VW.CURRENCY_CODE_2, SYS_VW.MONTH_1, SYS_VW.BASE_CURRENCY_0, SYS_VW.RATE_TO_USD_2, null)] expected 3, got 14\n at uL7 (/$bunfs/root/src/entrypoints/cli.js:4736:63)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-23T17:02:36.225Z"},{"error":"McpToolCallError: Error calling tool 'execute_query': 002031 (42601): SQL compilation error:\nUnsupported subquery type cannot be evaluated at line 1, position 1586\n at uL7 (/$bunfs/root/src/entrypoints/cli.js:4736:63)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-23T17:20:46.811Z"},{"error":"McpToolCallError: Error calling tool 'execute_query': 000904 (42000): SQL compilation error: error line 1 at position 153\ninvalid identifier 'V1.CUMULATIVE_INTEREST_STATUTORY'\n at uL7 (/$bunfs/root/src/entrypoints/cli.js:4736:63)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-23T17:45:45.068Z"},{"error":"McpToolCallError: Error calling tool 'execute_query': 001003 (42000): SQL compilation error:\nsyntax error line 1 at position 227 unexpected 'rows'.\nsyntax error line 1 at position 620 unexpected 'rows'.\nsyntax error line 1 at position 1,091 unexpected 'rows'.\nsyntax error line 1 at position 1,111 unexpected 'rows'.\nsyntax error line 1 at position 1,131 unexpected 'rows'.\n at uL7 (/$bunfs/root/src/entrypoints/cli.js:4736:63)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-23T17:46:03.535Z"},{"error":"McpToolCallError: Error calling tool 'execute_query': 000904 (42000): SQL compilation error: error line 1 at position 177\ninvalid identifier 'FX.FX_RATE_TO_USD'\n at uL7 (/$bunfs/root/src/entrypoints/cli.js:4736:63)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-23T17:46:12.207Z"},{"error":"McpToolCallError: Error calling tool 'execute_query': 000904 (42000): SQL compilation error: error line 1 at position 21\ninvalid identifier 'INTEREST_RATE'\n at uL7 (/$bunfs/root/src/entrypoints/cli.js:4736:63)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-23T17:51:21.378Z"},{"error":"McpToolCallError: Error calling tool 'execute_query': 002003 (02000): SQL compilation error:\nSchema 'FINTECH_DW.EZRA' does not exist or not authorized.\n at uL7 (/$bunfs/root/src/entrypoints/cli.js:4736:63)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-23T18:46:51.956Z"},{"error":"McpToolCallError: Error calling tool 'execute_query': 002003 (02000): SQL compilation error:\nSchema 'FINTECH_DW.EZRA_CORE' does not exist or not authorized.\n at uL7 (/$bunfs/root/src/entrypoints/cli.js:4736:63)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-23T18:46:58.981Z"},{"error":"McpToolCallError: Error calling tool 'execute_query': 002003 (02000): SQL compilation error:\nSchema 'ADHOC.EZRA_CORE' does not exist or not authorized.\n at uL7 (/$bunfs/root/src/entrypoints/cli.js:4736:63)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-23T18:48:15.890Z…

TL;DR

The most likely fix involves addressing SQL compilation errors and ensuring proper database schema and object existence, as well as correcting query syntax.

Guidance

1. Verify Database and Schema Existence: Ensure that the databases and schemas mentioned in the errors (e.g., STUBHUB_FINTECH, FINTECH_DW.TAX, FINTECH_DW.EZRA) exist and are properly configured.
2. Check Query Syntax: Review the SQL queries for syntax errors, particularly around the use of functions like IFF and subqueries, as indicated by the error messages.
3. Authorize Access: Confirm that the user or service account executing the queries has the necessary permissions to access the referenced databases, schemas, and objects.
4. Review Object Names: Validate that object names (e.g., V1.CUMULATIVE_INTEREST_STATUTORY, FX.FX_RATE_TO_USD, INTEREST_RATE) are correctly spelled and exist in the expected schemas.

Example

No specific code snippet can be provided without the exact query, but ensuring that queries follow the correct syntax and that all referenced objects exist is crucial. For example, if using a function like IFF, ensure it's used with the correct number of arguments as per the database system's documentation.

Notes

The provided error messages suggest a mix of issues related to database and schema existence, query syntax, and object accessibility. Resolving these will likely require a combination of database administration tasks and code review.

Recommendation

Apply a workaround by carefully reviewing and correcting the SQL queries to ensure they are syntactically correct and reference existing, accessible database objects. This approach is recommended because it directly addresses the errors reported without requiring additional context or version upgrades.