RMAN-20003: target database incarnation not found in recovery catalog

podczas zabaw z restorem można trafić na RMAN-20003 (ustawiamy żądanego scn-a):

Starting recover at 2022-05-04 17:50:46
released channel: ch1
released channel: ch2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 05/04/2022 17:50:46
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20003: target database incarnation not found in recovery catalog

RMAN> list incarnation;

using target database control file instead of recovery catalog

List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
——- ——- ——– —————- — ———- ———-
1 1 baza 2326959724 PARENT 1 2017-01-12 13:09:00
2 2 baza 2326959724 CURRENT 6974703964827 2022-05-04 12:39:48

FAL[client]: Failed to request gap sequence

FAL[client]: Failed to request gap sequenceGAP – thread 1 sequence 1778708-1778739DBID x branch xFAL[client]: All defined FAL servers have been attempted. wysypała się replikacja / brakuje archów, jezeli brakuje więcej, to można na bogato odtwarzać (nawet na primary i DG elegancko prześle na standby), albo bawić się w ten sposób: watch -n 2 „tail -n… Czytaj dalej FAL[client]: Failed to request gap sequence

NFS: vmount: Operation not permitted.NFS:

Pacjent: AIX 6.1, podczas montowania:

aix:/# mount dd:/backup /rmandd
mount: 1831-008 giving up on:
dd:/backup
vmount: Operation not permitted.

tymczasowo można obejść problem:

aix:/# nfso -o nfs_use_reserved_ports

Podczas recovery: RMAN-03002, ORA-00283, ORA-19764: database id does not match database id in control file

Recovery interrupted!
Recovered data files to a consistent state at change 1234567890
Media Recovery failed with error 19764
ORA-00283: recovery session canceled due to errors
ORA-19764: database id 67890 does not match database id 12345 in control file
Slave exiting with ORA-283 exception
ORA-10877 signalled during: alter database recover logfile '/arch/file_arch_1234321.arch’…

ORA-24777: use of non-migratable database link not allowed

— aplikacja czasami chce zbyt dużo od klasycznego dblinka i należy zmienić parametry połączenia w samej aplikacji na shared, albo dblink-a

— tworzymy go z opcją shared i dorzucamy authenticated

CREATE SHARED PUBLIC DATABASE LINK podajemy_nazwe_linka
CONNECT TO podajemy_login IDENTIFIED BY "podajemy_haslo"
AUTHENTICATED BY podajemy_login IDENTIFIED BY "podajemy_haslo""
USING '(DESCRIPTION =(ADDRESS = (PROTOCOL = TCP)(HOST = podajemy_hosta)(PORT = 1521)) (CONNECT_DATA = (SERVICE_NAME = podajemy_service_name)))';

ORA-02020: too many database links in use

— jak mamy za dużo otworzonych dblinków i jest to jedynie wybryk natury, to ubijamy (o ile można)

alter session close database link NAZWA_DBLINKA;
exec dbms_session.close_database_link (’NAZWA_DBLINKA’);

— a jak mamy zbyt mało, sprawdzamy:

show parameter open_links
open_links integer 4
open_links_per_instance integer 4

— zmieniamy parametry i przekręcamy db

alter system set open_li…

RDS Oracle DB REDO dodanie, usuniecie itd.

— dodanie plikow

EXEC rdsadmin.rdsadmin_util.add_logfile(p_size => '500M’);
EXEC rdsadmin.rdsadmin_util.add_logfile(p_size => '500M’);
EXEC rdsadmin.rdsadmin_util.add_logfile(p_size => '500M’);
EXEC rdsadmin.rdsadmin_util.add_logfile(p_size => '500M’);

— switchlog-a

EXEC rdsadmin.rdsadmin_util.switch_logfile;

— checkpoint

EXEC rdsadmin.rdsadmin_util.checkpoint;

— drop starych

EXEC rdsadmin.rdsadmin_util.drop_logfile(grp => 1);
EXEC rdsadmin.rdsadmin_util.drop_logfile(grp => 2);