GRANT EXECUTE ON DBMS_LOCK TO DDQCG;

grant execute on dbms_crypto to DDQCG;

exec dbms_utility.compile_schema( 'DD' );

for cancelling standby aplying after swtich log file run below command

ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;

SELECT FIRST_TIME,NEXT_TIME,STANDBY_DEST,SEQUENCE#,NAME FROM V$ARCHIVED_LOG ORDER

BY FIRST_TIME DESC;

Exec DBMS_STATS.GATHER_SCHEMA_STATS('SEOQCG');

Thanks for the suggestions so far. This is what I got back from my vendor. It is
possibly due to an unpublished Bug 7330813 that has to do with Function Based
Indexes. This bug is fixed in 11.2.

-Unpublished Bug 7330813 deails

CBO may incur high hard parse times (as compared to 10g) for queries involving
Tables with functional indexes.
This Fix complements the fix for unpublished bug 6194582.
Workaround:
Set "_replace_virtual_columns"=false;

I have set the above parameter so we will see if it helps. Keep in mind that Oracle
says not to use this Initialization parameter unless told to do so by Oracle
Support.

alter system set "_gby_hash_aggregation_enabled" = FALSE scope=both;