Para abrir o utilit\u00e1rio RMAN e conectar-se ao banco de dados, temos as seguintes maneiras (com autentica\u00e7\u00e3o via S.O):<\/p>\n\n\n
\n[oracle@oel8 ~]$ rman\n \nRecovery Manager: Release 18.0.0.0.0 - Production on Wed Mar 10 13:00:51 2021\nVersion 18.3.0.0.0\n \nCopyright (c) 1982, 2018, Oracle and\/or its affiliates. All rights reserved.\n \nRMAN> CONNECT TARGET \/\n \nconnected to target database: RMANDB (DBID=3825250984)\n \nRMAN>\n<\/pre><\/div>\n\n\n[oracle@oel8 ~]$ rman target \/\n \nRecovery Manager: Release 18.0.0.0.0 - Production on Wed Mar 10 13:02:33 2021\nVersion 18.3.0.0.0\n \nCopyright (c) 1982, 2018, Oracle and\/or its affiliates. All rights reserved.\n \nconnected to target database: RMANDB (DBID=3825250984)\n \nRMAN>\n<\/pre><\/div>\n\n\nConectando via autentica\u00e7\u00e3o por usu\u00e1rio e senha:<\/p>\n\n\n
\n[oracle@oel8 ~]$ rman\n \nRecovery Manager: Release 18.0.0.0.0 - Production on Wed Mar 10 13:05:10 2021\nVersion 18.3.0.0.0\n \nCopyright (c) 1982, 2018, Oracle and\/or its affiliates. All rights reserved.\n \nRMAN> connect target sys@RMANDB\n \ntarget database Password:\nconnected to target database: RMANDB (DBID=3825250984)\n \nRMAN> exit\n \n \nRecovery Manager complete.\n[oracle@oel8 ~]$ rman target sys@RMANDB\n \nRecovery Manager: Release 18.0.0.0.0 - Production on Wed Mar 10 13:05:34 2021\nVersion 18.3.0.0.0\n \nCopyright (c) 1982, 2018, Oracle and\/or its affiliates. All rights reserved.\n \ntarget database Password:\nconnected to target database: RMANDB (DBID=3825250984)\n \nRMAN>\n<\/pre><\/div>\n\n\nCriando um usu\u00e1rio no banco de dados com privil\u00e9gio de sysbackup (ou seja, n\u00e3o ter\u00e1 acesso para administrar o banco de dados, como um sysdba, e sim apenas para atividades inerentes ao RMAN):<\/p>\n\n\n
\n[oracle@oel8 ~]$ sqlplus \/ as sysdba\n \nSQL*Plus: Release 18.0.0.0.0 - Production on Wed Mar 10 13:06:09 2021\nVersion 18.3.0.0.0\n \nCopyright (c) 1982, 2018, Oracle. All rights reserved.\n \n \nConnected to:\nOracle Database 18c Enterprise Edition Release 18.0.0.0.0 - Production\nVersion 18.3.0.0.0\n \nSQL> CREATE USER BSS IDENTIFIED BY BSS;\n \nUser created.\n \nSQL> GRANT SYSBACKUP TO BSS;\n \nGrant succeeded.\n \nSQL> GRANT CREATE SESSION TO BSS;\n \nGrant succeeded.\n \nSQL> exit\n<\/pre><\/div>\n\n\nRealizando a autentica\u00e7\u00e3o com o usu\u00e1rio criado acima:<\/p>\n\n\n
\n[oracle@oel8 ~]$ rman target "'BSS\/BSS@RMANDB as sysbackup'"\n \nRecovery Manager: Release 18.0.0.0.0 - Production on Wed Mar 10 13:09:29 2021\nVersion 18.3.0.0.0\n \nCopyright (c) 1982, 2018, Oracle and\/or its affiliates. All rights reserved.\n \nconnected to target database: RMANDB (DBID=3825250984)\n \nRMAN>\n<\/pre><\/div>\n\n\nPodemos gerar um script de log com todo o conte\u00fado gerado dentro do RMAN, conforme exemplo abaixo (a op\u00e7\u00e3o append n\u00e3o reescreve o arquivo, mas sim vai adicionando conte\u00fado ao mesmo):<\/p>\n\n\n
\n[oracle@oel8 ~]$ rman target \/ log \/oracle\/rman.log append\nRMAN> show all;\nRMAN> exit\n[oracle@oel8 ~]$ cat \/oracle\/rman.log\n \nRecovery Manager: Release 18.0.0.0.0 - Production on Wed Mar 10 17:18:18 2021\nVersion 18.3.0.0.0\n \nCopyright (c) 1982, 2018, Oracle and\/or its affiliates. All rights reserved.\n \nconnected to target database: RMANDB (DBID=3825250984)\n \nRMAN>\nusing target database control file instead of recovery catalog\nRMAN configuration parameters for database with db_unique_name RMANDB are:\nCONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default\nCONFIGURE BACKUP OPTIMIZATION OFF; # default\nCONFIGURE DEFAULT DEVICE TYPE TO DISK; # default\nCONFIGURE CONTROLFILE AUTOBACKUP ON; # default\nCONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default\nCONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default\nCONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default\nCONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default\nCONFIGURE MAXSETSIZE TO UNLIMITED; # default\nCONFIGURE ENCRYPTION FOR DATABASE OFF; # default\nCONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default\nCONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default\nCONFIGURE RMAN OUTPUT TO KEEP FOR 7 DAYS; # default\nCONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default\nCONFIGURE SNAPSHOT CONTROLFILE NAME TO '\/oracle\/18.0.0\/product\/dbs\/snapcf_RMANDB.f'; # default\n \nRMAN>\n \nRecovery Manager complete.\n[oracle@oel8 ~]$\n<\/pre><\/div>\n\n\nUtilizando o recurso de CMDFILE, podemos encapsular os comandos rman em um script e execut\u00e1-lo conforme exemplo:<\/p>\n\n\n
\n[oracle@oel8 ~]$ cat \/oracle\/SCRIPT.rcvd\nrun\n{SHOW ALL;}\n[oracle@oel8 ~]$ rman target \/ CMDFILE=\/oracle\/SCRIPT.rcvd\n \nRecovery Manager: Release 18.0.0.0.0 - Production on Wed Mar 10 17:22:43 2021\nVersion 18.3.0.0.0\n \nCopyright (c) 1982, 2018, Oracle and\/or its affiliates. All rights reserved.\n \nconnected to target database: RMANDB (DBID=3825250984)\n \nRMAN> run\n2> {SHOW ALL;}\n3>\nusing target database control file instead of recovery catalog\nRMAN configuration parameters for database with db_unique_name RMANDB are:\nCONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default\nCONFIGURE BACKUP OPTIMIZATION OFF; # default\nCONFIGURE DEFAULT DEVICE TYPE TO DISK; # default\nCONFIGURE CONTROLFILE AUTOBACKUP ON; # default\nCONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default\nCONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default\nCONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default\nCONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default\nCONFIGURE MAXSETSIZE TO UNLIMITED; # default\nCONFIGURE ENCRYPTION FOR DATABASE OFF; # default\nCONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default\nCONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default\nCONFIGURE RMAN OUTPUT TO KEEP FOR 7 DAYS; # default\nCONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default\nCONFIGURE SNAPSHOT CONTROLFILE NAME TO '\/oracle\/18.0.0\/product\/dbs\/snapcf_RMANDB.f'; # default\n \nRecovery Manager complete.\nRMAN> exit\n \nRecovery Manager complete.\n[oracle@oel8 ~]$ rman target \/\n \nRecovery Manager: Release 18.0.0.0.0 - Production on Wed Mar 10 17:23:47 2021\nVersion 18.3.0.0.0\n \nCopyright (c) 1982, 2018, Oracle and\/or its affiliates. All rights reserved.\n \nconnected to target database: RMANDB (DBID=3825250984)\n \nRMAN> @\/oracle\/SCRIPT.rcvd\n \nRMAN> run\n2> {SHOW ALL;}\nusing target database control file instead of recovery catalog\nRMAN configuration parameters for database with db_unique_name RMANDB are:\nCONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default\nCONFIGURE BACKUP OPTIMIZATION OFF; # default\nCONFIGURE DEFAULT DEVICE TYPE TO DISK; # default\nCONFIGURE CONTROLFILE AUTOBACKUP ON; # default\nCONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default\nCONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default\nCONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default\nCONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default\nCONFIGURE MAXSETSIZE TO UNLIMITED; # default\nCONFIGURE ENCRYPTION FOR DATABASE OFF; # default\nCONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default\nCONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default\nCONFIGURE RMAN OUTPUT TO KEEP FOR 7 DAYS; # default\nCONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default\nCONFIGURE SNAPSHOT CONTROLFILE NAME TO '\/oracle\/18.0.0\/product\/dbs\/snapcf_RMANDB.f'; # default\n \nRMAN> **end-of-file**\n<\/pre><\/div>\n\n\nUma vari\u00e1vel linux que \u00e9 importante de definir para evitar confus\u00f5es ao utilizar o RMAN \u00e9 a NLS_DATE_FORMAT:<\/p>\n\n\n
\n[oracle@oel8 ~]$ cat .bash_profile | grep NLS\nNLS_DATE_FORMAT="YYYY-MM-DD:HH24:MI:SS"\nexport ORACLE_SID ORACLE_BASE ORACLE_HOME GRID_HOME LD_LIBRARY_PATH PATH NLS_DATE_FORMAT\n[oracle@oel8 ~]$\n<\/pre><\/div>\n\n\nConforme exemplos acima, dentro do RMAN \u00e9 poss\u00edvel definir uma s\u00e9rie de par\u00e2metros que definem o comportamento que a ferramenta adotar\u00e1. Como este banco de dados n\u00e3o teve nenhuma altera\u00e7\u00e3o ainda destes par\u00e2metros, notamos que h\u00e1 uma flag \\”# default\\” no final de cada linha. Para consultarmos um par\u00e2metro em espec\u00edfico, podemos usar o comando abaixo de exemplo:<\/p>\n\n\n
\nRMAN> SHOW CONTROLFILE AUTOBACKUP;\n \nRMAN configuration parameters for database with db_unique_name RMANDB are:\nCONFIGURE CONTROLFILE AUTOBACKUP ON; # default\n<\/pre><\/div>\n\n\nAlterando o conte\u00fado do par\u00e2metro, \u00e9 poss\u00edvel ver que a flag default n\u00e3o aparece mais:<\/p>\n\n\n
\nRMAN> CONFIGURE CONTROLFILE AUTOBACKUP OFF;\n \nnew RMAN configuration parameters:\nCONFIGURE CONTROLFILE AUTOBACKUP OFF;\nnew RMAN configuration parameters are successfully stored\n \nRMAN> SHOW CONTROLFILE AUTOBACKUP;\n \nRMAN configuration parameters for database with db_unique_name RMANDB are:\nCONFIGURE CONTROLFILE AUTOBACKUP OFF;\n \nRMAN>\n<\/pre><\/div>\n\n\nUtilizando a op\u00e7\u00e3o CLEAR vemos que o valor do par\u00e2metro retorna ao padr\u00e3o:<\/p>\n\n\n
\nRMAN> CONFIGURE CONTROLFILE AUTOBACKUP CLEAR\n2> ;\n \nold RMAN configuration parameters:\nCONFIGURE CONTROLFILE AUTOBACKUP OFF;\nRMAN configuration parameters are successfully reset to default value\n \nRMAN> SHOW CONTROLFILE AUTOBACKUP;\n \nRMAN configuration parameters for database with db_unique_name RMANDB are:\nCONFIGURE CONTROLFILE AUTOBACKUP ON; # default\n<\/pre><\/div>\n\n\nQuando um par\u00e2metro do RMAN for alterado (exceto para o seu valor default com a op\u00e7\u00e3o clear), ele tamb\u00e9m estar\u00e1 presente na view v$RMAN_CONFIGURATION:<\/p>\n\n\n
\nRMAN> CONFIGURE CONTROLFILE AUTOBACKUP OFF;\n \nnew RMAN configuration parameters:\nCONFIGURE CONTROLFILE AUTOBACKUP OFF;\nnew RMAN configuration parameters are successfully stored\n \nRMAN> exit\n \n \nRecovery Manager complete.\n[oracle@oel8 ~]$\n[oracle@oel8 ~]$\n[oracle@oel8 ~]$ sqlplus \/ as sysdba\n \nSQL*Plus: Release 18.0.0.0.0 - Production on Wed Mar 10 17:41:20 2021\nVersion 18.3.0.0.0\n \nCopyright (c) 1982, 2018, Oracle. All rights reserved.\n \n \nConnected to:\nOracle Database 18c Enterprise Edition Release 18.0.0.0.0 - Production\nVersion 18.3.0.0.0\n \nSQL> SELECT NAME,VALUE FROM v$RMAN_CONFIGURATION;\n \nNAME\n-----------------------------------------------------------------\nVALUE\n--------------------------------------------------------------------------------\nCONTROLFILE AUTOBACKUP\nOFF\n \n \nSQL>\n<\/pre><\/div>\n\n\nRMAN> CONFIGURE CONTROLFILE AUTOBACKUP CLEAR;\n \nusing target database control file instead of recovery catalog\nold RMAN configuration parameters:\nCONFIGURE CONTROLFILE AUTOBACKUP OFF;\nRMAN configuration parameters are successfully reset to default value\n \nRMAN> exit\n \n \nRecovery Manager complete.\n[oracle@oel8 ~]$ sqlplus \/ as sysdba\n \nSQL*Plus: Release 18.0.0.0.0 - Production on Wed Mar 10 17:44:14 2021\nVersion 18.3.0.0.0\n \nCopyright (c) 1982, 2018, Oracle. All rights reserved.\n \n \nConnected to:\nOracle Database 18c Enterprise Edition Release 18.0.0.0.0 - Production\nVersion 18.3.0.0.0\n \nSQL> SELECT NAME,VALUE FROM v$RMAN_CONFIGURATION;\n \nno rows selected\n<\/pre><\/div>\n\n\nNo RMAN, temos 2 categorias de comandos: Stand-alone e Jobs. Como os nomes sugerem, o primeiro refere-se aos comandos que s\u00e3o executados iterativa com o prompt, onde disparamos cada instru\u00e7\u00e3o (com o ; no final) e aguardamos a sua execu\u00e7\u00e3o para executar o passo seguinte. J\u00e1 o Job nos permite criar um bloco com uma s\u00e9rie de comandos que ser\u00e3o executados de forma sequencial pela ferramenta, e em caso de algum erro, o processo \u00e9 suspenso (n\u00e3o h\u00e1 rollback do que j\u00e1 foi executado):<\/p>\n\n\n
\n[oracle@oel8 ~]$ rman target \/\n \nRecovery Manager: Release 18.0.0.0.0 - Production on Wed Mar 10 17:53:22 2021\nVersion 18.3.0.0.0\n \nCopyright (c) 1982, 2018, Oracle and\/or its affiliates. All rights reserved.\n \nconnected to target database: RMANDB (DBID=3825250984)\n \nRMAN> #COMENTARIO: STAND-ALONE COMMAND\n2> SHOW CONTROLFILE AUTOBACKUP;\n \nusing target database control file instead of recovery catalog\nRMAN configuration parameters for database with db_unique_name RMANDB are:\nCONFIGURE CONTROLFILE AUTOBACKUP ON; # default\n \nRMAN> #COMENTARIO: JOB COMMAND\n2> RUN\n3> {\n4> SHOW CONTROLFILE AUTOBACKUP;\n5> }\n \nRMAN configuration parameters for database with db_unique_name RMANDB are:\nCONFIGURE CONTROLFILE AUTOBACKUP ON; # default\n \nRMAN>\n<\/pre><\/div>\n\n\nPor \u00faltimo: o controlfile abriga informa\u00e7\u00f5es de metadados sobre o Oracle (como suas estruturas f\u00edsicas, localiza\u00e7\u00e3o de datafiles e redologs, etc) e tamb\u00e9m sobre as informa\u00e7\u00f5es de backup emitidas pelo RMAN. Por padr\u00e3o, esses dados possuem reten\u00e7\u00e3o de 7 dias, mas caso n\u00e3o seja utilizado um cat\u00e1logo de forma apartada, o indicado \u00e9 que esta reten\u00e7\u00e3o seja maior:<\/p>\n\n\n
\n[oracle@oel8 ~]$ sqlplus \/ as sysdba\n \nSQL*Plus: Release 18.0.0.0.0 - Production on Wed Mar 10 17:57:47 2021\nVersion 18.3.0.0.0\n \nCopyright (c) 1982, 2018, Oracle. All rights reserved.\n \n \nConnected to:\nOracle Database 18c Enterprise Edition Release 18.0.0.0.0 - Production\nVersion 18.3.0.0.0\n \nSQL> SHOW PARAMETER CONTROL_FILE_RECORD_KEEP_TIME;\n \nNAME TYPE VALUE\n------------------------------------ ----------- ------------------------------\ncontrol_file_record_keep_time integer 7\nSQL> ALTER SYSTEM SET CONTROL_FILE_RECORD_KEEP_TIME=90 SCOPE=BOTH;\n \nSystem altered.\n \nSQL> SHOW PARAMETER CONTROL_FILE_RECORD_KEEP_TIME;\n \nNAME TYPE VALUE\n------------------------------------ ----------- ------------------------------\ncontrol_file_record_keep_time integer 90\nSQL>\n<\/pre><\/div>\n\n\nObs: Este procedimento foi criado pelo senhor Ahmed Baraka (www.ahmedbaraka.com) e foi apenas reproduzido por mim em um laborat\u00f3rio pessoal para fins de aprendizado.<\/p>\n","protected":false},"excerpt":{"rendered":"
Para abrir o utilit\u00e1rio RMAN e conectar-se ao banco de dados, temos as seguintes maneiras (com autentica\u00e7\u00e3o via S.O): Conectando via autentica\u00e7\u00e3o por usu\u00e1rio e senha: Criando um usu\u00e1rio no banco de dados com privil\u00e9gio de sysbackup (ou seja, n\u00e3o ter\u00e1 acesso para administrar o banco de dados, como um sysdba, e sim apenas para […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-2551","post","type-post","status-publish","format-standard","hentry","category-backup-recovery"],"_links":{"self":[{"href":"https:\/\/swiv.com.br\/index.php\/wp-json\/wp\/v2\/posts\/2551","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/swiv.com.br\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/swiv.com.br\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/swiv.com.br\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/swiv.com.br\/index.php\/wp-json\/wp\/v2\/comments?post=2551"}],"version-history":[{"count":1,"href":"https:\/\/swiv.com.br\/index.php\/wp-json\/wp\/v2\/posts\/2551\/revisions"}],"predecessor-version":[{"id":9240,"href":"https:\/\/swiv.com.br\/index.php\/wp-json\/wp\/v2\/posts\/2551\/revisions\/9240"}],"wp:attachment":[{"href":"https:\/\/swiv.com.br\/index.php\/wp-json\/wp\/v2\/media?parent=2551"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/swiv.com.br\/index.php\/wp-json\/wp\/v2\/categories?post=2551"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/swiv.com.br\/index.php\/wp-json\/wp\/v2\/tags?post=2551"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}