SQL to monitor sessions in an Oracle database

Here is a SQL script that you can use to monitor Oracle database sessions:

-- Query to monitor Oracle database sessions SELECT s.sid, s.serial#, s.username, s.status, s.machine, s.program, s.osuser, s.process, s.logon_time FROM v$session s WHERE s.type = 'USER' ORDER BY s.logon_time ASC;

This script queries the v$session view, which contains information about all the sessions currently connected to the database. The WHERE clause filters the rows to show only user sessions, and the ORDER BY clause sorts the results by logon time in ascending order.

The columns in the v$session view include:

  • sid: the session ID of the session
  • serial#: the serial number of the session
  • username: the username of the user connected to the session
  • status: the status of the session (e.g. ACTIVE, INACTIVE)
  • machine: the name of the machine from which the session is connected
  • program: the name of the program connected to the session
  • osuser: the operating system user associated with the session
  • process: the process ID of the session
  • logon_time: the time at which the session was established

You can modify this script to include other columns from the v$session view, or add additional filters to the WHERE clause to narrow down the results.

Comments

Post a Comment

Popular posts from this blog

Auditing user logon and logoff in Oracle

To track when a user logs on or off Oracle, enable auditing and audit CONNECT in your database.  Then you can query DBA_AUDIT_TRAIL to find logon and logoff info. alter session SET NLS_DATE_FORMAT = 'DD-MM-YYYY HH24:MI:SS'; select username, action,action_name,timestamp,logoff_time from dba_audit_trail where action_name = 'LOGON' and username = '&user'; Here are some more helpful links: http://itechshare.blogspot.com/2010/06/oracle-how-to-track-logon-logout-in.html http://itechshare.blogspot.com/2010/06/oracle-why-dbaaudittrail-shows-more.html
Read more

RMAN Restore vs. Recovery - what's the difference?

RESTORE is used to restore the datafiles from a backup. You can restore up to the time of the backup or a point before using SET UNTIL . You would lose any changes made to the database after the backup by performing only a RESTORE. RECOVER is used to roll the database forward after a RESTORE by applying the redo logs. In essence, RECOVER = RESTORE + redo logs. The following example assumes you have lost your control files and datafiles, but still have your redo logs. $ rman target / nocatalog RMAN> startup nomount; RMAN> restore controlfile from '/oback/controlfile'; RMAN> alter database mount; RMAN> restore database; RMAN> recover database; RMAN> alter database open resetlogs;
Read more

Use rsync on Unix to backup your archive logs

Rsync is a useful Unix tool for keeping directories in synch between two server.  I use it to copy Oracle archive logs from a production server to a test server. This command runs on my test server from the oracle user's crontab every 5 minutes.  It copies the files via SSH.  New files from the source directory are copied to the test backup directory.  If a file is deleted from the source directory, it is NOT removed from the target directory.  I have it setup this way because I want to control that manually.  I have a separate cronjob that purges archive log files over 3 days old. rsync -rave "ssh -l oracle" sourceServer:/u06/oradata/PROD/arch  /u06/oradata/prodArchBkp Rsync also preserves the timestamp of the source file in the target directory. You can also use rsync to delete files in the target directory that do not exist in the source directory. rsync -rave "ssh -l oracle" --delete sourceServer:/u06/oradata/PROD/arch  /u06/oradata/pr
Read more