Usamos cookies para medir audiência e melhorar sua experiência. Você pode aceitar ou recusar a qualquer momento. Veja sobre o iMasters.
Pessoal, recentemente 'postei' um topico aqui sobre problema de performance em um banco 10G...Executando o relatorio ADDM, há 2 recomendacoes fortes:FINDING 1: 61% impact (484 seconds)-----------------------------------Database sessions were found waiting for Oracle Resource Manager's active session slots. RECOMMENDATION 1: DB Configuration, 61% benefit (484 seconds) ACTION: Sessions were found waiting for active session slots. Consider increasing the active session limit for these Oracle Resource Manager consumer groups. SYMPTOMS THAT LED TO THE FINDING: SYMPTOM: Wait class "Scheduler" was consuming significant database time. (61% impact [484 seconds])FINDING 2: 57% impact (451 seconds)-----------------------------------SQL statements consuming significant database time were found. RECOMMENDATION 1: SQL Tuning, 47% benefit (372 seconds) ACTION: Investigate the SQL statement with SQL_ID "8s3z8qvt3c12r" for possible performance improvements. RELEVANT OBJECT: SQL statement with SQL_ID 8s3z8qvt3c12r and PLAN_HASH 1388734953 SELECT 'A' FROM DUAL RATIONALE: SQL statement with SQL_ID "8s3z8qvt3c12r" was executed 5178 times and had an average elapsed time of 0.071 seconds. RATIONALE: Waiting for event "resmgr:become active" in wait class "Scheduler" accounted for 92% of the database time spent in processing the SQL statement with SQL_ID "8s3z8qvt3c12r".Alguma dica?
Carregando comentários...