ORA-01555 say u again
今天客戶詢問出現ora-01555 如何處理:
經典的1555, 哎此錯誤我不知已經回答過多少次了,這次記錄在Space 中,如果再有就讓他們直接看。
[Machine]oerr ora 1555
01555, 00000, "snapshot too old: rollback segment number %s with name \"%s\" too small"
// *Cause: rollback records needed by a reader for consistent read are
// overwritten by other writers
// *Action: If in Automatic Undo Management mode, increase undo_retention
// setting. Otherwise, use larger rollback segments
Why is system raise 1555?
The usual cause of this error is that long-running transactions/queries are occurring within the database at the same time as short online transactions. When the short transactions complete, the rollback segments they have used is up for grabs and can be overwritten. As soon as that area is overwritten, the long-running queries/transactions can no longer maintain a read consistent picture of the data, and they fail with an ORA-1555. It\'s a scheduling problem. Run batch and long-running jobs at off-hours.
Example Scenario:
1.A long running Query (T1) is started.
2.A quick update (T2) is performed and committed on a table that T1 won\'t require for another 20 minutes. When T2 is committed it\'s rollback segment blocks and extents are kept but marked as inactive.
3.Another DML statement is issued (T3). Oracle assigns a rollback segment to T3 using a round robin algorithm. The assigned segment includes the same storage as the one previously used by T2. Thus it overwrites the inactive before-image of T2.
4.T1 now comes to the point in the query where it needs the before-image of the data that was changed by T2.
5.But T1 must read the before-image of the changed data records (for read consistency). [Page]
6.T1 attempts to read the before-image left from T2 -- only to find that it has been overwritten by T3.
7.T1 can no longer access the before-image of T2. T1 abends at this point.
8.ORACLE then issues: ORA-1555: snapshot too old (rollback segment too small).
How to handle it (Lis Li Said):
1: increate undo_retention
2:increate undo tablespace size
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/34596/viewspace-600576/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- ASSM AgainSSMAI
- Say "Hello tomorrow" with GoGo
- Leetcode Count and SayLeetCode
- LeetCode:Count and SayLeetCode
- 『杭電1848』Fibonacci again and againAI
- On MySQL replication, again…MySqlAI
- Leetcode 38 Count and SayLeetCode
- Leetcode-Count and SayLeetCode
- Count and Say leetcode javaLeetCodeJava
- HDU 1848 Fibonacci again and again(SG函式)AI函式
- ORA-01555——理解
- ERROR:ORA-01555Error
- Make U-Nets Great Again!北大&華為提出擴散架構U-DiT,六分之一算力即可超越DiTAI架構
- 初入 Vue 的世界 Say HelloVue
- Say goodbye to my photos&videosGoIDE
- leetcode刷題--Count and SayLeetCode
- If I were a boy againAI
- Decade counter againAI
- Trees and XOR Queries AgainAI
- 【ORA-01555】Oracle LOB欄位匯出 報錯 ORA-01555Oracle
- Oracle的ORA-01555Oracle
- ORA-01555 總結
- HDU 1848 Fibonacci again and again (尼姆博弈+sg函式)AI函式
- Oracle active dataguard ORA-01555Oracle
- 【故障處理】ORA-01555
- Ora-01555問題分析
- ORA-01555錯誤分析
- NYOJ 480 Fibonacci Again!AI
- Again, a chinese char conversion problemAI
- WEEK5|WEB Unserialize AgainWebAI
- ORA-01555 caused by SQL statement belowSQL
- ORA-01555 問題分析(轉)
- ORA-01555故障解決案例
- ORA-01555錯誤詳解
- suffice it to say 一言以蔽之
- iOS 和常見的離屏渲染Say Goodbye!iOSGo
- [LeetCode] Count and Say 計數和讀法LeetCode
- Use of Indexes Against Views (179)IndexAIView