\documentclass[11pt,twoside]{article}\makeatletter

\IfFileExists{xcolor.sty}%
  {\RequirePackage{xcolor}}%
  {\RequirePackage{color}}
\usepackage{colortbl}
\usepackage{wrapfig}
\usepackage{ifxetex}
\ifxetex
  \usepackage{fontspec}
  \usepackage{xunicode}
  \catcode`⃥=\active \def⃥{\textbackslash}
  \catcode`❴=\active \def❴{\{}
  \catcode`❵=\active \def❵{\}}
  \def\textJapanese{\fontspec{Noto Sans CJK JP}}
  \def\textChinese{\fontspec{Noto Sans CJK SC}}
  \def\textKorean{\fontspec{Noto Sans CJK KR}}
  \setmonofont{DejaVu Sans Mono}
  
\else
  \IfFileExists{utf8x.def}%
   {\usepackage[utf8x]{inputenc}
      \PrerenderUnicode{–}
    }%
   {\usepackage[utf8]{inputenc}}
  \usepackage[english]{babel}
  \usepackage[T1]{fontenc}
  \usepackage{float}
  \usepackage[]{ucs}
  \uc@dclc{8421}{default}{\textbackslash }
  \uc@dclc{10100}{default}{\{}
  \uc@dclc{10101}{default}{\}}
  \uc@dclc{8491}{default}{\AA{}}
  \uc@dclc{8239}{default}{\,}
  \uc@dclc{20154}{default}{ }
  \uc@dclc{10148}{default}{>}
  \def\textschwa{\rotatebox{-90}{e}}
  \def\textJapanese{}
  \def\textChinese{}
  \IfFileExists{tipa.sty}{\usepackage{tipa}}{}
\fi
\def\exampleFont{\ttfamily\small}
\DeclareTextSymbol{\textpi}{OML}{25}
\usepackage{relsize}
\RequirePackage{array}
\def\@testpach{\@chclass
 \ifnum \@lastchclass=6 \@ne \@chnum \@ne \else
  \ifnum \@lastchclass=7 5 \else
   \ifnum \@lastchclass=8 \tw@ \else
    \ifnum \@lastchclass=9 \thr@@
   \else \z@
   \ifnum \@lastchclass = 10 \else
   \edef\@nextchar{\expandafter\string\@nextchar}%
   \@chnum
   \if \@nextchar c\z@ \else
    \if \@nextchar l\@ne \else
     \if \@nextchar r\tw@ \else
   \z@ \@chclass
   \if\@nextchar |\@ne \else
    \if \@nextchar !6 \else
     \if \@nextchar @7 \else
      \if \@nextchar (8 \else
       \if \@nextchar )9 \else
  10
  \@chnum
  \if \@nextchar m\thr@@\else
   \if \@nextchar p4 \else
    \if \@nextchar b5 \else
   \z@ \@chclass \z@ \@preamerr \z@ \fi \fi \fi \fi
   \fi \fi  \fi  \fi  \fi  \fi  \fi \fi \fi \fi \fi \fi}
\gdef\arraybackslash{\let\\=\@arraycr}
\def\@textsubscript#1{{\m@th\ensuremath{_{\mbox{\fontsize\sf@size\z@#1}}}}}
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\def\abbr{}
\def\corr{}
\def\expan{}
\def\gap{}
\def\orig{}
\def\reg{}
\def\ref{}
\def\sic{}
\def\persName{}\def\name{}
\def\placeName{}
\def\orgName{}
\def\textcal#1{{\fontspec{Lucida Calligraphy}#1}}
\def\textgothic#1{{\fontspec{Lucida Blackletter}#1}}
\def\textlarge#1{{\large #1}}
\def\textoverbar#1{\ensuremath{\overline{#1}}}
\def\textquoted#1{‘#1’}
\def\textsmall#1{{\small #1}}
\def\textsubscript#1{\@textsubscript{\selectfont#1}}
\def\textxi{\ensuremath{\xi}}
\def\titlem{\itshape}
\newenvironment{biblfree}{}{\ifvmode\par\fi }
\newenvironment{bibl}{}{}
\newenvironment{byline}{\vskip6pt\itshape\fontsize{16pt}{18pt}\selectfont}{\par }
\newenvironment{citbibl}{}{\ifvmode\par\fi }
\newenvironment{docAuthor}{\ifvmode\vskip4pt\fontsize{16pt}{18pt}\selectfont\fi\itshape}{\ifvmode\par\fi }
\newenvironment{docDate}{}{\ifvmode\par\fi }
\newenvironment{docImprint}{\vskip 6pt}{\ifvmode\par\fi }
\newenvironment{docTitle}{\vskip6pt\bfseries\fontsize{22pt}{25pt}\selectfont}{\par }
\newenvironment{msHead}{\vskip 6pt}{\par}
\newenvironment{msItem}{\vskip 6pt}{\par}
\newenvironment{rubric}{}{}
\newenvironment{titlePart}{}{\par }

\newcolumntype{L}[1]{){\raggedright\arraybackslash}p{#1}}
\newcolumntype{C}[1]{){\centering\arraybackslash}p{#1}}
\newcolumntype{R}[1]{){\raggedleft\arraybackslash}p{#1}}
\newcolumntype{P}[1]{){\arraybackslash}p{#1}}
\newcolumntype{B}[1]{){\arraybackslash}b{#1}}
\newcolumntype{M}[1]{){\arraybackslash}m{#1}}
\definecolor{label}{gray}{0.75}
\def\unusedattribute#1{\sout{\textcolor{label}{#1}}}
\DeclareRobustCommand*{\xref}{\hyper@normalise\xref@}
\def\xref@#1#2{\hyper@linkurl{#2}{#1}}
\begingroup
\catcode`\_=\active
\gdef_#1{\ensuremath{\sb{\mathrm{#1}}}}
\endgroup
\mathcode`\_=\string"8000
\catcode`\_=12\relax

\usepackage[a4paper,twoside,lmargin=1in,rmargin=1in,tmargin=1in,bmargin=1in,marginparwidth=0.75in]{geometry}
\usepackage{framed}

\definecolor{shadecolor}{gray}{0.95}
\usepackage{longtable}
\usepackage[normalem]{ulem}
\usepackage{fancyvrb}
\usepackage{fancyhdr}
\usepackage{graphicx}
\usepackage{marginnote}

\renewcommand{\@cite}[1]{#1}


\renewcommand*{\marginfont}{\itshape\footnotesize}

\def\Gin@extensions{.pdf,.png,.jpg,.mps,.tif}

  \pagestyle{fancy}

\usepackage[pdftitle={Maintenance Modification Algorithms and its Implementation on object oriented data warehouse},
 pdfauthor={}]{hyperref}
\hyperbaseurl{}

	 \paperwidth210mm
	 \paperheight297mm
              
\def\@pnumwidth{1.55em}
\def\@tocrmarg {2.55em}
\def\@dotsep{4.5}
\setcounter{tocdepth}{3}
\clubpenalty=8000
\emergencystretch 3em
\hbadness=4000
\hyphenpenalty=400
\pretolerance=750
\tolerance=2000
\vbadness=4000
\widowpenalty=10000

\renewcommand\section{\@startsection {section}{1}{\z@}%
     {-1.75ex \@plus -0.5ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large\bfseries}}
\renewcommand\subsection{\@startsection{subsection}{2}{\z@}%
     {-1.75ex\@plus -0.5ex \@minus- .2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large}}
\renewcommand\subsubsection{\@startsection{subsubsection}{3}{\z@}%
     {-1.5ex\@plus -0.35ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\large}}
\renewcommand\paragraph{\@startsection{paragraph}{4}{\z@}%
     {-1ex \@plus-0.35ex \@minus -0.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\normalsize}}
\renewcommand\subparagraph{\@startsection{subparagraph}{5}{\parindent}%
     {1.5ex \@plus1ex \@minus .2ex}%
     {-1em}%
     {\reset@font\normalsize\bfseries}}


\def\l@section#1#2{\addpenalty{\@secpenalty} \addvspace{1.0em plus 1pt}
 \@tempdima 1.5em \begingroup
 \parindent \z@ \rightskip \@pnumwidth 
 \parfillskip -\@pnumwidth 
 \bfseries \leavevmode #1\hfil \hbox to\@pnumwidth{\hss #2}\par
 \endgroup}
\def\l@subsection{\@dottedtocline{2}{1.5em}{2.3em}}
\def\l@subsubsection{\@dottedtocline{3}{3.8em}{3.2em}}
\def\l@paragraph{\@dottedtocline{4}{7.0em}{4.1em}}
\def\l@subparagraph{\@dottedtocline{5}{10em}{5em}}
\@ifundefined{c@section}{\newcounter{section}}{}
\@ifundefined{c@chapter}{\newcounter{chapter}}{}
\newif\if@mainmatter 
\@mainmattertrue
\def\chaptername{Chapter}
\def\frontmatter{%
  \pagenumbering{roman}
  \def\thechapter{\@roman\c@chapter}
  \def\theHchapter{\roman{chapter}}
  \def\thesection{\@roman\c@section}
  \def\theHsection{\roman{section}}
  \def\@chapapp{}%
}
\def\mainmatter{%
  \cleardoublepage
  \def\thechapter{\@arabic\c@chapter}
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \pagenumbering{arabic}
  \setcounter{secnumdepth}{6}
  \def\@chapapp{\chaptername}%
  \def\theHchapter{\arabic{chapter}}
  \def\thesection{\@arabic\c@section}
  \def\theHsection{\arabic{section}}
}
\def\backmatter{%
  \cleardoublepage
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \setcounter{secnumdepth}{2}
  \def\@chapapp{\appendixname}%
  \def\thechapter{\@Alph\c@chapter}
  \def\theHchapter{\Alph{chapter}}
  \appendix
}
\newenvironment{bibitemlist}[1]{%
   \list{\@biblabel{\@arabic\c@enumiv}}%
       {\settowidth\labelwidth{\@biblabel{#1}}%
        \leftmargin\labelwidth
        \advance\leftmargin\labelsep
        \@openbib@code
        \usecounter{enumiv}%
        \let\p@enumiv\@empty
        \renewcommand\theenumiv{\@arabic\c@enumiv}%
	}%
  \sloppy
  \clubpenalty4000
  \@clubpenalty \clubpenalty
  \widowpenalty4000%
  \sfcode`\.\@m}%
  {\def\@noitemerr
    {\@latex@warning{Empty `bibitemlist' environment}}%
    \endlist}

\def\tableofcontents{\section*{\contentsname}\@starttoc{toc}}
\parskip0pt
\parindent1em
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\newenvironment{reflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemsep}{0pt}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\itshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{sansreflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\itemsep}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\upshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{specHead}[2]%
 {\vspace{20pt}\hrule\vspace{10pt}%
  \phantomsection\label{#1}\markright{#2}%

  \pdfbookmark[2]{#2}{#1}%
  \hspace{-0.75in}{\bfseries\fontsize{16pt}{18pt}\selectfont#2}%
  }{}
      \def\TheFullDate{2011-05-23 (revised: 23 May 2011)}
\def\TheID{\makeatother }
\def\TheDate{2011-05-23}
\title{Maintenance Modification Algorithms and its Implementation on object oriented data warehouse}
\author{}\makeatletter 
\makeatletter
\newcommand*{\cleartoleftpage}{%
  \clearpage
    \if@twoside
    \ifodd\c@page
      \hbox{}\newpage
      \if@twocolumn
        \hbox{}\newpage
      \fi
    \fi
  \fi
}
\makeatother
\makeatletter
\thispagestyle{empty}
\markright{\@title}\markboth{\@title}{\@author}
\renewcommand\small{\@setfontsize\small{9pt}{11pt}\abovedisplayskip 8.5\p@ plus3\p@ minus4\p@
\belowdisplayskip \abovedisplayskip
\abovedisplayshortskip \z@ plus2\p@
\belowdisplayshortskip 4\p@ plus2\p@ minus2\p@
\def\@listi{\leftmargin\leftmargini
               \topsep 2\p@ plus1\p@ minus1\p@
               \parsep 2\p@ plus\p@ minus\p@
               \itemsep 1pt}
}
\makeatother
\fvset{frame=single,numberblanklines=false,xleftmargin=5mm,xrightmargin=5mm}
\fancyhf{} 
\setlength{\headheight}{14pt}
\fancyhead[LE]{\bfseries\leftmark} 
\fancyhead[RO]{\bfseries\rightmark} 
\fancyfoot[RO]{}
\fancyfoot[CO]{\thepage}
\fancyfoot[LO]{\TheID}
\fancyfoot[LE]{}
\fancyfoot[CE]{\thepage}
\fancyfoot[RE]{\TheID}
\hypersetup{citebordercolor=0.75 0.75 0.75,linkbordercolor=0.75 0.75 0.75,urlbordercolor=0.75 0.75 0.75,bookmarksnumbered=true}
\fancypagestyle{plain}{\fancyhead{}\renewcommand{\headrulewidth}{0pt}}

\date{}
\usepackage{authblk}

\providecommand{\keywords}[1]
{
\footnotesize
  \textbf{\textit{Index terms---}} #1
}

\usepackage{graphicx,xcolor}
\definecolor{GJBlue}{HTML}{273B81}
\definecolor{GJLightBlue}{HTML}{0A9DD9}
\definecolor{GJMediumGrey}{HTML}{6D6E70}
\definecolor{GJLightGrey}{HTML}{929497} 

\renewenvironment{abstract}{%
   \setlength{\parindent}{0pt}\raggedright
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
   \textcolor{GJBlue}{\large\bfseries\abstractname\space}
}{%   
   \vskip8pt
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
}

\usepackage[absolute,overlay]{textpos}

\makeatother 
      \usepackage{lineno}
      \linenumbers
      
\begin{document}

             \author[1]{MRs. MEENAKSHI  SHARMA}

             \author[2]{Dr.  Mrs Pushpa  Suri}

             \affil[1]{  Kurukshetra University, Kurukshetra}

\renewcommand\Authands{ and }

\date{\small \em Received: 21 April 2011 Accepted: 13 May 2011 Published: 23 May 2011}

\maketitle


\begin{abstract}
        


A data warehouse (DW) is a database used for reporting Paper describes Modification Algorithm and implementation on Object Oriented Data Warehousing. A Data Warehouse collects information and data from source data bases to support analytical processing of decision support functions and acts as an information provider. In initial research data warehouses focused on relational data model. In this paper concept of object oriented data warehouse is introduced modification maintenance algorithms and its implementation to maintained consistency between data warehouse and source data base.

\end{abstract}


\keywords{Data warehousing, object oriented database, instance, maintenance}

\begin{textblock*}{18cm}(1cm,1cm) % {block width} (coords) 
\textcolor{GJBlue}{\LARGE Global Journals \LaTeX\ JournalKaleidoscope\texttrademark}
\end{textblock*}

\begin{textblock*}{18cm}(1.4cm,1.5cm) % {block width} (coords) 
\textcolor{GJBlue}{\footnotesize \\ Artificial Intelligence formulated this projection for compatibility purposes from the original article published at Global Journals. However, this technology is currently in beta. \emph{Therefore, kindly ignore odd layouts, missed formulae, text, tables, or figures.}}
\end{textblock*}


\let\tabcellsep& 	 	 		 
\section[{INTRODUCTION}]{INTRODUCTION}\par
he concept of data warehousing was first proposed by Inmon  {\ref (Inmon and Kelley,1993)}. A data warehouse is a repository of subjectively selected and adapted operational data which can successfully answer any ad hoc, statistical, complex or analytical queries. Data warehousing technology is becoming essential for effective business intelligence, business strategy formulation and implementation in a globally competitive environment where in larger and larger amounts of data are required to be processed faster and faster for comprehension of its real meaning and impact. The term Data Warehouse was coined by Bill  {\ref Inmon in 1990}, which he defined in the following way: "A warehouse is a subject-oriented, integrated, time-variant and non-volatile collection of data in support of management's decision making process". Data that gives information about a particular subject instead of about a company's ongoing operations. It is integrated as data that is gathered into the data warehouse from a variety of sources and merged into a coherent whole.\par
Data warehouse system is time variant as all data in the data warehouse is identified with a particular time period. Data is stable in a data warehouse. More data is added but data is never removed. This enables management to gain a consistent picture of the business. (Source: "What is a Data Warehouse?" W.H. Inmon, Prism, Volume 1,  {\ref Number 1, 1995)}. A singlesubject data warehouse is typically referred to as a data mart, while data warehouses are generally enterprise in scope. Also, data warehouses can be volatile. Due to the large amount of storage required for a data warehouse, (multi-terabyte data warehouses are not uncommon), only a certain number of periods of history are kept in the warehouse. For instance, if three years of data are decided on and loaded into the warehouse, every month the oldest month will be "rolled off" the database, and the newest month added. Data warehouse contains information that is being collected from different sources and integrated into a common repository for efficient query and analysis. When the data sources are disturbed over a different location then a DW has the responsibility to collect the necessary data and save it in appropriate form. In this paper some research topics are mentioned as Maintenance \hyperref[b12]{[11]}  \hyperref[b13]{[12]} [13] \hyperref[b16]{[15]} [17]  {\ref [20] [21]}, consistency \hyperref[b6]{[6]}, \hyperref[b27]{[26]}, \hyperref[b28]{[27]}.\par
In this paper is organized as follows. The concept of object oriented data warehousing. Formal definition of class instance and object oriented data warehousing. Maintenance modification algorithms for consistency between the object oriented data warehouse. Examples are also given there to illustrate the proposed algorithms and its implementation in oracle 10g. 
\section[{II.}]{II.} 
\section[{Object Oriented Data Warehousing}]{Object Oriented Data Warehousing}\par
In an object oriented database, each employee or class is associated with unique identifier, a set of attributes and a set of procedures. There could be no. of data types such as atomic or any other class. Object Oriented Data warehousing, like other areas of Information Technology, is a field in the midst of change. The current systems integration approach is associated T with the objective of creating a centralized operational data store and Decision Support System read-only server-based application [3]. To meet this objective, it is necessary to extract, transform, and transport data from isolated islands of information to such centralized repositories, and then to retrieve information efficiently and effectively through query and reporting tools. To perform multidimensional analysis, and to meet performance criteria, special methods and tools associated with On-Line Analytical Processing are employed. Multidimensional client, multidimensional server (Multidimensional Online Analytical Processing or Multidimensional Data Online Analytical Processing), Relational Online Analytical servers, and most recently, Vertical Technology servers, are used to help performance in the query and reporting process. Object Oriented Data Warehouse approaches are better at specifying user requirements than Systems Integration ones. In particular, systems integration approaches seem to move from process identification to data modeling without specifying the details of the identified processes. They do not employ Use Case specification and analysis to get at requirements, while this is a central aspect of Object Oriented Data Warehouse .The fourth class of specific reasons for an Object Oriented Data Warehouse approach to data warehousing is conceptual consistency with the various components of a data warehousing solution. The tools used to arrive at these solutions are increasingly object-oriented. For example, data extraction, transformation and transportation (ETT), tools from Sagent, Informatica, Carleton, ETI, VMARK and others strongly reflect the conceptual outlook of object technology. In the object oriented Data warehousing we used the classes and instances. An object type is a description of a set of object sharing the same attributes operations and relationships. Classes are implementation of types in software. So, objects are instances of classes as well as one of the types. In an object oriented data base system, we have defined certain definitions for various employees or classes. The classes can be organized according to their hierarchy. Let ID be a set of identities, A be set of attribute names be a set of data types allowed for A,TW be a set of atomic data types be a set of values and M be a set of processing methods. A set of employees in an object oriented database can be defines as follows: 
\section[{III. Notation And Definition}]{III. Notation And Definition}\par
July An instance t =\{tid, ta, tv,tm\}is created and inherits from a certain class cid=\{cid, ca, ct, cm\} such that tid ?ID, ta= ca tv= <tv 1, tv 2,??.. tv n> with tv i ? U and tv i being of type ct i for i=1 to n, and tm= cm.\par
Example 2 : For the example in Figure  {\ref 2} An object-oriented data warehouse W is a triple \{V, VC, I\}, where V is the set of view definitions, VC is a set of classes and I is the set of instances generated from the source database according to VC and V. Below, modification maintenance algorithms are proposed to maintain the consistency between an object-oriented data warehouse and its underlying source databases. They are instance insertion, instance modification alters, and instance modification update. 
\section[{IV.}]{IV.} 
\section[{Instance Insertion}]{Instance Insertion}\par
We have a source database, a new instance Iid is inserted into a source database. A new Msg known as transaction Msg is formed and sent from the data collector to the data warehouse for the view maintance. The proposed syntax of the transaction Msg for instance insertion as follow : MID, insert, Iid, Cid\par
In this Msg identifier of this transaction which is formatted automatically by data collector. Insert is denote type of Msg. Iid identifier the new instance which is inserted in a database and Cid class identifier form which this instance is inherits. 
\section[{The algorithm of maintenance for instance insertion}]{The algorithm of maintenance for instance insertion}\par
Input : -A Data Warehouse W(V,VC, I) and an instance Iid of the class Cid is inserted into the source database. Output : -A modified Data warehouse W' (V, VC, I') Step1 : A source receives an instance insertion truncation Message, which is formed and sent from the data collector to the data warehouse.\par
Step2 : Make the view definition to find the definition which refers to the class Cid in the From Part. View found is denoted by V A .\par
Step3 : If A is empty, set W'= W and exit the algo otherwise go to the next step.\par
Step4 : After application of select, where operations deduce all the attributes from the view named V A and denotes it by V B.\par
Step5 : Request the data collector to collect the contents of V B and instance Iid or alternatively from its subsequent descending instances.\par
Step6 : Acknowledge the contents of V B from the data collector.\par
Step7 : If contents of V B received and satisfy the conditions of view v in A. Create a new instance according to the class of the view otherwise do nothing. Step8 : After step 7, new necessary instances are created and inserted into the Data warehouse. Data warehouse now modified by.W' (V, VC, I') V. 
\section[{Instance Modification Alter}]{Instance Modification Alter}\par
When the attribute values of an instance tid in the source database are changed, a transaction Message is sent from the data collector to the data warehouse for view maintenance. In algorithm W is warehouse, V is View, C is the Class and I is Instance. The format of a transaction message for modifying an instance is proposed as follows:\par
MsgID, Alter, tid, cid, Where ui denotes the i-th attribute add to be alter and vi denotes the new attribute. Example3, assume that the attribute office in instance IN is alter from IN to INH. The data collector will detect it and send a transaction message (001, alter, office, R\&D, \{(office country)\}) to the warehouse. The maintenance algorithm for processing the above instance modification alters is proposed as follows:\par
The maintenance algorithm for instance modification Alter: Input: Data warehouse W(C, V, I) and modified alter instance tid of class cid. Output: A revised data warehouse W' (C, V, I') Step1: An Instance of modified alter message is received from the data collector.\par
Step2: Search the data warehouse W for instance tid: If instance tid exits in W exist algorithm otherwise Go to the step No.3 and set W'=W Step3: For the instance tid in warehouse alter its attribute according to the transaction message.\par
Step4: If the instance tid satisfies the condition of at least one view which refer to class cid, then keep the instance tid in I of the warehouse W otherwise remove tid from I in the warehouse W\par
The attribute of instance tid have been modified alter add in the data warehouse after the Step no.4.\par
Example 3 : Assume that the attribute of an instance have been added in the source database and the transaction Msg is formed as Alter type office add attribute (country char \hyperref[b21]{(20)})cascade. This message is processed by the instance modified alter algorithm as follow:\par
Step1: Receive the transaction message alter type office add attribute (country char \hyperref[b21]{(20)}) cascade from the data collector.\par
Step2: Since the instance A1 exists in the warehouse W then stop.\par
Step3: Alter the attribute country of the class office.\par
Step4: If A1 satisfies the condition of view country office it is kept in W. 
\section[{VI. Instance Modification Update}]{VI. Instance Modification Update}\par
When the attribute values of an instance tid in the source database are changed, a transaction message is sent from the data collector to the data warehouse for view maintenance. The format of a transaction message for modifying an instance is proposed as follows:\par
MsgID, update, tid, cid, where ui denotes the i-th attribute name to be updated and vi denotes the new value of ui. For example, assume that the value of attribute name in instance MKP is changed from KAUSHIK to PALAV. The data collector will detect it and send a transaction message ( S001, update, NAME, MKP, \{(MKP PALAV)\}) to the warehouse. The view -maintenance algorithm for processing the above instancemodification transaction message is proposed as follows.\par
The maintenance algorithm for instance modification update:\par
Input : data warehouse W (C, V, I) and a modified instance tid of class cid. Output : A revised data warehouse W' (C, V, I').\par
Step1. Receive an instance-modification transaction message which is formed from the data collector.\par
Step2. Search the data warehouse W for instances tid; If instance tid exists in W, do the next step; Otherwise, set W' = W and exit the algorithm.\par
Step3. For the instance tid in the warehouse, change its attribute values according to the transaction message.\par
Step4. Check whether the instance tid satisfies the conditions of the views V which refer to the class cid; If the instance satisfies the condition of at least one view, keep instance tid in I of the warehouse W; Otherwise, remove tid from I in the warehouse W. After Step 4, the attribute values of instance tid have been modified in the data warehouse. An example is given below to demonstrate the instance -modification algorithm.\par
Example4, Continuing Example 3, assume that the attribute values of an instance have been modified in EmpID char \hyperref[b21]{(20)}, EmpName name, Empdept dept, Emptitle char \hyperref[b11]{(10)}, counter int\par
Step1. Receive the transaction message (S001, update, NAME, MKP, \{(NAME PALAV)\}) from the data collector.\par
Step 2. Since the instance A1 exists in the warehouse W, the algorithm executes Step 3.\par
Step 3. Change the value of attribute NAME of the instance MKP from KAUSHIK to PALAV.\par
Step 4. Since A1 satisfies the condition of the view MKP Employee, it is kept in W. The graphical representation of the warehouse after the attribute value of instance A1 has been changed is shown in Figure 4.  
\section[{VII.}]{VII.} 
\section[{Implementation}]{Implementation} 
\section[{Conclusion}]{Conclusion}\par
The research of object oriented data warehousing is current topic so, there are many important issues which are yet to be explored. For online processing modification maintenance in object oriented data warehousing is very important. Modification maintenance of the data warehouse is very important to accuracy of the on-line analytical processing. In this paper, we have discussed the concept of object oriented data warehouse and modification maintenance al gorithms to maintain the consistency between the data warehousing and the source databases. They are instance insertion, instance modification alters and instance modification update. Although the proposed algorithms can be used to make object oriented data warehousing practical.\begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-2.png}
\caption{\label{fig_0}}\end{figure}
     			\footnote{© 2011 Global Journals Inc. (US)} 			\footnote{© 2011 Global Journals Inc. (US) b) Definition (Instance) c) Definition (Data warehouse)} 			\footnote{Global Journal of Computer Science and TechnologyVolume XI Issue XII Version I July} 			\footnote{© 2011 Global Journals Inc. (US) Global Journal of Computer Science and Technology Volume XI Issue XII Version I July} 			\footnote{Global Journal of Computer Science and TechnologyVolume XI Issue XII Version I July} 		 		\backmatter  			  				\begin{bibitemlist}{1}
\bibitem[Poland ()]{b8}\label{b8} 	 		\textit{},  		 			Poland 		.  	 	 		LNCS No. 1475  		1998. p. .  	 
\bibitem[20)) cascade SQL> Update type name set middle ='palav' where employeeid='EM01' the source database, and the transaction message is formed as (S001, update, Name, MKP, {(NAME PALAV)}). This message is processed by the instancemodification algorithm as follows. warehousing Proceeding of the Fourth international conference on computer science and informatics ()]{b3}\label{b3} 	 		‘20)) cascade SQL> Update type name set middle ='palav' where employeeid='EM01' the source database, and the transaction message is formed as (S001, update, Name, MKP, \{(NAME PALAV)\}). This message is processed by the instancemodification algorithm as follows. warehousing’.  	 	 		\textit{Proceeding of the Fourth international conference on computer science and informatics},  				 (eeding of the Fourth international conference on computer science and informaticsNorth Carolina, USA)  		1998. p. .  	 	 (SQL> Alter type office add attribute (country char) 
\bibitem[Rundensteiner ()]{b24}\label{b24} 	 		‘A Methodology for supporting Multiple Views in Object-Oriented Databases’.  		 			E A Rundensteiner 		.  	 	 		\textit{Proceedings of 18th International Conference on Very Large Data Bases},  				 (18th International Conference on Very Large Data BasesVancouver, Canada)  		1992. p. .  	 
\bibitem[Ra and Rundensteiner]{b23}\label{b23} 	 		‘A Transparent Schema-Evolution System Based on Object-Oriented View Technology’.  		 			Y G Ra 		,  		 			E A Rundensteiner 		.  	 	 		\textit{IEEE Transaction on Knowledge and Data Engineering}  		9  (4)  p. .  	 
\bibitem[Chaudhuri]{b0}\label{b0} 	 		‘An overview of Data warehousing and OLAP Technology’.  		 			S Chaudhuri 		,  		 			U 		.  	 	 		\textit{ACM}  		 	 
\bibitem[Gray W et al.]{b11}\label{b11} 	 		\textit{Data Base Management System},  		 			Gray W 		,  		 			James V Hansen 		,  		 			Hansen 		.  		 	 
\bibitem[Eder et al. ()]{b9}\label{b9} 	 		 			J Eder 		,  		 			H Frank 		,  		 			W Liebhart 		.  		\textit{Optimization of Object-Oriented Queries by Inverse Methods. Proceedings of East/West Database Workshop},  				 (Austria)  		1994.  	 
\bibitem[Hyun ()]{b4}\label{b4} 	 		\textit{Efficient self maintenance of materialized views},  		 			N Hyun 		.  		1996.  	 	 (Technical note) 
\bibitem[Huyn ()]{b13}\label{b13} 	 		\textit{Efficient self-maintenance of materialized views},  		 			N Huyn 		.  		1996.  	 	 (Technical Note) 
\bibitem[Labio and Garcia-Molina (1996)]{b16}\label{b16} 	 		‘Efficient snapshot differential algorithms for data warehousing’.  		 			W J Labio 		,  		 			H Garcia-Molina 		.  	 	 		\textit{Procwdings of VZDB Conference},  				 (wdings of VZDB ConferenceMumbai, India)  		September 1996.  	 
\bibitem[Huyn ()]{b12}\label{b12} 	 		‘Efficient view self maintenance’.  		 			N Huyn 		.  	 	 		\textit{Proceeding of the ACM Workshop on Materialized Views}  		1996.  	 
\bibitem[Zhuge and Garica-Molina ()]{b27}\label{b27} 	 		‘Graph structured views and their incremental maintenance’.  		 			Y Zhuge 		,  		 			H Garica-Molina 		.  	 	 		\textit{Proceedings of the International Conference on Data Engineering},  				 (the International Conference on Data EngineeringOrlando, FL)  		1998.  	 
\bibitem[O'neil and Quass (1997)]{b20}\label{b20} 	 		‘Improved query performance with variant indexes’.  		 			P O'neil 		,  		 			D Quass 		.  	 	 		\textit{Proceedings of the ACM SIG\textbackslash IOD Conference},  				 (the ACM SIG\textbackslash IOD ConferenceTucson, Arizona)  		May, 1997.  	 
\bibitem[Dobrovnik and Eder ()]{b6}\label{b6} 	 		‘Logical data independence and modularity through views in OODBMS’.  		 			M Dobrovnik 		,  		 			J Eder 		.  	 	 		\textit{Proceedings of the Engineering Systems Design and Analysis Conference},  				 (the Engineering Systems Design and Analysis Conference)  		1996. 2 p. .  	 
\bibitem[Quass (1996)]{b21}\label{b21} 	 		‘Maintenance expressions for views with aggregation’.  		 			D Quass 		.  	 	 		\textit{Proceedings of the ACM Workshop on Materialized Ems}  		June 7, 1996.  	 
\bibitem[Mumick et al. (1997)]{b19}\label{b19} 	 		‘Maintenance of data cubes and summary tables in a warehouse’.  		 			D Mumick 		,  		 			B Quass 		,  		 			Mumick 		.  	 	 		\textit{Proceedings of the ACM SIGMOD Conference},  				 (the ACM SIGMOD ConferenceTucson, Arizona)  		May, 1997.  	 
\bibitem[Quass et al. (1996)]{b22}\label{b22} 	 		‘Making views self-maintainable for data warehousing’.  		 			D Quass 		,  		 			A Gupta 		,  		 			I S Mumick 		,  		 			J Widom 		.  	 	 		\textit{Proceedings of the Conference on Parallel and Distributed Information Systems},  				 (the Conference on Parallel and Distributed Information SystemsMiami Beach, FL)  		December 1996.  	 
\bibitem[Gupta Mumick (ed.) ()]{b10}\label{b10} 	 		\textit{Materialized Views: Techniques, Implementations, and Applications},  				 			A Gupta,  			I S Mumick 		 (ed.)  		1999. The MIT Press.  	 
\bibitem[Kim ()]{b18}\label{b18} 	 		\textit{Modern Database Systems},  		 			W Kim 		.  		1995. New York, New York: ACM Press.  	 
\bibitem[Huyn ()]{b14}\label{b14} 	 		‘Multiple-view self-maintenance in data warehousing environments’.  		 			N Huyn 		.  	 	 		\textit{Proceedings of the 23d CZDB Conference},  				 (the 23d CZDB ConferenceAthens, Greece)  		1997.  	 
\bibitem[Chen (1999)]{b5}\label{b5} 	 		\textit{Object Oriented data warehousing and its maintenance technologies},  		 			W Chen 		.  		April, 1999. Taiwan, R.O.C.  		 			Master Dissertation, I-Shou University 		 	 
\bibitem[Dobrovnik and Eder]{b7}\label{b7} 	 		‘Partial Replication of Object-Oriented Databases’.  		 			M Dobrovnik 		,  		 			J Eder 		.  	 	 		\textit{Proceedings of the Second East-European Conference on Advances in maintenance in an object oriented data Databases and Information Systems -ADBIS'98},  				 (the Second East-European Conference on Advances in maintenance in an object oriented data Databases and Information Systems -ADBIS'98)  		 	 
\bibitem[Inmon and Kelley]{b15}\label{b15} 	 		\textit{RdbMS: Developing The Data Warehouse},  		 			W H Inmon 		,  		 			C Kelley 		.  		Boston, Massachusetts: QED Publishing Group. 1 p. 993.  	 
\bibitem[Widom (1995)]{b26}\label{b26} 	 		‘Research problems in data warehousing’.  		 			J Widom 		.  	 	 		\textit{Proceedings of the 41h Int'l Conference on Information and Knowledge Management},  				 (the 41h Int'l Conference on Information and Knowledge Management)  		November 1995.  	 
\bibitem[SQL> Create table emp of employee]{b1}\label{b1} 	 		\textit{SQL> Create table emp of employee},  		 	 
\bibitem[SQL>insert into emp values (employee ('EM01', name('minny, 'kaushik', 'pandove'), dept ('s001', 'R&D','kaithal]{b2}\label{b2} 	 		\textit{SQL>insert into emp values (employee ('EM01', name('minny, 'kaushik', 'pandove'), dept ('s001', 'R\&D','kaithal},  		 	 
\bibitem[Labio et al. (1997)]{b17}\label{b17} 	 		‘The W " S prototype for data warehouse creation and maintenance’.  		 			W J Labio 		,  		 			Y Zhuge 		,  		 			J L Wiener 		,  		 			H Gupta 		,  		 			H Garcia-Molina 		,  		 			J Widom 		.  	 	 		\textit{Proceedings of the ACMSIGMOD Conference},  				 (the ACMSIGMOD ConferenceTuscon, Arizona)  		May 1997.  	 
\bibitem[Scholl et al. ()]{b25}\label{b25} 	 		‘Updateable Views in Object-Oriented Databases’.  		 			M H Scholl 		,  		 			C Laasch 		,  		 			M Tresch 		.  	 	 		\textit{Second International Conference on Deductive and Object-Oriented Databases},  				 (Munich, Germany)  		1991. p. .  	 
\bibitem[Zhuge et al. (1995)]{b28}\label{b28} 	 		‘View maintenance in a warehousing environment’.  		 			Y Zhuge 		,  		 			H Garcia-Molina 		,  		 			J Hammer 		,  		 			J Widom 		.  	 	 		\textit{Proceedings of the ACM SIGMOD Conference},  				 (the ACM SIGMOD ConferenceSan Jose, California)  		May 1995.  	 
\end{bibitemlist}
 			 		 	 
\end{document}
