Two questions please

1. Is it true that during role change sometimes the scripts fail with no apparent reason and sometimes they work? In other words it appears to me that log shipping isn't a very stable solution when it comes to changing roles and it might render the secondary database in a permanent, disgraceful Read-only state. On the contrary setting up log shipping between a primary and secondary is straight forward and it works although when you have to add another one there comes the "Add" problem

2. Since log shipping is designed for disaster recovery...I.E. DISASTER strikes and the primary is blown into pieces, for this reason we want to promote the secondary, WHY ON EARTH THERE IS NO DOCUMENTATION ON WHAT TO DO THEN, and BOL assumes that the primary works ooh just fine and lets run this great script to do role change (which fails half the time)?
In other words, I would kindly like to ask what is the process for performing role change if the primary is not present

Thank you for your replies and the time you took to read my message, excuse my aggression but I am frustrated with the documentation and with the software

Thank you once mor
John C.