Alter database archivelog;
Can any one tell How to alter database as archivelog..
I tried wid
start up mount but its giving error as Insufficient privileges
Hi,
Login as Sysdba,
SELECT LOG_MODE FROM SYS.V$DATABASE;
you get the mode in which database is present right now.
Add the following line to Pfile
# Archive Log Destinations -
log_archive_dest_1='location=/u02/oradata/cuddle/archive' (path )
log_archive_start=TRUE
#startup the database in mount mode
startup mount
alter database archivelog;
alter database open;
That's it..
Cheers
Pavan Kumar N
Similar Messages
-
Alter database into Archivelog mode.
HI Team,
I am using ORACLE 9i.
I want to convert database into archivelog mode from noarchivelog mode.
Using the following SQL Commands I can able to convert my database into the Archivelog.
SQL> connect sys as sysdba
Enter password: *****************
Connected.
SQL> alter database archivelog;
alter database archivelog
ERROR at line 1:
ORA-01126: database must be mounted EXCLUSIVE and not open for this operation
SQL> startup mount;
ORA-01081: cannot start already-running ORACLE - shut it down first
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.
Total System Global Area 252779340 bytes
Fixed Size 453452 bytes
Variable Size 125829120 bytes
Database Buffers 125829120 bytes
Redo Buffers 667648 bytes
Database mounted.
SQL> alter database archivelog;
Database altered.
My problem is that I had to shutdown the database before converting it in to the archivelog mode...
Is there any way that without shuting down the database i can switch to archivelog mode.
Please comments...
Shatrughanif we shutdown immediate one's database..do
it's listener terminated too???The database registration with the listener yes, the listener itself no. That is, if you execute a command like "lsnrctl stat" you won't see the database anymore, but the listener is still active. Example :
[ora102 ~ db102]$ lsnrctl stat
LSNRCTL for Linux: Version 10.2.0.1.0 - Production on 05-MAY-2007 18:57:51
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)(PORT=1521)))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 10.2.0.1.0 - Production
Start Date 05-MAY-2007 18:27:34
Uptime 0 days 0 hr. 30 min. 16 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /home/ora102/OraHome1/network/admin/listener.ora
Listener Log File /home/ora102/OraHome1/network/log/listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=localhost)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC0)))
Services Summary...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "db102" has 1 instance(s).
Instance "db102", status READY, has 2 handler(s) for this service...
The command completed successfully
[ora102 ~ db102]$ sqlplus / as sysdba
SQL*Plus: Release 10.2.0.1.0 - Production on Sat May 5 18:58:03 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
SYS@db102 SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SYS@db102 SQL> exit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
[ora102 ~ db102]$ lsnrctl stat
LSNRCTL for Linux: Version 10.2.0.1.0 - Production on 05-MAY-2007 18:58:33
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)(PORT=1521)))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 10.2.0.1.0 - Production
Start Date 05-MAY-2007 18:27:34
Uptime 0 days 0 hr. 30 min. 58 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /home/ora102/OraHome1/network/admin/listener.ora
Listener Log File /home/ora102/OraHome1/network/log/listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=localhost)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC0)))
Services Summary...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
[ora102 ~ db102]$ -
Master database archivelog but not the slaves...is this possible?
Hi,
I've followinf situation:
1xmaster database server oracle 9i
3xslave database servers oracle 9i
The databases on the slaves are exact copies of the master. The slaves are refreshed every night by a san-sync. The san-sync copies all the datafiles/redo logs and control files to the slave servers. On the master database DML is executed so all changes to the data are made on the master database, the slaves are static. All the databases are in no-archivelog mode.
Rigth now I don't have a backup of the master database and I would like to implement a hot rman backup.
questions:
can I just run the master database in archivelog mode without turning on archiving on the slaves? I guess this might be a problem because archiving is turned on at database level ('alter database archivelog'). What will happen when I sync the master database to the slaves when the master database is in archivelog mode and the slaves are not. Please note we don't sync spfile/pfile.
regards,
MartinHi,
Thanks for your reply.
My doubts are about the master database should be in archive log mode but the slaves don't, the slaves are copies of the master (datafiles, redologs and controlfiles) and the slaves are refresh every night.
Right now the master database is also in noarchivelog mode. What if I change the master to archivelog mode and would like to keep the slaves in noarchivelog mode.
Will the slaves also be in archivelog mode after a database refresh?
I would like to know this because if this is true i'll need to do some setting in the init.ora file like archivelog dest etc...
regards,
Martin -
Alter database OR alter system?? what is the logic?
Hi,
this is just a general question not related to any particular issue. I seem to be missing the logic behind when we need to use the "alter system ... " statements and when we need to use the "alter database ..." statements. Is there a logic I can use to guess ? Or we only need to remember them (or look up for them)?
Let's take an example.
alter database archivelog; & alter system checkpoint;
OR
alter database add logfile; & alter system set undo_retention=800;
If you have a key that can be generally applied please let me know as I am not able to find it. Thank you,
enricoI am not sure if there is a general rule but this is what I use:
alter database is about modifying the database architecture, like data files, archived log files etc.
alter system is about modifying the instance. so, you are modifying the way oracle runs. Remember that all parameters should be done with alter system (like undo_retention)
hope this will help you. -
hi,
while alter the database to nonarchieving mode to archieving mode i am getting the followuing error
pls give the solution for this
SQL> startup mount
ORACLE instance started.
Total System Global Area 535662592 bytes
Fixed Size 1348508 bytes
Variable Size 255855716 bytes
Database Buffers 272629760 bytes
Redo Buffers 5828608 bytes
Database mounted.
SQL> select log_mode from v$database;
LOG_MODE
NOARCHIVELOG
SQL> shutdown;
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
SQL> startup mount exclusive;
ORACLE instance started.
Total System Global Area 535662592 bytes
Fixed Size 1348508 bytes
Variable Size 255855716 bytes
Database Buffers 272629760 bytes
Redo Buffers 5828608 bytes
Database mounted.
SQL> alter database archivelog;
alter database archivelog
ERROR at line 1:
ORA-00265: instance recovery required, cannot set ARCHIVELOG modeHi;
As Aman mention your db is not closed normaly, you are using abort option which mean you say you db cjust close wihtout any checking. Follow
1. shutdown immediate;
2. startup mount exclusive;
3. alter database archivelog;
4. alter database open;
5. SELECT LOG_MODE FROM SYS.V$DATABASE;
While you are doing all those process also check alert.log for any error message
Regard
Helios -
'alter database open resetlogs' didn't reset one of the datafiles
I've spent the last three and a half weeks recovering an oracle database (11g 64-bit linux) because of a corrupt block in an online redo log (which I thought was being written to multiple locations). I restored the files, moving some of them around in the process; recovered to the latest possible point; moved files back to their proper location; ran 'alter database open resetlogs'; and one of the datafiles (from a bigfile tablespace) didn't get reset. I checked afterward, and it was marked offline. I do not remember placing the file offline, and cannot find such a statement in my last 300 sqlplus commands, which includes commands well before I renamed this file and the commands surrounding the rename.
Restoring/recovering the database again will take too long, and is a remarkably poor option. Even if the database had opened correctly, the affected tablespace would not have been touched in the two or three minutes the database was open. Is there any way to force oracle to reset the logs again or otherwise fix this one file to mark it with the same date? Only allowing the resetlogs option after an incomplete recovery seems a poor restriction, especially, if files can slip through like this. I'm suspecting there is someway to just fix the checkpoint values for the tablespace, but I don't know where to begin. This particular file is <5% of the database, so if I have to do some sort of backup/restore with just it, that is probably doable.0: 11.1.0.6.0 on SUSE Linux Enterprise Server 10 SP2
1: rman
backup format '/opt/oracle/backup/mydatabase_%Y-%M-%D_%s_datafiles_%p' (database);
backup format '/opt/oracle/backup/mydatabase_%Y-%M-%D_%s_archivelogs_%p' archivelog all delete input;
backup format '/opt/oracle/backup/mydatabase_%Y-%M-%D_%s_control_%p' current controlfile spfile;
2:
restore database; --not sure what datafiles were restored with this
restore datafile X; --several files were restored individually
recover database until scn 1137554504; -- I verified that all datafiles were on the same checkpoint after this finished. Not having placed any files offline, I didn't bother checking that.
3:
SQL> alter database open resetlogs;
Database altered.
Elapsed: 00:04:20.34
SQL> quit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
4: Nothing in the tablespace has been touched since I ran 'alter database open resetlogs;'. It also appears that oracle placed the file offline (without me telling it to do so) and left it that way through the resetlogs, leaving the tablespace unusable during the time it was opened. The only things that would be out of date are the 'RESETLOGS_CHANGE#', the 'CHECKPOINT_CHANGE#', and associated values. It's still at the last scn before the resetlogs, and the system has been in archivelog mode the entire time. This is all information that Oracle could be tracking, and from a program logic standpoint there is no reason why Oracle cannot tie together the changes before the resetlogs, the resetlogs command and the changes after the resetlogs into a new, continuous string of changes. I assume there is some such feature in a high-caliber program because I'm actually a programmer (who would have included such advanced tracking features), and I've become a DBA out of necessity. I admit to not knowing all of the oracle DBA commands, hence me posting here before doing the work of submitting a request to metalink.
5: I consider it a poor restriction because it doesn't always reset the logs on all files, and as far as my knowledge goes it has rendered my 3.5 week recovery process WORTHLESS. I suppose it could cause numerous errors, especially if the database wasn't cleanly shut down, but having the ability to do something equivalent to datafiles that oracle skipped the process on seems quite useful in my situation. I guess the more fundamental problem to complain about is that it would apply such changes to only some of the files, while leaving others unusable, instead of just giving me an error that some files weren't going to be reset, but I think I'm done venting my Oracle frustrations for now.
Am I stuck with a tablespace that I cannot bring online with the database open, or is there some sort of 'alter database datafile' command (or anything else) that I know nothing of that will fix the straggling file?
Edited by: jbo5112 on Oct 5, 2009 3:33 PM -- obfuscated some file names to secure identity. -
ALTER DATABASE RENAME DATAFILE, what really needs to bu run later?
Hi!
If I "alter database" and move some datafiles to newly added luns, do I need to run:
On DB side:
1) perl adcfgclone.pl dbTechStack (according new luns!)
2) If 1) is yes, then probably have to run "perl adcfgclone.pl dbconfig $CONTEXT_FILE"?
On APPS side:
1) Autoconfig?
Second question. If on on new LUN is only having archived log files (no db datafiles are on that lun), should they be involved in Number of DATA_TOP's on the target system?
THXIf I "alter database" and move some datafiles to newly added luns, do I need to run:
On DB side:
1) perl adcfgclone.pl dbTechStack (according new luns!)
2) If 1) is yes, then probably have to run "perl adcfgclone.pl dbconfig $CONTEXT_FILE"?
On APPS side:
1) Autoconfig?Damir,
Could you please elaborate more? Why would you need to run perl adcfgclone.pl if you alter the database and add more datafiles?
Second question. If on on new LUN is only having archived log files (no db datafiles are on that lun), should they be involved in Number of DATA_TOP's on the target system?When cloning, it is not required to copy the archivelog files. DATA_TOPs should point to the mount points where datafiles are located. -
Standby db: continue manualluy alter database register logfile
Hi,
in my standby db 10.2.0.4, on linux platform, some archive log are not register properly and i need to perform the register logfile manually.
Which test a can i do to solve this problem?
Thank you.This is my standby alert log:
-- Connected User is Valid
RFS[10]: Assigned to RFS process 26620
RFS[10]: Identified database type as 'physical standby'
Tue Sep 14 05:05:58 2010
Errors in file /oracle/admin/orcl/udump/orcl1_rfs_26620.trc:
ORA-16401: archivelog rejected by RFS
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[11]: Assigned to RFS process 26622
RFS[11]: Identified database type as 'physical standby'
Tue Sep 14 05:05:58 2010
Errors in file /oracle/admin/orcl/udump/orcl1_rfs_26622.trc:
ORA-16401: archivelog rejected by RFS
Tue Sep 14 05:06:03 2010
Media Recovery Log /database/arch/orcl/arc1_16195_326468442.ARC
Media Recovery Waiting for thread 2 sequence 16536
Tue Sep 14 05:20:46 2010
alter database register logfile '/database/arch/orcl/arc2_16536_326468442.ARC'
Tue Sep 14 05:20:46 2010
There are 1 logfiles specified.
ALTER DATABASE REGISTER [PHYSICAL] LOGFILE
Resynchronizing thread 2 from sequence 16535 to 16536
Completed: alter database register logfile '/database/arch/orcl/arc2_16536_326468442.ARC'
Tue Sep 14 05:20:48 2010
Media Recovery Log /database/arch/orcl/arc2_16536_326468442.ARC
Tue Sep 14 05:21:07 2010
Media Recovery Log /database/arch/orcl/arc1_16196_326468442.ARC
Media Recovery Log /database/arch/orcl/arc1_16197_326468442.ARC
Media Recovery Log /database/arch/orcl/arc1_16198_326468442.ARC
Media Recovery Waiting for thread 1 sequence 16199
Tue Sep 14 05:45:29 2010
RFS[6]: Archived Log: '/database/arch/orcl/arc1_16199_326468442.ARC'
Tue Sep 14 05:45:29 2010
RFS[8]: Archived Log: '/database/arch/orcl/arc1_16200_326468442.ARC'
Tue Sep 14 05:45:29 2010
RFS[6]: Archived Log: '/database/arch/orcl/arc1_16201_326468442.ARC'
Tue Sep 14 05:45:40 2010
Media Recovery Log /database/arch/orcl/arc1_16199_326468442.ARC
Media Recovery Waiting for thread 2 sequence 16537
Tue Sep 14 06:00:05 2010
alter database register logfile '/database/arch/orcl/arc2_16537_326468442.ARC'
Tue Sep 14 06:00:05 2010
There are 1 logfiles specified.
ALTER DATABASE REGISTER [PHYSICAL] LOGFILE
alter database register are performed from a scheduled shell script that check log from V$ARCHIVED_LOG -
Alter database open resetlogs upgrade ; throwing error
Recently i have cloned a database from 11.2.0.2 to 11.2.0.3 on a new server.... I got the error as fowwos,
contents of Memory Script:
Alter clone database open resetlogs;
executing Memory Script
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00601: fatal error in recovery manager
RMAN-03004: fatal error during execution of command
RMAN-10041: Could not re-create polling channel context following failure.
RMAN-10024: error setting up for rpc polling
RMAN-10005: error opening cursor
RMAN-10002: ORACLE error: ORA-03114: not connected to ORACLE
RMAN-03002: failure of Duplicate Db command at 07/12/2012 16:19:24
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
RMAN-06136: ORACLE error from auxiliary database: ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-00704: bootstrap process failure
ORA-39700: database must be opened with UPGRADE option
Process ID: 29247
Session ID: 200 Serial number: 5
So i have tried
SQL> alter database open resetlogs upgrade;
alter database open resetlogs upgrade
ERROR at line 1:
ORA-01139: RESETLOGS option only valid after an incomplete database recovery
SQL> alter database open upgrade;
alter database open upgrade
ERROR at line 1:
ORA-01113: file 1 needs media recovery
ORA-01110: data file 1: '+DATA_CMX/cmx/datafile/system.270.788451975'
Any help ?Hi,
Duplicate is not supported using different version of database, so I recommend you don't use duplicate.
Because RMAN "duplicate" attempts to automatically rename (rename required recover) and open the database you may not use RMAN duplicate for this case, only RMAN restore.
Perform this work using normal restore database.
See this example.
On prod database with db_name/db_unique_name dbupg:
Recovery Manager: Release 11.2.0.2.0 - Production on Fri Jul 13 15:15:59 2012
RMAN> backup database plus archivelog delete input;
Starting backup at 13-JUL-12
current log archived
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=52 device type=DISK
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=17 RECID=1 STAMP=788540852
input archived log thread=1 sequence=18 RECID=2 STAMP=788541371
channel ORA_DISK_1: starting piece 1 at 13-JUL-12
channel ORA_DISK_1: finished piece 1 at 13-JUL-12
piece handle=/u01/app/oracle/flash_recovery_area01/DBUPG/backupset/2012_07_13/o1_mf_annnn_TAG20120713T151612_800shf7w_.bkp tag=TAG20120713T151612 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
channel ORA_DISK_1: deleting archived log(s)
archived log file name=/u01/app/oracle/flash_recovery_area01/DBUPG/archivelog/2012_07_13/o1_mf_1_17_800rz40y_.arc RECID=1 STAMP=788540852
archived log file name=/u01/app/oracle/flash_recovery_area01/DBUPG/archivelog/2012_07_13/o1_mf_1_18_800shcsd_.arc RECID=2 STAMP=788541371
Finished backup at 13-JUL-12
Starting backup at 13-JUL-12
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00001 name=+DS8000_DG/dbupg/datafile/system.271.788537119
input datafile file number=00002 name=+DS8000_DG/dbupg/datafile/sysaux.272.788537167
input datafile file number=00003 name=+DS8000_DG/dbupg/datafile/undotbs1.273.788537199
input datafile file number=00004 name=+DS8000_DG/dbupg/datafile/users.275.788537229
channel ORA_DISK_1: starting piece 1 at 13-JUL-12
channel ORA_DISK_1: finished piece 1 at 13-JUL-12
piece handle=/u01/app/oracle/flash_recovery_area01/DBUPG/backupset/2012_07_13/o1_mf_nnndf_TAG20120713T151614_800shgw5_.bkp tag=TAG20120713T151614 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:35
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including current control file in backup set
including current SPFILE in backup set
channel ORA_DISK_1: starting piece 1 at 13-JUL-12
channel ORA_DISK_1: finished piece 1 at 13-JUL-12
piece handle=/u01/app/oracle/flash_recovery_area01/DBUPG/backupset/2012_07_13/o1_mf_ncsnf_TAG20120713T151614_800sjm29_.bkp tag=TAG20120713T151614 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 13-JUL-12
Starting backup at 13-JUL-12
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=19 RECID=3 STAMP=788541412
channel ORA_DISK_1: starting piece 1 at 13-JUL-12
channel ORA_DISK_1: finished piece 1 at 13-JUL-12
piece handle=/u01/app/oracle/flash_recovery_area01/DBUPG/backupset/2012_07_13/o1_mf_annnn_TAG20120713T151652_800sjnf7_.bkp tag=TAG20120713T151652 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
channel ORA_DISK_1: deleting archived log(s)
archived log file name=/u01/app/oracle/flash_recovery_area01/DBUPG/archivelog/2012_07_13/o1_mf_1_19_800sjn5q_.arc RECID=3 STAMP=788541412
Finished backup at 13-JUL-12
RMAN> backup current controlfile;
Starting backup at 13-JUL-12
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including current control file in backup set
channel ORA_DISK_1: starting piece 1 at 13-JUL-12
channel ORA_DISK_1: finished piece 1 at 13-JUL-12
piece handle=/u01/app/oracle/flash_recovery_area01/DBUPG/backupset/2012_07_13/o1_mf_ncnnf_TAG20120713T153435_800tkwl2_.bkp tag=TAG20120713T153435 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 13-JUL-12I used same server to do this work... I really dont recommend that, if yes you must be aware about location of restore... you should use new server:
Create a spfile:
*.control_files='+DS8000_DG/dbclone/controlfile/Current.277.788541913'
*.db_name='dbupg'
*.db_unique_name='dbclone'
*.audit_file_dest='/u01/app/oracle/admin/dbclone/adump'
*.audit_trail='db'
*.compatible='11.2.0.0.0'
*.db_block_size=8192
*.db_create_file_dest='+MMC'
*.db_domain=''
*.db_recovery_file_dest_size=107374182400
*.db_recovery_file_dest='/u01/app/oracle/flash_recovery_area01'
*.diagnostic_dest='/u01/app/oracle'
*.log_file_name_convert='+DS8000_DG','+MMC'
*.memory_target=1031798784
*.open_cursors=300Make backup available on new server:
and:
SQL*Plus: Release 11.2.0.3.0 Production on Fri Jul 13 15:33:24 2012
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup nomount
ORACLE instance started.
Total System Global Area 1027182592 bytes
Fixed Size 2227936 bytes
Variable Size 599785760 bytes
Database Buffers 419430400 bytes
Redo Buffers 5738496 bytes
SQL> show parameter db_n
NAME TYPE VALUE
db_name string dbupg
SQL> show parameter db_un
NAME TYPE VALUE
db_unique_name string dbclone
RMAN> restore controlfile from '/u01/app/oracle/flash_recovery_area01/DBUPG/backupset/2012_07_13/o1_mf_ncnnf_TAG20120713T153435_800tkwl2_.bkp';
Starting restore at 13-JUL-12
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=290 device type=DISK
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:02
output file name=+DS8000_DG/dbclone/controlfile/current.277.788541913
Finished restore at 13-JUL-12
RMAN> startup mount
database is already started
database mounted
released channel: ORA_DISK_1
RMAN> run {
2> SET NEWNAME FOR DATABASE TO '+MMC';
3> restore database ;
4> }
executing command: SET NEWNAME
Starting restore at 13-JUL-12
Starting implicit crosscheck backup at 13-JUL-12
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=290 device type=DISK
Crosschecked 4 objects
Finished implicit crosscheck backup at 13-JUL-12
Starting implicit crosscheck copy at 13-JUL-12
using channel ORA_DISK_1
Crosschecked 2 objects
Finished implicit crosscheck copy at 13-JUL-12
searching for all files in the recovery area
cataloging files...
no files cataloged
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00001 to +MMC
channel ORA_DISK_1: restoring datafile 00002 to +MMC
channel ORA_DISK_1: restoring datafile 00003 to +MMC
channel ORA_DISK_1: restoring datafile 00004 to +MMC
channel ORA_DISK_1: reading from backup piece /u01/app/oracle/flash_recovery_area01/DBUPG/backupset/2012_07_13/o1_mf_nnndf_TAG20120713T151614_800shgw5_.bkp
channel ORA_DISK_1: piece handle=/u01/app/oracle/flash_recovery_area01/DBUPG/backupset/2012_07_13/o1_mf_nnndf_TAG20120713T151614_800shgw5_.bkp tag=TAG20120713T151614
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:46
Finished restore at 13-JUL-12
RMAN> recover database;
Starting recover at 13-JUL-12
using channel ORA_DISK_1
starting media recovery
media recovery complete, elapsed time: 00:00:01
Finished recover at 13-JUL-12So, just startup with upgrade option.
SQL*Plus: Release 11.2.0.3.0 Production on Fri Jul 13 15:39:31 2012
SQL> alter database open resetlogs upgrade; Now you can upgrade your database.
After upgrade database you can change the database name using NID:
$ nid
DBNEWID: Release 11.2.0.3.0 - Production on Fri Jul 13 15:50:23 2012
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
Keyword Description (Default)
TARGET Username/Password (NONE)
DBNAME New database name (NONE)
LOGFILE Output Log (NONE)
REVERT Revert failed change NO
SETNAME Set a new database name only NO
APPEND Append to output log NO
HELP Displays these messages NOHTH,
Levi Pereira
Edited by: Levi Pereira on Jul 13, 2012 4:04 PM -
Alter database ... keep identity hangs
Does anyone know what could cause the "alter database recover to logical standby keep identity" statement to hang waiting on "MRP wait on archivelog arrival"? I have executed this exact statement in the past on another physical standby and it went through fine.
I ran "exec dbms_logstdby.build" on the primary db (Linux 11.1.0.7), did a couple of log switches and then canceled the recovery process on the physical standby and executed the alter database...keep identity statement but the alter statement hung indefinitely on the standby db. It was always waiting to receive the current log file from the primary db.
Thanks.Ogan, thanks for your response.
All the archived logs appeared to have been applied so I'm not sure what "necessary archivelogs" are left to copy and apply. I could not find any archive gap. Any idea what may be the issue from the output (RAC primary -> physical standby) you requested? thanks.
From v$archived_log
THREAD# NAME SEQUENCE# ARC APPLIED
1 /flashrecovery/DBSB1/archivelog/2010_07_11/1_9133_832673014.arc 9133 YES YES
1 /u01/logs/dbsb1/1_9133_832673014.arc 9133 YES YES
1 /flashrecovery/DBSB1/archivelog/2010_07_11/1_9134_832673014.arc 9134 YES YES
1 /u01/logs/dbsb1/1_9134_832673014.arc 9134 YES YES
1 /flashrecovery/DBSB1/archivelog/2010_07_11/1_9135_832673014.arc 9135 YES YES
1 /u01/logs/dbsb1/1_9135_832673014.arc 9135 YES YES
1 /flashrecovery/DBSB1/archivelog/2010_07_11/1_9136_832673014.arc 9136 YES YES
1 /u01/logs/dbsb1/1_9136_832673014.arc 9136 YES YES
1 /flashrecovery/DBSB1/archivelog/2010_07_11/1_9137_832673014.arc 9137 YES NO
1 /u01/logs/dbsb1/1_9137_832673014.arc 9137 YES YES
1 /flashrecovery/DBSB1/archivelog/2010_07_11/1_9138_832673014.arc 9138 YES NO
1 /u01/logs/dbsb1/1_9138_832673014.arc 9138 YES YES
1 /flashrecovery/DBSB1/archivelog/2010_07_11/1_9139_832673014.arc 9139 YES NO
1 /u01/logs/dbsb1/1_9139_832673014.arc 9139 YES YES
1 /flashrecovery/DBSB1/archivelog/2010_07_12/1_9140_832673014.arc 9140 YES NO
1 /u01/logs/dbsb1/1_9140_832673014.arc 9140 YES YES
2 /flashrecovery/DBSB1/archivelog/2010_07_11/2_8192_832673014.arc 8192 YES YES
2 /u01/logs/dbsb1/2_8192_832673014.arc 8192 YES YES
2 /flashrecovery/DBSB1/archivelog/2010_07_11/2_8193_832673014.arc 8193 YES YES
2 /u01/logs/dbsb1/2_8193_832673014.arc 8193 YES YES
2 /flashrecovery/DBSB1/archivelog/2010_07_11/2_8194_832673014.arc 8194 YES YES
2 /u01/logs/dbsb1/2_8194_832673014.arc 8194 YES YES
2 /flashrecovery/DBSB1/archivelog/2010_07_11/2_8195_832673014.arc 8195 YES YES
2 /u01/logs/dbsb1/2_8195_832673014.arc 8195 YES YES
2 /flashrecovery/DBSB1/archivelog/2010_07_11/2_8196_832673014.arc 8196 YES NO
2 /u01/logs/dbsb1/2_8196_832673014.arc 8196 YES YES
2 /flashrecovery/DBSB1/archivelog/2010_07_12/2_8197_832673014.arc 8197 YES NO
2 /u01/logs/dbsb1/2_8197_832673014.arc 8197 YES YES
2 /flashrecovery/DBSB1/archivelog/2010_07_12/2_8198_832673014.arc 8198 YES NO
2 /u01/logs/dbsb1/2_8198_832673014.arc 8198 YES YES
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 9140
Next log sequence to archive 0
Current log sequence 9141 -
Diff btw "recover datafile file#" & "alter database recover datafile file#"
What is the difference between
"recover datafile file#"
"alter database recover datafile file#"
Thanks
NaveenI don't mean to be rude, but the statement that "There is no difference in both the commands" is facile in the extreme. Sounds like more off-the-cuff instant advice than the considered thoughts of someone who's actually bothered to try both commands out.
The "alter database recover..." command is a disaster waiting to happen and should never be used by anyone who actually wants to achieve a successful database recovery. It has the effect of suppressing most of the interactive dialogue you get when you submit the shorter "recover..." command, and indeed causes spurious errors to be displayed because the non-interactive recovery process gets it wrong.
For example, here's me recovering my database using the "alter database" syntax:
SQL> alter database open;
alter database open
ERROR at line 1:
ORA-01157: cannot identify/lock data file 4 - see DBWR trace file
ORA-01110: data file 4: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\WIN10\USERS01.DBF'
SQL> alter database recover datafile 4;
alter database recover datafile 4
ERROR at line 1:
ORA-00279: change 642359 generated at 07/04/2008 09:03:18 needed for thread 1
ORA-00289: suggestion :
C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\WIN10\ARCHIVELOG\2008_07_04\O1_MF_1_9_%U_.ARC
ORA-00280: change 642359 for thread 1 is in sequence #9Note the slightly alarming report of an 'error at line 1'. What's difficult to convey in mere text, however, is that at the end of that output, the thing just sits there, and you've no idea what on Earth is happening on the database. The text tells you it's making a suggestion, but there's no indication of how you accept the suggestion, of what's happening when you do accept it or where anything is up to.
I've interrupted one of those once (fortunately only in a training room) and lost the entire database as a result (because a half-complete, interrupted recovery is worse than no recovery at all).
Compare that with the plain "recover..." syntax example:
SQL> recover datafile 4;
ORA-00279: change 642359 generated at 07/04/2008 09:03:18 needed for thread 1
ORA-00289: suggestion :
C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\WIN10\ARCHIVELOG\2008_07_04\O1_MF_1_9_%U_.ARC
ORA-00280: change 642359 for thread 1 is in sequence #9
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 642571 generated at 07/04/2008 09:06:26 needed for thread 1
ORA-00289: suggestion :
C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\WIN10\ARCHIVELOG\2008_07_04\O1_MF_1_10_%U_.ARC
ORA-00280: change 642571 for thread 1 is in sequence #10
ORA-00278: log file
'C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\WIN10\ARCHIVELOG\2008_07_04\O1_MF_1_9_46TPVL2G_.ARC' no longer needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 642576 generated at 07/04/2008 09:06:32 needed for thread 1
ORA-00289: suggestion :
C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\WIN10\ARCHIVELOG\2008_07_04\O1_MF_1_12_%U_.ARC
ORA-00280: change 642576 for thread 1 is in sequence #12
ORA-00278: log file
'C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\WIN10\ARCHIVELOG\2008_07_04\O1_MF_1_11_46TPVRMK_.ARC' no longer needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
Log applied.
Media recovery complete.There are no weird error messages reported here. The suggestion is accompanied by a prompt that tells you how to accept it. Every time a new log is required, a new prompt is given. You can cleanly cancel at any time by typing 'cancel'. You are kept informed throughout and are in charge throughout.
Anyone that uses "alter database" syntax during a recovery is, therefore, either brave or foolhardy. In either case, there is a very profound difference between the two.
Your parting shot that 'alter database' is a SQL command and 'recover' can be an RMAN command misses the point by a wide mile, too. RMAN can issue pretty much any piece of SQL you like, so long as you wrap it in the SQL command:
RMAN> sql 'alter database recover datafile 4';
using target database control file instead of recovery catalog
sql statement: alter database recover datafile 4
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of sql command on default channel at 07/04/2008 09:23:16
ORA-00279: change generated at needed for thread
RMAN-11003: failure during parse/execution of SQL statement: alter database recover datafile 4
ORA-00279: change 642359 generated at 07/04/2008 09:03:18 needed for thread 1
ORA-00289: suggestion : C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\WIN10\ARCHIVELOG\2008_07_04\O1_MF_1_9_%U_.ARC
ORA-00280: change 642359 for thread 1 is in sequence #9We don't get much further in RMAN with this dodgy form of the recovery command than we did in SQL*Plus, it's true -but that's just because it's a silly command to use in the first place, wherever you thought to use it. The distinction you seek to draw between 'SQL commands' and 'RMAN commands' is false in this case, in other words. -
Orale 9i alter database open ( noarchivelog )
Hi all,
Not sure what was trhe issue as after I tried to put my database in noarchivelog mode it game me a ORA- device busy and logged me out of the session ?!!
Steps:
Shutdown first
then
- startup mount
- alter database noarchivelog
- alter database open
ORA-xxx device busy , acquire with NOWAIT option .....
Any ideas what i missed ?
ThxAfaik, there is really no need to adjust the log_archive_start and/or log_archive_dest parameters when changing the archivelog mode. The sequence mentioned by the OP (shutdown; startup mount; alter database noarchivelog; alter database open;) is sufficient.
-
What is the use of 'ALTER DATABASE CLOSE'?
Hello Everybody,
SQL*Plus: Release 10.1.0.2.0 - Production on Ma Aug 15 21:28:30 2005
Copyright © 1982, 2004, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - Production
With the Partitioning, OLAP and Data Mining options
SQL> conn / as sysdba
Connected.
SQL> startup force
ORACLE instance started.
Total System Global Area 171966464 bytes
Fixed Size 787988 bytes
Variable Size 145750508 bytes
Database Buffers 25165824 bytes
Redo Buffers 262144 bytes
Database mounted.
Database opened.
SQL> select status from v$instance;
STATUS
OPEN
SQL> alter database close;
Database altered.
SQL> select status from v$instance;
STATUS
MOUNTED
SQL> alter database open;
alter database open
ERROR at line 1:
ORA-16196: database has been previously opened and closed
If i have to shutdown the instance and database then
WHAT IS THE USE OF 'ALTER DATABASE CLOSE' ?
I need explanation. Why should i shutdown?
Dont give me this answer.
ORA-16196: database has been previously opened and closed
Cause: The instance has already opened and closed the database, which is allowed only once in its lifetime.
Action: Shut down the instance.If you read the documentation you will see that there is no ALTER DATABASE CLOSE command.
This is an undocumented Oracle command, which we are not supposed to use. Consequently we are not allowed to complain about the way that it works. Instead we're supposed to use SHUTDOWN IMMEDIATE.
Cheers, APC -
Alter database statement in anonymous pl/sql block
Is it possible to include an alter database statement in an anonymous pl/sql block?
When I execute this code to query user_tables for all table names, disable their constraints and drop the table, I got the following error:
***MY CODE
-- DECLARE VARIABLE(S)
DECLARE
v_TABLE_NAME TABLE_NAME.USER_TABLE%TYPE;
-- DECLARE AND DEFINE CURSOR
CURSOR c_GETTABLES is
SELECT TABLE_NAME from USER_TABLES;
BEGIN
OPEN c_GETTABLES;
LOOP
FETCH c_GETTABLES into v_TABLE_NAME;
EXIT when c_GETTABLES%notfound;
ALTER TABLE v_TABLE_NAME DISABLE PRIMARY KEY CASCADE;
DROP TABLE v_TABLE_NAME;
END LOOP;
CLOSE c_GETTABLES;
END;
***RESPONSE FROM SERVER
ALTER TABLE v_TABLE_NAME DISABLE PRIMARY KEY CASCADE;
ERROR at line 15:
ORA-06550: line 15, column 1:
PLS-00103: Encountered the symbol "ALTER" when expecting one of the following:
begin case declare exit for goto if loop mod null pragma
raise return select update while with <an identifier>
<a double-quoted delimited-identifier> <a bind variable> <<
close current delete fetch lock insert open rollback
savepoint set sql execute commit forall merge
<a single-quoted SQL string> pipe
ThanksWhen you want to perform ddl statements in a (anonymous) PL/SQL block, you have to use dynamic SQL because ddl is not possible in pl/sql.
Dynamic sql means that you sort of execute ddl statements in a sql manner. To use dynamic sql, two options exist:
- dbms_sql package : for oracle before 8i. To use this package is not always easy. Read about it carefully first before using.
- Native Dynamic SQL : implemented in 8i and very easy to use. An example would be :
declare
lv_statement varchar2(32676);
begin
lv_statement := 'ALTER TABLE MY_TABLE DISABLE CONSTRAINT MY_TABLE_CK1';
execute immediate lv_statement;
lv_statement := 'ALTER TABLE MY_TABLE ENABLE CONSTRAINT MY_TABLE_CK1';
execute immediate lv_statement;
end;
Good luck.
Edwin van Hattem -
Errors in alert log and listener log and "alter database mount exclusive"
Hello!
I need a help.
Database 11R2 works under MS Windows Server.
Whwn I start it using Services, according alert log it is started by command "alter database mount exclusive".
Next - alter database open.
After this, it seams that program, which should put data into database, can not work with it, because I see errors in alert log: ora-12537, 12560, 12535, 12570, 12547.
What does itmean and what to do?
This is extract from alert_log
ORACLE_BASE from environment = C:\Oracle
Mon Feb 04 14:54:53 2013
alter database mount exclusive
Successful mount of redo thread 1, with mount id 1458539517
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: alter database mount exclusive
alter database open
Thread 1 opened at log sequence 3105
Current log# 3 seq# 3105 mem# 0: C:\ORACLE\ORADATA\xxx\REDO03.LOG
Successful open of redo thread 1
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
SMON: enabling cache recovery
Successfully onlined Undo Tablespace 2.
Verifying file header compatibility for 11g tablespace encryption..
Verifying 11g file header compatibility for tablespace encryption completed
SMON: enabling tx recovery
Database Characterset is AL32UTF8
No Resource Manager plan active
Mon Feb 04 14:55:04 2013
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
Mon Feb 04 14:55:06 2013
QMNC started with pid=20, OS id=2860
Completed: alter database open
Mon Feb 04 14:55:11 2013
Starting background process CJQ0
Mon Feb 04 14:55:11 2013
CJQ0 started with pid=25, OS id=2000
Mon Feb 04 14:55:11 2013
db_recovery_file_dest_size of 4977 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Mon Feb 04 15:00:29 2013
Starting background process SMCO
Mon Feb 04 15:00:29 2013
SMCO started with pid=32, OS id=3212
Edited by: kogotok1 on Feb 4, 2013 4:54 PMThank you.
But in the same time - when I see in alert log those error messages ora -12560, 12537,12535,12570 and so on - clients programs, whiie try to connect, hang up.
For sql plus takes 20 minutes to connect.
lsnrctl status gives the following
LSNRCTL for 64-bit Windows: Version 11.2.0.1.0 - Production on 04-FEB-2013 16:01
:46
Copyright (c) 1991, 2010, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=xxx-BD.mosxxx
.elektra.net)(PORT=1521)))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for 64-bit Windows: Version 11.2.0.1.0 - Produ
ction
Start Date 01-FEB-2013 10:22:48
Uptime 3 days 5 hr. 39 min. 54 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File C:\Oracle\listener.ora
Listener Log File c:\oracle\diag\tnslsnr\xxx-BD\listener\alert\l
og.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=xxx-BD.mosxxx.elektra.net)
(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC1521ipc)))
Services Summary...
Service "CLRExtProc" has 1 instance(s).
Instance "CLRExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "XXX" has 2 instance(s).
Instance "XXX", status UNKNOWN, has 1 handler(s) for this service...
Instance "xxx", status READY, has 1 handler(s) for this service...
Service "XXXDB" has 1 instance(s).
Instance "xxx", status READY, has 1 handler(s) for this service...
The command completed successfully
To tell the truth I am confuse - I thought I have only 1 service "XXXDB" and 1 instance - "xxx".
May be I have wrong entries in tnslsnr.ora?
Maybe you are looking for
-
Not right colour when printing picture
a black and white picture is printed with a blue/green colour/haze, anybody any clue on how to solve? cartridges are oke. have them checked on the printer and in the store where i bought them. problem can exist since i installed hp software for the p
-
Hey people, This might be a stupid question but I'm just wondering what variables in java are initialized to if they are even initialized. Are they initialized and to what? The data types I'm talking about are int,boolean,String,byte,char which are t
-
BlackBerry 9220 trackpad is working intermittently
Hi BB Team, Good Day! I badly need your help as I can't use my phone that much.. My phone's trackpad suddenly not working. Therefore, I check all the forums and search for possible solutions. So far, Here are the things I have done.
-
Images won't open properly in cs6
I upgraded from cs5 to cs6 and my images are not opening properly in cs6. What can I do?
-
I uninstalled my desktop CC app because nothing happened when I try to launch it. How do I go about getting it downloaded and reinstalled?