Skip to content

Getting INTERNAL_ERROR_QUERY_ENGINE while trying to run msck repair table

0
  1. Created table using CREATE EXTERNAL TABLE daily_wallet_dlr_new( transactiondate bigint, walletid string, appname string, app_id string, sku string, source_phone_number string, destination_phone_number string, countrycode string, countryname string, amount string, currency string, hr string) PARTITIONED BY ( yr int, mth int, day int, wabanumber string) ROW FORMAT SERDE 'org.apache.hadoop.hive.ql.io.parquet.serde.ParquetHiveSerDe' STORED AS INPUTFORMAT 'org.apache.hadoop.hive.ql.io.parquet.MapredParquetInputFormat' OUTPUTFORMAT 'org.apache.hadoop.hive.ql.io.parquet.MapredParquetOutputFormat' LOCATION 's3://gsbiml-crystal-ball-prod/prod-wallet/walletDLR' TBLPROPERTIES ( 'parquet.compression'='SNAPPY', 'transient_lastDdlTime'='1712731575')
  2. msck repair table daily_wallet_dlr_new
  3. Getting the error: Amazon Athena experienced an internal error while executing this query. Please try submitting the query again and if the issue reoccurs, contact AWS support for further assistance. We apologize for the inconvenience. This query ran against the ‘bot_platform’ database, unless qualified by the query. Please post the error message on our forum or contact customer support with Query ID: a92dedeb-4915-4f58-ac6e-6d430323a15f
asked 2 years ago384 views
2 Answers
1

Hi Diksha,

Amazon Athena while trying to run the msck repair table command on your daily_wallet_dlr_new table.

Let's Solve the issue in simple way:

  • Retry the Query: Sometimes, internal errors can be transient. Try rerunning the msck repair table daily_wallet_dlr_new query.
  • Check Athena Service Status: Visit the AWS Service Health Dashboard (https://docs.aws.amazon.com/health/latest/ug/aws-health-dashboard-status.html) and check for any reported issues with Athena in your region.
  • Analyze the Table: Use the MSCK REPAIR TABLE command with the VALIDATE option to get more detailed information about potential errors with the table. The command would look like this:
MSCK REPAIR TABLE daily_wallet_dlr_new VALIDATE;
  • Check Table Properties: Ensure that the table properties like parquet.compression are set correctly. In your case, the compression is set to 'SNAPPY'. You can find the documentation for supported table properties here: https://hive.apache.org/
  • Reduce the Scope of Repair: If the entire table repair fails, try running the MSCK REPAIR TABLE command on a specific partition of the table. This can help isolate the issue if it's confined to a particular partition.
EXPERT
answered 2 years ago
  • hi, thanks for the answer. But I have tried running the query multiple times, but I had no luck. And there are around 1000 partitions for everyday, so I cannot do that partition thing.

0
MSCK REPAIR TABLE daily_wallet_dlr_new VALIDATE;

doesn't work for me.

line 1:1: mismatched input 'MSCK'. Expecting: 'ALTER', 'ANALYZE', 'CALL', 'COMMENT', 'COMMIT', 'CREATE', 'DEALLOCATE', 'DELETE', 'DENY', 'DESC', 'DESCRIBE', 'DROP', 'EXECUTE', 'EXPLAIN', 'GRANT', 'INSERT', 'MERGE', 'PREPARE', 'REFRESH', 'RESET', 'REVOKE', 'ROLLBACK', 'SET', 'SHOW', 'START', 'TRUNCATE', 'UNLOAD', 'UPDATE', 'USE', <query>
answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.