I need examples of complete schedules (all transactions must be either
committed or aborted) for all these areas:
a. Recoverable but not ACA (avoid cascading aborts).
b. ACA but not strict.
c. Recoverable but not conflict serializable.
d. View serializable but not conflict serializable.

Hello Eksolutions,

Perhaps the best answer to your question is the answer to #2 at
  http://www.cse.unsw.edu.au/~cs9315/ass/ass3solution.html
which clearly lists responses to
  a - #12 listed as "...it is recoverable, but not avoid cascading
aborts, not strict"
  b - #1 listed as "It is recoverable and avoid cascading aborts; not
strict"
  c - #11 listed as "It is ... not conflict-serializable; it is
recoverable..."
  d - #6 listed as "It is serializable and view-serializable, not
conflict-serializable"

The examples I listed are four of 12 problems / solutions for this
particular question with a variety of combinations of these
characteristics.

To search for further examples, a phrase like
  database conflict view serializable avoid cascading aborts
provides a number of other references. 

  --Maniac