[ 2016-08-30 ]

Paralelizando datapump en instancias específicas de un RAC

En un ambiente de RAC,  datapump utiliza todas las instancias disponibles para paralelizar  cuando el parametro cluster=y (default).

Para limitar la cantidad de instancias podemos hacer lo siguiente:

Usar el parametro de DP service_name.

Crear un servicio en la base RAC indicando las instancias que queremos utilizar.
$ srvctl add service -d <DatabaseName> -s nodes_2_3 -a RAC2,RAC3 -r RAC1,RAC4 -P BASIC

Y luego ejecutar datapump con los parametros:
cluster=y service_name=nodes_2_3

Ref: How To Limit The Data Pump Slaves To Only A Handful Of RAC Instances? (Doc ID 1590699.1)

[ 2016-08-19 ]

Gestionando AWR Baselines con DBMS_WORKLOAD_REPOSITORY

Creando una Baseline:

BEGIN
  DBMS_WORKLOAD_REPOSITORY.create_baseline (
    start_snap_id => 10,
    end_snap_id   => 100,
    baseline_name => 'AWR First baseline');
END;
/

NOTE: In 11g, there is a newly introduced procedure DBMS_WORKLOAD_REPOSITORY.CREATE_BASELINE_TEMPLATE that specifies a template for how baselines should be created for future time periods:

BEGIN
DBMS_WORKLOAD_REPOSITORY.CREATE_BASELINE_TEMPLATE (
start_time => to_date('&start_date_time','&start_date_time_format'),
end_time => to_date('&end_date_time','&end_date_time_format'),
baseline_name => 'MORNING',
template_name => 'MORNING',
expiration => NULL ) ;
END;
/

"expiration => NULL" means that this baseline will be kept forever.

Eliminando AWR baseline:

BEGIN
    DBMS_WORKLOAD_REPOSITORY.DROP_BASELINE (baseline_name => 'AWR First baseline');
END;
/

[ 2016-08-16 ]

Errores y bugs relacionados con el LGWR (Log Writer Process)

Algunos issues relacionados con el Log Writer y notas asociadas:

Redo log entries are generated in the redo log buffer of the system global area (SGA). LGWR writes the redo log entries sequentially into a redo log file. If the database has a multiplexed redo log, then LGWR writes the redo log entries to a group of redo log files.

Issues Specific to LGWR

Note 470.1 - Error ORA-00470: LGWR process terminated with error

Note 431246.1 - Pmon terminated instance due to LGWR termination ORA-470

Note 1089733.1 - ORA-00494: enqueue [CF] held for too long (more than 900 seconds); LGWR:Terminating Instance Due to Error 2103

Note 9556189.8 - Bug 9556189 - LGWR hangs for long periods using DNFS - CF waits likely

Note 6193945.8 - Bug 6193945 - High LGWR CPU use and long 'log file sync' latency in RAC

Note 6074620.8 - Bug 6074620 - LGWR unconditionally writes to trace file

Note 5896963.8 - Bug 5896963 - High LGWR CPU and longer "log file sync" with fix for bug 5065930

Note 5118272.8 - Bug 5118272 - Instance crash with ORA-600 [1433], [60] due to lgwr filling up msg blocks (Messages could be for LGWR or ARCH)

Note 813473.1 - LGWR Uses Async I/O Inspite Of Setting _lgwr_async_io=False

Note 1278149.1 - Intermittent Long 'log file sync' Waits, LGWR Posting Long Write Times, I/O Portion of Wait Minima



[ 2016-08-04 ]

Issues relacionados con el controlfile y como resolverlas

A continuación un compilado de notas referidas a issues relacionadas al control file y como resolverlas:

Note 429943.1 Summary Of Bugs On ORA-00600 [2103] Error
Note 1084048.6 ORA-01503, ORA-01161: on Create Controlfile
Note 881082.1 Unable to Restore Controlfile From RMAN Autobackup
Note 1072417.1 Performance Degradation as a Result of 'enq: CF - contention'
Note 1058851.6 EXCESSIVE I/O CONTROLFILE PERFORMANCE PROBLEMS
Note 265599.1 ORA-600 [2130] REPORTED With RMAN RESTORE CONTROLFILE VALIDATE
Note 849071.1 10.2.0.3 Instance Crash With ORA-600 [2103] Error
Note 28045.1 ORA-600 [2103] "Timeout on 'Control file' or 'Checkpoint Progress' Enqueue"
Note 1308378.1 After Upgrade To 11.2.0.2 We Recieve Ora-00245 During Autobackup Of The Controlfile
Note 10317487.8 Bug 10317487 - RMAN controlfile backup fails with ODM error ORA-17500 or ORA-245
Note 9145541.8 Bug 9145541 - OERI[25027]/OERI[4097]/OERI[4000]/ORA-1555 in plugged datafile after CREATE CONTROLFILE in 11g
Note 342696.1 Rman-20033: Control File Sequence# Too Low Rman-20033
Note 1265103.1 RMAN DUPLICATE fails with ORA-600 [KGEADE_IS_0] while creating controlfile



[ 2016-08-03 ]

Notas MOS relacionadas con controlfile

Notas relacionadas con controlfile:

Note 735106.1 How to Recreate a Controlfile
Note 881082.1 Unable to Restore Controlfile From RMAN Autobackup
Note 580414.1 RMAN - How to restore the controlfile using RMAN
Note 345180.1 How to duplicate a controlfile when ASM is involved
Note 329981.1 10gR2 New Feature: Eliminate Control File Re-Creation
Note 305565.1 Persistent Controlfile configurations for RMAN in 9i and 10g
Note 1056057.1 HOW TO MONITOR CONTROLFILE SECTION EXPANSION OVER TIME
Note 1086496.1 HOW DO CIRCULAR CONTROLFILE SECTIONS EXPAND? (LOG HISTORY / ARCHIVED LOG ETC)
Note 470463.1 How To Catalog Backups / Archivelogs / Datafile Copies / Controlfile Copies
Note 403883.1 How To Restore Controlfile From A Backupset Without A Catalog Or Autobackup
Note 406191.1
 Diagnosing ORA-600 [2103] Issues in a NON RAC environment