troubleshooting

BigQuery Troubleshooting

Parent Skill: /bigquery
Path: /bigquery/troubleshooting

Purpose

Debug errors, resolve common issues, and fix BigQuery problems.

When to Use

Trigger when:

• Keywords: error, fail, debug, troubleshoot, fix, problem
• User encounters: permissions errors, quota errors, syntax errors

Chat commands:

/bigquery/troubleshooting fix error "Resources exceeded"
/bigquery/troubleshooting debug permission denied
/bigquery/troubleshooting resolve syntax error in query

---

Common Errors & Solutions

1. Permission Denied (403)

Error:

Access Denied: BigQuery BigQuery: Permission denied while getting Drive credentials

Solutions:

# Grant necessary role
gcloud projects add-iam-policy-binding PROJECT_ID \
  --member="user:EMAIL" \
  --role="roles/bigquery.dataViewer"

# Check current permissions
bq show --dataset PROJECT:DATASET

2. Resources Exceeded (400)

Error:

Resources exceeded during query execution

Solutions:

-- Use partition filter
SELECT * FROM events
WHERE DATE(timestamp) = '2024-02-09'  -- Add partition filter
LIMIT 1000;

-- Break into smaller queries
-- Use LIMIT for development
-- Add more WHERE filters

3. Syntax Errors (400)

Error:

Syntax error: Expected end of input but got keyword SELECT

Common causes:

• Missing comma in SELECT
• Wrong JOIN syntax
• Unclosed parenthesis
• Reserved keyword as column name

Solutions:

-- ❌ Wrong
SELECT
  user_id
  event_name  -- Missing comma
FROM events;

-- ✅ Correct
SELECT
  user_id,
  event_name
FROM events;

-- Escape reserved keywords
SELECT `user`, `group` FROM table;

4. Table Not Found (404)

Error:

Not found: Table PROJECT:dataset.table

Solutions:

# Check table exists
bq ls PROJECT:dataset

# Check project/dataset name
bq show PROJECT:dataset.table

# Use fully qualified name
SELECT * FROM `project.dataset.table`;

5. Quota Exceeded (429)