Oracle Dataguard备库失败与主库响应测试-Mysql Tutorial-php.cn

Home

Database

Mysql Tutorial

Oracle Dataguard备库失败与主库响应测试

WBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWB

Jun 07, 2016 pm 04:55 PM

oracle

在客户环境中，使用了Oracle 10.2.0.4 DataGuard技术，通过最大可用性模式进行数据保护。以下简单测试，当备库关闭后，再

　　在客户环境中，使用了Oracle 10.2.0.4 DataGuard技术，通过最大可用性模式进行数据保护。
　　以下简单测试，当备库关闭后，再重启备库，主库及备库的响应过程。

　　在备库执行如下步骤：

　　SQL> shutdown immediate;
　　ORA-01109: database not open
　　Database dismounted.
　　ORACLE instance shut down.
　　SQL> startup mount;
　　ORACLE instance started.
　　Total System Global Area 1610612736 bytes
　　Fixed Size                  2084400 bytes
　　Variable Size             385876432 bytes
　　Database Buffers         1207959552 bytes
　　Redo Buffers               14692352 bytes
　　Database mounted.
　　SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
　　Database altered.
　　SQL> exit

　　当备库关闭后，主库立即检测到备库的失败：

　　Tue Nov 17 20:34:58 2009
　　ARC1: Attempting destination LOG_ARCHIVE_DEST_2 network reconnect (3113)
　　ARC1: Destination LOG_ARCHIVE_DEST_2 network reconnect abandoned
　　PING[ARC1]: Error 3113 when pinging standby STANDBY.
　　Tue Nov 17 20:35:17 2009
　　LGWR: Attempting destination LOG_ARCHIVE_DEST_2 network reconnect (3113)
　　LGWR: Destination LOG_ARCHIVE_DEST_2 network reconnect abandoned
　　Tue Nov 17 20:35:17 2009
　　Errors in file /opt/oracle/admin/oradbt/bdump/oradbt_lgwr_319632.trc:
　　ORA-03113: end-of-file on communication channel
　　LGWR: Network asynch I/O wait error 3113 log 1 service 'STANDBY'
　　Tue Nov 17 20:35:17 2009
　　Destination LOG_ARCHIVE_DEST_2 is UNSYNCHRONIZED
　　LGWR: Failed to archive log 1 thread 1 sequence 3466 (3113)
　　Tue Nov 17 20:35:18 2009
　　LGWR: Closing remote archive destination LOG_ARCHIVE_DEST_2: 'STANDBY' (error 3113)
　　(oradbt)
　　Tue Nov 17 20:35:18 2009
　　Errors in file /opt/oracle/admin/oradbt/bdump/oradbt_lgwr_319632.trc:
　　ORA-01041: internal error. hostdef extension doesn't exist
　　LGWR: Error 1041 closing archivelog file 'STANDBY'
　　LGWR: Error 1041 disconnecting from destination LOG_ARCHIVE_DEST_2 standby host 'STANDBY'

linux

，

Statement

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

Explain the role of InnoDB redo logs and undo logs.Apr 15, 2025 am 12:16 AM

InnoDB uses redologs and undologs to ensure data consistency and reliability. 1.redologs record data page modification to ensure crash recovery and transaction persistence. 2.undologs records the original data value and supports transaction rollback and MVCC.

What are the key metrics to look for in an EXPLAIN output (type, key, rows, Extra)?Apr 15, 2025 am 12:15 AM

Key metrics for EXPLAIN commands include type, key, rows, and Extra. 1) The type reflects the access type of the query. The higher the value, the higher the efficiency, such as const is better than ALL. 2) The key displays the index used, and NULL indicates no index. 3) rows estimates the number of scanned rows, affecting query performance. 4) Extra provides additional information, such as Usingfilesort prompts that it needs to be optimized.

What is the Using temporary status in EXPLAIN and how to avoid it?Apr 15, 2025 am 12:14 AM

Usingtemporary indicates that the need to create temporary tables in MySQL queries, which are commonly found in ORDERBY using DISTINCT, GROUPBY, or non-indexed columns. You can avoid the occurrence of indexes and rewrite queries and improve query performance. Specifically, when Usingtemporary appears in EXPLAIN output, it means that MySQL needs to create temporary tables to handle queries. This usually occurs when: 1) deduplication or grouping when using DISTINCT or GROUPBY; 2) sort when ORDERBY contains non-index columns; 3) use complex subquery or join operations. Optimization methods include: 1) ORDERBY and GROUPB

Describe the different SQL transaction isolation levels (Read Uncommitted, Read Committed, Repeatable Read, Serializable) and their implications in MySQL/InnoDB.Apr 15, 2025 am 12:11 AM

MySQL/InnoDB supports four transaction isolation levels: ReadUncommitted, ReadCommitted, RepeatableRead and Serializable. 1.ReadUncommitted allows reading of uncommitted data, which may cause dirty reading. 2. ReadCommitted avoids dirty reading, but non-repeatable reading may occur. 3.RepeatableRead is the default level, avoiding dirty reading and non-repeatable reading, but phantom reading may occur. 4. Serializable avoids all concurrency problems but reduces concurrency. Choosing the appropriate isolation level requires balancing data consistency and performance requirements.

MySQL vs. Other Databases: Comparing the OptionsApr 15, 2025 am 12:08 AM

MySQL is suitable for web applications and content management systems and is popular for its open source, high performance and ease of use. 1) Compared with PostgreSQL, MySQL performs better in simple queries and high concurrent read operations. 2) Compared with Oracle, MySQL is more popular among small and medium-sized enterprises because of its open source and low cost. 3) Compared with Microsoft SQL Server, MySQL is more suitable for cross-platform applications. 4) Unlike MongoDB, MySQL is more suitable for structured data and transaction processing.

How does MySQL index cardinality affect query performance?Apr 14, 2025 am 12:18 AM

MySQL index cardinality has a significant impact on query performance: 1. High cardinality index can more effectively narrow the data range and improve query efficiency; 2. Low cardinality index may lead to full table scanning and reduce query performance; 3. In joint index, high cardinality sequences should be placed in front to optimize query.

MySQL: Resources and Tutorials for New UsersApr 14, 2025 am 12:16 AM

The MySQL learning path includes basic knowledge, core concepts, usage examples, and optimization techniques. 1) Understand basic concepts such as tables, rows, columns, and SQL queries. 2) Learn the definition, working principles and advantages of MySQL. 3) Master basic CRUD operations and advanced usage, such as indexes and stored procedures. 4) Familiar with common error debugging and performance optimization suggestions, such as rational use of indexes and optimization queries. Through these steps, you will have a full grasp of the use and optimization of MySQL.

Real-World MySQL: Examples and Use CasesApr 14, 2025 am 12:15 AM

MySQL's real-world applications include basic database design and complex query optimization. 1) Basic usage: used to store and manage user data, such as inserting, querying, updating and deleting user information. 2) Advanced usage: Handle complex business logic, such as order and inventory management of e-commerce platforms. 3) Performance optimization: Improve performance by rationally using indexes, partition tables and query caches.

See all articles