by issuing "alter tablespace begin backup;" what happens to
tablespace?
Answers were Sorted based on User's Feedback
Answer / kittu
by issuing above statement it freezes tablespace it won't
allow single transaction to datafile. by this time redologs are generated & excessive redologs also
| Is This Answer Correct ? | 7 Yes | 3 No |
Answer / ravindra
When alter tablespace begin backup?
Ans:Oracle will write all changes to the datafile by rising
checkpoint and freezes the datafile header with latest SCN.
and backup will take upto latest SCN and transactions are
updating to datafiles also changes will be generate many
archivelogs because all changed transactions information
written to Redologs.
| Is This Answer Correct ? | 1 Yes | 0 No |
Answer / naveen
when u place a tablespace/database in backup (restore) mode(usually it's better idea to place only one tablespace at a time, as more logging is written, it should be done during a low activity period. And for the same reason, it is better to place the tablespaces one after one instead of putting all the tablespaces in backup mode)
when u alter the tablespace in begin backup mode - The datafile header is frozen so that whenever tablespace/datafile is copied, it reflects the checkpointSCN that was at the beginning of the backup. Then, when the copy will be restored, Oracle knows that it needs to start recovery at that SCN to apply the archived redo logs.This is to avoid the header inconsistency issue.That means that any further checkpoints do not update the datafile header SCN (but they do update a 'backup' SCN).
Each first modification to a block in buffer cache will write the full block into the redolog (in addition to the default behaviour that writes only the change vector).
At checkpoint the datafile header SCN is not updated - when updating a block, the first time it is updated since it came in the buffer cache,the whole before image of the block is recorded in redo- direct path writes do not go through the buffer cache, but they always write full blocks and then full block is written to redo log (if not in nologging)
This is to avoid the fractured block issue. There may be a fractured block in the copy, but it will be overwritten during the recovery with the full block image.
| Is This Answer Correct ? | 1 Yes | 0 No |
Answer / suman
alter tablespace begin backup; it means we can take the
backup of tablespace in hotbackup begin backup mode will be
start
| Is This Answer Correct ? | 2 Yes | 3 No |
Answer / kittu
by issuing above statement it freezes tablespace it won't
allow single transaction to datafile
| Is This Answer Correct ? | 1 Yes | 3 No |
Illustrate how to determine the amount of physical CPUs a Unix Box possesses (LINUX and/or Solaris).
Give two examples of how you might determine the structure of the table DEPT.
How do you resize a data file?
How can you tell how much space is left on a given file system and how much space each of the file system's subdirectories take-up?
What are the different sql server versions you have worked on? : sql server DBA
How do you find out from the RMAN catalog if a particular archive log has been backed-up?
Name three advisory statistics you can collect.
what is the difference between off-line back up and on-line back up in ibm db2 udb?
wat is global index and local indes
Give the stages of instance startup to a usable state where normal users may access it.
which background process will run @ the time of creation of catalog database
Explain what partitioning is and what its benefit is.
Oracle (3259)
SQL Server (4518)
MS Access (429)
MySQL (1402)
Postgre (483)
Sybase (267)
DB Architecture (141)
DB Administration (291)
DB Development (113)
SQL PLSQL (3330)
MongoDB (502)
IBM Informix (50)
Neo4j (82)
InfluxDB (0)
Apache CouchDB (44)
Firebird (5)
Database Management (1411)
Databases AllOther (288)