Home Database Mysql Tutorial rman 恢复--current redo 损坏的情况

rman 恢复--current redo 损坏的情况

Jun 07, 2016 pm 05:15 PM

用rman恢复,current redo 日志损坏的情况1、做全库备份RMANgt; run{ allocate channel c1 type disk maxpiecesize=500m; backu

用rman恢复,current redo 日志损坏的情况
1、做全库备份
RMAN> run{
 allocate channel c1 type disk maxpiecesize=500m;
 backup current controlfile format '+dgasm/backup/haozg/ctl_%d_%s';
 backup full database format '+dgasm/backup/haozg/db_%d_%s_%p_%t';
 release channel c1;
 }2> 3> 4> 5> 6>
released channel: ORA_DISK_1
allocated channel: c1
channel c1: SID=19 device type=DISK
Starting backup at 02-JUL-12
channel c1: starting full datafile backup set
channel c1: specifying datafile(s) in backup set
including current control file in backup set
channel c1: starting piece 1 at 02-JUL-12
channel c1: finished piece 1 at 02-JUL-12
piece handle=+DGASM/backup/haozg/ctl_ora11_57 tag=TAG20120702T110101 comment=NONE
channel c1: backup set complete, elapsed time: 00:00:03
Finished backup at 02-JUL-12
Starting backup at 02-JUL-12
channel c1: starting full datafile backup set
channel c1: specifying datafile(s) in backup set
input datafile file number=00001 name=+DGASM/ora11/datafile/system.257.785186755
input datafile file number=00002 name=+DGASM/ora11/datafile/sysaux.258.785186845
input datafile file number=00003 name=+DGASM/ora11/datafile/undotbs1.259.785186901
input datafile file number=00004 name=+DGASM/ora11/datafile/users.272.787487359
channel c1: starting piece 1 at 02-JUL-12
channel c1: finished piece 1 at 02-JUL-12
piece handle=+DGASM/backup/haozg/db_ora11_58_1_787575668 tag=TAG20120702T110107 comment=NONE
channel c1: starting piece 2 at 02-JUL-12
channel c1: finished piece 2 at 02-JUL-12
piece handle=+DGASM/backup/haozg/db_ora11_58_2_787575668 tag=TAG20120702T110107 comment=NONE
channel c1: backup set complete, elapsed time: 00:01:10
channel c1: starting full datafile backup set
channel c1: specifying datafile(s) in backup set
including current control file in backup set
including current SPFILE in backup set
channel c1: starting piece 1 at 02-JUL-12
channel c1: finished piece 1 at 02-JUL-12
piece handle=+DGASM/backup/haozg/db_ora11_59_1_787575738 tag=TAG20120702T110107 comment=NONE
channel c1: backup set complete, elapsed time: 00:00:02
Finished backup at 02-JUL-12
released channel: c1
RMAN>
2、做操作,,让不同的操作分布在不同的归档日志文件中,并且检查日志情况和检查点情况
SQL> select first_change#,next_change#,group#,sequence#,status from v$log;
FIRST_CHANGE# NEXT_CHANGE#     GROUP#  SEQUENCE# STATUS
------------- ------------ ---------- ---------- ----------------
       999200       999353          1          7 INACTIVE
       999353       999426          2          8 INACTIVE
       999426   2.8147E+14          3          9 CURRENT
SQL> create table test22(aab001 varchar(15),aab003 varchar(20));
Table created.
SQL>  insert into test22 values ('soft','0001');
1 row created.
SQL> /
1 row created.
SQL> /
1 row created.
SQL> commit;
Commit complete.
SQL> select * from test22;
AAB001          AAB003
--------------- --------------------
soft            0001
soft            0001
soft            0001
SQL> alter system switch logfile;
System altered.
SQL> select first_change#,next_change#,group#,sequence#,status from v$log;
FIRST_CHANGE# NEXT_CHANGE#     GROUP#  SEQUENCE# STATUS
------------- ------------ ---------- ---------- ----------------
      1000076   2.8147E+14          1         10 CURRENT
       999353       999426          2          8 INACTIVE
       999426      1000076          3          9 ACTIVE
SQL>  create table test33(aab001 number,aab004 varchar2(19));
Table created.
SQL> insert into test33 values(1,'zhang');
1 row created.
SQL> /.
1 row created.
SQL> /
1 row created.
SQL> commit;
Commit complete.
SQL> select * from test33;
    AAB001 AAB004
---------- -------------------
         1 zhang
         1 zhang
         1 zhang
SQL> alter system switch logfile;
System altered.
SQL>  select first_change#,next_change#,group#,sequence#,status from v$log;
FIRST_CHANGE# NEXT_CHANGE#     GROUP#  SEQUENCE# STATUS
------------- ------------ ---------- ---------- ----------------
      1000076      1000117          1         10 ACTIVE
      1000117   2.8147E+14          2         11 CURRENT
       999426      1000076          3          9 ACTIVE
SQL> create table c_test(aac001 varchar2(10),name varchar2(13));
Table created.
SQL> insert into c_test values('1392027','haozg');
1 row created.
SQL> /
1 row created.
SQL> /.
1 row created.
SQL> /
1 row created.
SQL> commit;
Commit complete.
SQL> select * from c_test;
AAC001     NAME
---------- -------------
1392027    haozg
1392027    haozg
1392027    haozg
1392027    haozg
SQL> select first_change#,next_change#,group#,sequence#,status from v$log;
FIRST_CHANGE# NEXT_CHANGE#     GROUP#  SEQUENCE# STATUS
------------- ------------ ---------- ---------- ----------------
      1000076      1000117          1         10 ACTIVE
      1000117   2.8147E+14          2         11 CURRENT
       999426      1000076          3          9 ACTIVE

3、shutdown abort
SQL> shutdown abort;
Oracle instance shut down.

linux

Statement of this Website
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn

Hot AI Tools

Undresser.AI Undress

Undresser.AI Undress

AI-powered app for creating realistic nude photos

AI Clothes Remover

AI Clothes Remover

Online AI tool for removing clothes from photos.

Undress AI Tool

Undress AI Tool

Undress images for free

Clothoff.io

Clothoff.io

AI clothes remover

Video Face Swap

Video Face Swap

Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Tools

Notepad++7.3.1

Notepad++7.3.1

Easy-to-use and free code editor

SublimeText3 Chinese version

SublimeText3 Chinese version

Chinese version, very easy to use

Zend Studio 13.0.1

Zend Studio 13.0.1

Powerful PHP integrated development environment

Dreamweaver CS6

Dreamweaver CS6

Visual web development tools

SublimeText3 Mac version

SublimeText3 Mac version

God-level code editing software (SublimeText3)

When might a full table scan be faster than using an index in MySQL? When might a full table scan be faster than using an index in MySQL? Apr 09, 2025 am 12:05 AM

Full table scanning may be faster in MySQL than using indexes. Specific cases include: 1) the data volume is small; 2) when the query returns a large amount of data; 3) when the index column is not highly selective; 4) when the complex query. By analyzing query plans, optimizing indexes, avoiding over-index and regularly maintaining tables, you can make the best choices in practical applications.

Can I install mysql on Windows 7 Can I install mysql on Windows 7 Apr 08, 2025 pm 03:21 PM

Yes, MySQL can be installed on Windows 7, and although Microsoft has stopped supporting Windows 7, MySQL is still compatible with it. However, the following points should be noted during the installation process: Download the MySQL installer for Windows. Select the appropriate version of MySQL (community or enterprise). Select the appropriate installation directory and character set during the installation process. Set the root user password and keep it properly. Connect to the database for testing. Note the compatibility and security issues on Windows 7, and it is recommended to upgrade to a supported operating system.

Explain InnoDB Full-Text Search capabilities. Explain InnoDB Full-Text Search capabilities. Apr 02, 2025 pm 06:09 PM

InnoDB's full-text search capabilities are very powerful, which can significantly improve database query efficiency and ability to process large amounts of text data. 1) InnoDB implements full-text search through inverted indexing, supporting basic and advanced search queries. 2) Use MATCH and AGAINST keywords to search, support Boolean mode and phrase search. 3) Optimization methods include using word segmentation technology, periodic rebuilding of indexes and adjusting cache size to improve performance and accuracy.

Difference between clustered index and non-clustered index (secondary index) in InnoDB. Difference between clustered index and non-clustered index (secondary index) in InnoDB. Apr 02, 2025 pm 06:25 PM

The difference between clustered index and non-clustered index is: 1. Clustered index stores data rows in the index structure, which is suitable for querying by primary key and range. 2. The non-clustered index stores index key values ​​and pointers to data rows, and is suitable for non-primary key column queries.

MySQL: Simple Concepts for Easy Learning MySQL: Simple Concepts for Easy Learning Apr 10, 2025 am 09:29 AM

MySQL is an open source relational database management system. 1) Create database and tables: Use the CREATEDATABASE and CREATETABLE commands. 2) Basic operations: INSERT, UPDATE, DELETE and SELECT. 3) Advanced operations: JOIN, subquery and transaction processing. 4) Debugging skills: Check syntax, data type and permissions. 5) Optimization suggestions: Use indexes, avoid SELECT* and use transactions.

Can mysql and mariadb coexist Can mysql and mariadb coexist Apr 08, 2025 pm 02:27 PM

MySQL and MariaDB can coexist, but need to be configured with caution. The key is to allocate different port numbers and data directories to each database, and adjust parameters such as memory allocation and cache size. Connection pooling, application configuration, and version differences also need to be considered and need to be carefully tested and planned to avoid pitfalls. Running two databases simultaneously can cause performance problems in situations where resources are limited.

The relationship between mysql user and database The relationship between mysql user and database Apr 08, 2025 pm 07:15 PM

In MySQL database, the relationship between the user and the database is defined by permissions and tables. The user has a username and password to access the database. Permissions are granted through the GRANT command, while the table is created by the CREATE TABLE command. To establish a relationship between a user and a database, you need to create a database, create a user, and then grant permissions.

Explain different types of MySQL indexes (B-Tree, Hash, Full-text, Spatial). Explain different types of MySQL indexes (B-Tree, Hash, Full-text, Spatial). Apr 02, 2025 pm 07:05 PM

MySQL supports four index types: B-Tree, Hash, Full-text, and Spatial. 1.B-Tree index is suitable for equal value search, range query and sorting. 2. Hash index is suitable for equal value searches, but does not support range query and sorting. 3. Full-text index is used for full-text search and is suitable for processing large amounts of text data. 4. Spatial index is used for geospatial data query and is suitable for GIS applications.

See all articles