今天在恢复一套测试库的时候遇到了ora-600(3020)错误SQLgt; recover datafile 6;ORA-00279: change 1981277 generated at 01/03
今天在恢复一套测试库的时候遇到了ora-600(3020)错误
SQL> recover datafile 6;
ORA-00279: change 1981277 generated at 01/03/2014 14:24:15 needed for thread 1
ORA-00289: suggestion : /opt/arch/archive_1_45_834576965.arc
ORA-00280: change 1981277 for thread 1 is in sequence #45
Specify log: {
auto
。。。
。。。
ORA-00283: recovery session canceled due to errors
ORA-00600: internal error code, arguments: [3020], [6], [59], [25165883], [],[], [], [], [], [], [], []
ORA-10567: Redo is inconsistent with data block (file# 6, block# 59, file
offset is 483328 bytes)
ORA-10564: tablespace GOOLEN
ORA-01110: data file 6: '/opt/app/Oracle/oradata/goolen/goolen01.dbf'
ORA-10561: block type 'TRANSACTION MANAGED DATA BLOCK', data object# 74195
ORA-01112: media recovery not started
alter日志报错:
Fri Jan 03 17:21:06 2014
ALTER DATABASE RECOVER datafile 6
Media Recovery Start
Serial Media Recovery started
ORA-279 signalled during: ALTER DATABASE RECOVER datafile 6 ...
ALTER DATABASE RECOVER CONTINUE DEFAULT
Media Recovery Log /opt/arch/archive_1_45_834576965.arc
Errors in file /opt/app/oracle/diag/rdbms/goolen/goolen/trace/goolen_ora_11763.trc:
ORA-00308: cannot open archived log '/opt/arch/archive_1_44_834576965.arc'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-10567: Redo is inconsistent with data block (file# 6, block# 59, file offset is 483328 bytes)
ORA-10564: tablespace GOOLEN
ORA-01110: data file 6: '/opt/app/oracle/oradata/goolen/goolen01.dbf'
ORA-10561: block type 'TRANSACTION MANAGED DATA BLOCK', data object# 74195
Errors in file /opt/app/oracle/diag/rdbms/goolen/goolen/trace/goolen_ora_11763.trc (incident=15025):
ORA-00600: internal error code, arguments: [3020], [6], [59], [25165883], [], [], [], [], [], [], [], []
ORA-10567: Redo is inconsistent with data block (file# 6, block# 59, file offset is 483328 bytes)
ORA-10564: tablespace GOOLEN
ORA-01110: data file 6: '/opt/app/oracle/oradata/goolen/goolen01.dbf'
ORA-10561: block type 'TRANSACTION MANAGED DATA BLOCK', data object# 74195
Incident details in: /opt/app/oracle/diag/rdbms/goolen/goolen/incident/incdir_15025/goolen_ora_11763_i15025.trc
Media Recovery failed with error 600
trace文件内容:
buffer tsn: 6 rdba: 0x0180003b (6/59)
scn: 0x0000.00158d60 seq: 0x01 flg: 0x04 tail: 0x8d600601
frmt: 0x02 chkval: 0xf96d type: 0x06=trans data
on-disk scn: 0x0.158d60
DUMP REDO
Opcodes *.*
DBAs (file#, block#):
(6, 59) .
SCNs: scn: 0x0000.00158d60 (1412448) thru scn: 0x0000.001e3b9c (1981340)
Times: creation thru eternity
*Error 308 when opening Archive Log -
/opt/arch/archive_1_44_834576965.arc
*Error is non fatal for dump - Dump will continue
*Error 308 when opening Archive Log -
/opt/arch/archive_1_44_834576965.arc
*Error is non fatal for dump - Dump will continue
*Error 308 when opening Archive Log -
/opt/arch/archive_1_39_834576965.arc
*Error is non fatal for dump - Dump will continue
*Error 308 when opening Archive Log -
/opt/arch/archive_1_39_834576965.arc
SQL> select segment_name, segment_type, owner
2 from dba_extents
3 where file_id = &file_id
4 and &block_id between block_id and block_id + blocks - 1;
Enter value for file_id: 6
old 3: where file_id = &file_id
new 3: where file_id = 6
Enter value for block_id: 59
old 4: and &block_id between block_id and block_id + blocks - 1
new 4: and 59 between block_id and block_id + blocks - 1
no rows selected
SQL> select *
2 from dba_free_space
3 where file_id = &file_id
4 and &block_id between block_id and block_id + blocks - 1;
Enter value for file_id: 6
old 3: where file_id = &file_id
new 3: where file_id = 6
Enter value for block_id: 59
old 4: and &block_id between block_id and block_id + blocks - 1
new 4: and 59 between block_id and block_id + blocks - 1
no rows selected
SQL> SELECT owner, segment_name, segment_type, partition_name
2 FROM dba_segments
3 WHERE header_file =&file_id
4 and header_block=&block_id;
Enter value for file_id: 6
old 3: WHERE header_file =&file_id
new 3: WHERE header_file =6
Enter value for block_id: 59
old 4: and header_block=&block_id
new 4: and header_block=59
no rows selected

Stored procedures are precompiled SQL statements in MySQL for improving performance and simplifying complex operations. 1. Improve performance: After the first compilation, subsequent calls do not need to be recompiled. 2. Improve security: Restrict data table access through permission control. 3. Simplify complex operations: combine multiple SQL statements to simplify application layer logic.

The working principle of MySQL query cache is to store the results of SELECT query, and when the same query is executed again, the cached results are directly returned. 1) Query cache improves database reading performance and finds cached results through hash values. 2) Simple configuration, set query_cache_type and query_cache_size in MySQL configuration file. 3) Use the SQL_NO_CACHE keyword to disable the cache of specific queries. 4) In high-frequency update environments, query cache may cause performance bottlenecks and needs to be optimized for use through monitoring and adjustment of parameters.

The reasons why MySQL is widely used in various projects include: 1. High performance and scalability, supporting multiple storage engines; 2. Easy to use and maintain, simple configuration and rich tools; 3. Rich ecosystem, attracting a large number of community and third-party tool support; 4. Cross-platform support, suitable for multiple operating systems.

The steps for upgrading MySQL database include: 1. Backup the database, 2. Stop the current MySQL service, 3. Install the new version of MySQL, 4. Start the new version of MySQL service, 5. Recover the database. Compatibility issues are required during the upgrade process, and advanced tools such as PerconaToolkit can be used for testing and optimization.

MySQL backup policies include logical backup, physical backup, incremental backup, replication-based backup, and cloud backup. 1. Logical backup uses mysqldump to export database structure and data, which is suitable for small databases and version migrations. 2. Physical backups are fast and comprehensive by copying data files, but require database consistency. 3. Incremental backup uses binary logging to record changes, which is suitable for large databases. 4. Replication-based backup reduces the impact on the production system by backing up from the server. 5. Cloud backups such as AmazonRDS provide automation solutions, but costs and control need to be considered. When selecting a policy, database size, downtime tolerance, recovery time, and recovery point goals should be considered.

MySQLclusteringenhancesdatabaserobustnessandscalabilitybydistributingdataacrossmultiplenodes.ItusestheNDBenginefordatareplicationandfaulttolerance,ensuringhighavailability.Setupinvolvesconfiguringmanagement,data,andSQLnodes,withcarefulmonitoringandpe

Optimizing database schema design in MySQL can improve performance through the following steps: 1. Index optimization: Create indexes on common query columns, balancing the overhead of query and inserting updates. 2. Table structure optimization: Reduce data redundancy through normalization or anti-normalization and improve access efficiency. 3. Data type selection: Use appropriate data types, such as INT instead of VARCHAR, to reduce storage space. 4. Partitioning and sub-table: For large data volumes, use partitioning and sub-table to disperse data to improve query and maintenance efficiency.

TooptimizeMySQLperformance,followthesesteps:1)Implementproperindexingtospeedupqueries,2)UseEXPLAINtoanalyzeandoptimizequeryperformance,3)Adjustserverconfigurationsettingslikeinnodb_buffer_pool_sizeandmax_connections,4)Usepartitioningforlargetablestoi


Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

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

Hot Article

Hot Tools

SublimeText3 Linux new version
SublimeText3 Linux latest version

SAP NetWeaver Server Adapter for Eclipse
Integrate Eclipse with SAP NetWeaver application server.

SublimeText3 Chinese version
Chinese version, very easy to use

Dreamweaver Mac version
Visual web development tools

PhpStorm Mac version
The latest (2018.2.1) professional PHP integrated development tool
