Re: PDB recover fails
Date: Thu, 21 Jan 2021 16:59:45 +0000
Message-ID: <BYAPR07MB5160934180C43E7D62512449E2A10_at_BYAPR07MB5160.namprd07.prod.outlook.com>
This sounds a bit like bug
30549637;AFTER UPGRADE TO 18C MANAGED RECOVERY FAILS Only the bug was fixed in the 19.7 RU and you should see
ORA-600 [KCNIBRUPDATE], [0], [1], [], [], [], [], [], [], [], [], [] We noticed the problem during RMAN duplicate from backup operations where the restore would be fine, but the recovery would fail.
You might want to run
opatch lsinventory | grep 30549637
and see if the bug is listed as being fixed.
Ian A. MacGregor
SLAC IT
SLAC National Accelerator Laboratory
From: oracle-l-bounce_at_freelists.org <oracle-l-bounce_at_freelists.org> on behalf of Seth Miller <sethmiller.sm_at_gmail.com> Sent: Wednesday, January 20, 2021 10:17 PM To: jbeckstrom_at_gcrta.org <jbeckstrom_at_gcrta.org> Cc: Mark W. Farnham <mwf_at_rsiz.com>; Nenad Noveljic <nenad.noveljic_at_gmail.com>; Noveljic Nenad <nenad.noveljic_at_vontobel.com>; Oracle L <oracle-l_at_freelists.org> Subject: Re: PDB recover fails
Is it listed as an incident or problem in the ADR?
On Wed, Jan 20, 2021 at 1:05 PM Beckstrom, Jeffrey <jbeckstrom_at_gcrta.org<mailto:jbeckstrom_at_gcrta.org>> wrote:
YUP. The alert log shows the database files being restored and then jumps to the shutdown where we put os files back.
SPLASHQA(3):Full restore complete of datafile 14 /oradata/splashqa/xxsplash_ind.dbf. Elapsed time: 0:00:28
SPLASHQA(3): checkpoint is 8667671
SPLASHQA(3): last deallocation scn is 1920979
2021-01-20T10:53:59.048619-05:00
SPLASHQA(3):Full restore complete of datafile 13 /oradata/splashqa/xxsplash_tab.dbf. Elapsed time: 0:00:37
SPLASHQA(3): checkpoint is 8667670
SPLASHQA(3): last deallocation scn is 1920979
2021-01-20T10:54:08.124337-05:00
SPLASHQA(3):Full restore complete of datafile 10 /oradata/splashqa/sysaux01.dbf. Elapsed time: 0:00:47
SPLASHQA(3): checkpoint is 8667671
SPLASHQA(3): last deallocation scn is 8616564
2021-01-20T10:54:11.073717-05:00
SPLASHQA(3):Full restore complete of datafile 9 /oradata/splashqa/system01.dbf. Elapsed time: 0:00:49
SPLASHQA(3): checkpoint is 8667670
SPLASHQA(3): last deallocation scn is 2388783
SPLASHQA(3): Undo Optimization current scn is 8665905
2021-01-20T11:06:47.212883-05:00
Shutting down ORACLE instance (immediate) (OS id: 22623)
2021-01-20T11:06:47.213129-05:00
Shutdown is initiated by sqlplus_at_dbsorat12.rta (TNS V1-V3).
2021-01-20T11:06:49.890665-05:00
Stopping background process SMCO
2021-01-20T11:06:50.902063-05:00
Shutting down instance: further logons disabled
2021-01-20T11:06:50.912013-05:00
Stopping background process CJQ0
Stopping background process MMNL
2021-01-20T11:06:51.923447-05:00
Stopping background process MMON
2021-01-20T11:06:53.924323-05:00
alter pluggable database all close immediate
Completed: alter pluggable database all close immediate
2021-01-20T11:06:53.940822-05:00
PDB$SEED(2):JIT: pid 22623 requesting stop
PDB$SEED(2):Buffer Cache flush deferred for PDB 2
License high water mark
From: Mark W. Farnham [mailto:mwf_at_rsiz.com<mailto:mwf_at_rsiz.com>]
Sent: Wednesday, January 20, 2021 1:58 PM
To: Beckstrom, Jeffrey <jbeckstrom_at_gcrta.org<mailto:jbeckstrom_at_gcrta.org>>; 'Nenad Noveljic' <nenad.noveljic_at_gmail.com<mailto:nenad.noveljic_at_gmail.com>>
Cc: 'Noveljic Nenad' <nenad.noveljic_at_vontobel.com<mailto:nenad.noveljic_at_vontobel.com>>; 'Oracle L' <oracle-l_at_freelists.org<mailto:oracle-l_at_freelists.org>>
Subject: RE: PDB recover fails
and you’ve already checked all the various Oracle log and alert areas?
From: oracle-l-bounce_at_freelists.org<mailto:oracle-l-bounce_at_freelists.org> [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Beckstrom, Jeffrey
Sent: Wednesday, January 20, 2021 1:26 PM
To: Nenad Noveljic
I don't think it is the env. We first ran restoere pluggable database …. and that worked
The recover pluggable database failed on both a windows client and the linux server itself.
From: Nenad Noveljic [mailto:nenad.noveljic_at_gmail.com]
Sent: Wednesday, January 20, 2021 1:17 PM
To: Beckstrom, Jeffrey <jbeckstrom_at_gcrta.org<mailto:jbeckstrom_at_gcrta.org>>
Cc: Noveljic Nenad <nenad.noveljic_at_vontobel.com<mailto:nenad.noveljic_at_vontobel.com>>; Oracle L <oracle-l_at_freelists.org<mailto:oracle-l_at_freelists.org>>
Subject: Re: PDB recover fails
Should be /var/lib/systemd/coredump on Linux.
Could you post env from the shell where rmam was called?
Von meinem iPhone gesendet
Am 20.01.2021 um 18:54 schrieb Beckstrom, Jeffrey <jbeckstrom_at_gcrta.org<mailto:jbeckstrom_at_gcrta.org>>:
There were no other message other than what I posted. Where would the core dump be located?
From: Noveljic Nenad [mailto:nenad.noveljic_at_vontobel.com]
Sent: Wednesday, January 20, 2021 12:23 PM
To: Beckstrom, Jeffrey <jbeckstrom_at_gcrta.org<mailto:jbeckstrom_at_gcrta.org>>; Oracle L <oracle-l_at_freelists.org<mailto:oracle-l_at_freelists.org>>
Subject: RE: PDB recover fails
P.S. it might be the case, that the RMAN client (not the dedicated server) got the segmentation fault. In this case, you wouldn’t see ORA-7445 in the alert log. Then I would check if the environment variables are set correctly, especially the library path and oracle home. If there is nothing obvious, you can get the call stack from the core dump and post it here.
From: Noveljic Nenad
Hi,
There was a segmentation fault.
ORA-7445 call stack and the error message would be helpful.
Best regards,
Nenad
From: oracle-l-bounce_at_freelists.org<mailto:oracle-l-bounce_at_freelists.org> <oracle-l-bounce_at_freelists.org<mailto:oracle-l-bounce_at_freelists.org>> On Behalf Of Beckstrom, Jeffrey
Sent: Mittwoch, 20. Januar 2021 18:10
Running 19.7. Testing PDB recover.
Datafile restore worked.
When attempting recovery it failed with:
Recovery Manager: Release 19.0.0.0.0 - Production on Wed Jan 20 10:58:04 2021
Version 19.7.0.0.0
Copyright (c) 1982, 2019, Oracle and/or its affiliates. All rights reserved.
connected to target database: CDB01T12 (DBID=3515690584)
connected to recovery catalog database
RMAN> recover pluggable database splashqa until sequence 108 thread 1;
Starting recover at 20-JAN-21
Any ideas as to what is wrong?
Please consider the environment before printing this e-mail.
Bitte denken Sie an die Umwelt, bevor Sie dieses E-Mail drucken.
Important Notice
This message is intended only for the individual named. It may contain confidential or privileged information. If you are not the named addressee you should in particular not disseminate, distribute, modify or copy this e-mail. Please notify the sender immediately by e-mail, if you have received this message by mistake and delete it from your system.
Without prejudice to any contractual agreements between you and us which shall prevail in any case, we take it as your authorization to correspond with you by e-mail if you send us messages by e-mail. However, we reserve the right not to execute orders and instructions transmitted by e-mail at any time and without further explanation.
E-mail transmission may not be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete. Also processing of incoming e-mails cannot be guaranteed. All liability of Vontobel Holding Ltd. and any of its affiliates (hereinafter collectively referred to as "Vontobel Group") for any damages resulting from e-mail use is excluded. You are advised that urgent and time sensitive messages should not be sent by e-mail and if verification is required please request a printed version.
Please note that all e-mail communications to and from the Vontobel Group are subject to electronic storage and review by Vontobel Group. Unless stated to the contrary and without prejudice to any contractual agreements between you and Vontobel Group which shall prevail in any case, e-mail-communication is for informational purposes only and is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction.
The legal basis for the processing of your personal data is the legitimate interest to develop a commercial relationship with you, as well as your consent to forward you commercial communications. You can exercise, at any time and under the terms established under current regulation, your rights. If you prefer not to receive any further communications, please contact your client relationship manager if you are a client of Vontobel Group or notify the sender. Please note for an exact reference to the affected group entity the corporate e-mail signature. For further information about data privacy at Vontobel Group please consult www.vontobel.com<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.vontobel.com%2F&data=04%7C01%7Cjbeckstrom%40gcrta.org%7C05eaac4d3a704d0c00d208d8bd7569f4%7Cebe8e20736ec47f48cb8f5f757605f5d%7C1%7C0%7C637467659293656652%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=xqahHP1BgVnQsUfd4LX2mTtkQ1uPa1oibbJIqW461rw%3D&reserved=0>.
Cc: Noveljic Nenad; Oracle L
Subject: RE: PDB recover fails
Sent: Mittwoch, 20. Januar 2021 18:12
To: 'jbeckstrom_at_gcrta.org<mailto:jbeckstrom_at_gcrta.org>' <jbeckstrom_at_gcrta.org<mailto:jbeckstrom_at_gcrta.org>>; Oracle L <oracle-l_at_freelists.org<mailto:oracle-l_at_freelists.org>>
Subject: RE: PDB recover fails
To: Oracle L <oracle-l_at_freelists.org<mailto:oracle-l_at_freelists.org>>
Subject: PDB recover fails
Segmentation fault (core dumped)
[dbsorat12:/oradata/splashqa:xxxxxxx] $
--
http://www.freelists.org/webpage/oracle-l
Received on Thu Jan 21 2021 - 17:59:45 CET