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.
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?
Today i am facing an error when going to rezise the datafile its fixed size is 19000M abut after truncating all tables it is 112M, but when i am going to resize its datafile to 500M its get me an error ora-03297 file contain used data beyond requested size values.
I have done the same before a week without any error.But this time i got the error
My system tablespace size is 800mb and it sends an alert saying that it has exceeded 80% of its usage.However its total max size is 30gb.
FYI Its autoextensible is set to 'YES'. 2 Node RAC database. File system is ASM
My question here is... is it advicable to resize a system tablespace to some size when autoextensible is set to 'YES' or genrally can we resize a system tablespace when autoextensible is set to 'No' ?
SQL> col FILE_NAME format a40 SQL> / FILE_NAME BYTES/1024/1024 AUT MAXBYTES/1024/1024 ---------------------------------------- --------------- --- ------------------ +DATA/ge01114/datafile/system.556.2254454 800 YES 30000.9844
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
I have one generic question about space management. I have one table with size of 1TB. This table stored in ORC1 tablespace. This tablespace contains 70 datafiles.
Since it's 10.2.0.4 database. I have dropped this table by using purge
drop table <<table_name>> purge;
Once table drop was completed. When I check the tablespace space it was 100% free but due to HWM was unable to resize the datafile from current size to small size. What was the reason behind this. Is there any process needs to follow when dropping big tables ? like instead of dropping the tables do I need to truncate first & then drop .
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'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.
I want to re-size redo log group on my production database .i have 10 redo log groups of 50mb each having 2 members.i want 4 redo groups to be of 250 mb each having 2 members and then i will drop that old 10 redo log group(50 mb ) , so that i will have only 4 redo log group of 250MB each having 2 members.But i have physical standby and logical standby configured on production database .
find attached file for redo log configuration of production database(CBSPROD),Logical standby database(CBSMIS), Physical standby database(CBSDR).
I have a "prj_tbl" named tablespace in a user's schema in my database. i have given 100mb size to the "prj_tbl" at the time of its creation and auto extend is open for 10mb,and now this tablespace is using nearly 3.6mb space for its data and remaining space is free,now i want to reduce the size of "prj_tbl" tablespace to 20mb and when i tried to resize it then ,
It throws an error- "'ora-03297 file contains used data beyond requested resize value oracle"
I think this message showing that my new size is small than the size of data on my tablespace but it shows free space nearly 96mb then it means my new size is larger than the size of data on tablespace. How should I reduce the size..
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.
I have a small problem resizing an ASM disk group . I've had a lun with size 50G and added on it an asm disk called LUN1D1. Then I have created a DISK GROUP called data1 (external) witch contain LUN1D1. DATA1 was then made asm volume. So I have an asm volume with size 50G and I need it to be 100G.
Now I have increased the size of the lun with 50G (100G in total). I have rescanned the LUN and os see the new size. The problem is I can not re size DISK GROUP data1 or disk LUN1D1.
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 need to modify an existing form, thus I have to resize a canvas and a window for it. In windows, I run it and I got the right display. When I transfer it to dev server running in linux, then I compile and run it, it display the previous/unmodified size. I'm sure my form is the one that running, I placed some text there and it was displayed.
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.
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
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?
why can not we resize online redolog files instead of re-creating the same with large size and remove the older onces.2. How can we make RMAN obsolute backups as usable ?
I have a classic report generated by Oracle Apex 4.0. I have customized it to have a hyperlink on each record, which when clicked opens a detail report in an iframe right under the current record. This, I am doing by using the Javascript insertRow method on the html table element (Condensed Javascript code below)
var pTable= html_CascadeUpTill(t,'TABLE'); var myNewRow = pTable.insertRow(pTR.rowIndex+1); var myNewCell = myNewRow.insertCell(0); myNewCell.innerHTML = '<iframe src="detail report url" height="0"></iframe>';In order to resize the height of the iFrame that is different for different detail records, I have the following code in the "Execute when Page Loads" section of the report [code]........
Without the setTimeout call to iResize function, the iframe resize is not happening. But this setTimeout is adding a delay in the resized iframe to appear which I want to avoid. Is there a way to do this? All the related posts/articles I have seen online deal with iframes that are built into the page but not generated on-the-fly as in my case.
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)
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 want to configure row device to usable for creating new asm diskgroup.we are using ASM. Steps to configure that row device to available for creating new diskgroup.
