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方法更加快速便捷。

MySQL'sBLOBissuitableforstoringbinarydatawithinarelationaldatabase,whileNoSQLoptionslikeMongoDB,Redis,andCassandraofferflexible,scalablesolutionsforunstructureddata.BLOBissimplerbutcanslowdownperformancewithlargedata;NoSQLprovidesbetterscalabilityand

ToaddauserinMySQL,use:CREATEUSER'username'@'host'IDENTIFIEDBY'password';Here'showtodoitsecurely:1)Choosethehostcarefullytocontrolaccess.2)SetresourcelimitswithoptionslikeMAX_QUERIES_PER_HOUR.3)Usestrong,uniquepasswords.4)EnforceSSL/TLSconnectionswith

ToavoidcommonmistakeswithstringdatatypesinMySQL,understandstringtypenuances,choosetherighttype,andmanageencodingandcollationsettingseffectively.1)UseCHARforfixed-lengthstrings,VARCHARforvariable-length,andTEXT/BLOBforlargerdata.2)Setcorrectcharacters

MySQloffersechar, Varchar, text, Anddenumforstringdata.usecharforfixed-Lengthstrings, VarcharerForvariable-Length, text forlarger text, AndenumforenforcingdataAntegritywithaetofvalues.

Optimizing MySQLBLOB requests can be done through the following strategies: 1. Reduce the frequency of BLOB query, use independent requests or delay loading; 2. Select the appropriate BLOB type (such as TINYBLOB); 3. Separate the BLOB data into separate tables; 4. Compress the BLOB data at the application layer; 5. Index the BLOB metadata. These methods can effectively improve performance by combining monitoring, caching and data sharding in actual applications.

Mastering the method of adding MySQL users is crucial for database administrators and developers because it ensures the security and access control of the database. 1) Create a new user using the CREATEUSER command, 2) Assign permissions through the GRANT command, 3) Use FLUSHPRIVILEGES to ensure permissions take effect, 4) Regularly audit and clean user accounts to maintain performance and security.

ChooseCHARforfixed-lengthdata,VARCHARforvariable-lengthdata,andTEXTforlargetextfields.1)CHARisefficientforconsistent-lengthdatalikecodes.2)VARCHARsuitsvariable-lengthdatalikenames,balancingflexibilityandperformance.3)TEXTisidealforlargetextslikeartic

Best practices for handling string data types and indexes in MySQL include: 1) Selecting the appropriate string type, such as CHAR for fixed length, VARCHAR for variable length, and TEXT for large text; 2) Be cautious in indexing, avoid over-indexing, and create indexes for common queries; 3) Use prefix indexes and full-text indexes to optimize long string searches; 4) Regularly monitor and optimize indexes to keep indexes small and efficient. Through these methods, we can balance read and write performance and improve database efficiency.


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

SecLists
SecLists is the ultimate security tester's companion. It is a collection of various types of lists that are frequently used during security assessments, all in one place. SecLists helps make security testing more efficient and productive by conveniently providing all the lists a security tester might need. List types include usernames, passwords, URLs, fuzzing payloads, sensitive data patterns, web shells, and more. The tester can simply pull this repository onto a new test machine and he will have access to every type of list he needs.

SublimeText3 English version
Recommended: Win version, supports code prompts!

Safe Exam Browser
Safe Exam Browser is a secure browser environment for taking online exams securely. This software turns any computer into a secure workstation. It controls access to any utility and prevents students from using unauthorized resources.

Dreamweaver CS6
Visual web development tools

Atom editor mac version download
The most popular open source editor
