Exam 1z0-083 topic 1 question 119 discussion

I think A - C

I think AC. Without commit it might be easy to cause row lock or resource busy.

A for obvious reasons, C mostly for locking issues.

I think AC

A,C no doubt! About Concurrency and Scalability The better your application handles concurrency, the more scalable it is. Concurrency is the simultaneous execution of multiple transactions. Statements within concurrent transactions can update the same data. Concurrent transactions must produce meaningful and consistent results. Therefore, a multiuser database must provide the following: Data concurrency , which ensures that users can access data at the same time. Data consistency, which ensures that each user sees a consistent view of the data, including visible changes from his or her own transactions and committed transactions of other users

I think AD.

This is a difficult question A is definitely correct, no question B - tablespaces are a logical construction, so should have no bearing on application scaling C - I've had to train users to NOT commit transactions, too often, in large jobs. This can't be correct. D - This used to be the answer, with older server architecture (and spinning disks!). I, once, brought a batch job down from 6 hours runtime, to 14 minutes, merely by exporting the main table - and reimporting it back into a single extent (in Oracle 9i). Modern storage arrays shouldn't care so much about this. E - Savepoints don't degrade performance, it's the use of rollback that does. Since BCE can't be the answer, maybe D is the second correct one. So, AD for me.

I think A - D Not C http://www.dba-oracle.com/t_best_oracle_commit_frequency.htm