I want to delete my export files daily from ASM diskgroup with a crontab job. I want to prepare a script for it. ASMCMD> ls exp1.dmp exp2.dmp exp3.dmp exp4.dmp ASMCMD> pwd +DATA/EXP How can I prepare this script? I prepared a template for it, but I couldn't script it.

set_gridenv
asmcmd
cd +DATA/EXP
rm -rf exp*.dmp
exit

I have an Oracle database 11gr2 and I have installed Oracle Grid on Oracle Linux 5.9. I have two disk groups. /etc/init.d/oracleasm listdisks : flash_recovery_area DATA The first disk group is mounted on /u01 and the second is mounted on /flash_recovery_area. The value of fra parameters are: db_recovery_file_dest = /+flash_recovery_area db_recovery_file_dest_size = 30G When I want to connect to rman and get backup from current database, I can but I can not find anything in /flash_recovery_area destination. Can any one help me?

I have an Oracle database 11gr2 and I want to install Oracle Grid on Oracle Linux 6.4. At first, I have installed Oracle Grid with the tutorial on this website: https://eudba.wordpress.com/2012/08/10/installing-oracle-11g-on-oracle-linux-6-with-asm-eng/ When the grid installation is finished, I have an error that says: "the Oracle grid service can not start". When I want to install the database with oracle user and with ASM, I have an error that I attached it to this question. Can any one help me?

I'm working somewhere now where every ASM diskgroup has been made with an extra disk under the QUORUM FAILGROUP option, and is built with the following pattern:

CREATE DISKGROUP stuffdg NORMAL REDUNDANCY
  FAILGROUP x DISK 'AFD:X' SIZE 30G
  FAILGROUP y DISK 'AFD:Y' SIZE 30G
  FAILGROUP z ...
  QUORUM FAILGROUP qrm DISK '/nfsmp/stuffdgdisk' SIZE 1G
  ATTRIBUTE ...;

But on all clusters they have over here, there's also a diskgroup whose sole purpose is to host OCR, voting files, ASM instance spfile etc. This diskgroup (let's call it +OCRDG...) is *also* built upon a similar shared drive visible at OS level (along with two regular ASM disks configured with AFD). Verifying this with CRSCTL QUERY CSS VOTEDISK you're shown the following:

[oracle@~]$ crsctl query css votedisk
##  STATE    File Universal Id                File Name Disk group
--  -----    -----------------                --------- ---------
 1. ONLINE   2b07d0a959d14fcbbf891f99e3bade87 (AFD:OCRDGD1) [VOTE]
 2. ONLINE   8943a8f2a8c64fc4bfaae430f45bc58d (AFD:OCRDGD2) [VOTE]
 3. ONLINE   1f166e30237a4f54bfabeb8d0ed63786 (/nfsmp/ocrdgd3) [VOTE]
Located 3 voting disk(s).

Listing all files under /nfsmp shows that since their creation, *only* /nfsmp/ocrdgd3 is used, all other files (like stuffdgdisk above) have kept the timestamp of their creation, months ago. My question: I've never used this configuration before (explicitly adding a quorum failgroup in regular diskgroups - I mean those used for data and archived logs destination or FRA), and obviously these files under /nfsmp (except for that which is used for OCR) are not used, so what is the point of this QUORUM FAILGROUP clause?? I've found the documentation very little helpful to understand this setup. Can someone enlighten me please? Thanks a lot. Regards, Seb

I have a recently made physical dataguard configuration and everything works correctly so far, but I've noticed that the datafiles that are created in the primary are created in the standby in a different route, the environment is as follows: Primary - db_name: oradb, db_unique_name: oradb. Oracle 11gR2. ASM storage. Diskgoups: SYS, SYS2 and DATA Standby - db_name: oradb, db_unique_name: oradb2. Oracle 11gR2. ASM storage. Diskgoups: SYS, SYS2 and DATA. When creating a tablespace in the primary, example: CREATE TABLESPACE TBS_DATA DATAFILE '+DATA' SIZE 50M AUTOEXTEND ON NEXT 1M MAXSIZE 100M ... the respective datafile is created in the diskgroup DATA ... +DATA/oradb/datafile/tbs_data... all good, the doubt that I have is that I realized that in the Standby database the datafile is created in the diskgroup SYS +SYS/oradb2/datafile/tbs_data... , what should I do to create the datafiles in the correct path, that is +DATA/oradb2/datafile/tbs_data...? Thank you very much in advance

I am not able to get a new disk in the moment and I was woldering if it's possible to share a disk between two diskgroup. I have a FRA diskgroup with a disk of 200gb and I need to add 100gb in DATA diskgroup. I have limited FRA disk to 100g: alter diskgroup FRA resize all size 100g; Then, the free space would be allocated in nother diskgroup (DATA). Is there a way to do it in ASM? I have tried in my lab, but I get the error: alter diskgroup DATA add disk 'ORCL:DATA_STB3' size 100g; (ORCL:DATA_STB3 is the disk where now I have 100gb free). ERROR at line 1: ORA-15032: not all alterations performed ORA-15029: disk 'ORCL:DATA_STB3' is already mounted by this instance If it's not possible, why can we limit ASM disk size? what situation this command is userful?

I've been supporting a lot of Oracle databases (not full-time; I'm a programmer 90% of the time) and I just happened to see in the Oracle 19 Linux Installation document that storing Oracle data files on a local file system is not recommended. All the databases I've been supporting have the data on a local file system. We are setting up a new server that has 5 internal drives; 2 small drives for the operating system, and 3 large (four terabyte) drives. So, seems like I could do what I'm familiar with, set up RAID 5 on the 3 large drives, pointing to /u01. Or, set up ASM on those drives. I played with ASM maybe 10 years ago, so I'm not terribly familiar with it. For this new server, a data center DBA group will be setting this up and maintaining it. So I'm basically wondering if there are any things I need to be aware of when setting this up with data on ASM. And also, for our existing databases, how important is it to migrate from local Linux file system to ASM.

I have the following question regarding the allocation of disks or LUNs to ASM in Oracle, specifically, I have an Oracle 18c DB in Cluster and I have created several diskgroups, now, I need to increase the size of the data diskgroup to which I only present a LUN of say 300 GB, it turns out that I have realized that it is not enough because the data volume will increase considerably, and I need at least 2 tb at the moment, I would like to know that it is recommended in these cases, to present a LUN of 2 TB, several of 300 GB ...??? My storage is completely integrated by NVMe SSD disks. Thank you very much

Oracle RAC 11.2 with asm storage, all type = EXTERN redundancy. I've been cleaning up some tablespaces and shrinking datafiles back down to sizes that they're not likely to grow much larger than (processes no longer used had blown them up). The sum of the bytes of datafiles from dba_data_files reflects this shrink, however, USED_MB in v$asm_diskgroup has not fallen and it doesn't match to what adding up the datafiles bytes is? What would account for this difference? We typically use v$asm_diskgroup to monitor if we're running low on space but this doesn't *appear* to be correct. SELECT name group_name , type type , total_mb total_mb , (total_mb - free_mb) used_mb , ROUND( (SELECT SUM(bytes)/1024/1024 FROM dba_data_files WHERE file_name LIKE '+DATA02%' ),0) AS datafile_used FROM v$asm_diskgroup w WHERE name = 'DATA02' GROUP_NAME TYPE TOTAL_MB USED_MB DATAFILE_USED ______________________________________ DATA02 EXTERN 542712 516902 506447

After patching GI Home and DB Home simultaneously using command: .oraenv +ASM1 opatchauto apply /patchlocation Should i run ./datapatch from DB home or GI home? Or it doesn't matter from which home? Thanks

I would like to know if there could be a problem when naming a datafile with spaces in the name, I have an Oracle 11gR2 database, using ASM as storage, a datafile was created, belonging to an application's tablespace, with a name that contains spaces: "+DATA/oracl/data/**my new dtf**" that is, the name of the tablespace is: **my new dtf**, it was created without problems, but I have doubts that it could cause a conflict.

I need to add an extra Port: 1522 Listener Parameter File /u01/app/19.0.0.0/grid/network/admin/listener.ora Listener Log File /u01/app/grid/diag/tnslsnr/xxxx/listener/alert/log.xml Listening Endpoints Summary... (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=LISTENER))) (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=xxxx)(PORT=1521))) Services Summary... Service "xxxx" has 1 instance(s). /u01/app/19.0.0.0/grid/network/admin/listener.ora-> LISTENER=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=ipc)(KEY=LISTENER)))) # line added by Agent ASMNET1LSNR_ASM=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=IPC)(KEY=ASMNET1LSNR_ASM)))) # line added by Agent ENABLE_GLOBAL_DYNAMIC_ENDPOINT_ASMNET1LSNR_ASM=ON # line added by Agent VALID_NODE_CHECKING_REGISTRATION_ASMNET1LSNR_ASM=SUBNET # line added by Agent ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER=ON # line added by Agent VALID_NODE_CHECKING_REGISTRATION_LISTENER=SUBNET # Every time I edit the listener.ora The listener fails to start: I tried: LISTENER = (DESCRIPTION_LIST = (DESCRIPTION = (ADDRESS = (PROTOCOL = IPC)(KEY = LISTENER)) (ADDRESS = (PROTOCOL = TCP)(HOST = xxxx)(PORT = 1521)) (ADDRESS = (PROTOCOL = TCP)(HOST = xxxx)(PORT = 1522)) ) ) ASMNET1LSNR_ASM=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=IPC)(KEY=ASMNET1LSNR_ASM)))) # line added by Agent ENABLE_GLOBAL_DYNAMIC_ENDPOINT_ASMNET1LSNR_ASM=ON # line added by Agent VALID_NODE_CHECKING_REGISTRATION_ASMNET1LSNR_ASM=SUBNET # line added by Agent ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER=ON # line added by Agent VALID_NODE_CHECKING_REGISTRATION_LISTENER=SUBNET # line added by Agent srvctl start listener PRCR-1079 : Failed to start resource ora.LISTENER.lsnr CRS-5016: Process "/u01/app/19.0.0.0/grid/bin/lsnrctl" spawned by agent "ORAAGENT" for action "start" failed: details at "(:CLSN00010:)" in "/u01/app/grid/diag/crs/xxxx/crs/trace/crsd_oraagent_grid.trc" Listener failed to start. See the error message(s) above... 2021-02-17 15:32:19.462 :CLSDYNAM:2613040896: [ora.LISTENER.lsnr]{1:35727:65428} [start] (:CLSN00010:)Utils:execCmd scls_process_join() uret 1 2021-02-17 15:32:19.462 :CLSDYNAM:2613040896: [ora.LISTENER.lsnr]{1:35727:65428} [start] clsnUtils::error Exception type=2 string= CRS-5016: Process "/u01/app/19.0.0.0/grid/bin/lsnrctl" spawned by agent "ORAAGENT" for action "start" failed: details at "(:CLSN00010:)" in "/u01/app/grid/diag/crs/etabonxrdbs0010/crs/trace/crsd_oraagent_grid.trc" 2021-02-17 15:32:19.463 : AGFW:2610939648: [ INFO] {1:35727:65428} Agent sending reply for: RESOURCE_START[ora.LISTENER.lsnr etabonxrdbs0010 1] ID 4098:1355034 2021-02-17 15:32:19.463 :CLSDYNAM:2613040896: [ora.LISTENER.lsnr]{1:35727:65428} [start] LsnrAgent::Lsnrctl::start lsnrctl start complete lsnrname:LISTENER output: LSNRCTL for Linux: Version 19.0.0.0.0 - Production on 17-FEB-2021 15:32:19 Copyright (c) 1991, 2020, Oracle. All rights reserved. ... 2021-02-17 18:19:34.200 :CLSDYNAM:2606737152: [ora.LISTENER.lsnr]{1:35727:1260} [check] clsnUtils::error Exception type=2 string= CRS-5020: Not all endpoints are registered for listener LISTENER I tried: srvctl modify listener -p "TCP:1521/TCP:1522"; srvctl config listener Name: LISTENER Type: Database Listener Network: 1, Owner: grid Home: End points: TCP:1521, 1522 Listener is enabled. Listener is individually enabled on nodes: Listener is individually disabled on nodes:

I have an Oracle Database instance installed under an OL7. It is a 12c2. Oracle GI also installed and my database has some files stored in ASM. I am using sqlplus to connect to the database instance and query v$asm_diskgroup. My ORACLE_HOME points to the home of my database instance. When I connect without specifying a "@CONNECTION" (e.g using: sqlplus user/name), then the view v$asm_diskgroup returns no rows. When I connect specifying a @TNSNAME (e.g: sqlplus user/name@TNSNAME ), then the view v$asm_diskgroup returns data correctly. Also, when I connect using sql developer, from another machine, the v$asm_diskgroup returns the rows. Why are no v$asm_diskgroup rows returned when I use sqlplus without @CONNECTION, that is, the default logon?

I'm trying to install oracle grid with asm filter driver. I've already installed grid software only. As root, I can't start asm. Actually, I don't have any answer from asmcmd filter driver commands: root@srvdb18c:/u01/app/18.0.0/grid/bin# env|grep ORACLE ORACLE_BASE=/u01/app/grid ORACLE_HOME=/u01/app/18.0.0/grid root@srvdb18c:/u01/app/18.0.0/grid/bin# ./asmcmd afd_configure root@srvdb18c:/u01/app/18.0.0/grid/bin# root@srvdb18c:~# $ORACLE_HOME/bin/asmcmd afd_state root@srvdb18c:~# What can be the problem? Important: it's a Solaris 11 system.

In my envoriment I am getting the following erro: ORA-15032: not all alterations performed ORA-15017: diskgroup "OCR" cannot be mounted ORA-15040: diskgroup is incomplete The problem is: I already has droped this diskgroup (I've changed the OCR diskgroup to another diskgroup OCR_NEW). I have two instances, in the first instance it's everything ok, but in the second instance I get this erro. Where can be the problem? I didn't find anything. I already tried to disable before to try remove in srvctl command, but not work as well. [oracle@server2 trace]$ srvctl disable diskgroup -diskgroup OCR PRCA-1000 : ASM Disk Group OCR does not exist PRCR-1001 : Resource ora.OCR.dg does not exist

I have a bunch of asmdisks: /dev/oracleasm/disks/DATA01 /dev/oracleasm/disks/DATA02 .. /dev/oracleasm/disks/DATA07 Probably, they were created as: oracleasm createdisk DATA01 /dev/sda1 oracleasm createdisk DATA01 /dev/sda2 But I'm not sure. How to define relied block device for created ASM disk? How to be sure that DATA01 is made of /dev/sda1?

I have Oracle Linux running on vmware hosting an Oracle database with ASM (single instance). There isn't any operating system device persistence and therefore whenever my OS reboots, the disk number changes and ASM doesn't mount the disks even after I set diskstring parameter. I do not have OS multipathing since I have multipath on storage. Disks are configured using asmlib only. I understand asmlib was introduced to ease the management of disks (addition of disks to the cluster) but wasn't it also designed to prevent this from happening? How can I prevent on server reboots, the disk major and minor number changes and diskgroups are not getting mounted. Will add more information if required.

I am trying to install GI 19c on Oracle Linux 7 (required for 19c), and have used AsmLib to try to achieve device persistence (owner,group) for ASM devices/disks. Prior to that I used udev rules for the same and was able to achieve the same. Both times I get the same issue while doing ASM disk discovery as explained below. Problem is when I try to invoke the gridSetup.sh from node 1, all checks pass including node readiness, ssh equivalence, scan etc, but the installer fails(not able to find the disks) at discovering ASM disks which are already marked by oracleasm(AsmLib) as asm disks and are owned by grid:oinstall. The installer logs from oui show the below. WARNING: [May 29, 2019 12:32:14 PM] SRVCTL not found as there is no Grid Infrastructure home on the box. INFO: [May 29, 2019 12:32:14 PM] Executing [/u01/app/19.0.0/grid/bin/kfod.bin, nohdr=true, verbose=true, op=dfltdstr] INFO: [May 29, 2019 12:32:14 PM] Starting Output Reader Threads for process /u01/app/19.0.0/grid/bin/kfod.bin INFO: [May 29, 2019 12:32:14 PM] The process /u01/app/19.0.0/grid/bin/kfod.bin exited with code 1 INFO: [May 29, 2019 12:32:14 PM] Waiting for output processor threads to exit. INFO: [May 29, 2019 12:32:14 PM] Parsing Error 49802 initializing ADR INFO: [May 29, 2019 12:32:14 PM] Parsing ERROR!!! could not initialize the diag context Already tried setting ORACLE_BASE env variable and added to path, so adrci is executable. Also verified owner and permissions, (oracle:oinstall) Also checked on permissions for /u01/app/19.0.0/grid/bin/kfod.bin and they are executable by grid user.(grid:oinstall) Also tried various different asm diskstrings like ORCL:VOL*, ORCL*, VOL*, /dev/oracleasm/disks/* etc, but none of them worked. FYI: This is a fresh install of 19c GI onto a 2 node RAC cluster, (2 freshly created virtualbox machines with shared disks) with no prior GI or RDBMS installations on. Any help/assistance is greatly appreciated. Thanks

Oracle Version: 12.1.0.2 I had about 100 GB freespace on my **+ASM** diskgroup on Friday. When I came back on Monday, I see only 45 gigs. How can I find what consumed my space? Or is there a SQLPlus command (or) TOAD method we can use?
**Your help is my salvation.**

Last night the recovery area on one of our Oracle Database Appliances went full. This was reported in one of the database alert logs, and we were able to clear out some space before the next log switch, at which point the production would have come to a halt. It certainly would have been nice to have a little more warning, like when the disk group was 70% full. What options do we have for monitoring disk usage inside ASM?