Hi Jeff! I already have such a script in my SQLPATH, I have posted it
here already. It's not very hard to make. I could have even written it
in PL/SQL, in which case I would not need to spool. Just a simple cursor
FOR loop with "EXECUTE IMMEDIATE" in the body and we're done. And that
also fixes security problems: grant 'ALTER SYSTEM' to the procedure and
grant the procedure to the DBA role. This is not a hard thing to make.
Niall's suggestion about building a random serial killer into SQLcl is
much harder to implement but would be very funny to use. Does anyone
here remember "xmelt" and "xflip" programs that were used to check
whether someone has left his X11 display open to public? Unfortunately,
the security has tightened these days so "xhost +" is no longer a
default. I've had some innocent fun with xmelt. I was able to convince a
junior system administrator, no less, to go to his seniors and ask for
the screen that is not melting. That was in the environment that was
much less PC than today, when the people knew what have the Romans ever
done for us. And his seniors continued to play the game and told him to
put X11 manual under the 23" CRT screen which has weighed a good 100 LBS
and see whether that will stop melting. In the mean time, he was told to
re-read the corporate standard for the logging script.
Regards
On 11/22/19 9:33 AM, Jeff Smith wrote:
We’ll of course need a
Are you sure?
Are you really, really sure?
And then someone will still complain they murdered the wrong person.
