since I'm still in the state of experiencing a database I would like to
know what mistakes I made some time ago. And as I learned that in Oracle
everything is a table or within one I'm wondering if there is kind of
history table for my SYS commands...
TIA
Marc
You can audit users. (see conceptsguide). When this is configured,
audit trails will be in the table SYS.AUD$ , or in OS files.
Alternatively, I make a personal file ( e.g. notepad file) and write
down the things i do to solve a problem. This helps me to reverse my
actions if needed, to have an overview for others of what i tried to
solve the problem, and to provide fuel for my personal 'nice-to-know'
knowledgebase.
H.
The short answer is: No
One could write some system trigger which logs entries to a table
whenever a DDL command is issued. But out of the box, the functionality
you describe is not available.
HTH,
Brian
--
===================================================================
Brian Peasland
d...@nospam.peasland.net
http://www.peasland.net
Remove the "nospam." from the email address to email me.
"I can give it to you cheap, quick, and good.
Now pick two out of the three" - Unknown
--
Posted via a free Usenet account from http://www.teranews.com
Get PL/SQL Developer from Allround Automations. I have it save my
last 1000 statements for this sort of "oh crap" statement recall if I
need it.
Hello,
thanks all for the ideas. The problem is that I would like to see the
commands from the very beginning (e.g. find out, how a user was created
exactly).
As I like the "web" view I think I will first of all install the perl
DBI driver and wrap the driver around my commands. I like the
"editability" of html-forms... Also I will just have to append the sent
command to some kind of ASCII-text file.
Thanks to all and best wishes for the upcoming weekend (YYYPPPIIEEE)
Marc
If you are using sqlplus on a UNIX system try the non commercial freeware
tool rlwrap. Oracle the Netherlands also installs this tool on training
systems at Oracle courses.
With the up and down arrows of your keyboard you can browse through your
sqlplus history.
Really big mistakes are in the alert log. I thought someone was being
goofy when I saw this (X's added for obscurity):
...
/* OracleOEM */ ALTER TABLESPACE "XXXXXX" ADD DATAFILE '/oradata/XXXX/
xxxxxxx23
.dbf' SIZE 2048000M
...
ORA-1144 signalled during: /* OracleOEM */ ALTER TABLESPACE...
until I saw that there is a bug in OEM that ignores changing the M/K
with the drop down (or something like that).
The lesson being "you" may not be the only one using SYS commands.
jg
--
@home.com is bogus.
http://www.signonsandiego.com/uniontrib/20070904/news_1b4japannet.html
Gints Plivna
http://www.gplivna.eu