sql >> Database >  >> RDS >> Database

ZDLRA – RMAN-20035 ongeldige hoge RECID

Fout "RMAN-20035:ongeldige hoge RECID ” bij het uitvoeren van RMAN-back-up op beveiligde database met behulp van ZDLRA:


# rman target / catalog /@zdlra01-scan:1521/zdlra

Recovery Manager: Release 12.1.0.2.0 - Production on Mon Sep 3 09:06:21 2021

Copyright (c) 1982, 2014, Oracle and/or its affiliates. All rights reserved.

connected to target database: CDBSIV01 (DBID=2462007622)
connected to recovery catalog database
recovery catalog schema release 21.01.00.00. is newer than RMAN release

RMAN> backup device type sbt tag 'BACKUP_ZDL_ARCH' archivelog all not backed up delete all input;

Starting backup at 03-SEP-21
current log archived
allocated channel: ORA_SBT_TAPE_1
channel ORA_SBT_TAPE_1: SID=300 device type=SBT_TAPE
channel ORA_SBT_TAPE_1: RA Library VER=12.2.0.1
allocated channel: ORA_SBT_TAPE_2
channel ORA_SBT_TAPE_2: SID=554 device type=SBT_TAPE
channel ORA_SBT_TAPE_2: RA Library VER=12.2.0.1
allocated channel: ORA_SBT_TAPE_3
channel ORA_SBT_TAPE_3: SID=306 device type=SBT_TAPE
channel ORA_SBT_TAPE_3: RA Library VER=12.2.0.1
allocated channel: ORA_SBT_TAPE_4
channel ORA_SBT_TAPE_4: SID=175 device type=SBT_TAPE
channel ORA_SBT_TAPE_4: RA Library VER=12.2.0.1
skipping archived logs of thread 1 from sequence 48371 to 48378; already backed up
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 09/03/2021 10:28:06
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20035: invalid high RECID

Oplossing:probleem wordt opgelost door de onderstaande opdrachten uit te voeren naar de zdlra-database:

Back-up uitvoeren met foutopsporing ingeschakeld:

# rman target / catalog /@zdlra01-scan:1521/zdlra debug=ALL log=/tmp/rmandebug.txt
RMAN> backup device type sbt tag 'BACKUP_ZDL_ARCH' archivelog all not backed up delete all input;
RMAN>

Zoek de waarden van bphwm en bshwm in de gegenereerde debug rmandebug.txt bestand:

DBGSQL:RCVCAT> begin :resync :=dbms_rcvcat.ckptNeeded(ckp_scn => :cfscn, ckp_cf_seq => :cfseq, cf_version => :vertime, cf_type => :cftype, high_df_recid => sqlcode =20035
DBGSQL:B :resync =NULL
DBGSQL:B:cfscn =13930161892388
DBGSQL:B:cfseq =7912622
DBGSQL:B:vertime =“27 mei -2017 14:29:51”
DBGSQL:B :cftype =1
DBGSQL:B :dfhwm =616
DBGSQL:B :tshwm =11
DBGSQL:B :rlhwm =54
DBGSQL:B :dchwm =0
DBGSQL:B:alhwm =54333
DBGSQL:B:bphwm =11482
DBGSQL:B:dohwm =54297
DBGSQL:B:offrhwm =0
DBGSQL:B:pchwm =0
DBGSQL:B:rmhwm =19
DBGSQL:B :rltime =“27-mei-2017 14:29:54”
DBGSQL:B :bshwm =11120
DBGSQL:B :lrstscn =2712589
DBGSQL:B :lrsttime =“27-mei-2017 14:29:54”
DBGSQL:B :ichwm =2
DBGSQL:B :tfhwm =33182
DBGSQL:B :rthwm =0
DBGSQL:B :grsphwm =0
DBGSQL:B :nrsphwm =0
DBGSQL:B :bcrhwm =0
DBGSQL:B :pdbhwm =0
DBGSQL:B:pichwm =0
DBGSQL:fout:ORA-20035:Ongeldige hoge recid:high_bp_recid (krmkosqlerr)
DBGSQL:ORA-06512 :op “RASYS.DBMS_RCVCAT”, regel 5609 (krmkosqlerr)
DBGSQL:ORA-06512:op “RASYS.DBMS_RCVCAT”, regel 5469 (krmkosqlerr)
DBGSQL:ORA-06512:op regel 1 (krmkosqlerr )
DBGSQL:(krmkosqlerr)
DBGSQL:VERLATEN krmkosqlerr
DBGMISC:krmksqlerror aangeroepen vanuit bestand krmk7.c, regel 5177 [13:25:41.708]

Log in op de zdlra-database en voer de sqls uit:

[oracle@zdra01db02 ~]$ sqlplus / as sysdba

SQL*Plus: Release 19.0.0.0.0 - Production on Mon Sep 3 09:19:19 2021
Version 19.9.0.0.0

Copyright (c) 1982, 2020, Oracle. All rights reserved.

Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.9.0.0.0

SQL> select SITE_KEY,db_key,DB_UNIQUE_NAME from RASYS.RCI_SITE where DB_UNIQUE_NAME = 'CDBSIV01';

SITE_KEY DB_KEY DB_UNIQUE_NAME
---------- ---------- ------------------------------------------------------------------------------------------------------------------------
353605282 353605280 CDBSIV01

HIGH_BP_RECID bijwerken en HIGH_BS_RECID naar beveiligde database CDBSIV01 (DB_KEY =353605280 en site_key =353605282):


SQL> update RASYS.pdb_node set HIGH_BP_RECID = 11482 where site_key = 353605282 and DB_KEY = 353605280;

1 row updated.

SQL> update RASYS.pdb_node set HIGH_BS_RECID = 11120 where site_key = 353605282 and DB_KEY = 353605280;

1 row updated.

SQL> commit;

Commit complete.

Log in op de beveiligde database en verzend een back-up:


# rman target / catalog /@zdlra01-scan:1521/zdlra

Recovery Manager: Release 12.1.0.2.0 - Production on Mon Sep 3 10:10:21 2021

Copyright (c) 1982, 2014, Oracle and/or its affiliates. All rights reserved.

connected to target database: CDBSIV01 (DBID=2462007622)
connected to recovery catalog database
recovery catalog schema release 21.01.00.00. is newer than RMAN release

RMAN> backup device type sbt tag 'BACKUP_ZDL_ARCH' archivelog all not backed up delete all input;

Starting backup at 03-SEP-21
current log archived
allocated channel: ORA_SBT_TAPE_1
channel ORA_SBT_TAPE_1: SID=137 device type=SBT_TAPE
channel ORA_SBT_TAPE_1: RA Library VER=12.2.0.1
allocated channel: ORA_SBT_TAPE_2
channel ORA_SBT_TAPE_2: SID=31 device type=SBT_TAPE
channel ORA_SBT_TAPE_2: RA Library VER=12.2.0.1
allocated channel: ORA_SBT_TAPE_3
channel ORA_SBT_TAPE_3: SID=145 device type=SBT_TAPE
channel ORA_SBT_TAPE_3: RA Library VER=12.2.0.1
allocated channel: ORA_SBT_TAPE_4
channel ORA_SBT_TAPE_4: SID=317 device type=SBT_TAPE
channel ORA_SBT_TAPE_4: RA Library VER=12.2.0.1
skipping archived log of thread 1 with sequence 49711; already backed up
channel ORA_SBT_TAPE_1: starting archived log backup set
channel ORA_SBT_TAPE_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=49712 RECID=55651 STAMP=1085043984
channel ORA_SBT_TAPE_1: starting piece 1 at 03-SEP-21
channel ORA_SBT_TAPE_1: finished piece 1 at 03-SEP-21
piece handle=db_CDBSIV01xxxx_p00aot8j_1_1 tag=BACKUP_ZDL_ARCH comment=API Version 2.0,MMS Version 12.2.0.1
channel ORA_SBT_TAPE_1: backup set complete, elapsed time: 00:00:01
Finished backup at 03-SEP-21

Starting Control File and SPFILE Autobackup at 03-SEP-21
piece handle=c-2462007622-20211004-09 comment=API Version 2.0,MMS Version 12.2.0.1
Finished Control File and SPFILE Autobackup at 03-SEP-21

RMAN>
 


  1. SQL - Opgeslagen procedure aanroepen voor elk record

  2. Analyse van MS SQL Server voor degenen die het voor het eerst zien

  3. Wat is SQL Server RAISERROR?

  4. Aan de slag met MariaDB met Docker, Java Spring en JDBC