Oracle asm alias file alias, asmalias

Oracle asm alias file alias, asmalias

Today, I saw a friend on the Internet asking: Why did I set log_archive_dest_1 In the ASM storage management mode to specify the archiving path, but I found two archived log files in ASM? (Not flashing back)

I checked some information and thought it was like this:
Every file created in ASM gets a system-generated filename, otherwise known as a fully qualified filename (FQFN ). the fully qualified filename represents a complete path name in the ASM file system. an example of a fully qualified filename is:
+ Dgroup2/sample/controlfile/Current.256.541956473
You can use the fully qualified filename to reference (read or retrieve) an ASM file. ASM generates a fully qualified filename upon any request to create a file. A creation request cannot specify a fully qualified filename. instead, it uses a simpler syntax to specify a file, such as an alias or just a disk group name. ASM then creates the file, placing it in the correct ASM "path" according to file type, and then assigns an appropriate fully qualified filename. if you specify an alias in the creation request, ASM also creates the alias so that it references the fully qualified filename.

Finally, ls-l looked at the archive log files under the two directories in ASM and found that this is indeed the case:

Oracle does not want us to change the path of these files, but we are keen to do this, and the file names automatically generated by ORacle are not easily remembered and managed by humans, it is estimated that oracle has realized this problem and has an alias.