Oracle ASM Cluster File System (Oracle ACFS) Known Bugs

These are known bugs for Oracle ASM Cluster File System (Oracle ACFS) in Oracle Database 12c Release 2 (12.2).

Bug 24585489

If Oracle ACFS replication and Oracle ACFS Security are active or have ever been active on the file systems involved in the replication, then the acfsutil repl upgrade command cannot be used to upgrade Oracle ACFS replication.


Execute one of the following:

  • Install the patch for this bug.

  • To update replication for Oracle Database 12c Release 2 (12.2), terminate replication on the primary and the standby databases using the acfsutil repl terminate command, then run acfsutil repl init to start replication upgrade for 12.2.

Bug 24509867

If Oracle ACFS security, encryption, or auditing are enabled and if you create a snapshot that directly invokes acfsutil snap duplicate create or acfsutil snap duplicate apply to apply the snapshot, the apply command fails even though no error is reported.


Do not enable Oracle ACFS security, encryption, or auditing if you are directly invoking acfsutil snap duplicate create or acfsutil snap duplicate apply.

Bug 24501993

Use Case 1:

Consider that security, encryption and auditing are already enabled on the file system, and snap-based replication needs to be initialized with the specified tags. If replication is enabled for the specified tags and security, encryption and auditing are also enabled, and if the security directory is not tagged with one of the specified tags, then replication will fail.

Use Case 2:

Consider that replication is initialized with the specified tags, and security, encryption and auditing need to be initialized. If snap-based replication is initialized with tags that do not replicate the files in the security directory, an attempt to enable security, encryption and auditing fails.

Workaround for Use Case 1:

Tag the security directory with the one of the specified tags for the replication.

Workaround for Use Case 2:

  1. Pause the replication.

  2. Enable security, encryption and auditing and add a tag that is specified for the replication to the security directory recursively running as Oracle ACFS Security administrator.

  3. Resume the replication.

Bug 24346121

When using acfsutil snap dup create piped into acfsutil snap dup apply to perform a data transfer, confusing error output can occur if the same transfer is accidentally performed multiple times in succession (for example, if the same command line is invoked multiple times). During each of the duplicated invocations, a set of error messages are produced by the snap dup create operation. These messages are benign and can be ignored. In this case, the snap dup apply operation does not write any data to disk, and the operation immediately terminates with an exit status of 2. The error messages result from the termination of the apply process while the create process is still trying to send data to it.


These messages are benign and can be ignored.

Bug 23327160

The compatible.advm disk group attribute or Oracle ACFS compatibility value for an Oracle ACFS file system needs to be set to a value that is equivalent to a supported Oracle Database base release stream to take advantage of the new Oracle ACFS features associated with each release. Invalid numbers are values between 12.1 and that are not complete release numbers; for example, 12.1.2, 12.1.8,, and 12.2.1


Specify Oracle Database base release numbers that are valid and complete; for example: 12.1,,,,, 12.2,, and

Bug 22191226

Terminating Oracle ACFS replication on the primary database can take a long time if a large amount of data is currently being transferred from the primary database to the standby database.


If you are willing to lose some updates from the primary database, then you can terminate replication more quickly by invoking the acfsutil repl terminate primary operation and, while waiting for this operation to complete on the primary database, the you can terminate replication on the standby database with the acfsutil repl terminate standby immediate operation. Using the immediate keyword results in speedy termination on the standby database and breaks a connection from the primary database enabling the termination command on the primary database to complete soon after.