####### Erros previstos:
No asm:
SQL> startup;
ORA-01078: failure in processing system parameters
ORA-29701: unable to connect to Cluster Synchronization Service
executar o comando abaixo:
cd $ORACLE_HOME/bin
./crsctl start resource ora.cssd
quinta-feira, 20 de abril de 2017
terça-feira, 18 de abril de 2017
Verificar Jobs do Oracle
Verificar Jobs do Oracle
desc DBA_SCHEDULER_JOB_RUN_DETAILS ;
SQL> desc DBA_SCHEDULER_JOB_RUN_DETAILS ;
Name Null? Type
----------------------------------------- -------- ----------------------------
LOG_ID NUMBER
LOG_DATE TIMESTAMP(6) WITH TIME ZONE
OWNER VARCHAR2(30)
JOB_NAME VARCHAR2(65)
JOB_SUBNAME VARCHAR2(65)
STATUS VARCHAR2(30)
ERROR# NUMBER
REQ_START_DATE TIMESTAMP(6) WITH TIME ZONE
ACTUAL_START_DATE TIMESTAMP(6) WITH TIME ZONE
RUN_DURATION INTERVAL DAY(3) TO SECOND(0)
INSTANCE_ID NUMBER
SESSION_ID VARCHAR2(30)
SLAVE_PID VARCHAR2(30)
CPU_USED INTERVAL DAY(3) TO SECOND(2)
ADDITIONAL_INFO VARCHAR2(4000)
-- vendo os detalhes das falhas
select *from dba_scheduler_job_RUN_DETAILS where JOB_NAME like 'NOME_DO_JOB';
select job_name,status,error# from DBA_SCHEDULER_JOB_RUN_DETAILS where job_name='NOME_DO_JOB';
-- Identificar Jobs com falhas e agendamentos duplicados.
SET PAGES 999;
SET LINES 999;
SELECT * FROM (
SELECT SCHEMA_USER, BROKEN, SUM(FAILURES) FAILURES, COUNT(1) FROM DBA_JOBS
GROUP BY SCHEMA_USER, BROKEN)
WHERE BROKEN = 'Y' OR FAILURES > 0;
SELECT WHAT FROM DBA_JOBS WHERE BROKEN = 'Y' OR FAILURES > 0;
--Quantidade de falhas
select OWNER,JOB_NAME,FAILURE_COUNT, to_char(LAST_START_DATE,'DD-MM-RRRR HH24:MI:SS') ultima_execucao
from dba_scheduler_jobs where FAILURE_COUNT <>0;
desc DBA_SCHEDULER_JOB_RUN_DETAILS ;
SQL> desc DBA_SCHEDULER_JOB_RUN_DETAILS ;
Name Null? Type
----------------------------------------- -------- ----------------------------
LOG_ID NUMBER
LOG_DATE TIMESTAMP(6) WITH TIME ZONE
OWNER VARCHAR2(30)
JOB_NAME VARCHAR2(65)
JOB_SUBNAME VARCHAR2(65)
STATUS VARCHAR2(30)
ERROR# NUMBER
REQ_START_DATE TIMESTAMP(6) WITH TIME ZONE
ACTUAL_START_DATE TIMESTAMP(6) WITH TIME ZONE
RUN_DURATION INTERVAL DAY(3) TO SECOND(0)
INSTANCE_ID NUMBER
SESSION_ID VARCHAR2(30)
SLAVE_PID VARCHAR2(30)
CPU_USED INTERVAL DAY(3) TO SECOND(2)
ADDITIONAL_INFO VARCHAR2(4000)
-- vendo os detalhes das falhas
select *from dba_scheduler_job_RUN_DETAILS where JOB_NAME like 'NOME_DO_JOB';
select job_name,status,error# from DBA_SCHEDULER_JOB_RUN_DETAILS where job_name='NOME_DO_JOB';
-- Identificar Jobs com falhas e agendamentos duplicados.
SET PAGES 999;
SET LINES 999;
SELECT * FROM (
SELECT SCHEMA_USER, BROKEN, SUM(FAILURES) FAILURES, COUNT(1) FROM DBA_JOBS
GROUP BY SCHEMA_USER, BROKEN)
WHERE BROKEN = 'Y' OR FAILURES > 0;
SELECT WHAT FROM DBA_JOBS WHERE BROKEN = 'Y' OR FAILURES > 0;
--Quantidade de falhas
select OWNER,JOB_NAME,FAILURE_COUNT, to_char(LAST_START_DATE,'DD-MM-RRRR HH24:MI:SS') ultima_execucao
from dba_scheduler_jobs where FAILURE_COUNT <>0;
sexta-feira, 6 de janeiro de 2017
atualizar ASM
instalar o oracle asm na versão do kernel
sudo yum --nogpgcheck install oracleasm-`uname -r`
sudo yum --nogpgcheck install oracleasm-`uname -r`
Assinar:
Postagens (Atom)
-
Verificar Jobs do Oracle desc DBA_SCHEDULER_JOB_RUN_DETAILS ; SQL> desc DBA_SCHEDULER_JOB_RUN_DETAILS ; Name ...
-
1 - TABELA com 50GB na sysaux Motivo - Armazena informações de snapshots do awr (automatic workload repository), que são relativos a relató...
-
Analisando SQL traces em Bancos de Dados Oracle - Parte 1 Fonte: http://www.fabioprado.net/2013/09/analisando-traces-em-bancos-de-da...