English Русский Contacts Site map Add to favorites
Registration
Login
Master braindump list
New braindumps
Submit a dump
Get latest dump
braindumps.com.ua
flame
3COM (7)
Adobe (1)
BEA (1)
Checkpoint (22)
Cisco (20)
Citrix (21)
CIW (15)
Compaq (0)
CompTIA (51)
CWNA (2)
EMC (2)
Exin (4)
GEJOS (4)
HDI (1)
HP (4)
IBM (13)
Juniper (5)
Linux Prof Institute (LPI) (2)
Lotus (11)
Microsoft (2462)
Network Appliance (2)
Novell (16)
Oracle (423)
PLSQL (1)
PMI (5)
SAS (1)
Sun (87)
Teradata (4)
Login:
Password:
RSS feed

Contacts
Certification links
Links
Authorized users can post comments.
Please log in or sign up.

back to list
Back to main forum
Backup and Recovery 

АвторSubject: Q10
written 19 January 2008 10:10   View profile Jonnik  Edit/Delete  Answer  Answer with quotation
Explanation:
NOLOGGING operations affect a standby database environment, because changes in the primary database will not be written into redo logs and will not be applied to the standby database, so the affected data files needs to be copied from the primary to the standby database manually. It's better to avoid NOLOGGING operation usage in a standby database environment.
Incorrect Answers:
1: There is a difference in these two situations.
2: There is no release 0.1.
4: NOLOGGING operations can be used on the primary database only. Changes to the standby database will be applied with physical datafiles copying, not with archived redo log files applying only.
Oracle 8, DBA Certification Exam Guide, Jason S. Couchman, p. 1159
Chapter 24: Oracle8i New Features Topics

Current tread:
back to list

Q10 - Go to question 10:10 19.01.08

back to list
Up ^ gen. 0.084 Server date 05:10 10-01-2009 Developed by Zip © 2006 Up ^
Forum
Start online exam simulation
Master braindump
User braindumps
Main forum
Question comments