1. RELATIONAL FAULT TOLERANT INTERFACE TO HETEROGENEOUS DISTRIBUTED DATABASES Prof. Osama Abulnaja Afraa Khalifah 1103999

2. Content Introduction. The General Structure of The Model. Extended RPC Model. The Structure of The Basic Elements of the Model. View Generator. (UFI) User Friendly Interface. The Client Stub - Optimal Access plan generation. Server Stub - AMI and AMU The Structure of The Catalog Fault-Tolerant Aspects and Recovery. Conclusion.

3. Introduction Paper focus on the problem of heterogeneous distributed databases. Paper propose an uniform logical interface to the end user from a collection of different environments. Fault tolerance aspects of reliability of this system as well as error detection techniques and recovery protocols are also described. Problems due to heterogeneity : o Interconnection o Filing o User interface

4. The General Structure of The Model illustrates extended RPC model and how it works CLIENT UFI (User Friendly Interface) CLIENT STUB DBMS process Access Plan generator Query processing Code Generation TRANSPORT SERVER STUB AMI SERVER AMU CATALOG call return call return call Return (Local Procedure Call) callreturncallreturn (Remote Procedure Call)

5. The General Structure of The Model illustrates extended RPC model and how it works CLIENT UFI (User Friendly Interface) CLIENT STUB DBMS process Access Plan generator Query processing Code Generation TRANSPORT SERVER STUB AMI SERVER AMU CATALOG call return call return call Return (Local Procedure Call) callreturncallreturn (Remote Procedure Call) Receives user's queries. Queries are passed to the lexical analyzer and parser which transform them into parse tree form.

6. The General Structure of The Model illustrates extended RPC model and how it works CLIENT UFI (User Friendly Interface) CLIENT STUB DBMS process Access Plan generator Query processing Code Generation TRANSPORT SERVER STUB AMI SERVER AMU CATALOG call return call return call Return (Local Procedure Call) callreturncallreturn (Remote Procedure Call) receives queries into parse tree form and transfers them to the optimal access plan generation and code generation modules. This code contains calls to the procedures which can reside to other systems. Responsible also for translating the arguments into a suitable format for transmission over the network Generating code must be linked before calling one another.

7. The General Structure of The Model illustrates extended RPC model and how it works CLIENT UFI (User Friendly Interface) CLIENT STUB DBMS process Access Plan generator Query processing Code Generation TRANSPORT SERVER STUB AMI SERVER AMU CATALOG call return call return call Return (Local Procedure Call) callreturncallreturn (Remote Procedure Call) bind clients and servers together before RPC can take place.

8. The General Structure of The Model illustrates extended RPC model and how it works CLIENT UFI (User Friendly Interface) CLIENT STUB DBMS process Access Plan generator Query processing Code Generation TRANSPORT SERVER STUB AMI SERVER AMU CATALOG call return call return call Return (Local Procedure Call) callreturncallreturn (Remote Procedure Call) Demarshalls the parameters and calls the desired server routine using the regular procedure call mechanism. Marshalls the return values into a message.

9. The General Structure of The Model illustrates extended RPC model and how it works CLIENT UFI (User Friendly Interface) CLIENT STUB DBMS process Access Plan generator Query processing Code Generation TRANSPORT SERVER STUB AMI SERVER AMU CATALOG call return call return call Return (Local Procedure Call) callreturncallreturn (Remote Procedure Call) Relational user can access non relational model of DB (remotely) Using the transport mechanism and corresponding relational schema from the catalog The user can access the DB on another node.

10. Extended RPC Model RPC provide stub generators for(transport protocols - data representation - semantics and type systems) Extended RPC model support the following cases: First: Local procedure call Relational user can access relational DB which is locally available Relational user can access network, hierarchical or other nonrelatinal model of DB. Second: Remote procedure call Relational user can access relational DB on another node (remotely). Relational user can access nonrelational model of DB (remotely).

11. Catalog The Structure of The Basic Elements of the Model Non Relational SchemaUser Information View Generator Relational Schema (View) Integrity Constraints Rule BaseData Base View Generator

12. Catalog The Structure of The Basic Elements of the Model View Generator Non Relational SchemaUser Information View Generator Relational Schema (View) Integrity Constraints Rule BaseData Base Extracts logical information from the given non relational schema and through user- system dialogue at view definition time generates relational schema. Translated schema is stored in the catalog as relational schema.

13. The Structure of The Basic Elements of the Model UFI module enabling easy interaction with the resources to the end users. UFI module enables processing of user's ad-hoc queries. Generate relational view over existing relational and non relational databases. communicate with the catalog for searching or modifying its contents. process ad-hoc queries related on databases resident on one or more systems. The UFI will communicate with the user via five types of screens created by the resident systems : predefined screens for generating relational views over nonrelational databases, screens for communication with the catalog, predefined screen for all queries, screens for automatic generation of reports, screens defined interactively by the users. (UFI) User Friendly Interface

14. The Structure of The Basic Elements of the Model (UFI) User Friendly Interface UFI transfers user's queries to the lexical analyzer and parser. Realize a special SQL parser. Using high probability. Syntax error correction activity depends on : The context in which error has occurred, Our knowledge for appropriate recovery action. In this way, we have balanced the efficient query execution flow with the level of fault tolerant in the process of query parsing.

15. The Structure of The Basic Elements of the Model Query Standardization View Substitution Simplification Amelioration Evaluation Selection of Access Plan Generator of Code Catalog Query against View relations (Parse Tree) View relations definition from catalog The Client Stub - Optimal Access plan generation

16. The Structure of The Basic Elements of the Model Query Standardization View Substitution Simplification Amelioration Evaluation Selection of Access Plan Generator of Code Catalog Query against View relations (Parse Tree) View relations definition from catalog Using SQL to build prototype system. The goal is the construction of a standardized starting point for query optimization. The Client Stub - Optimal Access plan generation

17. The Structure of The Basic Elements of the Model Query Standardization View Substitution Simplification Amelioration Evaluation Selection of Access Plan Generator of Code Catalog Query against View relations (Parse Tree) View relations definition from catalog Eliminate the redundancy. The Client Stub - Optimal Access plan generation

18. The Structure of The Basic Elements of the Model Query Standardization View Substitution Simplification Amelioration Evaluation Selection of Access Plan Generator of Code Catalog Query against View relations (Parse Tree) View relations definition from catalog construct improve expressions with respect to evaluation performance. The Client Stub - Optimal Access plan generation

19. The Structure of The Basic Elements of the Model Query Standardization View Substitution Simplification Amelioration Evaluation Selection of Access Plan Generator of Code Catalog Query against View relations (Parse Tree) View relations definition from catalog map the transformed query into alternative sequences of elementary operations for which a good implementation and its associated cost are known. The Client Stub - Optimal Access plan generation

20. The Structure of The Basic Elements of the Model Query Standardization View Substitution Simplification Amelioration Evaluation Selection of Access Plan Generator of Code Catalog Query against View relations (Parse Tree) View relations definition from catalog Compute the cost for each access plan, will choose the cheapest one. The Client Stub - Optimal Access plan generation

21. The Structure of The Basic Elements of the Model Query Standardization View Substitution Simplification Amelioration Evaluation Selection of Access Plan Generator of Code Catalog Query against View relations (Parse Tree) View relations definition from catalog Generate the code of the access module. The Client Stub - Optimal Access plan generation

22. The Structure of The Basic Elements of the Model Query Standardization View Substitution Simplification Amelioration Evaluation Selection of Access Plan Generator of Code Catalog Query against View relations (Parse Tree) View relations definition from catalog The Client Stub - Optimal Access plan generation All modules must communicate with the catalog to perform its functions. Particular integrity constraints will enable the existing relational view optimization facilities to be used for compiling non relational database.

23. The Structure of The Basic Elements of the Model Server Stub - AMI and AMU AMI (Access Method Interface) receive calls from the client stub The code generation module in the client stub generates a code which contains calls to the AMI routines. The server stub receives the AMI routine name and arguments into network's format. The AMU are access method utilities resident on the server system.

24. The Structure of The Basic Elements of the Model The Structure of The Catalog The catalog is organized as a knowledge base. The knowledge base contains two parts: database - rule base. All user requests will be interpreted by the system in accordance with information stored in catalog. where and how The catalog should be stored?

25. Fault-Tolerant Aspects and Recovery Client 1 Client n Server 1 Server m Access Plan 1 Access Plan n Access Plan 1 Access Plan k

26. Fault-Tolerant Aspects and Recovery Client 1 Client n Server 1 Server m Access Plan 1 Access Plan n Access Plan 1 Access Plan k To improve reliability allow the existence and execution of several access plans

27. Fault-Tolerant Aspects and Recovery Client 1 Client n Server 1 Server m Access Plan 1 Access Plan n Access Plan 1 Access Plan k The client will send messages to multiple servers in the network. Choose one of other access plans. The choice can be performed in different ways.

28. Conclusion Development of the extended client server model. Development of knowledge-based protocols for user error correction through the query processing. Provide an expert subsystem for view definition. Development of the catalog structure as relational database and knowledge base. Develop fault tolerant model to provide high degree of fault tolerance and robustness of the system. Provide better database model and structure transparency.