10g升級至11g需要考慮的引數優化

jeanron100發表於2013-07-13
優化

10g升級至11g除了需要做一個詳盡的計劃，

需要採集10g系統的負載情況，做一個整體的把握，在升級之後，再做負載分析。

保證不會出現大的問題，sql的執行計劃不會有大的變動。

引數優化方面，需要考慮下面3個方面。


à對於 deprecated Parameter in 11G

The following parameters are deprecated from 11G onwards, need suggestion for these parameters.

Name

Note

 

 

background_dump_dest

Replaced by DIAGNOSTIC_DEST

/xxxx/oracle/xxxxDB01/oradmp/bdump/

/xxxxx/oracle/xxxxDB02/oradmp/bdump/

cursor_space_for_time

 

FALSE

FALSE

fast_start_io_target

 

0

0

log_archive_local_first

 

TRUE

TRUE

log_archive_start

 

FALSE

FALSE

max_enabled_roles

 

150

150

parallel_automatic_tuning

 

FALSE

FALSE

parallel_server

 

FALSE

FALSE

parallel_server_instances

 

1

1

plsql_debug

Replaced by PLSQL_OPTIMIZE_LEVEL

FALSE

FALSE

plsql_v2_compatibility

 

FALSE

FALSE

remote_os_authent

 

FALSE

FALSE

serial_reuse

 

disable

disable

sql_trace

 

FALSE

FALSE

standby_archive_dest

 

?/dbs/arch

?/dbs/arch

user_dump_dest

 

/xxxxx/oracle/xxxxDB01/oradmp/udump/

/xxxxx/oracle/xxxxDB02/oradmp/udump/

à對於 11G 新引數

Name

Value

OL Change

Note

sec_case_sensitive_logon

FALSE

Yes

to disable password case sensitive

sec_max_failed_login_attempts

10

No

Need to set realistic value as per Site Security policy. Default is 10

result_cache_max_size

?

Yes

To use result cache feature. Can increase the memory size when it is required.

deferred_segment_creation

FALSE

Yes

Make consistent for the object in the dictionary

 diagnostic_dest

 

Yes

 Replacement for udump/bdump directorires

db_unrecoverable_scn_tracking

TRUE

_optimizer_cost_model

choose

Yes

_like_with_bind_as_equality

TRUE

Yes

 

 

 

 

 

 

à對於10g中已經優化的引數。

below parameters are existing in production now, need suggestions if need to tune.

_optimizer_cost_model

parallel_execution_message_size

_optim_peek_user_binds

_db_block_numa

_ksmg_granule_size

_kghdsidx_count

_enable_numa_optimization

......


來自 “ ITPUB部落格 ” ，連結：http://blog.itpub.net/23718752/viewspace-766201/，如需轉載，請註明出處，否則將追究法律責任。

相關文章