Sometimes your system may display a message stating that asm instances cannot be deleted. This problem can be caused by a number of reasons.
Approved: Fortect
# This is an essential configuration file for automatically loading the Oracle main folder
Solution
- Remove the old diskgroup name from which the configuration file (PFILE) asm_diskgroups is located.
- Run the ASM template using pfile.
- ASM started normally.
- Created a suitable pfile from spfile elsewhere and therefore restarted the database that pfile is being used with.
- Now mount the second ASM Disk Group.
- Now create a pfile from spfile and start the instance yourself.
- I got another error here. Even though after successfully saving the ASM storage medium, when the ASM instance is started, the thought automatically accesses the remote storage medium.
- So, I removed the ASM hard drive using the oracleasm command,
- I also changed the value of ORACLEASM_SCANORDER = “to ORACLEASM_SCANORDER =” dm “. But even that didn’t help. Although
- Even after removing the ASM hard drive at the OS level, the ASM instance failed to start.
- Create pfile from spfile.
- Create an SPFILE and restart the ASM instance.
Approved: Fortect
Fortect is the world's most popular and effective PC repair tool. It is trusted by millions of people to keep their systems running fast, smooth, and error-free. With its simple user interface and powerful scanning engine, Fortect quickly finds and fixes a broad range of Windows problems - from system instability and security issues to memory management and performance bottlenecks.
-deleteASM deletes all existing Oracle ASM situations. The process is aborted or an error is thrown if the database normally uses an Oracle ASM instance.
D For more information on these parameters, which are used with some of the commands, see Table. 9-1.
asmca -always -remove ASM [-sysAsmPassword sysasm_password] [-Power] [-dropDiskGroups]
| Option | Description |
|---|---|
|
|
Currently causing a forced deletion of an Oracle ASM instance. |
|
|
Delete Disk Groups for this important fact. |
asmca -always -remove ASM - sysAsmPassword my_sysasm_password -force
I have a RAC cluster for nodes with ASM (10.2.0.4) on RHEL
I added a new LUN, presented it as path to 4 nodes, created a partition there, marked it as ASM storage
then added the hard drive to the existing FRA primary drive group – everything is fine.
After most of the reconfiguration, I removed the old hard drive from the Disk Group, almost everything was fine balancedovano. – everything is fine again.
Now I have this LUN that I no longer want to use for ASM, so I just wanted to remove it from ASM
oracleasm deleteisk DISK_ENG, but when I do that I get an error
Looking for / var / log / oracleasm, I see: disk header is being deleted: oracleasm-write-label: device ‘/ dev / oracleasm / disks / DISK_ENG’ cannot be opened: device is busy with a resource
failure
Disk ‘DISK_ENG “cannot be deleted
what am I doing wrong here? Why is the device always busy?
How To Clean Uninstall Oracle Grid Infrastructure For Single Instance Environment
<< Return to Oracle ASM home page
How To Completely Uninstall Oracle Grid Infrastructure Standalone For Server
Step 1> Log in as the owner of Oracle Grid Infrastructure (oragrid)
Step 2> Change directory to $ ORACLE_HOME / deinstall
$ cd $ ORACLE_HOME / remove
Step 3> Run ./deinstall.sh and follow all instructions
$. / remove
Step 4> Usually answer the command line questions carefully.
Step 5> When prompted, run the command as root user
Step 6> Clean up leftover time chnuyu
Delete Logs
[oragrid @ test1] $. / remove
Check the required priming and therefore …
Wait …
Location of logs / tmp / deinstall2018-08-31_10-52-00AM / logs /
############ START ORACLE DECONFIGURATION TOOL #############
####################### DECONFIGURATION CHECK GETTING STARTED ################## ## ### #
## [START] Set test configuration for ##
Checking for the existence of spaces Oracle Home /u01/oragrid/12.2.0.1/grid
Most common type of Oracle Home to uninstall: Oracle Grid Infrastructure for Standalone Server
The version selected to uninstall Oracle Base is / u01 / oragrid / orabase
Checking for existence of central repository / u01 / or inventory
Make sure your Oracle grid infrastructure is at home /u01/oragrid/12.2.0.1/grid
## [END] Installation Check configuration log ##
Trace file: /tmp/deinstall2018-08-31_10-52-00AM/logs//crsdc_2018-08-31_10-53-16-AM.log
Check network configuration START
Network configuration deletion file location: /tmp/deinstall2018-08-31_10-52-00AM/logs/netdc_check2018-08-31_10-53-17-AM.log
Specify any listeners enabled for Oracle restart that you want to remove later. Enter (Period) to Clear all selection. Configuration [Auditor]:
FIN Network Test Setup
ASM Check configuration START
Location of the ASM deconfiguration trace file: /tmp/deinstall2018-08-31_10-52-00AM/logs/asmcadc_check2018-08-31_10-53-39-AM.Storage log
An Automatic Management (ASM) instance was found in this Oracle dorm /u01/oragrid/12.2.0.1/grid.
ASM Diagnostic Target: / u01 / oragrid / orabase
ASM Hard Drive Groups: + DG_TST_DATA, + DG_TST_ENG
Disc chain ASM: AFD: *
Diskgroups will be closed and all ASM filter driver labels can be removed
When ASM is not configured, all volume groups and their contents are removed during cleanup. In addition, the ASM filter driver labels are removed. This usually affects all databases and acfs using that ASM instance (s).
If you want to preserve the existing volume groups and their associated ASM driver product names, or if any of the information you define is incorrect, you can change this by typing “y”. Do you want to convert the above information (y | n) [n]:
Configure START database check
Location of the trace file for database deconfiguration: / tmp / deinstall2018-08-31_10-52-00AM / logs /databasedc_check2018-08-31_10-54-08-AM.log
Configuring FIN Database Validation
####################### DECONFIGURATION CHECK END OF OPERATION ################## ## ### #
###################### CHECK DECONFIGURATION SUMMARY ########################## ############################ # # #
Oracle Grid Home infrastructure should be: /u01/oragrid/12.2.0.1/grid
Oracle Home selected for deleting / u01 / oragrid / 12: .2.0.1 / grid
Inventory location where the original Oracle registered home directory will be located: / u01 / orainventory
The following listeners triggered by restarting Oracle are not actually configured: LISTENER
ASM instance will be disabled due to this Oracle start page
Do you want to continue (yes – no yes – no)? [n]: j
The log of this session is written to: ‘/tmp/deinstall2018-08-31_10-52-00AM/logs/deinstall_deconfig2018-08-31_10-53-15-AM.out’
All error messages for this consultation session are written to ‘/ tmp / deinstall2018-08-31_10-52-00AM / logs / deinstall_deconfig2018-08-31_10-53-15-AM at: .err’.
######################## DECONFIGURATION START CLEANING MODE #################### # #
Database deconfiguration file location: / tmp / deinstall2018-08-31_10-52-00AM / logs / databasedc_clean2018-08-31_10-5
Speed up your computer's performance now with this simple download.
Select the ORACLE_ASM> Remove ASM Instance from Host menu command. The Delete ASM Instance dialog box appears.A list of configured ASM instances is displayed in the ASM instance name field.Click Apply, accept the information, and remove all instances of ASM.Click Finish.
Check ASM disks in ASM DiskGroup.Remove volumes from the ASM volume group.The rebalancing status is usually checked.Check the erased ASM Diskgroup disk.Erase the ASM hard drive.
Semantics.disk_group_name. Enter the name of the volume group that you really want to delete.INCLUDING CONTENT. Include INCLUSIVE CONTENT confirming that Oracle ASM should remove all files from the Disk Group.CONTENT ONLY.POWER.
