One of the Hitachi support guy has suggested to create a separate disk group for Online redo logs. His rationale was that ORLs was write only files and it would be better to put in a separate disk group.
I've been using ASM for a few years now and have always installed a new system with 3 diskgroups
+DATA - for datafiles, control files, redo logs +FRA - for achive logs, flash recovery. RMAN backup
Those I guess are the standards, but I've always created an extra (very small) diskgroup, called +ONLINE where I keep multiplexed copies of the redo logs and control files.
My reasoning behind this is that if there are any issues with the +DATA diskgroup, the redo logs and control files can still be accessed.
In the olden days (all those 5 years ago!), on local storage, this was important, but is it still important now? With all the striping and mirroring going on (both at ASM and RAID level), am I just being overtly paranoid? Does this additional +ONLINE diskgroup actually hamper performance? (with dual write overheads that are not necessary)
I've only successfully duplicate a standby database.
from the alert log
ORA-00313: open failed for members of log group 1 of thread 1 ORA-00312: online log 1 thread 1: 'D:ORA102CTAREDO01.LOG' ORA-27041: unable to open file OSD-04002: unable to open file O/S-Error: (OS 2) The system cannot find the file specified.
[code].....
when I tried to add the online and standby redo log, it error out
SYS@CTA>select logdetail.member, loggroup.group#, loggroup.sequence#, loggroup.archived, loggroup.status lg_status, logdetail.status ld_detail, logdetail.type 2 from v$log loggroup join v$logfile logdetail 3 on loggroup.group# = logdetail.group#; MEMBER -------------------------------------------------------------------------------- GROUP# SEQUENCE# ARC LG_STATUS LD_DETA TYPE ---------- ---------- --- ---------------- ------- -------
[code].....
based on my understanding from [URL] ....
Quote:
As part of the duplicating operation, RMAN automates the following steps:
Creates a control file for the duplicate database
Restores the target datafiles to the duplicate database and performs incomplete recovery by using all available incremental backups and archived redo logs
Shuts down and starts the auxiliary instance (refer to "Task 4: Start the Auxiliary Instance" for issues relating to client-side versus server-side initialization parameter files)
Opens the duplicate database with the RESETLOGS option after incomplete recovery to create the online redo logs (except when running DUPLICATE ... FOR STANDBY, in which case RMAN does not open the database) when duplicating for standby database it does not create online redo logs. Duplicating a standby database does not creates online redo logs.
how should I add the online and standby redo logs. If I transfer the redo logs from primary to standby, it always encountered the the following error
Dump file d:ora102ctadumpcta_arc0_3624.trc Tue Sep 13 19:21:53 2011 ORACLE V10.2.0.4.0 - Production vsnsta=0 vsnsql=14 vsnxtr=3 Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production With the OLAP, Data Mining and Real Application Testing options Windows XP Version V5.1 Service Pack 2
Although i have removed current online redo log file in linux os (Oracle Linux),when i type "commit" it says that "commit complete".
Is this fair for this princip?*:" if Only when all redo records associated with a given transaction are safely on disk in the online logs is the user process notified that the transaction has been committed."*
I think that it can lead to loss of data in some cases..I'm using Oracle 11g R2 on OEL (x64)..
P.S : I haven't multiplexed current ORL group files...
I got many times oracle ORA-00494 error and the database went down but since 29th of july the database have not been killed. The error message is below :
ORA-00494: mise en file d'attente [CF] d�tenue pendant trop longtemps ( (more than 900 seconds)) par inst 1, osid 176484 ORA-00028: votre session a �t� ferm�e
My database is used for datawarehouse of many terabytes.
Initially the redo log size was 500Mbytes and I've set it to 3Gbytes. The maximum log switch is after 5 minutes. I want log to be switched every 20 minutes or every 30 minutes.
To obtain the size of redo logs I've executed this query :
SQL> select OPTIMAL_LOGFILE_SIZE from v$instance_recovery;
OPTIMAL_LOGFILE_SIZE -------------------- 54763
53,5 Gbytes is it not very big as redo log size? What's the maximum size of redo log? To set very big redo log size what are the requirements? Which precautions should I take before? What are the risks? Are any other ways to change the log switch frequency?
I'm an Oracle novice and from what I've read so far, it seems that you should be able to do rollbacks and data recovery using the redo logs. I'm having a difficulty understanding the need for the undo tablespace.
it seems that you should be able to do rollbacks and data recovery using the redo logs. I'm having a difficulty understanding the need for the undo tablespace.
This morning when I checked my archive logs, I suprised that the redo files are generating after every 3 min and each of file size is 50M, which is the actual size of both log members. I m using RAC database with DR server.Usally the total redo logs quantity for one day is 4 to 5. but since 10 pm of yesterday to 7 am today, the quantity of log files are 109, each of 50 M .
I'm running Oracle 9i on AIX 5.2. I'm not using a recovery catalog, nor am I using media management software. I perform a full, online rman backup of the database and archived redo logs daily to disk, then use operating system commands to copy the backup to tape. There is only space on disk for two days' backups, so I need to have a retention policy of "redundancy = 1", and run a "delete obsolete" prior to the backup. The problem is that I don't want to subject the archived redo logs to this retention policy.
I have two physical standby databases connected by WAN to the primary site, and I might need archived redo logs that are a few days (or more) old in the event of a prolonged WAN outage. I've read about the "keep forever" option, but apparently it isn't available without using a recovery catalog. Is there any way to spare the archived redo logs from my retention policy?
Note: I want to "protect" the actual archived redo logs from the retention policy, not the backups of the archived redo logs.
URL....I'm practicing for the OCP test and one of the questions is that there is a backup from yesterday and the last archived logs are from the day before yesterday not mentioned if it's cold or hot backup.
If its a cold backup - cant we recover it? is it a must to have the archived redo logs also when recovering a cold backup? That sounds not logical since those logs are made only for a hot backup. URL.....
ORA-00202: control file: '+DATA/xa21/control01.ctl' ORA-17503: ksfdopn:2 Failed to open file +DATA/xa21/control01.ctl ORA-15001: diskgroup "DATA" does not exist or is not mounted ORA-15077: could not locate ASM instance serving a required diskgroup
The alert log +ASM instance, said:
ORA-27091: unable to queue I/O ORA-27070: async read/write failed OSD-04006: ReadFile() failure, unable to read from file O/S-Error: (OS 23) Data error (cyclic redundancy check).
I tried to resolve a physical error in file systems, with CHKDSK tool, unsuccessfully.
My exadata quarter rack machine has two asm diskgroups, DATA1 with 5TB and RECO with 3TB. I'd like to resize RECO to 1TB and DATA1 to 7TB.
I know ALTER DISKGROUP RESIZE command, but my question is about resize RECO volume from 3 to 1 TB: is it supported by Oracle?? Let me know risks /issues with this resize?
A am new in RAC configuration.I configuring RAC with ASM diskgroup with the external redundency. So now i am facing problem to mount the ASM diskgroup. I am giving the the RAC configuration description below.
1. using two node rac1 and rac2
2. asm disk configuration 3 drive /dev/raw/raw1 /dev/raw/raw2 /dev/raw/raw3 on both node
3. and i am using vmware to configure the both node asmdisk group
after configuring the os level and oracle clustring , i run dbca to configure asm disk group..so in the create disk screen i have found my previous create 3 disks
/dev/raw/raw1 /dev/raw/raw2 /dev/raw/raw3
so first two disks
/dev/raw/raw1 /dev/raw/raw2
i named it "dg1" then press ok , when i pressed ok a warring is appear that is "could not mount the diskgroup on remote node on rac2 using the connection service rac2:1521:+ASM2. Ensure that the listener is running on this node and the asm instance is registred to the listener. Receive the following error:
ORA-15032 : not all alterations performed ORA-15063 : ASM discovered insufficient number of disk for diskgroup "DG1"
as the same way i create another diskgroup "fg" for flash recovery area using disk /dev/raw/raw3
so after creating the two diskgroup i saw the two diskgroup is appere in the "diskgroup appere screen" an saw that only one diskgroup is mounted but not second node i.e. rac2 diskgroup is not mounted . What should i do no .
I've been ASM quite a while. I've two diskgroups extdg and nordg which are of external and normal redundancy respectively. Total diskgroup size is 9G, usuable space came down to 3mb when i tried to resize it to itz maximum. the value under usable column shows the same.
FYI... i've totally three disks in nordg, two in one failgroup and one in another.The disk sized equally 3g each.
I have an Oracle database 11.1.0.6 with ASM storage.
SQL> select * from v$version; BANNER -------------------------------------------------------------------------------- Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - 64bit Production PL/SQL Release 11.1.0.6.0 - Production CORE 11.1.0.6.0 Production TNS for Solaris: Version 11.1.0.6.0 - Production NLSRTL Version 11.1.0.6.0 - Production
There is a disk group named +FRA which has only 1 disk (call it disk 0 for later references).
+FRA disk group is in type of EXTERNAL redundancy
I'd like to add another disk to +FRA disk group and copy all files stored in disk 0 to the new disk (call it disk 1 for ex.), then take off disk 0 (not use for +FRA disk group any more).
Expected result: there is only one disk 1 left in the +FRA disk group, with all the data from disk 0 and keep their original file names
What is correct way to move the default oracle spfile to ASM diskgroup so i can successfully bring up the instance . After bring up the instance , it should point to ASM diskgroup. My oracle database 11.2.0.3 is siting on sun solaris 64 Bit.
We are implementing a 2 node RAC configuration with ASM on vmware and openfiler on LINUX RHEL 6.2. We started our installation with grid infrastructure. While executing root.sh on node 1 it gives error diskgroup cannot be mounted and no alterntions perfomed as below.
+[main] [ 2012-10-04 05:38:33.150 PDT ] [UsmcaLogger.logException:173] SEVERE:method oracle.sysman.assistants.usmca.backend.USMDiskGroupManager:mountDiskGroups+ +[main] [ 2012-10-04 05:38:33.151 PDT ] [UsmcaLogger.logException:174] ORA-15032: not all alterations performed+ ORA-15017: diskgroup "CRS" cannot be mounted
you have given 500gb of harddisk. how will u implement the size or how to assing the size for disks in the diskgroup.give me the best practice that is used in production
I added a new disk to a diskgroup. It starts to rebalance. However, I plan to drop the diskgroup anyhow and recreate it since I want to restore a database to it.(I shouldn't have added the new disk beforehand, my mistake) So now it's rebalancing and may take some hours.Can I drop the diskgroup now?I think there is no way to stop the rebalance?
When I try to start the database or ASM instance its showing the following error.
SQL> connect sys as sysdba Enter password: Connected to an idle instance. SQL> startup ORA-01078: failure in processing system parameters ORA-01565: error in identifying file '+FLASH_RECOVERY_AREA/XXXXX/spfileXXXXX.ora' ORA-17503: ksfdopn:2 Failed to open file +FLASH_RECOVERY_AREA/XXXXX/spfileXXXXXX.ora ORA-15077: could not locate ASM instance serving a required diskgroup SQL>
when am trying to view the data's by below Sql its show name as null for FLASH_RECOVERY_AREA. so I couldn't even set compatible ATTRIBUTE
SQL> select NAME , COMPATIBILITY, DATABASE_COMPATIBILITY from V$ASM_DISKGROUP; NAME COMPATIBILITY DATABASE_COMPATIBILITY ------------- ---------------------- ----------------------------------- RUBIKON_DATA 10.1.0.0.0 10.1.0.0.0
SQL> show parameter asm_disk NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ asm_diskgroups string RUBIKON_DATA, FLASH_RECOVERY_A REA asm_diskstring string /dev/mapper/Rubikon_data1, /dev/mapper/Rubikon_data2, /dev/mapper/Rubikon_fb
because of name is null mount mode as CLOSED and HEADER_STATUS as INCOMPATIBLE.
SQL> select name, mount_status, header_status,mode_status,state, path from v$asm_disk ; NAME MOUNT_S HEADER_STATU MODE_ST STATE PATH -------------- ------- ------------ ------- -------- ------------------------- CLOSED INCOMPATIBLE ONLINE NORMAL /dev/mapper/Rubikon_fb RUBIKON_DATA_0000 CACHED MEMBER ONLINE NORMAL /dev/mapper/Rubikon_data1 RUBIKON_DATA_0001 CACHED MEMBER ONLINE NORMAL /dev/mapper/Rubikon_data2
I'm new on 11g, due to my limit storage with mounted internal disk, so I think, may I can store archivelog in ASM without FRA? However, I did not find any document to verify.
Including order number, name and contact details (email, address, telephones) of customer and date the order was placed, order including product code, quantity ordered and cost charged; and Data on each product in the catalog including product code, name, description, unit price and category.
user to input information n number of order items (where 1 ≤ n ≤ 20) as parameters