Scribd
Upload
11 views3 pages

Class Notes

Supplemental logging enhances redo logs by adding extra columns to uniquely identify rows, with two types: database level and table/object level. The document outlines commands for enabling supplemental logging and managing trail files for data replication between databases. It also provides examples of updating data and the naming conventions for trail files.

Uploaded by

Rajshekhariah Umesh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
11 views3 pages

Class Notes

Supplemental logging enhances redo logs by adding extra columns to uniquely identify rows, with two types: database level and table/object level. The document outlines commands for enabling supplemental logging and managing trail files for data replication between databases. It also provides examples of updating data and the naming conventions for trail files.

Uploaded by

Rajshekhariah Umesh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

Supplemetal Logging is of two types:

1. Database Level - alter database add supplemental log data(all) columns;


2. table Level/Object Level

SQL>
alter table ggtraining1.dept11 add supplemental log data (PK|UK|ALL) columns;

GGSCI>
add trandata pdb1.ggtraining1.dept11
add trandata pdb1.ggtraining1.dept11,cols (dname,loc)

add schematrandata pdb1.ggtraining1


1000

5 tables-1005

Supplemental logging adds an extra column into redo logs so that a row can be uniquely
identified.

dept11 --------------------------------------->dept22
Dno Dname loc Dno Dname loc
1 SALES CANADA 1 SALES CANADA
2 SALES INDIA 2 SALES INDIA
3 HR INDIA 3 HR INDIA

update dept11 set


loc='AUS' where
dno=2;
commit;

2 SALES Aus 2 SALES Aus

BI: 2,India
AI: 2,Aus

Supplemental logging is enabled in below order:


1. PK
2. UK
3. All

Customized column

200 columns

pdb1.ggtraining1.dept11--->pdb2.ggtraining2.dept22
pdb1.ggtraining1.emp11--->pdb2.ggtraining2.emp22

naming convention of trail files:

dirdat directory
2 characters
aa000000000
aa000000001
aa000000002
ab
ac
at
zz
zu

lt
rt

add exttrail /data/app/oracle/ogg_src/dirdat/lt,extract extint19

add extract dpint19,exttrailsource /data/app/oracle/ogg_src/dirdat/lt

add rmttrail /data/app/oracle/ogg_trg/dirdat/rt,extract dpint19


RMTTRAIL added.
register etract extin19,database container(pdb1,pdb2)

You might also like