A caution -- in case you are asking about in-flight JDBC/ODBC/etc. parameterized queries that you want to explain using a separate session and/or a separate tool like BTEQ.
If you simply substitute query parameter values back into the SQL request text as hardcoded literals you may get an explain that is quite different from the plan used with the parameter values.
Also, the database may execute the SQL request differently depending on driver-specific connection parameters, such as whether LOB support is enabled, which session character set is used, etc.
A caution -- in case you are asking about in-flight JDBC/ODBC/etc. parameterized queries that you want to explain using a separate session and/or a separate tool like BTEQ.
If you simply substitute query parameter values back into the SQL request text as hardcoded literals you may get an explain that is quite different from the plan used with the parameter values.
Also, the database may execute the SQL request differently depending on driver-specific connection parameters, such as whether LOB support is enabled, which session character set is used, etc.