Oracle procedures scheduled as jobs
From: Fith <pfith_at_ibm.net>
Date: Mon, 12 Apr 1999 13:32:16 +0100
Message-ID: <37123c4b_at_news3.us.ibm.net>
Does anyone know why a procedure that runs from SQL+ (when executed manually) in around 38 minutes without affecting the processor much would max out the processor and take over 6 hours when scheduled as a job (through the enterprise manager)? I'm using version 7.3.3.
Date: Mon, 12 Apr 1999 13:32:16 +0100
Message-ID: <37123c4b_at_news3.us.ibm.net>
Does anyone know why a procedure that runs from SQL+ (when executed manually) in around 38 minutes without affecting the processor much would max out the processor and take over 6 hours when scheduled as a job (through the enterprise manager)? I'm using version 7.3.3.
Thanks. Received on Mon Apr 12 1999 - 14:32:16 CEST