truncating table involved in long running rollback
From: Laurentiu Oprea <laurentiu.oprea06_at_gmail.com>
Date: Tue, 8 Dec 2020 22:43:26 +0200
Message-ID: <CA+riqSWc1gWeSj-2Gw3PrZiYujCMQJwXzePA+6fo61ssJuMuYA_at_mail.gmail.com>
Hello everyone,
Date: Tue, 8 Dec 2020 22:43:26 +0200
Message-ID: <CA+riqSWc1gWeSj-2Gw3PrZiYujCMQJwXzePA+6fo61ssJuMuYA_at_mail.gmail.com>
Hello everyone,
I need some help in order to understand a situation. I had an update statement on a table that for various reasons I needed to kill the session.
Smon started to take care of recovery I could see the active action by querying v$fast_start_transactions;
Because the table was a staging table part of and ODI job
and because ETA for recovery was 25
hours (very suspicions this is something I need to investigate) I decided to
truncate the table to release the locks and restart the job.
But after truncate the rollback still continued to run behind the scenes. Even so apparently the locks were release from the table.
Is it expected to have the recovering running after truncate?
Version: 12.1.0.2
Thank you.
-- http://www.freelists.org/webpage/oracle-lReceived on Tue Dec 08 2020 - 21:43:26 CET