logoff triggers I've seen a database that implemented the logic shown at http://www.dba-oracle.com/art_builder_sec_audit.htm that also did not purge the audit trail. The problem with this particular trigger, other than that it probably doesn't do what the author expected or answer the requirements of SOX described at the start of the article, is the use of 7 non-indexed updates to the same large and high volume table in the logoff code one would probably have done. cheers Niall On Fri, Jun 5, 2009 at 4:20 PM, David Cheyne <david.cheyne@xxxxxxxxx> wrote: > Hi list, > > I've been given a server to look at: > > Solaris 10 > 10.2.0.3 EE > > All seems fine with the database and machine, till I try and exit any > command line tools. Both RMAN and SQLPLUS hang (without error) and after > about 2-3 minutes return to the system prompt. No ill effects are seen at > any level. Apps running on the machine have no hangs or performance issues. > Listener log appears clean. > > Your thoughts please. > > Many thanks. > > David Cheyne > B.A.(hons) > > Oracle DBA > > Odd spacing and typos courtesy of my iPhone > -- > //www.freelists.org/webpage/oracle-l > > > -- Niall Litchfield Oracle DBA http://www.orawin.info