Today, one issue was reported where diskgroup got created successfully but disk group had a special character in it. Diskgroup name with special character caused an issue for us as no operation were allowed Later we could identify diskgroup name with special character. Here is how we found it out. When we fired select we came to know “▒” this character got added as suffix.
You may like –
- Postgres SQL installation on Linux
- PRIF-33: Failed to set or delete interface because hosts could not be discovered | CRS-02325: Unable to get Grid Plug and Play (GPnP) profile from requested cluster nodes
- Post Patch PRCR-1105 : Failed to relocate resource ora.mgmtdb to node oracledbworld02 PRCR-1089 : Failed to relocate resource ora.mgmtdb Oracle 19c
- OEM13c : Admin Server Port is occupied by another process. Please stop process to free port
- Expdp using VIEWS_AS_TABLES in Oracle 19c
Table of Contents
ISSUE – Special Character in Diskgroup Name
select name from v$asm_diskgroup where name like 'REDO_SANSUI%';
Name
-------------
REDO_SANSUI▒
Now the problem was we were unable to add disks to the diskgroup. When we tried to drop the diskgroup . We tried all possible commands, And error was still the same
drop diskgroup REDO_SANSUI;
drop diskgroup "REDO_SANSUI▒";
drop diskgroup "REDO_SANSUIÂ";
ORA-15001: diskgroup "REDO_SANSUI" does not exist or is not mounted
Here is the output of ASM alert log.
* validated domain 18, flags = 0x0
NOTE: cache recovered group 18 to fcn 0.0
NOTE: redo buffer size is 256 blocks (1056768 bytes)
Tue Jun 09 12:26:57 2020
NOTE: LGWR attempting to mount thread 1 for diskgroup 18
(REDO_SANSUIÂ)
NOTE: LGWR found thread 1 closed at ABA 0.10750 lock domain=0 inc#=0
instnum=0
NOTE: LGWR mounted thread 1 for diskgroup 18 (REDO_SANSUIÂ)
Tue Jun 09 12:26:57 2020
NOTE: LGWR opened thread 1 (REDO_SANSUIÂ) at fcn 0.0 ABA 2.0
lock domain=18 inc#=206 instnum=1 gx.incarn=612620665 mntstmp=2020/06/09
12:26:57.340000
Tue Jun 09 12:26:57 2020
NOTE: cache mounting group 18/0x2483D979 (REDO_SANSUIÂ) succeeded
NOTE: cache ending mount (success) of group REDO_SANSUIÂ
number=18 incarn=0x2483d979
Tue Jun 09 12:26:57 2020
NOTE: Instance updated compatible.asm to 10.1.0.0.0 for grp 18
Tue Jun 09 12:26:57 2020
SUCCESS: diskgroup REDO_SANSUIÂ was mounted
Tue Jun 09 12:26:57 2020
SUCCESS: create diskgroup REDO_SANSUIÂ external redundancy disk
'/dev/rdsk/c1d33s6'
Tue Jun 09 12:26:57 2020
ERROR: failed to online diskgroup resource ora.REDO_SANSUIÂ.dg
WARNING: unknown state for diskgroup resource
ora.REDO_SANSUIÂ.dg, Return Value: 3
Tue Jun 09 12:26:59 2020
Solution –>
It’s because of Putty Session settings.
If you see, Remote Character set UTF-8 and our database was a Non-UTF-8 database. Hence to resolve this issue, we need to change the Remote Character Set to ISO8859-15
Now click apply and take session of the database on this Putty.
And we tried to drop the diskgroup. And it worked for us.
sql>drop diskgroup "REDO_SANSUIÂ";
Finally we could drop the diskgroup with special character in it. And later we created a new one and added redo logs on it.
Let me share from where we got the hint on this issue. We came across a Oracle Support MOS doc MOS DOC 2178585.1 which explains about the disk_name got an special character and how they resolved it. Thank you for Reading!!! Happy Learning 🙂