Chiappa, é 9i sim, sei que tem apenas statspack. O que acontece é que temos uma rotina que gera o statspack para cada dois períodos (id's) e os armazena em disco, justamente por isso, com um período de retenção de 7 dias. De qualquer forma o statspack não demonstrou nada anormal no período anterior ao sinistro. Mistério continua parte 2. :)
Att,/Regards, Vitor Jr. Infraestrutura / Infrastructure Team Oracle 11g DBA Certified Professional - OCP Oracle Certified Expert, Oracle Real Application Clusters 11g and Grid Infrastructure Administrator - OCE Oracle Database 11g Performance Tuning Certified Expert - OCE Oracle Exadata 11g Certified Implementation Specialist Oracle Certified Associate, MySQL 5 mail, gtalk e msn: vitorj...@gmail.com http://certificacaobd.com.br/ skype: vjunior1981 https://mybizcard.co/vitor.jr.385628 2013/12/30 <jlchia...@yahoo.com.br> > > > Colega, sorry mas SE o seu banco é 9ir2/9.2.08, Como É que vc tirou um > awr/ash dele ??? Isso Não Existe no 9i, sim??? E se foi um statspack, como > nós sabemos a diferença do statspack para o awr/ash é que o statspack só > usa tabelas EM MEMÓRIA, então òbvio Ululante que após um restart vc Não Vai > ver coisa alguyma, siiiimmm ? > Do manual "Oracle9i Database Performance Tuning Guide and Reference" > cap. 21, Using Statspack (ênfase com *s minha) : > > "Running a Statspack Performance Report > > After snapshots are taken, you can generate performance reports. The SQL > scripts that generate the reports prompts you for a beginning snapshot ID, > an ending snapshot ID, and a report name. The Statspack package includes > two reports. > > First, run a Statspack report, SPREPORT.SQL, which is a general > instance health report that covers all aspects of instance performance. > This reports calculates and prints ratios and differences for all > statistics between the two snapshots, similar to the BSTAT/ESTAT report. > After examining the instance report, run a SQL report, SPREPSQL.SQL, > on a single SQL statement (identified by its hash value). The SQL report > only reports on data relating to the single SQL statement. > > Note: > > It is not correct to specify begin and end snapshots where the begin > snapshot and end snapshot were taken from different instance startups. In > other words, ***** the instance must not have been shutdown **** between > the times that the begin and end snapshots were taken. > > This is necessary because the database's dynamic performance tables, > which Statspack queries to gather the data, reside in memory. Hence, > shutting down the database resets the values in the performance tables to > 0. Because Statspack subtracts the begin-snapshot statistics from the > end-snapshot statistics, the resulting output is invalid. If begin and end > snapshots taken between shutdowns are specified in the report, then the > report shows an appropriate error to indicate this. > " > > []s > > Chiappa > >
