.NET/ASP.NET/C#/VB.NET PDF Document SDK

Data dictionary views such as DBA_USERS, ROLE_ROLE_PRIVS, and ROLE_TAB_PRIVS help you find out who the users are and what their privileges are. However, those views don t help you find out what the users are doing in the database right now you need the session-related dynamic views for that. These views are some of the most useful ones you ll be using on a day-to-day basis for monitoring user sessions.

how to print barcode labels with excel data, barcodes excel 2010 free, barcode fonts for excel 2016, barcode font excel free, how to convert number to barcode in excel 2010, barcode excel 2007 freeware, excel formula to generate 8 digit barcode check digit, free online barcode generator excel, excel 2010 barcode font, excel barcode schriftart,

There is an important difference between the cleanup work done during normal object destruction and during finalization. When an object is finalized, it should clean up only native resources. During finalization, you are not allowed to call another finalizable .NET object, because the called object could be finalized already. The order of finalization calls is undetermined. (There is one exception to this rule, which I will discuss later in this chapter.) The wrapper class shown in the following code has two fields: a native handle (hxyz) and a tracking reference to a finalizable object (memberObj). Notice that the destructor cleans up the managed resource and the native resource (it deletes memberObj and calls XYZDisconnect). In contrast to the destructor, the finalization function cleans up only the native resource. public ref class XYZConnection { HXYZ hxyz; AFinalizableObject^ memberObj; public: XYZConnection() : hxyz(::XYZConnect()) { ... } ~XYZConnection() { try { // cleanup managed resources: dispose member variables here delete memberObj; memberObj = nullptr; } finally { // cleanup native resources even if member variables could not be disposed

If you want to find out which of your users has been granted the SYSOPER or the SYSDBA role, you can do so by using the V$PWFILE_USERS view, as follows: SQL> SELECT * FROM V$PWFILE_USERS; USERNAME SYSDBA SYSOPER -------------------------------SYS TRUE TRUE SQL>

The V$SESSION_CONNECT_INFO view shows you the session authentication details for users. The following code details the V$SESSION_CONNECT_INFO view: SQL> DESC V$SESSION_CONNECT_INFO Name Null Type ----------------------------------------- -------- --------------SID NUMBER AUTHENTICATION_TYPE VARCHAR2(26) OSUSER VARCHAR2(30) NETWORK_SERVICE_BANNER VARCHAR2(4000) SQL> The important column is AUTHENTICATION_TYPE, which could hold the following values: Database, if the authentication is through the database OS, if you re using the operating system s external authentication Network, if you re using the network protocol Listing 23-28 shows the contents of the V$SESSION_CONNECT_INFO view.

With this switch combination (-eo) you can also format your output in many ways to show many other options, such as memory size, process age, process CPU time, and so on (On some UNIX systems, you may need to define the UNIX95 variable within the script for the ps -eo command to function properly The UNIX95 variable can be set to anything you d like; it just needs to not be undefined) When specifying the process for our script to monitor, you ll want to use only the command name, as this is what the script will be looking for The second field contains the indicator you want to track.

Listing 23-28. Using the V$SESSION_CONNECT_INFO View SQL> SELECT * FROM V$SESSION_CONNECT_INFO; SID AUTHENTICATION OSUSER NETWORK_SERVICE_BANNER ---------------------------------------------------------------7 DATABASE SYSTEM 8 DATABASE SYSTEM 9 DATABASE salapati Windows NT TCP/IP NT Protocol Adapter for 32-bit Windows: Version 9.2.0.1.0 Production 9 DATABASE salapati Oracle Advanced Security: Encryption service for 32-bit Windows: Version 9.2.0.1.0 Production 9 DATABASE salapati Oracle Advanced Security: crypto-checksumming service for 32bit Windows: Version 9.2.0.1.0 Produ SQL>

The V$SESSION view gives you a wealth of information about the users, including their operating system username, terminal name, whether they re actively executing a transaction or just connected to the database, and how long their connection has been in place. In Oracle Database 10g, the V$SESSION view also contains several wait-related columns such as WAIT_CLASS_ID, WAIT_ CLASS#, WAIT_CLASS, WAIT_TIME, and SECONDS_IN_WAIT.

The V$SESS_IO view provides session I/O statistics. Here are the columns in this view: SQL> DESC V$SESS_IO Name ------------------SID BLOCK_GETS CONSISTENT_GETS PHYSICAL_READS BLOCK_CHANGES CONSISTENT_CHANGES SQL>

The V$SESSION_LONGOPS view shows the status of all operations that run for a long time (more than six seconds in absolute time). The columns SOFAR and TIME_REMAINING indicate how much of the work is done and how long the operation has to go before completing. The following is a sample query using the view: SQL> SELECT sid, opname, sofar,totalwork, 2 start_time, time_remaining 3* FROM V$SESSION_LONGOPS; You can use either the V$SESSION_LONGOPS or V$RECOVERY_PROGRESS view, which is a subview of the former, to monitor the progress of a backup. The following code shows the structure of the V$RECOVERY_PROGRESS view: