Last updated on NOVEMBER 22, 2016
Applies to:Oracle Database - Enterprise Edition - Version 10.1.0.2 to 184.108.40.206 [Release 10.1 to 11.2]
Information in this document applies to any platform.
- Startup or alter database open hangs after loading plan baselines from sqlset from 10gr2 to 11gr2. Plans were loaded from AWR in 10.2.0.5 version, packed and table exported.
- "ORA-44203: timeout waiting for lock on cursor" is seen in the alert log file.
- Making optimizer_use_sql_plan_baselines='FALSE' restores the DB back to normal.
DB upgraded to 11gr2 and the table imported, plan unpacked and loaded to sqlset baseline.The following procedure was followed :-
Load STS from AWR baseline in 10.2.0.5:
start_snap_id => 24390,
end_snap_id => 24402,
baseline_name => 'system_baseline');
OPEN baseline_cursor FOR
FROM TABLE (DBMS_SQLTUNE.SELECT_WORKLOAD_REPOSITORY(
'system_baseline', NULL, NULL, 'elapsed_time', NULL,
NULL, NULL, 10)) p;
sqlset_name => '11upgrade',
populate_cursor => baseline_cursor);
Pack the STS and export the staging table:
Create staging table:
Pack STS in to staging table:
Steps in 220.127.116.11:
++ Export the staging file from the 10g Database.
++ Import the staging table into oracle 11g.
Unpack the STS:
Load the execution plan in to sql management base in 18.104.22.168:
plan_cnt := DBMS_SPM.LOAD_PLANS_FROM_SQLSET(sqlset_name => '11upgrade',sqlset_owner=> 'SYS');
dbms_output.put_line('Number of plans loaded: ' || plan_cnt);
Subsequent shut down of the database in 11g and startup would hang the database.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms