-

-- ====================================================================================

-- Script Name : unused_objects_report.sql

-- Purpose     : Identify unused or stale objects based on user-defined inactivity days

-- Author      : ChatGPT for Raunak

-- ====================================================================================


SET ECHO OFF

SET LINESIZE 200

SET PAGESIZE 100

SET FEEDBACK OFF

SET VERIFY OFF

SET TRIMSPOOL ON


-- === Accept user input for age threshold ===

ACCEPT v_days NUMBER PROMPT 'Enter number of days to consider an object as UNUSED (e.g., 90): '


-- === Generate timestamped spool file ===

COLUMN spool_file_name NEW_VALUE spool_file

SELECT 'unused_objects_' || TO_CHAR(SYSDATE, 'YYYYMMDD_HH24MISS') || '.lst' AS spool_file_name FROM dual;

SPOOL &spool_file


PROMPT ============================================================================

PROMPT Report: Objects Unused for at least &v_days days

PROMPT ============================================================================


COLUMN OWNER           FORMAT A20

COLUMN OBJECT_NAME     FORMAT A30

COLUMN OBJECT_TYPE     FORMAT A20

COLUMN STATUS          FORMAT A10

COLUMN CREATED         FORMAT A20

COLUMN LAST_DDL_TIME   FORMAT A20

COLUMN SEGMENT_SIZE_MB FORMAT 999,999.99

COLUMN LAST_ANALYZED   FORMAT A20


SELECT

    o.owner,

    o.object_name,

    o.object_type,

    o.status,

    o.created,

    o.last_ddl_time,

    ROUND(NVL(s.bytes, 0)/1024/1024, 2) AS segment_size_mb,

    CASE 

        WHEN o.object_type = 'TABLE' THEN t.last_analyzed 

        ELSE NULL 

    END AS last_analyzed

FROM 

    dba_objects o

LEFT JOIN 

    dba_segments s 

    ON o.owner = s.owner 

    AND o.object_name = s.segment_name 

    AND s.segment_type = o.object_type

LEFT JOIN 

    dba_tab_statistics t 

    ON o.owner = t.owner 

    AND o.object_name = t.table_name 

    AND o.object_type = 'TABLE'

WHERE 

    o.owner NOT IN ('SYS', 'SYSTEM', 'SYSMAN', 'DBSNMP')

    AND o.object_type IN ('TABLE', 'INDEX', 'VIEW', 'MATERIALIZED VIEW')

    AND (

        o.last_ddl_time < SYSDATE - &v_days

        OR (o.object_type = 'TABLE' AND (t.last_analyzed IS NULL OR t.last_analyzed < SYSDATE - &v_days))

    )

    AND (s.bytes IS NULL OR s.bytes = 0 OR s.bytes < 1024*1024) -- < 1 MB

ORDER BY 

    o.owner, o.object_type, o.object_name;


PROMPT ============================================================================

PROMPT Done. Report saved to &spool_file

PROMPT ============================================================================

SPOOL OFF


Popular posts from this blog

-
Image
How to shutdown a Single Instance Database in Oracle 19c Overview Shutdown is an operation performed when a command is issued by the Administrator to bring down the Database or when it receives a signal to bring down the Database incase of a failure/malfunction or due to SHUTDOWN ABORT comm and execution. The options used by t he Administrator to bring down the Database is called as Shutdown Modes and the Database Server follows a sequence to shutdown a Database . Let's check how does that happen. Concepts The following are the shutdown Modes. Shutdown Modes A database administrator with SYSDBA or SYSOPER privileges can shut down the database using the SQL*Plus SHUTDOWN command or Enterprise Manager. The SHUTDOWN command has the following options that determine the shutdown behavior. Now let's look into each SHUTDOWN option in detail. SHUTDOWN ABORT  This mode is used for emergency situations, such as when shutdown with "IMMEDIATE" option doesn't work. This mode o...
Read more
-
How to startup a Single Instance Database in Oracle 19c Overview An Oracle Database goes through various stages until it is made available to the users. They are categorized into the below stages. Concepts The following are the stages of the startup sequence. Nomount   The instance is started, but is not yet associated with a database. The stages are as follows:  1. Searches for a server parameter file in a platform-specific default location and, if not found, for a text initialization parameter file (specifying STARTUP with the SPFILE or PFILE parameters overrides the default behavior)  2. Reads the parameter file to determine the values of initialization parameters  3. Allocates the SGA based on the initialization parameter settings  4. Starts the Oracle background processes  5. Opens the alert log and trace files and writes all explicit parameter settings to the alert log in valid parameter syntax At this stage, no database is associated with the instanc...
Read more
-
 SET LINES 150 SET PAGES 1000 SET VERIFY OFF SET FEEDBACK OFF SET HEADING ON SET TRIMSPOOL ON SET LONG 10000 SET LONGCHUNKSIZE 10000 PROMPT =================================================== PROMPT       Oracle RAC Session Monitor - Full Version PROMPT =================================================== -- Step 1: Input Method PROMPT Choose input method: PROMPT Enter 'U' for Username or 'S' for SID/SERIAL# ACCEPT input_method CHAR DEFAULT 'U' -- Variables Initialization DEFINE sid = '' DEFINE serial = '' DEFINE instid = 1 DEFINE username = '' DEFINE sqlid = '' PROMPT -- Step 2: If Username mode, accept username and list sessions PROMPT Enter Username (leave blank if using SID/SERIAL#): ACCEPT username CHAR COLUMN inst_id_col NEW_VALUE instid COLUMN sid_col NEW_VALUE sid COLUMN serial_col NEW_VALUE serial SELECT inst_id, sid, serial#, status, program, module, sql_id, event FROM gv$session WHERE username = UPPER('&username...
Read more