Bugra Canbakal's Oracle Blog

User managed backup ve restore

Bugra Canbakal — Sun, 31 Mar 2013 08:37:53 +0000

1.AMAÇ VE KAPSAM

Bu yazıda user managed backup alıp , bu almış olduğumuz backup’ı restore işlemi uygulayacağız.

2.UYGULAMA

2.1. Tablespacelerin backuplarını cp le alabilmemiz için öncelikle database üstünde tablespacelerin statusunu değiştirmemiz gerekmekte. Tek tek tablespaceleri backup moduna almak yerine “ALTER DATABASE BEGIN BACKUP;” komutunuda kullanabilirsiniz.

[oracle@sb]$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.2.0 Production on Fri Jan 18 10:21:38 2013
Copyright (c) 1982, 2010, Oracle. All rights reserved.
SQL> select 'alter tablespace '||TABLESPACE_NAME||' begin backup;' from SYS.DBA_DATA_FILES;
'ALTERTABLESPACE'||TABLESPACE_NAME||'BEGINBACKUP;'
-------------------------------------------------------------
alter tablespace USERS begin backup;
alter tablespace UNDOTBS1 begin backup;
alter tablespace SYSAUX begin backup;
alter tablespace SYSTEM begin backup;
alter tablespace EXAMPLE begin backup;
alter tablespace MGMT_ECM_DEPOT_TS begin backup;
alter tablespace MGMT_TABLESPACE begin backup;
alter tablespace MGMT_AD4J_TS begin backup;

8 rows selected.

SQL> alter tablespace USERS begin backup; 
Database altered.
SQL> alter tablespace UNDOTBS1 begin backup; 
Database altered.
SQL> alter tablespace SYSAUX begin backup; 
Database altered.
SQL> alter tablespace SYSTEM begin backup; 
Database altered.
SQL> alter tablespace EXAMPLE begin backup; 
Database altered.
SQL> alter tablespace MGMT_ECM_DEPOT_TS begin backup; 
Database altered.
SQL> alter tablespace MGMT_TABLESPACE begin backup; 
Database altered.
SQL> alter tablespace MGMT_AD4J_TS begin backup;
Database altered.

2.2. Şimdide cp scriptimizi hazırlayalım.

SQL> select 'cp '|| FILE_NAME || ' /cloud/backup'||FILE_NAME from SYS.DBA_DATA_FILES;
'CP'||FILE_NAME||'/CLOUD/BACKUP'||FILE_NAME
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
cp /oracle/app/oracle/oradata/dbf12c/users01.dbf /cloud/backup/oracle/app/oracle/oradata/dbf12c/users01.dbf
cp /oracle/app/oracle/oradata/dbf12c/undotbs01.dbf /cloud/backup/oracle/app/oracle/oradata/dbf12c/undotbs01.dbf
cp /oracle/app/oracle/oradata/dbf12c/sysaux01.dbf /cloud/backup/oracle/app/oracle/oradata/dbf12c/sysaux01.dbf
cp /oracle/app/oracle/oradata/dbf12c/system01.dbf /cloud/backup/oracle/app/oracle/oradata/dbf12c/system01.dbf
cp /oracle/app/oracle/oradata/dbf12c/example01.dbf /cloud/backup/oracle/app/oracle/oradata/dbf12c/example01.dbf
cp /oracle/app/oracle/oradata/dbf12c/mgmt_depot.dbf /cloud/backup/oracle/app/oracle/oradata/dbf12c/mgmt_depot.dbf
cp /oracle/app/oracle/oradata/dbf12c/mgmt.dbf /cloud/backup/oracle/app/oracle/oradata/dbf12c/mgmt.dbf
cp /oracle/app/oracle/oradata/dbf12c/mgmt_ad4j.dbf /cloud/backup/oracle/app/oracle/oradata/dbf12c/mgmt_ad4j.dbf

2.3. Yukarda oluşturduğumuz scripti çalıştırıyorum böylelikle tablespacelerin yedeklerini başka bir klasöre almış olacağım.

[oracle@sb]$ cp /oracle/app/oracle/oradata/dbf12c/users01.dbf /cloud/backup/oracle/app/oracle/oradata/dbf12c/users01.dbf
[oracle@sb]$ cp /oracle/app/oracle/oradata/dbf12c/undotbs01.dbf /cloud/backup/oracle/app/oracle/oradata/dbf12c/undotbs01.dbf
[oracle@sb]$ cp /oracle/app/oracle/oradata/dbf12c/sysaux01.dbf /cloud/backup/oracle/app/oracle/oradata/dbf12c/sysaux01.dbf
[oracle@sb]$ cp /oracle/app/oracle/oradata/dbf12c/system01.dbf /cloud/backup/oracle/app/oracle/oradata/dbf12c/system01.dbf
[oracle@sb]$ cp /oracle/app/oracle/oradata/dbf12c/example01.dbf /cloud/backup/oracle/app/oracle/oradata/dbf12c/example01.dbf
[oracle@sb]$ cp /oracle/app/oracle/oradata/dbf12c/mgmt_depot.dbf /cloud/backup/oracle/app/oracle/oradata/dbf12c/mgmt_depot.dbf
[oracle@sb]$ cp /oracle/app/oracle/oradata/dbf12c/mgmt.dbf /cloud/backup/oracle/app/oracle/oradata/dbf12c/mgmt.dbf
[oracle@sb]$ cp /oracle/app/oracle/oradata/dbf12c/mgmt_ad4j.dbf /cloud/backup/oracle/app/oracle/oradata/dbf12c/mgmt_ad4j.dbf

2.4. Tablespacelerin yedeklerini aldığımıza göre backup modu kapatabilirim.

SQL> select 'alter tablespace '||TABLESPACE_NAME||' end backup;' from SYS.DBA_DATA_FILES;
'ALTER TABLESPACE'||TABLESPACE_NAME||' end backup;'
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
alter tablespace USERS end backup;
alter tablespace UNDOTBS1 end backup;
alter tablespace SYSAUX end backup;
alter tablespace SYSTEM end backup;
alter tablespace EXAMPLE end backup;
alter tablespace MGMT_ECM_DEPOT_TS end backup;
alter tablespace MGMT_TABLESPACE end backup;
alter tablespace MGMT_AD4J_TS end backup;
8 rows selected.

SQL> alter tablespace USERS end backup;
Database altered.
SQL> alter tablespace UNDOTBS1 end backup;
Database altered.
SQL> alter tablespace SYSAUX end backup;
Database altered.
SQL> alter tablespace SYSTEM end backup;
Database altered.
SQL> alter tablespace EXAMPLE end backup;
Database altered.
SQL> alter tablespace MGMT_ECM_DEPOT_TS end backup;
Database altered.
SQL> alter tablespace MGMT_TABLESPACE end backup;
Database altered.
SQL> alter tablespace MGMT_AD4J_TS end backup;
Database altered.

2.5. Hali hazırda archivelog’a cevrilmemiş redo logları archivelog a çevirip redo logları boşaltmamız gerekiyor.

SQL> alter system archive log current ;
System altered.

2.6. Control file backupını alıp backup işlemini bitiriyoruz, controlfile’larınızın lokasyonlarını bilmiyorsanız onuda veritabanından sorgulamanız gerekmekte

SQL> alter database backup controlfile to '/cloud/backup/oracle/app/oracle/oradata/dbf12c/control.ctl';
Database altered.

2.7. Veritabanını kapatmadan önce restore işleminde kolaylık sağlaması için bir script daha calıstırıyorum.

SQL> select 'cp /cloud/backup'|| FILE_NAME || ' '||FILE_NAME from SYS.DBA_DATA_FILES;
'CP /CLOUD/BACKUP '||FILE_NAME||' '||FILE_NAME
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
cp /cloud/backup/oracle/app/oracle/oradata/dbf12c/users01.dbf /oracle/app/oracle/oradata/dbf12c/users01.dbf
cp /cloud/backup/oracle/app/oracle/oradata/dbf12c/undotbs01.dbf /oracle/app/oracle/oradata/dbf12c/undotbs01.dbf
cp /cloud/backup/oracle/app/oracle/oradata/dbf12c/sysaux01.dbf /oracle/app/oracle/oradata/dbf12c/sysaux01.dbf
cp /cloud/backup/oracle/app/oracle/oradata/dbf12c/system01.dbf /oracle/app/oracle/oradata/dbf12c/system01.dbf
cp /cloud/backup/oracle/app/oracle/oradata/dbf12c/example01.dbf /oracle/app/oracle/oradata/dbf12c/example01.dbf
cp /cloud/backup/oracle/app/oracle/oradata/dbf12c/mgmt_depot.dbf /oracle/app/oracle/oradata/dbf12c/mgmt_depot.dbf
cp /cloud/backup/oracle/app/oracle/oradata/dbf12c/mgmt.dbf /oracle/app/oracle/oradata/dbf12c/mgmt.dbf
cp /cloud/backup/oracle/app/oracle/oradata/dbf12c/mgmt_ad4j.dbf /oracle/app/oracle/oradata/dbf12c/mgmt_ad4j.dbf

2.8. Artık restore işlemine başlayabiliriz. Veritabanını kapatıyorum,mevcut tablespace&controlfile siliyorum ve backupını almış olduğum tablespace&controlfile ları original lokasyonlarına kopyalıyorum.

SQL> Shutdown abort;
ORACLE instance shut down.
SQL>exit;
[oracle@sb]$ rm -f /oracle/app/oracle/oradata/dbf12c/*
[oracle@sb]$ cp /cloud/backup/oracle/app/oracle/oradata/dbf12c/users01.dbf /oracle/app/oracle/oradata/dbf12c/users01.dbf
[oracle@sb]$ cp /cloud/backup/oracle/app/oracle/oradata/dbf12c/undotbs01.dbf /oracle/app/oracle/oradata/dbf12c/undotbs01.dbf
[oracle@sb]$ cp /cloud/backup/oracle/app/oracle/oradata/dbf12c/sysaux01.dbf /oracle/app/oracle/oradata/dbf12c/sysaux01.dbf
[oracle@sb]$ cp /cloud/backup/oracle/app/oracle/oradata/dbf12c/system01.dbf /oracle/app/oracle/oradata/dbf12c/system01.dbf
[oracle@sb]$ cp /cloud/backup/oracle/app/oracle/oradata/dbf12c/example01.dbf /oracle/app/oracle/oradata/dbf12c/example01.dbf
[oracle@sb]$ cp /cloud/backup/oracle/app/oracle/oradata/dbf12c/mgmt_depot.dbf /oracle/app/oracle/oradata/dbf12c/mgmt_depot.dbf
[oracle@sb]$ cp /cloud/backup/oracle/app/oracle/oradata/dbf12c/mgmt.dbf /oracle/app/oracle/oradata/dbf12c/mgmt.dbf
[oracle@sb]$ cp /cloud/backup/oracle/app/oracle/oradata/dbf12c/mgmt_ad4j.dbf /oracle/app/oracle/oradata/dbf12c/mgmt_ad4j.dbf
[oracle@sb]$ cp /cloud/backup/oracle/app/oracle/oradata/dbf12c/control.ctl /oracle/app/oracle/oradata/dbf12c/control01.ctl
[oracle@sb]$ cp /cloud/backup/oracle/app/oracle/oradata/dbf12c/control.ctl /oracle/app/oracle/oradata/dbf12c/control02.ctl

2.9. Veritabanını açmayı deniyelim.

SQL> startup
ORACLE instance started.
Total System Global Area 2142679040 bytes
Fixed Size 1337720 bytes
Variable Size 671090312 bytes
Database Buffers 1442840576 bytes
Redo Buffers 27410432 bytes
Database mounted.
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SQL> alter database open resetlogs;
alter database open resetlogs
*
ERROR at line 1:
ORA-01195: online backup of file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/oracle/app/oracle/oradata/dbf12c/system01.dbf'

2.10. Veritabanını açmamıza izin vermedi, zaten bende belli bir zaman dilimine kadar restore yapmak istiyordum buyüzden backup’ını almıs oldugumuz controlfile kullanarak restore işlemini yapıyoruz.

SQL> recover database using backup controlfile until time '2013-03-16:10:00:00';
ORA-00279: change 1237645 generated at 03/16/2013 9:25:27 needed for thread 1
ORA-00289: suggestion :
/oracle/app/oracle/flash_recovery_area/DBF12C/archivelog/2013_03_16/o1_mf_1_60_8
o06tyom_.arc
ORA-00280: change 1237645 for thread 1 is in sequence #60
Specify log: {=suggested | filename | AUTO | CANCEL}
auto
ORA-00279: change 1239277 generated at 03/16/2013 9:39:42 needed for thread 1
ORA-00289: suggestion :
/oracle/app/oracle/flash_recovery_area/DBF12C/archivelog/2013_03_16/o1_mf_1_61_8
o071fh4_.arc
ORA-00280: change 1239277 for thread 1 is in sequence #61
ORA-00278: log file
'/oracle/app/oracle/flash_recovery_area/DBF12C/archivelog/2013_03_16/o1_mf_1_60_
8o06tyom_.arc' no longer needed for this recovery
ORA-00308: cannot open archived log
'/oracle/app/oracle/flash_recovery_area/DBF12C/archivelog/2013_03_16/o1_mf_1_62_
%u_.arc'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3

2.11. Ve şimdi veritabanını resetlog kullanarak tekrardan açmaya çalışalım.

SQL> alter database open resetlogs;
Database altered.
SQL> select status from gv$instance ;
STATUS
 ------------
 OPEN

The post User managed backup ve restore appeared first on Bugra Canbakal's Oracle Blog.

Flashback database

Bugra Canbakal — Fri, 18 Jan 2013 12:04:35 +0000

1.AMAÇ VE KAPSAM
Flashback database teknolojisi sayesinde mantiksal yapilmiş olan hataları belirtmiş olduğumuz flashback süresi boyutunda düzeltmemiz mümkün.Flashback database de dönüş işlemini gerçekleştirirken zaman,log sequence veya scn kullanabiliriz.

Not: Disk hatalari veya datafile/redo/controlfile dosyalarin silinmesi gibi fiziksel hatalarda ise bu teknolojiyi kullanamayız.

2.UYGULAMA

2.1. Kapalı olan veritabanıma bağlanıp flashback database özelliğini açıyoruz.

[oracle@sb trace]$ sqlplus / as sysdba

SQL*Plus: Release 11.2.0.2.0 Production on Fri Jan 18 10:21:38 2013

Copyright (c) 1982, 2010, Oracle.  All rights reserved.

Connected to an idle instance.

SQL> startup mount
ORACLE instance started.

Total System Global Area 4.0353E+10 bytes
Fixed Size            2235176 bytes
Variable Size         2.1072E+10 bytes
Database Buffers     1.9193E+10 bytes
Redo Buffers           85233664 bytes
Database mounted.
SQL> alter database flashback on;
Database altered.

2.2. Db_flashback_retention_target süresine bakmamız gerekiyor ,bu parametre default olarak 1140 dk ya ayarlidir bunu 2 gune cekip veritabanını açık posizyona getiriyoruz.

SQL> show parameter flashback

NAME                                 TYPE             VALUE
------------------------------------ ---------------- --------------
db_flashback_retention_target         integer         1440

SQL> alter system set db_flashback_retention_target=2880;

System altered.

SQL> alter database open;

Database altered.

2.3. 1000 row lu dummy bir tablo oluşturuyorum.

 CREATE TABLE bcanbakal.table_x 
as select * from dba_objects where rownum < 1001;    Table created. SQL> select count(1) from bcanbakal.table_x;

  COUNT(1)
----------
      1000

2.4. Oluşturmuş olduğum bu tabloya truncate işlemini gerçekleştirecem, bu işlemi gerçekleştirmeden önce tablo dolu haldeyken ki database scn numarasini alıyorum.

SQL> select a.oldest_flashback_scn,(select scn_to_timestamp(a.oldest_flashback_scn) from dual) oldest_flashback_time,(select 'Current scn: '|| current_scn||' .Current scn to date: '|| scn_to_timestamp(current_scn) from v$database) current_scn,a.retention_target,a.flashback_size,a.estimated_flashback_size from v$flashback_database_log a;

OLDEST_FLASHBACK_SCN     OLDEST_FLASHBACK_TIME                 CURRENT_SCN                                                                       RETENTION_TARGET   FLASHBACK_SIZE  ESTIMATED_FLASHBACK_SIZE
--------------------     ----------------------------------   --------------------------------------------------------------                    ----------------    --------------  ------------------------
         4363163         30-OCT-12 11.03.32.000000000 AM         Current scn: 5243411 .Current scn to date: 18-JAN-13 11.03.47.000000000 AM         2880            100687872       5256462336     

SQL> truncate table bcanbakal.table_x;

Table truncated.      

SQL> select count(1) from bcanbakal.table_x;

  COUNT(1)
----------
     0

2.5. Veritabanı kapatıp ,tablomuzu truncate yapmadan önceki scn numarasına flashback database teknolojisiyle dönüş yapıyorum.

SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.

Total System Global Area 4.0353E+10 bytes
Fixed Size            2235176 bytes
Variable Size         2.1072E+10 bytes
Database Buffers     1.9193E+10 bytes
Redo Buffers           85233664 bytes
Database mounted.
SQL> flashback database to scn 5243411;

Flashback complete.

2.6. Veritabanını resetlogs la açıyoruz bu işlemden sonra yeni bir fullback almanızı öneririm, çünkü artık eski backupların bir özelliği kalmıyacak.

SQL> alter database open resetlogs;

Database altered.

2.7. Flashback islemi bittigine gore tablomuzu tekrardan kontrol edebiliriz.

SQL> select count(1) from bcanbakal.table_x;

  COUNT(1)
----------
      1000

The post Flashback database appeared first on Bugra Canbakal's Oracle Blog.

UTL MAIL: Veritabanina email gönderme package’ın kurulması

Bugra Canbakal — Mon, 31 Dec 2012 08:45:40 +0000

1.AMAÇ VE KAPSAM
Veritabanı üstünden mail gönderebilmek için utlmail ve prvtmail scriptlerini çalıştırmamız gerekiyor, script sayesinde bazı packagelar ve synonymler oluşturacağız.Script kurulumunu tamamladıktan sonra smtp server ve gerekli hakları verdiğimiz taktirde veritabanı üstünden mail gönderebilir hale gelicez.

2.UYGULAMA

2.1. Veritabanına sqlplus üstünden sysdba olarak bağlanıyoruz ve utlmail.sql scriptini çalıştırıyoruz.

2.1.1.Utlmail.sql içeriği

-bash-3.2$ cat $ORACLE_HOME/rdbms/admin/utlmail.sql
REM
REM $Header: plsql/admin/utlmail.sql /main/6 2009/01/06 14:20:27 traney Exp $
REM
REM utlmail.sql
REM
REM Copyright (c) 2002, 2008, Oracle and/or its affiliates.
REM All rights reserved. 
REM
REM    NAME
REM      utlmail.sql - PL/SQL Package for sending email messages (UTL_MAIL)
REM
REM    DESCRIPTION
REM      
REM
REM    NOTES
REM      PL/SQL package to send email messages.
REM    This package by default is not granted to anyone. Users
REM    who want to send email should contact their DBA
REM    to obtain the necessary execute privilege for this package.
REM
REM    MODIFIED   (MM/DD/YY)
REM    traney      12/29/08 - add reply-to
REM    rpang       05/04/06 - Made invoker rights routine
REM    lvbcheng    02/21/05 - 2801081
REM    lvbcheng    12/11/03 - Remove grant of UTL_MAIL to public 
REM    lvbcheng    02/25/03 - define priority levels
REM    eehrsam     10/07/02 - eehrsam_utl_mail_new_pkg
REM    eehrsam     05/01/02 - Created
REM

CREATE OR REPLACE PACKAGE utl_mail AUTHID CURRENT_USER AS

  -------------
  --  CONSTANTS
  --
  invalid_argument EXCEPTION;
  invalid_priority EXCEPTION;
  invalid_argument_errcode CONSTANT PLS_INTEGER:= -29261;
  PRAGMA EXCEPTION_INIT(invalid_argument, -29261);
  PRAGMA EXCEPTION_INIT(INVALID_PRIORITY, -44101);
  /*----------------------------------------------------------------
  **
  ** SEND - send an email message
  **
  ** This procedure packages and delivers an email message to the 
  ** SMTP server specified by the following configuration parameters:
  **
  **   SMTP_SERVER=my_server.my_company.com
  **   SMTP_DOMAIN=my_company.com
  **
  ** SEND PROCEDURE
  ** IN
  **   sender       - sender address
  **   recipients   - address(es) of 1 or more recipients, comma delimited
  **   cc           - CC (carbon copy) recipient(s)), 1 or more addresses,
  **                    comma delimited, default=NULL
  **   bcc          - BCC (blind carbon copy) recipient(s), 1 or more 
  **                    addresses, comma delimited, default=NULL
  **   subject      - subject string, default=NULL
  **   message      - message text, default=NULL
  **   mime_type    - mime type, default='text/plain'
  **   priority     - message priority, default=3, valid values are [1..5]
  **
  ** SEND_ATTACH_VARCHAR2 PROCEDURE
  ** IN
  **   sender       - sender address
  **   recipients   - address(es) of 1 or more recipients, comma delimited
  **   cc           - CC (carbon copy) recipient(s)), 1 or more addresses,
  **                    comma delimited, default=NULL
  **   bcc          - BCC (blind carbon copy) recipient(s), 1 or more 
  **                    addresses, comma delimited, default=NULL
  **   subject      - subject string, default=NULL
  **   message      - message text, default=NULL
  **   mime_type    - mime type, default='text/plain'
  **   priority     - message priority, default=3, valid values are [1..5]
  **   att_txt_inline - boolean specifying whether the attachment is viewable 
  **                    inline with the message body text, default=TRUE
  **   attachment   - attachment text data
  **   att_mime_type- attachment mime_type, default='text/plain'
  **   att_filename - filename to be offered as a default upon saving the
  **                    attachment to disk
  **
  ** SEND_ATTACH_RAW PROCEDURE
  ** IN
  **   sender       - sender address
  **   recipients   - address(es) of 1 or more recipients, comma delimited
  **   cc           - CC (carbon copy) recipient(s)), 1 or more addresses,
  **                    comma delimited, default=NULL
  **   bcc          - BCC (blind carbon copy) recipient(s), 1 or more 
  **                    addresses, comma delimited, default=NULL
  **   subject      - subject string, default=NULL
  **   message      - message text, default=NULL
  **   mime_type    - mime type, default='text/plain'
  **   priority     - message priority, default=3, valid values are [1..5]
  **   att_raw_inline - boolean specifying whether the attachment is viewable 
  **                    inline with the message body text, default=TRUE
  **   attachment   - attachment RAW data
  **   att_mime_type- attachment mime_type, default='application/octet'
  **   att_filename - filename to be offered as a default upon saving the
  **                    attachment to disk
  **
  */

  PROCEDURE send(sender         IN VARCHAR2 CHARACTER SET ANY_CS,
                 recipients     IN VARCHAR2 CHARACTER SET ANY_CS,
                 cc             IN VARCHAR2 CHARACTER SET ANY_CS DEFAULT NULL,
                 bcc            IN VARCHAR2 CHARACTER SET ANY_CS DEFAULT NULL,
                 subject        IN VARCHAR2 CHARACTER SET ANY_CS DEFAULT NULL,
                 message        IN VARCHAR2 CHARACTER SET ANY_CS DEFAULT NULL,
                 mime_type      IN VARCHAR2 CHARACTER SET ANY_CS 
                                   DEFAULT 'text/plain; charset=us-ascii',
                 priority       IN PLS_INTEGER DEFAULT 3,
                 replyto        IN VARCHAR2 CHARACTER SET ANY_CS DEFAULT NULL);

  PROCEDURE send_attach_varchar2(
                 sender         IN VARCHAR2 CHARACTER SET ANY_CS,
                 recipients     IN VARCHAR2 CHARACTER SET ANY_CS,
                 cc             IN VARCHAR2 CHARACTER SET ANY_CS DEFAULT NULL,
                 bcc            IN VARCHAR2 CHARACTER SET ANY_CS DEFAULT NULL,
                 subject        IN VARCHAR2 CHARACTER SET ANY_CS DEFAULT NULL,
                 message        IN VARCHAR2 CHARACTER SET ANY_CS DEFAULT NULL,
                 mime_type      IN VARCHAR2 CHARACTER SET ANY_CS 
                                   DEFAULT 'text/plain; charset=us-ascii',
                 priority       IN PLS_INTEGER DEFAULT 3,
                 attachment     IN VARCHAR2 CHARACTER SET ANY_CS,
                 att_inline     IN BOOLEAN  DEFAULT TRUE,
                 att_mime_type  IN VARCHAR2 CHARACTER SET ANY_CS 
                                   DEFAULT 'text/plain; charset=us-ascii',
                 att_filename   IN VARCHAR2 CHARACTER SET ANY_CS DEFAULT NULL,
                 replyto        IN VARCHAR2 CHARACTER SET ANY_CS DEFAULT NULL);

  PROCEDURE send_attach_raw(
                 sender         IN VARCHAR2 CHARACTER SET ANY_CS,
                 recipients     IN VARCHAR2 CHARACTER SET ANY_CS,
                 cc             IN VARCHAR2 CHARACTER SET ANY_CS DEFAULT NULL,
                 bcc            IN VARCHAR2 CHARACTER SET ANY_CS DEFAULT NULL,
                 subject        IN VARCHAR2 CHARACTER SET ANY_CS DEFAULT NULL,
                 message        IN VARCHAR2 CHARACTER SET ANY_CS DEFAULT NULL,
                 mime_type      IN VARCHAR2 CHARACTER SET ANY_CS 
                                   DEFAULT 'text/plain; charset=us-ascii',
                 priority       IN PLS_INTEGER DEFAULT 3,
                 attachment     IN RAW,
                 att_inline     IN BOOLEAN  DEFAULT TRUE,
                 att_mime_type  IN VARCHAR2 CHARACTER SET ANY_CS 
                                   DEFAULT 'application/octet',
                 att_filename   IN VARCHAR2 CHARACTER SET ANY_CS DEFAULT NULL,
                 replyto        IN VARCHAR2 CHARACTER SET ANY_CS DEFAULT NULL);

END;
/

CREATE OR REPLACE PUBLIC SYNONYM utl_mail FOR sys.utl_mail;

2.1.2. Utlmail.sql sqlplus üstünden sysdba olarak çalıştırıyoruz.

SQL> @$ORACLE_HOME/rdbms/admin/utlmail.sql

Package created.

Synonym created.

2.2. Veritabanına sqlplus üstünden sysdba olarak bağlanıyoruz ve prvtmail.plb scriptini çalıştırıyoruz.

2.2.1. Prvtmail.plb scriptin içeriği

-bash-3.2$  cat $ORACLE_HOME/rdbms/admin/utlmail.sql
REM
REM $Header: plsql/admin/utlmail.sql /main/6 2009/01/06 14:20:27 traney Exp $
REM
REM utlmail.sql
REM
REM Copyright (c) 2002, 2008, Oracle and/or its affiliates.
REM All rights reserved. 
REM
REM    NAME
REM      utlmail.sql - PL/SQL Package for sending email messages (UTL_MAIL)
REM
REM    DESCRIPTION
REM      
REM
REM    NOTES
REM      PL/SQL package to send email messages.
REM    This package by default is not granted to anyone. Users
REM    who want to send email should contact their DBA
REM    to obtain the necessary execute privilege for this package.
REM
REM    MODIFIED   (MM/DD/YY)
REM    traney      12/29/08 - add reply-to
REM    rpang       05/04/06 - Made invoker rights routine
REM    lvbcheng    02/21/05 - 2801081
REM    lvbcheng    12/11/03 - Remove grant of UTL_MAIL to public 
REM    lvbcheng    02/25/03 - define priority levels
REM    eehrsam     10/07/02 - eehrsam_utl_mail_new_pkg
REM    eehrsam     05/01/02 - Created
REM

CREATE OR REPLACE PACKAGE utl_mail AUTHID CURRENT_USER AS

  -------------
  --  CONSTANTS
  --
  invalid_argument EXCEPTION;
  invalid_priority EXCEPTION;
  invalid_argument_errcode CONSTANT PLS_INTEGER:= -29261;
  PRAGMA EXCEPTION_INIT(invalid_argument, -29261);
  PRAGMA EXCEPTION_INIT(INVALID_PRIORITY, -44101);
  /*----------------------------------------------------------------
  **
  ** SEND - send an email message
  **
  ** This procedure packages and delivers an email message to the 
  ** SMTP server specified by the following configuration parameters:
  **
  **   SMTP_SERVER=my_server.my_company.com
  **   SMTP_DOMAIN=my_company.com
  **
  ** SEND PROCEDURE
  ** IN
  **   sender       - sender address
  **   recipients   - address(es) of 1 or more recipients, comma delimited
  **   cc           - CC (carbon copy) recipient(s)), 1 or more addresses,
  **                    comma delimited, default=NULL
  **   bcc          - BCC (blind carbon copy) recipient(s), 1 or more 
  **                    addresses, comma delimited, default=NULL
  **   subject      - subject string, default=NULL
  **   message      - message text, default=NULL
  **   mime_type    - mime type, default='text/plain'
  **   priority     - message priority, default=3, valid values are [1..5]
  **
  ** SEND_ATTACH_VARCHAR2 PROCEDURE
  ** IN
  **   sender       - sender address
  **   recipients   - address(es) of 1 or more recipients, comma delimited
  **   cc           - CC (carbon copy) recipient(s)), 1 or more addresses,
  **                    comma delimited, default=NULL
  **   bcc          - BCC (blind carbon copy) recipient(s), 1 or more 
  **                    addresses, comma delimited, default=NULL
  **   subject      - subject string, default=NULL
  **   message      - message text, default=NULL
  **   mime_type    - mime type, default='text/plain'
  **   priority     - message priority, default=3, valid values are [1..5]
  **   att_txt_inline - boolean specifying whether the attachment is viewable 
  **                    inline with the message body text, default=TRUE
  **   attachment   - attachment text data
  **   att_mime_type- attachment mime_type, default='text/plain'
  **   att_filename - filename to be offered as a default upon saving the
  **                    attachment to disk
  **
  ** SEND_ATTACH_RAW PROCEDURE
  ** IN
  **   sender       - sender address
  **   recipients   - address(es) of 1 or more recipients, comma delimited
  **   cc           - CC (carbon copy) recipient(s)), 1 or more addresses,
  **                    comma delimited, default=NULL
  **   bcc          - BCC (blind carbon copy) recipient(s), 1 or more 
  **                    addresses, comma delimited, default=NULL
  **   subject      - subject string, default=NULL
  **   message      - message text, default=NULL
  **   mime_type    - mime type, default='text/plain'
  **   priority     - message priority, default=3, valid values are [1..5]
  **   att_raw_inline - boolean specifying whether the attachment is viewable 
  **                    inline with the message body text, default=TRUE
  **   attachment   - attachment RAW data
  **   att_mime_type- attachment mime_type, default='application/octet'
  **   att_filename - filename to be offered as a default upon saving the
  **                    attachment to disk
  **
  */

  PROCEDURE send(sender         IN VARCHAR2 CHARACTER SET ANY_CS,
                 recipients     IN VARCHAR2 CHARACTER SET ANY_CS,
                 cc             IN VARCHAR2 CHARACTER SET ANY_CS DEFAULT NULL,
                 bcc            IN VARCHAR2 CHARACTER SET ANY_CS DEFAULT NULL,
                 subject        IN VARCHAR2 CHARACTER SET ANY_CS DEFAULT NULL,
                 message        IN VARCHAR2 CHARACTER SET ANY_CS DEFAULT NULL,
                 mime_type      IN VARCHAR2 CHARACTER SET ANY_CS 
                                   DEFAULT 'text/plain; charset=us-ascii',
                 priority       IN PLS_INTEGER DEFAULT 3,
                 replyto        IN VARCHAR2 CHARACTER SET ANY_CS DEFAULT NULL);

  PROCEDURE send_attach_varchar2(
                 sender         IN VARCHAR2 CHARACTER SET ANY_CS,
                 recipients     IN VARCHAR2 CHARACTER SET ANY_CS,
                 cc             IN VARCHAR2 CHARACTER SET ANY_CS DEFAULT NULL,
                 bcc            IN VARCHAR2 CHARACTER SET ANY_CS DEFAULT NULL,
                 subject        IN VARCHAR2 CHARACTER SET ANY_CS DEFAULT NULL,
                 message        IN VARCHAR2 CHARACTER SET ANY_CS DEFAULT NULL,
                 mime_type      IN VARCHAR2 CHARACTER SET ANY_CS 
                                   DEFAULT 'text/plain; charset=us-ascii',
                 priority       IN PLS_INTEGER DEFAULT 3,
                 attachment     IN VARCHAR2 CHARACTER SET ANY_CS,
                 att_inline     IN BOOLEAN  DEFAULT TRUE,
                 att_mime_type  IN VARCHAR2 CHARACTER SET ANY_CS 
                                   DEFAULT 'text/plain; charset=us-ascii',
                 att_filename   IN VARCHAR2 CHARACTER SET ANY_CS DEFAULT NULL,
                 replyto        IN VARCHAR2 CHARACTER SET ANY_CS DEFAULT NULL);

  PROCEDURE send_attach_raw(
                 sender         IN VARCHAR2 CHARACTER SET ANY_CS,
                 recipients     IN VARCHAR2 CHARACTER SET ANY_CS,
                 cc             IN VARCHAR2 CHARACTER SET ANY_CS DEFAULT NULL,
                 bcc            IN VARCHAR2 CHARACTER SET ANY_CS DEFAULT NULL,
                 subject        IN VARCHAR2 CHARACTER SET ANY_CS DEFAULT NULL,
                 message        IN VARCHAR2 CHARACTER SET ANY_CS DEFAULT NULL,
                 mime_type      IN VARCHAR2 CHARACTER SET ANY_CS 
                                   DEFAULT 'text/plain; charset=us-ascii',
                 priority       IN PLS_INTEGER DEFAULT 3,
                 attachment     IN RAW,
                 att_inline     IN BOOLEAN  DEFAULT TRUE,
                 att_mime_type  IN VARCHAR2 CHARACTER SET ANY_CS 
                                   DEFAULT 'application/octet',
                 att_filename   IN VARCHAR2 CHARACTER SET ANY_CS DEFAULT NULL,
                 replyto        IN VARCHAR2 CHARACTER SET ANY_CS DEFAULT NULL);

END;
/

CREATE OR REPLACE PUBLIC SYNONYM utl_mail FOR sys.utl_mail;

2.2.2. Prvtmail.plb scriptini sqlplus üstünden sysdba olarak çalıştırıyoruz.

SQL> @$ORACLE_HOME/rdbms/admin/prvtmail.plb

Package created.

Package body created.

Grant succeeded.

Package body created.

No errors.

2.3. Smtp serverı set edip ,kullanıcımıza utl_mail package’ını çalıştırma hakkını vermemiz gerekiyor.

SQL> alter system set smtp_out_server= '172.20.100.100' scope=both;

System altered.

SQL>  GRANT EXECUTE ON UTL_MAIL TO bcanbakal;

Grant succeeded.

2.4. Aşağıdaki tarz bir sorguylapackage çalışıp çalışmadığını test edebilirsiniz.

SQL> exec UTL_MAIL.SEND ('gonderen@mail_adresi.com','alici_1@mail_adresi.com;alici_2@mail_adresi.com',NULL,NULL,'Mailin subject kismi','Mailin body kismi' , 'text/html; charset=us-ascii',NULL);

PL/SQL procedure successfully completed.

2.6. Aşağıdaki tarz ORA-06502,ORA-06512 hatalarını alırsanız smtp serverınızda sorun var demektir.

ORA-06502: PL/SQL: numeric or value error
ORA-06512: at "SYS.UTL_MAIL", line 654
ORA-06512: at "SYS.UTL_MAIL", line 671

2.7. UTL_MAIL package büyük mailler gönderirken sorun çıkartabiliyor, bu tarz durumlarda daha profosyonel bir çözüm olan CES i kullanmanızı öneririm.

CES package scripti: http://www.oracletips.info/ces_email_files.sql

CES package email gönderme örnekleri: http://www.uaex.edu/bknox/Using_CES.email_files.htm

The post UTL MAIL: Veritabanina email gönderme package’ın kurulması appeared first on Bugra Canbakal's Oracle Blog.

Logical Standby Kurulumu

Bugra Canbakal — Wed, 28 Nov 2012 11:46:49 +0000

1.AMAÇ VE KAPSAM
Başka bir yazımda Physical standby veritabanı kurulumunu anlatmıştım, bu yazımda ise kurmuş olduğumuz physical standby database’i logical standby’a çevireceğiz.

2.UYGULAMA

2.1. Primary database üstünde asagidaki SQL sorgusunu yaziyoruz, Sorgular sonucu veritabaninda hangi tablolar logical standbyda desteklenmiyor onlari buluyoruz.

SQL> Select * from dba_logstdby_unsupported;

 OWNER                 TABLE_NAME                    COLUMN_NAME         DATA_TYPE          
--------------------- --------------------------    ----------------    --------------- 
OE    CATEGORIES_TAB    CATEGORY_ID                    Object Table        NUMBER
OE    CATEGORIES_TAB    PARENT_CATEGORY_ID            Object Table

OWNER                 TABLE_NAME                    COLUMN_NAME         DATA_TYPE          
--------------------- --------------------------    ----------------    --------------- 
WMSYS                 WM$UDTRIG_INFO                TRIG_CODE           LONG
WMSYS                 WM$VERSIONED_TABLES           UNDO_CODE           WM$ED_UNDO_CODE_TABLE_TYPE

2.2. Primary key veya non-null unique indexes bulunmayan tablolari asagidaki sorguyla bulabiliyoruz.
N = Logical standby için tablo içinde yeterli sayida column bilgisine ulasabildigini söylüyor
Y = LONG, CLOB veya BLOB gibi birbirine bagli olmayan datatypelari bulmaniza yariyor.Supplemental loggingi açarak bu kisimlarida tanimlanabilir yapabiliriz.

SQL>  SELECT OWNER, TABLE_NAME,BAD_COLUMN FROM DBA_LOGSTDBY_NOT_UNIQUE
     WHERE TABLE_NAME NOT IN (SELECT TABLE_NAME FROM DBA_LOGSTDBY_UNSUPPORTED);

OWNER                          TABLE_NAME                     B
------------------------------ ------------------------------ -
SCOTT                          BONUS                          N
SCOTT                          SALGRADE                       N
SH                             SALES                          N
SH                             COSTS                          N
SH                             SUPPLEMENTARY_DEMOGRAPHICS     N

2.3. Supplemental log açikmi diye bakiyoruz.

SQL> select supplemental_log_data_pk,supplemental_log_data_ui from v$database;

SUP SUP
--- ---
NO  NO

2.4.Eger açik degilse primary key ve unique index için supplemental loggingi açiyoruz ve yeni bir log üretmesini sagliyoruz.

SQL> ALTER  DATABASE ADD SUPPLEMENTAL LOG DATA (PRIMARY KEY,UNIQUE INDEX) COLUMNS;

Database altered.

SQL> ALTER SYSTEM SWITCH LOGFILE;

System altered.

2.5. Paralizim açik degilse açiyoruz. // her dbde gerekmiyor.

SQL> ALTER SYSTEM SET LOG_PARALLELISM=1 SCOPE=BOTH;

2.6. Physcal standby database’in loglari islemesini engelliyoruz.

SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;

Database altered.

2.7. Primary database’in log archive dest 1 All_LOGFILES ve ALL_ROLES diye tanimli bunu ONLINE_LOGFILES ve ALL_ROLES diye degistiriyoruz. Log_archive_dest_3 e ise tamamen yeniden yapilandirip aktif yapiyorum ve 3 parametresi üstünde bazi oynamalar yapmamiz gerekiyor.

SQL> show parameter log

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
log_archive_dest_1                   string      LOCATION=/u01/app/oracle/datab
                                                 ases/prim/redo/
                                                 VALID_FOR=(ALL_LOGFILES,ALL_RO
                                                 LES)
                                                 DB_UNIQUE_NAME=bugra
log_archive_dest_2                   string      service=stdby lgwr async noaff
                                                 irm valid_for=(online_logfiles
                                                 ,primary_role) db_unique_name=
                                                 stdby
log_archive_dest_3                   string
log_archive_dest_state_1             string      ENABLE
log_archive_dest_state_2             string      enable
log_archive_dest_state_3             string      enable
remote_login_passwordfile            string      EXCLUSIVE
sec_case_sensitive_logon             boolean     TRUE
sec_max_failed_login_attempts        integer     10

SQL> alter system set LOG_ARCHIVE_DEST_1='LOCATION=/u01/app/oracle/databases/prim/redo/ VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES)  DB_UNIQUE_NAME=bugra'
scope=both;

System altered.

SQL> Alter system set LOG_ARCHIVE_DEST_3='LOCATION=/u01/app/oracle/databases/prim/redo2/ VALID_FOR=(STANDBY_LOGFILES,STANDBY_ROLE) DB_UNIQUE_NAME=bugra' scope=both;

System altered.

SQL> alter system set LOG_ARCHIVE_DEST_STATE_3=ENABLE scope=both;

System altered.

2.8. Redo log sözlügünü olusturmamiz gerekiyor böylelikle LOG_ARCHIVE_DEST_1 e tanimladigimiz ONLINE_LOGFILE çalisabilecek. Bunun için LogMiner sözlügünü yaratiyoruz.

SQL> EXECUTE DBMS_LOGSTDBY.BUILD;  

PL/SQL procedure successfully completed.

2.9.Redo loglar artik Logical standby kurulumu için uygun hale geldi.Physical standby makinasina gidip logical standby içni recover islemini baslatiyoruz.

SQL> ALTER DATABASE RECOVER TO LOGICAL STANDBY stdby;

Standby Alertloglari

Media Recovery Complete (stdby)
tkcrrxms: Killing 4 processes (all RFS)
RESETLOGS after incomplete recovery UNTIL CHANGE 904454
Resetting resetlogs activation ID 772557144 (0x2e0c4958)
Online log /u01/app/oracle/product/11.1.0/oradata/stdby/redogroup_1.262.720476831: Thread 1 Group 1 was previously cleared
Online log /u01/app/oracle/product/11.1.0/oradata/stdby/redogroup_1.263.720476839: Thread 1 Group 1 was previously cleared
Online log /u01/app/oracle/product/11.1.0/oradata/stdby/redogroup_2.264.720476843: Thread 1 Group 2 was previously cleared
Online log /u01/app/oracle/product/11.1.0/oradata/stdby/redogroup_2.265.720476851: Thread 1 Group 2 was previously cleared
Standby became primary SCN: 904452
Sat Sep 18 02:28:01 2010
Setting recovery target incarnation to 3
Converting standby mount to primary mount.
ACTIVATE STANDBY: Complete - Database mounted as primary (stdby)
*** DBNEWID utility started ***
DBID will be changed from 772585308 to new DBID of 1331092977 for database BUGRA
DBNAME will be changed from BUGRA to new DBNAME of STDBY
Starting datafile conversion
Setting recovery target incarnation to 1
Datafile conversion complete
Failed to find temporary file: /u01/app/oracle/product/11.1.0/oradata/stdby/data/temp.268.720476923
Database name changed to STDBY.
Modify parameter file and generate a new password file before restarting.
Database ID for database STDBY changed to 1331092977.
All previous backups and archived redo logs for this database are unusable.
Database has been shutdown, open with RESETLOGS option.
Succesfully changed database name and ID.
*** DBNEWID utility finished succesfully ***
Completed: ALTER DATABASE RECOVER TO LOGICAL STANDBY stdby
Sat Sep 18 02:28:14 2010
destination database instance is 'started' not 'mounted'

2.10. Logical standbyimiz nomount posizyonunda açilmis oldu simdi 1,2 ve 3. log_archive_dest parametrelerini değiştireceğiz.

SQL> Show parameter log

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
log_archive_dest_1                   string      location=/u01/app/oracle/produ
                                                 ct/11.1.0/oradata/stdby/arc1/
                                                 valid_for=(all_logfiles,all_ro
                                                 les) db_unique_name=stdby
log_archive_dest_2                   string      service=bugra lgwr async noaff
                                                 irm valid_for=(online_logfiles
                                                 ,primary_role) db_unique_name=
                                                 bugra
log_archive_dest_3                   string
log_archive_dest_state_1             string      enable
log_archive_dest_state_2             string      ENABLE
log_archive_dest_state_3             string      enable

SQL> alter system set LOG_ARCHIVE_DEST_1=
  'LOCATION=/u01/app/oracle/product/11.1.0/oradata/stdby/arc1/
   VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES)
   DB_UNIQUE_NAME=stdby'scope=both;

System altered.

SQL> Alter system set LOG_ARCHIVE_DEST_2=
  'SERVICE=bugra ASYNC
   VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
   DB_UNIQUE_NAME=bugra' scope=both;

System altered.

SQL> Alter system set LOG_ARCHIVE_DEST_3=
  'LOCATION=/u01/app/oracle/product/11.1.0/oradata/stdby/arc2/
   VALID_FOR=(STANDBY_LOGFILES,STANDBY_ROLE)
   DB_UNIQUE_NAME=stdby' scope=both;

System altered.

SQL> Alter system set LOG_ARCHIVE_DEST_STATE_1=ENABLE scope=both;

System altered.

SQL> Alter system set LOG_ARCHIVE_DEST_STATE_2=ENABLE scope=both;

System altered.

SQL> Alter system set LOG_ARCHIVE_DEST_STATE_3=ENABLE scope=both;

System altered.

2.11. Database’i kapatip mount posizyonunda açiyoruz sonrada resetlogs yapip databasei open hale getiriyoruz.Start logical standby apply immediate dedikten sonra redolar islenmeye basliyacaktir.

SQL> shutdown immediate;
ORA-01507: database not mounted

ORACLE instance shut down.
SQL> startup mount;
ORA-32004: obsolete and/or deprecated parameter(s) specified
ORACLE instance started.

Total System Global Area  146472960 bytes
Fixed Size                  1298472 bytes
Variable Size              92278744 bytes
Database Buffers           50331648 bytes
Redo Buffers                2564096 bytes
Database mounted.
SQL> ALTER DATABASE OPEN RESETLOGS;

Database altered.

SQL> ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE;

Database altered.

2.12. Standby Alert Loglarına bakalım.

Completed: alter database open
ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE
ALTER DATABASE START LOGICAL STANDBY APPLY (stdby)
with optional part
IMMEDIATE
Attempt to start background Logical Standby process
Sat Sep 18 03:32:48 2010
LSP0 started with pid=24, OS id=32724 
Completed: ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE
LOGMINER: Parameters summary for session# = 1
LOGMINER: Number of processes = 3, Transaction Chunk Size = 201
LOGMINER: Memory Size = 30M, Checkpoint interval = 150M
LOGMINER: SpillScn 0, ResetLogScn 522753
Sat Sep 18 03:33:12 2010
LOGMINER: session#=1, reader MS00 pid=28 OS id=32739 sid=82 started
Sat Sep 18 03:33:14 2010
LOGMINER: session#=1, builder MS01 pid=29 OS id=32741 sid=79 started
Sat Sep 18 03:33:14 2010
LOGMINER: session#=1, preparer MS02 pid=30 OS id=32743 sid=78 started
LOGMINER: Begin mining logfile during dictionary load for session 1 thread 1 sequence 41, /u01/app/oracle/product/11.1.0/oradata/stdby/arc1/1_41_720476831.dbf
LOGMINER: Turning ON Log Auto Delete

2.13. Son olarak V$database sorgu çekip database’in çalışma şeklini görebiliriz.

 
SQL> select log_mode,open_mode , database_role from v$database;

LOG_MODE     OPEN_MODE  DATABASE_ROLE
------------ ---------- ----------------
ARCHIVELOG   READ WRITE LOGICAL STANDBY

The post Logical Standby Kurulumu appeared first on Bugra Canbakal's Oracle Blog.

Asm diskgroup içine yeni bir disk eklemek

Bugra Canbakal — Mon, 26 Nov 2012 12:43:23 +0000

1.AMAÇ VE KAPSAM

Kullanılan bir asm diskgroup içine yeni bir disk ekleyip diskgroup büyüteme çalışmasını anlatacağım.Bu çalışmayı yapmadan önce adımlar hakkında genel bir bilgi vermek istiyorum.Elimde DISK4 isminde hiçbir diskgroupa ayit olmayan bir asm diskim var bu diskin öncelikle sağlamlığını kontrol edicem, bu çalışma bittikten sonra production ortama zarar vermemesi için yeni bir diskgroup oluşturup bu diski bu groupa ekliyecem eğer bu aşamaları geçtiysem production diskgroup’a diskimizi ekliyeceğim.

2.UYGULAMA

2.1.Boşta olan DISK4 diskini asm üstünden kontrol edicez. (RAC ortamında bu calısma 2 node üstündede yapılır)

[root@oracle ~]# /etc/init.d/oracleasm  scandisks

Scanning the system for Oracle ASMLib disks:               [  OK  ]

[root@oracle ~]# /etc/init.d/oracleasm  listdisks

DISK1

DISK2

DISK3

DISK4

[root@oracle ~]# /etc/init.d/oracleasm  querydisk DISK4

Disk "DISK4" is a valid ASM disk

[root@oracle ~]# ls -l /dev/oracleasm/disks/DISK4

brw-rw---- 1 oracle dba 8, 34 Jun 23 23:40 /dev/oracleasm/disks/DISK4

2.2. Şimdi asm headerları düzgün mü diye kontrol etmemiz gerekiyor.Bunun için ASM metadata editor kfed’ i kullanıcaz. Çıktısında “kfbh.type: 1 ; 0×002: KFBTYP_DISKHEAD” görürsek asm’nin headerları düzgün diyebiliriz.

[root@oracle ~]# kfed read /dev/oracleasm/disks/DISK4
 kfbh.endian: 1 ; 0x000: 0x01
 kfbh.hard: 130 ; 0x001: 0x82
 kfbh.type: 1 ; 0x002: KFBTYP_DISKHEAD
 ...
 kfbh.check: 1539641569 ; 0x00c: 0x5bc510e1
 ...
 kfdhdb.driver.provstr: ORCLDISKDISK4 ; 0x000: length=13
 ...
 kfdhdb.dsknum: 0 ; 0x024: 0x0000
 kfdhdb.grptyp: 2 ; 0x026: KFDGTP_NORMAL
 kfdhdb.hdrsts: 3 ; 0x027: KFDHDR_MEMBER
 kfdhdb.dskname: PLAY0 ; 0x028: length=5
 kfdhdb.grpname: PLAY ; 0x048: length=4
 kfdhdb.fgname: P1 ; 0x068: length=2
 ...
 kfdhdb.blksize: 4096 ; 0x0ba: 0x1000
 kfdhdb.ausize: 4194304 ; 0x0bc: 0x00400000
 ...
 kfdhdb.dsksize: 1221 ; 0x0c4: 0x000004c5
 ...

2.3.1. ASM instance baglaniyoruz. (RAC ortamında aşağıdaki çalışmaları tek node üstünde yapıyoruz)

[oracle@oracle ~]$ export ORACLE_SID=+ASM

[oracle@oracle ~]$ sqlplus /  as sysdba

SQL*Plus: Release 11.1.0.6.0 - Production on Fri Jun 24 00:11:02 2011

Copyright (c) 1982, 2007, Oracle.  All rights reserved.

Connected to:

Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production

With the Partitioning, OLAP, Data Mining and Real Application Testing options

2.3.2. DISK4 ü test amaçlı yeni diskgroup oluşturup bu gruop’a ekliyoruz..

P.S.: Çalışma esnasında asm_diskstring le ilgili hata aldım, aynı hatayı alan başka arkadaşlarımda olmuştu bu yüzden hatayı ve gerekli çalışmayıda ekliyorum.

SQL> CREATE DISKGROUP TEST EXTERNAL REDUNDANCY DISK '/dev/oracleasm/disks/DISK4';

CREATE DISKGROUP TEST EXTERNAL REDUNDANCY DISK '/dev/oracleasm/disks/DISK4'

*

ERROR at line 1:

ORA-15018: diskgroup cannot be created

ORA-15031: disk specification '/dev/oracleasm/disks/DISK4' matches no disks

ORA-15014: path '/dev/oracleasm/disks/DISK4' is not in the discovery set

SQL> show parameter disk

NAME                                 TYPE        VALUE

------------------------------------ ----------- ------------------------------

asm_diskgroups                       string      DATA1, DATA2

asm_diskstring                       string

disk_asynch_io                       boolean     TRUE

SQL> alter system set asm_diskstring='/dev/oracleasm/disks/DISK*';

alter system set asm_diskstring='/dev/oracleasm/disks/DISK*'

*

ERROR at line 1:

ORA-02097: parameter cannot be modified because specified value is invalid

ORA-15014: path 'ORCL:DISK1' is not in the discovery s

SQL> alter system set asm_diskstring='ORCL:DISK*';

System altered.

SQL> CREATE DISKGROUP TEST EXTERNAL REDUNDANCY DISK 'ORCL:DISK4';

Diskgroup created.

2.4. TEST diskgroup’unu oluşturduk aşağıdaki sorguyu çalıştırdıgınızda TEST diskgroupunu görmeniz gerekiyor.

SQL> SELECT STATE, NAME FROM V$ASM_DISKGROUP;

STATE       NAME
----------- ------------------------------
MOUNTED     DATA1
MOUNTED     DATA2
MOUNTED     TEST

2.5. TEST diskgroup’unu mount görüyorsanız asmye yeni eklemiş oldugunuz disk düzgün calısıyor demektir.Şimdi gerçek amacımız olan DISK4 ü DATA1 groupuna ekliyecez.Bunun için önce TEST diskgroup’unu drop edip DISK4 boşa çıkartıyoruz.

SQL> drop diskgroup test;

Diskgroup dropped.

2.6. Diski eklemeden önce veirtabaninin instanceina sysdba olarak baglanip suanki disk durumumuza bakalim

SQL> COL % FORMAT 99.0
SQL> SELECT name, free_mb, total_mb, free_mb/total_mb*100 "%" FROM v$asm_diskgroup;
NAME                              FREE_MB   TOTAL_MB     %
------------------------------ ---------- ---------- -----
DATA1                                8554      10196  83.9
DATA2                                4902       5137  95.4

2.7. ASM Simdi tekrardan +ASM instance girelim ve yeni diskimizi DATA1 diskgroupuna ekleyelim.

SQL>  ALTER DISKGROUP DATA1 ADD DISK 'ORCL:DISK4';

Diskgroup altered.

2.8. Normal instanceda asagidaki sorguyu tekrardan calistirip diskimizin yeni diskgroupa eklendigini görelim.

 
SQL> SELECT name, free_mb, total_mb, free_mb/total_mb*100 "%" FROM v$asm_diskgroup;

NAME                              FREE_MB   TOTAL_MB     %
------------------------------ ---------- ---------- -----
DATA1                               13689      15333  89.3
DATA2                                4902       5137  95.4

SQL>

The post Asm diskgroup içine yeni bir disk eklemek appeared first on Bugra Canbakal's Oracle Blog.

Lokal disk üstünde açılmış olan bir datafile’ı ASM üstüne taşımak

Bugra Canbakal — Wed, 04 Jul 2012 11:36:03 +0000

1.AMAÇ VE KAPSAM
Bazı durumlarda yanlışlıkla veya rac sistem üstüne çalışıldığı unutulup lokal disk üstünde datafile oluşturulabiliyor. Aşağıdaki yazımda lokal disk üstüne oluşturduğumuz bu datafileları nasıl ortak alan olan ASM üstüne taşıyacağımızı anlatacağım.

2.UYGULAMA

2.1. 2 node RAC sistem üstünde 2 tane tablespace 1. node’un lokal disk’i üstünde oluşturdum.

SQL> select file_name,tablespace_name from dba_data_files where tablespace_name like 'AHBS%';

FILE_NAME        TABLESPACE_NAME
--------------------------------------------------------------------------------

/u01/app/oracle/product/11.2.0.2/dbhome_1/dbs/ahbs_data_ts     AHBS_DATA_TS

/u01/app/oracle/product/11.2.0.2/dbhome_1/dbs/AHBS_INDEX_TS01.dbf    AHBS_INDEX_TS

2 rows selected.

2.2. Bu tablespaceler üstünde çalışma yapabilmemiz için öncelikle tablespaceleri offline çekmemiz gerekmekte.

SQL> alter tablespace AHBS_INDEX_TS offline;
Tablespace altered.
SQL> alter tablespace AHBS_DATA_TS offline;
Tablespace altered.

2.3. Tablespaceleri offline çektiğimize göre ASM ye kopyama işlemine başlayabiliriz.Bunun için rman’e girip copy datafile komutu kullanıyoruz.

[oracle@sba5db07 ~]$ rman

Recovery Manager: Release 11.2.0.2.0 - Production on Sat Jun 30 18:10:00 2012

Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.

RMAN> connect target;

connected to target database: MERGE (DBID=3048845705)

RMAN> copy datafile '/u01/app/oracle/product/11.2.0.2/dbhome_1/dbs/ahbs_data_ts' to  '+DATA_SBA5/merge/datafile/ahbs_data_ts_01.dbf';

Starting backup at 30-JUN-12
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=201 instance=MERGE1 device type=DISK
channel ORA_DISK_1: starting datafile copy
input datafile file number=00017 name=/u01/app/oracle/product/11.2.0.2/dbhome_1/dbs/ahbs_data_ts
output file name=+DATA_SBA5/merge/datafile/ahbs_data_ts_01.dbf tag=TAG20120630T182127 RECID=4 STAMP=787342893
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:07
Finished backup at 30-JUN-12

RMAN> copy datafile  '/u01/app/oracle/product/11.2.0.2/dbhome_1/dbs/AHBS_INDEX_TS01.dbf'  to  '+DATA_SBA5/merge/datafile/AHBS_INDEX_TS01.dbf' ;

Starting backup at 30-JUN-12
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile copy
input datafile file number=00018 name=/u01/app/oracle/product/11.2.0.2/dbhome_1/dbs/AHBS_INDEX_TS01.dbf
output file name=+DATA_SBA5/merge/datafile/ahbs_index_ts01.dbf tag=TAG20120630T182136 RECID=5 STAMP=787342896
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:01
Finished backup at 30-JUN-12

2.4. Datafile’larımızı ortak ASM alan üstüne taşıdık ,veritabanına bu tablespaceleri artık ASM üstünden çalıştıracaksın dememiz gerekiyor.Bu işlem için rename file komutunu kullanmamız gerekiyor.

SQL> alter database rename file   '/u01/app/oracle/product/11.2.0.2/dbhome_1/dbs/ahbs_data_ts' to  '+DATA_SBA5/merge/datafile/ahbs_data_ts_01.dbf' ;

Database altered.

SQL> alter database rename file  '/u01/app/oracle/product/11.2.0.2/dbhome_1/dbs/AHBS_INDEX_TS01.dbf'  to  '+DATA_SBA5/merge/datafile/AHBS_INDEX_TS01.dbf' ;

Database altered.

2.5. Artık tablespacelerimizi online’a çekebiliriz.

SQL> alter tablespace AHBS_INDEX_TS online;

Tablespace altered.

SQL> alter tablespace AHBS_DATA_TS online;

Tablespace altered.

2.6. Değiştirmiş olduğumuz tablespaceleri veritabanından kontrol edelim.

SQL> select file_name,tablespace_name from dba_data_files where tablespace_name like 'AHBS%';

FILE_NAME        TABLESPACE_NAME
--------------------------------------------------------------------------------

+DATA_SBA5/merge/datafile/ahbs_data_ts_01.dbf     AHBS_DATA_TS

+DATA_SBA5/merge/datafile/AHBS_INDEX_TS01.dbf    AHBS_INDEX_TS

The post Lokal disk üstünde açılmış olan bir datafile’ı ASM üstüne taşımak appeared first on Bugra Canbakal's Oracle Blog.

Oracle RMAN Catalog Kurulumu

Bugra Canbakal — Fri, 29 Jun 2012 07:52:18 +0000

1.AMAÇ VE KAPSAM
Rman üstünde yapılan backup işlemleri veritabanın controlfile’ına kaydedilir,bu controlfile’ın kaybolma olasılığına karşılık oracle bize rman catalog özelliğini önermekte,bu özellik sayesinde controlfile kaydedilen rman bilgileri başka bir veritabanında saklanır.Catalog bunun dışında rman scriptleri ve alınan backupların bilgilerini saklamak içinde kullanılabilir.Bu özelliği kullanabilmemiz için product veritabanımız dışında catalog’ların tutulacağı başka bir veritabanımızda olmalı.
Aşağıdaki yazımda oracle rman catalog’un nasil kurulacagini, source veritabanin catalogdb ye nasıl register edileceğini ve bunu nasıl kontrol edeceğinizi anlatacağım.

2.UYGULAMA

2.1. Veritabanlarımız hakkında kısa bilgiler.

192.168.166.128 sourcesrv (production olacak veritabanımız)
192.168.166.129 targetsrv (catalogdb olacak veritabanımız)

2.2. Targetsrv veritabanımızda catalog kullanıcımızı oluşturup gerekli hakları veriyoruz.

[oracle@targetsrv ~]$ sqlplus / as sysdba

SQL*Plus: Release 11.2.0.2.0 Production on Thu Jun 28 14:10:05 2012

Copyright (c) 1982, 2010, Oracle.  All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> create user catalog identified by catalog;

User created.

SQL> grant recovery_catalog_owner to catalog;

Grant succeeded.

SQL> alter user catalog quota unlimited on users;

User altered.

2.3. Catalog kullanıcısıyla TARGET veritabanın rman ‘ine bağlanıp catalogu oluşturuyoruz.

[oracle@targetsrv ~]$ rman

Recovery Manager: Release 11.2.0.2.0 - Production on Thu Jun 28 14:13:23 2012

Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.

RMAN> connect catalog catalog/catalog@TARGET

connected to recovery catalog database

RMAN> create catalog

recovery catalog created

2.4. Şimdi product sistemimize gidip TARGET veritabanımıza register yaptıracağız.

[oracle@sourcesrv ~]$ rman

Recovery Manager: Release 11.2.0.2.0 - Production on Thu Jun 28 14:19:32 2012

Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.

RMAN> connect target sys/sys@SOURCE

connected to target database: SOURCE (DBID=2888707862)

RMAN> connect catalog catalog/catalog@TARGET

connected to recovery catalog database

RMAN> register database;

database registered in recovery catalog
starting full resync of recovery catalog
full resync complete

2.5. Veritabanımızın cataloga register olup olmaduğını görmek için “report schema” komutunu çalıştırıyoruz.

RMAN> report schema;

Report of database schema for database with db_unique_name SOURCE

List of Permanent Datafiles
===========================
File Size(MB) Tablespace           RB segs Datafile Name
---- -------- -------------------- ------- ------------------------
1    700      SYSTEM               YES     /oracle/app/oradata/source/system01.dbf
2    510      SYSAUX               NO      /oracle/app/oradata/source/sysaux01.dbf
3    60       UNDOTBS1             YES     /oracle/app/oradata/source/undotbs01.dbf
4    10       USERS                NO      /oracle/app/oradata/source/users01.dbf
5    313      EXAMPLE              NO      /oracle/app/oradata/source/example01.dbf

List of Temporary Files
=======================
File Size(MB) Tablespace           Maxsize(MB) Tempfile Name
---- -------- -------------------- ----------- --------------------
1    20       TEMP                 32767       /oracle/app/oradata/source/temp01.dbf

2.6. SOURCE veritabanında bugune kadar backup alınmamıştı, TARGET veritabanına gidip catalogda birşey varmı diye kontrol ediyoruz.

[oracle@targetsrv ~]$ sqlplus catalog/catalog
SQL*Plus: Release 11.2.0.2.0 Production on Thu Jun 28 14:40:06 2012
Copyright (c) 1982, 2010, Oracle.  All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - Production
SQL> SELECT BS_KEY, BACKUP_TYPE, COMPLETION_TIME
FROM   RC_DATABASE_INCARNATION i, RC_BACKUP_SET b
WHERE  i.DB_KEY = 1
AND    i.DB_KEY = b.DB_KEY
AND    i.CURRENT_INCARNATION = 'YES';  2    3    4    5  

no rows selected

2.7. Kayıt bulunamadı, SOURCE veritabanına gidip backup’ı başlatıyorum.

[oracle@sourcesrv ~]$ rman 

Recovery Manager: Release 11.2.0.2.0 - Production on Thu Jun 28 14:19:32 2012 
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved. 

RMAN> connect target sys/sys@SOURCE 
connected to target database: SOURCE (DBID=2888707862) 

RMAN> connect catalog catalog/catalog@TARGET 
connected to recovery catalog database

RMAN> backup database;

Starting backup at 28-JUN-12
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=40 device type=DISK
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00001 name=/oracle/app/oradata/source/system01.dbf
input datafile file number=00002 name=/oracle/app/oradata/source/sysaux01.dbf
input datafile file number=00005 name=/oracle/app/oradata/source/example01.dbf
input datafile file number=00003 name=/oracle/app/oradata/source/undotbs01.dbf
input datafile file number=00004 name=/oracle/app/oradata/source/users01.dbf
channel ORA_DISK_1: starting piece 1 at 28-JUN-12
channel ORA_DISK_1: finished piece 1 at 28-JUN-12
piece handle=/oracle/app/fast_recovery_area/SOURCE/backupset/2012_06_28/o1_mf_nnndf_TAG20120628T143335_7yrj8kg6_.bkp tag=TAG20120628T143335 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:01:37
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including current control file in backup set
including current SPFILE in backup set
channel ORA_DISK_1: starting piece 1 at 28-JUN-12
channel ORA_DISK_1: finished piece 1 at 28-JUN-12
piece handle=/oracle/app/fast_recovery_area/SOURCE/backupset/2012_06_28/o1_mf_ncsnf_TAG20120628T143335_7yrjcnnz_.bkp tag=TAG20120628T143335 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 28-JUN-12

2.8. Backup başarılı şekilde alındı, şimdi TARGET veritabanına gidip aynı sorguyu tekrardan çalıştırıyoruz.

[oracle@targetsrv ~]$ sqlplus catalog/catalog
SQL*Plus: Release 11.2.0.2.0 Production on Thu Jun 28 14:40:06 2012
Copyright (c) 1982, 2010, Oracle.  All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - Production
SQL> SELECT BS_KEY, BACKUP_TYPE, COMPLETION_TIME
FROM   RC_DATABASE_INCARNATION i, RC_BACKUP_SET b
WHERE  i.DB_KEY = 1
AND    i.DB_KEY = b.DB_KEY
AND    i.CURRENT_INCARNATION = 'YES';  

    BS_KEY B COMPLETIO
---------- - ---------
        33 D 28-JUN-12
        34 D 28-JUN-12

2.9. Almış olduğumuz backup catalogda gözüktü.Catalogda bulunan veritabanını catalogdan çıkarmak için aşağıdaki işlemleri yapmamız gerekiyor.

[oracle@sourcesrv ~]$ rman
Recovery Manager: Release 11.2.0.2.0 - Production on Thu Jun 28 14:45:46 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.

RMAN> connect catalog catalog/catalog@TARGET

connected to recovery catalog database

RMAN> connect target sys/sys@SOURCE

connected to target database: SOURCE (DBID=2888707862)

RMAN> unregister database;

database name is "SOURCE" and DBID is 2888707862

Do you really want to unregister the database (enter YES or NO)? yes
database unregistered from the recovery catalog

RMAN> report schema
2> ;

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of report command at 06/28/2012 14:46:46
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20001: target database not found in recovery catalog

RMAN>

2.10. Veritabanın registerını kaldırdık şimdide TARGET veritabanına gidip catalog’u kaldıracam.

[oracle@targetsrv ~]$ rman 

Recovery Manager: Release 11.2.0.2.0 - Production on Thu Jun 28 14:49:15 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.

RMAN> connect catalog catalog/catalog@TARGET

connected to recovery catalog database

RMAN> drop catalog;

recovery catalog owner is CATALOG
enter DROP CATALOG command again to confirm catalog removal

RMAN> drop catalog;

recovery catalog dropped

The post Oracle RMAN Catalog Kurulumu appeared first on Bugra Canbakal's Oracle Blog.

RAC Impdp ORA-31693, ORA-29913, ORA-31640, ORA-19505, ORA-27037 hatalarının çözümü

Bugra Canbakal — Tue, 05 Jun 2012 06:42:02 +0000

1.AMAÇ VE KAPSAM

Oracle Rac 11gR2 versionlu veritabanında dump dosyanız shared olmayan bir alan üstündeyken parallel parametresini kullanıp impdp yaparsanız ORA-31693, ORA-29913, ORA-31640, ORA-19505, ORA-27037 hatasını alırsınız.Bunun sebebi RAC veritabanı import işlemini bütün nodelar üstünden yapmaya çalışıp paralellendirmesidir , dumpınız 1. sunucuda shared olmayan bir alanda bulunuyorsa 2. node buna erişemiyeceğinden dolayı hatayı alacaksınız.

2.UYGULAMA

2.1. Impdp işlemini yapalım.

$ impdp bcanbakal/bcanbakal directory=exp parallel=8 dumpfile=schmedump_%U.dmp logfile=log:impdp.log full=y 

ORA-31693: Table data object "ESK"."FPP_WALT_MATCH" failed to load/unload and is being skipped due to error:
ORA-31640: unable to open dump file "/u01/app/exp/schmedump_08.dmp" for read
ORA-19505: failed to identify file "/u01/app/exp/schmedump_08.dmp"
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3

2.2. Almış olduğumuz bu hatayı 3 şekilde çözebiliriz.

2.2.1. Dump dosyasını shared bir alana taşıyabiliriz.(ASM gibi)

2.2.2. impdp işlemini yaparken CLUSTER=N parametresini koyarak import işleminin sadece o node’da çalışmasını sağlayabiliriz.

$ impdp bcanbakal/bcanbakal directory=exp parallel=8 dumpfile=schmedump_%U.dmp logfile=log:impdp.log full=y CLUSTER=N

2.2.3. impdp işleminde paralelliği kullandığımızda oracle arka tarafta CLUSTER=YES olarak algılar, paralelliği kaldırırsanız hatasız import yapabilirsiniz.

$ impdp bcanbakal/bcanbakal directory=exp  dumpfile=schmedump_%U.dmp logfile=log:impdp.log full=y

The post RAC Impdp ORA-31693, ORA-29913, ORA-31640, ORA-19505, ORA-27037 hatalarının çözümü appeared first on Bugra Canbakal's Oracle Blog.

Virtual Indexes

Bugra Canbakal — Tue, 29 May 2012 10:51:47 +0000

1.AMAÇ VE KAPSAM

Productıon olarak çalışan veritabanlarında querylere göre index oluşturup performans testleri yapmak oldukça riskli bir çalışmadır, bundan dolayı oracle bize virtual index özelliğini sağlamış. Bu özellik sayesinde index oluşturmadan querylerinizin performanslarını kontrol edebilirsiniz ve bu esnada uygulamadan gelen quer

ylerin execution planları bozulmayıp eski çalışmalarına devam edicektir.

2.UYGULAMA

2.1. Tablomuzu oluşturalım.

SQL> CREATE TABLE BCANBAKAL.ISLEM_LOG_02
(
  LOG_ID               VARCHAR2(40 BYTE)        NOT NULL,
  LOG_YAPAN            VARCHAR2(40 BYTE),
  LOG_YAPILAN          VARCHAR2(40 BYTE),
  LOG_ISLEM_KATEGORI   VARCHAR2(25 BYTE),
  LOG_ISLEM            VARCHAR2(255 BYTE),
  LOG_ISLEM_SONUC      CHAR(1 BYTE),
  LOG_ACIKLAMA         VARCHAR2(1000 BYTE),
  LOG_SON_ISLEM_DAMGA  VARCHAR2(20 BYTE),
  LOG_IP               VARCHAR2(15 BYTE)
)
TABLESPACE USERS
PCTUSED    0
PCTFREE    10
INITRANS   1
MAXTRANS   255
STORAGE    (
            INITIAL          64K
            NEXT             1M
            MINEXTENTS       1
            MAXEXTENTS       UNLIMITED
            PCTINCREASE      0
            BUFFER_POOL      DEFAULT
           )
LOGGING
NOCOMPRESS
NOCACHE
NOPARALLEL
MONITORING;

2.2. Cost değeri yüksek olsun diye tablomun içine biraz data gömdüm.

SQL> select count(*) from bcanbakal.islem_log_02;

  COUNT(*)
----------
    632053
1 row selected.

2.3. Simdi LOG_IP kolonu üstünden bir sorgu çekip costunu görelim.

SQL> SQL> SET AUTOTRACE TRACEONLY explain statistics

SQL> SELECT * FROM bcanbakal.ISLEM_LOG_02 WHERE LOG_IP ='95.9.29.232';

293 rows selected.

Execution Plan
----------------------------------------------------------
   0       SELECT STATEMENT Optimizer Mode=ALL_ROWS (Cost=28769 Card=87 Bytes=94 K)
   1    0    TABLE ACCESS STORAGE FULL BCANBAKAL.ISLEM_LOG_02 (Cost=28769 Card=87 Bytes=94 K)

2.4. Nosegment opsiyonuylan ISLEM_LOG_02 tablosu üstünde bir virtual index olusturalim.

SQL> CREATE INDEX IDX_ISLEM_LOG_02_LOGIP ON ISLEM_LOG_02(LOG_IP) NOSEGMENT;

Index Created

2.5. Olusturmus oldugumuz virtual indexi kullanabilmek için Oracle’ın underscore parametrelerinden biri olan _use_nosegment_indexes aktif hale getirmemiz gerekiyor.

SQL> ALTER SESSION SET "_use_nosegment_indexes" = TRUE;

SET AUTOTRACE TRACEONLY explain statistics

SELECT * FROM bcanbakal.ISLEM_LOG_02 WHERE LOG_IP ='95.9.29.232';

Execution Plan
----------------------------------------------------------
   0       SELECT STATEMENT Optimizer Mode=ALL_ROWS (Cost=2 Card=87 Bytes=94 K)
   1    0    TABLE ACCESS BY INDEX ROWID BCANBAKAL.ISLEM_LOG_02 (Cost=2 Card=87 Bytes=94 K)
   2    1      INDEX RANGE SCAN BCANBAKAL.IDX_ISLEM_LOG_02_LOGIP (Cost=1 Card=87)

2.6. Virtual indeximiz gerçek olmaya hak kazandı, sql sorgusunun costu 28769 dan 2 ye düştü.Son olarak indeximizi oluşturuyoruz..

SQL> CREATE INDEX IDX_ISLEM_LOG_02_LOGIP_r ON ISLEM_LOG_02(LOG_IP);

The post Virtual Indexes appeared first on Bugra Canbakal's Oracle Blog.

Oracle Table Redefinition

Bugra Canbakal — Sun, 20 May 2012 09:44:49 +0000

1.AMAÇ VE KAPSAM

Redefinition production ortamlarda veritabaninda kesinti yaratmadan tablo’nun storage parametrelerini degiştirmek,farkli bir tablespace taşimak veya yeni kolonlar eklemek,silmek ve degiştirmek için kullanilabilir.
Aşağıdaki çalışmamda bir tabloyu partition’li hale getirip 2009,2010,2011 yıllarına ayit partition’larını exadatanin özelliği olan “archive high” compress’liyecem,2012 yılının aylarınıda OLTP compress yapicam.Bu esnada veritabanı operasyonel olarak çalişmaya devam edicek.
Kisaca redefinition nasil çalıştığını anlatayım: yeni tablonuzu redefinitiona tanımladığınızda redef. bu tablonuzu materialized view çeviriyor ve datayı bu mv’un içine aktarıyor bu esnada orjinal tablonuzda da materialized view log olusturup tablonuza gelen insert,delete ve update işlemlerini kayit altina aliyor.

2.UYGULAMA

2.1. Tablonuz redefinition yapıp yapmamaya uygun olup olmadığımızı aşağıdaki sorgularla görebiliriz.

PK üstünden redefinition yapmak için.

SQL> EXEC DBMS_REDEFINITION.CAN_REDEF_TABLE('MVS', 'ISLEM_LOG',1);

ROWNUM üstünden redefinition yapmak için.

SQL> EXEC DBMS_REDEFINITION.CAN_REDEF_TABLE('MVS', 'ISLEM_LOG',2);

2.2. Tablonuz büyükse parallelliği açmanızı öneririm.

SQL> alter session force parallel dml parallel 32;
SQL> alter session force parallel query parallel 32;

2.3. Yeni tablomuzu orjinal tablodan farklı olarak partition ve compress özelliği ekleyerek oluşturuyoruz.

SQL> CREATE TABLE MVS.ISLEM_LOG_OLD
(
  LOG_ID               VARCHAR2(40 BYTE)        NOT NULL,
  LOG_YAPAN            VARCHAR2(40 BYTE),
  LOG_YAPILAN          VARCHAR2(40 BYTE),
  LOG_ISLEM_KATEGORI   VARCHAR2(25 BYTE),
  LOG_ISLEM            VARCHAR2(255 BYTE),
  LOG_ISLEM_SONUC      CHAR(1 BYTE),
  LOG_ACIKLAMA         VARCHAR2(1000 BYTE),
  LOG_SON_ISLEM_DAMGA  VARCHAR2(20 BYTE),
  LOG_IP               VARCHAR2(15 BYTE)
)
TABLESPACE AHBS_DATA_TS
PCTUSED    0
PCTFREE    10
INITRANS   1
MAXTRANS   255
STORAGE    (
            INITIAL          64K
            NEXT             1M
            MINEXTENTS       1
            MAXEXTENTS       UNLIMITED
            PCTINCREASE      0
            BUFFER_POOL      DEFAULT
           )
NOLOGGING
PARTITION BY RANGE (LOG_SON_ISLEM_DAMGA)
(  
  PARTITION ISLEMLOG_2009 VALUES LESS THAN ('20100101000000000')
    LOGGING
    COMPRESS FOR ARCHIVE HIGH  
    TABLESPACE LOG_TS
    PCTFREE    10
    INITRANS   1
    MAXTRANS   255
    STORAGE    (
                INITIAL          64K
                NEXT             1M
                MINEXTENTS       1
                MAXEXTENTS       UNLIMITED
                BUFFER_POOL      DEFAULT
               ),  
  PARTITION ISLEMLOG_2010 VALUES LESS THAN ('20110101000000000')
    LOGGING
    COMPRESS FOR  ARCHIVE HIGH
    TABLESPACE LOG_TS
    PCTFREE    10
    INITRANS   1
    MAXTRANS   255
    STORAGE    (
                INITIAL          64K
                NEXT             1M
                MINEXTENTS       1
                MAXEXTENTS       UNLIMITED
                BUFFER_POOL      DEFAULT
               ),  
  PARTITION ISLEMLOG_2011 VALUES LESS THAN ('20120101000000000')
    LOGGING
    COMPRESS FOR ARCHIVE HIGH
    TABLESPACE LOG_TS
    PCTFREE    10
    INITRANS   1
    MAXTRANS   255
    STORAGE    (
                INITIAL          64K
                NEXT             1M
                MINEXTENTS       1
                MAXEXTENTS       UNLIMITED
                BUFFER_POOL      DEFAULT
               ),  
  PARTITION ISLEMLOG_201201 VALUES LESS THAN ('20120201000000000')
    LOGGING
    COMPRESS FOR OLTP
    TABLESPACE LOG_TS
    PCTFREE    10
    INITRANS   1
    MAXTRANS   255
    STORAGE    (
                INITIAL          64K
                NEXT             1M
                MINEXTENTS       1
                MAXEXTENTS       UNLIMITED
                BUFFER_POOL      DEFAULT
               ),  
  PARTITION ISLEMLOG_201202 VALUES LESS THAN ('20120301000000000')
    LOGGING
    COMPRESS FOR OLTP
    TABLESPACE LOG_TS
    PCTFREE    10
    INITRANS   1
    MAXTRANS   255
    STORAGE    (
                INITIAL          64K
                NEXT             1M
                MINEXTENTS       1
                MAXEXTENTS       UNLIMITED
                BUFFER_POOL      DEFAULT
               ),  
  PARTITION ISLEMLOG_201203 VALUES LESS THAN ('20120401000000000')
    LOGGING
    COMPRESS FOR OLTP
    TABLESPACE LOG_TS
    PCTFREE    10
    INITRANS   1
    MAXTRANS   255
    STORAGE    (
                INITIAL          64K
                NEXT             1M
                MINEXTENTS       1
                MAXEXTENTS       UNLIMITED
                BUFFER_POOL      DEFAULT
               ),  
  PARTITION ISLEMLOG_201204 VALUES LESS THAN ('20120501000000000')
    LOGGING
    COMPRESS FOR OLTP
    TABLESPACE LOG_TS
    PCTFREE    10
    INITRANS   1
    MAXTRANS   255
    STORAGE    (
                INITIAL          64K
                NEXT             1M
                MINEXTENTS       1
                MAXEXTENTS       UNLIMITED
                BUFFER_POOL      DEFAULT
               ),  
  PARTITION ISLEMLOG_201205 VALUES LESS THAN ('20120601000000000')
    LOGGING
    COMPRESS FOR OLTP
    TABLESPACE LOG_TS
    PCTFREE    10
    INITRANS   1
    MAXTRANS   255
    STORAGE    (
                INITIAL          64K
                NEXT             1M
                MINEXTENTS       1
                MAXEXTENTS       UNLIMITED
                BUFFER_POOL      DEFAULT
               ),  
  PARTITION ISLEMLOG_201206 VALUES LESS THAN ('20120701000000000')
    LOGGING
    COMPRESS FOR OLTP
    TABLESPACE LOG_TS
    PCTFREE    10
    INITRANS   1
    MAXTRANS   255
    STORAGE    (
                INITIAL          64K
                NEXT             1M
                MINEXTENTS       1
                MAXEXTENTS       UNLIMITED
                BUFFER_POOL      DEFAULT
               ),  
  PARTITION ISLEMLOG_201207 VALUES LESS THAN ('20120801000000000')
    LOGGING
    COMPRESS FOR OLTP
    TABLESPACE LOG_TS
    PCTFREE    10
    INITRANS   1
    MAXTRANS   255
    STORAGE    (
                INITIAL          64K
                NEXT             1M
                MINEXTENTS       1
                MAXEXTENTS       UNLIMITED
                BUFFER_POOL      DEFAULT
               ),  
)
COMPRESS FOR OLTP  
NOCACHE
NOPARALLEL
MONITORING;

2.4. Artık redefinition işlemine başlayabiliriz.Start_redef_table tanımları sırasıyla şu şekilde (‘schema_ismi’,'orjinal_tablo’,'yeni_tablo’,'orjinal_tablo_kolon1 yeni_tablo_kolon1,orjinal_tablo_kolon2 yeni_tablo_kolon2, …..) diye gitmekte.Bu işlem bittiğinde var olan datalar yeni tablonuza aktarılmış olacak,aktarılmamış olanlarda materilized view log da saklanıcaklar.Eğer tablonuzda Pk bulunmuyorsa ROWNUM üstünden redef işinizi tamamlamanız gerekir.

PK üstünden redefinition başlatmak için.

SQL> exec dbms_redefinition.start_redef_table('MVS','ISLEM_LOG','ISLEM_LOG_OLD','LOG_ID LOG_ID, LOG_YAPAN LOG_YAPAN, LOG_YAPILAN LOG_YAPILAN,LOG_ISLEM_KATEGORI LOG_ISLEM_KATEGORI,LOG_ISLEM LOG_ISLEM,LOG_ISLEM_SONUC LOG_ISLEM_SONUC,LOG_ACIKLAMA LOG_ACIKLAMA,LOG_SON_ISLEM_DAMGA LOG_SON_ISLEM_DAMGA,LOG_IP LOG_IP');

ROWNUM üstünden redefinition başlatmak için.

SQL> exec dbms_redefinition.start_redef_table('MVS','ISLEM_LOG','ISLEM_LOG_OLD','LOG_ID LOG_ID, LOG_YAPAN LOG_YAPAN, LOG_YAPILAN LOG_YAPILAN,LOG_ISLEM_KATEGORI LOG_ISLEM_KATEGORI,LOG_ISLEM LOG_ISLEM,LOG_ISLEM_SONUC LOG_ISLEM_SONUC,LOG_ACIKLAMA LOG_ACIKLAMA,LOG_SON_ISLEM_DAMGA LOG_SON_ISLEM_DAMGA,LOG_IP LOG_IP',2);

2.5. Data taşıma işlemini bitirdiğimize göre orjinal tablodaki index,trigger,cons. ve grant gibi özellikleride yeni tablomuza taşıyabiliriz.Bu işlemi aşağıdaki gibi yada manuel olarak yapabilirsiniz.

SQL> DECLARE
num_errors PLS_INTEGER;
BEGIN
DBMS_REDEFINITION.COPY_TABLE_DEPENDENTS('MVS','ISLEM_LOG','ISLEM_LOG_OLD',DBMS_REDEFINITION.CONS_ORIG_PARAMS,TRUE, TRUE, TRUE, FALSE, num_errors, TRUE);
END;
/

2.6. Redefinition işlemini uzun tutup bitirmemeniz gereken durumlar oluşabiliyor eğer aradaki süre çok açılırsa son adım olan finish_redef_table uzun sürebiliyor bu tarz durumlarda sync işlemini yapmanızda yarar var.

SQL> BEGIN
DBMS_REDEFINITION.SYNC_INTERIM_TABLE('MVS','ISLEM_LOG','ISLEM_LOG_OLD');
END;
/

2.7. Redef. işlemini artık bitirebiliriz. Bu komuttan sonra orjinal tablonuzla yeni tablonuz rename yapıp birbirlerinin yerine geçiceklerdir.

SQL> BEGIN
DBMS_REDEFINITION.FINISH_REDEF_TABLE('MVS','ISLEM_LOG','ISLEM_LOG_OLD');
END;
/

2.8. Redefinition işlemini iptal etmek için aşağıdaki komutu kullanabilirsiniz.

SQL> exec DBMS_REDEFINITION.ABORT_REDEF_TABLE('MVS', 'ISLEM_LOG', 'ISLEM_LOG_OLD')

The post Oracle Table Redefinition appeared first on Bugra Canbakal's Oracle Blog.