Iam using Teradata 14.x. I come from Oracle background. In Oracle, there are data dictionay views to look at
explain plan" when query was actually exceuted which can be different from plan generated using explain plan statement. Which dbc tables/viewsexcution time explain plan is stored in Teradata.
In oracle it is different and here it is different. You can have a look at DBC.DBQLExplainTbl . Also have a look at DBQLXMLTbl. I hope this is what you are looking for.
There will be no difference between an EXPLAIN and actually running the query.
If you want to see the actual resource usage (CPU/IO/spool/etc.) you must check DBQL, especially dbc.QryLogStepsV (if it's enabled) which shows actual vs. estimated row counts & runtime.