An excellent choice by the way would be to introduce DBMS_LOCK.SLEEP(5) into a key procedure. If the code is wrapped no-one will be able to easily tell, and when you remove it you can say you simply removed some of the inefficient developers' code and replaced it with your own. Double Kudos!!!