For this test that always fails, do you specify the Recovery Time Objective (RTO) - is it clear to these juniors what "success" is? I'm assuming it is well defined, but I have a hard time with tests that are setup to fail. Juniors are going to make mistakes - that's why they are juniors and not intermediaries or seniors. Do they have access to a senior level during this test to gauge their input and is that input freely given? I could see sacking a junior for not engaging with team members to make sure they had their bases covered, but not for solely failing to backup redo logs in a final test that even some intermediaries (and maybe a few seniors) would fail. (Granted, I'm probably reading more into your comment than intended and I sincerely apologize if so - I'm just genuinely puzzled by what you posted and I'm sure there's more to it than what you provided - at least I hope so) Regards, Chris On Mon, Feb 10, 2014 at 10:58 AM, Dave Morgan <oracle@xxxxxxxxxxx> wrote: > Hi All, > We probably train 3-4 juniors per year. Our success rate is under > 40%. > > The problem is the mindset. Our basic rule is before you do anything you > must know > "How am I going to return to where I started if something goes wrong?" > > Our training program is 3 months of nothing but database creation, backup > and > recovery, in a test environment. > > The final test is a recovery that we know will fail. If the trainee did > not back up > the redo logs before attempting the recovery then we say "Bye, Bye" > > I do not think experience has anything to do with it. One of our best > intermediates > came to us from a courier job. > > As always YMMV > > Dave > > -- > Dave Morgan > Senior Consultant, 1001111 Alberta Limited > dave.morgan@xxxxxxxxxxx > 403 399 2442 > -- > //www.freelists.org/webpage/oracle-l > > >