Creating tablespace in Oracle

Permanent tablespace

create tablespace ts_something
  logging
  datafile '/dbf1/ts_sth.dbf' 
  size 32m 
  autoextend on 
  next 32m maxsize 2048m
  extent management local;

create tablespace data datafile '/home/oracle/databases/ora10/data.dbf'
size                                  10M
autoextend on maxsize                200M
extent management local uniform size  64K;

Killing Oracle Sessions

This is something I can never remember off the top of my head. So here we go:
Credit: http://www.oracle-base.com/articles/misc/KillingOracleSessions.php

Identify the Session to be Killed

Killing sessions can be very destructive if you kill the wrong session, so be very careful when identifying the session to be killed. If you kill a session belonging to a background process you will cause an instance crash.

Identify the offending session using the V$SESSION or GV$SESSION view as follows.

SET LINESIZE 100
COLUMN spid FORMAT A10
COLUMN username FORMAT A10
COLUMN program FORMAT A45

SELECT s.inst_id,
       s.sid,
       s.serial#,
       p.spid,
       s.username,
       s.program
FROM   gv$session s
       JOIN gv$process p ON p.addr = s.paddr AND p.inst_id = s.inst_id
WHERE  s.type != 'BACKGROUND';

   INST_ID        SID    SERIAL# SPID       USERNAME   PROGRAM
---------- ---------- ---------- ---------- ---------- ---------------------------------------------
         1         30         15 3859       TEST       sqlplus@oel5-11gr2.localdomain (TNS V1-V3)
         1         23        287 3834       SYS        sqlplus@oel5-11gr2.localdomain (TNS V1-V3)
         1         40        387 4663                  oracle@oel5-11gr2.localdomain (J000)
         1         38        125 4665                  oracle@oel5-11gr2.localdomain (J001)

SQL>

The SID and SERIAL# values of the relevant session can then be substituted into the commands in the following sections.

ALTER SYSTEM KILL SESSION

The basic syntax for killing a session is shown below.

SQL> ALTER SYSTEM KILL SESSION 'sid,serial#';

In a RAC environment, you optionally specify the INST_ID, shown when querying the GV$SESSION view. This allows you to kill a session on different RAC node.

SQL> ALTER SYSTEM KILL SESSION 'sid,serial#@inst_id';

The KILL SESSION command doesn't actually kill the session. It merely asks the session to kill itself. In some situations, like waiting for a reply from a remote database or rolling back transactions, the session will not kill itself immediately and will wait for the current operation to complete. In these cases the session will have a status of "marked for kill". It will then be killed as soon as possible.

In addition to the syntax described above, you can add the IMMEDIATE clause.

SQL> ALTER SYSTEM KILL SESSION 'sid,serial#' IMMEDIATE;

This does not affect the work performed by the command, but it returns control back to the current session immediately, rather than waiting for confirmation of the kill.

If the marked session persists for some time you may consider killing the process at the operating system level. Before doing this it's worth checking to see if it is performing a rollback. You can do this by running this script (session_undo.sql). If the USED_UREC value is decreasing for the session in question you should leave it to complete the rollback rather than killing the session at the operating system level.

Validation Summary, "Object doesn’t support this property or method" error

This is an issue that I could only came across to on IE7 and not any of the other browsers. Nonetheless, I spent almost a day trying to figure out why my asp.net validators threw "Object doesn’t support this property or method" javascript error everytime a validation failed or in other words, it wanted to show the ValidationSummary.
Here's how to reproduce the issue :

- Attach a validation control to a control, and put a validation summary in the page anywhere.
- Have any control…. any control with ids “pre”, “post”, “first”, “end”, "result", "headerSep" and you’ll get the   java script error when validation summary needs to be updated at the end of validation.


Solution? Just make sure you don't have any controls identified with with "pre", "post", "first", "end", "result", "headerSep". If you do, rename them

Here's more info on this:


http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=408628

How To Implement User Impersonation in ASP.NET

Below is a way to impersonate a certain user with your web app:


      
                    using System.DirectoryServices;
        using System.Runtime.InteropServices;     
  
        public const int LOGON32_LOGON_INTERACTIVE = 2;
        public const int LOGON32_PROVIDER_DEFAULT = 0;
        public const string password = "password";


        public string user = "userName";


        [DllImport("advapi32.dll")]
        public static extern int LogonUserA(String lpszUserName,
            String lpszDomain,
            String lpszPassword,
            int dwLogonType,
            int dwLogonProvider,
            ref IntPtr phToken);
        [DllImport("advapi32.dll", CharSet = CharSet.Auto, SetLastError = true)]
        public static extern int DuplicateToken(IntPtr hToken,
            int impersonationLevel,
            ref IntPtr hNewToken);


        [DllImport("advapi32.dll", CharSet = CharSet.Auto, SetLastError = true)]
        public static extern bool RevertToSelf();


        [DllImport("kernel32.dll", CharSet = CharSet.Auto)]
        public static extern bool CloseHandle(IntPtr handle);



public Boolean ImpersonateUser(string domain, string userName, string password)
        {
            WindowsIdentity tempWindowsIdentity;
            WindowsImpersonationContext impersonationContext;
            IntPtr token = IntPtr.Zero;
            IntPtr tokenDuplicate = IntPtr.Zero;


            if (RevertToSelf())
            {
                if (LogonUserA(userName, domain, password, LOGON32_LOGON_INTERACTIVE,
                    LOGON32_PROVIDER_DEFAULT, ref token) != 0)
                {
                    if (DuplicateToken(token, 2, ref tokenDuplicate) != 0)
                    {


                        tempWindowsIdentity = new WindowsIdentity(tokenDuplicate);
                        impersonationContext = tempWindowsIdentity.Impersonate();
                        if (impersonationContext != null)
                        {
                            CloseHandle(token);
                            CloseHandle(tokenDuplicate);
                            return true;
                        }
                    }
                }
            }
            if (token != IntPtr.Zero)
                CloseHandle(token);
            if (tokenDuplicate != IntPtr.Zero)
                CloseHandle(tokenDuplicate);
            return false;


        }

Missing Windows Authentication provider For IIS 7 on Windows Server 2008

This article is extremely helpful if you're to support IIS 7.0 for your IIS 6.0 application that uses Windows Authentication. Interestingly, IIS 7.0 on Windows 2008 does not come with Windows Authentication, so we have to install it before we deploy the product.

 This is from http://weblogs.asp.net/zroiy/archive/2008/08/17/missing-windows-authentication-provider-for-iis-7-on-windows-server-2008.aspx

In case your Windows Server 2008 machine doesn't include a windows authentication scheme (see image below), do the following

Open up Server Manager (one way to do this is by right clicking the computer node from within the start menu and choosing  Manage). Expend the Roles node. Right click the Web Server (IIS) and choose Add Role Services. You'll get the following wizard, just scroll down a bit and check Windows Authentication under the security node.

If you've done everything right , you should also get the following option in IIS authentication pane. If it doesn't, try running appcmd, or restarting. Here's the appcmd command you should run:
appcmd set config /section:windowsAuthentication /enabled:true