Three is the number, the number shall be three ...

Might anyone care to wager why a developer at Oracle would use 3 iterations of flushing the shared_pool during execution of the jserver.sql script in creation of the JServer subsequent to database creation?

Possible reasons:

1. Developer is a Huge Monty Python fan.
2. 4 isn't prime
3. 42 was deemed to be excessive
4. 1 and 2 iterations were simply no enough - tested and 4th iteration gained nothing.

Its not like its a routine where the code examines v$sgastat or anything. Its just 3 statements.

158 dbms_output.put_line('flush shared_pool');

159  execute immediate 'alter system flush shared_pool';
160  execute immediate 'alter system flush shared_pool';
161  execute immediate 'alter system flush shared_pool';

humorous comments appreciated.

Paul

btw - 10.1.0.3 Std Ed / w2k adv svr sp4

--
http://www.freelists.org/webpage/oracle-l