Today on the Internet to see a friend asked: Why in the way of ASM storage Management is clearly set only log_archive_dest_1 to specify the path of the archive, but in ASM found two archived log files? (Not open Flashback)
I looked up 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 on the correct ASM "path" according to file type, and then assigns an appropriate FU lly qualified filename. If you specify a alias in the creation request, ASM also creates the alias so it references the fully qualified file Name.
Finally, Ls-l looked at the archive log files under these two directories in ASM and found that this is really the case:
Oracle does not want us to change the path of these files, but we are passionate about doing this, and Oracle automatically generates filenames that are inconvenient for human memory and management, and it is estimated that Oracle is also aware of this problem and has an alias.
Oracle ASM alias File aliases