Query is slow... Please help

Question

I have view,we are calling this view in the VB application. It is taking 400 seconds to pull the data from this view. I have a proper indexes... Still it is slow. Any one can help me...
CREATE OR REPLACE FORCE VIEW RMSADMIN.V_EQUIPMENT_TYPE_BROWSE
(RECID, PARTNUM, REV_LEV, FC, FC_REV_DISPLAY,
EQP_TYPE_DESC, LOCAL_TOOL, TOOLTYPE, COMPONENTDESC, MOTORSIZE,
POWERTYPE, STAGES, LOBES, MATRIX, CONNECTION,
STABSIZE, SITEID)
AS
SELECT EI.ROWID AS RECID,
NVL(EI.PARTNUM,''),
NVL(EI.REV_LEV,''),
NVL(EI.FC_DISPLAY,''),
NVL(EI.FC_REV_DISPLAY,' ') FC_REV_DISPLAY,
NVL(EI.EQP_TYPE_DESC,''),
NVL(EI.LOCAL_TOOL,''),
NVL(EI.TT_NAME,''),
NVL(MC.DESCRIPTION, '') COMPONENTDESC,
NVL(MS.MOTORSIZE, '') MOTORSIZE,
NVL(MP.MOTORPOWERTYPE, '') POWERTYPE,
NVL(MST.MOTORSTAGES, '') STAGES,
NVL(ML.MOTORLOBES, '') LOBES,
NVL(MM.MATRIXTYPE, '') MATRIX,
NVL(MC.MOTORCONNECTION, '') CONNECTION,
NVL(SS.MOTORSTABSIZE, '') STABSIZE,
EI.SITEID
FROM T_EQP_TYPE_MOTORINFO MI,
T_EQP_TYPE EI,
T_LKP_MOTOR_COMPONENT_TYPE MC,
T_LKP_MOTORSIZE MS,
T_LKP_MOTORPOWERTYPE MP,
T_LKP_MOTORSTAGES MST,
T_LKP_MOTORLOBES ML,
T_LKP_MOTORMATRIXTYPE MM,
T_LKP_MOTORCONNECTION MC,
T_LKP_MOTORSTABSIZE SS
WHERE EI.ID = MI.EQP_type_ID(+) AND
EI.SITEID = MI.EQP_TYPE_SITEID(+) AND
MI.COMPONENTTYPE_ID = MC.MOTOR_COMP_TYPE_ID(+) AND
MI.COMPONENTTYPE_SITEID = MC.MOTOR_COMP_TYPE_SITEID(+) AND
MI.SIZE_ID = MS.ID(+) AND
MI.SIZE_SITEID = MS.SITEID(+) AND
MI.POWERTYPE_ID = MP.ID(+) AND
MI.POWERTYPE_SITEID = MP.SITEID(+) AND
MI.STAGES_ID = MST.ID(+) AND
MI.STAGES_SITEID = MST.SITEID(+) AND
MI.LOBES_ID = ML.ID(+) AND
MI.LOBES_SITEID = ML.SITEID(+) AND
MI.MOTORMATRIX_TYPE_ID = MM.MOTORMATRIX_TYPE_ID(+) AND
MI.MOTORMATRIX_TYPE_SITEID = MM.MOTORMATRIX_TYPE_SITEID(+) AND
MI.CONNECTION_ID = MC.ID(+) AND
MI.CONNECTION_SITEID = MC.SITEID(+) AND
MI.STABSIZE_ID = SS.ID(+) AND
MI.STABSIZE_SITEID = SS.SITEID(+);

Answer 1

Are the statistics on the table up to date? If /*+ FIRST_ROWS */ is improving performance, Oracle is probably not using all the indexes it can in the unhinted query. This is often the case when the CBO has bad statistics to work with and thinks that full table scans are excessively cheap.
Justin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC