RMAN-05534
warning: LOG_FILE_NAME_CONVERT resulted in invalid Oracle ASM or Exascale names; names changed to disk group only.
Cause
It is not possible to convert Oracle Automatic Storage Management (Oracle ASM) or Exascale Oracle Managed File names using LOG_FILE_NAME_CONVERT parameter. RMAN changed these invalid names to the converted disk group name instead.
Action
If the automatic change is incorrect, use one of the following options instead of using LOG_FILE_NAME_CONVERT for Oracle Automatic Storage Management (Oracle ASM) or Exascale Oracle Managed Files:
- Use the LOGFILE clause for online log files.
- After DUPLICATE completes, create standby log files using the SQL ALTER DATABASE ADD STANDBY LOGFILE command.
RMAN-05534
warning: LOG_FILE_NAME_CONVERT resulted in invalid ASM names; names changed to disk group only.
Cause
It was not possible to convert ASM Oracle Managed Files names using LOG_FILE_NAME_CONVERT parameter. RMAN changed these invalid names to the converted disk group name instead.
Action
If the automatic change is incorrect, use one of the following options instead of using LOG_FILE_NAME_CONVERT for ASM Oracle Managed Files:
- Use the LOGFILE clause for online log files.
- After DUPLICATE completes, create standby log files using the SQL ALTER DATABASE ADD STANDBY LOGFILE command.
RMAN-05534
warning: LOG_FILE_NAME_CONVERT resulted in invalid ASM names; names changed to disk group only.
Cause
It was not possible to convert ASM Oracle Managed Files names using LOG_FILE_NAME_CONVERT parameter. RMAN changed these invalid names to the converted disk group name instead.
Action
If the automatic change is incorrect, use one of the following options instead of using LOG_FILE_NAME_CONVERT for ASM Oracle Managed Files:
- Use the LOGFILE clause for online log files.
- After DUPLICATE completes, create standby log files using the SQL ALTER DATABASE ADD STANDBY LOGFILE command.
