Oracle undo_management参数不一致错误

来源:http://www.dnamique.com 作者:计算机网络 人气:77 发布时间:2020-05-04
摘要:条件Linux 5.8,四个节点只可以一个节点mount,纵然尝试mount其它节点就报ORA-01105和ORA-01606不当数据库版本复制代码 代码如下:SQL select * from v$version;BANNEVision GT ---------------------------

条件Linux 5.8 RAC,四个节点只可以一个节点mount,纵然尝试mount其它节点就报ORA-01105和ORA-01606不当数据库版本复制代码 代码如下:SQL select * from v$version; BANNEVision GT ---------------------------------------------------------------- Oracle Database 10g Enterprise Edition Release - 64bi PL/SQL Release - Production CORE Production TNS for Linux: Version - Production NLSRTL Version - Production crs财富景况复制代码 代码如下:[oracle@node1 dbs]$ $ORA_CRS_HOME/bin/crs_stat -t Name

Type Target State Host

ora....D1.inst application OFFLINE OFFLINE ora....D2.inst application ONLINE ONLINE node2 ora.PROD.db application ONLINE ONLINE node2 ora....SM1.asm application ONLINE ONLINE node1 ora....E1.lsnr application ONLINE ONLINE node1 ora.node1.gsd application ONLINE ONLINE node1 ora.node1.ons application ONLINE ONLINE node1 ora.node1.vip application ONLINE ONLINE node1 ora....SM2.asm application ONLINE ONLINE node2 ora....E2.lsnr application ONLINE ONLINE node2 ora.node2.gsd application ONLINE ONLINE node2 ora.node2.ons application ONLINE ONLINE node2 ora.node2.vip application ONLINE ONLINE node2节点1 mount报错复制代码 代码如下:SQL startup ORACLE instance started. Total System Global Area 17壹玖陆柒464 bytes Fixed Size 2094832 bytes Variable Size 113248528 bytes Database Buffers 50331648 bytes Redo Buffers 6291456 bytes ORA-01105: mount is incompatible with mounts by other instances ORA-01606: gc_files_to_locks not identical to that of another mounted instanceError: ORA 1105 Text: mount is incompatible with

mounts by other instances

Cause: An attempt was made to mount the database, but another instance has already mounted a database by the same name, and the mounts are not compatible. dditional messages will accompany this message to report why the mounts are incompatible. Action: See the accompanying messages for the appropriate action to take. Error: ORA 1606 Text:

GC_FILES_TO_LOCKS not identical to that of another mounted instance

Cause: The initialization parameter GC_FILES_TO_LOCKS is not the same as another instance mounted in parallel mode. This parameter must be the same as that for all shared instances. Action: Modify the parameter to be compatible with the other instances, then shut down and restart the instance.根据那些荒谬提醒,查询四个节点的gc_files_to_locks参数,均为空值(暗中同意值卡塔尔,也正是值相似复制代码 代码如下:SQL show parameter gc_files_to_locks; NAME TYPE VALUE

------------------------------ gc_files_to_locks

string检查多个节点的gc相关隐含参数,发掘装有值也均一致复制代码 代码如下:NAME DESC福睿斯IPTION VALUE

------- _gc_affinity_limit dynamic affinity limit 50 _gc_affinity_minimum dynamic affinity minimum activity per minute 6000 _gc_affinity_time if non zero, enable dynamic object affinity 10 _gc_async_memcpy if TRUE, use async memcpy FALSE _gc_check_bscn if TRUE, check for stale blocks TRUE _gc_coalesce_recovery_reads if TRUE, coalesce recovery reads TRUE _gc_defer_time how long to defer down converts for hot buffers 3 _gc_dissolve_undo_affinity if TRUE, dissolve undo affinity after an offline FALSE _gc_dynamic_affinity_locks if TRUE, get dynamic affinity locks TRUE _gc_element_percent global cache element percent 103 _gc_global_lru turn global lru off, make it automatic, or turn it on AUTO _gc_initiate_undo_affinity if TRUE, initiate undo affinity after an online TRUE _gc_integrity_checks set the integrity check level 1 _gc_keep_recovery_buffers if TRUE, make recovery buffers current TRUE _gc_latches number of latches per LMS process 8 _gc_maximum_bids maximum number of bids which can be prepared 0 _gcs_fast_reconfig if TRUE, enable fast reconfiguration for gcs locks TRUE _gcs_latches number of gcs resource hash latches to be allocated per LMS process 64 _gcs_pkey_history number of pkey remastering history 4000 _gcs_process_in_recovery if TRUE, process gcs requests during instance recovery TRUE _gcs_resources number of gcs resources to be allocated _gcs_shadow_locks number of pcm shadow locks to be allocated _gc_statistics if TRUE, kcl statistics are maintained TRUE _gcs_testing GCS testing parameter 0 _gc_tsn_undo_affinity if TRUE, use TSN undo affinity TRUE _gc_undo_affinity if TRUE, enable dynamic undo affinity TRUE _gc_undo_affinity_locks if TRUE, get affinity locks for undo TRUE _gc_use_cr if TRUE, allow CR pins on PI and WRITING buffers TRUE _gc_vector_read if TRUE, vector read current buffers TRUE留心比较数据库参数,发掘undo十分复制代码 代码如下:--节点1 SQL show parameter undo NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ undo_management string MANUAL undo_retention integer 900 undo_tablespace string SYSTEM --节点2 SQL show parameter undo NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ undo_management string AUTO undo_retention integer 900 undo_tablespace string UNDOTBS1这里一度闻名遐尔,因为四个节点的undo_*连带参数配置不科学,导致数据库只好一个节点mount。进一层定位难题发掘,原本是因为dba疏忽在编制节点1的参数文件的时候把undo_*有关的参数给弄丢了,从而数据库使用了私下认可值undo_management=manual,undo_tablespace=system

本文由8535.com-新浦京娱乐场官网|欢迎您发布于计算机网络,转载请注明出处:Oracle undo_management参数不一致错误