SOX is about seperation of duties and the creation of procedures to monitor and control same.  Once you have a procedure in place to cover the 'viewing/usage' of an 'SA' type password, and that procedure is documented and repeatable, then you are covered.  One way to get around your immediate issue....is to put the password in an sealed envelope and to maintain a register of when it was created/opened.  If the 'SA' holder is not available, then the register is updated + countersigned, the envelope opened, password used, problem solved, password changed, new envelope created, register updated + countersigned.  Being SOX compliant will be a matter of showing your SOX auditors the register, the current sealed envelope and the process of opening/using/creating a new version.

An IT solution is not always available within SOX.  SOX in fact is not an IT specific process.  Once a clear seperation of duties process exists like above, then you should be SOX compliant.