Sunday, July 31, 2016

Orphan object(s) in the backup specification

Warning message from DP

Warning: While reading mount point information, Data Protector found 2 backup object(s), which reference inexistent mountpoint(s) on client system 'winserver123.abc.com'.
Do you want to leave this(these) orphan object(s) in the backup specification?

Reason:

  • Maybe a shared drive that's no longer available on the workstation or were reclaimed.
  • If it exists, it's not accessible by the DP software. In such case the data list needs to be updated/changed on what needs to be backed up.
Solution:
  • Login to the client workstation and check from the Computer Management -> Storage -> Disk Management
  • Check the problematic mountpoint exists and in healthy state. If it doesn't, remove the mountpoint from the backup specification and save it.

Thursday, July 21, 2016

ORA-19588: archived log RECID ***** STAMP ********* is no longer valid

Error log:

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on dev_0 channel at 03/08/2014 07:50:43
ORA-19588: archived log RECID 99528 STAMP 841638632 is no longer valid

Recovery Manager complete.
[Major] From: ob2rman@dbserver01.com "stin"  Time: 03/08/14 07:50:56
External utility reported error.

RMAN PID=12391

[Major] From: ob2rman@dbserver01.com "stin"  Time: 03/08/14 07:50:56
The database reported error while performing requested operation.

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
 RMAN-03009: failure of backup command on dev_0 channel at 03/08/2014 07:50:43
 ORA-19588: archived log RECID 99528 STAMP 841638632 is no longer valid

Recovery Manager complete.

Cause:


-> Archive log backup fails due to invalid/stale archive files which are left uncleared after the backup completion.
-> It can be when there is two consecutive backups happening. For instance, an archive backup gets triggered while there's active full backup. The overlaps would cause this error.

Solution:
Database admin should run "crosscheck archivelog all" to remove the files that were backed up already.

Hope that helps!

Tuesday, July 19, 2016

Restarting DP Cell Manager

How to restart DP cell manager

When the cell manager hangs or any kind of malfunction requires DP cell manager to be reset the following steps could help! 


1. To check the status of cell manager services
/opt/omni/sbin/omnisv –status

2. Run the following cmd to Stop all DP related services (CRS, RDS and MMD)
/opt/omni/sbin/omnisv –stop

3. Double check whether all the services went down
/opt/omni/sbin/omnisv –status

4. Check if any omni related process is running. If not move to next step
Ps –ef |grep omni    ( Command to check any omni processes are in hung status)
kill -9 <PID>            ( kill the process if any using its Process ID)
Ps –ef |grep omni    ( double check and move to next step)

5. Start the cell manager services now

/opt/omni/sbin/omnisv –start

6. Check all the services are up. If not follow steps 2, 3 & 4

/opt/omni/sbin/omnisv –status

7. Once the services are up, run the below command before any backup is triggered after the restart. This will clear all the in-progress sessions that went to hung status during the services restart.

/opt/omni/sbin/omnidbutil –clear

Please use these steps with caution!