在归档日志有丢失的情况下并且数据文件损坏,恢复数据库。 用rman恢复,归档有丢失,恢复到指定的sequence1、在数据库open的情况
在归档日志有丢失的情况下并且数据文件损坏,,恢复数据库。
用rman恢复,归档有丢失,恢复到指定的sequence
1、在数据库open的情况下,做一些操作,确定这些操作所在的归档日志文件
SQL> select group#,sequence#,members,status from v$log;
GROUP# SEQUENCE# MEMBERS STATUS
---------- ---------- ---------- ----------------
1 10 1 ACTIVE
2 11 1 CURRENT
3 9 1 ACTIVE
SQL> show user;
USER is "HAOZG"
SQL> create table test11(name varchar2(10),age number);
Table created.
SQL> insert into test11 values('haozg',28);
1 row created.
SQL> commit;
Commit complete.
SQL> /
Commit complete.
SQL> insert into test11 values('zhangf',29);
1 row created.
SQL> commit;
Commit complete.
SQL> alter system switch logfile;
System altered.
SQL> select group#,sequence#,members,status from v$log;
GROUP# SEQUENCE# MEMBERS STATUS
---------- ---------- ---------- ----------------
1 10 1 ACTIVE
2 11 1 ACTIVE
3 12 1 CURRENT
上面做的操作保存在sequence是11的归档日志文件中。
2、做全库备份
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';
sql 'alter system archive log current';
release channel c1;
}2> 3> 4> 5> 6> 7>
using target database control file instead of recovery catalog
allocated channel: c1
channel c1: SID=44 device type=DISK
Starting backup at 01-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 01-JUL-12
channel c1: finished piece 1 at 01-JUL-12
piece handle=+DGASM/backup/haozg/ctl_ora11_41 tag=TAG20120701T101120 comment=NONE
channel c1: backup set complete, elapsed time: 00:00:03
Finished backup at 01-JUL-12
Starting backup at 01-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.787470817
channel c1: starting piece 1 at 01-JUL-12
channel c1: finished piece 1 at 01-JUL-12
piece handle=+DGASM/backup/haozg/db_ora11_42_1_787486286 tag=TAG20120701T101126 comment=NONE
channel c1: starting piece 2 at 01-JUL-12
channel c1: finished piece 2 at 01-JUL-12
piece handle=+DGASM/backup/haozg/db_ora11_42_2_787486286 tag=TAG20120701T101126 comment=NONE
channel c1: backup set complete, elapsed time: 00:02:00
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 01-JUL-12
channel c1: finished piece 1 at 01-JUL-12
piece handle=+DGASM/backup/haozg/db_ora11_43_1_787486406 tag=TAG20120701T101126 comment=NONE
channel c1: backup set complete, elapsed time: 00:00:01
Finished backup at 01-JUL-12
sql statement: alter system archive log current
released channel: c1
RMAN>
3、然再做操作,确定所在的归档文件
SQL> select group#,sequence#,members,status from v$log;
GROUP# SEQUENCE# MEMBERS STATUS
---------- ---------- ---------- ----------------
1 13 1 CURRENT
2 11 1 INACTIVE
3 12 1 ACTIVE
SQL> create table test22(name varchar2(10),age number);
Table created.
SQL> insert into test22 values('guany',30);
1 row created.
SQL> commit;
Commit complete.
SQL> alter system switch logfile;
System altered.
SQL> select group#,sequence#,members,status from v$log;
GROUP# SEQUENCE# MEMBERS STATUS
---------- ---------- ---------- ----------------
1 13 1 ACTIVE
2 14 1 CURRENT
3 12 1 ACTIVE
SQL> alter system switch logfile;
System altered.
SQL> /
System altered.
SQL> select group#,sequence#,members,status from v$log;
GROUP# SEQUENCE# MEMBERS STATUS
---------- ---------- ---------- ----------------
1 16 1 CURRENT
2 14 1 ACTIVE
3 15 1 ACTIVE
上面的操作在sequence是13 的归档日志文件中
4、到数据库的归档目录下删除sequence 是13的归档日志文件
[Oracle@ archivelog]$ ls -al
total 9904
drwxr-xr-x 2 oracle oinstall 4096 Jul 1 10:16 .
drwxrwxr-x 12 oracle oinstall 4096 Jun 18 17:04 ..
-rw-r----- 1 oracle oinstall 2560 Jul 1 10:03 1_10_787471195.dbf
-rw-r----- 1 oracle oinstall 20992 Jul 1 10:08 1_11_787471195.dbf
-rw-r----- 1 oracle oinstall 10061312 Jul 1 10:13 1_12_787471195.dbf
-rw-r----- 1 oracle oinstall 18944 Jul 1 10:16 1_13_787471195.dbf
-rw-r----- 1 oracle oinstall 2560 Jul 1 10:03 1_9_787471195.dbf
[oracle@ archivelog]$ mv 1_13_787471195.dbf ../
[oracle@ archivelog]$ ls
1_10_787471195.dbf 1_11_787471195.dbf 1_12_787471195.dbf 1_9_787471195.dbf
[oracle@ archivelog]$ ls -al
total 10168
drwxr-xr-x 2 oracle oinstall 4096 Jul 1 10:20 .
drwxrwxr-x 12 oracle oinstall 4096 Jul 1 10:19 ..
-rw-r----- 1 oracle oinstall 2560 Jul 1 10:03 1_10_787471195.dbf
-rw-r----- 1 oracle oinstall 20992 Jul 1 10:08 1_11_787471195.dbf
-rw-r----- 1 oracle oinstall 10061312 Jul 1 10:13 1_12_787471195.dbf
-rw-r----- 1 oracle oinstall 282624 Jul 1 10:20 1_14_787471195.dbf
-rw-r----- 1 oracle oinstall 3072 Jul 1 10:20 1_15_787471195.dbf
-rw-r----- 1 oracle oinstall 2560 Jul 1 10:03 1_9_787471195.dbf

MySQLviewshavelimitations:1)Theydon'tsupportallSQLoperations,restrictingdatamanipulationthroughviewswithjoinsorsubqueries.2)Theycanimpactperformance,especiallywithcomplexqueriesorlargedatasets.3)Viewsdon'tstoredata,potentiallyleadingtooutdatedinforma

ProperusermanagementinMySQLiscrucialforenhancingsecurityandensuringefficientdatabaseoperation.1)UseCREATEUSERtoaddusers,specifyingconnectionsourcewith@'localhost'or@'%'.2)GrantspecificprivilegeswithGRANT,usingleastprivilegeprincipletominimizerisks.3)

MySQLdoesn'timposeahardlimitontriggers,butpracticalfactorsdeterminetheireffectiveuse:1)Serverconfigurationimpactstriggermanagement;2)Complextriggersincreasesystemload;3)Largertablesslowtriggerperformance;4)Highconcurrencycancausetriggercontention;5)M

Yes,it'ssafetostoreBLOBdatainMySQL,butconsiderthesefactors:1)StorageSpace:BLOBscanconsumesignificantspace,potentiallyincreasingcostsandslowingperformance.2)Performance:LargerrowsizesduetoBLOBsmayslowdownqueries.3)BackupandRecovery:Theseprocessescanbe

Adding MySQL users through the PHP web interface can use MySQLi extensions. The steps are as follows: 1. Connect to the MySQL database and use the MySQLi extension. 2. Create a user, use the CREATEUSER statement, and use the PASSWORD() function to encrypt the password. 3. Prevent SQL injection and use the mysqli_real_escape_string() function to process user input. 4. Assign permissions to new users and use the GRANT statement.

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


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

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

Dreamweaver CS6
Visual web development tools

ZendStudio 13.5.1 Mac
Powerful PHP integrated development environment

VSCode Windows 64-bit Download
A free and powerful IDE editor launched by Microsoft

WebStorm Mac version
Useful JavaScript development tools
