How to audit failed login attempts in Oracle

I just copy the article from Mr Messin's blog.

You must set the audit_trail=DB in the init.ora/spfile
then you must audit with audit session whenever not successful ;
Here is a complete walk through on the setup and a script that will help query the audit trail for the failed login attempts. Be sure to clean up you audit trail so it does not grow out of control.

The Example Walk Through for Setup:

SQL> connect sys as sysdba
Enter password: ******
Connected.
SQL> alter system set audit_trail=DB scope=spfile ;

System altered.

SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup ;
ORACLE instance started.

Total System Global Area 612368384 bytes
Fixed Size 1250428 bytes
Variable Size 234883972 bytes
Database Buffers 369098752 bytes
Redo Buffers 7135232 bytes
Database mounted.
Database opened.
SQL> audit session whenever not successful ;

Audit succeeded.

SQL> connect dummy/dummy
ERROR:
ORA-01017: invalid username/password; logon denied
Warning: You are no longer connected to ORACLE.
SQL> connect sys as sysdba
Enter password: ******
Connected.
SQL> select os_username,
username,
userhost,
to_char(timestamp,'mm/dd/yyyy hh24:mi:ss') timestamp,
returncode
from dba_audit_session
where action_name = 'LOGON'
and returncode > 0
order by timestamp ;

OS_USERNAME
--------------------------------------------------------------------------------
USERNAME
------------------------------
USERHOST
--------------------------------------------------------------------------------TIMESTAMP RETURNCODE
------------------- ----------------
MRMESSIN\Mike Messina
DUMMYWORKGROUP\MRMESSIN
11/08/2007 09:07:54 1017
SQL>

Here is a script that will show you the failed login attempts made to an Oracle Database after your setup.

-----------------------------------------------
-- see_failed_login_attempts.sql
--
-- Michael Messina
--
-- query the Oracle Audit Trail and
-- will write a log file of the failed
-- login attempts for the database.
--
-- Requires:
-- audit_trail=DB in init.ora/spfile
-- audit session whenever not successful ;
-----------------------------------------------
set pagesize 200
set linesize 150
column os_username format a15
column username format a15
column userhost format a40
column timestamp format a20
column returncode format 9999999999

spool failed_login_attempts.log

select os_username,
username,
userhost,
to_char(timestamp,'mm/dd/yyyy hh24:mi:ss') timestamp,
-- action_name,
returncode
from dba_audit_session
where action_name = 'LOGON'
and returncode > 0
order by timestamp ;

spool off

How to spool to a single file in SQL Plus

The team wants my scripts to spool to one log file so it is easier to verify. I found the following from Oracle Forum.

For UNIX or Linux.

spool temp.txt
your_sql;
spool off
host cat temp.txt >> your_file.txt
host rm temp.txt

For Windows.

spool temp.txt
your_sql;
spool off
host type temp.txt >> your_file.txt
host del temp.txt

Finally I can see some data

It is real fun that when you see the tool shows you some data after putting some efforts into the site. That is my way to test out the sites visibility.

To improve the visibility of your website, there are several points you have to verify:

First of all, the on page factors. These are basic stuffs that you have to look at. If you optimize them, you have a good foundation. However, that doesn't means you will rank high by doing these basic things. Because most of the websites have done that already. If you don't do, you won't be ranked even with tons of other efforts.

Secondly, you have to pick good keywords, that can drive you traffic and profits. That sounds easy, but not that simply as you thought. High traffic keywords always have higher competitions. What are you going to do?

Last but not the least, back links from other reputation sites. The way google beat yahoo is that google use back links to evaluate a site. So you know how important they are.

In conclusion, we need to check quite some elements to ensure our sites' visibility on the internet.

partitioning in SQL Server 2005

I am working on an assignment of migrating a database from SQL 2000 to 2005. That is not a big deal. But at the mean time, there is a huge table contains orders in the database which I want to partition it. In oracle, we can use redefine package to partition an existing table, this won't be an issue. However, this is SQL Server...so I have to determine what is the best practice...
1)migrate the whole db, create a new partitioned order_new table, move the data to the order_new, rename order to order_old, rename order_new to order.
2)migrate the whole db, use scripts(if there is any) to partition the existing order table.
3)migrate the whole db except the order table, create a partition one on the new server, import the data.(the migration might encounter constraint issues, not a good approach)
4)any other ideas?

my new Site for quality link building

I think the team should focus on building quality links.

About being a good DBA

A set of useful DBA Script is a must have tool.

优化后，排上Google第一了！

没有用lijingtuzhi这个长尾巴，就凭oracle dba coop这几个通用的关键字，也排上第一！