update : 28-06-2017

DBA Script : temp_sort_users.sql

-- | FILE : temp_sort_users.sql |
-- +----------------------------------------------------------------------------+
-- | |
-- | |
-- | www.high-oracle.com |
-- |----------------------------------------------------------------------------|
-- | www.high-oracle.com |
-- |----------------------------------------------------------------------------|
-- | DATABASE : Oracle |
-- | FILE : temp_sort_users.sql |
-- | CLASS : Temporary_Tablespace |
-- | PURPOSE : List all temporary tablespaces and the users performing sorts. |
-- | The statistics will come from the v$sort_usage view which shows |
-- | currently active sorts for the instance. Joining "v$sort_usage" |
-- | to "v$session" will provide the user who is performing a sort |
-- | within the sort segment. |
-- | The CONTENTS column shows whether the segment is created in a |
-- | temporary or permanent tablespace, however, unless you are |
-- | using Oracle8, this should always be temporary. |
-- | This script is RAC enabled. |
-- | NOTE : As with any code, ensure to test this script in a development |
-- | environment before attempting to run it in production. |
-- +----------------------------------------------------------------------------+
SET TERMOUT OFF;
COLUMN current_instance NEW_VALUE current_instance NOPRINT;
SELECT rpad(instance_name, 17) current_instance FROM v$instance;
SET TERMOUT ON;
PROMPT
PROMPT +------------------------------------------------------------------------+
PROMPT | Report : Temporary Sort Users |
PROMPT | Instance : ¤t_instance |
PROMPT +------------------------------------------------------------------------+
SET ECHO OFF
SET FEEDBACK 6
SET HEADING ON
SET LINESIZE 180
SET PAGESIZE 50000
SET TERMOUT ON
SET TIMING OFF
SET TRIMOUT ON
SET TRIMSPOOL ON
SET VERIFY OFF
CLEAR COLUMNS
CLEAR BREAKS
CLEAR COMPUTES
COLUMN instance_name FORMAT a8 HEADING 'Instance'
COLUMN tablespace_name FORMAT a15 HEADING 'Tablespace Name'
COLUMN sid FORMAT 99999 HEADING 'SID'
COLUMN serial_id FORMAT 99999999 HEADING 'Serial ID'
COLUMN session_status FORMAT a9 HEADING 'Status'
COLUMN oracle_username FORMAT a18 HEADING 'Oracle User'
COLUMN os_username FORMAT a18 HEADING 'O/S User'
COLUMN os_pid FORMAT a8 HEADING 'O/S PID'
COLUMN session_terminal FORMAT a10 HEADING 'Terminal' TRUNC
COLUMN session_machine FORMAT a30 HEADING 'Machine' TRUNC
COLUMN session_program FORMAT a20 HEADING 'Session Program' TRUNC
COLUMN contents FORMAT a9 HEADING 'Contents'
COLUMN extents FORMAT 999,999,999 HEADING 'Extents'
COLUMN blocks FORMAT 999,999,999 HEADING 'Blocks'
COLUMN bytes FORMAT 999,999,999,999 HEADING 'Bytes'
COLUMN segtype FORMAT a12 HEADING 'Segment Type'
BREAK ON instance_name SKIP PAGE
SELECT
i.instance_name instance_name
, t.tablespace tablespace_name
, s.sid sid
, s.serial# serial_id
, s.status session_status
, s.username oracle_username
, s.osuser os_username
, p.spid os_pid
, s.program session_program
, t.contents contents
, t.segtype segtype
, (t.blocks * c.value) bytes
FROM
gv$instance i
, gv$session s
, gv$process p
, gv$sort_usage t
, (select value from v$parameter
where name = 'db_block_size') c
WHERE
s.inst_id = p.inst_id
AND p.inst_id = i.inst_id
AND t.inst_id = i.inst_id
AND s.inst_id = i.inst_id
AND s.saddr = t.session_addr
AND s.paddr = p.addr
ORDER BY
i.instance_name
, s.sid;

End Script

Oracle Database Error Messages



Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.