That’s some timing you’ve got there.
There are ANYDATA datatypes inside that BIND_LIST column. We just fixed a bug with this about an hour ago.
It should be fixed in the GA, and if we have another beta (not including today’s), it should work there too.
As a workaround, do this:
SELECT SQL_ID, FORCE_MATCHING_SIGNATURE, SQL_TEXT, OBJECT_LIST, BIND_DATA, PARSING_SCHEMA_NAME, MODULE, ACTION, ELAPSED_TIME, CPU_TIME, BUFFER_GETS, DISK_READS, DIRECT_WRITES, ROWS_PROCESSED, FETCHES, EXECUTIONS, END_OF_FETCH_COUNT, OPTIMIZER_COST, OPTIMIZER_ENV, PRIORITY, COMMAND_TYPE, FIRST_LOAD_TIME, STAT_PERIOD, ACTIVE_STAT_PERIOD, OTHER, PLAN_HASH_VALUE, SQL_PLAN, CON_DBID
FROM TABLE (DBMS_SQLTUNE.select_workload_repository (
begin_snap => 31771,
end_snap => 31777,
basic_filter => ‘parsing_schema_name not in (’‘DBSNMP’’,’‘SYS’’,’‘ORACLE_OCM’’)’,
ranking_measure1 => ‘elapsed_time’,
result_limit => 250));