jump to navigation

Solusi Backup Linux [2] September 7, 2009

Posted by setijoagus in Linux.
Tags: ,
add a comment

B. Mengenal rdiff-backup

A remote incremental backup of all your files could be as easy as “rdiff-backup / host.net::/target-dir”

‘rdiff-backup backs up one directory to another, possibly over a network. The target directory ends up a copy of the source directory, but extra reverse diffs are stored in a special subdirectory of that target directory, so you can still recover files lost some time ago. The idea is to combine the best features of a mirror and an incremental backup. rdiff-backup also preserves subdirectories, hard links, dev files, permissions, uid/gid ownership, modification times, extended attributes, acls, and resource forks. Also, rdiff-backup can operate in a bandwidth efficient manner over a pipe, like rsync. Thus you can use rdiff-backup and ssh to securely back a hard drive up to a remote location, and only the differences will be transmitted. Finally, rdiff-backup is easy to use and settings have sensical defaults.’

mulai menggunakan
1. download [saya menggunakan centos 4.7]
ftp://fr.rpmfind.net/linux/dag/redhat/el4/en/i386/dag/RPMS/rdiff-backup-1.2.8-1.el4.rf.i386.rpm

2. install
[root@linux ~]# rpm -ivh rdiff-backup-1.2.8-1.el4.rf.i386.rpm
warning: rdiff-backup-1.2.8-1.el4.rf.i386.rpm: V3 DSA signature: NOKEY, key ID 6b8d79e6
Preparing… ########################################### [100%]
1:rdiff-backup ########################################### [100%]

3. perintah – perintah rdiff-backup
==========================================================
3a. untuk backup : /usr/bin/rdiff-backup [yang_dibackup] [lokasi_backup]
==========================================================
[root@linux s11]# ls -la /s11/foto_logistik/*.txt
-rw-r–r– 1 root foto_logistik 11 Sep 2 13:43 /s11/foto_logistik/test.txt
[root@linux s11]# /usr/bin/rdiff-backup /s11/ /backup/s11


==========================================================
3b. untuk list backup : /usr/bin/rdiff-backup -l [lokasi_backup]
==========================================================
[root@linux /]# /usr/bin/rdiff-backup -l /backup/s11/
Found 4 increments:
increments.2009-09-02T13:14:11+07:00.dir Wed Sep 2 13:14:11 2009
increments.2009-09-02T13:28:06+07:00.dir Wed Sep 2 13:28:06 2009
increments.2009-09-02T13:44:04+07:00.dir Wed Sep 2 13:44:04 2009
increments.2009-09-02T13:51:29+07:00.dir Wed Sep 2 13:51:29 2009
Current mirror: Wed Sep 2 14:30:02 2009


==========================================================
3c. untuk restore : /usr/bin/rdiff-backup -r now [lokasi_backup] [lokasi_restore]
==========================================================
[root@linux s11]# /usr/bin/rdiff-backup -r now /backup/s11/foto_logistik/test.txt /s11/foto_logistik/test.txt
[root@linux s11]# /usr/bin/rdiff-backup -r now /backup/s11/foto_logistik/test.txt /s11/foto_logistik/test2.txt
[root@linux s11]# ls -la /s11/foto_logistik/*.txt
-rw-r–r– 1 root foto_logistik 11 Sep 2 13:43 /s11/foto_logistik/test2.txt
-rw-r–r– 1 root foto_logistik 11 Sep 2 13:43 /s11/foto_logistik/test.txt


==========================================================
3d. untuk restore : /usr/bin/rdiff-backup -r [jam tertentu] [lokasi_backup] [lokasi_restore]
==========================================================
[root@linux /]# rdiff-backup -r 2009-09-02T13:44:04+07:00 /backup/s11/foto_logistik/test.txt /s11/foto_logistik/test3.txt
[root@linux /]# rdiff-backup -r 2009-09-02T13:51:29+07:00 /backup/s11/foto_logistik/test.txt /s11/foto_logistik/test4.txt
[root@linux /]# rdiff-backup -r now /backup/s11/foto_logistik/test.txt /s11/foto_logistik/test5.txt

==========================================================
3e. hapus archive
==========================================================
[root@linux s11]# /usr/bin/rdiff-backup –remove-older-than 3D /backup/s11

Solusi Backup Linux [1] September 7, 2009

Posted by setijoagus in Linux.
Tags: , ,
add a comment

A. Awal Mula
Dulu saya melakukan backup di linux menggunakan tar, dimana saya buatkan script seperti berikut :
=============================================================
script backup tar
=============================================================
# .bash_profile
cd /backup
b_name=`date +%w`
if [ "$b_name" = 1 -o "$b_name" = 4 ]
then
tar cvzf /backup/ac/01snkm_acumum.tgz /s03/ac/umum -X no_file > logac_umum.txt
elif [ "$b_name" = 2 -o "$b_name" = 5 ]
then
tar cvzf /backup/ac/02sljm_acumum.tgz /s03/ac/umum -X no_file > logac_umum.txt
elif [ "$b_name" = 3 -o "$b_name" = 6 ]
then
tar cvzf /backup/ac/03rbst_acumum.tgz /s03/ac/umum -X no_file > logac_umum.txt
elif [ "$b_name" = 0 ]
then
tar cvzf /backup/ac/04mg_acumum.tgz /s03/ac/umum -X no_file > logac_umum.txt
fi

artinya dalam 1 minggu saya memiliki file :
/backup/ac/01snkm_acumum.tgz
/backup/ac/02sljm_acumum.tgz
/backup/ac/03rbst_acumum.tgz
/backup/ac/04mg_acumum.tgz

1. Cara ini sudah lama saya gunakan dan saya nyaman, untuk restore dengan menggunakan ‘mc’, saya bisa pilih file yang hanya akan direstore.
2. Sejalan dengan waktu hasil ‘tar’ menjadi semakin besar cara restore dengan menggunakan ‘mc’, menjadi tidak bisa, terpaksa dech ……..
3. Menggunakan cara ‘tar xvf’, kemudian baru direstore file yang rusak/diinginkan/hilang
4. waktu terus berlalu, file hasil ‘tar’ semakin membesar, pada saat ,menjalankan ‘tar xvf’, timbul error
tar: This does not look like a tar archive
tar: Skipping to next header
tar: Archive contains obsolescent base-64 headers
5. Tapi hal ini masih dapat diatasi dengan menggunakan ‘gzip -d’ baru kemudian ‘tar -xvf’ “thank’s to Jesus”
6. 3 bulan terakhir ada Komplain, pada saat schedulle backup berjalan [8 malam s/d 5 pagi], akses jadi lambat, bahkan backup masih berjalan sampai dengan jam 8 pagi baru selesai [serasa nggak ada jalan keluar]

ADVANCE REPLIKASI with LIMITED BANDWIDTH Agustus 29, 2009

Posted by setijoagus in Mikrotik, REPLICATION, oracle.
Tags: , ,
1 comment so far

Seberapa banyak bandwidth yang dibutuhkan untuk melakukan replikasi sebenarnya ?, sejujurnya saya juga nggak tahu, walaupun pertimbangannya adalah berapa banyak jumlah transaksi yang terjadi dalam satuan waktu tertentu.
Berikut saya melakukan percobaan kecil – kecilan dengan kondisi seperti skema ini

replication_01
dari hasil test bandwidth yang sudah saya lakukan didapat angka bandwidth yang tidak pernah mencapai lebih dari 16 Kbps

replication_02
Test segera dimulai
a. Pada server ORCL1, dilakukan perintah insert
SQL> insert into dept values (51,’dept’,'dept’);
SQL> insert into dept values (52,’dept’,'dept’);
………………………………………..
SQL> insert into dept values (96,’dept’,'dept’);
SQL> insert into dept values (97,’dept’,'dept’);
SQL> insert into dept values (98,’dept’,'dept’);
SQL> insert into dept values (99,’dept’,'dept’);
SQL> commit;

SQL> select to_char(sysdate, ‘Dy DD-Mon-YYYY HH24:MI:SS’) as “Time” from dual;
Time
————————
Sat 29-Aug-2009 14:44:40

SQL> select * from dept order by deptno;
DEPTNO DNAME LOC
———- ————– ————-
10 ACCOUNTING NEW YORK
20 RESEARCH DALLAS
30 SALES CHICAGO
40 OPERATIONS BOSTON
51 dept dept
52 dept dept
53 dept dept
54 dept dept
55 dept dept
56 dept dept
57 dept dept
58 dept dept
………………….
97 dept dept
98 dept dept
99 dept dept
53 rows selected.

b. Pada server ORCL2, beberapa saat kemudian [belum terjadi replikasi data]
SQL> select to_char(sysdate, ‘Dy DD-Mon-YYYY HH24:MI:SS’) as “Time” from dual;
Time
————————
Sat 29-Aug-2009 14:45:34

SQL> select * from dept order by deptno;
DEPTNO DNAME LOC
———- ————– ————-
10 ACCOUNTING NEW YORK
20 RESEARCH DALLAS
30 SALES CHICAGO
40 OPERATIONS BOSTON

c. Pada server ORCL2, dulangi langkah diatas [sudah terjadi replikasi data]
SQL> select to_char(sysdate, ‘Dy DD-Mon-YYYY HH24:MI:SS’) as “Time” from dual;
Time
————————
Sat 29-Aug-2009 14:45:36

SQL> select * from dept order by deptno;
DEPTNO DNAME LOC
———- ————– ————-
10 ACCOUNTING NEW YORK
20 RESEARCH DALLAS
30 SALES CHICAGO
40 OPERATIONS BOSTON
51 dept dept
52 dept dept
53 dept dept
54 dept dept
55 dept dept
56 dept dept
57 dept dept
58 dept dept
………………….
97 dept dept
98 dept dept
99 dept dept
53 rows selected.

jadi [Sat 29-Aug-2009 14:24:40] – [Sat 29-Aug-2009 14:25:36] = 56 detik
jadi 53 rows – 4 rows = 49 rows

d. Pada server ORCL1, dilakukan perintah delete
SQL> delete dept where deptno > 40;
49 rows deleted.
SQL> commit;
Commit complete.
SQL> select to_char(sysdate, ‘Dy DD-Mon-YYYY HH24:MI:SS’) as “Time” from dual;
Time
————————
Sat 29-Aug-2009 14:34:17
SQL> select * from dept order by deptno;
DEPTNO DNAME LOC
———- ————– ————-
10 ACCOUNTING NEW YORK
20 RESEARCH DALLAS
30 SALES CHICAGO
40 OPERATIONS BOSTON

e. Pada server ORCL2, beberapa saat kemudian
SQL> select to_char(sysdate, ‘Dy DD-Mon-YYYY HH24:MI:SS’) as “Time” from dual;
Time
————————
Sat 29-Aug-2009 14:34:35

SQL> select * from dept order by deptno;
DEPTNO DNAME LOC
———- ————– ————-
10 ACCOUNTING NEW YORK
20 RESEARCH DALLAS
30 SALES CHICAGO
40 OPERATIONS BOSTON
51 dept dept
52 dept dept
53 dept dept
54 dept dept
55 dept dept
56 dept dept
57 dept dept
58 dept dept
………………….
97 dept dept
98 dept dept
99 dept dept
53 rows selected.

f. Pada server ORCL2, dulangi langkah diatas
SQL> select to_char(sysdate, ‘Dy DD-Mon-YYYY HH24:MI:SS’) as “Time” from dual;
Time
————————
Sat 29-Aug-2009 14:34:36
SQL> select * from dept order by deptno;
DEPTNO DNAME LOC
———- ————– ————-
10 ACCOUNTING NEW YORK
20 RESEARCH DALLAS
30 SALES CHICAGO
40 OPERATIONS BOSTON

jadi [Sat 29-Aug-2009 14:34:17] – [Sat 29-Aug-2009 14:34:36] = 19 detik
jadi 53 rows – 4 rows = 49 rows

Create Advance Replication [AGAIN & SIMPLE] Agustus 29, 2009

Posted by setijoagus in REPLICATION, oracle.
Tags: ,
add a comment

Ini tulisan Create Advance Replication, yang ketiga kali di blog ini, ada beberapa pertanyaan soal create replikasi yang sulit.
Berikut cara cepat create replikasi [2 server Oracle, tabel scott.DEPT & scott.EMP] , dengan syarat :
a. 2 oracle db server telah disetup dengan nama SID = ORCL1 & ORCL2
b. 2 oracle db telah startup
c. tnsnames.ora di masing – masing server telah tersetup dengan benar, contoh

Picture0001d. jalankan script, di ORCL1

Picture0002e. periksa apakah replikasi sudah bisa dieksekusi ?, jika COUNT masih belum bernilai = 0, maka replikasi belum dpt dijalankan

Picture0003f. tunggu beberapa saat, periksa kembali sampai dengan COUNT bernilai = 0

Picture0004g. start replikasi

Picture0005e. lampiran script bikin_replikasi.sql
————————————————————————
– orcl1 orcl1 orcl1 orcl1 orcl1 orcl1 orcl1 orcl1 orcl1 orcl1 orcl1
————————————————————————
– 1. unlock user scott & setup global
————————————————————————
conn system/oracle007@orcl1
alter user scott account unlock;
alter user scott identified by tiger;
conn scott/tiger;

conn system/oracle007@orcl1
alter system set global_names=TRUE;
alter system set job_queue_processes = 1;

————————————————————————
– 2. create admin replikasi
– Grant privs to the propagator, to propagate changes to remote sites
– Grant privs to the receiver to apply deferred transactions
– Authorise the administrator to administer replication groups and schemas
————————————————————————
CREATE USER repadmin IDENTIFIED BY repadmin;

BEGIN
DBMS_REPCAT_ADMIN.GRANT_ADMIN_ANY_SCHEMA (
username => ‘repadmin’);
END;
/

GRANT SELECT ANY DICTIONARY TO repadmin;

BEGIN
DBMS_DEFER_SYS.REGISTER_PROPAGATOR (
username => ‘repadmin’);
END;
/

BEGIN
DBMS_REPCAT_ADMIN.REGISTER_USER_REPGROUP (
username => ‘repadmin’,
privilege_type => ‘receiver’,
list_of_gnames => NULL);
END;
/

————————————————————————————-
– 3. Schedule job to purge
————————————————————————————-
CONNECT repadmin/repadmin@orcl1
BEGIN
DBMS_DEFER_SYS.SCHEDULE_PURGE (
next_date => SYSDATE,
– interval 1 menit
interval => ’sysdate + 1*(1/(24*60))’,
delay_seconds => 0);
END;
/

————————————————————————
– 4. Create private db links for all repadmin users
————————————————————————
conn system/oracle007@orcl1
create public database link orcl2 using ‘orcl2′;
conn repadmin/repadmin@orcl1
create database link orcl2 connect to repadmin identified by repadmin;

————————————————————————
– 5. Schedule job to push
————————————————————————
conn repadmin/repadmin@orcl1
BEGIN
DBMS_DEFER_SYS.SCHEDULE_PUSH (
destination => ‘orcl2′,
– interval 1 menit
interval => ’sysdate + 1*(1/(24*60))’,
next_date => SYSDATE,
parallelism => 1,
execution_seconds => 1500,
delay_seconds => 1200);
END;
/

————————————————————————
– 6. Create replication group for MASTERDEF site
– Register objects within the group
————————————————————————
conn repadmin/repadmin@orcl1
begin
dbms_repcat.create_master_repgroup (
gname => ’scott_repg’);
end;
/

BEGIN
DBMS_REPCAT.CREATE_MASTER_REPOBJECT (
gname => ’scott_repg’,
type => ‘TABLE’,
oname => ‘EMP’,
sname => ’scott’,
use_existing_object => TRUE,
copy_rows => FALSE);
END;
/

BEGIN
DBMS_REPCAT.CREATE_MASTER_REPOBJECT (
gname => ’scott_repg’,
type => ‘TABLE’,
oname => ‘DEPT’,
sname => ’scott’,
use_existing_object => TRUE,
copy_rows => FALSE);
END;
/

conn repadmin/repadmin@orcl1
BEGIN
DBMS_REPCAT.GENERATE_REPLICATION_SUPPORT (
sname => ’scott’,
oname => ‘emp’,
type => ‘TABLE’,
min_communication => TRUE);
END;
/

BEGIN
DBMS_REPCAT.GENERATE_REPLICATION_SUPPORT (
sname => ’scott’,
oname => ‘dept’,
type => ‘TABLE’,
min_communication => TRUE);
END;
/

————————————————————————
– orcl2 orcl2 orcl2 orcl2 orcl2 orcl2 orcl2 orcl2 orcl2 orcl2 orcl2
————————————————————————
– 6. unlock user scott & setup global
————————————————————————
conn system/oracle007@orcl2
alter user scott account unlock;
alter user scott identified by tiger;
conn scott/tiger;

conn system/oracle007@orcl2
alter system set global_names=TRUE;
alter system set job_queue_processes = 1;

————————————————————————
– 7. create admin replikasi
– Grant privs to the propagator, to propagate changes to remote sites
– Grant privs to the receiver to apply deferred transactions
– Authorise the administrator to administer replication groups and schemas
————————————————————————
CREATE USER repadmin IDENTIFIED BY repadmin;

BEGIN
DBMS_REPCAT_ADMIN.GRANT_ADMIN_ANY_SCHEMA (
username => ‘repadmin’);
END;
/

GRANT SELECT ANY DICTIONARY TO repadmin;

BEGIN
DBMS_DEFER_SYS.REGISTER_PROPAGATOR (
username => ‘repadmin’);
END;
/

BEGIN
DBMS_REPCAT_ADMIN.REGISTER_USER_REPGROUP (
username => ‘repadmin’,
privilege_type => ‘receiver’,
list_of_gnames => NULL);
END;
/

————————————————————————————-
– 8. Schedule job to purge
————————————————————————————-
CONNECT repadmin/repadmin@orcl2
BEGIN
DBMS_DEFER_SYS.SCHEDULE_PURGE (
next_date => SYSDATE,
– interval 1 menit
interval => ’sysdate + 1*(1/(24*60))’,
delay_seconds => 0);
END;
/

————————————————————————
– 9. Create private db links for all repadmin users
————————————————————————
conn system/oracle007@orcl2
create public database link orcl1 using ‘orcl1′;
conn repadmin/repadmin@orcl2
create database link orcl1 connect to repadmin identified by repadmin;

————————————————————————
– 10. Schedule job to push
————————————————————————
conn repadmin/repadmin@orcl2
BEGIN
DBMS_DEFER_SYS.SCHEDULE_PUSH (
destination => ‘orcl1′,
– interval 1 menit
interval => ’sysdate + 1*(1/(24*60))’,
next_date => SYSDATE,
parallelism => 1,
execution_seconds => 1500,
delay_seconds => 1200);
END;
/

————————————————————————
– 11. Add master desination sites
————————————————————————
conn repadmin/repadmin@orcl1
BEGIN
DBMS_REPCAT.ADD_MASTER_DATABASE (
gname => ’scott_repg’,
master => ‘orcl2′,
use_existing_objects => TRUE,
copy_rows => FALSE,
propagation_mode => ‘ASYNCHRONOUS’);
END;
/

Demo Advance Replication with Metode Conflicts Resolution Agustus 29, 2009

Posted by setijoagus in REPLICATION, oracle.
Tags: , , ,
add a comment

Setelah dilakukan perubahan pada setting Advance Replication, terutama dengan penambahan kolom TIMESTAMP, seperti yang terlihat pada gambar di bawah ini
Picture001
Sekarang waktunya untuk melakukan test.
a. di sisi server ORCL1 dilakukan perubahan data pada baris yang bersesuaian
SQL> conn scott/tiger@orcl2
SQL> update dept set dname = ‘ORCL1′, timestamp = systimestamp
where deptno = 40 ;
SQL> commit;

b. demikiam juga di sisi server ORCL2 dilakukan perubahan data pada baris yang bersesuaian
SQL> conn scott/tiger@orcl1
SQL> update dept set dname = ‘ORCL1′, timestamp = systimestamp
where deptno = 40 ;
SQL> commit;

c. setelah dilakukan test hasilnya seperti terlihat dibawah ini, terlihat ada perbedaan isi.
Picture002d. beberapa saat kemudian hasil yang dianggap valid adalah “LATEST TIMESTAMP” pada orcl1, yang pada akhirnya terupdate hasil server ORCL2

Picture003

Create Advance Replication with Metode Conflicts Resolution Agustus 28, 2009

Posted by setijoagus in REPLICATION, oracle.
Tags: ,
add a comment

Untuk membuat agar tabel – tabel yang telah di replikasi, memiliki Metode Conflicts Resolution, maka perlu ada penambahan kolom, pada contoh di bawah ini ditunjukkan bagaimana membuat Metode Conflicts Resolution – LATEST TIMESTAMP.
Jika pada contoh http://www.dba-oracle.com/art_select_repl.pdf, menggunakan sysdate sebagai Metode Conflicts Resolution – LATEST TIMESTAMP, pada contoh ini saya menggunakan systimestamp.

a. siapkan terlebih dulu agar server – server memiliki ukuran waktu yang sama, bisa menggunakan teknologi ntp server, detail ntp server bisa dilihat di http://setijoagus.wordpress.com/2009/03/27/membangun-server-client-network-time-protocol-ntp/

setup_01

b. melakukan re-konfigurasi kembali agar server oracle support Metode Conflicts Resolution – LATEST TIMESTAMP, langkah – langkahnya :
1. stop replikasi
2. alter tabel TIMESTAMP
3. Register objects within the group
4. conflict resolution & column group
5. start replikasi

setup_02

setup_03

c. Script lengkap

————————————————————————
– orcl1 orcl1 orcl1 orcl1 orcl1 orcl1 orcl1 orcl1 orcl1 orcl1 orcl1
————————————————————————
– 1. stop replikasi
————————————————————————
CONNECT repadmin/repadmin@orcl1
BEGIN
DBMS_REPCAT.SUSPEND_MASTER_ACTIVITY (
gname => ’scott_repg’);
END;
/

————————————————————————
– 2. alter tabel TIMESTAMP
————————————————————————
BEGIN
DBMS_REPCAT.ALTER_MASTER_REPOBJECT (
sname => ’scott’,
oname => ‘emp’,
type => ‘TABLE’,
ddl_text => ‘ALTER TABLE SCOTT.EMP ADD (TIMESTAMP TIMESTAMP(6) WITH LOCAL TIME ZONE)’);
END;
/

BEGIN
DBMS_REPCAT.ALTER_MASTER_REPOBJECT (
sname => ’scott’,
oname => ‘dept’,
type => ‘TABLE’,
ddl_text => ‘ALTER TABLE SCOTT.DEPT ADD (TIMESTAMP TIMESTAMP(6) WITH LOCAL TIME ZONE)’);
END;
/

————————————————————————
– 3. Register objects within the group
————————————————————————
BEGIN
DBMS_REPCAT.GENERATE_REPLICATION_SUPPORT (
sname => ’scott’,
oname => ‘emp’,
type => ‘TABLE’,
min_communication => TRUE);
END;
/

BEGIN
DBMS_REPCAT.GENERATE_REPLICATION_SUPPORT (
sname => ’scott’,
oname => ‘dept’,
type => ‘TABLE’,
min_communication => TRUE);
END;
/

————————————————————————
– 4. conflict resolution & column group
————————————————————————
BEGIN
DBMS_REPCAT.CREATE_MASTER_REPOBJECT (
gname => ’scott_repg’,
type => ‘TRIGGER’,
oname => ‘insert_time’,
sname => ’scott’,
ddl_text => ‘CREATE OR REPLACE TRIGGER scott.insert_time
BEFORE
INSERT OR UPDATE ON scott.emp FOR EACH ROW
BEGIN
IF DBMS_REPUTIL.FROM_REMOTE = FALSE THEN
:NEW.TIMESTAMP := SYSTIMESTAMP;
END IF;
END;’);
END;
/

BEGIN
DBMS_REPCAT.CREATE_MASTER_REPOBJECT (
gname => ’scott_repg’,
type => ‘TRIGGER’,
oname => ‘insert_time2′,
sname => ’scott’,
ddl_text => ‘CREATE OR REPLACE TRIGGER scott.insert_time2
BEFORE
INSERT OR UPDATE ON scott.dept FOR EACH ROW
BEGIN
IF DBMS_REPUTIL.FROM_REMOTE = FALSE THEN
:NEW.TIMESTAMP := SYSTIMESTAMP;
END IF;
END;’);
END;
/

BEGIN
DBMS_REPCAT.MAKE_COLUMN_GROUP (
sname => ’scott’,
oname => ‘emp’,
column_group => ‘emp_timestamp_cg’,
list_of_column_names => ‘ename,job,mgr,hiredate,sal,comm,deptno,timestamp’);
END;
/

BEGIN
DBMS_REPCAT.MAKE_COLUMN_GROUP (
sname => ’scott’,
oname => ‘dept’,
column_group => ‘dept_timestamp_cg’,
list_of_column_names => ‘dname,loc,timestamp’);
END;
/

BEGIN
DBMS_REPCAT.ADD_UPDATE_RESOLUTION (
sname => ’scott’,
oname => ‘emp’,
column_group => ‘emp_timestamp_cg’,
sequence_no => 1,
method => ‘LATEST TIMESTAMP’,
parameter_column_name => ‘timestamp’);
END;
/

BEGIN
DBMS_REPCAT.ADD_UPDATE_RESOLUTION (
sname => ’scott’,
oname => ‘dept’,
column_group => ‘dept_timestamp_cg’,
sequence_no => 1,
method => ‘LATEST TIMESTAMP’,
parameter_column_name => ‘timestamp’);
END;
/

BEGIN
DBMS_REPCAT.GENERATE_REPLICATION_SUPPORT (
sname => ’scott’,
oname => ‘emp’,
type => ‘TABLE’,
min_communication => TRUE);
END;
/

BEGIN
DBMS_REPCAT.GENERATE_REPLICATION_SUPPORT (
sname => ’scott’,
oname => ‘dept’,
type => ‘TABLE’,
min_communication => TRUE);
END;
/

————————————————————————
– 5. start replikasi
————————————————————————
BEGIN
DBMS_REPCAT.RESUME_MASTER_ACTIVITY (
gname => ’scott_repg’);
END;
/

Advance Replication Metode Conflicts Resolution Agustus 28, 2009

Posted by setijoagus in REPLICATION, oracle.
Tags: , ,
add a comment

Menurut http://www.dba-oracle.com/art_select_repl.pdf, untuk mengatasi Conflicts, pada Advance Replication ada beberapa cara :
art_01

Latest Timestamp Value

art_02

Site Priority Value

art_03

MIKROTIK as a bandwidth management Agustus 28, 2009

Posted by setijoagus in Mikrotik, Network.
Tags: , ,
add a comment

16. klik Queues
mikrotik_a01

17. pada Tab Simple Queues –> klik +
isikan Name Queues : ALL NETWORK
isikan Target Address : 172.20.0.0/16

mikrotik_a02

18. pada Tab Simple Queues –> klik +
isikan Name Queues : PC.33.33
isikan Target Address : 172.20.33.33
Max Limit untuk upload dan download 64Kbps

mikrotik_a03

19. test dari komputer 172.20.33.33 & gunakan browser untuk mengakses bandwidthmeter, didapat hasil lebih dari 64 Kbps, hal ini terjadi karena maximal untuk upload dan download mengikuti Queues : ALL NETWORK.
artinya pada saat bandwidth secara keseluruhan Queues ALL NETWORK belum maximal, maka Queues : PC.33.33, dapat menggunakan semaximal mungkin bandwidth yang ada.

mikrotik_a04

20. hapus Queues ALL NETWORK, sehingga pada Simple Queues hanya terdapat Queues : PC.33.33

21. hasil yang didaptkan dibawah 64Kbps

mikrotik_a06

MIKROTIK as a BRIDGE Agustus 28, 2009

Posted by setijoagus in Mikrotik, Network.
Tags: ,
add a comment

LAN 1 [dengan ip : 172.20.0.0/16] akan dihubungkan LAN 2 [juga dengan ip : 172.20.0.0/16], LAN 1 bisa diganti sebagai router yang connect ke internet
mikrotik_00

1. lewat WinBox akan dikonfigurasi MIKROTIK sebagai BRIDGE
mikrotik_01
2. dari menu klik Interface, terlihat 2 ethernet
mikrotik_02
3. setup ip, dari menu klik IP –> klik Address –> klik + –> isikan alamat ip
untuk ether 1 172.20.2.21
mikrotik_03
4. untuk ether 2 172.20.2.22
mikrotik_04
5. setup bridge, dari menu klik Bridge
mikrotik_05
6. klik + –> isikan [default]
mikrotik_06
7. tab pindah ke Port –> + –> isikan [default] dengan ether1
mikrotik_07
8. ulangi langkah 6 untuk ether2
mikrotik_08

9. setup router, dari menu klik IP –> klik Routes
mikrotik_09
10. klik +
isikan destination : 172.20.0.0/16
isikan gateway : 172.20.114.73 [sesuaikan, sbg contoh gateway di jaringan LAN 1]
mikrotik_10
11. testing dari mikrotik, dari menu klik Tools –> klik Ping
mikrotik_11
12. ping ke 172.20.140.31
mikrotik_12
13. ping ke 172.20.140.33
mikrotik_13
14. testing dari client LAN 2, ping ke anggota client di LAN 1
mikrotik_14
15. testing dari client LAN 1, ping ke anggota client di LAN 2
mikrotik_15

Advance Replication Conflicts Agustus 27, 2009

Posted by setijoagus in REPLICATION, oracle.
Tags:
add a comment

menurut http://download-east.oracle.com/docs/cd/B13789_01/server.101/b10732/repconfl.htm , jika menggunakan Advance Replication maka akan terjadi Conflict, type – tye conflict yang mungkin terjadi adalah :
1. Uniqueness Conflicts
2. Update Conflicts
3. Delete Conflicts

contoh Uniqueness Conflicts
misalkan pada saat bersamaan [selisih milli second / second / belum sampai schedulle push terjadi] di sisi kantor pusat [sid = orcl1] dengan kantor cabang [sid = orcl2], dilakukan insert data dengan kolom PK yang sama
SQL> conn scott/tiger@orcl1
SQL> insert into dept values (60,’orcl1′,’orcl1′);
SQL> commit;

SQL> conn scott/tiger@orcl2
SQL> insert into dept values (60,’orcl2′,’orcl2′);
SQL> commit;

maka akan terjadi Uniqueness Conflicts
replikasi_conflicts_01

replikasi_conflicts_02

replikasi_conflicts_03