恢复db_recovery_file_dest_size参数为默认值“0”方法
db_recovery_file_dest_size参数的作用是限制闪回恢复区可存放文件总大
db_recovery_file_dest_size参数的作用是限制闪回恢复区可存放文件总大小。一旦将参数db_recovery_file_dest_size设置为非零值后“很难”恢复为默认值“0”。这里我给出两种可以将此参数恢复为默认值“0”的方法,一种是“迂回策略”,一种是reset方法。
1.查看默认情况下db_recovery_file_dest_size参数值
db_recovery_file_dest_size参数的默认值是“0”。
SYS@PROD> show parameter db_recovery_file_dest_size
NAME TYPE VALUE
------------------------------------ ----------- -------------
db_recovery_file_dest_size big integer 0
SYS@PROD> col name for a20
SYS@PROD> select * from v$recovery_file_dest;
NAME SPACE_LIMIT SPACE_USED SPACE_RECLAIMABLE NUMBER_OF_FILES
----- ----------- ---------- ----------------- ---------------
0 0 0 0
2.将db_recovery_file_dest_size参数调整为非零值
SYS@PROD> alter system set db_recovery_file_dest_size=4g;
System altered.
SYS@PROD> show parameter db_recovery_file_dest_size
NAME TYPE VALUE
------------------------------------ ----------- ------------
db_recovery_file_dest_size big integer 4G
SYS@PROD> select * from v$recovery_file_dest;
NAME SPACE_LIMIT SPACE_USED SPACE_RECLAIMABLE NUMBER_OF_FILES
----- ----------- ---------- ----------------- ---------------
4294967296 0 0 0
3.尝试将db_recovery_file_dest_size参数修改为“0”
SYS@PROD> alter system set db_recovery_file_dest_size=0;
alter system set db_recovery_file_dest_size=0
*
ERROR at line 1:
ORA-02097: parameter cannot be modified because specified value is invalid
ORA-19803: Parameter DB_RECOVERY_FILE_DEST_SIZE is out of range (1 -
18446744073709551614)
报错信息非常显然,db_recovery_file_dest_size参数大小必须介于1~18446744073709551614之间,也就是说不可以调整为其默认值“0”。
有朋友说,是不是可以尝试使用scope=spfile方式调整此参数。注意,也是不可以的。验证如下。
SYS@PROD> alter system set db_recovery_file_dest_size=0 scope=spfile;
System altered.
此处貌似修改成功,但是这样调整后数据库将无法重新启动,报错信息如下。
SYS@PROD> startup;
ORA-19803: Parameter DB_RECOVERY_FILE_DEST_SIZE is out of range (1 - 18446744073709551614)
一样的报错原因,db_recovery_file_dest_size参数大小必须介于1~18446744073709551614之间。
4.迂回处理方法
既然使用常规方法无法达到我们将db_recovery_file_dest_size参数调整为“0”的目的,那我们应该如何应对这个需求呢。
经过尝试,可以通过pfile迂回的达到恢复的目的。
1)使用当前的spfile生成pfile
SYS@PROD> create pfile from spfile;
File created.
2)使用vi命令将pfile中的db_recovery_file_dest_size参数信息删除掉
[Oracle@secdb1 ~]$ vi $ORACLE_HOME/dbs/initPROD.ora
……
*.db_recovery_file_dest_size=4294967296
……
注:如果经过上面scope=spfile方法调整过的话,pfile中的信息如下:
*.db_recovery_file_dest_size=0
方法是一样的,将整行信息删除掉。
3)停止数据库并生成spfile,并用spfile启动数据库
SYS@PROD> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SYS@PROD> create spfile from pfile;
File created.
SYS@PROD> startup;
ORACLE instance started.
Total System Global Area 314572800 bytes
Fixed Size 1219184 bytes
Variable Size 109053328 bytes
Database Buffers 201326592 bytes
Redo Buffers 2973696 bytes
Database mounted.
Database opened.
4)查看修改成果
SYS@PROD> show parameter db_recovery_file_dest_size
NAME TYPE VALUE
------------------------------------ ----------- -----------
db_recovery_file_dest_size big integer 0
SYS@PROD> col name for a20
SYS@PROD> select * from v$recovery_file_dest;
NAME SPACE_LIMIT SPACE_USED SPACE_RECLAIMABLE NUMBER_OF_FILES
------ ----------- ---------- ----------------- ---------------
0 0 0 0
目的达到。
5.使用直截了当的reset方法
恢复参数为默认值的另外一种便捷方法是使用reset方法,可以避免上面的“迂回策略”,,调整过程展示如下,供各位朋友参考。
SYS@PROD> show parameter db_recovery_file_dest_size
NAME TYPE VALUE
------------------------------------ ----------- --------
db_recovery_file_dest_size big integer 4G
SYS@PROD> alter system reset db_recovery_file_dest_size scope=spfile sid='*';
System altered.
SYS@PROD> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SYS@PROD> startup;
ORACLE instance started.
Total System Global Area 314572800 bytes
Fixed Size 1219184 bytes
Variable Size 109053328 bytes
Database Buffers 201326592 bytes
Redo Buffers 2973696 bytes
Database mounted.
Database opened.
SYS@PROD> show parameter db_recovery_file_dest_size
NAME TYPE VALUE
------------------------------------ ----------- ----------
db_recovery_file_dest_size big integer 0
6.小结
本文通过实验的方式探索出了一种恢复数据库参数为默认值的方法。请朋友们从原理上去理解这个过程,参数文件的根本作用就是“覆盖参数的默认值”,以便刻画出一个最适合自己应用场景的环境。因此参数文件中记录的都是与默认参数值不一样的内容。因此通过删除pfile参数文件中的的参数,便可达到恢复参数为其默认值的目的。BTW,使用reset方法更加快速便捷。

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

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics











The main role of MySQL in web applications is to store and manage data. 1.MySQL efficiently processes user information, product catalogs, transaction records and other data. 2. Through SQL query, developers can extract information from the database to generate dynamic content. 3.MySQL works based on the client-server model to ensure acceptable query speed.

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.

MySQL is an open source relational database management system, mainly used to store and retrieve data quickly and reliably. Its working principle includes client requests, query resolution, execution of queries and return results. Examples of usage include creating tables, inserting and querying data, and advanced features such as JOIN operations. Common errors involve SQL syntax, data types, and permissions, and optimization suggestions include the use of indexes, optimized queries, and partitioning of tables.

MySQL's position in databases and programming is very important. It is an open source relational database management system that is widely used in various application scenarios. 1) MySQL provides efficient data storage, organization and retrieval functions, supporting Web, mobile and enterprise-level systems. 2) It uses a client-server architecture, supports multiple storage engines and index optimization. 3) Basic usages include creating tables and inserting data, and advanced usages involve multi-table JOINs and complex queries. 4) Frequently asked questions such as SQL syntax errors and performance issues can be debugged through the EXPLAIN command and slow query log. 5) Performance optimization methods include rational use of indexes, optimized query and use of caches. Best practices include using transactions and PreparedStatemen

MySQL is chosen for its performance, reliability, ease of use, and community support. 1.MySQL provides efficient data storage and retrieval functions, supporting multiple data types and advanced query operations. 2. Adopt client-server architecture and multiple storage engines to support transaction and query optimization. 3. Easy to use, supports a variety of operating systems and programming languages. 4. Have strong community support and provide rich resources and solutions.

Compared with other programming languages, MySQL is mainly used to store and manage data, while other languages such as Python, Java, and C are used for logical processing and application development. MySQL is known for its high performance, scalability and cross-platform support, suitable for data management needs, while other languages have advantages in their respective fields such as data analytics, enterprise applications, and system programming.

MySQL is suitable for small and large enterprises. 1) Small businesses can use MySQL for basic data management, such as storing customer information. 2) Large enterprises can use MySQL to process massive data and complex business logic to optimize query performance and transaction processing.

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.
