Every Rman Command Generates Error ORA-01861 (文档 ID 791329.1)

最新推荐文章于 2022-10-29 17:44:37 发布

cucuan4341

最新推荐文章于 2022-10-29 17:44:37 发布

阅读量87

点赞数

In this Document
  Symptoms
  Cause
  Solution
  References

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process, and therefore has not been subject to an independent technical review.

Applies to:

Oracle Server - Enterprise Edition - Version: 10.2.0.3
This problem can occur on any platform.

Symptoms

Getting errors when running rman commands:

RMAN-03014: implicit resync of recovery catalog failed
RMAN-03009: failure of full resync command on default channel at 03/02/2009 15:04:27
ORA-01861: literal does not match format string

Cause

Invalid date data in the controlfile.

Solution

Dumped the controlfile with this command:

alter session set events 'immediate trace name controlf level 20';

Then because the problem had just started and because the months had changed from February to March, I searched for invalid dates in the February time frame. and found an invalid date for a completion time of a backuppiece, below you can see the date 02/030/09 is an invalid date:

RECID #236846 Recno 9799 Record timestamp 02/27/09 21:42:43 piece #1 copy #1 pool 0
Backup set key: stamp=676780305, count=224870
V$RMAN_STATUS: recid=3221200628, stamp=3221200624
Flags:
Device: DISK
Handle: +FRA_S03/arkeon/backupset/2009_01_22/nnndn1_tag20090122t014737_0.1508.676780307
Media-Handle:
Comment:
Tag: TAG20090122T014737
Completion time 02/30/09 12:10:33

The controlfile was recreated and the rman activities could then continue without the error. In this instance the database was a RAC database so the customer used this note to recreate the controlfile with:

Note 118931.1
Title: Recreating the Controlfile in RAC and OPS