Alter database register logfile
Hi,
I just setup a dr site for our client for R/3 production system.
I had two options to automatically apply the logfiles in standby system.
Option 1: Wrote a script to automate the archive from primary to standby and then apply on standby.
Option 2: Just moved the archive from primary to standby and fired the command alter database managed standby database;
Here i had to fire one more command on different sql session to register the archive on standby system. Registering log file has to be done for all archive logs.
Currently the standby system is running based on option1.
My question is,
why do i need to register these archive files?
Is there any way, this registration can be skipped?
Regards,
Iyyappan
Hello Iyyappan,
at first we have to clarify: A logical or a physical standby database?
For example:
If the primary database is unavailable, you have to perform the register manually.
It is described by the oracle dataguard concepts:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/log_transport.htm#i1148216
And take a look at here what a "gap" is:
http://www.dba-oracle.com/t_oracledataguard_37_archive_gap_sequence_.htm
Regards
Stefan
Similar Messages
-
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 -
Hi friends,
Oracle DB 9i
I am making a standby database backup (hi-brid), and keep updating every hour on top of the hour sked it with the archive logs generated.
I am just confused a little. If I have 3 logfiles, and if I command "alter database switch log files", does the 3 logfiles
be converted to the backup archive logs ? or only one of them only, and I have to issue the command 3x so that I will be able to get all the latest transaction inside the 3 redo logfiles to be applied at the standby server.
Thanks a lot,
Ms Indaycrystal wrote:
oh i see :D , so at any time there is one and only one redo log group that has data? all the other 2 are empty?not empty, but already archived. When an online redo log fills, there is an automatic switch to the next group. As soon as the switch is complete, the archiver will start archiving the group that was just filled. Archiving does not wait until all redo groups are filled.
=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2010.12.17 14:54:47 =~=~=~=~=~=~=~=~=~=~=~=
login as: oracle
oracle@vmlnx01's password:
Last login: Fri Dec 17 14:49:39 2010 from 192.168.160.1
[oracle@vmlnx01 ~]$ sqlplus / as sysdba
SQL*Plus: Release 10.2.0.4.0 - Production on Fri Dec 17 14:55:08 2010
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> select group#, archived, status from v$log order by 1;
alter system switch logfile;
GROUP# ARC STATUS
1 YES INACTIVE
2 YES INACTIVE
3 NO CURRENT
SQL>
System altered.
SQL> select group#, archived, status from v$log order by 1;
alter system switch logfile;
GROUP# ARC STATUS
1 NO CURRENT
2 YES INACTIVE
3 YES ACTIVE
SQL>
System altered.
SQL> select group#, archived, status from v$log order by 1;
alter system switch logfile;
GROUP# ARC STATUS
1 YES ACTIVE
2 NO CURRENT
3 YES ACTIVE
SQL>
System altered.
SQL> select group#, archived, status from v$log order by 1;
alter system switch logfile;
GROUP# ARC STATUS
1 YES INACTIVE
2 YES INACTIVE
3 NO CURRENT
SQL>
System altered.
SQL> select group#, archived, status from v$log order by 1;
alter system switch logfile;
GROUP# ARC STATUS
1 NO CURRENT
2 YES INACTIVE
3 YES ACTIVE
SQL>
System altered.
SQL> exit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
[oracle@vmlnx01 ~]$ exit
logout -
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. -
Alter database clear unarchived logfile group... who, what?
I am the sole DBA for our site, all of them running RHEL 5, Oracle 11.2.0.3.
I recently (within the last hour), received a text message from one of our databases that poll the alert.log...
ORA-1031 signalled during: ALTER DATABASE CLEAR UNARCHIVED LOGFILE GROUP 3
Unfortunately, the 'audit database' was not enabled (it is now!), and the trace file generated did not contain anything of use.
I know someone has been loading data since 1:30pm up until near the time I received this text, and I'm wondering if he is mucking in the system, or if this command can somehow be generated automatically by Oracle. If so, I certainly wouldn't expect an ORA-1031insufficient permissions error....
I checked my v$log, v$logfile, and did a log switch just to check if any possibility of redo log corruption, but all looks fine.
Has anyone else ever had random Oracle errors like this?....Hi,
That's someone manually doing something when they really don't know what they are doing. I've only had to run that command once in 16 years as a dba. Oracle wouldn't ever run that itself.
Cheers,
Harry -
ORA-301 Signalled during: ALTER DATABASE ...
Hi,
I tried to add 4 standby redologs to our standby setup, and first file went well.
theothers already got error ORA-301:
ALTER DATABASE ADD STANDBY LOGFILE GROUP 8 '/export/home/oracle/logs/redo8.log' SIZE 2G
Fri May 31 15:31:22 2013
Completed: ALTER DATABASE ADD STANDBY LOGFILE GROUP 8 '/export/home/oracle/logs/redo8.log' SIZE 2G
ALTER DATABASE ADD STANDBY LOGFILE GROUP 9 '/export/home/oracle/logs/redo9.log' SIZE 2G
ORA-301 signalled during: ALTER DATABASE ADD STANDBY LOGFILE GROUP 9 '/export/home/oracle/logs/redo9.log' SIZE 2G...
ALTER DATABASE ADD STANDBY LOGFILE GROUP 10 '/export/home/oracle/logs/redo10.log' SIZE 2G
ORA-301 signalled during: ALTER DATABASE ADD STANDBY LOGFILE GROUP 10 '/export/home/oracle/logs/redo10.log' SIZE 2G...
ALTER DATABASE ADD STANDBY LOGFILE GROUP 11 '/export/home/oracle/logs/redo11.log' SIZE 2G
ORA-301 signalled during: ALTER DATABASE ADD STANDBY LOGFILE GROUP 11 '/export/home/oracle/logs/redo11.log' SIZE 2G...
Fri May 31 16:33:39 2013
I tried to track any info in the web and metalink, but it's the first time I encounter an ORA error with no documentation... :(
Some facts:
The oracle is 11.2.0 on Linux
There is no space issue on disk
Thanks for any help/ideas...thanks for the reply.
first one I stated in the original post. there is tons of storage :)
for the others 2 -
user has priviledge... he created the first file succesfully...
those files do not exist on the disk already.
Thanks -
ORA-279 signalled during: ALTER DATABASE RECOVER automatic standby databas
Hi,
oracle server:8.1.7.0.0
os:solaris 5.9
we created standby server by taking coldbackup of primary server and we are using rsync to syschronize the archive log files between production and standby servers but every over we recover the standby server by executing
sql>recover automatic standby database:
but in alert log file i am getting the following error :
but when i googled for ora-279 error some people says it is default behaviour and can it be ignored and why it is asking next logfile.
Media Recovery Log /oratranslog/arch_1_1701118.arc
Wed Mar 26 21:35:34 2008
Media Recovery Log /oratranslog/arch_1_1701119.arc
Wed Mar 26 21:35:54 2008
Media Recovery Log /oratranslog/arch_1_1701120.arc
ORA-279 signalled during: ALTER DATABASE RECOVER automatic standby database...
Wed Mar 26 21:36:24 2008
ALTER DATABASE RECOVER CANCEL
Wed Mar 26 21:36:24 2008
Media Recovery Cancelled
Completed: ALTER DATABASE RECOVER CANCEL
Thanks and Regards
Prakash
juniour oracle dbadamorgan,
He is running 8.1.7.0. "DataGuard" scripts were initially available for 9i and then
backported (and available as a seperate download) for 8i. Many 8i implementations
did not and do not use DataGuard.
Even if it is "Jurassic" {which it certainly is NOT}, they obviously do have a good
reason for setting up a standby -- they DO have data of value. So, maybe they have
not upgraded to 9i or 10g. There could be a dozen reasons
1. Server HW/OS doesn't support 9i/10g, not budgetting for Server upgrade
2. Application using Forms 2.x or 4.5 and not tested on 9i / 10g (4.5 not certified
on 9i)
3. Low end client PCs working perfectly with Character-mode forms, not powerful
enought to run Jinitiator and Forms 6i / 9i
Just because someone hasn't upgraded to 10g doesn't mean that they are at fault
when you do NOT know the reason why they have not upgraded.
Surely, they do know that 8i is desupported. Don't you think that their management
has undertaken due diligence / cost-benefit analysis in considering whether they
should upgrade to 10g ?
Maybe they have another project implementing 10g in parallel and will be able
to shutdown this environment soon. Maybe they don't need to do so.
Do understand that people are intelligent enough to make their own decisions
considering their particular circumstances and don't go shooting off with your
assumption that anyone not running 10g is a dinosaur. -
Standby database errors - Alter database open read only
alter database open read only
AUDIT_TRAIL initialization parameter is changed to OS, as DB is NOT compatible for database opened with read-only access
Signalling error 1152 for datafile 1!
Beginning standby crash recovery.
Serial Media Recovery started
Managed Standby Recovery starting Real Time Apply
Media Recovery Waiting for thread 1 sequence 216
Mon Dec 20 11:58:18 2010
Standby crash recovery need archive log for thread 1 sequence 216 to continue.
Please verify that primary database is transporting redo logs to the standby database.
Wait timeout: thread 1 sequence 216
Standby crash recovery aborted due to error 16016.
Errors in file /u01/app/oracle/diag/rdbms/mdm2/MDM2/trace/MDM2_ora_17442.trc:
ORA-16016: archived log for thread 1 sequence# 216 unavailable
Recovery interrupted!
Completed standby crash recovery.
Signalling error 1152 for datafile 1!
Errors in file /u01/app/oracle/diag/rdbms/mdm2/MDM2/trace/MDM2_ora_17442.trc:
ORA-10458: standby database requires recovery
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '+MDMDG1/mdm2/datafile/system.280.738243341'
ORA-10458 signalled during: alter database open read only...
Mon Dec 20 12:13:46 2010
ALTER DATABASE RECOVER managed standby database using current logfile disconnect
Attempt to start background Managed Standby Recovery process (MDM2)
Mon Dec 20 12:13:46 2010
MRP0 started with pid=23, OS id=18974
MRP0: Background Managed Standby Recovery process started (MDM2)
started logmerger process
Mon Dec 20 12:13:51 2010
Managed Standby Recovery starting Real Time Apply
Parallel Media Recovery started with 2 slaves
Waiting for all non-current ORLs to be archived...
All non-current ORLs have been archived.
Media Recovery Waiting for thread 1 sequence 216
Completed: ALTER DATABASE RECOVER managed standby database using current logfile disconnect
The above lines are from alert log of standby database.
Standby standbase
SQL> alter database open read only;
alter database open read only
ERROR at line 1:
ORA-10458: standby database requires recovery
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '+MDMDG1/mdm2/datafile/system.280.738243341'
Parameters set on primary are
log_archive_dest_1 LOCATION=+MDMDG3/MDM1/ARCH VALID_FOR=(ALL_LOGFILES,ALL_ROLE ) DB_UNIQUE_NAME=MDM1
log_archive_dest_state_1 ENABLE
log_archive_dest_2 SERVICE=MDM2 SYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=MDM2
log_archive_dest_state_2 ENABLE
dg_broker_config_file1 +MDMDG2/mdm/dg_config/dgconfig1_mdm.dat
dg_broker_config_file2 +MDMDG2/mdm/dg_config/dgconfig2_mdm.dat
fal_server MDM2
standby_file_management AUTO
log_archive_config dg_config=(MDM1,MDM2)
db_file_name_convert MDM2, MDM1
ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE availability ;
Standby pfile
*.archive_lag_target=900
*.audit_file_dest='/u01/app/oracle/admin/MDM2/adump'
*.audit_trail='db'
*.compatible='11.2.0.0.0'
*.control_files='+MDMDG1/MDM2/CONTROLFILE/controlfile01.ctl','+MDMDG2/MDM2/CONTROLFILE/controlfile02.ctl'
*.db_block_size=8192
*.db_create_file_dest='+MDMDG1'
*.db_domain=''
*.db_file_name_convert='MDM1','MDM2'
*.db_name='MDM'
*.db_recovery_file_dest='+MDMDG2'
*.db_recovery_file_dest_size=10485760000
*.db_unique_name='MDM2'
*.dg_broker_config_file1='+MDMDG2/MDM/DG_CONFIG/dgconfig1_MDM.dat'
*.dg_broker_config_file2='+MDMDG2/MDM/DG_CONFIG/dgconfig2_MDM.dat'
*.diagnostic_dest='/u01/app/oracle'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=MDM2XDB)'
*.fal_server='MDM11','MDM12'
*.instance_name='MDM2'
*.log_archive_config='dg_config=(MDM1,MDM2)'
*.log_archive_dest_1='LOCATION=+MDMDG3/MDM2/ARCH VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=MDM2'
*.log_archive_dest_2='SERVICE=MDM1 ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=MDM1'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='ENABLE'
*.log_archive_format='MDM_%t_%s_%r.arc'
*.log_file_name_convert='MDM1','MDM2'
*.memory_target=838860800
*.nls_language='ENGLISH'
*.nls_territory='UNITED KINGDOM'
*.open_cursors=300
*.processes=500
*.remote_login_passwordfile='exclusive'
*.sessions=555
*.standby_file_management='AUTO'
*.undo_tablespace='UNDOTBS1'
On standby ASM
ASMCMD [+] > find * *
+MDMDG1/ASM/
+MDMDG1/ASM/ASMPARAMETERFILE/
+MDMDG1/ASM/ASMPARAMETERFILE/REGISTRY.253.737811541
+MDMDG1/MDM/
+MDMDG1/MDM2/
+MDMDG1/MDM2/CONTROLFILE/
+MDMDG1/MDM2/CONTROLFILE/controlfile01.ctl
+MDMDG1/MDM2/CONTROLFILE/current.265.738243333
+MDMDG1/MDM2/DATAFILE/
+MDMDG1/MDM2/DATAFILE/CANVAS_POPULARITY_DATA.264.738243343
+MDMDG1/MDM2/DATAFILE/CANVAS_POPULARITY_IDX.277.738243343
+MDMDG1/MDM2/DATAFILE/MDM_SRC_DATA.282.738243343
+MDMDG1/MDM2/DATAFILE/MDM_SRC_IDX.275.738243343
+MDMDG1/MDM2/DATAFILE/MIPS_MDM_DATA.283.738243341
+MDMDG1/MDM2/DATAFILE/MIPS_MDM_IDX.276.738243343
+MDMDG1/MDM2/DATAFILE/SYSAUX.281.738243341
+MDMDG1/MDM2/DATAFILE/SYSTEM.280.738243341
+MDMDG1/MDM2/DATAFILE/TEST_TBSP1.273.738243345
+MDMDG1/MDM2/DATAFILE/TEST_TBSP2.272.738243345
+MDMDG1/MDM2/DATAFILE/UNDOTBS1.256.738243343
+MDMDG1/MDM2/DATAFILE/UNDOTBS2.279.738243343
+MDMDG1/MDM2/DATAFILE/USERS.278.738243347
+MDMDG1/MDM2/ONLINELOG/
+MDMDG1/MDM2/ONLINELOG/group_1.259.738243429
+MDMDG1/MDM2/ONLINELOG/group_2.257.738243431
+MDMDG1/MDM2/ONLINELOG/group_21.284.738243505
+MDMDG1/MDM2/ONLINELOG/group_22.261.738243505
+MDMDG1/MDM2/ONLINELOG/group_23.274.738243505
+MDMDG1/MDM2/ONLINELOG/group_3.258.738243431
+MDMDG1/MDM2/ONLINELOG/group_31.262.738243513
+MDMDG1/MDM2/ONLINELOG/group_32.270.738243513
+MDMDG1/MDM2/ONLINELOG/group_33.263.738243513
+MDMDG1/MDM2/ONLINELOG/group_4.260.738243431
+MDMDG2/MDM/
+MDMDG2/MDM/DG_CONFIG/
+MDMDG2/MDM2/
+MDMDG2/MDM2/AUTOBACKUP/
+MDMDG2/MDM2/AUTOBACKUP/2010_12_20/
+MDMDG2/MDM2/AUTOBACKUP/2010_12_20/s_738242861.263.738244155
+MDMDG2/MDM2/CONTROLFILE/
+MDMDG2/MDM2/CONTROLFILE/controlfile02.ctl
+MDMDG2/MDM2/CONTROLFILE/current.271.738243335
+MDMDG2/MDM2/ONLINELOG/
+MDMDG2/MDM2/ONLINELOG/group_1.270.738243429
+MDMDG2/MDM2/ONLINELOG/group_2.269.738243431
+MDMDG2/MDM2/ONLINELOG/group_21.268.738243505
+MDMDG2/MDM2/ONLINELOG/group_22.272.738243505
+MDMDG2/MDM2/ONLINELOG/group_23.262.738243505
+MDMDG2/MDM2/ONLINELOG/group_3.273.738243431
+MDMDG2/MDM2/ONLINELOG/group_31.266.738243513
+MDMDG2/MDM2/ONLINELOG/group_32.265.738243513
+MDMDG2/MDM2/ONLINELOG/group_33.264.738243513
+MDMDG2/MDM2/ONLINELOG/group_4.261.738243431
+MDMDG3/MDM/
+MDMDG3/MDM/ARCH/
+MDMDG3/MDM2/
+MDMDG3/MDM2/ARCH/
-- Please can I know how to open read only standby database.user5846399 wrote:
ORA-16016: archived log for thread 1 sequence# 216 unavailable
Recovery interrupted!archived log for thread 1 sequence# 216
This file is needed for recovery, Find it and move it to the standby database side. -
First-time install on a SBS 2011 server, name replaced as <SERVER> for this post. I had created a separate IIS site rather than using the Default Web Site and I am guessing this might be a permission issue on the folder...
Installation failed with Event ID 110 and a repeating error that states, "<Error>: Attempt to configure Active Directory Rights Management Server failed. The provisioning process failed to create the Configuration database due to the following
error from Sql Server: System.Data.SqlClient.SqlException: ALTER DATABASE failed because a lock could not be placed on database 'DRMS_Config_adrms_<SERVER>_local_443'. Try again later. ALTER DATABASE statement failed. ALTER DATABASE failed because a
lock could not be placed on database ." Configuration as follows:
<Informational>: This server might need to be restarted after the installation completes.
Active Directory Rights Management Services
Cluster Type
Root cluster
Trust Hierarchy
Production
Configuration Database Server
Windows Internal Database
Service Account
<SERVER>\adrms
Cluster Key Storage
AD RMS centrally managed key storage
Cluster Web Site
Active Directory RMS
Cluster Internal Address
https://adrms.<SERVER>.local:443/
SSL Certificate
Create a self-signed certificate
Licensor Certificate Name
<SERVER>
Register SCP
Register nowHi Ahmad, I have the same problem, I have a server windows server 2008 R2 standard. While
doing an Enterprise to Standard downgrade, I have removed enterprise edition of SQL Server 2008, rebooted and while installing standard edition, I get the below error saying "You SQL server 2008 installation completed with failures. Some or all identity
references could not be translated"
Bit of background. This server has another express instance of SQL Server 2008. I have
used local system account, network service as well as our general SQL service account, but I get the error towards the end of the installation and it fails saying “Some or all identity references could not be translated.”
I am installing a named instance with the same name as before but fails. I have tried
creating a new test instance that fails too. Any ideas? I have uninstalled SQL enterprise edition from
Add and Remore Programs/Programs and Features. I've also run the Windows Installer CleanUp Utility but no joy.
Cheers -
Did anyone have seen this behavior?
DB version : 11.1.0.7
OS : HP-UX Itanum
EBS -11.5.10.2
We are doing daily refresh/clone of a database instance from production. Recently we are seeing the growth of $ORACLE_HOME/dbs directory during this
refresh. During investigation we find out that
1) When we rename the database files after database restoration. Each below command genrating the 24MB of log file under $ORACLE_HOME/dbs.
Command :
alter database rename file '/db02/prod/XDB.dbf' to '/db02/test/XDB.dbf';
alter database rename file '/db02/prod/a_archive01.dbf' to '/db02/test/a_archive01.dbf';
Logfiles under $ORACLE_HOME/dbs on target :
-rw-r----- xxxxx 24379392 Sep 20 05:30 ./dbs/c-1437102747-20130920-02
-rw-r----- xxxxx 24379392 Sep 20 05:30 ./dbs/c-1437102747-20130920-03
2) After few minutes, these logs got removed from the directory.
3) Did not find anything unusual in the alert log.These are controlfile autobackups. Every time you make a physical change to the database structure, an autobackup is created. In 11.2, the frequency is reduced -- for example if you make 5 changes in quick succession, one autobackup is created.
CONTROLFILE AUTOBACKUP ON would be visible when you do a SHOW ALL in rman.
Hemant K Chitale -
Alter database create datafile as
Hi
T1-)shutdown immediate;
T2-)Take full backup
T3-)startup;
T4-)move the objects in tablespace test1 to some other tablespace
T5-)drop tablespace test1;
T6-)create tablespace test1
datafile 'C:\oraclexe\oradata\XE\test1.dbf' reuse;
T7-)alter system switch logfile;
In some other server;
startup nomount;
restore the backupset which was taken at T2.
restore controlfile at T7.
startup mount;
alter database create datafile 'C:\oraclexe\oradata\XE\test1.dbf' as 'C:\oraclexe\oradata\XE\test1.dbf';
ALTER DATABASE RECOVER automatic database until cancel using backup controlfile;
Recovery performed succefully.
What I wanna ask is;
Since First I issue:
"alter database create datafile as ...."
The contents of this datafile should be deleted with this statement.
Why oracle doesnt give error in recovery, during appliying the statement at T4 ?
I have already deleted the contents of the datafile, how come oracle move the objects?
I hope I am clearHi,
although it is beyound my imagination what kind of real world scenario you are trying to simulate with your test, I can tell you why no error gets returned:
You create a new tablespace t1 after you dropped the old one. That gets stored in the current controlfile. The previous backup of the datafile of the old tablespace that incidentally has the same name is now useless for the new tablespace.
You then restore that controlfile and create the datafile manually as it looked after you created the new tablespace (empty) and then recover that. RMAN does that (without complaining even about the uselessness of your doing). If you look into that tablespace, you will see that it is empty as it was after you created it - unless you have put any objects into it after the second creation of that tablespace t1.
Kind regards
Uwe
http://uhesse.wordpress.com -
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 -
Hi all,
As Oracle says, this command "lets you explicitly force Oracle Database to begin writing to a new redo log file group". But, how does Oracle Database 10g choose which redo log file group will be used next?
I faced a situation where it follows a strange pattern:
SQL> alter system switch logfile;
System altered.
SQL> select f.GROUP#, f.MEMBER, l.BYTES/1024/1024 MB, l.STATUS from v$logfile f, v$log l where f.group# = l.group#;
GROUP# MEMBER MB STATUS
1 /redologs/MYDB/redoMYDB01.log 800 INACTIVE
2 /redologs/MYDB/redoMYDB02.log 800 INACTIVE
3 /redologs/MYDB/redoMYDB03.log 800 INACTIVE
4 /redologs/MYDB/redoMYDB04.log 800 ACTIVE
5 /redologs/MYDB/redoMYDB05.log 800 ACTIVE
6 /oradata/dbf1/MYDB/redoMYDB06.log 800 INACTIVE
7 /oradata/dbf1/MYDB/redoMYDB07.log 800 INACTIVE
8 /oradata/dbf1/MYDB/redoMYDB08.log 800 INACTIVE
9 /oradata/dbf1/MYDB/redoMYDB09.log 800 INACTIVE
10 /oradata/dbf1/MYDB/redoMYDB10.log 800 INACTIVE
11 /oradata/dbf1/MYDB/redoMYDB11.log 800 INACTIVE
12 /oradata/dbf1/MYDB/redoMYDB12.log 800 INACTIVE
13 /oradata/dbf1/MYDB/redoMYDB13.log 800 INACTIVE
14 /oradata/dbf1/MYDB/redoMYDB14.log 800 INACTIVE
15 /oradata/dbf1/MYDB/redoMYDB15.log 800 INACTIVE
16 /oradata/dbf1/MYDB/redoMYDB16.log 800 CURRENT
16 rows selected.
SQL> alter system switch logfile;
System altered.
SQL> select f.GROUP#, f.MEMBER, l.BYTES/1024/1024 MB, l.STATUS from v$logfile f, v$log l where f.group# = l.group#;
GROUP# MEMBER MB STATUS
1 /redologs/MYDB/redoMYDB01.log 800 INACTIVE
2 /redologs/MYDB/redoMYDB02.log 800 INACTIVE
3 /redologs/MYDB/redoMYDB03.log 800 INACTIVE
4 /redologs/MYDB/redoMYDB04.log 800 ACTIVE
5 /redologs/MYDB/redoMYDB05.log 800 ACTIVE
6 /oradata/dbf1/MYDB/redoMYDB06.log 800 CURRENT
7 /oradata/dbf1/MYDB/redoMYDB07.log 800 INACTIVE
8 /oradata/dbf1/MYDB/redoMYDB08.log 800 INACTIVE
9 /oradata/dbf1/MYDB/redoMYDB09.log 800 INACTIVE
10 /oradata/dbf1/MYDB/redoMYDB10.log 800 INACTIVE
11 /oradata/dbf1/MYDB/redoMYDB11.log 800 INACTIVE
12 /oradata/dbf1/MYDB/redoMYDB12.log 800 INACTIVE
13 /oradata/dbf1/MYDB/redoMYDB13.log 800 INACTIVE
14 /oradata/dbf1/MYDB/redoMYDB14.log 800 INACTIVE
15 /oradata/dbf1/MYDB/redoMYDB15.log 800 INACTIVE
16 /oradata/dbf1/MYDB/redoMYDB16.log 800 ACTIVE
16 rows selected.
Thanks!Oracle doesn't use the GROUP# to identify the "next" redo log.
It switched from Group#16 to Group#6. This would happen if, in the past, Group#6 was added to the database when Group#16 was the CURRENT redolog. At that time, the next SWITCH from Group#16 would have caused it to switch from Group#16 to the "newest" UNUSED group -- Group#6. Thereafter, Oracle persists with the behaviour of switching from Group#16 to Group#6.
Hemant K Chitale -
ORA-1624 signalled during: ALTER DATABASE CLEAR....
Hi,
I get this error in my alert file what it means?
ORA-1624 signalled during: ALTER DATABASE CLEAR UNARCHIVED LOGFILE GROUP 1...
Thanks
Edited by: vittel on Sep 3, 2008 1:28 PM
Edited by: vittel on Sep 3, 2008 1:29 PMHi,
First thanks for your quick response.
The only thing that we have running in the database is a scheduled program how run every 3 min to switch the current log and he applied the archive log to the standby database!!!
It can be a session how is trying to do this "Alter database clear unarchived logfile...." ?
Thanks -
Register logfile manually in asm.
Hi,
My primary databse is on file system having 10.2.0.5 db version.
My standby db is on ASM(11.2.0.2)
Operating system is Windows 2003.
somehow My standby database is not able to capture archivelogs from primary database.
so i want to manually transfer missing archivelogs on standby datbase server and want to manually register the missing archivelogs.
But as my primary db is in file system and standby db is in asm. how i can copy my missing archivelogs in asm diskgroups.
So please let me know wht are the steps to register logfile manually in asm.919131 wrote:
Hi,
My primary databse is on file system having 10.2.0.5 db version.
My standby db is on ASM(11.2.0.2)
Operating system is Windows 2003.
somehow My standby database is not able to capture archivelogs from primary database.
so i want to manually transfer missing archivelogs on standby datbase server and want to manually register the missing archivelogs.
But as my primary db is in file system and standby db is in asm. how i can copy my missing archivelogs in asm diskgroups.
So please let me know wht are the steps to register logfile manually in asm.Use this link to move Archive files from ASM to normal file system --> http://repettas.wordpress.com/2008/11/01/restore-archive-logs-to-new-location-using-rman/
>
919131
Newbie
Handle: 919131
Status Level: Newbie
Registered: Mar 6, 2012
Total Posts: 13
Total Questions: 7 (7 unresolved)
>
OTN is not helpful to you to resolve your questions, all questions are unanswered, when all questions are unanswered why you are posting here?
Close all old threads and keep the forum clean.
Edited by: CKPT on Jul 3, 2012 6:48 PM
Maybe you are looking for
-
Print driver is not shown in "Print Using:" menu
I have a HP psc 2410 printer that I have connected directly to my Mac, but I want to connect it though my Windows PC which is my home server. The printer works fine when it is connected via the USB cable and the driver listed after "Print Using:" in
-
Getting my hands on some mac equipment
Hello everyone. I earlier posted about an Intel iMac for a friend of mine who had a question. You guys were great and helped, so I want to ask again. This time I'm thinking of getting my own mac. I've wanted them for a long time now, but never could,
-
Hi All, I have set item group discount using discount groups (module inventory --> price lists --> special prices --> discount groups) form but how to see the discount group result in the B1 and not using query report ? Pls give advice. TIA Rgd, Stev
-
When is Apple gonna release a patch for iTunes to sync apps?
I already bought the apps the day it first came out and i can't even sync the january software upgrade to my ipod touch. i'm not about to re-sync my ipod and lose all my music just for 5 little apps. i refuse to do that. i wanna know when apple is go
-
Without data element can we create table
without data element is it possible to create table if it is possible how ? could u plz expain steps.