CRS-2883: Resource 'ora.gpnpd’ failed during Clusterware stack start (grid 12.1.0.2)

Przy starcie crs-a może być lipa w postaci:
CRS-2883: Resource 'ora.gpnpd’ failed during Clusterware stack start

sprawdzamy loga /u01/app/grid/diag/crs/host1/crs/trace/gpnpd.trc

default:804535872: gpnpd START pid=32479 Oracle Grid Plug-and-Play Daemon
default:804535872: clsgpnpd_main instance started
GPNP:804535872: clsgpnp_Init: [at clsgpnp0.c:659] '/u01/app/12.1.0.2/grid’ in effect as GPnP home base.
GPNP:804535872: clsgpnp_Init: [at clsgpnp0.c:713] GPnP pid=32479
CLSDMT:663672576: PID for the Process [32479], connkey 10
CLSDMT:663672576: Error3 -2 writing PID [32479] to the file []
CLSDMT:663672576: Failed to record pid for GPNPD
CLSDMT:663672576: Terminating process
GPNP:663672576: CLSDM requested exit

RECOVER COPY OF DATABASE WITH TAG ORA-19870 ORA-19625 ORA-27037

— błędy wyskoczą jak nie mamy dostępu / zabierzemy zasób na, ktorym były kopie datafile-ów i chcemy zrobić recover copy of database with tag 'X’;

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 04/15/2025 10:28:54
ORA-19870: error while restoring backup piece /zfssa/pool_backup/x_backup1/jq3mv282_1_1
ORA-19625: error identifying file /zfssa/pool_backup/x_backup1/data_D-x_I-1838446808_TS-UNDOTBS1_FNO-3_cg3ktclf
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3

— robimy crosschecka i ponawiamy bckp jak nie mamy już zasobu z kopią:

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’…