Random Timestamp Generated In Backup Controlfile
(Doc ID 1540102.1)
Last updated on FEBRUARY 27, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.3 and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
Goal
When using:
'alter database backup controlfile to trace resetlogs;' command
There are sometimes extra lines and a timestamp appearing within the script.
This then causes the use of the file to fail. The position of the timestamp in the file appears to be random.
eg. ....
.....
-- After mounting the created controlfile, the following SQL
-- statement will place the database in the appropriate
-- protection mode:
-- ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE PERFORMANCE
STARTUP NOMOUNT
CREATE CONTROLFILE REUSE DATABASE "PRODX" RESETLOGS NOARCHIVELOG
MAXLOGFILES 20
MAXLOGMEMBERS 5
MAXDATAFILES 600
MAXINSTANCES 1
MAXLOGHISTORY 2629
LOGFILE
*** 2013-03-25 10:57:31.141 <<<<-----
GROUP 1 (
'/MIS/db/prodx/data04/logs02/log02PROD01.dbf',
'/MIS/db/prodx/data01/logs01/log01PROD01.dbf'
) SIZE 400M BLOCKSIZE 512,
GROUP 2 (
'/MIS/db/prodx/data01/logs01/log01PROD02.dbf',
'/MIS/db/prodx/data04/logs02/log02PROD02.dbf'
) SIZE 400M BLOCKSIZE 512,
....
etc.
Why is this happening?
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |
| References |