Oracle RMAN backup

# Rman Backups:                 
15 21 * * * ${HOME}/bin/pkg/rman_backup/_run.sh   testdb     > /dev/null 2>> /tmp/crontab_oracle.err


$more _run.sh
#!/bin/bash


#
# Package Name:
#

tmp_string="`dirname $0`"
pkg_name="`basename ${tmp_string}`"

if [ "${pkg_name}" = "." ]; then
  tmp_string="`pwd`"
  pkg_name="`basename ${tmp_string}`"
fi

# Check Parameters:
if [ $1 ]
then
  oracle_sid=`echo ${1} | tr "[A-Z]" "[a-z]"`
else
  echo "`date +%Y.%m.%d" "%H:%M:%S` - ${pkg_name}: Error! (Parameter=1). Call `basename $0` " >&2
  exit 2
fi

#
# Setup Environment:
#

pkg_env="${HOME}/bin/_conf/.env"
if [ ! -r "${pkg_env}" ]; then
  echo "`date +%Y.%m.%d" "%H:%M:%S` - ${pkg_name}: ERROR!!! Execution Aborted. Not Found Environment file: ${pkg_env}" >&2
  exit 2
fi

if [ -s "${pkg_env}" ]; then
  . ${pkg_env}
else
  echo "`date +%Y.%m.%d" "%H:%M:%S` - ${pkg_name}: ERROR!!! Execution Aborted. Environment file is empty: ${pkg_env}" >&2
  exit 2
fi


#
# Check Environment:
#


# Check ORACLE_USER:
if [ -z "${ORA_USER}" ]; then
  echo "`date +%Y.%m.%d" "%H:%M:%S` - ${pkg_name}: ERROR!!! Execution Aborted. Environment variable ORA_USER not defined" >&2
  exit 2
else
  ora_user=${ORA_USER}
fi

# Check Database Instance:
loc_status=`ps -fu ${ora_user} | grep -w "ora_[a-z]*_${oracle_sid}"`
loc_res=$?

if [ ${loc_res} -eq 0 ]; then
  echo "Database Instance OK"
else
  echo "Error! Not found Database Instance."
  exit
fi


# Check ORACLE_HOME:
if [ -z "${ORACLE_HOME}" ]; then
  echo "`date +%Y.%m.%d" "%H:%M:%S` - ${pkg_name}: ERROR!!! Execution Aborted. Environment variable ORACLE_HOME not defined" >&2
  exit 2
elif [ ! -d "${ORACLE_HOME}" ]; then
  echo "`date +%Y.%m.%d" "%H:%M:%S` - ${pkg_name}: ERROR!!! Execution Aborted. Directory ORACLE_HOME not found (${ORACLE_HOME})" >&2
  exit 2
fi


# Check TMP_DIR:
if [ -z "${TMP_DIR}" ]; then
  echo "`date +%Y.%m.%d" "%H:%M:%S` - ${pkg_name}: ERROR!!! Execution Aborted. Environment variable TMP_DIR not defined" >&2
  exit 2
elif [ ! -d "${TMP_DIR}" ]; then
  echo "`date +%Y.%m.%d" "%H:%M:%S` - ${pkg_name}: ERROR!!! Execution Aborted. Directory TMP_DIR not found (${TMP_DIR})" >&2
  exit 2
elif [ ! -w "${TMP_DIR}" ]; then
  echo "`date +%Y.%m.%d" "%H:%M:%S` - ${pkg_name}: ERROR!!! Execution Aborted. Directory TMP_DIR not writeable (${TMP_DIR})" >&2
  exit 2
fi


# Check BIN_DIR:
if [ -z "${BIN_DIR}" ]; then
  echo "`date +%Y.%m.%d" "%H:%M:%S` - ${pkg_name}: ERROR!!! Execution Aborted. Environment variable BIN_DIR not defined" >&2
  exit 2
elif [ ! -d "${BIN_DIR}" ]; then
  echo "`date +%Y.%m.%d" "%H:%M:%S` - ${pkg_name}: ERROR!!! Execution Aborted. Directory BIN_DIR not found (${BIN_DIR})" >&2
  exit 2
fi


# Check COMPANY_NAME:
if [ -z "${COMPANY_NAME}" ]; then
  echo "`date +%Y.%m.%d" "%H:%M:%S` - ${pkg_name}: ERROR!!! Execution Aborted. Environment variable COMPANY_NAME not defined" >&2
  exit 2
fi


# Check HOST_NAME:
if [ -z "${HOST_NAME}" ]; then
  echo "`date +%Y.%m.%d" "%H:%M:%S` - ${pkg_name}: ERROR!!! Execution Aborted. Environment variable HOST_NAME not defined" >&2
  exit 2
fi


# Check MAIL_RECIPIENTS:
if [ -z "${MAIL_DBA}" ]; then
  echo "`date +%Y.%m.%d" "%H:%M:%S` - ${pkg_name}: ERROR!!! Execution Aborted. Environment variable MAIL_RECIPIENTS not defined" >&2
  exit 2
fi


# Check UTL_SEND:
if [ -z "${UTL_SEND}" ]; then
  echo "`date +%Y.%m.%d" "%H:%M:%S` - ${pkg_name}: ERROR!!! Execution Aborted. Environment variable UTL_SEND not defined" >&2
  exit 2
elif [ ! -f "${UTL_SEND}" ]; then
  echo "`date +%Y.%m.%d" "%H:%M:%S` - ${pkg_name}: ERROR!!! Execution Aborted. File UTL_SEND not found (${UTL_SEND})" >&2
  exit 2
elif [ ! -x "${UTL_SEND}" ]; then
  echo "`date +%Y.%m.%d" "%H:%M:%S` - ${pkg_name}: ERROR!!! Execution Aborted. File UTL_SEND not executable (${UTL_SEND})" >&2
  exit 2
fi

# Initialize Package:

pkg_flag="`basename $0 .sh`"
run_in_progress=${TMP_DIR}/${pkg_name}_${oracle_sid}.lock
log_file=${TMP_DIR}/${pkg_name}_${oracle_sid}.log
prefix="${COMPANY_NAME}#${HOST_NAME}(${oracle_sid}) ${pkg_name}"
mess_theme="${prefix}: Error! Another process running (${run_in_progress})"

mail_recipients="$MAIL_DBA"
echo $mail_recipients

# Check Another process for running:
if [ -f ${run_in_progress} ]; then
  echo "`date +%Y.%m.%d" "%H:%M:%S` - ${pkg_name}: Error! Another process running. Remove a file ${run_in_progress}" >&2
  echo "Remove a file ${run_in_progress}" | ${BIN_DIR}/_lib/utl_send.sh "${mess_theme}" "${mail_recipients}"
  exit 2
fi

# Prevent Parallel Execution:
touch ${run_in_progress}

# Run Implementation:
${BIN_DIR}/pkg/${pkg_name}/body.sh "${pkg_flag}" "${oracle_sid}" | tee ${log_file}

# Cleanup Stop Flag:
test -r ${run_in_progress} && rm ${run_in_progress}

$



$more body.sh
#!/bin/bash


#
# Check Parameters:
#

# Package Name:
tmp_string="`dirname $0`"
pkg_name="`basename ${tmp_string}`"

if [ "${pkg_name}" = "." ]; then
  tmp_string="`pwd`"
  pkg_name="`basename ${tmp_string}`"
fi

# Check for internal call:
if [ ! $1 = '_run' ]; then
  echo "`date +%Y.%m.%d" "%H:%M:%S` - ${pkg_name}: Error! (Parameter=1) Call `basename $0` from ./_run.sh" >&2
  exit 2
fi


# Check For :
if [ $2 ]
then
  echo " 2=${2} (ORACLE_SID)"
  ORACLE_SID=`echo ${2} | tr "[A-Z]" "[a-z]"`; export ORACLE_SID
else
  echo "`date +%Y.%m.%d" "%H:%M:%S` - ${pkg_name}: Error! (Parameter=2) Call `basename $0` With 2-d parameter" >&2
  exit 2
fi


#
# Define local variables:
#

# Variables:

prefix="${COMPANY_NAME}#${HOST_NAME}(${ORACLE_SID}) ${pkg_name}"
mess_theme="${prefix}:Rman backup"
log_file=${TMP_DIR}/${pkg_name}_${ORACLE_SID}.log


mail_recipients="$MAIL_DBA"
echo $mail_recipients

begin_backup="`date +%Y.%m.%d" "%H:%M:%S`"

$UTL_RMAN target / catalog 'rman/pwd@catdb.sun.com'  cmdfile ${BIN_DIR}/_sql/hot_full_backupset.rman  log=${log_file}

end_backup="`date +%Y.%m.%d" "%H:%M:%S`"

cat  ${log_file}  | ${BIN_DIR}/_lib/utl_send.sh "${mess_theme}" "${mail_recipients}"
$



$more hot_full_copy.rman

#### Clear #####################
CONFIGURE RETENTION POLICY CLEAR;
CONFIGURE BACKUP OPTIMIZATION CLEAR;
CONFIGURE DEFAULT DEVICE TYPE CLEAR;
CONFIGURE CONTROLFILE AUTOBACKUP CLEAR;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK CLEAR;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT CLEAR;
CONFIGURE DEVICE TYPE DISK CLEAR;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK CLEAR;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT  CLEAR;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK CLEAR;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT CLEAR;
CONFIGURE CHANNEL DEVICE TYPE DISK CLEAR;
CONFIGURE CHANNEL DEVICE TYPE SBT CLEAR;
CONFIGURE MAXSETSIZE CLEAR;
CONFIGURE SNAPSHOT CONTROLFILE NAME CLEAR;
##############################################################################################
#
CONFIGURE RETENTION POLICY TO REDUNDANCY 7;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '$RMAN_BKP/$ORACLE_SID/cf_%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '$RMAN_BKP/$ORACLE_SID/%U';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
###########################################################################################
#
CROSSCHECK COPY OF DATABASE;
CROSSCHECK COPY OF ARCHIVELOG ALL;
CROSSCHECK COPY OF CONTROLFILE;
CROSSCHECK BACKUP OF CONTROLFILE;

DELETE NOPROMPT EXPIRED COPY OF DATABASE;
DELETE NOPROMPT EXPIRED COPY OF ARCHIVELOG ALL;
DELETE NOPROMPT EXPIRED COPY OF CONTROLFILE;
DELETE NOPROMPT EXPIRED BACKUP OF CONTROLFILE;
#

DELETE NOPROMPT OBSOLETE;
#

###########################################################################################
#
sql 'alter system switch logfile';
sql 'alter system archive log current';

BACKUP AS COPY DATABASE include current controlfile for standby;

sql 'alter system switch logfile';
sql 'alter system archive log current';

backup archivelog all format '$RMAN_BKP/$ORACLE_SID/%U' delete input;

sql 'alter system switch logfile';
sql 'alter system archive log current';
################################################################################################
#
DELETE NOPROMPT OBSOLETE;
#
$



# Manage STBY:
35 05 * * * ${HOME}/bin/pkg/manage_stby/_run.sh  testdb       > /dev/null 2>> /tmp/crontab_oracle.err



$more _run.sh

#!/bin/bash


#
# Package Name:
#

tmp_string="`dirname $0`"
pkg_name="`basename ${tmp_string}`"

if [ "${pkg_name}" = "." ]; then
  tmp_string="`pwd`"
  pkg_name="`basename ${tmp_string}`"
fi

# Check Parameters:
if [ $1 ]
then
  oracle_sid=`echo ${1} | tr "[A-Z]" "[a-z]"`
else
  echo "`date +%Y.%m.%d" "%H:%M:%S` - ${pkg_name}: Error! (Parameter=1). Call `basename $0` " >&2
  exit 2
fi

#
# Setup Environment:
#

pkg_env="${HOME}/bin/_conf/.env"
if [ ! -r "${pkg_env}" ]; then
  echo "`date +%Y.%m.%d" "%H:%M:%S` - ${pkg_name}: ERROR!!! Execution Aborted. Not Found Environment file: ${pkg_env}" >&2
  exit 2
fi

if [ -s "${pkg_env}" ]; then
  . ${pkg_env}
else
  echo "`date +%Y.%m.%d" "%H:%M:%S` - ${pkg_name}: ERROR!!! Execution Aborted. Environment file is empty: ${pkg_env}" >&2
  exit 2
fi


#
# Check Environment:
#


# Check ORACLE_USER:
if [ -z "${ORA_USER}" ]; then
  echo "`date +%Y.%m.%d" "%H:%M:%S` - ${pkg_name}: ERROR!!! Execution Aborted. Environment variable ORA_USER not defined" >&2
  exit 2
else
  ora_user=${ORA_USER}
fi

# Check Database Instance:
loc_status=`ps -fu ${ora_user} | grep -w "ora_[a-z]*_${oracle_sid}"`
loc_res=$?

if [ ${loc_res} -eq 0 ]; then
  echo "Database Instance OK"
else
  echo "Error! Not found Database Instance."
  exit
fi


# Check ORACLE_HOME:
if [ -z "${ORACLE_HOME}" ]; then
  echo "`date +%Y.%m.%d" "%H:%M:%S` - ${pkg_name}: ERROR!!! Execution Aborted. Environment variable ORACLE_HOME not defined" >&2
  exit 2
elif [ ! -d "${ORACLE_HOME}" ]; then
  echo "`date +%Y.%m.%d" "%H:%M:%S` - ${pkg_name}: ERROR!!! Execution Aborted. Directory ORACLE_HOME not found (${ORACLE_HOME})" >&2
  exit 2
fi


# Check TMP_DIR:
if [ -z "${TMP_DIR}" ]; then
  echo "`date +%Y.%m.%d" "%H:%M:%S` - ${pkg_name}: ERROR!!! Execution Aborted. Environment variable TMP_DIR not defined" >&2
  exit 2
elif [ ! -d "${TMP_DIR}" ]; then
  echo "`date +%Y.%m.%d" "%H:%M:%S` - ${pkg_name}: ERROR!!! Execution Aborted. Directory TMP_DIR not found (${TMP_DIR})" >&2
  exit 2
elif [ ! -w "${TMP_DIR}" ]; then
  echo "`date +%Y.%m.%d" "%H:%M:%S` - ${pkg_name}: ERROR!!! Execution Aborted. Directory TMP_DIR not writeable (${TMP_DIR})" >&2
  exit 2
fi


# Check BIN_DIR:
if [ -z "${BIN_DIR}" ]; then
  echo "`date +%Y.%m.%d" "%H:%M:%S` - ${pkg_name}: ERROR!!! Execution Aborted. Environment variable BIN_DIR not defined" >&2
  exit 2
elif [ ! -d "${BIN_DIR}" ]; then
  echo "`date +%Y.%m.%d" "%H:%M:%S` - ${pkg_name}: ERROR!!! Execution Aborted. Directory BIN_DIR not found (${BIN_DIR})" >&2
  exit 2
fi


# Check COMPANY_NAME:
if [ -z "${COMPANY_NAME}" ]; then
  echo "`date +%Y.%m.%d" "%H:%M:%S` - ${pkg_name}: ERROR!!! Execution Aborted. Environment variable COMPANY_NAME not defined" >&2
  exit 2
fi


# Check HOST_NAME:
if [ -z "${HOST_NAME}" ]; then
  echo "`date +%Y.%m.%d" "%H:%M:%S` - ${pkg_name}: ERROR!!! Execution Aborted. Environment variable HOST_NAME not defined" >&2
  exit 2
fi


# Check MAIL_RECIPIENTS:
if [ -z "${MAIL_DBA}" ]; then
  echo "`date +%Y.%m.%d" "%H:%M:%S` - ${pkg_name}: ERROR!!! Execution Aborted. Environment variable MAIL_RECIPIENTS not defined" >&2
  exit 2
fi


# Check UTL_SEND:
if [ -z "${UTL_SEND}" ]; then
  echo "`date +%Y.%m.%d" "%H:%M:%S` - ${pkg_name}: ERROR!!! Execution Aborted. Environment variable UTL_SEND not defined" >&2
  exit 2
elif [ ! -f "${UTL_SEND}" ]; then
  echo "`date +%Y.%m.%d" "%H:%M:%S` - ${pkg_name}: ERROR!!! Execution Aborted. File UTL_SEND not found (${UTL_SEND})" >&2
  exit 2
elif [ ! -x "${UTL_SEND}" ]; then
  echo "`date +%Y.%m.%d" "%H:%M:%S` - ${pkg_name}: ERROR!!! Execution Aborted. File UTL_SEND not executable (${UTL_SEND})" >&2
  exit 2
fi

# Initialize Package:

pkg_flag="`basename $0 .sh`"
run_in_progress=${TMP_DIR}/${pkg_name}_${oracle_sid}.lock
log_file=${TMP_DIR}/${pkg_name}_${oracle_sid}.log
prefix="${COMPANY_NAME}#${HOST_NAME}(${oracle_sid}) ${pkg_name}"
mess_theme="${prefix}: Error! Another process running (${run_in_progress})"

mail_recipients="$MAIL_DBA"
echo $mail_recipients

# Check Another process for running:
if [ -f ${run_in_progress} ]; then
  echo "`date +%Y.%m.%d" "%H:%M:%S` - ${pkg_name}: Error! Another process running. Remove a file ${run_in_progress}" >&2
  echo "Remove a file ${run_in_progress}" | ${BIN_DIR}/_lib/utl_send.sh "${mess_theme}" "${mail_recipients}"
  exit 2
fi

# Prevent Parallel Execution:
touch ${run_in_progress}

# Run Implementation:
${BIN_DIR}/pkg/${pkg_name}/body.sh "${pkg_flag}" "${oracle_sid}" | tee ${log_file}

# Cleanup Stop Flag:
test -r ${run_in_progress} && rm ${run_in_progress}

$



$more body.sh
#!/bin/bash


#
# Check Parameters:
#

# Package Name:
tmp_string="`dirname $0`"
pkg_name="`basename ${tmp_string}`"

if [ "${pkg_name}" = "." ]; then
  tmp_string="`pwd`"
  pkg_name="`basename ${tmp_string}`"
fi

# Check for internal call:
if [ ! $1 = '_run' ]; then
  echo "`date +%Y.%m.%d" "%H:%M:%S` - ${pkg_name}: Error! (Parameter=1) Call `basename $0` from ./_run.sh" >&2
  exit 2
fi


# Check For :
if [ $2 ]
then
  echo " 2=${2} (ORACLE_SID)"
  ORACLE_SID=`echo ${2} | tr "[A-Z]" "[a-z]"`; export ORACLE_SID
else
  echo "`date +%Y.%m.%d" "%H:%M:%S` - ${pkg_name}: Error! (Parameter=2) Call `basename $0` With 2-d parameter" >&2
  exit 2
fi


#
# Define local variables:
#

# Variables:

prefix="${COMPANY_NAME}#${HOST_NAME}(${ORACLE_SID}) ${pkg_name}"
mess_theme="${prefix}:Manage_standby"
log_file=${TMP_DIR}/${pkg_name}_${ORACLE_SID}.log


mail_recipients="$MAIL_DBA $MAIL_SYS"
echo $mail_recipients

begin_backup="`date +%Y.%m.%d" "%H:%M:%S`"

$UTL_RMAN target /  cmdfile ${BIN_DIR}/_sql/manage_stby.rman  log=${log_file}

end_backup="`date +%Y.%m.%d" "%H:%M:%S`"

cat  ${log_file}  | ${BIN_DIR}/_lib/utl_send.sh "${mess_theme}" "${mail_recipients}"
$





$more manage_stby.rman

#
DELETE NOPROMPT ARCHIVELOG ALL COMPLETED BEFORE 'SYSDATE-1';
#
$



 RMAN Настройка и резервное копирование

Запуск RMAN из консоли UNIX системы осуществляется от oracle- пользователя
#rman target /
Запуск с указанием журнала истории RMAN сессии:
#rman target / LOG /u01/log1  APPEND
Подключение с использованием файла паролей:
Для установления соединения к не открытой БД с помощью RMAN используется файл паролей
#rman target sys/pass
Выполнение командного файла при запуске RMAN:
rman target / CMDFILE=/oracle/home/script1.rcv
Удаленное подключение:
rman target sys/ pass@server1.ora.ru


Основные настройки RMAN
Для настройки RMAN используется команда CONFIGURE
Включить автоматическое резервирование CONTROLFILE в каждом резервном наборе (при каждом бэкапе):
RMAN> configure controlfile autobackup on;

RMAN позволяет настраивать возможность хранения объектов резервных копий следующим образом:
Можно задать период, в который будет возможность, восстановится на определенный момент во времени. Например, 7 дней хранятся все объекты резервных копий. Соответственно на любой из семи дней в прошлом мы можем восстановиться, т.к. у нас есть все объекты резервных копий сделанных за этот период.

Данная команда задает окно восстановления в 7 дней:
RMAN> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
Либо можно указать избыточность хранения объектов резервных копий. Например, мы хотим держать две полных резервных копии БД.
RMAN>CONFIGURE RETENTION POLICY TO REDUNDANCY 2;

Команда CLEAR сбрасывает настройки параметров.
Например:
RMAN> configure controlfile autobackup clear;
RMAN> configure default device type clear;

Команда SHOW  показывает текущие установки RMAN
Например:
RMAN> show all;
RMAN> show controlfile autobackup;

Определение устройства, на которое будет записываться резервная копия
DISK – запись на диск
SBT – запись на ленту
Просмотр :
RMAN> show default device type;
RMAN configuration parameters are:
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default

Установка записи на ленту:
RMAN> CONFIGURE DEFAULT DEVICE TYPE TO SBT;
new RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
new RMAN configuration parameters are successfully stored
Для того чтобы производить запись на ленту необходимо также настроить связь между RMAN и ленточной библиотекой.

Резервное копирование
Условием резервного копирования БД является режим ARHIVELOG. Для выполнения онлайн резервирования БД должна быть открыта или смонтирована.
Выполняет резервное копирование БД  согласно параметрам RMAN:
RMAN> backup database;

Резервное копирование БД и архивных журналов
RMAN> backup database plus archivelog;

Резервное копирование в заданный файл:
RMAN> backup database plus archivelog format '/restore/rman/backup_rman.bkp';

Резервное копирование controlfile, spfile:
RMAN> backup current controlfile spfile;

Резервное копирование отдельного файла данных:
RMAN> backup datafile '/u02/oradata/orcl/users01.dbf';

Резервное копирование табличного пространства:
RMAN> backup tablespace users;

Создание полного инкрементального бэкапа
RMAN> backup incremental level 0 database;

Создание дифференциального инкрементального бэкапа:
RMAN> backup incremental level 1 database;

Создание кумулятивного инкрементального бэкапа:
RMAN> backup incremental level 1 cumulative database;

Просмотр созданных резервных копий:
RMAN> list backup;
RMAN> list backup of database;

Просмотр зарезервированных архивных журналов:
RMAN> list copy of database archivelog all;
RMAN> list copy of database archivelog from time=’дата’;

Просмотр структуры базы:
RMAN> report schema;

Просмотр устаревших объектов резервных наборов:
RMAN> report obsolete;

Информация о том какие файлы необходимо резервировать
RMAN>report need backup …;

пример:
RMAN> report need backup days 3

Отобразится информация о том, что не было зарезервировано за последние три дня.
Удаление всех устаревших файлов согласно принятой политике удержания:
RMAN> delete obsolete;

Удалить резервные набор под номером 3
RMAN> delete backupset 3;

Удалить все архивные журналы:
RMAN> delete archivelog all;

Удаление всех резервных копий:
RMAN> delete backup

Проверка резервной копии:
RMAN> crosscheck backup;

Проверка контрольного журнала:
RMAN> crosscheck backup of controlfile;

Проверка всех зарезервированных архивных журналов:
RMAN> crosscheck archivelog all;

Получение информации через представления:
v$rman_configuration – информация о текущих настройках параметров RMAN
v$archived_log – информация о архивных журналах
v$backup_device – устройство для резервного копирования
v$backup_corruption – показывает поврежденные блоки в резервных копиях, если он есть.
v$session_longops – мониторинг операций процесса резервирования



select NAME, SEQUENCE#, COMPLETION_TIME from v$archived_log where FIRST_TIME between to_date('26.06.2011 13:00:00','dd.mm.yyyy hh24:mi:ss') and to_date('04.07.2011 13:00:00','dd.mm.yyyy hh24:mi:ss')

SEQUENCE# COMPLETION_TIM
--------- --------------
    39610 26.06.11 13:41
    39611 26.06.11 15:41
........................
    40350 04.07.11 11:48
    40351 04.07.11 13:29

-Восстановить управляющий файл в новое место:
RUN
{
  ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
  SEND 'NB_ORA_SERV=nbumas-mo-cen, NB_ORA_CLIENT=titan2'; # NB_ORA_CLIENT которым делался бэкап
  RESTORE CONTROLFILE FROM AUTOBACKUP;
  ALTER DATABASE MOUNT;
}


Восстановление на указанный момент времени:
rman target / nocatalog msglog /oracle/admin/mtseip/restore_mtseip.log append

SET ARCHIVELOG DESTINATION TO '/oracle/data/mtseip/arch/'

RUN {
ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
SEND 'NB_ORA_SERV=nbumas-mo-cen, NB_ORA_CLIENT=titan2'; # NB_ORA_CLIENT которым делался бэкап
set until time "to_date('04-07-2011 13:00:00','dd-mm-yyyy HH24:MI:SS')";
RESTORE DATABASE;
RECOVER DATABASE;
RELEASE CHANNEL ch00;
}
sql 'alter database open resetlogs';
----------------------------------
Восстановление архивлогов

RUN {
ALLOCATE CHANNEL ch01 TYPE 'SBT_TAPE';
SEND 'NB_ORA_SERV=nbumas-mo-cen, NB_ORA_CLIENT=titan2'; # NB_ORA_CLIENT которым делался бэкап
restore ARCHIVELOG from logseq 39610 until sequence 40351;
RELEASE CHANNEL ch01;
}




-Выставить переменные окружения (SID) и ORACLE_HOME(в доке не указано)
export set ORACLE_SID=rdb
export set ORACLE_HOME=/oracle/10203_64
export set LD_LIBRARY_PATH=/usr/lib:/usr/openwin/lib:/usr/dt/lib:/oracle/10203_64/lib
 export set PATH = /usr/bin:/usr/sbin:/opt/bin:/usr/local/bin:/etc:/etc/init.d:/opt/FERMI/bin:/opt/PUBssh/bin:/opt/PUBsamba/bin:/usr/ccs/bin:/usr/proc/bin:/usr/openv/volmgr/bin:/oracle/10203_64/bin
export set PFILE='' #на титане еще и пфайл устанавливается как переменная - пришлось сбросить


% rman TARGET / NOCATALOG

-далее устанавливает DBID и стартуем NOMOUNT

RMAN> set DBID=1969103386;
RMAN> STARTUP NOMOUNT;

-RMAN ругнется, что не нашел файл параметров, но стартует инстанс с "фиктивным" файлом параметров, что позволит потом восстановить и его.

-Восстановление файла параметров spfile в pfile.

RUN
{
  ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
  SEND 'NB_ORA_SERV=nbumas-mo-cen, NB_ORA_CLIENT=nbumas-mo-cen'; # NB_ORA_CLIENT которым делался бэкап
  RESTORE SPFILE TO PFILE '?/dbs/initrdb_r.ora' FROM AUTOBACKUP;
  SHUTDOWN ABORT;
}


-отредактировать параметры pfile под текущее расположение на хосте:
audit
IFILE
*_DUMP_DEST
LOG_ARCHIVE_DEST*
CONTROL_FILES


-Запустить базу с новым iniшником:
STARTUP FORCE NOMOUNT PFILE='/oracle/11107_64/10g_64/10204_64/dbs/initprod.ora';

-Восстановить управляющий файл в новое место:
RUN
{
  ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
  SEND 'NB_ORA_SERV=nbumas-mo-cen, NB_ORA_CLIENT=nbumas-mo-cen'; # NB_ORA_CLIENT которым делался бэкап
  RESTORE CONTROLFILE FROM AUTOBACKUP;
  ALTER DATABASE MOUNT;
}


-Подключится /as sysdba и выбрать инфу по файлам:
% sqlplus '/ AS SYSDBA'

SQL>
COLUMN NAME FORMAT a60
SPOOL LOG 'db_filenames.out'
SELECT FILE# AS "File/Grp#", NAME FROM V$DATAFILE
UNION
SELECT GROUP#,MEMBER FROM V$LOGFILE;
SPOOL OFF

SQL EXIT


         1 /opt/oracle/oradata/rdb/redo1a
         2 /opt/oracle/oradata/rdb/redo2a
         3 /opt/oracle/oradata/rdb/redo3a
         4 /opt/oracle/oradata/rdb/redo4a
         5 /opt/oracle/oradata/rdb/redo5a
         6 /opt/oracle/oradata/rdb/redo6a

set newname for datafile 1 to '/oracle/admin/test/arch/prod/data/system';
set newname for datafile 2 to '/oracle/admin/test/arch/prod/data/undo';
set newname for datafile 3 to '/oracle/admin/test/arch/prod/data/sysaux';
set newname for datafile 4 to '/oracle/admin/test/arch/prod/data/users';
set newname for datafile 5 to '/oracle/admin/test/arch/prod/data/rman';
set newname for datafile 6 to '/oracle/admin/test/arch/prod/data/tools01.dbf';
set newname for datafile 7 to '/oracle/admin/test/arch/prod/data/rm11.dbf';
set newname for datafile 8 to '/oracle/admin/test/arch/prod/data/rmf.dbf';
set newname for datafile 9 to '/oracle/admin/test/arch/prod/data/rmor.dbf';


SQL "ALTER DATABASE RENAME FILE ''/opt/oracle/oradata/rdb/redo1a'' 
  TO ''/oracle/admin/test/arch/prod/data/redo1a''";
SQL "ALTER DATABASE RENAME FILE ''/opt/oracle/oradata/rdb/redo2a'' 
  TO ''/oracle/admin/test/arch/prod/data/redo2a''";
SQL "ALTER DATABASE RENAME FILE ''/opt/oracle/oradata/rdb/redo3a'' 
  TO ''/oracle/admin/test/arch/prod/data/redo3a''";
SQL "ALTER DATABASE RENAME FILE ''/opt/oracle/oradata/rdb/redo4a'' 
  TO ''/oracle/admin/test/arch/prod/data/redo4a''";
SQL "ALTER DATABASE RENAME FILE ''/opt/oracle/oradata/rdb/redo5a'' 
  TO ''/oracle/admin/test/arch/prod/data/redo5a''";
SQL "ALTER DATABASE RENAME FILE ''/opt/oracle/oradata/rdb/redo6a'' 
  TO ''/oracle/admin/test/arch/prod/data/redo6a''";


-------------------
Новое место размещения
/oracle/admin/test/arch/rdb/data
/oracle/admin/test/arch/rdb/admin/arch

/oracle/admin/test/arch/rdb/admin/aud
/oracle/admin/test/arch/rdb/admin/bdump
/oracle/admin/test/arch/rdb/admin/cdump


'/oracle/11107_64/10g_64/rdb/cntrl01.dbf'
run
{
ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
SEND 'NB_ORA_CLIENT=nbumas-mo-cen, NB_ORA_SERV=nbumas-mo-cen';
set newname for datafile 1 to '/oracle/admin/test/arch/rdb/data/system';
set newname for datafile 2 to '/oracle/admin/test/arch/rdb/data/undo';
set newname for datafile 3 to '/oracle/admin/test/arch/rdb/data/sysaux';
set newname for datafile 4 to '/oracle/admin/test/arch/rdb/data/users';
set newname for datafile 5 to '/oracle/admin/test/arch/rdb/data/rman';
set newname for datafile 6 to '/oracle/admin/test/arch/rdb/data/tools01.dbf';
set newname for datafile 7 to '/oracle/admin/test/arch/rdb/data/rm11.dbf';
set newname for datafile 8 to '/oracle/admin/test/arch/rdb/data/rmf.dbf';
set newname for datafile 9 to '/oracle/admin/test/arch/rdb/data/rmor.dbf';
SQL "ALTER DATABASE RENAME FILE ''/opt/oracle/oradata/rdb/redo1a'' 
  TO ''/oracle/admin/test/arch/rdb/data/redo1a''";
SQL "ALTER DATABASE RENAME FILE ''/opt/oracle/oradata/rdb/redo2a'' 
  TO ''/oracle/admin/test/arch/rdb/data/redo2a''";
SQL "ALTER DATABASE RENAME FILE ''/opt/oracle/oradata/rdb/redo3a'' 
  TO ''/oracle/admin/test/arch/rdb/data/redo3a''";
SQL "ALTER DATABASE RENAME FILE ''/opt/oracle/oradata/rdb/redo4a'' 
  TO ''/oracle/admin/test/arch/rdb/data/redo4a''";
SQL "ALTER DATABASE RENAME FILE ''/opt/oracle/oradata/rdb/redo5a'' 
  TO ''/oracle/admin/test/arch/rdb/data/redo5a''";
SQL "ALTER DATABASE RENAME FILE ''/opt/oracle/oradata/rdb/redo6a'' 
  TO ''/oracle/admin/test/arch/rdb/data/redo6a''";
restore database;
SWITCH DATAFILE ALL; # Update control file with new location of datafiles.
RECOVER DATABASE;
}

-----------------------

""""""""""""
RESTORE CONTROLFILE ... FROM 'media_handle' or TAG 'user_tag';
""""""""""""

run
{
  ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
  SEND 'NB_ORA_SERV=nbumas-mo-cen, NB_ORA_CLIENT=nbumas-mo-cen';
  RESTORE SPFILE TO PFILE '?/dbs/initrdbtest.ora' FROM AUTOBACKUP;
#  SHUTDOWN ABORT;
}


Проблема HPIUM на Linix'е - на солярку не восстановим.

ora:gamma:STR:11107_64:/oracle/admin: mkdir /oracle/data/mtseip/arch
ora:gamma:STR:11107_64:/oracle/admin: mkdir /oracle/data/mtseip/adump
ora:gamma:STR:11107_64:/oracle/admin: mkdir /oracle/data/mtseip/diag
ora:gamma:STR:11107_64:/oracle/admin: mkdir /oracle/data/mtseip/data/
ora:gamma:STR:11107_64:/oracle: mkdir /oracle/oradata
ora:gamma:STR:11107_64:/oracle/oradata: ln -s /oracle/data/mtseip/data/ /oracle/oradata/hpium





rman target / catalog rman11/rcat11@rdb msglog /oracle/admin/hpium/restore_hpium.log append
startup nomount;



-Восстановить управляющий файл в новое место:
RUN
{
  ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
  SEND 'NB_ORA_SERV=nbumas-mo-cen, NB_ORA_CLIENT=miida'; # NB_ORA_CLIENT которым делался бэкап
  RESTORE CONTROLFILE FROM AUTOBACKUP;
  ALTER DATABASE MOUNT;
}


Восстановление на указанный момент времени:


SET ARCHIVELOG DESTINATION TO '/oracle/data/mtseip/arch/'

RUN {
ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
SEND 'NB_ORA_SERV=nbumas-mo-cen, NB_ORA_CLIENT=miida'; # NB_ORA_CLIENT которым делался бэкап
RESTORE DATABASE;
RELEASE CHANNEL ch00;
}

RUN {
ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
SEND 'NB_ORA_SERV=nbumas-mo-cen, NB_ORA_CLIENT=miida'; # NB_ORA_CLIENT которым делался бэкап
RESTORE DATABASE VALIDATE;
RELEASE CHANNEL ch00;
}



sql 'alter database open resetlogs';
----------------------------------
Восстановление архивлогов

RUN {
ALLOCATE CHANNEL ch01 TYPE 'SBT_TAPE';
SEND 'NB_ORA_SERV=nbumas-mo-cen, NB_ORA_CLIENT=miida'; # NB_ORA_CLIENT которым делался бэкап
restore ARCHIVELOG from logseq 39610 until sequence 40351;
RELEASE CHANNEL ch01;
}




RMAN Error Codes 6000-6999


RMAN-06000


could not open recovery manager library file: string
Cause:The "recover.bsq" file could not be opened.
Action: Check that the file was installed correctly and that the user running RMAN has authority to read the file.

RMAN-06001


error parsing job step library
Cause:A syntax error was encountered while parsing "recover.bsq".
Action: Ensure that the correct version of the file is installed and that it has not been modified in any way.

RMAN-06002


command not allowed when not connected to a recovery catalog
Cause:A command that is allowed only when a recovery catalog connect string was supplied was attempted.
Action: Avoid using the command, or restart RMAN and supply a recovery catalog connect string via the CATALOG parameter.

RMAN-06003


ORACLE error from target database: string
Cause:This message should be accompanied by other error message(s) indicating the cause of the error.
Action: Check the accompanying errors.

RMAN-06004


ORACLE error from recovery catalog database: string
Cause:This message should be accompanied by other error message(s) indicating the cause of the error.
Action: Check the accompanying errors.

RMAN-06005


connected to target database: string (DBID=string)
Cause:This is an informational message only.
Action: No action is required.

RMAN-06006


connected to target database: string (not mounted)
Cause:This is an informational message only.
Action: No action is required.

RMAN-06007


target database not mounted and db_name not set in init.ora
Cause:The target database has not mounted the control file, and its "init.ora" file does not specify the DB_NAME parameter.
Action: MOUNT the target database, or add the DB_NAME parameter to its "init.ora" and restart the instance.

RMAN-06008


connected to recovery catalog database
Cause:This is an informational message only.
Action: No action is required.

RMAN-06009


using target database control file instead of recovery catalog
Cause:This is an informational message only.
Action: No action is required.

RMAN-06010


error while looking up datafile: string
Cause:An error occurred while looking up the specified datafile in the recovery catalog or target database control file.
Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the filename is entered correctly. If the datafile was added recently, then a RESYNC CATALOG must be done to update the recovery catalog.

RMAN-06011


invalid level specified: number
Cause:An invalid incremental backup level was specified.
Action: Incremental backup level must be between 0 and 4.

RMAN-06012


channel: string not allocated
Cause:A RELEASE or SETLIMIT command was found for a channel identifier that was not yet allocated.
Action: Correct the channel identifier, or add an ALLOCATE CHANNEL command.

RMAN-06013


duplicate channel identifier found: string
Cause:A channel identifier was reused without first releasing the channel.
Action: Add a RELEASE CHANNEL command.

RMAN-06014


command not implemented yet: string
Cause:Not all commands are implemented for the beta release.
Action: Avoid using the command.

RMAN-06015


error while looking up datafile copy name: string
Cause:An error occurred while looking up the specified datafile copy name in the recovery catalog or target database control file.
Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the filename is entered correctly. If the datafilevopy was created when the recovery catalog was not available, then a RESYNC CATALOG must be done to update the recovery catalog.

RMAN-06016


duplicate backup operand specified: string
Cause:The specified operand appears more than once in the same backup specifier or backup command.
Action: Delete the duplicated operand.

RMAN-06017


initialization of parser failed
Cause:The parser package initialization routine returned an error.
Action: This message should be accompanied by other error message(s) indicating the cause of the error.

RMAN-06018


duplicate operand specified in backup specification: string
Cause:A backup specification operand appears more than once in a backup specification.
Action: Delete the duplicate operand.

RMAN-06019


could not translate tablespace name "string"
Cause:An error occurred while looking up the specified tablespace name in the recovery catalog or target database control file.
Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the tablespace is entered correctly. If the tablespace was added recently, then a RESYNC CATALOG must be done to update the recovery catalog.

RMAN-06020


connected to auxiliary database (not started)
Cause:This is an informational message only.
Action: No action is required.

RMAN-06021


FROM DATAFILECCOPY/BACKUPSET may not be specified with archive logs
Cause:The FROM DATAFILECCOPY/BACKUPSET option applies only to datafile and control file restores.
Action: Use this option only for datafile and control file restores.

RMAN-06022


invalid level specified for image copy: number
Cause:An invalid incremental backup level was specified for an image copy.
Action: Incremental backup level must be 0 for image copies.

RMAN-06023


no backup or copy of datafile number found to restore
Cause:A datafile, tablespace, or database restore could not proceed because no backup or copy of the indicated file was found. It may be the case that a backup or copy of this file exists but does not satisfy the criteria specified in the user's restore operands.
Action: None - this is an informational message. See message 6026 for further details.

RMAN-06024


no backup or copy of the control file found to restore
Cause:A control file restore could not proceed because no backup or copy of the control file was found. It may be the case that a backup or copy of this file exists but does not satisfy the criteria specified in the user's restore operands.
Action: None - this is an informational message. See message 6026 for further details.

RMAN-06025


no backup of log thread number seq number lowscn string found to restore
Cause:An archive log restore restore could not proceed because no backup of the indicated archived log was found. It may be the case that a backup of this file exists but does not satisfy the criteria specified in the user's restore operands.
Action: None - this is an informational message. See message 6026 for further details.

RMAN-06026


some targets not found - aborting restore
Cause:Some of the files specified for restore could not be found. Message 6023, 6024, or 6025 is also issued to indicate which files could not be found. Some common reasons why a file can not be restored are that there is no backup or copy of the file that is known to recovery manager, or there are no backups or copies that fall within the criteria specified on the RESTORE command, or some datafile copies have been made but not cataloged.
Action: The Recovery Manager LIST command can be used to display the backups and copies that Recovery Manager knows about. Select the files to be restored from that list.

RMAN-06027


no archive logs found that match specification
Cause:An archive log record specifier did not match any archive logs in the recovery catalog.
Action: Resubmit the command with a different archive log record specifier. The rman LIST command can be used to display all archive logs that Recovery Manager knows about.

RMAN-06028


duplicate operand specified in restore specification: string
Cause:The CHANNEL, TAG, FROM, PARMS, VALIDATE, DEVICE TYPE, CHECK READONLY or DB_UNIQUE_NAME option was specified more than once in the restore command or in one of the restore specifications.
Action: Correct and resubmit the comand.

RMAN-06029


the control file may be included only in a datafile backup set
Cause:The "include current/standby control file" option was specified for an archive log backup set.
Action: Use this option only for datafile backup sets.

RMAN-06030


the DELETE [ALL] INPUT option may not be used with a datafile backup set
Cause:The DELETE [ALL] INPUT option was specified for a backup that contains the current control file or datafiles.
Action: Remove the option and resubmit the command.

RMAN-06031


could not translate database keyword
Cause:An error was received when calling dbms_rcvman
Action: This message should be accompanied by other error message(s) indicating the cause of the error.

RMAN-06032


at least 1 channel of TYPE DISK must be allocated to execute a COPY command
Cause:No channel of TYPE DISK was allocated.
Action: Allocate a channel of TYPE DISK and re-issue the command.

RMAN-06033


channel string not allocated
Cause:An rman command requests a specific channel, but the requested channel has not been allocated.
Action: ALLOCATE the channel, or correct the channel identifier.

RMAN-06034


at least 1 channel must be allocated to execute this command
Cause:No channels were allocated.
Action: ALLOCATE a channel.

RMAN-06035


wrong version of recover.bsq, expecting string, found string
Cause:The "recover.bsq" file is incompatible with the RMAN executable.
Action: Install the correct version of recover.bsq.

RMAN-06036


datafile number is already restored to file string
Cause:A SET NEWNAME command was issued to restore a datafile to a location other than the original datafile, and Recovery Manager determined that the best candidate for restoring the file is the datafile copy with the same name, therefore the file is already restored and no action need be taken.
Action: None - this is an informational message.

RMAN-06038


recovery catalog package detected an error
Cause:A call to dbms_rcvman returned an error.
Action: This message should be accompanied by other error message(s) indicating the cause of the error.

RMAN-06039


no set newname command has been issued for datafile number
Cause:A SWITCH command was specified for a datafile, but no destination was specified and no SET NEWNAME command has been previously issued for that file. An explicit file to switch to must be specified if no SET NEWNAME command has been issued.
Action: Correct and resubmit the SWITCH command.

RMAN-06040


control file is already restored to file string
Cause:The best candidate control file for restoration is the one that is named in the RESTORE CONTROLFILE command, hence no action need be taken.
Action: None - this is an informational message.

RMAN-06041


cannot switch file number to copy of file number
Cause:An attempt was made to switch a datafile to a copy of a different datafile.
Action: Correct and resubmit the SWITCH command.

RMAN-06042


PLUS ARCHIVELOG option is not supported with non-datafile backups
Cause:The PLUS ARCHIVELOG option was supplied but does not apply to this type of backup.
Action: Remove the PLUS ARCHIVELOG operand and re-enter the command.

RMAN-06043


TAG option not supported for archive log copies
Cause:The tag option was supplied but does not apply to this type of copy.
Action: Remove the TAG operand and re-enter the command

RMAN-06045


LEVEL option not supported for archive log or current/standby control file copies
Cause:The LEVEL option was supplied but does not apply to this type of copy.
Action: Remove the LEVEL operand and re-enter the command.

RMAN-06046


archive log name: string
Cause:An error occurred while translating an archive log name to its recovery catalog recid/timestamp. This message should be accompanied by other error message(s) indicating the cause of the error.
Action: Check the accompanying errors.

RMAN-06047


duplicate datafile number specified for restoration from copy
Cause:The indicated datafile was specified more than once in the same restore command.
Action: Correct and resubmit the RESTORE command.

RMAN-06048


duplicate control file specified for restoration from copy
Cause:The control file was specified more than once in the same RESTORE command.
Action: Correct and resubmit the RESTORE command.

RMAN-06049


CHECK LOGICAL option not supported for archive log or current/standby control file copies
Cause:The check logical option was supplied but does not apply to this type of copy.
Action: Remove the CHECK LOGICAL operand and re-enter the command

RMAN-06050


archive log thread number sequence number is already on disk as file string
Cause:An archive log which was requested to be restored (either explicitely or via a range specification) does not need to be restored because it already exists on disk.
Action: None - this is an informational message

RMAN-06051


DELETE INPUT option not implemented yet
Cause:This option was specified in a backup specification.
Action: Remove the DELETE INPUT option.

RMAN-06052


no parent backup or copy of datafile number found
Cause:An incremental backup at level 1 or higher could not find any parent backup or copy of the indicated datafile. A level 0 backup of the datafile will be taken automatically.
Action: This is an informational message only.

RMAN-06053


unable to perform media recovery because of missing log
Cause:This message is accompanied with another message identifying the missing log. The log would be needed to perform the media recovery, but the log is not on disk and no backup set containing the log is available.
Action: Determine if a backup set containing the log can be made available. If so, then use the CHANGE command to make the backup set available and retry the command. If not, then a point in time recovery up to the missing log is the only alternative.

RMAN-06054


media recovery requesting unknown log: thread string seq string lowscn string
Cause:Media recovery is requesting a log whose existance is not recorded in the recovery catalog or control file.
Action: If a copy of the log is available, then add it to the recovery catalog and/or control file via a CATALOG command and then retry the RECOVER command. If not, then a point in time recovery up to the missing log is the only alternative and database can be opened using ALTER DATABASE OPEN RESETLOGS command.

RMAN-06055


could not find log sequence string thread string
Cause:A log which was on disk at the start of media recovery or which should have been restored from a backup set could not be found.
Action: Check the Recovery Manager message log to see if the log was restored by a previous job step. If so, then check the V$ARCHIVED_LOG view to see if the log is listed in the control file. If so, then validate that the log exists on disk and is readable. If the log was not restored, or was restored but no record of the log exists in V$ARCHIVED_LOG, then contact Oracle Customer Support.

RMAN-06056


could not access datafile number
Cause:A backup or copy could not proceed because the datafile header could not be read or the header was not valid.
Action: Make the datafile accessible or skip it.

RMAN-06057


a standby control file cannot be included along with a current control file
Cause:"current controlfile" was specified along with "standby controlfile".
Action: Remove "current controlfile" or "standby controlfile" from backup specification.

RMAN-06058


a current control file cannot be included along with a standby control file
Cause:"standby controlfile" was specified along with "current controlfile".
Action: Remove "standby controlfile" or "current controlfile" from backup specification.

RMAN-06059


expected archived log not found, lost of archived log compromises recoverability
Cause:The archived log was not found. The repository thinks it does exist. If the archived log has in fact been lost and there is no backup, then the database is no longer recoverable across the point in time covered by the archived log. This may occur because the archived log was removed by an outside utility without updating the repository.
Action: If the archived log has been removed with an outside utility and the archivelog has already been backed up, then you can synchronize the repository by running CROSSCHECK ARCHIVELOG ALL. If the archivelog has not been previously backed up, then you should take a full backup of the database and archivelogs to preserve recoverability. Previous backups are not fully recoverable.

RMAN-06060


WARNING: skipping datafile compromises tablespace string recoverability
Cause:SKIP INACCESSIBLE or SKIP OFFLINE option resulted in skipping datafiles during BACKUP. If the datafile has in fact been lost and there is no backup, then the tablespace is no longer recoverable without ALL archive logs since datafile creation. This may occur because the datafile was deleted by an outside utility or the datafile is made OFFLINE [DROP].
Action: If there is no backup of skipped datafiles and the tablespace has to be recoverable without ALL archive logs since datafile creation, then you should make these datafiles available for backup.

RMAN-06061


WARNING: skipping archivelog compromises recoverability
Cause:SKIP INACCESSIBLE option resulted in skipping archivelogs during BACKUP. If the archived log has in fact been lost and there is no backup, then the database is no longer recoverable across the point in time covered by the archived log. This may occur because archived log was removed by an outside utility without updating the repository.
Action: If the archived log has been removed with an outside utility and the archivelog has already been backed up, then you can synchronize the repository by running CROSSCHECK ARCHIVELOG ALL. If the archivelog has not been previously backed up, then you should take a full backup of the database and archivelogs to preserve recoverability. Previous backups are not fully recoverable.

RMAN-06062


can not backup SPFILE because the instance was not started with SPFILE
Cause:A backup command requested a backup of the SPFILE, but no SPFILE was used to startup the instance.
Action: Create an SPFILE and re-start the instance using the SPFILE or modify the command.

RMAN-06063


DBID is not found in the recovery catalog
Cause:DBID is not found in the recovery catalog.
Action: Verify that the DBID is correct and restart the command.

RMAN-06064


creating datafile fno=string name=string
Cause:RESTORE/RECOVER command was issued and there were no backup available for the datafile.
Action: This is an informational message only.

RMAN-06065


The backup operand [string] conflicts with another specified operand.
Cause:The user attempted to use two (or more) conflicting operands within the same statement.
Action: Remove one or both of the conflicting operands.

RMAN-06066


the target database must be mounted when issuing a RECOVER command
Cause:A RECOVER command was issued, but the target database control file is not mounted.
Action: Mount the target database control file by issuing ALTER DATABASE MOUNT via Enterprise Manager or Server Manager.

RMAN-06067


RECOVER DATABASE required with a backup or created control file
Cause:The control file has been restored from a backup or was created via ALTER DATABASE CREATE CONTROLFILE.
Action: Use the RECOVER DATABASE command to perform the recovery.

RMAN-06068


recovery aborted because of missing datafiles
Cause:This error should be accompanied by one or more instances of message ORA-06094.
Action: Refer to message ORA-06094.

RMAN-06069


the filename for datafile string is missing in the control file
Cause:Media recovery of a backup control file added this datafile to the control file, but it does not set the filename because that is unsafe.
Action: If the datafile is on disk, then issue ALTER DATABASE RENAME to correct the control file. Otherwise, RESTORE the datafile, and then use SWITCH to make it known to the control file. If the tablespace containing this datafile will be dropped, then reissue the RECOVER command with a SKIP clause to skip recovery of this tablespace.

RMAN-06070


DBWR could not identify datafile string
Cause:DBWR could not find the specified datafile.
Action: Ensure that the datafile exists and is accessible.

RMAN-06071


could not open datafile string
Cause:An error was encountered when trying to open the specified datafile.
Action: Ensure that the datafile exists and is accessible.

RMAN-06073


file header is corrupt for datafile string
Cause:ORACLE detected a corruption in the file header. A media failure has probably occurred.
Action: RESTORE the datafile to a new location, then do a SWITCH, and then retry the RECOVER command.

RMAN-06074


file string is not an ORACLE datafile
Cause:The file header indicates that this file is not a datafile. The file may have been overlaid or corrupted.
Action: RESTORE the datafile to a new location, then do a SWITCH, and then retry the RECOVER command.

RMAN-06075


datafile string does not belong to this database
Cause:The file header indicates that this file belongs to some other ORACLE database.
Action: RESTORE the datafile to a new location, then do a SWITCH, and then retry the RECOVER command.

RMAN-06076


datafile string contains wrong datafile
Cause:The datafile header indicates the file contains a different datafile number.
Action: RESTORE the datafile, and then retry the RECOVER command.

RMAN-06077


datafile string is a different version than contained in the control file
Cause:The control file entry for this datafile specifies a different version of this datafile. Different versions of a datafile can exist when a tablespace is dropped, and a new tablespace is created which reuses the same datafile numbers.
Action: If the datafile is correct, the fix the control file by using the SWITCH command. Otherwise, RESTORE the correct version of this datafile and retry the RECOVER command.

RMAN-06078


the control file is older than datafile string
Cause:The control file appears to be older than the specified datafile, but it is not marked as a backup control file. This indicates that the control file has been replaced with an older version. This error does not occur when a backup controlfile which was created via Recovery Manager or the ALTER DATABASE BACKUP CONTROLFILE command is restored because such controlfiles are marked as backups.
Action: RESTORE a control file and perform RECOVER DATABASE.

RMAN-06079


database must be mounted to perform recovery
Cause:A RECOVER command was issued, but the target database is not mounted.
Action: Issue ALTER DATABASE MOUNT.

RMAN-06080


SWITCH required for datafile string
Cause:The control file record for this datafile is for an older incarnation of the datafile. A SWITCH command must be issued to updated the control file before doing RECOVER.
Action: Issue SWITCH command then retry RECOVER.

RMAN-06081


error reading datafile header for datafile string, code string
Cause:X$KCVFH returned the specified code in the hxerr column when it was queried for the specified datafile.
Action: Ensure the datafile exists and is readable. Using a newer release of Recovery Manager may return a more meaningful error message. If you have no newer version of Recovery Manager, contact Oracle Customer Support.

RMAN-06082


datafile copy tag string is ambiguous
Cause:The specified tag refers to multiple datafile copies belonging to different datafiles.
Action: Specify the datafile copy by filename rather than by tag.

RMAN-06083


error when loading stored script string
Cause:The recovery catalog database returned an error. This error explains the cause of the problem.
Action: Correct the problem and retry.

RMAN-06084


the target database may not be mounted when issuing REPLICATE
Cause:A REPLICATE command was issued, but the target database is already mounted.
Action: dismount the target database control file by issuing ALTER DATABASE CLOSE and ALTER DATABASE DISMOUNT via Enterprise Manager or Server Manager.

RMAN-06085


must use SET NEWNAME command to restore datafile string
Cause:A RESTORE command for the specified datafile could not find a destination name for the specified datafile.
Action: Add a SET NEWNAME command prior to the RESTORE command to specify the restore destination for this file.

RMAN-06086


offline files may only be skipped in a datafile backup set
Cause:The SKIP OFFLINE option was specified for an archive log backup set.
Action: Use this option only for datafile backup sets.

RMAN-06087


read-only files may only be skipped in a datafile backup set
Cause:The SKIP READONLY option was specified for an archive log backup set.
Action: Use this option only for datafile backup sets.

RMAN-06088


datafile copy string not found or out of sync with catalog
Cause:The indicated file is not found, or is found but is not the same file that the recovery catalog thinks it is. It is likely that some operation outside of Recovery Manager has altered the file, or that Recovery Manager has not resynced with the target database.
Action: Re-catalog the file and retry the operation.

RMAN-06089


archived log string not found or out of sync with catalog
Cause:The indicated file is not found, or is found but is not the same file that the recovery catalog thinks it is. It is likely that some operation outside of Recovery Manager has altered the file, or that Recovery Manager has not resynced with the target database.
Action: Re-catalog the file and retry the operation.

RMAN-06090


error while looking up control file copy: string
Cause:An error occurred while looking up the specified control file copy in the recovery catalog or target database control file.
Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the filename is entered correctly. If the control file copy was created when the recovery catalog was not available, then a RESYNC CATALOG must be done to update the recovery catalog.

RMAN-06091


no channel allocated for maintenance (of an appropriate type)
Cause:A command was entered that requires a maintenance channel, and no maintenance channel is allocated, or none of the appropriate type.
Action: Use ALLOCATE CHANNEL FOR MAINTENANCE before deleting backup pieces, or using the CROSSCHECK or DELETE EXPIRED commands. Proxy copies require a non-DISK channel.

RMAN-06092


error while looking up backup piece
Cause:An error occurred while looking up the specified backup piece in the recovery catalog or target database control file.
Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the name or key is entered correctly. If the backup piece was created when the recovery catalog was not available, then a RESYNC CATALOG must be done to update the recovery catalog.

RMAN-06093


recovery catalog contains obsolete version of datafile string
Cause:The specified datafile number was dropped and then reused. The control file mounted by the target database contains the newer version of the datafile, but the recovery catalog contains information about only the older version.
Action: Issue a RESYNC command to update the recovery catalog, then reissue the failing command. If the error persists, contact Oracle Customer Support.

RMAN-06094


datafile string must be restored
Cause:A RECOVER command was issued, and the recovery catalog indicates the specified datafile should be part of the recovery, but this datafile is not listed in the control file, and cannot be found on disk.
Action: Issue a RESTORE command for this datafile, using the same UNTIL clause specified to the RECOVER command (if any), then reissue the RECOVER.

RMAN-06095


a backup control file must be restored to recover datafile string
Cause:The controfile currently mounted by the target database contains a newer incarnation of the datafile than the recovery catalog indicates is appropriate for the point-in-time being recovered to.
Action: Restore the control file, using the same UNTIL clause specified on the failing RECOVER command, then reissue the command. If no control file can be restored, then you should issue a CREATE CONTROLFILE command.

RMAN-06096


SWITCH required for newname of datafile string to take effect
Cause:A SET NEWNAME was issued for this datafile, but no SWITCH command was issued before the RECOVER command.
Action: Issue a SWITCH command to make the newname take effect before doing RECOVER.

RMAN-06098


the target database must be mounted when issuing a BACKUP command
Cause:A BACKUP command was issued, but the target database control file is not mounted.
Action: Mount the target database control file by issuing ALTER DATABASE MOUNT via Enterprise Manager or Server Manager.

RMAN-06099


error occurred in source file: string, line: number
Cause:See accompanying error
Action: See accompanying error

RMAN-06100


no channel to restore a backup or copy of datafile number
Cause:A datafile, tablespace, or database restore could not proceed because the backup of the indicated file exists on a device type that was not allocated for restore.
Action: None - this is an informational message. See message 6026 for further details.

RMAN-06101


no channel to restore a backup or copy of the control file
Cause:A control file restore could not proceed because the backup of the indicated file exists on a device type that was not allocated for restore.
Action: None - this is an informational message. See message 6026 for further details.

RMAN-06102


no channel to restore a backup or copy of log thread number seq number lowscn string
Cause:An archive log restore restore could not proceed because the backup of the indicated file exists on a device type that was not allocated for restore.
Action: None - this is an informational message. See message 6026 for further details.

RMAN-06103


duplicate qualifier found in REPORT command: string
Cause:The indicated qualifier appears more than once in a REPORT qualifier list.
Action: delete the duplicate qualifier

RMAN-06105


duplicate qualifier found in LIST command: string
Cause:The indicated qualifier appears more than once in a LIST qualifier list.
Action: delete the duplicate qualifier

RMAN-06106


this command requires that target database be mounted
Cause:A command was issued that requires the target database to be mounted, but the target database is not mounted.
Action: Mount the target database control file by issuing ALTER DATABASE MOUNT via Enterprise Manager or Server Manager.

RMAN-06107


WARNING: control file is not current for REPORT NEED BACKUP DAYS
Cause:The REPORT NEED BACKUP DAYS command may report some files as requiring backups when they really do not, because the most current online status of the file is not known unless a current control file is mounted.
Action: No action is required, however, a current control file should be mounted, if possible, to get the most accurate REPORT output.

RMAN-06108


changed datafile copy unvailable
Cause:This is an informational message only.
Action: No action is required.

RMAN-06109


changed archive log unavailable
Cause:This is an informational message only.
Action: No action is required.

RMAN-06110


changed control file copy unavailable
Cause:This is an informational message only.
Action: No action is required.

RMAN-06111


changed backup piece unavailable
Cause:This is an informational message only.
Action: No action is required.

RMAN-06112


changed datafile copy available
Cause:This is an informational message only.
Action: No action is required.

RMAN-06113


changed archive log available
Cause:This is an informational message only.
Action: No action is required.

RMAN-06114


changed control file copy available
Cause:This is an informational message only.
Action: No action is required.

RMAN-06115


changed backup piece available
Cause:This is an informational message only.
Action: No action is required.

RMAN-06116


cannot crosscheck unavailable object
Cause:An attempt was made to crosscheck an object which is unavailable.
Action: Make object available and try again or don't crosscheck object.

RMAN-06117


cannot do DELETE EXPIRED on an object which is not expired
Cause:An attempte was made to DELETE EXPIRED an object which is not expired.
Action: Remove EXPIRED keyword, crosscheck object, or don't delete object.

RMAN-06118


a backup control file older than SCN string must be used for this recovery
Cause:An attempt was made to recover the database, but some files had no backup, and were not present in the control file at the beginning of the restore. This happens when the control file used during the recovery is a backup control file taken before the creation of some of the files that had no backup. In this situation, the control file that is used must be taken before the creation of all files that have no backup. This will enable RMAN to automatically re-create all of the files that had no backup.
Action:Restore a control file that was backed up before the specified SCN. The following RMAN commands can be used to do this: SET UNTIL SCN ;(where is the SCN displayed in the message) RESTORE CONTROLFILE;

RMAN-06119


uncataloged datafile copy
Cause:This is an informational message only.
Action: No action is required.

RMAN-06120


uncataloged archive log
Cause:This is an informational message only.
Action: No action is required.

RMAN-06121


uncataloged control file copy
Cause:This is an informational message only.
Action: No action is required.

RMAN-06122


CHANGE .. UNCATALOG not supported for BACKUPSET
Cause:The CHANGE BACKUPSET .. UNCATALOG command was entered. The UNCATALOG operation is not supported with backup set.
Action: Use CHANGE BACKUPSET .. DELETE instead.

RMAN-06123


operation not supported without the recovery catalog or mounted control file
Cause:A command was used which requires a connection to a recovery catalog database or the target database to be mounted. The command cannot be used when no backup repository is available.
Action: If a recovery catalog database is available, then connect to the recovery catalog and retry the command, otherwise enter a different command.

RMAN-06124


error while looking up datafile copy key: number
Cause:An error occurred while looking up the specified datafile copy key in the recovery catalog.
Action: This error is accompanied by other errors describing the reason for the failure.

RMAN-06125


error while looking up archive log key: number
Cause:An error occurred while looking up the specified archive log key in the recovery catalog.
Action: This error is accompanied by other errors describing the reason for the failure.

RMAN-06126


skipping offline file string
Cause:The indicated file will not be included in the backup set because it is offline and the SKIP OFFLINE option was specified.
Action: No action is required.

RMAN-06127


skipping read-only file string
Cause:The indicated file will not be included in the backup set because it is read only and the SKIP READONLY option was specified.
Action: No action is required.

RMAN-06128


skipping inaccessible file string
Cause:The indicated file will not be included in the backup set because it could not be read, and the SKIP INACCESSIBLE option was specified.
Action: No action is required.

RMAN-06129


invalid reserved channel ID: string
Cause:The specified channel id is invalid. DELETE and DEFAULT are reserved channel names and may not be specified by users.
Action: Specify a different channel ID.

RMAN-06131


skip offline/readonly only allowed with current control file
Cause:The SKIP OFFLINE and SKIP READONLY options are only permitted when the target database control file is current. When the target control file is not current, it is not possible to obtain a datafile's offline/readonly status.
Action: Remove the skip option or mount a current control file on the target database.

RMAN-06132


cannot backup datafile string because it is not in the control file
Cause:A backup command was issued that includes the specified datafile, but the datafile is not listed in the control file. The control file is not current (it is a backup or a created control file).
Action: Recover the control file to make it current, then retry the backup command.

RMAN-06133


recovery catalog may have obsolete data for datafile string
Cause:A RESTORE UNTIL was issued, and the recovery catalog choose an older incarnation of the datafile than is listed in the control file.
Action: If the recovery catalog has correct data for the datafile, then restore a backup control file using the same UNTIL clause, then retry the datafile restore. Otherwise, restore a backup of the incarnation of the datafile listed in the control file.

RMAN-06134


host command complete
Cause:An operating system command has completed.
Action: None - this is an informational message.

RMAN-06135


error executing host command: string
Cause:A host command returned a non-zero return code.
Action: Correct the offending command.

RMAN-06136


ORACLE error from auxiliary database: string
Cause:This message should be accompanied by other error message(s) indicating the cause of the error.
Action: Check the accompanying errors.

RMAN-06137


must have recovery catalog for REPORT SCHEMA AT TIME
Cause:A 'REPORT SCHEMA at_clause' command was issued, but there is no recovery catalog database.
Action: If you are not using a recovery catalog, then you may only issue the 'REPORT SCHEMA' command with no at_clause.

RMAN-06138


control file not mounted - must specify AT clause with REPORT command
Cause:A 'REPORT SCHEMA' with no at_clause was issued, and there is no recovery catalog, and there is also no control file mounted at the target database, so there is no place to get the information about the current list of files comprising the database.
Action: Use a recovery catalog or mount a control file at the target database.

RMAN-06139


WARNING: control file is not current for REPORT SCHEMA
Cause:A 'REPORT SCHEMA' with no at_clause was issued, and there is no recovery catalog, and the control file mounted by the target instance is not current, so the information about the current list of datafiles may not be current.
Action: Use a recovery catalog or mount a current control file.

RMAN-06140


cannot specify TAG option with LIST INCARNATION
Cause:The TAG option was specified with LIST INCARNATION. This is not permitted because there is no TAG associated with a database incarnation.
Action: Remove the TAG option and re-run the LIST command.

RMAN-06141


cannot specify ARCHIVELOG LIKE option with RESTORE
Cause:The ARCHIVELOG LIKE option was specified with RESTORE. This is not permitted because recovery catalog contains only those records that are not deleted from disk.
Action: Remove the ARCHIVELOG LIKE option and re-run the command.

RMAN-06142


DEVICE TYPE cannot be specified with this command
Cause:The DEVICE TYPE option was specified with a command that does not support it.
Action: Remove the DEVICE TYPE option and re-run the command.

RMAN-06143


LIKE may only be specified with COPY
Cause:The LIKE option was specified with a RMAN command. This is not permitted because only copies of datafiles, control files or archive logs have file names that may be tested with a LIKE operand.
Action: Remove the LIKE option and re-run the RMAN command.

RMAN-06144


FROM or UNTIL may not be specified with LIST INCARNATION
Cause:The FROM or UNTIL option was specified with LIST INCARNATION. This is not permitted because there is no time associated with a database incarnation.
Action: Remove the FROM or UNTIL option and re-run the LIST command.

RMAN-06145


control file is not current - obsolete file list may be incomplete
Cause:A CHANGE or REPORT command needs to compute the list of backups that are redundant and may be deleted. If the mounted control file is not current, it may not be possible to determine if a satisfactory backup exists for files which have been offline since the last OPEN RESETLOGS.
Action: No action need be taken - this is an informational message only. To ensure a complete report of obsolete backups, mount a current control file.

RMAN-06146


changes found for file number beyond offline SCN
Cause:A CHANGE or REPORT command needs to compute the list of backups that are redundant and may be deleted. A backup was found for a file which is shown as offline in the target database control file, but the backup contains changes beyond the SCN when the file went offline. This is most likely because the target database control file is not really current, but is a restored copy of an older control file.
Action: Mount a current control file or a backup control file.

RMAN-06147


no obsolete backups found
Cause:A CHANGE or REPORT command could find no files that meet the specified criteria for obsoleteness.
Action: None - this is an informational message.

RMAN-06148


redundancy count must be greater than zero
Cause:The REDUNDANCY operand specified for a CHANGE or REPORT OBSOLETE command was zero.
Action: Specify a REDUNDANCY operand of 1 or greater.

RMAN-06150


auxiliary name for datafile number set to: string
Cause:This message is issued in response to a CONFIGURE AUXNAME command.
Action: None - this is an informational message.

RMAN-06151


datafile string creation scn string
Cause:This is an informational message. It should be accompanied by other messages.
Action: none

RMAN-06153


validation failed for datafile copy
Cause:The CHANGE DATAFILECOPY VALIDATE command found that the datafile copy could not be found or no longer contains the same data, so its record was deleted from the recovery catalog.
Action: None - this is an informational message.

RMAN-06154


validation succeeded for datafile copy
Cause:The CHANGE DATAFILECOPY VALIDATE command found that the datafile copy still matches its data in the recovery catalog.
Action: None - this is an informational message.

RMAN-06155


validation failed for control file copy
Cause:The CHANGE CONTROLFILECOPY VALIDATE command found that the control file copy could not be found or no longer contains the same data, so its record was deleted from the recovery catalog.
Action: None - this is an informational message.

RMAN-06156


validation succeeded for control file copy
Cause:The CHANGE CONTROLFILECOPY VALIDATE command found that the control file copy still matches its data in the recovery catalog.
Action: None - this is an informational message.

RMAN-06157


validation failed for archived log
Cause:The CROSSCHECK ARCHIVELOG command determined that the archived log could not be found or no longer contained the same data, so its record was marked expired.
Action: None - this is an informational message.

RMAN-06158


validation succeeded for archived log
Cause:The CROSSCHECK ARCHIVELOG command determined that the archived log still matches its data.
Action: None - this is an informational message.

RMAN-06159


error while looking up backup set
Cause:An error occurred while looking up the specified backup set in the recovery catalog or target database control file.
Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the key is entered correctly. If the backup set was created when the recovery catalog was not available, then a RESYNC CATALOG must be done to update the recovery catalog.

RMAN-06160


no backup pieces found for backup set key: number
Cause:No backup pieces for the requested backup set were found in the recovery catalog, or the target database control file.
Action: Specify an existing backup set.

RMAN-06161


error when inspecting auxiliary filename: string
Cause:This error is accompanied by other errors explaining the cause.
Action: Correct the auxiliary filename if it is wrong via the CONFIGURE AUXNAME command.

RMAN-06162


sql statement: string
Cause:This is the sql statement about to be executed for a SQL command.
Action: None, informational message only.

RMAN-06163


some datafiles cannot be recovered, aborting the RECOVER command
Cause:This message should be followed by one or more 6162 or 6164 messages.
Action: Check the accompanying errors.

RMAN-06164


WARNING: no channel of required type allocated to recover datafile number
Cause:A RECOVER command could not proceed because incremental backup sets or archive log backup sets exist on a device type that has not been allocated.
Action: Use the LIST command to determine which device type is needed, then allocate a channel of that type.

RMAN-06165


datafile string is too old to recover, restore a more recent copy
Cause:The archived logs and/or incremental backup sets required to recover the datafile do not exist, but a more recent backup of the datafile exists which can be recovered.
Action: Issue a RESTORE for the datafile, then reissue the RECOVER command.

RMAN-06166


datafile string cannot be recovered
Cause:Incremental backups or archived redo logs needed to recover the datafile cannot be found, and no recoverable full backup or datafile copy exists.
Action: Use the LIST command to see if there is a backup set or datafile copy that can be made AVAILABLE. If not, then the datafile is unrecoverable. If a full or datafile copy exists, then a point-in-time recovery may be possible.

RMAN-06167


already connected
Cause:a CONNECT command was issued, but RMAN is already connected to the specified database.
Action: RMAN has no DISCONNECT command, so to connect to a different instance, exit RMAN and start it again.

RMAN-06168


no backup pieces with this tag found: string
Cause:A tag was used to specify a list of backup pieces, but no backup pieces with this tag could be found.
Action: Make sure the tag is specified correctly.

RMAN-06169


could not read file header for datafile string error reason string
Cause:The specified datafile could not be accessed. The reason codes are: 1 - filename is MISSINGxx in the control file 2 - file is offline 3 - file is not verified 4 - DBWR could not find the file 5 - unable to open file 6 - I/O error during read 7 - file header is corrupt 8 - file is not a datafile 9 - file does not belong to this database 10 - file number is incorrect 12 - wrong file version 15 - control file is not current
Action: If the error can be corrected, do so and retry the operation. The SKIP option can be used to ignore this error during a backup.

RMAN-06170


no control file copy found with offline range recid string stamp string datafile string
Cause:This offline range is needed for recovering the specified datafile, but the offline range record has aged out of the current control file and no control file copy with the record could be accessed. At least 1 control file copy containing the offline range was found in the recovery catalog and was in AVAILABLE status.
Action: Query the rc_controlfile_copy view for the names of all control file copies, then issue a CHANGE CONTROLFILECOPY ... VALIDATE; command for them. Then reissue the RECOVER command.

RMAN-06171


not connected to target database
Cause:A command was issued but no connection to the target database has been established.
Action: Issue a CONNECT TARGET command to connect to the target database.

RMAN-06172


no autobackup found or specified handle is not a valid copy or piece
Cause:A restore could not proceed because no autobackup was found or specified handle is not a valid copy or backup piece. In case of restore from autobackup, it may be the case that a backup exists, but it does not satisfy the criteria specified in the user's restore operands. In case of restore from handle, it may be the handle is not a backup piece or controflile copy. In may be that it does not exist.
Action: Modify autobackup search criteria or verify the handle.

RMAN-06173


no set newname command has been issued for datafile string when restore auxiliary
Cause:Auxiliary type was specified for the control file, but no SET NEWNAME command has been previously issued for a datafile.
Action: Issue SET NEWNAME command for every datafile in the recovery set.

RMAN-06174


not connected to auxiliary database
Cause:An auxiliary command was issued but no connection to a auxiliary database has been established.
Action: Issue a CONNECT AUXILIARY command to connect to the auxiliary database.

RMAN-06175


deleted script: string
Cause:A DELETE SCRIPT command was executed.
Action: None, informational message only.

RMAN-06176


no recovery required; all files are readonly or offline
Cause:A RECOVER DATABASE command does not need to recover any files because all of the files to be recovered are offline or read only. This can only occur when the SKIP clause includes the system tablespace.
Action: None, informational message only

RMAN-06177


restore not done; all files readonly, offline, or already restored
Cause:A RESTORE command does not need to restore any files, because all of the files to be restored are offline, read-only, or are already restored to their correct destinations.
Action: None, informational message only

RMAN-06178


datafile number not processed because file is offline
Cause:A RESTORE DATABASE or RECOVER DATABASE command omitted processing the indicated datafile because it is offline clean at the desired point in time.
Action: None, informational message only

RMAN-06179


datafile number not processed because file is read-only
Cause:A RESTORE DATABASE or RECOVER DATABASE command omitted processing the indicated datafile because it is part of a read-only tablespace at the desired point in time.
Action: None, informational message only

RMAN-06180


incremental backups require Enterprise Edition
Cause:A BACKUP command with INCREMENTAL LEVEL > 0 was specified.
Action: Use FULL, or INCREMENTAL LEVEL 0.

RMAN-06181


multiple channels require Enterprise Edition
Cause:Attempt to allocate more than 1 channel in a job.
Action: Remove all except one ALLOCATE CHANNEL command.

RMAN-06182


archive log larger than MAXSETSIZE: thread string seq string string
Cause:A BACKUP ARCHIVELOG command specified the MAXSETSIZE operand too low. The specified archive log is larger than MAXSETSIZE will allow.
Action: Increase MAXSETSIZE limit.

RMAN-06183


datafile or datafile copy larger than MAXSETSIZE: file# string string
Cause:A BACKUP DATAFILE(copy) command specified the MAXSETSIZE operand too low. The specified datafile is larger than MAXSETSIZE will allow.
Action: Increase MAXSETSIZE limit.

RMAN-06184


duplicate object in backup specifier: string string
Cause:A backup command specifies the same datafile or copy of a datafile multiple times.
Action: Eliminate the duplicates.

RMAN-06185


Recovery Manager incompatible with string database: RMAN number.number.number.number to number.number.number.number required
Cause:This version of recovery manager was incompatible with the indicated database or the dbms_backup_restore package installed in the indicated database.
Action: If the database has been upgraded from an earlier version, ensure that the catxxxx.sql script has been run successfully. Re-install dbmsbkrs.sql and prvtbkrs.plb if necessary. Otherwise, use a version of RMAN within the range specified in the error message.

RMAN-06186


PL/SQL package string.string version string in string database is too old
Cause:The specified PL/SQL package is a version that is too old to work with this version of the Recovery Manager (RMAN).
Action: If the database indicated is CATALOG, then you can use the UPGRADE CATALOG command to upgrade the recovery catalog to the most current version. If the database is TARGET or AUXILIARY, then you must either upgrade the specified database or use an older version of RMAN.

RMAN-06187


control file copy string not found or out of sync with catalog
Cause:The indicated file is not found, or is found but is not the same file that the recovery catalog thinks it is. It is likely that some operation outside of Recovery Manager has altered the file, or that Recovery Manager has not resynced with the target database.
Action: Re-catalog the file and retry the operation.

RMAN-06188


cannot use command when connected to a mounted target database
Cause:An attempt was made to issue a command that can be used only when there is no connection to the target database or when the target database is not mounted.
Action: Dismount the database or restart RMAN and use the command before connecting to the target database.

RMAN-06189


current DBID number does not match target mounted database (number)
Cause:SET DBID was used to set a DBID that does not match the DBID of the database to which RMAN is connected.
Action: If the current operation is a restore to copy the database, do not mount the database. Otherwise, avoid using the SET DBID command, or restart RMAN.

RMAN-06190


PL/SQL package string.string version string in string database is not current
Cause:RMAN detected an old version of the specified package. RMAN will execute in backwards-compatible mode.
Action: No action is required, but certain features and bug-fixes may not be available when RMAN runs in backwards-compatible mode. If the database is CATALOG, then you can use the UPGRADE CATALOG command to upgrade the recovery catalog to the most current version. If the database is TARGET or AUXILIARY, then you must either upgrade the specified database or use an older version of RMAN. The files that must be run to upgrade the target or auxiliary database are dbmsrman.sql and prvtrman.plb.

RMAN-06191


PL/SQL package string.string version string in string database is too new
Cause:RMAN detected an incompatible version of the specified package.
Action: Use a newer version of recovery manager. Message 6439 indicates the minimum required version of recovery manager.

RMAN-06192


maximum value for MAXPIECESIZE or MAXSETSIZE must be between 1 Kb and 2048 Gb
Cause:Input size for MAXPIECESIZE or MAXSETSIZE was out of range.
Action: Specify a valid size and retry the command.

RMAN-06193


connected to target database (not started)
Cause:This is an informational message only.
Action: The database must be started before any other RMAN commands are issued.

RMAN-06194


target database instance not started
Cause:A command was issued that requires the target database instance be started.
Action: Issue a STARTUP command to start the instance.

RMAN-06195


auxiliary database not started
Cause:A command was issued that requires the auxiliary database instance be started.
Action: Issue a STARTUP AUXILIARY command.

RMAN-06196


Oracle instance started
Cause:A STARTUP command completed successfully.
Action: None, this is an informational message.

RMAN-06197


Total System Global Area string bytes
Cause:This is an informational message only.
Action: No action is required.

RMAN-06198


%-24s string bytes
Cause:This is an informational message only.
Action: No action is required.

RMAN-06199


database mounted
Cause:This is an informational message only.
Action: No action is required.

RMAN-06200


Changed string objects to AVAILABLE status
Cause:This is an informational message only.
Action: No action is required.

RMAN-06201


Deleted string objects
Cause:This is an informational message only.
Action: No action is required.

RMAN-06202


Deleted string EXPIRED objects
Cause:This is an informational message only.
Action: No action is required.

RMAN-06203


Changed KEEP options for string objects
Cause:This is an informational message only.
Action: No action is required.

RMAN-06204


Changed string objects to UNAVAILABLE status
Cause:This is an informational message only.
Action: No action is required.

RMAN-06205


Uncataloged string objects
Cause:This is an informational message only.
Action: No action is required.

RMAN-06206


Crosschecked string objects
Cause:This is an informational message only.
Action: No action is required.

RMAN-06207


WARNING: string objects could not be deleted for string channel(s) due
Cause:This is an informational message only.
Action: No action is required.

RMAN-06208


to mismatched status. Use CROSSCHECK command to fix status
Cause:This is an informational message only.
Action: No action is required.

RMAN-06209


List of failed objects
Cause:This is an informational message only.
Action: No action is required.

RMAN-06210


List of Mismatched objects
Cause:This is an informational message only.
Action: No action is required.

RMAN-06211


==========================
Cause:This is an informational message only.
Action: No action is required.

RMAN-06212


Object Type Filename/Handle
Cause:This is an informational message only.
Action: No action is required.

RMAN-06213


--------------- ---------------------------------------------------
Cause:This is an informational message only.
Action: No action is required.

RMAN-06214


%-15s string
Cause:This is an informational message only.
Action: No action is required.

RMAN-06220


Creating automatic instance, with SID='string'
Cause:No connection to the auxiliary instance was provided, but the command requires an auxiliary instance.
Action: No action is required unless you want to create a permanent database, in which case you should stop the command and re-run it, providing an auxiliary instance connection.

RMAN-06221


Removing automatic instance
Cause:RMAN is removing the automatic auxiliary instance that was created for this command.
Action: No action is required.

RMAN-06223


starting up automatic instance string
Cause:This is an informational message only.
Action: No action is required.

RMAN-06224


Automatic instance created
Cause:This is an informational message only.
Action: No action is required.

RMAN-06225


shutting down automatic instance string
Cause:This is an informational message only.
Action: No action is required.

RMAN-06226


Automatic instance removed
Cause:This is an informational message only.
Action: No action is required.

RMAN-06230


List of Stored Scripts in Recovery Catalog
Cause:This message is issued in response to a LIST SCRIPT NAMES command. The following fields are shown for each script that is stored in the recovery catalog: Header indicating to what database the script belongs. Script Name: name of the script. Description: comment associated with this script.
Action: No action is required.

RMAN-06246


List of Database Incarnations
Cause:This message is issued in response to a LIST INCARNATION OF DATABASE command. The following fields are shown for each database that is registered with the recovery catalog: DB Key: This is the unique key which identifies this database in the recovery catalog. Inc Key: This is the unique key which identifies this incarnation of the database in the recovery catalog. DB Name: The name of the database. DB ID: The database ID. This is a number which remains the same for the life of the database, even if the database name is changed. Status: 'YES' if this is the current incarnation of this database, otherwise 'NO'. Reset SCN: SCN of the most recent resetlogs operation. Reset Time: Time of the most recent resetlogs operation.
Action: No action is required.

RMAN-06250


Report of files that need backup due to unrecoverable operations
Cause:An unlogged change (such as 'create table unrecoverable') has been made to this file, and the most recent backup of the file does not contain those changes.
Action: Take a backup of this file. If this file is lost before a backup is taken, then the unlogged modifications will be lost. The message indicates whether a full backup is required or whether a incremental backup will suffice.

RMAN-06263


%-4s string string
Cause:This message is issued in response to the REPORT NEED BACKUP INCREMENTAL command, for those files which would use more than the specified number of incrementals during recovery.
Action: To reduce the number of incremental backups which would be used during recovery of this datafile, take a new full backup of this file now.

RMAN-06270


Report of files whose recovery needs more than number days of archived logs
Cause:This message is issued in response to the REPORT NEED BACKUP DAYS command for those files which need more than the specified number of days' archived logs for recovery.
Action: To reduce the number of log files needed for recovery of this datafile, take a new full or incremental backup now.

RMAN-06274


Report of files that must be backed up to satisfy number days recovery window
Cause:This message is issued in response to the REPORT NEED RECOVERY WINDOW OF n DAYS command for those files that must be backed up to satisfy specified retention policy.
Action: To satisfy specified recovery window for this datafile, take a new full or incremental backup now.

RMAN-06275


invalid number of days specified for report : string days
Cause:This message is issued in response to the REPORT NEED RECOVERY WINDOW OF n DAYS or REPORT NEED BACKUP DAYS n command when an invalid number of days was specified in input command.
Action: The number of days specified in REPORT command must be greater than zero.

RMAN-06280


Report of obsolete backups and copies
Cause:This message is issued in response to the REPORT OBSOLETE command. Each of the files listed is obsolete because it is more redundant than the level of redundancy specified in the REPORT command.
Action: Depending on your needs, you might need to take new backups.

RMAN-06290


Report of database schema
Cause:This message is issued in response to the REPORT SCHEMA command. The report shows the physical schema of the database at the indicated time. The following fields are shown for each datafile and temporary file: File: The file number. Size(MB): The size of the file in mega bytes. Tablespace: The name of the tablespace which contains this file. RB segs: YES if this file is part of a tablespace containing rollback segments, otherwise NO. Datafile/Tempfile Name: The file name. Maxsize(MB): Maximum file size to which file can be extended
Action: No action is required.

RMAN-06300


Report of files with less than number redundant backups
Cause:This message is issued when the REPORT NEED BACKUP REDUNDANCY command is used for those files which have less than the specified number of backups which can be used for recovery.
Action: Take another backup of the datafiles listed.

RMAN-06306


====================
Cause:This message is issued in response to a LIST BACKUP DATABASE/TABLESPACE/DATAFILE command when some backups were taken with the PROXY option. If a recovery catalog is in use, then the information comes from the recovery catalog, otherwise it comes from the target database control file. The following fields are shown for each proxy datafile backup. Key: This is the unique key which identifies this proxy backup in the recovery catalog. This value can be used in a CHANGE command to change its status. If the target database control file is being used as the recovery catalog, then this field uniquely identifies this copy in the control file. File: The file number that this file was copied from. Status: This is the status of the file. Possible values are: A - Available U - Unavailable D - Deleted X - Expired Status 'U' will not be used if the target database control file is being used as the recovery catalog. Completion time: This is the date and time when the backup was created. This column will be printed in the default Oracle date format, unless overridden with a NLS_DATE_FORMAT environment variable. Ckp SCN: This is the checkpoint SCN of the backup. The file contains all changes made at or before this SCN. Ckp time: This is the time that the file was last checkpointed. Handle: This is the media manager handle of the proxy backup.
Action: No action is required.

RMAN-06378


List of Backup Sets
Cause:This message is issued in response to a LIST BACKUP command.
Action: No action is required.

RMAN-06400


database opened
Cause:This is an informational message only.
Action: No action is required.

RMAN-06401


database is already started
Cause:A STARTUP command without the FORCE option was issued, but the target database is already started.
Action: Use the FORCE option if you want to restart the database.

RMAN-06402


Oracle instance shut down
Cause:This is an informational message only.
Action: No action is required.

RMAN-06403


could not obtain a fully authorized session
Cause:The most likely cause of this error is that one of the databases to which RMAN had previously connected is not started or has has been shutdown. Other error messages should identify exactly which database is the problem.
Action: Startup the database causing the problem.

RMAN-06404


database dismounted
Cause:This is an informational message only.
Action: No action is required.

RMAN-06405


database closed
Cause:This is an informational message only.
Action: No action is required.

RMAN-06406


deleted archive log
Cause:This is an informational message only.
Action: No action is required.

RMAN-06407


auxiliary instance file string deleted
Cause:This is an informational message only.
Action: No action is required.

RMAN-06408


recovery catalog upgraded to version string
Cause:This is an informational message issued by the UPGRADE CATALOG command. It indicates the version of the recovery catalog schema to which the recovery catalog was just upgraded. Note that this version number may not reflect the version number of your rman executable or target database, because the recovery catalog schema is not changed with each Oracle release.
Action: No action is required.

RMAN-06409


LIKE clause in LIST BACKUP OF ARCHIVELOG is not supported
Cause:LIST BACKUP OF ARCHIVELOG LIKE was used, which is not supported.
Action: Remove LIKE clause from command.

RMAN-06410


cannot use command when channels are allocated
Cause:An attempt was made to issue a command that can be used only when there are no allocated channels.
Action: Do not use the command, or de-allocate channels and use the command when no channels are allocated.

RMAN-06411


backup copies setting out of range (1-4): number
Cause:An attempt was made to set backup copies to an invalid value.
Action: Use a value in the specified range.

RMAN-06412


no proxy copy channel found
Cause:A proxy copy was started, but no allocated channel supports proxy copy. This could be because the media management software used by the target database does not support proxy copy, or because all of the allocated channels are of type DISK, which never support proxy copy.
Action: If this is a backup, then either allocate a non-disk channel, or do not use the PROXY option. If this is a restore, then a channel of the same type which created the proxy backup was allocated, but now does not support proxy copy. If proxy copy is no longer supported by the media management software at the target database, the CROSSCHECK or CHANGE commands should be used so that those backups will not be considered for further restores.

RMAN-06413


channel string does not support proxy copy
Cause:The channel which was specified for this backup or restore does not support proxy copy. This could be because the media management software used by the target database does not support proxy copy, or because the channel is of type DISK, which never supports proxy copy.
Action: If this is a backup, then either allocate a non-disk channel, or do not use the PROXY option. If this is a restore, then a channel of the same type which created the proxy backup was allocated, but now does not support proxy copy. If proxy copy is no longer supported by the media management software at the target database, the CROSSCHECK command should be used so that those backups will not be considered for further restores.

RMAN-06414


target database COMPATIBLE option does not support proxy copy
Cause:PROXY was specified, and the target database uses a media manager that supports proxy copy, but the COMPATIBLE initialization parameter of the target database must be 8.1.0 or greater to create proxy backups. If the database is downgraded to the earlier release that is specified in the COMPATIBLE parameter, then it will no longer be able to restore proxy backups.
Action: Either take a non-proxy backup or change the target database COMPATIBLE parameter.

RMAN-06415


file string cannot be proxy backed up
Cause:The PROXY option was specified, but the media management software used by the target database cannot back up the specified file using proxy copy. If PROXY ONLY was specified, then the backup is terminated. If PROXY was specified, then this file will be placed into a non-proxy backup set.
Action: Remove the ONLY option to place the files into a regular backup set, or contact the media management vendor if you believe that the media management software should support proxy copy of this file.

RMAN-06416


PROXY ONLY was specified and some files could not be proxy copied
Cause:PROXY ONLY was specified, and some of the files to be backed up could not be backed up by the media management software used by the target database. Message 6415 is issued for each file that cannot be proxy copied.
Action: Remove the ONLY option to place the files into a regular backup set, or contact the media management vendor if you believe that the media management software should support proxy copy of these files.

RMAN-06418


proxy incremental backups with level > 0 not supported
Cause:PROXY was specified for a non-level-zero incremental backup. Proxy backups may only be full or level 0 backups.
Action: Remove one of the conflicting options.

RMAN-06419


file string cannot be proxy restored from handle string
Cause:The media management software used by the target database indicated that it cannot restore the specified file from the specified backup handle.
Action: Consult the media management software documentation to find out why this restriction exists or contact the media management vendor.

RMAN-06420


some files could not be proxy restored - aborting restore
Cause:Some of the files to be restored could not be restored by the media management software used by the target database. Message 6419 is issued for each file that cannot be restored.
Action: Contact the media management vendor if you believe that the media management software should support proxy copy of these files. The CROSSCHECK or CHANGE commands can be used to remove these proxy copies from the catalog to prevent the RESTORE command from trying to restore from these proxy backups.

RMAN-06421


sent command to channel: string
Cause:This is an informational message only.
Action: No action is required.

RMAN-06422


no channels found for SEND command
Cause:No channels with the specified names or device types were found. If no channel qualifiers were specified, then no channels were allocated.
Action: Specify a different channel type or allocate a channel of the desired type.

RMAN-06423


requested limit of number exceeds vendor limit of number
Cause:A SETLIMIT CHANNEL command was used to set the backup piece size limit, but the media management software used by the target database cannot create backup pieces that large.
Action: Specify a smaller backup piece limit.

RMAN-06424


error while looking up proxy copy
Cause:An error occurred while looking up the specified proxy copy in the recovery catalog or target database control file.
Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the name or key is entered correctly. If the proxy copy was created when the recovery catalog was not available, then a RESYNC CATALOG must be done to update the recovery catalog.

RMAN-06425



Cause:This is an informational message only.
Action: No action is required.

RMAN-06426


RECOVERY_CATALOG_OWNER role must be granted to user string
Cause:The CREATE CATALOG or UPGRADE CATALOG command was used, but the userid that was supplied in the CATALOG connect string does not have the RECOVERY_CATALOG_OWNER role granted as a DEFAULT role.
Action: Grant the RECOVERY_CATALOG_OWNER role to the recovery catalog owner.

RMAN-06427


recovery catalog already exists
Cause:The CREATE CATALOG command cannot be used when the recovery catalog already exists.
Action: Use the UPGRADE CATALOG command to upgrade your recovery catalog to the most current release without losing any existing backup data. Use the DROP CATALOG command to remove an existing recovery catalog.

RMAN-06428


recovery catalog is not installed
Cause:A recovery catalog database connection has been made, but the recovery catalog tables and views have not been installed.
Action: If you mis-typed the recovery catalog owner userid, then correct the userid and reconnect to the recovery catalog. If this is the first time that you have signed on to Recovery Manager with this recovery catalog owner userid, then use the CREATE CATALOG command to create the recovery catalog schema. Alternatively, exit RMAN and connect without specifying a recovery catalog connection.

RMAN-06429


%s database is not compatible with this version of RMAN
Cause:The indicated database is not compatible with this version of the Recovery Manager (RMAN). Other messages have also been issued which detail the cause of the error.
Action: See the other messages. If the database is CATALOG, then you may be able to use the CREATE CATALOG or UPGRADE CATALOG commands to correct the problem. If the database is TARGET or AUXILIARY, then you must either upgrade the target database or use a newer version of the RMAN executable.

RMAN-06430


recovery catalog userid cannot be SYS
Cause:A recovery catalog connection was made to userid SYS. The recovery catalog must be created in a userid other than SYS.
Action: Specify a different userid in the CATALOG connect string.

RMAN-06431


recovery catalog created
Cause:This is an informational message issued by the CREATE CATALOG command.
Action: No action is required.

RMAN-06432


recovery catalog dropped
Cause:This is an informational message issued by the DROP CATALOG command.
Action: No action is required.

RMAN-06433


error installing recovery catalog
Cause:An error was received from the recovery catalog database while it was being installed. Another error message shows the error message from the server.
Action:The most common reasons for failure to install the recovery catalog are:
- Lack of space in the recovery catalog database: allocate more space, use the DROP CATALOG command to remove any partially installed recovery catalog, and retry the command.
- Object already exists: This is caused by a partial recovery catalog installation. Use the DROP CATALOG command to remove the partially installed recovery catalog and retry the command.

RMAN-06434


some errors occurred while removing recovery catalog
Cause:Some errors were received from the recovery catalog database while removing the recovery catalog.
Action: Correct the error(s) and retry the command. Note that the Recovery Manager intercepts and ignores common errors, such as 'object not found', which can happen while removing a partially installed recovery catalog. Only serious errors will be displayed while removing the recovery catalog.

RMAN-06435


recovery catalog owner is string
Cause:This is an informational message issued by the UPGRADE CATALOG and DROP CATALOG commands.
Action: No action is required.

RMAN-06436


enter DROP CATALOG command again to confirm catalog removal
Cause:The DROP CATALOG command deletes the recovery catalog, rendering all database backups unusable, and should be used with care. The command must be entered twice to ensure that this is really what you want to do.
Action: If you really want to remove the recovery catalog, then enter the DROP CATALOG command again.

RMAN-06437


cannot drop catalog - catalog is newer than this RMAN
Cause:The DROP CATALOG command was entered, but the recovery catalog was created by a newer version of the Recovery Manager (RMAN). This version of RMAN may not be able to drop the entire recovery catalog.
Action: Use the version of RMAN which most recently created or upgraded the recovery catalog.

RMAN-06438


error executing package DBMS_RCVMAN in string database
Cause:Recovery Manager requires the DBMS_RCVMAN package in the SYS schema of the indicated database. Normally this package is installed during database creation. To re-create the package, run the files dbmsrman.sql and prvtrmns.plb.
Action: re-create the DBMS_RCVMAN package in the SYS schema.

RMAN-06439


RMAN must be upgraded to version string to work with this package
Cause:This message indicates the minimum version of recovery manager required to use the package which was specified in message 6191.
Action: A newer version of RMAN must be used with this package.

RMAN-06441


cannot upgrade catalog - catalog is already newer than this RMAN
Cause:The recovery catalog is already at a version level that is greater than this version of the Recovery Manager. The UPGRADE CATALOG command is not needed.
Action: Either upgrade to a more recent Recovery Manager, or continue to use the current version. Message 6191 will be issued if the recovery catalog is too new to work with this version of Recovery Manager.

RMAN-06442


enter UPGRADE CATALOG command again to confirm catalog upgrade
Cause:The UPGRADE CATALOG command alters the recovery catalog schema. Although the recovery catalog is designed to be compatible with older versions of the Recovery Manager (RMAN), it is possible that an upgrade will remove support for older versions of RMAN.
Action: If you really want to upgrade the recovery catalog, then enter the UPGRADE CATALOG command again. If you are not going to use an older version of RMAN with this recovery catalog, then compatibility is not an issue. If you plan to also continue using an older version of RMAN with this recovery catalog then, before upgrading, consult the Migration Guide for the current Oracle release to determine if upgrading to the current version of the recovery catalog will remove support for older versions of RMAN.

RMAN-06443


error upgrading recovery catalog
Cause:An error was received from the recovery catalog database while upgrading the recovery catalog.
Action: Correct the error and retry the command. Note that the Recovery Manager intercepts and ignores common errors, such as 'column already exists,' which can happen if the recovery catalog has already been partially upgraded. Only serious errors will be displayed while upgrading the recovery catalog.

RMAN-06444


%s created with compilation errors
Cause:During the CREATE CATALOG or UPGRADE CATALOG command, the indicated PL/SQL package specification or body could not be created because of PL/SQL compilation errors.
Action: The PL/SQL packages used by the recovery catalog are located in the RECOVER.BSQ library file, and should never be modified. Make sure that the RECOVER.BSQ file has not been modified or damaged, and then if this error persists, contact Oracle support. Connect to the recovery catalog owner and query the USER_ERRORS view to find out the details of the compilation errors.

RMAN-06445


cannot connect to recovery catalog after NOCATALOG has been used
Cause:The CONNECT CATALOG command was used after the user had already specified the NOCATALOG option.
Action: Re-start rman if you wish to use a recovery catalog.

RMAN-06446


changed proxy copy unavailable
Cause:This is an informational message only.
Action: No action is required.

RMAN-06447


changed proxy copy available
Cause:This is an informational message only.
Action: No action is required.

RMAN-06448


uncataloged proxy copy
Cause:This is an informational message only.
Action: No action is required.

RMAN-06449


deleted proxy copy
Cause:This is an informational message only.
Action: No action is required.

RMAN-06450


crosschecked proxy copy: found to be 'string'
Cause:This is an informational message only.
Action: No action is required.

RMAN-06451


proxy copy handle=string recid=string stamp=string
Cause:This is an informational message only.
Action: No action is required.

RMAN-06452


%s package upgraded to version string
Cause:This is an informational message issued by the UPGRADE CATALOG command. It indicates the version to which the indicated package was just upgraded. Note that this version number may not reflect the version number of your rman executable or target database, because the recovery catalog packages are not changed with each Oracle release.
Action: No action is required.

RMAN-06453


RECOVERABLE may only be used with datafile objects
Cause:An attempt was made to use LIST ... RECOVERABLE .. with OF CONTROLFILE or OF ARCHIVELOG.
Action: Remove the RECOVERABLE keyword and try again.

RMAN-06454


duplexed backups require Enterprise Edition
Cause:The SET COPIES or CONFIGURE BACKUP COPIES command was used to create more than one copy of each backup piece, but Enterprise Edition is not installed.
Action: Do not attempt to create more than one copy of each backup piece.

RMAN-06455


point-in-time tablespace recovery requires Enterprise Edition
Cause:A point-in-time tablespace recovery was attempted, but Enterprise Edition is not installed.
Action: Do not do point-in-time tablespace recovery.

RMAN-06456


command is obsolete
Cause:This is an informational message only.
Action: No action is required.

RMAN-06457


UNTIL scn (string) is ahead of last scn in archived logs (string)
Cause:UNTIL scn cannot be more than the last scn of the last archived log
Action: Check the UNTIL scn.

RMAN-06458


AS COPY option cannot be used with RECOVERY FILES, RECOVERY AREA or DB_RECOVERY_FILE_DEST
Cause:The RECOVERY FILES, RECOVERY AREA or DB_RECOVERY_FILE_DEST was specified with AS COPY.
Action: Remove the AS COPY option and resubmit the command.

RMAN-06459


BACKUP VALIDATE|DURATION is not supported with PROXY
Cause:BACKUP VALIDATE|DURATION and PROXY were specified in the same backup command.
Action: Remove the incompatible option.

RMAN-06460


control cile copy string cannot be backed up by proxy.
Cause:The PROXY option was specified, but proxy copy of control file is not supported. This file will be placed into a non-proxy backup set.
Action: No action required, this is an informational message.

RMAN-06461


current control file cannot be backed up by proxy.
Cause:The PROXY option was specified, but proxy copy of control file is not supported. This file will be placed into a non-proxy backup set.
Action: No action required, this is an informational message.

RMAN-06462


no backupsets found on device DISK that match specification
Cause:A backupset record specifier did not match an backupset on device DISK in the recovery catalog.
Action: Resubmit the command with a different backupset record specifier. The rman LIST command can be used to display all backupsets that Recovery Manager knows about.

RMAN-06463


Backup set key string cannot be backed up by proxy.
Cause:The PROXY option was specified, but proxy copy of backup set is not supported. This file will be placed into a non-proxy backup set.
Action: No action required, this is an informational message.

RMAN-06464


BACKUP BACKUPSET is not supported with VALIDATE option
Cause:BACKUP BACKUPSET and VALIDATE were specified in the same backup command.
Action: To VALIDATE BACKUPSET use 'validate' or 'restore validate' command.

RMAN-06465


configuration not implemented: string
Cause:The configuration is not implemented in the current release.
Action: Avoid using the command.

RMAN-06466


error parsing configuration string (string)
Cause:Unsupported configuration string is stored in recovery catalog or target database control file.
Action: Check compatibility matrix rman executable and target database and recover catalog. Use dbsm_backup_restore.deleteConfig to remove problematic configuration.

RMAN-06467


could not translate DBA: number
Cause:An error was received when calling dbms_rcvman
Action: This message should be accompanied by other error message(s) indicating the cause of the error.

RMAN-06468


Invalid Data Block Address: number
Cause:The DBA specified doesn't belong to the mentioned tablespace
Action: Check the DBA

RMAN-06469


could not translate corruption list
Cause:An error was received when calling dbms_rcvman
Action: This message should be accompanied by other error message(s) indicating the cause of the error.

RMAN-06470


DEVICE TYPE is supported only when automatic channels are used
Cause:The DEVICE TYPE option was specified with a BACKUP, RESTORE, RECOVER, DUPLICATE, CHANGE, VALIDATE, CROSSCHECK, or DELETE EXPIRED command. This option is allowed only when automatically allocated channels are used.
Action: Remove the DEVICE TYPE option and re-run the command. Or Remove all ALLOCATE commands and re-run the script so that channels are automatically allocated.

RMAN-06471


no configuration found to allocate channels for string
Cause:Device type configuration was not found in recovery catalog
Action: Setup device type configuration using configure command for required device type

RMAN-06472


channel id string is automatically allocated
Cause:Channel id was used on ALLOCATE/RELEASE command.
Action: Use other channel id that does not belong to reserved channel id's namespace

RMAN-06474


maintenance channels are not allocated
Cause:RELEASE CHANNEL was used without allocating any maintenance channels.
Action: Allocate maintenance channel before executing this command.

RMAN-06475


parallelism setting out of range (1-254): number
Cause:Parallelism for the device type in CONFIGURE PARALLELISM command is out of range
Action: Enter value of parallelism that are within the allowed range.

RMAN-06476


channel number out of range (1-254): number
Cause:Channel number entered in CONFIGURE CHANNEL command is out of range.
Action: Enter channel number within allowed range and retry the command. for this device and retry the command

RMAN-06477


configuration value length exceeds 1024
Cause:CONFIGURE CHANNEL command entered has configuration value greater than 1024 bytes.
Action: Reduce the length of CONFIGURE CHANNEL command options

RMAN-06478


WARNING: datafile copy 'string' cannot be found on disk
Cause:The CHANGE DATAFILECOPY AVAILABLE command was used, but the datafile copy cannot be found on disk.
Action: If the storage containing the datafile copy has been removed from the host, restore it and retry the command. If the datafile copy is permanently gone, then issue the CHANGE DATAFILECOPY DELETE command for this datafile.

RMAN-06479


WARNING: control file copy 'string' cannot be found on disk
Cause:The CHANGE CONTROLFILECOPY AVAILABLE command was used, but the control file copy cannot be found on disk.
Action: If the storage containing the control file copy has been removed from the host, restore it and retry the command. If the control file copy is permanently gone, then issue the CHANGE CONTROLFILECOPY DELETE command for this control file.

RMAN-06480


WARNING: archivelog 'string' cannot be found on disk
Cause:The CHANGE ARCHIVELOG AVAILABLE command was used, but the archivelog cannot be found on disk.
Action: If the storage containing the archivelog has been removed from the host, restore it and retry the command. If the archivelog is permanently gone, then issue the CHANGE ARCHIVELOG DELETE command for this archivelog.

RMAN-06481


WARNING: backup piece 'string' cannot be found on the storage medium
Cause:The CHANGE BACUKPPIECE AVAILABLE command was used, but the backup piece cannot be found on the storage medium.
Action: If the storage containing the backup piece has been removed from the host, restore it and retry the command. If the backup piece is permanently gone, then issue the CHANGE BACKUPPIECE DELETE command for this backup piece.

RMAN-06482


WARNING: proxy copy 'string' cannot be found on the storage medium
Cause:The CHANGE PROXY AVAILABLE command was used, but the proxy copy cannot be found on disk.
Action: If the storage containing the proxy copy has been removed from the host, restore it and retry the command. If the proxy copy is permanently gone, then issue the CHANGE PROXY DELETE command for this proxy copy.

RMAN-06483


changed datafile copy expired
Cause:This is an informational message only.
Action: No action is required.

RMAN-06484


changed control file copy expired
Cause:This is an informational message only.
Action: No action is required.

RMAN-06485


changed archivelog expired
Cause:This is an informational message only.
Action: No action is required.

RMAN-06486


changed backup piece expired
Cause:This is an informational message only.
Action: No action is required.

RMAN-06487


changed proxy copy expired
Cause:This is an informational message only.
Action: No action is required.

RMAN-06488


restore from autobackup does not allow any other modifiers
Cause:A control file or SPFILE restore from autobackup was attempted and other restore options were used.
Action: Do not specify any other options for the control file autobackup restore.

RMAN-06489


no configuration found to allocate clone channel number for device type string
Cause:Target channel configuration could not be used for clone channel as it contains CONNECT option.
Action: Setup clone channel configuration using CONFIGURE CLONE command for required channel number and device type

RMAN-06490


WARNING: limit of autobackups for the day has been reached
Cause:No more control file autobackups are possible in this day.
Action: This is a warning message, no action is required.

RMAN-06491


controlfile autobackup format "string" contains more than one "string" format specifier
Cause:A CONTROLFILE AUTOBACKUP FORMAT cannot have more than one reserved format specifier.
Action: Specify only one reserved format specifier or use an alternative format.

RMAN-06492


controlfile autobackup format "string" must specify a "string" format specifier
Cause:A reserved format specifier was not specified for the CONTROLFILE AUTOBACKUP FORMAT
Action: Add a specifier to the CONTROLFILE AUTOBACKUP FORMAT

RMAN-06493


only UNTIL TIME clause is allowed when performing a restore from autobackup, found: string
Cause:For restoring a control file autobackup only SET UNTIL TIME can be used. It is not possible to translate the others to a precise day.
Action: Specify SET UNTIL TIME to indicate the day to start the restore of a control file autobackup.

RMAN-06494


%s = string is out of range (string-string)
Cause:The specified parameter for restoring a control file autobackup is out of the valid range.
Action: Change the parameter value to a valid number or do not specify it.

RMAN-06495


must explicitly specify DBID with SET DBID command
Cause:Restore of a control file autobackup was attempted when the database is not mounted.
Action: Specify the DBID of the database using SET DBID or mount the database.

RMAN-06496


must use the TO clause when the database is mounted or open
Cause:A control file restore was attempted when the database is mounted or open and no alternate destination was specified.
Action: Specify an alternate destination with the TO clause or dismount the database.

RMAN-06497


WARNING: control file is not current, control file autobackup skipped
Cause:Control file autobackup is not possible without a current control file.
Action: This is a warning message, no action is required.

RMAN-06498


skipping datafile string; already backed up string time(s)
Cause:The indicated datafile will not be included in the backup set. It is already backed up on the device requested and file is offline/read-only datafile. Use the FORCE option to override backup optimization.
Action: No action is required.

RMAN-06499


skipping archive log file string; already backed up string time(s)
Cause:The indicated log file will not be included in the backup set because it is already backed up on the device requested. Use FORCE option to override backup optimization.
Action: No action is required.

RMAN-06500


skipping backupset key string; already backed up string time(s)
Cause:The indicated backupset will not be copied because it is already backed up on the device requested. Use FORCE option to override backup optimization.
Action: No action is required.

RMAN-06501


skipping datafile string; already backed up on string
Cause:The indicated datafile will not be included in the backup set. It is already been backed up once, or before the since time specified.
Action: No action is required.

RMAN-06502


skipping archive log file string; already backed on string
Cause:The indicated log file will not be included in the backup set. It is already been backed up once, or before the since time specified.
Action: No action is required.

RMAN-06503


skipping backupset key string; already backed up on string
Cause:The indicated backupset will not be backed up. It has already been backed up on the device once, or before the since time specified.
Action: No action is required.

RMAN-06504


PROXY option with multiple backup copies is not supported
Cause:Multiple backup copies and PROXY option were specified in BACKUP command.
Action: Resolve the conflict.

RMAN-06506


the MAXSETSIZE option cannot be used with a backup backupset
Cause:The MAXSETSIZE option was specified for a backup backupset command.
Action: Remove the option and resubmit the command.

RMAN-06507


trying alternate file for archivelog thread number, sequence number
Cause:This is an informational message, appearing when an archivelog was found out of sync with catalog database.
Action: No action is required.

RMAN-06508


MAXSETSIZE string kbytes should be greater than blocksize string bytes
Cause:MAXSETSIZE configured or specified in backup command should be greater than database blocksize.
Action: Specify a larger MAXSETSIZE limit.

RMAN-06509


only SPFILE or control file can be restored from autobackup
Cause:A datafile or archived log restore from autobackup was attempted.
Action: Do not specify DATAFILE or ARCHIVELOG for restore from autobackup.

RMAN-06510


RMAN retention policy is set to recovery window of number days
Cause:This is an informational message only.
Action: No action is required.

RMAN-06511


RMAN retention policy is set to redundancy number
Cause:This is an informational message only.
Action: No action is required.

RMAN-06512


copy will be obsolete on date string
Cause:This is an informational message only.
Action: No action is required.

RMAN-06513


copy will never be obsolete
Cause:This is an informational message only.
Action: No action is required.

RMAN-06514


archived logs required to recover from this copy will not be kept
Cause:This is an informational message only.
Action: No action is required.

RMAN-06515


archived logs required to recover from this copy will expire when this copy expires
Cause:This is an informational message only.
Action: No action is required.

RMAN-06516


time specified in KEEP UNTIL clause must be be after today
Cause:KEEP UNTIL support only a future time.
Action: Correct the time and retry the command.

RMAN-06517


KEEP option is not supported for archive log backups
Cause:The KEEP option is not supported for archive logs.
Action: Either remove KEEP option and retry the command or don't specify archive logs for this backup.

RMAN-06518


backup will be obsolete on date string
Cause:This is an informational message only.
Action: No action is required.

RMAN-06519


backup will never be obsolete
Cause:This is an informational message only.
Action: No action is required.

RMAN-06520


archived logs required to recover from this backup will not be kept
Cause:This is an informational message only.
Action: No action is required.

RMAN-06521


archived logs required to recover from this backup will expire when this backup expires
Cause:This is an informational message only.
Action: No action is required.

RMAN-06522


KEEP FOREVER option is not supported without the recovery catalog
Cause:The KEEP FOREVER option was used, but it requires a connection to a recovery catalog database. The KEEP FOREVER option cannot be used when the backup repository is the target database control file. This is because information about this backup cannot be permanently stored. (If information is stored just in the control file it will be aged out depending on CONTROL_FILE_RECORD_KEEP_TIME initialization parameter.)
Action: If a recovery catalog database is available, then connect to the recovery catalog and retry the command, otherwise use a different KEEP option. 6523, 1, "unused"

RMAN-06524


RMAN retention policy will be applied to the command
Cause:This is an informational message only.
Action: No action is required.

RMAN-06525


RMAN retention policy is set to none
Cause:Command DELETE OBSOLETE and REPORT OBSOLETE requires that either:
* RMAN retention policy is not NONE or,
* RMAN retention policy is specified with REPORT/DELETE command.
Action: Either configure RMAN retention policy with CONFIGURE command or specify it at the end of DELETE/REPORT command.

RMAN-06526


KEEP option cannot be used with incremental backup
Cause:The KEEP option was specified for a incremental backup.
Action: Remove the option and resubmit the command.

RMAN-06527


KEEP option is not supported for backup of backup sets
Cause:The KEEP option is not supported for backup of backup sets.
Action: Either remove KEEP option and retry the command or don't specify backup sets for this backup.

RMAN-06528


CHANGE ... KEEP not supported for BACKUPPIECE
Cause:The CHANGE BACKUPPIECE ... KEEP command was entered. KEEP attributes cannot be specified for backup pieces.
Action: Use CHANGE BACKUPSET ... KEEP instead.

RMAN-06529


CHANGE ... KEEP not supported for ARCHIVELOG
Cause:The CHANGE ARCHIVELOG ... KEEP command was entered. KEEP attributes cannot be specified for archive logs.
Action: Use CHANGE BACKUPSET ... KEEP instead.

RMAN-06530


CHANGE ... KEEP not supported for backup set which contains archive logs
Cause:The CHANGE BACKUPSET ... KEEP command was entered, but the BACKUPSET contains archive logs. Backup sets with archive logs cannot have KEEP attributes.
Action: Do not specify backup set with archive logs for the CHANGE BACKUPSET ... KEEP command.

RMAN-06531


CHANGE ... KEEP not supported for incremental BACKUPSET
Cause:The CHANGE BACKUPSET ... KEEP command was entered, but the BACKUPSET is an incremental backup set. Incremental backup sets cannot have KEEP attributes.
Action: Do not specificy backup set with archive logs for the CHANGE BACKUPSET ... KEEP command.

RMAN-06532


redundancy count must be greater than zero
Cause:The REDUNDANCY operand specified for the retention policy was zero.
Action: Specify a REDUNDANCY operand of 1 or greater.

RMAN-06533


KEEP ... NOLOGS option cannot be used when datafiles are fuzzy
Cause:The KEEP ... NOLOGS option was specified for a backup or copy of files in a fuzzy state. This kind of backup requires archive logs for recovery, so archive logs must be kept.
Action: Remove the KEEP ... NOLOGS option or make sure the files are not in in a fuzzy state and resubmit the command.

RMAN-06534


KEEP ... CONSISTENT option is not supported
Cause:The KEEP ... CONSISTENT option was specified but the option is not supported.
Action: Remove the option and resubmit the command.

RMAN-06535


LIST COPY OF SPFILE is not supported
Cause:LIST COPY OF SPFILE was used, which is not supported because SPFILE cannot have a copy.
Action: Remove SPFILE from the command.

RMAN-06536


BACKED UP ... TIMES option is supported only for archived logs
Cause:The BACKUP UP ... TIMES option was used as a qualifier. This option is supported only for archived logs.
Action: Remove the option and resubmit the command.

RMAN-06537


CHANGE ... KEEP not supported for BACKUP
Cause:The CHANGE BACKUP... KEEP command was entered. KEEP attributes cannot be specified for copies and backup pieces in a single command.
Action: Use CHANGE BACKUPSET ... KEEP instead.

RMAN-06540


tablespace string will be excluded from future whole database backups
Cause:This is an informational message only.
Action: No action is required.

RMAN-06541


tablespace string will be included in future whole database backups
Cause:This is an informational message only.
Action: No action is required.

RMAN-06542


file string is excluded from whole database backup
Cause:The indicated file will not be included in the backup set because it's tablesapce is configured as excluded from backup.
Action: No action is required.

RMAN-06543


duplicate or conflicting LIST options: string and string
Cause:The indicated options conflict with each other or appear more than once in a LIST command.
Action: remove the duplicate/conflicting option from the command.

RMAN-06544


Do you really want to delete the above objects (enter YES or NO)?
Cause:This is a user prompt.
Action: Answer the question to proceed.

RMAN-06545


"string" is an invalid response - please re-enter.
Cause:An incorrect response was entered.
Action: Enter a correct response.

RMAN-06546


Error occurred getting response - assuming NO response
Cause:An error occurred reading user response.
Action: No action is required, this is an informational message only.

RMAN-06547


tablespace SYSTEM cannot be excluded from whole database backup
Cause:The SYSTEM tablespace must be included in whole database backup.
Action: Remove the SYSTEM tablespace from the CONFIGURE ... EXCLUDE and retry the operation.

RMAN-06548


connected to auxiliary database: string (DBID=string)
Cause:This is an informational message only.
Action: No action is required.

RMAN-06549


connected to auxiliary database: string (not mounted)
Cause:This is an informational message only.
Action: No action is required.

RMAN-06550


clone database not mounted and db_name not set in init.ora
Cause:The clone database "init.ora" file does not specify the DB_NAME parameter.
Action: Add the DB_NAME parameter to the clone database "init.ora" and restart the instance.

RMAN-06551


error while looking up datafile copy for file number: string
Cause:An error occurred while looking up the specified datafile copy in the recovery catalog or target database control file.
Action: This error is accompanied by other errors describing the reason for the failure. If the datafile copy was created during a RESTORE with a new name, ensure that the RESTORE completed successfully.

RMAN-06552


newname for datafile number was set to NEW, but file was not restored
Cause:A SWITCH command was specified for a datafile, but the newname was set to NEW and the file was not restored. If newname is set to NEW, the file must be restored before issuing a SWITCH command.
Action: Correct and resubmit the SWITCH command.

RMAN-06553


DB_CREATE_FILE_DEST must be set for SET NEWNAME ... TO NEW
Cause:The SET NEWNAME ... TO NEW option was specified but the OMF destinatation init parameter DB_CREATE_FILE_DEST is not set.
Action: Supply a full name to the SET NEWNAME command or set DB_CREATE_FILE_DEST at the target database.

RMAN-06554


WARNING: file string is in backup mode
Cause:A file which is being backed up or copied is in backup mode. RMAN will back up the file anyway, but files do not need to be put into backup mode before backing them up with RMAN.
Action: Use the ALTER TABLESPACE ... END BACKUP statement, at the target database server, to take the files out of backup mode.

RMAN-06555


datafile string must be restored from backup created before string
Cause:An incomplete recovery session was started, but the file is in newer than the UNTIL TIME clause.
Action: Check the UNTIL TIME clause or restore the file from a sufficient old backup.

RMAN-06556


datafile string must be restored from backup older than scn string
Cause:An incomplete recovery session was started, but the file is newer than the UNTIL clause.
Action: Check the UNTIL clause or restore the file from a sufficient old backup.

RMAN-06557


unable to restore archived log thread number, sequence number
Cause:Restore of the specified archived log failed because the size of the archived log is larger than available disk space.
Action: One of the following: 1) Increase the MAXSIZE parameter and retry the command. 2) Free up disk space in the recovery area.

RMAN-06558


archived log size of number kb is bigger than available space of number kb
Cause:This message should be followed by one or more 6557 messages.
Action: Check the accompanying errors.

RMAN-06559


MAXSIZE must be larger than 1 kb
Cause:The MAXSIZE parameter is out of range.
Action: Specify a valid size and retry the command.

RMAN-06560


WARNING: backup set with key number will be read number times
Cause:This message should be followed by one or more 6562 messages.
Action: Check the accompanying messages.

RMAN-06561


available space must be larger than number kb
Cause:The recovery failed because it requires more disk space. One of the following could have caused this error: 1) The MAXSIZE option is used but is not large enough to restore files. 2) Files should be restored to recovery area, but available disk space is not large enough to restore files.
Action: One of the following: 1) Increase the MAXSIZE parameter and retry the command. 2) Free up disk space in the recovery area.

RMAN-06562


available space of number kb needed to avoid reading the backup set multiple times
Cause:A backup set is read more than once. Multiple reads of a backup set can slow restore performance. One of the following could have caused this: 1) The MAXSIZE option is used but is not large enough to restore files. 2) Files should be restored to a recovery area, but the available disk space is not large enough to restore files.
Action: One of the following: 1) Increase the MAXSIZE parameter and retry the command. 2) Free up disk space in the recovery area.

RMAN-06563


control file or SPFILE must be restored using FROM AUTOBACKUP
Cause:RESTORE CONTROLFILE or RESTORE SPFILE was specified without the FROM AUTOBACKUP option when RMAN is not connected to the recovery catalog.
Action: If the recovery catalog is available, connect to the recovery catalog and retry the restore. If the recovery catalog in not available, following is the procedure to restore control file or SPFILE:
1. Specify the DBID of the database with the SET DBID command.
2. If the autobackup was created with non-default autobackup format, then specify the autobackup format using the SET CONTROLFILE AUTOBACKUP FORMAT command.
3. If the backup was created with SBT device, then allocate an SBT channel using the ALLOCATE CHANNEL command.
4. Restore control file or SPFILE by starting the RESTORE ... FROM AUTOBACKUP command.

RMAN-06564


must use the TO clause when the instance is started with SPFILE
Cause:A restore of the SPFILE from autobackup was attempted when the instance is started with SPFILE and no alternate destination was specified.
Action: Specify an alternate destination with the TO clause.

RMAN-06565


WARNING: string: sqlcode number was caught, automatic retry #number
Cause:The RMAN client caught a transient error and will automatically retry several times.
Action: No action required, this is an informational message.

RMAN-06566


target database incarnation not found in control file
Cause:resetlogs change# and/or time of the target database doesn't match any database incarnation in the control file.
Action: One of the following actions can be taken to resolve this error 1) Restore the control file from the incarnation. 2) To populate the new incarnation, inspect or restore an archived log/datafile/datafile copy/backup set from the target incarnation

RMAN-06567


connected to auxiliary database: string (DBID=string, not open)
Cause:This is an informational message only.
Action: No action is required.

RMAN-06568


connected to target database: string (DBID=string, not open)
Cause:This is an informational message only.
Action: No action is required.

RMAN-06570


datafile number switched to datafile copy "string"
Cause:This message was issued in response to a SWITCH command.
Action: No action is required, this is an informational message.

RMAN-06571


datafile number does not have recoverable copy
Cause:The SWITCH command with the option TO COPY was specified but the datafile has no valid copy to switch to.
Action: Verify whether the datafile has a valid datafile copy.

RMAN-06572


database is open and datafile number is not offline
Cause:The SWITCH command with the option TO COPY was specified, but datafile is not offline and database is open.
Action: Either make sure the datafile is offline or the database must be mounted but not opened.

RMAN-06575


platform id number found in datafile string header is not a valid platform id
Cause:The platform id found in the datafile header was not recognized.
Action: Verify that this is a valid datafile.

RMAN-06576


platform 'string' (number) found in header of datafile string does not match specified platform name 'string' (number)
Cause:The platform specified in the command did not match the platform found in the datafile header.
Action: Specify the correct platform name and retry the command.

RMAN-06577


FROM TAG option may only be used with datafilecopies
Cause:The FROM TAG option was specified for datafiles.
Action: Remove the option and resubmit the command.

RMAN-06578


INCREMENTAL LEVEL > 0 must be specified with FOR RECOVER OF
Cause:The FOR RECOVER OF option was specified without specifying INCREMENTAL LEVEL > 0.
Action: Specify INCREMENTAL LEVEL > 0 and resubmit the command.

RMAN-06580


the string option cannot be used with AS COPY
Cause:The specified option was specified for a backup as copy command.
Action: Remove the option and resubmit the command.

RMAN-06581


option string not supported
Cause:This option was specified and it is not supported.
Action: Remove the specified option.

RMAN-06582


AS COPY option cannot be used when backing up backupsets
Cause:The backupset was specified with AS COPY.
Action: Remove the AS COPY option or remove the backupsets.

RMAN-06583


at least 1 channel of TYPE DISK must be allocated to use AS COPY option
Cause:No channel of TYPE DISK was allocated.
Action: Allocate a channel of TYPE DISK and re-issue the command or remove AS COPY.

RMAN-06584


WARNING: AS BACKUPSET option added due to allocation of multiple channel types
Cause:DISK and non DISK channels were allocated for a backup command. Configuration indicates to produce image copies to DISK, however due to the mixed channel types BACKUPSETs will be created on DISK.
Action: Do not allocate non DISK channels to produce image copies to DISK or allocate only non DISK channels to produce BACKUPSETs only.

RMAN-06585


no copy of datafile number found
Cause:An available datafile copy for the specified datafile could not be found.
Action: make sure that all specified datafiles have a copy available.

RMAN-06586


no copy of datafile number with tag string found
Cause:An available datafile copy for the specified datafile could not be found.
Action: make sure that all specified datafiles have a copy available.

RMAN-06587


one or more datafilecopies were not found
Cause:This error message was accompanied by an additional error message or messages indicating the cause of the error.
Action: Follow the recommended actions of the additional error message or messages.

RMAN-06588


number of patterns (number) to DB_FILE_NAME_CONVERT should be even
Cause:An uneven number of patterns was specified.
Action: Specify one more or one less pattern.

RMAN-06589


cannot specify DB_FILE_NAME_CONVERT option without AS COPY
Cause:The DB_FILE_NAME_CONVERT option was specified without AS COPY. This is not permitted for backupset backups where multiple files are combined into a set.
Action: Remove the DB_FILE_NAME_CONVERT option and re-run the BACKUP command.

RMAN-06590


tablespace string cannot be converted
Cause:The system tablespaces could not be transported to other platforms.
Action: Remove the specified tablespace from the CONVERT command and retry the operation.

RMAN-06591


must specify TO PLATFORM
Cause:There was a missing parameter to the command.
Action: Specify the TO PLATFORM parameter with the command.

RMAN-06592


must specify FROM PLATFORM
Cause:There was a missing parameter to the command.
Action: Specify the FROM PLATFORM parameter with the command.

RMAN-06593


platform name 'string' specified in FROM PLATFORM is not valid
Cause:The platform name was not recognized.
Action: Specify a valid platform name.

RMAN-06594


platform name 'string' specified in TO PLATFORM is not valid
Cause:The platform name was not recognized.
Action: Specify a valid platform name.

RMAN-06595


platform name 'string' does not match database platform name 'string'
Cause:The platform name specified did not match the name of the database performing the conversion.
Action: Specify the correct platform name.

RMAN-06596


to use CONVERT compatibility must be set to 10.0.0 or greater, currently set to string
Cause:A command was attempted that requires a higher database compatibility.
Action: Raise the compatibility of the database before attempting the command again.

RMAN-06597


conversion between platforms 'string' and 'string' is not implemented
Cause:Conversion of Oracle data files between the specified platforms was not supported.
Action: Do not do the conversion.

RMAN-06598


conversion between platforms 'string' and 'string' is not needed
Cause:Conversion of Oracle data files between the specified platforms was not necessary because the Oracle data file format is already the same on both platforms.
Action: Do not do the conversion.

RMAN-06599


tablespace string is not read-only
Cause:A conversion was attempted on a tablespace which is not read-only.
Action: Change the tablespace to read-only and retry the operation.

RMAN-06600


old RMAN configuration parameters:
Cause:This message is issued in response to a CONFIGURE command.
Action: No action is required, this is an informational message only.

RMAN-06601


new RMAN configuration parameters:
Cause:This message is issued in response to a CONFIGURE command.
Action: No action is required, this is an informational message only.

RMAN-06604


new RMAN configuration parameters are successfully stored
Cause:This message is issued in response to a CONFIGURE command.
Action: No action is required, this is an informational message only.

RMAN-06605


old RMAN configuration parameters are successfully deleted
Cause:This message is issued in response to a CONFIGURE command.
Action: No action is required, this is an informational message only.

RMAN-06606


RMAN configuration parameters are successfully reset to default value
Cause:This message is issued in response to a CONFIGURE command.
Action: No action is required, this is an informational message only.

RMAN-06607


RMAN configuration parameters are:
Cause:This message is issued in response to a SHOW command.
Action: No action is required, this is an informational message only.

RMAN-06608


RMAN configuration has no stored or default parameters
Cause:This message is issued in response to a SHOW command.
Action: No action is required, this is an informational message only.

RMAN-06609


AS COPY can be configured only for disk device
Cause:The AS COPY option was specified for non disk device.
Action: Remove the AS COPY option and resubmit the command.

RMAN-06610


For record type string recids from number to number are re-used before resync
Cause:This messages is issued when the control file records were re-used before resyncing to catalog database.
Action: Increase control_file_keep_record_time setting or issue BACKUP command that it will generate fewer control file records, e.g., backup few tablespaces instead of the complete database in one BACKUP command.

RMAN-06700


error parsing text script in file string
Cause:Incorrect syntax or invalid commands were found.
Action: Fix text script and retry the command.

RMAN-06701


could not construct path for file: "string"
Cause:An error was encountered when trying to construct the full pathname for the specified file.
Action: Ensure that the path is correct.

RMAN-06702


could not initialize for input file: "string"
Cause:An error was encountered when trying to initialize the specified file for input.
Action: Ensure that the file exists.

RMAN-06703


could not open file: "string" (reason=string)
Cause:An error was encountered when trying to open the specified file.
Action: Ensure that the file has correct permissions.

RMAN-06705


text script line is too long (>1024)
Cause:A text script contained a line longer than the permitted maximum length.
Action: Split the line in smaller lines an retry the operation.

RMAN-06706


could not close file: "string" (reason=string)
Cause:An error was encountered when trying to close the specified file.
Action: Ensure that the file has correct permissions and still exists.

RMAN-06707


could not initialize for output file: "string"
Cause:An error was encountered when trying to initialize the specified file for output.
Action: Ensure that the file exists.

RMAN-06708


short write while writing file "string". Wrote string bytes instead of string bytes
Cause:An attempt was made to write to a file system that was full.
Action: Ensure that the file system has room for the file. Check system logs.

RMAN-06709


No scripts in recovery catalog
Cause:An attempt was made to list the scripts in the catalog, but no scripts could be found in the specified recovery catalog.
Action: No action required, this is an informational message only.

RMAN-06710


script string not found in catalog
Cause:An attempt was made to call a script that could not be found in the target database or as a global script in the specified catalog.
Action: Verify the script name and retry the command.

RMAN-06711


global scripts require a target connection
Cause:Connection to a target database was not specified.
Action: Provide a target connection and retry the command.

RMAN-06716


skipping datafile number; already restored to file string
Cause:Recovery Manager determined that this file is already restored. Use FORCE option to override this optimization.
Action: No action required, this is an informational message only.

RMAN-06717


number of source files (string) and destination files (string) does not match
Cause:The number of files to retrieve from the catalog does not match the number of destinations specified.
Action: Ensure that the number of files to be retrieved matches the number of destinations specified.

RMAN-06718


could not find file "string" in catalog
Cause:The filename provided was not found in the catalog.
Action: The specified file is not stored in the catalog, or it is stored with a different path than the one provided. Specify the filename as stored in the catalog.

RMAN-06719


file "string" (string bytes) restrieved from catalog
Cause:This is an informational message only.
Action: No action is required.

RMAN-06720


file "string" removed from catalog
Cause:This is an informational message only.
Action: No action is required.

RMAN-06721


could not normalize path for file: "string"
Cause:An error was encountered when trying to normalize the pathname for the specified file.
Action: Ensure that the path is correct.

RMAN-06722


unable to remove file "string" from catalog
Cause:This message should be accompanied by other error message(s) indicating the cause of the error.
Action: Follow actions for other messages.

RMAN-06723


file "string" (string bytes) updated in catalog
Cause:This is an informational message only.
Action: No action is required.

RMAN-06724


backup not done; all files already backed up
Cause:A BACKUP command does not need to backup any files, because all of the files to backup are already backed up.
Action: No action required, this is an informational message only.

RMAN-06725


database not open: sort area size too small
Cause:sort area size too small to execute RMAN commands.
Action: open the database or increase sort_area_size.

RMAN-06726


could not locate archivelog string
Cause:The specified archivelog could not be found on any allocated channel.
Action: Allocate additional channels on other nodes of the cluster, or, if the archived logs have been deleted, use the CROSSCHECK ARCHIVELOG command to correct the recovery catalog entries.

RMAN-06727


could not locate datafile copy string
Cause:The specified datafile copy could not be found on any allocated channel.
Action: Allocate additional channels on other nodes of the cluster, or if the datafile copy have been deleted, use the CROSSCHECK DATAFILECOPY command to correct the recovery catalog entries.

RMAN-06728


could not locate control file copy string
Cause:The specified control file copy could not be found on any allocated channel.
Action: Allocate additional channels on other nodes of the cluster, or if the control file copy have been deleted, use the CROSSCHECK CONTROLFILECOPY command to correct the recovery catalog entries.

RMAN-06729


no backup of the SPFILE found to restore
Cause:A SPFILE restore could not proceed because no backup of the SPFILE was found. It may be the case that a backup of this file exists but does not satisfy the criteria specified in the user's restore operands.
Action: Modify options for the SPFILE restore.

RMAN-06730


no channel to restore a backup of the SPFILE
Cause:A SPFILE restore could not proceed because the backup on a device type that was not allocated for restore.
Action: No action required, this is an informational message only. See message 6026 for further details.

RMAN-06731


command string:string%% complete, time left number:number:number
Cause:This is an informational message only.
Action: No action is required.

RMAN-06732


database dropped
Cause:This is an informational message only.
Action: No action is required.

RMAN-06733


database unregistered from the recovery catalog
Cause:This is an informational message only.
Action: No action is required.

RMAN-06734


Do you really want to drop all backups and the database (enter YES or NO)?
Cause:This is a user prompt.
Action: Answer the question to proceed.

RMAN-06735


Do you really want to drop the database (enter YES or NO)?
Cause:This is a user prompt.
Action: Answer the question to proceed.

RMAN-06736


Do you really want to unregister the database (enter YES or NO)?
Cause:This is a user prompt.
Action: Answer the question to proceed.

RMAN-06737


database name "string" does not match target database name "string"
Cause:The UNREGISTER DATABASE command was used with a database name that does not match the name of the database to which RMAN is connected.
Action: Specify the correct database name or avoid specifying the database name when connected to the target database.

RMAN-06738


database name "string" is not unique in the recovery catalog
Cause:The UNREGISTER DATABASE command was used with a database name that is ambiguous.
Action: Use the SET DBID command to specify the database id and resolve the ambiguity.

RMAN-06739


database "string" is not found in the recovery catalog
Cause:The UNREGISTER DATABASE command was used with a database name that was not found in the recovery catalog.
Action: Make sure the database name specified in the DROP DATABASE command syntax is correct.

RMAN-06740


database name is not specified
Cause:The UNREGISTER DATABASE command failed because of the following:
o RMAN is not connected to the target database
o The database name is not specified in the command
o DBID is not set with the SET DBID command
Action: Any one of the following actions will fix the problem: o Connect to the target database o Specify database name o Set DBID with SET DBID command

RMAN-06741


database name is "string" and DBID is string
Cause:This is an informational message only.
Action: No action is required.

RMAN-06742


platform name 'string' longer than number
Cause:The specified platform name exceeds the maximum allowable platform name.
Action: Correct the platform name.

RMAN-06743


specification does not match any backupset in the repository
Cause:The specified backupsets are not found in the repository.
Action: Verify backupset existence and retry the command.

RMAN-06744


specification does not match any datafile copy in the repository
Cause:The specified datafilecopies are not found in the repository.
Action: Verify datafile copy existence and retry the command.

RMAN-06745


skipping datafile copy string; already backed up string time(s)
Cause:The indicated datafile copy was not included in the backup set because it was already backed up on the device requested.
Action: Use FORCE option to override backup optimization.

RMAN-06746


backup cancelled because all files were skipped
Cause:All files for this backup set were skipped, therefore no backup no backup set was created.
Action: This message is informational only.

RMAN-06747


at least 1 channel of tertiary storage must be allocated to execute this command
Cause:The executed command requires a SBT channel, but no channels of type SBT were configured or allocated.
Action: ALLOCATE or CONFIGURE a SBT channel.

RMAN-06748


no or more than one tertiary storage channel found
Cause:RECOVERY FILES, RECOVERY AREA or DB_RECOVERY_FILE_DEST option was specified in BACKUP command, but no or more than one tertiary channel was found. One of the following could have caused this error: 1) All of the allocated channels are of type DISK. 2) No tertiary storage (SBT) channel configured. 3) CHANNEL or DEVICE TYPE option specified is of DISK type. 4) More than one tertiary storage channel allocated or configured and no DEVICE TYPE or CHANNEL option specified.
Action: One of the following: 1) Allocate a channel of TYPE SBT. 2) Configure a SBT channel. 3) Specify CHANNEL, DEVICE TYPE option of TYPE SBT.

RMAN-06749


restore point string does not exist.
Cause:The specified restore point does not exists in v$restore_point table of the target database.
Action: Check the name of restore point and retry the command.

RMAN-06750


SPFILE cannot be backed up by proxy.
Cause:The PROXY option was specified, but proxy copy of SPFILE is not supported. This file will be placed into a non-proxy backup set.
Action: No action required, this is an informational message only.

RMAN-06751


ASM file string cannot be proxy backed up.
Cause:The PROXY option was specified, but proxy copy of ASM file is not supported. This file will be placed into a non-proxy backup set.
Action: No action required, this is an informational message only.

RMAN-06752


error while looking up temporary file: string
Cause:An error occurred while looking up the specified temporary file in the recovery catalog or target database control file.
Action: This error is accompanied by other errors describing the reason for the failure; see those error messages for further information. One possible problem is that the temporary file name was not entered correctly.

RMAN-06753


temporary file not found in the repository
Cause:The specified temporary file is not found in the control file or recovery catalog.
Action: Make sure that the temporary file name is correct and retry

RMAN-06754


INCREMENTAL FROM SCN option is not supported with [string]
Cause:The INCREMENTAL FROM SCN option was supplied but does not apply to this type of backup.
Action: Remove the INCREMENTAL FROM SCN operand and re-enter the command.

RMAN-06755


WARNING: datafile string: incremental-start SCN is too recent; using checkpoint SCN string instead
Cause:The incremental-start SCN which was specified when starting an incremental datafile backup is greater than the datafile checkpoint SCN, which could cause some blocks to be missed.
Action: Specify a smaller incremental-start SCN.

RMAN-06756


cannot flashback database to non-guaranteed restore point string when flashback is off
Cause:The indicated restore point was not guranteed and flashback was disabled. When flashback is disabled, Oracle can flashback only to guranteed restore point.
Action: Specify a guranteed restore point or turn on flashback and retry the command. the command.

RMAN-06757


DB_UNIQUE_NAME "string" does not match target database ("string")
Cause:The value specified in the FOR DB_UNIQUE_NAME option did not match the DB_UNIQUE_NAME parameter setting of the target database.
Action: Use the RMAN STARTUP command, with no parameter file option, to start the target database without a parameter file, then run the RESTORE SPFILE command again.

RMAN-06758


DB_UNIQUE_NAME is not unique in the recovery catalog
Cause:RMAN could not identify which SPFILE to restore for this target database, because the recovery catalog contained two or more different instances of this database, each with different DB_UNIQUE_NAME values.
Action: Use the FOR DB_UNIQUE_NAME option to specify the name of the instance whose parameter file you want to restore.

RMAN-06759


skipping datafile copies that are already backed up
Cause:Some datafile copies were not be backed up because they were already backed up on the device requested.
Action: No action is required. You can use the FORCE option to override backup optimization and force these files to be backed up.

RMAN-06760


skipping archived logs that are already backed up
Cause:Some archived logs were not be backed up because they were already backed up on the device requested.
Action: No action is required. You can use the FORCE option to override backup optimization and force these files to be backed up.

RMAN-06761


skipping backup sets that are already backed up
Cause:Some backup sets were not be backed up because they were already backed up on the device requested.
Action: No action is required. You can use the FORCE option to override backup optimization and force these files to be backed up.

RMAN-06762


ignoring encryption for proxy or image copies
Cause:This information message is displayed when the RMAN client is generating proxy or image copies and encryption was enabled for the input files.
Action: This is an informational message only.

RMAN-06763


specified encryption algorithm not supported
Cause:An encryption algorithm not supported by the database is specified during backup.
Action: Refer to contents of v$backup_encryption_algorithms view for the list of supported encryption algorithm. Specify a valid encryption algorithm and retry the command.

RMAN-06764


%s
Cause:An error occured when processing user request.
Action: none

RMAN-06765


tablespace string will be encrypted in future backup sets
Cause:This is an informational message only.
Action: No action is required.

RMAN-06766


tablespace string will not be encrypted in future backup sets
Cause:This is an informational message only.
Action: No action is required.

RMAN-06767


tablespace string will default to database encryption configuration
Cause:This is an informational message only.
Action: No action is required.

RMAN-06768


duplicate or conflicting options are specified: string and string
Cause:An error occured when processing the command because user specified two duplicate options or the two options are not allowed to be used together.
Action: Remove one of the above options and retry the command.

RMAN-06769


length of password must be greater than zero
Cause:Zero length password was specified for encrypted backups.
Action: Retry the command using a password with non-zero length.

RMAN-06770


backup encryption requires Enterprise Edition
Cause:The backup command tried to create encrypted backups, but Enterprise Edition is not installed.
Action: Do not create encrypted backups.

RMAN-06899


updating recovery catalog with new database incarnation
Cause:The target database has a new incarnation that has not already been seen by the recovery catalog. This usually happens because a point-in-time recovery was done. RMAN has made the necessary updates to the recovery catalog.
Action: This is an informational message only.

RMAN-06900


WARNING: unable to generate V$RMAN_STATUS or V$RMAN_OUTPUT row
Cause:The routine createRmanStatusRow() or createRmanOutputRow() could add new row into V$RMAN_STATUS or V$RMAN_OUTPUT.
Action: Check the associated error messages. If the associated error message indicates a condition that can be corrected, do so, otherwise contact Oracle.

RMAN-06901


WARNING: disabling update of the V$RMAN_STATUS and V$RMAN_OUTPUT rows
Cause:Informational message only.
Action: No action required.

RMAN-06902


AS COMPRESSED BACKUPSET option cannot be used when backing up backupsets
Cause:The backupset was specified with AS COMPRESSED BACKUPSET.
Action: Remove the AS COMPRESSED BACKUPSET option.

RMAN-06903


backup of datafile string was cancelled
Cause:This is an informational message displayed when PARTIAL option of DURATION option was specified on the BACKUP command and backup could not be completed within the given duration time.
Action: Run the BACKUP command to backup cancelled files, or let the next backup window backup the cancelled files. It should be noted that the files that were skipped in the current job will be given preference to other files for next the BACKUP command with DURATION option.

RMAN-06904


backup of log thread number seq number lowscn string was cancelled
Cause:This is an informational message displayed when PARTIAL option of DURATION option was specified on the BACKUP command and backup could not be completed within the given duration time.
Action: Run BACKUP command to backup cancelled files, or let the next backup window backup the cancelled files. It should be noted that the files that were skipped in the current job will be given preference to other files for next the BACKUP command with DURATION option.

RMAN-06905


backup of backupset key number was cancelled
Cause:This is an informational message displayed when PARTIAL option of DURATION option was specified on the BACKUP command and backup could not be completed within the given duration time.
Action: Run BACKUP command to backup cancelled files, or let the next backup window backup the cancelled files. It should be noted that the files that were skipped in the current job will be given preference to other files for next the BACKUP command with DURATION option.

RMAN-06906


backup of control file was cancelled
Cause:This is an informational message displayed when PARTIAL option of DURATION option was specified on the BACKUP command and backup could not be completed within the given duration time.
Action: Run BACKUP command to backup cancelled files, or let the next backup window backup the cancelled files. It should be noted that the files that were skipped in the current job will be given preference to other files for next the BACKUP command with DURATION option.

RMAN-06907


MINIMIZE LOAD option not allowed for the specified input files
Cause:This option was specified in a backup command specification for BACKUP BACKUPSET or BACKUP CURRENT CONTROLFILE command.
Action: Remove the MINIMIZE LOAD option and retry the command.

RMAN-06908


WARNING: operation will not run in parallel on the allocated channels
Cause:RMAN allocated more than one channel for a job, but the job will not run in parallel on these channels because parallelism require Enterprise Edition.
Action: None

RMAN-06909


WARNING: parallelism require Enterprise Edition
Cause:RMAN allocated more than one channel for a job, but the job will not run in parallel on these channels because parallelism require Enterprise Edition.
Action: None

RMAN-06910


can not invoke parallel recovery for test recovery
Cause:Recover database was called with TEST and PARALLEL option
Action: Call recover database with either just the TEST or PARALLEL option

RMAN-06911


only one PARALLEL or NOPARALLEL clause may be specified
Cause:Recover database was called with PARALLEL and NOPARALLEL option
Action: Call recover database with either just the PARALLEL or NOPARALLEL option.

RMAN-06912


backup of spfile was cancelled
Cause:This is an informational message displayed when PARTIAL option of DURATION option was specified on the BACKUP command and backup could not be completed within the given duration time.
Action: Run BACKUP command to backup cancelled files, or let the next backup window backup the cancelled files. It should be noted that the files that were skipped in the current job will be given preference to other files for next the BACKUP command with DURATION option.

RMAN-06920


database string is not open read-only
Cause:CONVERT DATABASE attempted on a database that was not open read-only.
Action: Open the database in read-only mode and retry the operation.

RMAN-06921


Convert database check failed
Cause:This database could not be transported because dbms_tdb.check_db returned FALSE.
Action: None

RMAN-06922


External table string.string found in the database
Cause:An external table was found in the database.
Action: Redefine the table in the transported database.

RMAN-06923


Directory string.string found in the database
Cause:A directory object was found in the database.
Action: Redefine the directory in the transported database.

RMAN-06924


BFILE string.string found in the database
Cause:A BFILE was found in the database.
Action: Redefine the BFILE in the transported database.

RMAN-06925


BFILEs are used in the system, please redefine them in the transported database
Cause:BFILEs may or may not exist in the database. Automatically performed BFILE check failed because database was open read-only and could not allocate temporary space. This does not affect CONVERT DATABASE operation.
Action: Use dbms_tdb.check_external to perform BFILE check when the database is open in read/write mode.

RMAN-06926


User string with string privilege found in password file
Cause:Password file was used.
Action: Re-create the password file on the target platform using ORAPWD for the transported database.

RMAN-06927


Cannot specify NEW DATABASE clause more than once
Cause:NEW DATABASE clause specified more than once
Action: Remove redundant NEW DATABASE clause and retry the operation.

RMAN-06928


Cannot specify ON TARGET PLATFORM clause more than once
Cause:ON TARGET PLATFORM clause specified more than once
Action: Remove redundant ON TARGET PLATFORM clause and retry the operation.

RMAN-06929


Cannot specify TRANSPORT SCRIPT clause more than once
Cause:TRANSPORT SCRIPT clause specified more than once
Action: Remove redundant ON TARGET PLATFORM clause and retry the operation.

RMAN-06930


Cannot specify SKIP clause more than once
Cause:SKIP clause specified more than once
Action: Remove redundant SKIP clause and retry the operation.

RMAN-06931


Cannot specify FROM PLATFORM clause
Cause:CONVERT DATABASE command cannot use FROM PLATFORM clause.
Action: Change FROM PLATFORM clause and retry.

RMAN-06932


Database name 'string' longer than number
Cause:The specified database name exceeded the maximum allowable database name length.
Action: Correct the database name.

RMAN-06933


Transport script name too long
Cause:The specified transport script name exceeded the maximum allowable script name length.
Action: Correct the script name.

RMAN-06934


Format string too long
Cause:The specified format string exceeded the maximum allowable format string length.
Action: Correct the format string.

RMAN-06935


Convert script name too long
Cause:The specified convert script name exceeded the maximum allowable script name length.
Action: Correct the script name.

RMAN-06941


Database must be closed and mounted EXCLUSIVE and RESTRICTED.
Cause:DROP DATABASE was attempted while the database was open or not mounted EXCLUSIVE and RESTRICTED.
Action: Change the database state to mounted EXCLUSIVE and RESTRICTED.