Skip to main content

Useful Oracle Queries

Sometimes we need to find the indexes present for a table or the table structure or db links present etc. To find these details we have some standard DB queries which gives us the required results. The following queries are applicable to only Oracle database.

SELECT * FROM ALL_TABLES  

The following query lists out all the tables present in the database. If you want search a particular table we can use it in the following way

SELECT * FROM ALL_TABLES WHERE TABLE_NAME LIKE '%emp%'

SELECT * FROM ALL_TAB_COLUMNS

This query list out all the columns. If we want to know a particular column is present in which all tables we can frame the query in the following way

SELECT * FROM ALL_TAB_COLUMNS WHERE COLUMN_NAME='ID';

SELECT * FROM ALL_DB_LINKS

This query will return the list of db links present in the database

SELECT * FROM ALL_INDEXES

This query will list out all the indexes present in the database.If we want to find the indexes present for a particular table we can frame the query in the following way

SELECT * FROM ALL_INDEXES WHERE TABLE_NAME='EMP'

If we want to find the DDL of an index we can use the following query

       Select Dbms_Metadata.Get_Ddl
       ( 'INDEX'
       , Index_Name
       , Owner
       )
       From   All_Indexes
       Where  Table_Name  = '<your table>'
      And    Table_Owner = '<your table owner>'
;

SELECT * FROM V$SESSION_LONGOPS

This query will list out all the long running queries that are currently being executed

SELECT * FROM V$LOCKED_OBJECT

This query will list out the all the locked objects list in the database

SELECT * FROM ALL_VIEWS

This query will list out all the views in the database

SELECT * FROM ALL_CONSTRAINTS

This query will list out all the constraints in the database

Hope this article helps you in your oracle working environment


Comments

Popular posts from this blog

Comparing Objects in Informatica

We might face a scenario where there may be difference between PRODUCTION v/s SIT version of code or any environment or between different folders in same environment. In here we go for comparison of objects we can compare between mappings,sessions,workflows In Designer it would be present under "Mappings" tab we can find "Compare" option. In workflow manger under "Tasks & Workfows" tab we can find "Compare" option for tasks and workflows comparison respectively. However the easiest and probably the best practice would be by doing using Repository Manager.In Repository Manager under "Edit" tab we can find "Compare" option. The advantage of using Repository manager it compares all the objects at one go i.e. workflow,session and mapping. Hence reducing the effort of individually checking the mapping and session separately. Once we select the folder and corresponding workflow we Can click compare for checking out

Finding Duplicate records and Deleting Duplicate records in TERADATA

Requirement: Finding duplicates and removing duplicate records by retaining original record in TERADATA Suppose I am working in an office and My boss told me to enter the details of a person who entered in to office. I have below table structure. Create Table DUP_EXAMPLE ( PERSON_NAME VARCHAR2(50), PERSON_AGE INTEGER, ADDRS VARCHAR2(150), PURPOSE VARCHAR2(250), ENTERED_DATE DATE ) If a person enters more than once then I have to insert his details more than once. First time, I inserted below records. INSERT INTO DUP_EXAMPLE VALUES('Krishna reddy','25','BANGALORE','GENERAL',TO_DATE('01-JAN-2014','DD-MON-YYYY')) INSERT INTO DUP_EXAMPLE VALUES('Anirudh Allika','25','HYDERABAD','GENERAL',TO_DATE('01-JAN-2014','DD-MON-YYYY')) INSERT INTO DUP_EXAMPLE VALUES('Ashok Vunnam','25','CHENNAI','INTERVIEW',TO_DATE('01-JAN-2014',

Target Load Type - Normal or Bulk in Session Properties

We can see the Target load type ( Normal or Bulk) property in session under Mapping tab and we will go for Bulk to improve the performance of session to load large amount of data. SQL loader utility will be used for Bulk load and it will not create any database logs(redolog and undolog), it directly writes to data file.Transaction can not be rolled back as we don't have database logs.However,Bulk loading is very as compared to Normal loading. In target if you are using Primary Key or Primary Index or any constraints you can't use Bulk mode. We can see this property in the below snap shot.