very help full videos specially for Freshers an also I want you to share some more videos or Demo on RMAN Backup an performing Disaster Recovery ... Thanks
When you explain cold backups at 5:50, how do you expect DBA backup to copy all the physical database files and tablespaces for cold backup, Since most Oracle databases use ASM storage for tablespaces, in last 8yrs..? I dont think "cp" copy command can reach ASM files.. and O/S level backup utilities dont reach ASM either.
My database is not coming up and not able to open due to ORA-01157:datafile corruption. errors: ORA-01157: cannot identify/lock data file 22 - see DBWR trace file ORA-01110: data file 22: 'datafile/location' And Assumptions are, 1) DB is non-archive log mode 2) DB is in mount stage 3) no RMAN backup How to recover the datafile by following above assumptions and open the database? Kindly help me out of this.
Good morning Mallik garu, I have L0 backup in +DATA ..can I use this backup and RECOVERY/RESTORE THE DATABASE TO TEST MACHINE WHICH IS NON ASM .DO YOU HAVE ANY VEDIOS PLEASE LET ME KNOW SIR.
No, HOT backup information will not be logged anywhere inside database. This is one time activity that to performed using OS CP command and no need to store this backup information in side database.
Hot DB backup with RMAN *is* recorded in the control files. This allows RMAN to know status of what backups were recently performed, so incremental backups may be handled properly, based on earlier backup runs. This info is also critical for RMAN to allow restore/recovery when the database is not open... and this is one of the reasons that backing up your control files is so important for recovery of everything else with RMAN. The backups are not recorded in Oracles main tablespaces like System or Sysaux, because these are not usable If DB is broken, cannot open, and Oracle is only in mount status. There are some low level admin views to allow SYS DBA to view this control file information with SQL statements. If you are using an RMAN recovery catalog in a separate database, then RMAN backup activities for many servers can also be tracked/recorded there.
thank you, sir, your explanation helps me effortlessly understand RMAN concept and recovery solution
very help full videos specially for Freshers an also I want you to share some more videos or Demo on RMAN Backup an performing Disaster Recovery ... Thanks
Sure definitely more to come in upcoming days
Do you gave any documents on these playlist for all the topics mentioned in playlist. Please share the docs that would be very beneficial for us...
When you explain cold backups at 5:50, how do you expect DBA backup to copy all the physical database files and tablespaces for cold backup, Since most Oracle databases use ASM storage for tablespaces, in last 8yrs..?
I dont think "cp" copy command can reach ASM files.. and O/S level backup utilities dont reach ASM either.
There several ways to copy file from asm storage to file system
My database is not coming up and not able to open due to ORA-01157:datafile corruption.
errors:
ORA-01157: cannot identify/lock data file 22 - see DBWR trace file
ORA-01110: data file 22: 'datafile/location'
And Assumptions are,
1) DB is non-archive log mode
2) DB is in mount stage
3) no RMAN backup
How to recover the datafile by following above assumptions and open the database?
Kindly help me out of this.
Excellent
Very nicely explained 🙏🏻🙏🏻🙏🏻
Good morning Mallik garu,
I have L0 backup in +DATA ..can I use this backup and RECOVERY/RESTORE THE DATABASE TO TEST MACHINE WHICH IS NON ASM .DO YOU HAVE ANY VEDIOS PLEASE LET ME KNOW SIR.
Good explanation.
Glad it was helpful!
One question though! Are hot backup information stored anywhere? Like in the controlfile or any place else!
No,
HOT backup information will not be logged anywhere inside database.
This is one time activity that to performed using OS CP command and no need to store this backup information in side database.
Mallik034 thanks a lot...
Hot DB backup with RMAN *is* recorded in the control files. This allows RMAN to know status of what backups were recently performed, so incremental backups may be handled properly, based on earlier backup runs.
This info is also critical for RMAN to allow restore/recovery when the database is not open... and this is one of the reasons that backing up your control files is so important for recovery of everything else with RMAN.
The backups are not recorded in Oracles main tablespaces like System or Sysaux, because these are not usable If DB is broken, cannot open, and Oracle is only in mount status. There are some low level admin views to allow SYS DBA to view this control file information with SQL statements.
If you are using an RMAN recovery catalog in a separate database, then RMAN backup activities for many servers can also be tracked/recorded there.
why cold backup, not hot backup in the ground rule of backup and recovery? Please explain the reason.
Hi Malik can u upload realtime scenario like error in dataguard and patching
Sure its noted and will make some videos of DR patching
could plz share that ppt
Better to show things practically.
Yeah sure noted