ORACLE error from auxiliary database: ORA-01152: file 2 was not restored fr
Hello,
i'm trying to clone a database. It is in archive log mode.
I took a full back using below command
run {
backup
tag 'DAILY_WHOLE'
format 'FULL_backup_%s_%p_%c.bkp' database
plus archivelog
tag 'DAILY_WHOLE'
delete all input;
backup
current controlfile
format 'FULL_backup_%s_%p_%c.bkp' tag 'WHOLE'
spfile
format 'FULL_backup_%s_%p_%c.bkp' tag 'WHOLE';
}then i issue a duplicate database command
RUN
DUPLICATE DATABASE TO TEST_DB
NOFILENAMECHECK
NOREDO
BACKUP LOCATION '/disk10/flash_recovery_area/PROD';
}at the very end I got this error.
contents of Memory Script:
Alter clone database open resetlogs;
executing Memory Script
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 05/15/2013 11:59:21
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
RMAN-06136: ORACLE error from auxiliary database: ORA-01152: file 2 was not restored from a sufficiently old backup
ORA-01110: data file 2: 'sysaux.dbf'Can anyone help me? I would appreciate it. thanks
NOREDO would be used when you have a Consistent Backup (i.e. backup taken when the database is MOUNTed but not OPEN) and so, no archivelogs need to be applied. (This would also be the case for a NOARCHIVELOG database).
See the notes on NOREDO in the DUPLICATE command documentation in the Backup and Recovery Reference.
http://docs.oracle.com/cd/E11882_01/backup.112/e10643/rcmsynta020.htm#i81724
Hemant K Chitale
Similar Messages
-
RMAN-06136: ORACLE error from auxiliary database
Dear All,
When i start to recover a tablespace(TSPITR) using RMAN, getting below errors. Could any guide me
RMAN-03002: failure of recover command at 02/07/2013 14:12:30
RMAN-03015: error occurred in stored script Memory Script
RMAN-06136: ORACLE error from auxiliary database: ORA-01119: error in creating database file '/rman/SHFLCLN/oradata'
ORA-27056: could not delete file
IBM AIX RISC System/6000 Error: 1: Not owner
RMAN-06956: create datafile failed; retry after removing /rman/SHFLCLN/oradata from OS01119, 00000, "error in creating database file '%s'"
// *Cause: Usually due to not having enough space on the device.
// *Action: -
Error in duplicating dataguard, RMAN-04006: error from auxiliary,ORA-12514
Hi All,
Trying to duplicate using rman and facing below issue
rman TARGET sys/oracle@pawsdb AUXILIARY sys/oracle@adpaws
Recovery Manager: Release 11.2.0.3.0 - Production on Tue Jun 19 20:47:09 2012
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: PAWSDB (DBID=3014417093)
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04006: error from auxiliary database: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
TNS on aux looks like this
ADPAWS =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 10.210.23.227)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = adpaws)
Listener under grid home (ASM) on aux looks like this
# listener.ora Network Configuration File: /home/oracle/app/oracle/product/11.2.0/grid/network/admin/listener.ora
# Generated by Oracle configuration tools.
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(ORACLE_HOME= /home/oracle/app/oracle/product/11.2.0/grid)
(SID_NAME = adpaws)
(GLOBAL_DBNAME= adpaws.example.com)
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = cuscmetl.hillscte.com)(PORT = 1521))
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
ADR_BASE_LISTENER = /home/oracle/app/oracle
output of lsnrctl on aux looks like this
LSNRCTL for Linux: Version 11.2.0.3.0 - Production on 19-JUN-2012 20:53:49
Copyright (c) 1991, 2011, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=cuscmetl.hillscte.com)(PORT=1521)))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 11.2.0.3.0 - Production
Start Date 19-JUN-2012 20:53:42
Uptime 0 days 0 hr. 0 min. 6 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /home/oracle/app/oracle/product/11.2.0/grid/network/admin/listener.ora
Listener Log File /home/oracle/app/oracle/diag/tnslsnr/cuscmetl/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=cuscmetl.hillscte.com)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
Services Summary...
Service "adpaws.example.com" has 1 instance(s).
Instance "adpaws", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
TNS on target is also configured properly, both are tnsping successful from each other, running this command from aux server results in failure
Please help
thanksThanks for reply, below are the last 50 lines from listener log
<msg time='2012-06-19T21:10:13.125-05:00' org_id='oracle' comp_id='tnslsnr'
type='UNKNOWN' level='16' host_id='server2.server.com'
host_addr='10.210.23.227'>
<txt>19-JUN-2012 21:10:13 * (CONNECT_DATA=(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))(SERVICE_NAME=etldb)(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.210.23.229)(PORT=56363)) * establish * etldb * 0
</txt>
</msg>
<msg time='2012-06-19T21:10:13.160-05:00' org_id='oracle' comp_id='tnslsnr'
type='UNKNOWN' level='16' host_id='server2.server.com'
host_addr='10.210.23.227'>
<txt>19-JUN-2012 21:10:13 * (CONNECT_DATA=(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))(SERVICE_NAME=etldb)(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.210.23.229)(PORT=56364)) * establish * etldb * 0
</txt>
</msg>
<msg time='2012-06-19T21:10:18.125-05:00' org_id='oracle' comp_id='tnslsnr'
type='UNKNOWN' level='16' host_id='server2.server.com'
host_addr='10.210.23.227'>
<txt>19-JUN-2012 21:10:18 * (CONNECT_DATA=(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))(SERVICE_NAME=etldb)(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.210.23.229)(PORT=56366)) * establish * etldb * 0
</txt>
</msg>
<msg time='2012-06-19T21:10:18.160-05:00' org_id='oracle' comp_id='tnslsnr'
type='UNKNOWN' level='16' host_id='server2.server.com'
host_addr='10.210.23.227'>
<txt>19-JUN-2012 21:10:18 * (CONNECT_DATA=(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))(SERVICE_NAME=etldb)(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.210.23.229)(PORT=56367)) * establish * etldb * 0
</txt>
</msg>
<msg time='2012-06-19T21:10:23.126-05:00' org_id='oracle' comp_id='tnslsnr'
type='UNKNOWN' level='16' host_id='server2.server.com'
host_addr='10.210.23.227'>
<txt>19-JUN-2012 21:10:23 * (CONNECT_DATA=(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))(SERVICE_NAME=etldb)(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.210.23.229)(PORT=56368)) * establish * etldb * 0
</txt>
</msg>
<msg time='2012-06-19T21:10:23.159-05:00' org_id='oracle' comp_id='tnslsnr'
type='UNKNOWN' level='16' host_id='server2.server.com'
host_addr='10.210.23.227'>
<txt>19-JUN-2012 21:10:23 * (CONNECT_DATA=(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))(SERVICE_NAME=etldb)(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.210.23.229)(PORT=56369)) * establish * etldb * 0
</txt>
</msg>
<msg time='2012-06-19T21:10:28.125-05:00' org_id='oracle' comp_id='tnslsnr'
type='UNKNOWN' level='16' host_id='server2.server.com'
host_addr='10.210.23.227'>
<txt>19-JUN-2012 21:10:28 * (CONNECT_DATA=(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))(SERVICE_NAME=etldb)(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.210.23.229)(PORT=56371)) * establish * etldb * 0
</txt>
</msg>
<msg time='2012-06-19T21:10:28.160-05:00' org_id='oracle' comp_id='tnslsnr'
type='UNKNOWN' level='16' host_id='server2.server.com'
host_addr='10.210.23.227'>
<txt>19-JUN-2012 21:10:28 * (CONNECT_DATA=(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))(SERVICE_NAME=etldb)(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.210.23.229)(PORT=56372)) * establish * etldb * 0
</txt>
</msg> -
Error RMAN connection to auxiliary database ORA- 12514
Hi,
I'm trying to make a clone of my database in another server but when I'm trying to connect as follow the RMAN return
to me the error ORA-12514.
C:\Documents and Settings\joses.morales>rman TARGET sys/pass@iswgen nocatalog
AUXILIARY sys/[email protected]
Recovery Manager: Release 8.1.7.4.1 - Production
RMAN-06005: connected to target database: ISWGEN (DBID=2348350645)
RMAN-06009: using target database controlfile instead of recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04006: error from auxiliary database: ORA-12514: TNS:listener could not resolve SERVICE_NAME given in connect descriptor
For more information:
- the auxiliary database is started whit nomount option.
- this is my listener.ora in the auxiliary host
LISTENER =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = WSSP61)(PORT = 1521))
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME = oracle8)
(ORACLE_HOME = C:\oracle\ora81)
(SID_NAME = iswgen)
(SID_DESC =
(GLOBAL_DBNAME = oracle8)
(ORACLE_HOME = C:\oracle\ora81)
(SID_NAME = oracle8)
- this is my tnsnames.ora in the auxiliary host
ISWGEN =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = wssp61)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = iswgen)
ORACLE8 =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = WSSP61)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = oracle8)
- this is my tnsnames.ora in the target host
iswgen =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = gdcoracle)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = iswgen)
iswgen.wssp61 =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = wssp61)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = iswgen)
- target server: gdcoracle
- auxiliary server: wssp61
- global name in auxiliary: Oracle8
- intances in auxiliary: Oracle8 & Iswgen
I was expecting the follow message:
connected to target database: ISWGEN (DBID=519338572)
using target database control file instead of recovery catalog
connected to auxiliary database: ISWGEN.WSSP61 (not mounted)
Can anybody help me to resolve this error ORA-12514??
ThanksI'm try to connect to the auxiliary server at SQLPLUS and I get the follow:
C:\Documents and Settings\joses.morales>sqlplus /nolog
SQL*Plus: Release 8.1.7.0.0 - Production on Sex Jun 1 12:26:09 2007
(c) Copyright 2000 Oracle Corporation. All rights reserved.
SQL> conn sys@iswgen
Informe a senha:
ERROR:
ORA-12514: TNS:listener nao conseguiu resolver o SERVICE_NAME fornecido no
descitor de conexao
SQL> conn sys@iswgen as sysdba
Informe a senha:
ERROR:
ORA-12514: TNS:listener nao conseguiu resolver o SERVICE_NAME fornecido no
descitor de conexao
SQL> conn internal as sysdba
Conectado.
SQL>
Any sugestions?
Thanks everyone and regards -
Error ORA-01152: file 1 was not restored from a sufficiently old backup
Its also not thread just to share info with oracle gurus here.If my findings for the below workaround is wrong then please do correct me.
Sometime you get the error after performing restoring controlfile when you don't have autobackup controlfile on
error ORA-01152: file 1 was not restored from a sufficiently old backup
why?
Cause When you shutdown the database with using the normal,transactional or immediate options not abort a full checkpoint occurs.A full checkpoint ensures that all of the dirty blocks contained in the buffer cache are written to the data files,the database comes into synchronized state at this time i.e controlfile CKPT SCN=databasefile CKPT.
Like in this demo i am not taking backup the database in opened mode
Demo 1
SQL> archive log list
Database log mode No Archive Mode
Automatic archival Disabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 9
Current log sequence 11
SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount
ORACLE instance started.
Total System Global Area 171966464 bytes
Fixed Size 787988 bytes
Variable Size 145488364 bytes
Database Buffers 25165824 bytes
Redo Buffers 524288 bytes
Database mounted.
SQL> alter database archivelog
2 /
Database altered.
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 9
Next log sequence to archive 11
Current log sequence 11
Recovery Manager: Release 10.1.0.2.0 - Production
Copyright (c) 1995, 2004, Oracle. All rights reserved.
RMAN> connect target sys/sys
connected to target database: ORCL1 (DBID=1024798223)
RMAN> list backup
2> ;
using target database controlfile instead of recovery catalog
RMAN> backup database
2> ;
Starting backup at 08-DEC-07
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=C:\ORACLE10G\ORACLE\ORADATA\ORCL1\ORCL1\SYSTEM01.DBF
input datafile fno=00003 name=C:\ORACLE10G\ORACLE\ORADATA\ORCL1\ORCL1\SYSAUX01.DBF
input datafile fno=00002 name=C:\ORACLE10G\ORACLE\ORADATA\ORCL1\ORCL1\UNDOTBS01.DBF
input datafile fno=00004 name=C:\ORACLE10G\ORACLE\ORADATA\ORCL1\ORCL1\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 08-DEC-07
channel ORA_DISK_1: finished piece 1 at 08-DEC-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL1\ORCL1\BACKUPSET\2007_12_08\O1_MF_NNNDF_TAG20071208T143558_3ONSCZBY_.BKP
comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:45
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
including current controlfile in backupset
including current SPFILE in backupset
channel ORA_DISK_1: starting piece 1 at 08-DEC-07
channel ORA_DISK_1: finished piece 1 at 08-DEC-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL1\ORCL1\BACKUPSET\2007_12_08\O1_MF_NCSNF_TAG20071208T143558_3ONSFGN7_.BKP
comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:05
Finished backup at 08-DEC-07
SQL> shutdown immediate
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.Now i delete the controlfile from OS command.
SQL> startup
ORACLE instance started.
Total System Global Area 171966464 bytes
Fixed Size 787988 bytes
Variable Size 145488364 bytes
Database Buffers 25165824 bytes
Redo Buffers 524288 bytes
ORA-00205: error in identifying controlfile, check alert log for more infoi don't have automatized control file backup neither i have control file copy.What i will do
to recover control file i will restore controlfile from backup.Before doing it that i will bring
the database in mount state.
SQL> shutdown immediate
ORA-01507: database not mounted
ORACLE instance shut down.
SQL> startup mount
ORACLE instance started.
Total System Global Area 171966464 bytes
Fixed Size 787988 bytes
Variable Size 145488364 bytes
Database Buffers 25165824 bytes
Redo Buffers 524288 bytes
ORA-00205: error in identifying controlfile, check alert log for more infoi have two backup piece in my backupset folder you cant check control file backup
existence with list backup controlfile at RMAN prompt cause it needs database in
mount state.You will have to test both backup set pieces.
RMAN> restore controlfile from
'C:\oracle\flash_recovery_area\orcl1\ORCL1\BACKUPSET\2007_12_08\O1_MF_NCSNF_TAG20071208T143558_3ONSFGN7_.BKP';
Starting restore at 08-DEC-07
using channel ORA_DISK_1
channel ORA_DISK_1: restoring controlfile
channel ORA_DISK_1: restore complete
output filename=C:\ORACLE10G\ORACLE\ORADATA\ORCL1\ORCL1\CONTROL01.CTL
output filename=C:\ORACLE10G\ORACLE\ORADATA\ORCL1\ORCL1\CONTROL02.CTL
output filename=C:\ORACLE10G\ORACLE\ORADATA\ORCL1\ORCL1\CONTROL03.CTL
Finished restore at 08-DEC-07
SQL> startup
ORACLE instance started.
Total System Global Area 171966464 bytes
Fixed Size 787988 bytes
Variable Size 145488364 bytes
Database Buffers 25165824 bytes
Redo Buffers 524288 bytes
Database mounted.
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SQL> alter database open resetlogs
2 /
Database altered.You can see database now comes into open mode without raising error error
ORA-01152: file 1 was not restored from a sufficiently old backup,you can see that
database shutdown with immediate which synchronized the control file with database
file.
Demo 2
------------Now in this demo i am taking backup the database in opened mode before backup
database i have deleted alls previous backup.
Database is in opened moder if i take the backup in database opened mode
(i.e full checkpoint will not occur controlfile CKPT SCN<>datafile CKPT SCN)
you will get the error when you will restore controlfile from backup set.
error ORA-01152: file 1 was not restored from a sufficiently old backup
Reason is that CKPT SCN in the datafiles will be ahead of the backupset control file no
full checkpoint occuring. You are not taking backup in consistent state and the
backupset will not be in consistent state.When you will restore the control file from
backupset then yours restored control file SCN will be lesser then yours datafile
checkpoint SCN.
SQL> startup
ORACLE instance started.
Total System Global Area 171966464 bytes
Fixed Size 787988 bytes
Variable Size 145488364 bytes
Database Buffers 25165824 bytes
Redo Buffers 524288 bytes
Database mounted.
Database opened.
RMAN> backup database
2> ;
Starting backup at 11-DEC-07
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=C:\ORACLE10G\ORACLE\ORADATA\ORCL1\ORCL1\SYSTEM01.D
BF
input datafile fno=00003 name=C:\ORACLE10G\ORACLE\ORADATA\ORCL1\ORCL1\SYSAUX01.D
BF
input datafile fno=00002 name=C:\ORACLE10G\ORACLE\ORADATA\ORCL1\ORCL1\UNDOTBS01.
DBF
input datafile fno=00004 name=C:\ORACLE10G\ORACLE\ORADATA\ORCL1\ORCL1\USERS01.DB
F
channel ORA_DISK_1: starting piece 1 at 11-DEC-07
channel ORA_DISK_1: finished piece 1 at 11-DEC-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL1\ORCL1\BACKUPSET\2007_12_11\O1_M
F_NNNDF_TAG20071211T125123_3OWJD0V5_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:56
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
including current controlfile in backupset
including current SPFILE in backupset
channel ORA_DISK_1: starting piece 1 at 11-DEC-07
channel ORA_DISK_1: finished piece 1 at 11-DEC-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL1\ORCL1\BACKUPSET\2007_12_11\O1_M
F_NCSNF_TAG20071211T125123_3OWJFT97_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:09
Finished backup at 11-DEC-07now i shut down the database in order to delete the control file from os command
SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> deleting the controlfile from oradata folder
SQL> startup
ORACLE instance started.
Total System Global Area 171966464 bytes
Fixed Size 787988 bytes
Variable Size 145488364 bytes
Database Buffers 25165824 bytes
Redo Buffers 524288 bytes
ORA-00205: error in identifying controlfile, check alert log for more infonow i would restore the controlfile from backupset.
RMAN> restore controlfile from 'C:\oracle\flash_recovery_area\orcl1\ORCL1\BACKUP
SET\2007_12_11\O1_MF_NCSNF_TAG20071211T125123_3OWJFT97_.BKP'
2> ;
Starting restore at 11-DEC-07
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=159 devtype=DISK
channel ORA_DISK_1: restoring controlfile
channel ORA_DISK_1: restore complete
output filename=C:\ORACLE10G\ORACLE\ORADATA\ORCL1\ORCL1\CONTROL01.CTL
output filename=C:\ORACLE10G\ORACLE\ORADATA\ORCL1\ORCL1\CONTROL02.CTL
output filename=C:\ORACLE10G\ORACLE\ORADATA\ORCL1\ORCL1\CONTROL03.CTL
Finished restore at 11-DEC-07
SQL> shutdown immediate
ORA-01507: database not mounted
ORACLE instance shut down.
SQL> startup
ORACLE instance started.
Total System Global Area 171966464 bytes
Fixed Size 787988 bytes
Variable Size 145488364 bytes
Database Buffers 25165824 bytes
Redo Buffers 524288 bytes
Database mounted.
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SQL> alter database open resetlogs
2 /
alter database open resetlogs
ERROR at line 1:
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: 'C:\ORACLE10G\ORACLE\ORADATA\ORCL1\ORCL1\SYSTEM01.DBF'what would you do that now you have lost controlfile ,you dont have copy either you dont
have autobackup on for controlfile,you need to create the control file
SQL> shutdown immediate
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
SQL> startup nomount
ORACLE instance started.
Total System Global Area 171966464 bytes
Fixed Size 787988 bytes
Variable Size 145488364 bytes
Database Buffers 25165824 bytes
Redo Buffers 524288 bytes
SQL> create controlfile reuse database orcl1 noresetlogs archivelog
2 MAXLOGFILES 50
3 MAXLOGMEMBERS 3
4 MAXDATAFILES 300
5 MAXINSTANCES 8
6 MAXLOGHISTORY 500
7 LOGFILE
8 GROUP 1 'C:\oracle10g\oracle\oradata\orcl1\orcl1\redo01.LOG',
9 GROUP 2 'C:\oracle10g\oracle\oradata\orcl1\orcl1\redo02.LOG',
10 GROUP 3 'C:\oracle10g\oracle\oradata\orcl1\orcl1\redo03.LOG'
11 DATAFILE
12 'C:\oracle10g\oracle\oradata\orcl1\orcl1\SYSAUX01.DBF',
13 'C:\oracle10g\oracle\oradata\orcl1\orcl1\SYSTEM01.DBF',
14 'C:\oracle10g\oracle\oradata\orcl1\orcl1\UNDOTBS01.DBF',
15 'C:\oracle10g\oracle\oradata\orcl1\orcl1\USERS01.DBF'
16
SQL> /
Control file created.
SQL> alter database open
2 /
Database altered.KhurramNo need to manually recreate the controlfile. Simply issue RECOVER DATABASE prior to opening database.
E:\>rman target /
Recovery Manager: Release 10.2.0.1.0 - Production on Sun Dec 30 01:22:34 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database (not started)
RMAN> startup
Oracle instance started
database mounted
database opened
Total System Global Area 612368384 bytes
Fixed Size 2006192 bytes
Variable Size 239076176 bytes
Database Buffers 364904448 bytes
Redo Buffers 6381568 bytes
RMAN> backup database;
Starting backup at 30-DEC-07
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=148 devtype=DISK
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=E:\ORACLE\ORADATA\ORA10G\SYSTEM01.DBF
input datafile fno=00002 name=E:\ORACLE\ORADATA\ORA10G\UNDOTBS01.DBF
input datafile fno=00003 name=E:\ORACLE\ORADATA\ORA10G\SYSAUX01.DBF
input datafile fno=00004 name=E:\ORACLE\ORADATA\ORA10G\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 30-DEC-07
channel ORA_DISK_1: finished piece 1 at 30-DEC-07
piece handle=D:\DB_BACKUPS\12J4S23M_1_1.BKP tag=TAG20071230T012302 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:01:35
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
including current control file in backupset
including current SPFILE in backupset
channel ORA_DISK_1: starting piece 1 at 30-DEC-07
channel ORA_DISK_1: finished piece 1 at 30-DEC-07
piece handle=D:\DB_BACKUPS\13J4S26L_1_1.BKP tag=TAG20071230T012302 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
Finished backup at 30-DEC-07
RMAN> shutdown immediate
database closed
database dismounted
Oracle instance shut down
RMAN> exit
Recovery Manager complete.
E:\>del e:\oracle\oradata\ora10g\*.ctl
E:\>rman target /
Recovery Manager: Release 10.2.0.1.0 - Production on Sun Dec 30 01:25:39 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database (not started)
RMAN> startup
Oracle instance started
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of startup command at 12/30/2007 01:25:56
ORA-00205: error in identifying control file, check alert log for more info
RMAN> restore controlfile from 'D:\DB_BACKUPS\13J4S26L_1_1.BKP';
Starting restore at 30-DEC-07
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=157 devtype=DISK
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
output filename=E:\ORACLE\ORADATA\ORA10G\CONTROL01.CTL
output filename=E:\ORACLE\ORADATA\ORA10G\CONTROL02.CTL
output filename=E:\ORACLE\ORADATA\ORA10G\CONTROL03.CTL
Finished restore at 30-DEC-07
RMAN> alter database mount;
database mounted
released channel: ORA_DISK_1
RMAN> alter database open resetlogs;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 12/30/2007 01:27:33
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: 'E:\ORACLE\ORADATA\ORA10G\SYSTEM01.DBF'
RMAN> recover database;
Starting recover at 30-DEC-07
Starting implicit crosscheck backup at 30-DEC-07
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
Crosschecked 1 objects
Finished implicit crosscheck backup at 30-DEC-07
Starting implicit crosscheck copy at 30-DEC-07
using channel ORA_DISK_1
Finished implicit crosscheck copy at 30-DEC-07
searching for all files in the recovery area
cataloging files...
no files cataloged
using channel ORA_DISK_1
starting media recovery
archive log thread 1 sequence 1 is already on disk as file E:\ORACLE\ORADATA\ORA10G\REDO03.LOG
archive log filename=E:\ORACLE\ORADATA\ORA10G\REDO03.LOG thread=1 sequence=1
media recovery complete, elapsed time: 00:00:02
Finished recover at 30-DEC-07
RMAN> alter database open resetlogs;
database opened
RMAN> shutdown immediate
database closed
database dismounted
Oracle instance shut down
RMAN> startup
connected to target database (not started)
Oracle instance started
database mounted
database opened
Total System Global Area 612368384 bytes
Fixed Size 2006192 bytes
Variable Size 247464784 bytes
Database Buffers 356515840 bytes
Redo Buffers 6381568 bytes
RMAN> -
ORA-01031: insufficient privileges from auxiliary database while connecting
i am getting this error ORA-01031: insufficient privileges from auxiliary database while connecting plz help.
TNS-01106: Listener using listener name VINAR has already been started
[oraclone@server VINTEST_server]$ tnsping VINAR
TNS Ping Utility for Linux: Version 11.1.0.7.0 - Production on 17-JAN-2013 19:10:49
Copyright (c) 1997, 2008, Oracle. All rights reserved.
Used parameter files:
/d04/oraclone/db/tech_st/11.1.0/network/admin/VINTEST_server/sqlnet_ifile.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=server.csacons.com)(PORT=1571)) (CONNECT_DATA= (SERVICE_NAME=VINAR) (INSTANCE_NAME=VINAR)))
OK (0 msec)
[oraclone@server VINTEST_server]$ rman target sys/change_on_install@VINAR auxiliary /
Recovery Manager: Release 11.1.0.7.0 - Production on Thu Jan 17 19:11:38 2013
Copyright (c) 1982, 2007, Oracle. All rights reserved.
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04005: error from target database:
ORA-01031: insufficient privileges
[oraclone@server VINTEST_server]$ sqlplus sys/change_on_install@VINAR as sysdba
SQL*Plus: Release 11.1.0.7.0 - Production on Thu Jan 17 19:31:52 2013
Copyright (c) 1982, 2008, Oracle. All rights reserved.
ERROR:
ORA-01031: insufficient privileges
Enter user-name: sys@VINAR as sysdba
Enter password:
ERROR:
ORA-01031: insufficient privileges
Enter user-name: [oraclone@server VINTEST_server]$
[oraclone@server VINTEST_server]$
SQL> select * from v$pwfile_users;
no rows selected
SQL>
listner.ora
SID_LIST_VINTEST =
(SID_LIST =
(SID_DESC =
(ORACLE_HOME= /d04/oraclone/db/tech_st/11.1.0)
(SID_NAME = VINTEST)
#(GLOBAL_DBNAME = VINAR)
#(ORACLE_HOME= /d03/oravnr/db/tech_st/11.1.0)
#(SID_NAME = VINAR)
(SID_DESC =
#(ORACLE_HOME= /d04/oraclone/db/tech_st/11.1.0)
#(SID_NAME = VINTEST)
(GLOBAL_DBNAME = VINAR)
(ORACLE_HOME= /d03/oravnr/db/tech_st/11.1.0)
(SID_NAME = VINAR)
tnsnames.ora
VINTEST=
(DESCRIPTION=
(ADDRESS=(PROTOCOL=tcp)(HOST=server.csacons.com)(PORT=1591))
(CONNECT_DATA=
(SERVICE_NAME=VINTEST)
(INSTANCE_NAME=VINTEST)
VINAR=
(DESCRIPTION=
(ADDRESS=(PROTOCOL=tcp)(HOST=server.csacons.com)(PORT=1571))
(CONNECT_DATA=
(SERVICE_NAME=VINAR)
(INSTANCE_NAME=VINAR)
kind regards
plz helpPl do not post duplicates - ORA-01031: insufficient privileges from auxiliary database while connecting
-
ORA-01152: file 1 was not restored from a sufficiently old backup
Hi,
I have restored the control file from auto-backup, but some of my archive logs are missing...
when I am recovering it as
RECOVER DATABASE UNTIL CANCEL USING BACKUP CONTROLFILE;
ORA-00279: change 37158334186 generated at 02/19/2012 02:53:11 needed for
thread 1
ORA-00289: suggestion : /u07/oradata/main/arch/main_738330900_118084_1.dbf
ORA-00280: change 37158334186 for thread 1 is in sequence #118084
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
CANCEL
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/u02/oradata/main/system01.dbf'
and
ALTER DATABASE OPEN RESETLOGS
ERROR at line 1:
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/u02/oradata/main/system01.dbf'
how to sort out this issue, I just want to open the database in whatever mode.
Please help me.If no - then startup in mount state and make this file offline.This is archive log file. Might you thought it as datafile ;-)
@OP.
Once again i suggest you to refer what aman said below.
Aman.... wrote:
This has been discussed already couple of times, tried using the search ?
https://forums.oracle.com/forums/search.jspa?threadID=&q=ORA-01152%3A+file+1+was+not+restored+from+a+sufficiently+old+backup&objID=f61&dateRange=all&userID=&numResults=15
Aman....Also check tihs. but but but but its not an supported format, it can be uesd when there are no other options.
*RECOVER A DATAFILE WITH MISSING ARCHIVELOGS [ID 418476.1]*
Edited by: CKPT on Feb 21, 2012 12:11 PM -
RMAN-04005: error from target database:
Hi,
when I want register my target by
]$ rman catalog prdrman/prdrman@PRD target sys/manager@DEV
I receive this :
RMAN-04005: error from target database:
ORA-01031: insufficient privileges
Do you have any idea ?
Many thanks before.Here are some further hints from documentation:
ORA-01031: insufficient privileges
When : SQL> connect sym/sym as SYSDBA
Additional : init.ora remote_login_passwordfile=EXCLUSIVE or SHARED
Cause : Username/password is not correct (if the user is added by granting
SYSDBA to the user, this user is added to the passwordfile with the
password from the data dictionary)
or:
Password file has
-> incorrect name orapw<name_of_database>
-> is not in $ORACLE_HOME/dbs
-> has wrong privileges
They should be -rwSr-----
For example:
-rwSr----- 1 server sdb 1536 Mar 25 08:12 orapwv901
Solve : You can set the correct privileges (Unix) by issueing
$ chmod 4640 passwordfile
As a last resort, recreate the password file and remind to add
additional privileged (sysdba or sysoper) users -
Oracle Error code: 1116, message: ORA-01116: error in opening database file
Hi ,
Please advise on this error message
Oracle Error code: 1116, message: ORA-01116: error in opening database file 202 ORA-01110: data file 202: '/u02/app/oracle/oradata/ubidev12/dbf/temp02.dbf'
All these while, the dashboard working well in my local computer application with server database.
Just discovered this error when I refresh the data.
Kindly advise.
Thanks,
Kim Yokethe more detail error is
Oracle Error code: 1116, message: ORA-01116: error in opening database file 203 ORA-01110: data file 203: '/u02/app/oracle/oradata/ubidev12/dbf/temp03.dbf' ORA-27041: unable to open file SVR4 Error: 2: No such file or directory Additional information -
RMAN Restore on Test DB Fails - ORA-01152:file 1 was not restored from blah
Calling all RMAN Gurus!
I'm having trouble recovering an RMAN backup on my test DB server. Please Help!
Solaris 10/Oracle 10.2.0.4 Standard Edition (Both Servers)
Part one - Step by Step
Primary Server
1. Perform full backup: backup database plus archivelog;
2. Copy Backupset & Controlfile to test server: "RSYNC/NFS Mount"
Test Server
1. rman target /
2. startup nomount;
3. restore controlfile blah blah
4. alter database mount;
5. catalog backuppiece
6. restore database; - no issues
*7. recover database noredo; - no issues*
*8. alter database open resetlogs;*
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 09/09/2009 08:48:22
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/data/oracle/oradata/planodb/system01.dbf'
All is good until I try and open the database. What am I missing?? Why doesn't this work???
Because .... If I go through the exact steps but I perform a "recover database" instead of "recover database noredo", I can open the database!!!
Example :
6. restore database; no issues
7. recover database;
Starting recover at 09-SEP-09
using channel ORA_DISK_1
starting media recovery
channel ORA_DISK_1: starting archive log restore to default destination
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=34
channel ORA_DISK_1: reading from backup piece /data/oracle/orabase/backup/backup
set/2009_09_09/o1_mf_annnn_BACKUP_PLANODB_000_0_5bgkffqq_.bkp
channel ORA_DISK_1: restored backup piece 1
piece handle=/data/oracle/orabase/backup/backupset/2009_09_09/o1_mf_annnn_BACKUP
PLANODB000_0_5bgkffqq_.bkp tag=BACKUP_PLANODB_000_090909010005*
channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
archive log filename=/data/oracle/oradata/arch/PLANODB/archivelog/2009_09_09/o1_
mf_1_34_5bhdkwd4_.arc thread=1 sequence=34
channel default: deleting archive log(s)
archive log filename=/data/oracle/oradata/arch/PLANODB/archivelog/2009_09_09/o1_
mf_1_34_5bhdkwd4_.arc recid=42 stamp=697106925
unable to find archive log
archive log thread=1 sequence=35
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 09/09/2009 08:48:52
RMAN-06054: media recovery requesting unknown log: thread 1 seq 35 lowscn 1425007
This is ok because seq 35 doesn't actually exist!
8. alter database open resetlogs;
database opened!You could also explore the UNTIL clause of the RECOVER DATABASE command to specify Recovery until a specific Log, SCN or Timestamp.
Since you are cloning a Hot Backup to another server the Recovery has to be an Incomplete Recovery. So, it will be to a Log, SCN or Timestamp -- either of which you could also explicitly specify with the UNTIL clause.
Hemant K Chitale
http://hemantoracledba.blogspot.com -
Good Morning All,
One of our RMAN backups is failing with the following error message. Any suggestions would be greatly appreciated.
==================================================================================================
Starting backup at 12/30/2008 22:03:47
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 12/30/2008 22:03:47
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> ##BACKUP ARCHIVELOG ALL FORMAT '%d_bkp_al_%t_Set%s_Piece%p' delete input;
2>
3> # DELETE ARCHIVELOG UNTIL TIME 'SYSDATE-7';
4>
5> # check if database can be restored
6> # RESTORE DATABASE VALIDATE;
7>
8> # check if controlfile can be restored
9> ##RESTORE CONTROLFILE to '/backups/admin/custpr/custpr_bkp_cntlfile.ctl' VALIDATE;
10>
11> # check if archivelogs for the past two weeks can be restored
12> # RESTORE ARCHIVELOG FROM TIME 'SYSDATE-7' VALIDATE;
13>
14> # - Verify all backups on backup media are intact
15> # CROSSCHECK BACKUP OF DATABASE;
16>
17> # - Display a list of files that need to be backed up based on the retention
18> # policy. For this case study, files that don't have at least 1 backups
19> # will be reported.
20> REPORT NEED BACKUP;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 7 days
Report of files whose recovery needs more than 7 days of archived logs
File Days Name
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of report command at 12/30/2008 22:03:48
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> # - delete un-necessary backups. This command deletes backups based on the
2> # retention policy.
3> ######### commented out DELETE OBSOLETE - TSM not configured to delete on 68
4> #########DELETE OBSOLETE;
5>
6> # - get complete list of existing backups
7> LIST BACKUP;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of list command at 12/30/2008 22:03:49
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> #-end of file-
2> **end-of-file**
RMAN>
Edited by: ORA_UMAIR on Dec 31, 2008 7:51 AMThis Oracle Database is 9.2.0.6.0. Here is the complete log file. The RMAN script that I am using ran successfully many times before.
====================================================================================================
Recovery Manager: Release 9.2.0.6.0 - 64bit Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
RMAN>
connected to recovery catalog database
RMAN>
connected to target database: CUSTPR (DBID=525071053)
RMAN>
RMAN> #########################################################################
2> # LEVEL 0 BACKUP #
3> #########################################################################
4>
5> # Configure backups to be written to disk.
6> CONFIGURE DEFAULT DEVICE TYPE TO DISK;
old RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
new RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Set the retention policy to a recovery window of 7 days. This ensures that
2> # RMAN retains all backups needed to recover the database to any point in time
3> # in the last 7 days. You can use the DELETE OBSOLETE command to delete
4> # backups that are no longer required by the retention policy. To exclude a
5> # backup from consideration by the policy, you can use KEEP option with the
6> # BACKUP command.
7> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
old RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to use two disk channels for backup, restore, recovery, and
2> # maintenance operations.
3> CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
old RMAN configuration parameters:
CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
new RMAN configuration parameters:
CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to write disk backups to the /backup directory.
2> # The format specifier %t is replaced with a 4-byte timestamp, %s with the
3> # backup set number, and %p with the backup piece number.
4> CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
old RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
new RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to back up the control file after each backup.
2> CONFIGURE CONTROLFILE AUTOBACKUP ON;
old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to write controlfile autobackups to the /backup directory.
2> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Enable the backup optimization feature introduced in 9i to make sure that
2> # RMAN won't backup an archivelog or datafile if there already exists a backup
3> # of that file. The FORCE option can be used to override optimization on a
4> # specific BACKUP command.
5> CONFIGURE BACKUP OPTIMIZATION ON;
old RMAN configuration parameters:
CONFIGURE BACKUP OPTIMIZATION ON;
new RMAN configuration parameters:
CONFIGURE BACKUP OPTIMIZATION ON;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Use the SHOW ALL command to see the current configuration settings.
2> SHOW ALL ;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%d_bkp_cf%F';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 1;
CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' FORMAT '%d_bkp_df%t_Set%s_Piece%p';
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/orahome2/custprdb/9.2.0/dbs/snapcf_custpr.f'; # default
RMAN>
RMAN> # The following commands are run each day to start the backup cycle.
2> # The steps are:
3> # - Take an incremental level 0 backup of the database. A level 0 backup is
4> # a complete backup of the entire file which can be used as the basis
5> # for a subsequent incremental backup.
6> # - Backup all archivelogs that have not already been backed up.
7> # - Delete on-disk archivelogs older than seven days.
8>
9> BACKUP INCREMENTAL LEVEL 0 FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p'
10> DATABASE maxsetsize 33G
11> PLUS ARCHIVELOG FORMAT '/backups/admin/custpr/%d_bkp_al%t_Set%s_Piece%p'
12> delete all input;
Starting backup at 12/30/2008 22:01:40
current log archived
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=11 devtype=DISK
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=8008 recid=7910 stamp=674638862
input archive log thread=1 sequence=8009 recid=7911 stamp=674671207
input archive log thread=1 sequence=8010 recid=7912 stamp=674697380
input archive log thread=1 sequence=8011 recid=7913 stamp=674780433
input archive log thread=1 sequence=8012 recid=7914 stamp=674784211
input archive log thread=1 sequence=8013 recid=7915 stamp=674863288
input archive log thread=1 sequence=8014 recid=7916 stamp=674863300
channel ORA_DISK_1: starting piece 1 at 12/30/2008 22:01:41
channel ORA_DISK_1: finished piece 1 at 12/30/2008 22:03:47
piece handle=/backups/admin/custpr/CUSTPR_bkp_al674863300_Set3083_Piece1 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:02:07
channel ORA_DISK_1: deleting archive log(s)
archive log filename=/custpr/arch/arch_custpr_8008.log recid=7910 stamp=674638862
archive log filename=/custpr/arch/arch_custpr_8009.log recid=7911 stamp=674671207
archive log filename=/custpr/arch/arch_custpr_8010.log recid=7912 stamp=674697380
archive log filename=/custpr/arch/arch_custpr_8011.log recid=7913 stamp=674780433
archive log filename=/custpr/arch/arch_custpr_8012.log recid=7914 stamp=674784211
archive log filename=/custpr/arch/arch_custpr_8013.log recid=7915 stamp=674863288
archive log filename=/custpr/arch/arch_custpr_8014.log recid=7916 stamp=674863300
Finished backup at 12/30/2008 22:03:47
Starting backup at 12/30/2008 22:03:47
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 12/30/2008 22:03:47
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> ##BACKUP ARCHIVELOG ALL FORMAT '%d_bkp_al_%t_Set%s_Piece%p' delete input;
2>
3> # DELETE ARCHIVELOG UNTIL TIME 'SYSDATE-7';
4>
5> # check if database can be restored
6> # RESTORE DATABASE VALIDATE;
7>
8> # check if controlfile can be restored
9> ##RESTORE CONTROLFILE to '/backups/admin/custpr/custpr_bkp_cntlfile.ctl' VALIDATE;
10>
11> # check if archivelogs for the past two weeks can be restored
12> # RESTORE ARCHIVELOG FROM TIME 'SYSDATE-7' VALIDATE;
13>
14> # - Verify all backups on backup media are intact
15> # CROSSCHECK BACKUP OF DATABASE;
16>
17> # - Display a list of files that need to be backed up based on the retention
18> # policy. For this case study, files that don't have at least 1 backups
19> # will be reported.
20> REPORT NEED BACKUP;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 7 days
Report of files whose recovery needs more than 7 days of archived logs
File Days Name
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of report command at 12/30/2008 22:03:48
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> # - delete un-necessary backups. This command deletes backups based on the
2> # retention policy.
3> ######### commented out DELETE OBSOLETE - TSM not configured to delete on 68
4> #########DELETE OBSOLETE;
5>
6> # - get complete list of existing backups
7> LIST BACKUP;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of list command at 12/30/2008 22:03:49
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> #-end of file-
2> **end-of-file**
RMAN>
Recovery Manager complete. -
I am geting errors in my database alert log file ora-12012 and ora 44003
Hi all,
I am using oracle 10g ...10.2.0.1.0 and OS is solaris 10.......
i am geting these errors in my database alert log file last two days..i am not geting why it is coming?
ORA-12012: error on auto execute of job 8887
ORA-44003: invalid SQL name
and trace file is i got i am posting here please help any one is aware about this....
System name: SunOS
Node name: obrmzone1
Release: 5.10
Version: Generic_137111-06
Machine: sun4v
Instance name: ------
Redo thread mounted by this instance: 1
Oracle process number: 144
Unix process pid: 26874, image:--------- (J000)
*** ACTION NAME:(AUTO_SPACE_ADVISOR_JOB) 2011-06-10 22:00:49.372
*** MODULE NAME:(DBMS_SCHEDULER) 2011-06-10 22:00:49.372
*** SERVICE NAME:(SYS$USERS) 2011-06-10 22:00:49.372
*** SESSION ID:(110.7114) 2011-06-10 22:00:49.372
*** 2011-06-10 22:00:49.372
ORA-12012: error on auto execute of job 8887
ORA-44003: invalid SQL name
thank you in advance,
DavI just google with "ORA-44003: invalid SQL name" and found below link:
http://www.oracle-base.com/articles/10g/dbms_assert_10gR2.php
SIMPLE_SQL_NAME
The SIMPLE_SQL_NAME function checks the input string conforms to the basic characteristics of a simple SQL name:
The first character of the name is alphabetic.
The name only contains alphanumeric characters or the "_", "$", "#"
Quoted names must be enclosed by double quotes and may contain any characters, including quotes provided they are represented by two quotes in a row ("").
The function ignores leading and trailing white spaces are ignored
The length of the input string is not validated. -
Error in Recover Database - ORA-01547 , ORA-01194 and ORA-01110
Hello folks,
I am facing a problem when recovering a database..
I made each tablespace in backup mode, then copied the datafile. I revert back the tablespace status to normal status.Once all datafiles are copied to target location, i created the control file from the source db.
I started the target db by
sqlplus "/ as sysdba"
then i executed the control file
SQL>@ctrlfile.sql
Control file got created.
SQL>recover database until cancel using backup controlfile;
it asked for archives. I gave the path one by one until everything was done.Now i gave 'cancel' as below.
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
cancel
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 377 needs more recovery to be consistent
ORA-01110: data file 377: '<path>/xxfndx01.dbf'
ORA-01112: media recovery not started
Could anyone please tell me where I went wrong and how can I move ahead from this stage???
Later on, when I gave open resetlogs, it gave the same error(as below)
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01194: file 377 needs more recovery to be consistent
ORA-01110: data file 377: '<path>/xxfndx01.dbf'
Please let me know the mistake I made, how to avoid that and how to proceed now ???
Thanks,
Cherrish Vaidiyan
[email protected]Hello Cherrish,
A very good question you have asked. I hope you realize that you're doing an incomplete recovery. There is some amount of information that is still there in the online redo-log, that would not be applied on your target db. Moreover when you're using backup controlfile, you do not know till which point you need to apply archive logs.
For incomplete recovery, Oracle for some reason has been very strict about the recover database command. i.e.
recover database using backup controlfile
recover database using backup controlfile until cancel
Is not same. It also applies to the command that you had given. By giving the command 'recover database using backup controlfile until cancel', you're telling Oracle that incomplete recovery is in process, and you would do resetelogs, to make sure all files are in sync. This is required when you have lost the redo-logs
In case you have just lost the control file. All latest redo-logs, archive-logs and datafiles are okay (or have been restored), then recover database using backup controlfile; would work perfectly okay. and resetlogs would not be required.. and that would be a complete recovery
I hope this all makes sense to you
Regards
Sudhanshu -
Concurrent request - view output - Error connecting to database ORA-1017
Hi all,
When I run Active Users concurrent request.
It complete sucessfully without any error.
but when i click on view output then i get following error.
Error connecting to database ORA-1017
Reg
Chirag Patel
NairobiHi All,
I followed this metalink note.
Copy File : Error connecting to database ORA-1017 [ID 269511.1]
and it if working fine now.
Reg
Chirag Patel -
I need help! when I am importing my NEF Raw files from my D3300 camera into lightroom 5 and try to use the "copy as DNG" button I always get an error message saying that "saying the file is not recognized by the raw format support". The whole purpose of that button is so that the file can be recognized... How can I make the "copy as DNG" button work as it is supposed too?? Thank you
Thank you for responding. So I essentially will never be able to use that button in lightroom 5? do I need to get LR 6? Will there ever be an update for LR 5 that will enable me to use it?
Does DNG Converter work within LR or do I have to upload pictures to my computer and then make a second copy in DNG format. and then go into LR and use them?
Thank you @dj_paige
Maybe you are looking for
-
How can I execute an action in Acrobat XI Pro using PowerPoint VBA?
I am using Acrobat XI Pro and PowerPoint that came with Office 2013 running on Windows 8. I have an action in the Action Wizard that executes JavaScript code. It works fine when I click Tools | Action Wizard | Actions | <my script>, and Start in Acro
-
TS1389 iTunes authorization not accepting my new apple id and password
I plugged in my ipod to sync it and it asked to authorize my computer. I entered my password and I got an error message. I got an email to reset my password. I did. I go back to iTunes and I get the same error. I get another email to reset my passwor
-
Using the WRT54G and a WUSB54GC with an Xbox 360.
Hi, I have a WRT54G router and I just bought a WUSB54GC compact Wireless-G USB adapter because I thought I could connect it to my Xbox 360 to play games online. Is this possible? I've tried a few times, but I can't get it to work. I'm not too tech sa
-
Depreciation run problem."You can only post in new year after closing the"
Hi, We are implementing Asset accounting to one of our co code.New Assets were created in Jan and when I tried to Post depreciation for Jan, I get an error log that says "You can only post in new year after closing the previous year." When i double c
-
I have just recently started to sync my IPod Touch to another computer, which I have authorised. I can download purchased songs off this, but a notification comes up when i want to sync apps purchased, saying that it has to delete my other apps befor