write complete waits.

  • From: Michael Calisi <oracle455@xxxxxxxxx>
  • To: oracle-l@xxxxxxxxxxxxx
  • Date: Thu, 1 Oct 2015 17:44:02 -0400

We been experiencing log file sync as being in the top wait in our AWR top
10. This has been resolved, and now a new wait has surfaced. write complete
waits.

I have notice that when log write complete waits occur a particular sql is
always running. One thing about the sql it goes up against columns of
blob, clob.

Anyone experience sql performance when blob/clob columns are used?

SELECT 0, AOL_STYLE.AOL_STYLE_ID STYLE_ID, NVL(AOL_STYLE_L10N.HEADER,
AOL_STYLE.HEADER) HEADER, NVL(AOL_STYLE_L10N.FOOTER, AOL_STYLE.FOOTER)
FOOTER, AOL_STYLE.STYLESHEET FROM EG_PROPOSAL_TYPE, AOL_STYLE,
CGADMIN.AOL_STYLE_L10N WHERE EG_PROPOSAL_TYPE.GRANTMAKER_ID = :B3 AND
EG_PROPOSAL_TYPE.EG_PROPOSAL_TYPE_ID = :B2 AND
EG_PROPOSAL_TYPE.DONOR_STYLE_ID = AOL_STYLE.AOL_STYLE_ID AND
EG_PROPOSAL_TYPE.GRANTMAKER_ID = AOL_STYLE.GRANTMAKER_ID AND
AOL_STYLE.AOL_STYLE_ID = AOL_STYLE_L10N.AOL_STYLE_ID(+) AND
AOL_STYLE.GRANTMAKER_ID = AOL_STYLE_L10N.GRANTMAKER_ID(+) AND
AOL_STYLE_L10N.LANGUAGE_CODE(+) = :B1 UNION ALL SELECT 1,
AOL_STYLE.AOL_STYLE_ID STYLE_ID, NVL(AOL_STYLE_L10N.HEADER,
AOL_STYLE.HEADER) HEADER, NVL(AOL_STYLE_L10N.FOOTER, AOL_STYLE.FOOTER)
FOOTER, AOL_STYLE.STYLESHEET FROM EG_CONFIGURATION, AOL_STYLE,
CGADMIN.AOL_STYLE_L10N WHERE EG_CONFIGURATION.GRANTMAKER_ID = :B3 AND
EG_CONFIGURATION.DONOR_STYLE_ID = AOL_STYLE.AOL_STYLE_ID AND
EG_CONFIGURATION.GRANTMAKER_ID = AOL _STYLE.GRANTMAKER_ID AND
AOL_STYLE.AOL_STYLE_ID = AOL_STYLE_L10N.AOL_STYLE_ID(+) AND
AOL_STYLE.GRANTMAKER_ID = AOL_STYLE_L10N.GRANTMAKER_ID(+) AND
AOL_STYLE_L10N.LANGUAGE_CODE(+) = :B1 ORDER BY 1

Other related posts: