【故障-ORACLE】GGS_STICK出來大量鎖的問題
SID SERIAL# USERNAME Term Resource Type TAB OWNER ID1 ID2 Lock Held Lock Req. CTIME
------- ------- ---------- ------ -------------------- ---------- -------- -------- -------- -------------- --------------
2592 5045 TRFF_APP CHINA- TOSystem GGS_STICK GGS 106853 1 Row Exclusive 171689
808CF6 99E
2538 16209 SYS pts/0 TOSystem GGS_STICK GGS 106853 1 Row Exclusive 1097
2569 45087 YWXT_USER unknow TOSystem GGS_STICK GGS 106853 1 Row Exclusive 92038 n
2538 16209 SYS pts/0 TOSystem GGS_BF_CAC GGS 106815 1 Row Exclusive 1094 HE
2712 135 YWXT_USER unknow TOSystem GGS_STICK GGS 106853 1 Row Exclusive 88323 n
2517 19239 TRFF_APP unknow TOSystem GGS_STICK GGS 106853 1 Row Exclusive 68628 n
解釋:在metalink上有文章“OGG GGS_STICK getting locked during the DDL Upgrade [ID 1441479.1]”專門處理了這個問題。
Applies to:
Oracle GoldenGate - Version: 11.1.1.1.3 and later [Release: 11.1.1.1 and later ]
Information in this document applies to any platform.
SMON process is holding locks on ggs_stick:
Checking for sessions that are holding locks on Oracle Golden Gate metadata tables ...
The following sessions are holding 1 locks on objects owned by GGS :
INST_ID SID SERIAL# OS_USER USERNAME
---------- ---------- ---------- --------------------------------
PID
------------------------------------
PROGRAM
-----------------------------------------------------------------------------------
2 760 1 oracle
12482
oracle@acctsvcdb2.iad.expertcity
Details of locks being held:
INST_ID SID SERIAL# OBJECT_LOCKED
----------------------------------------------------------------
LOCK_TYPE
------------------------------------
2 760 1 GGS_STICK
TO
BEGIN
*
ERROR at line 1:
ORA-20783:
GoldenGate DDL Replication setup:
*** Disconnect all sessions that are holding locks on Oracle GoldenGate metadata tables, and retry.
ORA-06512: at line 3
GGS_STICK is locked by SMON
We have reported a bug #13825904, where there is an enhancement that will allow the ddl_setup to run without checking the locks. This feature would be added in the latest versions from OGG V11.2.
As a workaround, please modify the params.sql (found in the OGG install location) and include the below, then redo the process of DDL upgrade.
define _skip_lock_check = 'SMON'
define _skip_create_objects = 'TRUE'
** Bouncing the database can also be one of the options to let the locks to be cleared out on source, if this is acceptable.
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/11088128/viewspace-722701/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- 【故障-ORACLE】_NEXT_OBJE Exclusive鎖問題分析OracleOBJ
- tempdb大量閂鎖等待問題分析
- oracle 解鎖的問題Oracle
- oracle鎖表問題Oracle
- oracle 鎖問題的解決Oracle
- 【故障公告】取代 memcached 的 redis 出現問題造成網站故障Redis網站
- 故障解析丨一次死鎖問題的解決
- oracle外來鍵索引解決父表鎖定問題Oracle索引
- Oracle 解決鎖表問題Oracle
- 一個ORACLE死鎖問題的追蹤Oracle
- 操作oracle出現的問題Oracle
- Oracle Rman多通道故障轉移問題分析Oracle
- 解決Oracle死鎖問題步驟Oracle
- oracle安裝出現的問題Oracle
- 解決Oracle中Exp/Imp大量資料處理問題Oracle
- 【故障】“ORACLE使用者被鎖定”故障處理和分析Oracle
- weblogic多資料來源故障轉移問題Web
- 一次oracle行級鎖導致的問題Oracle
- Oracle 10g使用者鎖定的問題Oracle 10g
- Oracle觸發器死鎖問題解決Oracle觸發器
- Oracle死鎖一例(ORA-00060),鎖表導致的業務死鎖問題Oracle
- 檢查Oracle的鎖狀態並清除問題會話Oracle會話
- guava cache大量的WARN日誌的問題分析Guava
- MongoDB建立大量集合測試問題MongoDB
- RAC 鎖管理與鎖問題的定位(二)
- RAC 鎖管理與鎖問題的定位(一)
- Oracle使用者密碼被鎖定導致的故障Oracle密碼
- 測試MySQL鎖的問題MySql
- sql server死鎖的問題SQLServer
- java鎖的問題速通Java
- Oracle資源正忙,要求指定NOWAIT——Oracle解鎖問題OracleAI
- 和外來鍵相關的阻塞和死鎖問題總結
- TSM + Oracle備份出現問題Oracle
- 故障分析 | show processlist 引起的效能問題
- JDBC用ResultSet訪問大量資料時會遇到的問題JDBC
- synchronized鎖重入問題synchronized
- MySQL死鎖問題MySql
- 深入淺出oracle鎖(ZT)Oracle