Rogerio Antonio

English Version Neste post escrevo sobre gestao manual do do DOP ( Degree of Parallelism). A gestao do paralelismo pode ser feita manualmente de 3 formas :  1 - Paralelismo ao nivel da Sessao  ALTER SESSION ENABLE | DISABLE | FORCE Parallel QUERY | DML | DDL  2 - Paralelismo ao nivel do Objecto create table my_tab(i number) parallel 5 ; alter table   my_tab p arallel 10 ; select table_name, degree   from dba_tables where table_name = 'INDX_P_5'; -- tabelas particionadas  -  -- aplica- se ano nivel da tabelas  nao das particoes  --  Table IOT  create table my_iot_tab( i parallel key ) organization index parallel; -- index create index indx_p_5 on Tabela (i) Parallel 5 ; alter index indx_p_5 Parallel 10 ; select index_name, degree   from dba_indexes where index_name = 'INDX_P_5'; 3 - Paralelismo Hints * tem precedencia sobre todos as outras opcoes (MANUAL ou AUTO) ...

PT :  Como identificar codigo em uso   EN :  How to identify code currently in use

English Version Neste post partilho algumas queries que usei para monitorizar o processamento de mensagens no RIB. -- find all items queues SQL> select * from user_queues where queue_type = 'NORMAL_QUEUE' and name like '%ITEM%' --- find all items to process SQL> select * from ETITEMSTLFROMRIBTABLE -- queue subscribers SQL> select * from AQ$_ETITEMSTLFROMRIBTABLE_S -- queue historic SQL> select * from AQ$_ETITEMSTLFROMRIBTABLE_H where msgid = 'FE4C339218D830B1E0440024813309CD' --- find all tables/queue tables SQL> select * from dba_tables where table_name like '%ETITEMSTLFROMRIB%' Testar Integracao - RMS > WMS Uma forma facil de testar a integracao (RIB) apos adicionar um novo warehouse (WMS), e actualizar um Item no RMS e validar se as alteracoes estao a ser transmitidas ao WMS, no exemplo seguinte mostro como fazer isso, e os tabelas/queues envolvidas. Item : 101715654 -- RMS DB SQL> select  item, item_desc  from item_master wher...

PT :  RIB -  JMS AQ  EN :  RIB -   JMS AQ

English Version Por vezes e necessario fazer trace a sessao desde inicio, nessas situacoes e util usar um  logon trigger ex: baches de Oracle Retail / RPM / RMS Em seguida partilho tres logon triggers , que podem ser uteis nessas circunstancias, o primeiro usando o hostname do cliente. SQL> drop trigger sys.set_trace_rpm; SQL> create or replace trigger sys.set_trace_rpm after logon on database when (user in ('RPM_OAS')) declare retail_module varchar(200); begin select module into  retail_module from gv$session where sid =  upper(sys_context('userenv','sid')) and (osuser is null and machine like 'rpm_app_server%'); execute immediate 'alter session set statistics_level=all';  execute immediate 'alter session set max_dump_file_size=unlimited';  execute immediate 'alter session set events ''10046 trace name context forever, level 12''';  execute immediate 'alter session set tracefile_identifier=''RA_...

EN Por vezes e necessario fazer trace a sessao desde inicio, nessas situacoes e util usar um  logon trigger ex: baches de rpm PT Sometimes is useful to trace the session from the beginning, for that is useful to use a logon trigger eg RPM batches Code SQL>   SQL>  drop trigger sys.set_trace_rpm; SQL> create or replace trigger sys.set_trace_rpm after logon on database when (user in ('RPM_OAS')) declare retail_module varchar(200); begin select module into  retail_module from gv$session where sid =  upper(sys_context('userenv','sid')) and (osuser is null and machine like 'rpm_app_server%'); execute immediate 'alter session set statistics_level=all';  execute immediate 'alter session set max_dump_file_size=unlimited';  execute immediate 'alter session set events ''10046 trace name context forever, level 12''';  execute immediate 'alter session set tra...

PT  : E a tal query que nao termina .. EN : And about that query that never ends ...

Versao Portuguesa Sometimes is useful to trace the session from the beginning, for that is useful to use a logon trigger eg RPM batches I'm sharing three logon trigger examples to help in that situations, the first one using the client hostname, if you know it.  SQL> drop trigger sys.set_trace_rpm; SQL> create or replace trigger sys.set_trace_rpm after logon on database when (user in ('RPM_OAS')) declare retail_module varchar(200); begin select module into  retail_module from gv$session where sid =  upper(sys_context('userenv','sid')) and (osuser is null and machine like 'rpm_app_server%'); execute immediate 'alter session set statistics_level=all';  execute immediate 'alter session set max_dump_file_size=unlimited';  execute immediate 'alter session set events ''10046 trace name context forever, level 12''';  execute immediate 'alter session set tracefile_identifier=''RA_RPM'''; e...