Sometimes the fix may not repair the block for an already existent invalid SCN on disk; then repair this issue with: 1. Share this: Twitter Facebook. Like this: Like Loading Published by heemasatapathy.
Leave a Reply Cancel reply Enter your comment here Fill in your details below or click an icon to log in:. Email required Address never made public. Name required. Follow Following. You should specify a value for maxextents that is less than for your rollback segments and DO NOT use the unlimited specifier.
Explanation: ———— You may have encountered [BUG]. There is an undocumented limitation on the maxextents you can have on a rollback segment. When you use the unlimited qualifier in your rollback segment it may exceed the limit and cause the ORA[]. The db is continuously generating ORA internal error code, arguments: [], [], [], [], [], [], [], []. According to oracle support site, this sounds like corrupt undo information which is preventing the rollback.
Yes this is a corrupt undo segment. I faced a similar problem a few months back but that was on a desupported oracle 7. Oracle suggested that once we extract the data out of the object that is blocking the undo we recreate the DB.
But since you are on a supported platform i. But you be prepared to rebuild the DB just in case after recovery. Mail — MB free storage. Do more. Manage less. I have upgrade Oracle from 8. No redistribution. Version: 7. This is a known bug and is fixed in 8. Patch Bundle 29, a direct replacement for Patch Bundle 28 has been released by Oracle, but has not been certified by Symantec DLP and will not be made available.
Patch Bundle 30 has been certified and is readily available. Oracle CPU Patches are cummulative. By applying the latest patch, all prior fixes are applied a well. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
0コメント