sources | solution | error |
---|---|---|
metalink Doc ID 756799.1 | as per metalink Doc ID 756799.1 this is due Bug 6767655 and fixed in 10.2.0.5 (Server Patch Set) And the Workaround is Avoid concurrent DML and index rebuild online. Serialize these operations |
ORA-07445: exception encountered: core dump [kauxs_do_journal()+4] [SIGSEGV] [Address not mapped to object] [0x000000002] [] [] |
(Doc ID 293002.1) | cause ~~~~~~~~ The "UPGRADE CATALOG" step list in the patch or patchset readme was not submitted. This could leave the recovery catalog schema in a version lower than 9.2.0.4.0. Fix ~~~~~ Connect to the target and the catalog database then run "UPGRADE CATALOG". Re-enter "UPGRADE CATALOG" a second time when prompted. If "RESYNC CATALOG" then runs without errors the issue should be resolved. resync catalog; RMAN> upgrade catalog; # twice to confir |
RMAN-03014 implicit resync of recovery catalog failed |
Doc ID 1312448.1 |
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on B1 channel at 10/26/2014 12:56:48
ORA-19513: failed to identify sequential file
ORA-27206: requested file not found in media management catalog
|
الاثنين، 20 أبريل 2015
some oracle errors
الاشتراك في:
تعليقات الرسالة (Atom)
ليست هناك تعليقات:
إرسال تعليق