Cache Lookup Failed for Relation OID 104865841 - Suspected Catalog Corruption

Question

Description:
We are encountering a persistent error in our Amazon Redshift cluster when attempting to drop a view (src.de_application__subscription_status_history). The error message cache lookup failed for relation 104865841 points to a system catalog issue, potentially caused by an orphaned or corrupted catalog entry. We have attempted several steps (outlined below), but the issue remains unresolved.

ERROR:  cache lookup failed for relation 104865841

Request:
We believe the system catalog may be corrupted and requires manual intervention to repair or remove the orphaned entry. Please investigate the issue and assist in cleaning up the system catalog to resolve the error.

Thank you for your assistance.

Aaron Rose · Answer

Hi gopalfreddies,

### Clarifying the Issue
The error **"Cache Lookup Failed for Relation OID 104865841"** suggests **system catalog corruption**, possibly from orphaned or inconsistent metadata entries during operations like `DROP VIEW`. Here’s a step-by-step approach to resolve it:

1. **Restart the Cluster**:  
   Start with a simple reboot of your Redshift cluster. This often resolves transient catalog issues and refreshes the system state.  
   - Go to your **Amazon Redshift Console** → Select the cluster → Actions → **Reboot**.

2. **Use the CASCADE Option**:  
   If the error appears while dropping a view, try modifying your `DROP VIEW` command:  
   ```sql
   DROP VIEW src.de_application__subscription_status_history CASCADE;
   ```  
   This removes dependent objects, which may resolve the corruption issue.

3. **Perform a Classic Resize**:  
   Performing a non-elastic resize forces Redshift to rebuild the system catalog.  
   - In the **Redshift Console**, navigate to your cluster, choose **Resize**, and select a non-elastic option.

4. **Restore from a Snapshot**:  
   If the catalog corruption persists, restoring the cluster from the latest automated snapshot may help.  
   - Steps: Go to **Snapshots** → Select a valid snapshot → Choose **Restore**.

5. **Engage AWS Support**:  
   If none of the above steps resolve the issue, you’ll need AWS Support for a deeper investigation. This may require manual catalog repair, which AWS engineers can assist with. Include error logs and the exact commands you’re running to expedite troubleshooting.

Cheers, Aaron 😊

Cache Lookup Failed for Relation OID 104865841 - Suspected Catalog Corruption

Clarifying the Issue

Add your answer

Relevant content