аЯрЁБс>ўџ ЕЖўџџџГДџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџмЅhcр e€"…Ge€~ЁLа Lа аUаUаUаUаU$єUєUєUєUєUV‚ŠV єUŽcоЋWR§ZHE\E\E\E\˜н]ьЩ^xŒcŽcŽcŽcŽcŽcŽcldXФdƒŽcаUA_ez,E\E\A_A_ŽcA_аUаUE\–WA_A_A_A_аUE\аUE\A_KpЉ=їkСєUєUаUаUаUаUA_ŒcA_A_ Informix Service Offering: Questionnaire Design and MigrationPartner Technical Services Author: Tom Laszewski Creation Date: August 19, 1998 Last Updated: August November 1911, 19982001 Control Number: Version: 23.0 Approvals: Raja Srinivasan AUTOTEXT "PIC Oracle Logo" \* MERGEFORMAT  Copy Number _____ Document Control Change Record DateAuthorVersionChange ReferenceAugust 19,1998Tom Laszewski2.0Original document put into Oracle format.November 11, 2001Franчois PONS3.0Oracle9i update Reviewers NamePosition Distribution Copy No.NameLocation Contents  TOC \o "1-3" Document Control  GOTOBUTTON _Toc428952251  PAGEREF _Toc428952251 iiii Change Record  GOTOBUTTON _Toc428952252  PAGEREF _Toc428952252 iiii Reviewers  GOTOBUTTON _Toc428952253  PAGEREF _Toc428952253 iiii Distribution  GOTOBUTTON _Toc428952254  PAGEREF _Toc428952254 iiii Executive Summary  GOTOBUTTON _Toc428952255  PAGEREF _Toc428952255 11 Introduction  GOTOBUTTON _Toc428952256  PAGEREF _Toc428952256 22 Purpose  GOTOBUTTON _Toc428952257  PAGEREF _Toc428952257 22 Background  GOTOBUTTON _Toc428952258  PAGEREF _Toc428952258 22 Section I - General Information  GOTOBUTTON _Toc428952259  PAGEREF _Toc428952259 33 Client Information  GOTOBUTTON _Toc428952260  PAGEREF _Toc428952260 33 Section II - Questions  GOTOBUTTON _Toc428952261  PAGEREF _Toc428952261 55 Architecture  GOTOBUTTON _Toc428952262  PAGEREF _Toc428952262 55 Database  GOTOBUTTON _Toc428952263  PAGEREF _Toc428952263 88 Current use of stored procedures (if applicable)  GOTOBUTTON _Toc428952264  PAGEREF _Toc428952264 1514 Current use of Embedded SQL/C  GOTOBUTTON _Toc428952265  PAGEREF _Toc428952265 1716 Current use of Informix 4GL  GOTOBUTTON _Toc428952266  PAGEREF _Toc428952266 2017 Current use of other application development tools  GOTOBUTTON _Toc428952267  PAGEREF _Toc428952267 2118 Support  GOTOBUTTON _Toc428952268  PAGEREF _Toc428952268 2219 Other special logic/subsystems to migrate  GOTOBUTTON _Toc428952269  PAGEREF _Toc428952269 2320 Documentation  GOTOBUTTON _Toc428952270  PAGEREF _Toc428952270 2421 Section III - INFORMATION/SOLUTIONS  GOTOBUTTON _Toc428952271  PAGEREF _Toc428952271 2522 Informix Database  GOTOBUTTON _Toc428952272  PAGEREF _Toc428952272 2522 Informix SQL  GOTOBUTTON _Toc428952273  PAGEREF _Toc428952273 2522 Informix Stored Procedures  GOTOBUTTON _Toc428952274  PAGEREF _Toc428952274 2522 Informix Embedded SQL/C and COBOL  GOTOBUTTON _Toc428952275  PAGEREF _Toc428952275 2623 Informix 4GL  GOTOBUTTON _Toc428952276  PAGEREF _Toc428952276 2723 Informix New Era  GOTOBUTTON _Toc428952277  PAGEREF _Toc428952277 2724  Executive Summary This template is used by Oracle Consulting, and Design and MigrationPartner Technical Services, to migrate a customer from Informix to Oracle. Oracles' Partner Technical Design and Migration Services has developed this template based upon the common deliverables produced for customers migrating from competitive database platforms to Oracle. This is the first template used when an Oracle consultant is preparing scope and project plan documents for an Informix to Oracle migration project. The information in this document is then used to complete the Project Scope template. Introduction Purpose This documents contains questions that need to be answered for any Informix to Oracle migration effort. The three main sections of the document are as follows: Section 1(General Information) - Asks general questions about the company and product. Section 2(Questions) - Asks all the questions that are necessary to prepare a thorough scope document. Section 3(Information/Solutions) - Contains information about converting systems from Informix to Oracle, as well as solutions to common problems. The questions in Section II are asked of the client. The answers, along with the project scope template and section III of this document, are used to complete the project scope document. Background Oracles’ Partner Technical Design and Migration Services has performed many Informix to Oracle migrations over the past five years. Consultants have asked many of the same questions in order to perform these migration efforts. This document is a compilation of the questions asked of Informix technical personnel in order to successfully complete an Informix to Oracle project scope effort. Section I - General Information Client Information Client name Address System/ application name Contacts: Manager: Technical Manager: DBA: Lead Developer: Others: E-mail address Manager: Technical Manager: DBA: Lead Developer: Others: Phone/Fax/Pagers Manager: Technical Manager: DBA: Lead Developer: Others:  Section II - Questions Architecture Describe the business use of the system: Why: Need to understand how the system is used Target hardware and target operating system Describe the architecture of the system: Why: This will answer many questions regarding the system, and will introduce Oracle Consulting to the technical environment. Online: Batch: Ad hoc: Describe any special features(such as: replication, parallel servers, distributed processing, middleware(i.e. Tuxedo, Encina, Top End, Web Application Servers etc.): Why: These area may need special consideration, and alternatives may exist in Oracle. Database Informix version number Why: Oracle and third party migration tools exist for specific versions of Informix and Oracle. In addition, different versions of Informix have different features. Type of system (such as: OLTP, OLAP, data warehouse etc.) Why: The type of system will effect affect the number and size of the redo logs and rollback segmentsUndo tablespace. The type of system and number of tables will also effect affect the disk layout, and therefore the number and size of tablespaces. Total size of development(and/or production) database in MB Why: Space needs to be made available for the corresponding Oracle database, as well as the data files that will hold the data as it is being transferred between Informix and Oracle. Also the size of the database will aeffect table and/or tablespace setting such as: INITIAL, NEXT, PCTINCREASE, MINEXTENTS and MAXEXTENTS. Number of tables Why: The number of tables will impact the estimate for the schema migration. If the Oracle "Informix Conversion Kit"Migration Workbench is used, the process should be for the most part automatic. If the schema migration is done manually, an estimate needs to be made for schema migration based upon the number of tables. Size and usage of tables Why: The size and usage of tables will effect affect where tables will be placed (i.e. tablespaces). Largest tables (number and size): Most active tables (number and size): Look up tables (number and size): HowNumber of views Why: Complex vViews may need to be converted manually. All views need to be graded on level of complexity (easy, average and complex). Number of indexes Why: Indexes are automatically converted if the Oracle Migration Workbench Oracle " Informix Conversion Kit" is used. If the schema migration is done manually, an estimate needs to be made for schema migration based upon the number of indexes. Number of clustered indexes Why: Indexes are automatically converted if Oracle Migration Workbench is used. However, the same concept of clustered indexes does not exist between Informix and Oracle. Informix clustered indexes mean the data is organized in the order of the clustered index. This order is always maintained. Since Oracle does not have the same concept, detailed analysis of Informix clustered indexes may need to be done. Number of clustered indexes Why: Indexes are automatically converted if the Oracle " Informix Conversion Kit" is used. However, the same concept of clustered indexes does not exist between Informix and Oracle. Informix clustered indexes mean the data is organized in the order of the clustered index. This order is allows maintained. Since Oracle does not have the same concept, detailed analysis of Informix clustered indexes may need to be done. Tables with CHARACTER columns exceeding 2000 characters but less than 4000 characters Why: An Oracle CHAR can be a length of up to 2000 characters. An Oracle VARCHAR can be a length of up to 4000 characters. Tables with one CHARACTER columns exceeding 4000 characters Why: An Oracle CHAR can be a length of up to 2000 characters. An Oracle VARCHAR can be a length of up to 4000 characters. An Oracle LOB column (ie CLOB - character - or BLOB - binary) can hold up to 4 gigabytes in size. A Oracle LONG data type can be up to 2 gigabytes in size. However, only one LONG column can exist on a tableshould not be used anymore. In the past LONG datatypes had to be used for these columns but only one LONG column could exist on a table. Oracle9i can have up to 1000 LOB columns on a table. Tables with two or more CHARACTER columns exceeding 4000 characters Why: An Oracle CHAR can be a length of up to 2000 characters. An Oracle VARCHAR can be a length of up to 4000 characters. A LONG data type can be up to 2 gigabytes in size. However, only one LONG column can exist on a table. Oracle 8 has the LOB data type that can be up to 4 gigabytes in length and there can be up to 1000 LOB columns on a table. It is 1000 since this is the maximum number of columns on a table. Tables with index on CHARACTER columns that exceed 4000 characters Why: Character columns greater than 4000 characters can only be LONG and LOB. Oracle does not allows full text indexationes on these types ofLOB columns (Oracle Text). Column defaults that include DATE or FUNCTION Why: These column defaults will may need to be rewritten manually. The schema converter does not automatically Oracle Migration Workbench tries to convert these default types. Check constraints Why: The check constraints may need to be manually edited to conform to Oracle syntax. Tables with SERIAL columns Why: Informix SERIAL data types columns are automatically converted if the Oracle Migration Workbench Oracle " Informix Conversion Kit" is used. They become NUMBER columns in Oracle, and a sequence associated to a trigger isare created for each column(This may not be exactly what is desired, so manuallly changes may need to be made.). However, all insert statements will need to change to call the "nextval" function. Tables with DATETIME columns to ten thousandths of a second, when this precision is needed Why: The classical Oracle DATE data type only stores time to the second. The Informix DATETIME data type can be converted to a NUMBER with a sequence, or a DATE without the thousandths of a second, or to the new Oracle9i TIMESTAMP data type. The Oracle Migration Workbench does not yet support the new Oracle9i data types. Choosing between NUMBER and DATE It depends on whether the DATETIME column is used in an index to uniquely identify a row. If the column is a number, a sequence must be used, otherwise, the column is a DATE datatype. Alternatively, the new Oracle9i datetime datatype can be used manually to convert to Oracle9i. Tables with INTERVAL columns Why: Informix INTERVAL columns are automatically converted to a NUMBER if the Oracle Migration Workbench Oracle " Informix Conversion Kit" is used. Oracle8i does not support an INTERVAL column as a date datatype. Alternatively, the new Oracle9i INTERVAL YEAR TO MONTH or INTERVAL DAY TO SECOND datatypes can be used manually to convert to Oracle9i. Number of triggers Why: The Oracle Migration Workbench normally converts triggers and stored proceduresTriggers will need to be manually converted. However, there are some limitations to the Migration Workbench parser and All all triggers need to be graded on level of complexity(easy, average) and complex to better evaluate the effort).  Current use of stored procedures (if applicable) Total number of stored procedures Why: The Oracle Migration Workbench normally converts triggers and stored procedures. However, there are some limitations to the Migration Workbench parser and all triggers need to be graded on level of complexity(easy, average) and complex to better evaluate the effortStored procedures will need to be manually converted. All stored procedures need to be graded on level of complexity(easy, average and complex). Percentage of stored procedures using temporary tables Why: The Migration Workbench converts temporary tables to Oracle global temporary tables. Unlike Informix Dynamic Server temporary tables, Oracle temporary table structures are persistent across sessions, therefore the converted CREATE TEMP TABLE statement is only ever executed once within the Oracle databaseTemporary tables are not supported in Oracle. Each use of a temporary table needs to be analyzed to see how it can be migrated. Percentage of stored procedures using backwards scrolling cursors Why: Backward scrolling cursors are not supported in OraclePL/SQL. Each use of backward scrolling cursors needs to be analyzed to see how it can be migrated. Oracle9i has introduced support for scrollable cursors in OCI and JDBC, but not yet in PL/SQL. Percentage of stored procedures that are cursory procedures (ie using “return with resume”) Why: "Return with resume" is not supported in Oracle in the same form. With Oracle Migartion Workbench, t he result set returned by an Informix Dynamic Server cursory procedure is emulated by adding a REF CURSOR variable to the parameter list of the converted PL/SQL procedure Each use of " return with resume" needs to be analyzed to see how it can be migrated.  Percentage of stored procedures that are cursory procedures Why: May need special coding to migrate to Oracle.  Current use of Embedded SQL/C or SQL/COBOL Number of files to translate Why: This is a first indication of the complexity of the conversion. Embedded SQL in C or COBOL should generally be converted to Oracle Pro*C or Pro*COBOL. Oracle provides an "Informix ESQL converter" to help in the process, but this utility dates from an old version ( Oracle7.3) . An Informix ESQL/C to PRO*C facility for the Oracle Migration Workbench 2.0.2 is currently being developed. Embedded SQL being an ANSI standard and Oracle9i now having a lot of compatibility features, manual conversion is also an option. The following questions should help to measure the difficulty. Smallest number of files able to test with Why: This would help to prototype the migration effort Number of modules with ESQL/C using only static SQL Why: The Oracle "Informix ESQL converter" will automatically convert most of the code in the Embedded SQL programs. More on this can be found in section IIIThese modules tend to be much erasier to port to Oracle Pro*C. Also the Oracle Migration Workbench 2.0.2 facility will only support these. Number of modules with ESQL/C using partially dynamic SQL Why: This is the case when the number of select list items, the number of placeholders for input host variables and the data types of the input host variables are known at precompile time. These modules are more complicated but still relatively easy and can be ported to Oracle Pro*C (or Pro*COBOL) using dynamic SQL method 3. Number of modules with ESQL/C using fully dynamic SQL Why: These modules tend to be more complex. With Oracle, it may be preferred easier to use the Oracle Call Interface in stead of Embedded SQL to implement this. This is because Informix dynamic SQL is different than Oracles’ dynamic SQL. However, one can also keep the same precompiler approach. Please note that Oracle9i implements ANSI dynamic SQL, also known as SQL92 dynamic SQL. Number of modules using backward scrolling cursors Why: Backward scrolling cursors are not supported in Oracle precompilers. However, in C, the Oracle9i Call Interface (OCI) implements supports for scrollable cursors. Each use of backward scrolling cursors needs to be analyzed to see how it can be migrated. Does the application make use of the ESQL/C DateType Functions ? Why:These are Informix proprietary functions that will require changes. Date types: datestr(),rdayofweek(),rdefmtdate(),rfmtdate(),rjulmdy(),rleapyear(),rmdyjul(),rstrdate(),rtoday() Decimal types: deccvasc(),dectoasc(),deccvint(),deccvlong(),dectolong(),deccvdbl(),dectodbl(),decadd(),decsub(),decmul(),decdiv(),deccmp(),deccopy(),dececvt(),decfcvt(),decround(),dectrunc() Number formatting routines: rfmtdec(),rfmtdouble(),rfmtlong() Datetimes and interval routine: dtcurrent(),dtcvasc(),dtextend(),dttoasc(),incvasc(),intoasc() Other ESQL/C Library Functions: bycmpr(),bycopy(),byfill(),byleng(),ldchar(),rdownshift(),rgetmsg(),risnull(),rsetnull(),rstod(),rstoi(),rstol(),rtypalign(),rtypmsize(),rtypname(),rtypwidth(),rupshift(),sqlbreak(),sqlexit(),sqlstart(),sqldetach(),stcat(),stchar(),stcmpr(),stcopy(),stleng()  Current use of Informix 4GL Number of Informix 4GL forms Why: The number of 4GL forms will impact the estimate for converting. Do you expect to use third party tools to migrate these Why: A There are a couple of third party toosl which can decrease automate all or part of the conversion estimateprocess. It can also negative impact on the future viability of the system. More on this can be found in section III. Do you expect to manually redesign these using Oracle Designer Why: If the Informix 4GL is to be totally rewritten, more time will be needed to perform the application migration.  Current use of other application development tools Do you use UNIFACE, Powerbuilder or some other third party application development tool? Which one? Why: Typically independent 3RD party application development tools are easier to migrate than proprietary tools such as Embedded SQL/C, Informix 4GL or Informix New Era. Most tools support the major database vendors: Oracle, Sybase, Informix and Microsoft SQL Server. How many windows does the system have? How many have database access? Why: If the database access code contains Informix specific syntax it may need to be manually modified.However Oracle9i introduces numerous compatibility features in SQL. Is the SQL embedded in the tool or are stored procedures used? Why: As a rule, it is easier to migrate applications that uses embedded SQL then it is to migrate applications that use stored procedures. This is because stored procedures contain a proprietary database SQL programming language and return results to the client in a proprietary fashion. Support DBA Maintenance Scripts? (Examples: backup, recovery, database integrity, index rebuilds) Why: The scripts will contain database proprietary UNIX commands and SQL.. DBA tools and scripts? (Examples: 3RD party backup tools, 3RD party DBA tools, import/export scripts) Why: These tools and scripts will have to migrated, or alternatives found. Other? (Examples: ad hoc scripts) Why: These tools, utilities and/or scripts will have to migrated. Other special logic/subsystems to migrate Any other special subsystems or special processing the system performs? (Example: A security subsystem that implements security, by user, horizontally/”by row”. ) Why: These special subsystems have to migrated, or alternatives found. Perhaps Oracle has the same functionality built-in. Documentation System documentation (Examples: system flows, program functionality) Why: System documentation will most likely change. User documentation Why: User documentation will most likely change. Section III - INFORMATION/SOLUTIONS Informix Database The Informix database migrates fairly easy to the Oracle database. A few differences are worth noticing: The SERIAL datatype, used to generate primary key values, must be implemented using sequence numbers and triggers in Oracle. INTERVAL – Oracle9i supports the INTERVAL YEAR TO MONTH and INTERVAL DAY TO SECOND datatypes. Scrollable cursors – Oracle9i supports scrollable cursors at the OCI level. INTERVAL - Convert to number. Informix SQL Informix SQL and Oracle SQL are both based upon the same underlying ANSI database language standards. However, RDBMS providers have often added their own extensions to the standard language. This engine-specific SQL should be converted manually. Informix extensions include: MATCHES - Matches is a string matching function that allows you to locate quite complex string expressions. There is no equivalent in Oracle. The closest feature is combined use of LIKE and SUBSTRING in Oracle. Solution: Manually convert using Oracle LIKE and SUBSTRING. Backward scrolling cursors. Solution: Scrolling cursors can be simulated by using PL/SQL tables. In order to determine an effective solution, the SQL will need to examined in detail. For example, backwards scrolling cursors may fetch absolute (fetch a specific record in the cursor) or fetch relative (based on last record, fetch any number backwards). These types of details will need to be highlighted during program mapping and analysis. Informix Stored Procedures The Migration Workbench parser may not convert some SPL statements to PL/SQL code. Generally, this happens when the statement functionality cannot be replicated in PL/SQL, if the statement is unnecessary within the PL/SQL code, or if the statement requires manual conversion by the DBA. The following list of statements are currently not supportedInformix stored procedures can be migrated to Oracle with the help of our Stored Procedure converter tool. However, there are a few features of Informix, that do not map to features in Oracle, or only maps with modifications: All DDL statements within stored procedures, with the exception of the CREATE TABLE statement Solution: Manual conversion. DBINFO('sqlca.sqlerrd1') Solution: Manual conversion. DBINFO(DBSPACE, number) Solution: Manual conversion. All SET statements with the exception of SET DEBUG FILE Solution: Manual conversion. Temporary tables. Oracle does not have a concept of temporary tables, but we provide white papers that outlines the possible implementations. Solution: Attached is two white papers on temporary tables. Backward scrolling cursors. Oracle does (currently) not support backward scrolling of cursors in PL/SQL, and there is no simple way to implement them. It is expected that a future version of Oracle will support it, but this will at the earliest be after version 8.1. Solution: Scrolling cursors can be simulated by using PL/SQL tables. In order to determine an effective solution, these types of stored procedure will need to examined in detail. For example, backwards scrolling cursors may fetch absolute (fetch a specific record in the cursor) or fetch relative (based on last record, fetch any number backwards). These types of details will need to be highlighted during program mapping and analysis. Return with resume. Informix stored procedures can return data to the calling environment by means of a SQL query inside the stored procedure. The Stored Procedure Converter implements this using cursor variables, which implies application modifications are necessary. Solution: Implement changes to the application. NOTE: Oracle's DMS is working on a kit to automatically convert Informix stored procedures to Oracle. The kit supports all Informix constructs except for: DDL statements, dynamic SQL, ON EXCEPTION IN, WHENEVER, SYSTEM and administrative related commands. Informix Embedded SQL/C and COBOL The syntax used in Informix for Embedded SQL from C and COBOL programs is a little different from that used by Oracle. However, our Informix ESQL converter will assist in migrating Embedded SQL programs. This facility will be integrated to Oracle Migration Workbench with support for static SQL in version 2.0.2 of the workbench and with support for dynamic SQL in version 2.0.3. As is the case with Informix stored procedures, backward scrolling cursors is not available from Oracle Embedded SQL. However, support for scrollable cursors has been added in C to the OCI. Frequently, Informix Embedded SQL has been used purely to implement Dynamic SQL, i.e. SQL processing, where the actual SQL statements are not known until runtime. With Oracle, it may be preferred to use the Oracle Call Interface in stead of Embedded SQL to implement this. Solution: The majority of this code can be converted using the Oracle DMS ESQL/C to Pro*C converter(convertor is written and provided by Oracle). However, there will be some instances where manually rewriting of the code will be necessary. For example, error handling may require manual changes. Informix 4GL Although similar in scope, the Informix 4GL language is very different in implementation from the Oracle SQL*Forms tool. Third party tools exist to ease in a migration from Informix 4GL to Oracle Developer or Oracle Designer, however, an application rewrite should also be considered. AnoOther third party tools exists, which will deploy Informix 4GL applications unmodified (i.e. both application code and user interface is unmodified) running on an Oracle database and without any Informix libraries or other proprietary Informix code. Furthermore, these applications may then also benefit of improved user interfaces (GUI and/or thin client). Solution: Third party tool to migrateion automatically or rewrite in Oracle Developer or Oracle Designer. Third party tools are offered from Fourjs (www.4js.com), QueriX (www.querix.co.ukwww.querix.co.uk ) and, ArtInSoft S.A.(www.artinsoft.com) and Freesoft (www.freesoft.hu ). The following information has been prepared by Oracle Migration Technology Group. FOUR J's DevelopmentTools Ltd 20, rue Troyon 92310 Sevres France +331 55 64 07 00 Company Description: Four J's is a company that offers tools for the generation and development of applications through its Business Development Suite. Target Market Overview: Rapid Application Development; 4GL and IRAD; Legacy Migration Tools; eBusiness solutions. Product/Service: Four J's Business Development Suite is a technology that combines 4GL with Application Generator capabilities to derive a new application. Main Features: Nearly transparent migration to Oracle Enhances the look and feel An integrated development environment An Application generator that designs screen layouts and creates 80% of the code An application across many clients, Win. 95/98/2k,X.11, HTML, Java, WAP, XML Separation of business logic from presentation logic An efficient thin-client technology Hardware/Operating System Supported: Microsoft Windows NT, Motorola UNIX, SCO UNIX, SUN OS,Sun Solaris (Intel), Sun Solaris (SPARC), Wyse UNIXSystem V Querix UK Limited Querix House 36A London Road Southampton Hampshire-SO15 2AG, United Kingdom +44 (0)23-80232-345 Company Description: QueriX is a fast-growing software tool author specializing in 4GL compilers that run on Oracle databases including GUI (Windows, Java and HTML) Interfaces. The company's products are used for virtually any programming purpose, and the embedded SQL provides a powerful environment for developing applications that utilise relational database systems. The comprehensive portfolio of services QueriX offers includes total migration solutions, as well as consultancy services, advising clients on how 4GL applications can be restructured to reduce program overhead and provide for easier maintenance. The company's products are distributed in China, the Asia-Pacific, North and SouthAmerica, South Africa, and Europe. Target Market Overview: Current QueriX customers range from developers of products for vertical markets, such as insurance and pharmaceutical firms, to horizontal markets including accountancy and data warehousing. Clients include Sherwood International, Drogueria Uruguay, and Brunthaler Industrielle Informationstechnik GmbH Product/Service: The Hydra - 4GL compiler for Oracle Phoenix Windows GUI Chimera Java GUI Arachne Web Technology Main Features: 4TH generation development tool for easy creation of front-end applications with a relational database engines as the back-end server Analyzes Informix 4GL code and converts into C programs Connect to Oracle as well as Informix databases Maintains the same look and feel of original application Nearly transparent migration Run-time free pricing Hardware/Operating System Supported: All ORACLE supported platforms: Compaq RISC, Ultrix, Data General AOS/VS, HP UX, IBM RS 6000 AIX, Linux, Microsoft Windows, Microsoft Windows NT, SCO MPX UNIX, SCO UNIX, SunSolaris (Intel), Sun Solaris (SPARC) Artinsoft Artinsoft SA Ofiplaza del Este Edificio A, piso 3 San Josщ, SJ-923-7050 Costa Rica USA telephone +(506) 283-3144 EMEA telephone +44 (0)20 8263 2817 Company Description: Artinsoft gives organisations the "freedom" to choose their platform and strategic direction, enabling resources to be focused on more profitable opportunities. Product/Service: Freedom is an automated, rapid source language translation and database migration service. The Freedom tool migrates 4GL code to Java. This technology is developed by Artinsoft to convert ~90% of the code automatically to Java. Main Features: Fast software generation through automation Solidly based on specialization knowledge Hardware/Operating System Supported: All ORACLE supported platforms Freesoft FreeSoft Ltd. Vahot u. 6. Budapest, H-1119 Hungary +36 1 3712910 Company Description: FreeSoft Ltd. is a Hungarian software development company and a Certified Solutions Partner of Oracle, member of the Oracle Migration Technology Initiative group. Besides migration project services Freesoft uses up-to-date WEB, Internet technology. ORACLE Designer, Developer, JDeveloper, JAVA, Javascript, C++, HTML, XML are the main components of their tools. FreeSoft's Quality Management System has gained the certificate justifying the meeting of requirements of ISO 9001 standard for the scope of "Custom-designed software application systems development, support and software license sale" Target Market Overview: FreeSoft helps organisations to maximise value from investments in information technology by supplying software solutions, software and systems integration services, consultancy to the highest professional standards. Freesoft have multinational companies, financial institutions and administrative organizations as clients. Product/Service: Available migration tools I2O Ingres to Oracle/Forms X2O: Informix to Oracle/Forms N2J :Adabas/Natural to Oracle/Java A2J : Access/VB to Oracle/Java Main Features: Fastest and most cost effective solution (against rewriting or manual conversion) The original functionality remains consistent Ability to renew or add new functionality in a state-of-the-art development environment Web-enabling the inherited legacy functionality The QueriX tool has the following features: 4TH generation development tool for easy creation of front-end applications with a relational database engines as the back-end server Analyzes Informix 4GL code and converts into C programs Connect to Oracle as well as Informix databases Maintains the same look and feel of original application Nearly transparent migration Run-time free pricing NOTE: Because C is generated, programs must be modified and maintained using a text editor and C. However, the same 4GL syntax is used. The ArtInSoft tool has the following features: Providing a Java Generator initially Support for Oracle Designer in future Informix New Era Informix New Era is a GUI based tool. There is currently no migration path (except a rewrite) from New Era to any Oracle based tool, and New Era applications cannot currently run on an Oracle database. Solution: Rewrite in Oracle Developer or Oracle Designer.  if " REF DocControlNumber  " = "Error! Reference source not found." ""  REF DocControlNumber     PAGE 1 if "styleref TitlePartner Technical ServicesDesign and Migration Services" = "Error! No text of specified style in document." "" styleref TitlePartner Technical ServicesDesign and Migration ServicesPartner Technical ServicesDesign and Migration Services if "styleref "Heading 2"Executive SummarySection III - INFORMATION/SOLUTIONS" = "Error! No text of specified style in document." "" styleref "Heading 2"Executive SummarySection III - INFORMATION/SOLUTIONSExecutive SummarySection III - INFORMATION/SOLUTIONS  FILENAME \* FirstCap Inform_ques_temp.docInform_ques_temp.doc  if " REF DocVersion  3.0 2.0 " = "Error! Reference source not found." "" "(v.  REF DocVersion  3.0 2.0 )" (v.  REF DocVersion  3.0 )(v.  REF DocVersion  3.0 2.0 ) /“Ё–™*œЏЏЄв/Ѕт=ІаЇаЈаЉ5ЊeŒЋџЁ–œЏЏЄв/Ѕт=ІаЇаЈаЉ5ЊeŒЋ…дџhxџhxџhxџhxџhxџhxџhxџhxџhxЗoЇЗoЇЗoЇ‚_ ‚_ ˆ[ witoB:љBЌј%И  !і   ШŠі C ЬШŠШŠ(ŠШ AЯУџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџРџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџРџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџРџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџРџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџРџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџРџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџРџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџРџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџРџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџРџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџРџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџРџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџРџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџРџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџРџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџРџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџРџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџРџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџРџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџРџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџРџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџРџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџРџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџРџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџРџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџРџџџџџџџџџџџџџџџџџџџџџў?џџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџјџџџџџџџџџРџџџџџџџџџџџџџџџџџџџџџјџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџ№џџџџџџџџРџџџџџџџџџџџџџџџџџџџџџ№?УџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџрџџџџџџџџџРџџџџџџџџџџџџџџџџџџџџџ№џ№џџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџСџуџџџџџџџџРџџџџџџџџџџџџџџџџџџџџџсџќџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџУџёџџџџџџџџРџџџџџџџџџџџџџџџџџџџџџсџќџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџУџјџџџџџџџџРџџџџџџџџџџџџџџџџџџџџџёџў?џџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџУџќџџџџџџџџРџџџџџџџџџџџџџџџџџџџџџ№џў?џџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџсџќџџџџџџџџРџџџџџџџџџџџџџџџџџџџџџјў?џџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџёџјџџџџџџџРџџџџџџџџџџџџџџџџџџџџџќ?ќ?џџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџјџ№џџџџџџџџРџџџџџџџџџџџџ§џџџџџџџџџ€?џџџџџџџј?џџџџџџџџџўџџџџџџџџџџџџџџј?џџџџџџџџџў?џСџџџџџџРџџџр>№€јќр№€р€џџ€xрРџџ€<Р№ќ8р€Чј€РјРџрўўџџџџџРџџџр№p<№€рџџџ8№€џџ€<Рр№ќ8р€8№€ƒƒ№Рџрўќ?џџџџџРџџџќќрќр~ј>џџџ>ј?уџџ№рџ№Ујџќ?№ј№!№сќ№џќџР|јџџџџџРџџџџў‡ўœ№ў№џќ<џџџўџќ>љџџј?сџ‡№џƒќ?‡џќ?№ј< рџ№ў№ќ№џџўџРј?џ№?ЯџџџџџРџџџџџ‡ўСќј~№џќ<џџџўџќ>џџџј?сџ‡№џ‡ў‡џќ?№ј~сџ№ќ№|?№џџўџРјџ№џџџџџџРџџџџџ‡ўсќ?ќ>№џќ>џџџўџќ>џџџј?сџ‡№џў‡џќ?№јсџ№ќ?ј|?№џџџџСј?џ№џџџџџџџРџџџџџЯ‡ўсќ?ќ>№џќ?€?џџўџќёџџўџќ<џџј?сџ‡№џў‡џќ?№јџрџ№ќ?ј№џќ?ёџџўџќ>Рџџј?сџ‡№џў‡џќ?№јџрџ№ќ?ј|?№џџџ№ќ?У№|џџџџџРџџџџјџ‡ўсќ?ј>№џќ?№џџўџќ>№џџј?сџ‡№џ‡ў‡џќ№јрџ№ќ?№|?№џџџ№ќ?У№џ‡џџџџџРџџџџџќсќ?№~рќјрџўџј?ёџџј?Рџ№џ‡ќ?Žќрќрџрў№ј№џџџјў?РxџџџџџџРџџџџўќ?Чсќ?р~Рќ№рџј?ј?ёџџј?€№Уј>јСў?РрўсјрџџџјќўР8џџџџџРџџџџјџp?уУќўрўр‡Рџјр‡уџџј?РРс№џ€рџСјџџџјќџ€?Z[rsuwy‡ˆЃЄЛМОРТежёђ    89PQRSU^_z{’“”•—ЃЄПРзийкм§ў12346JKfgієіђшђшђшсошђшђшђшсошђшђшђшсошђшђшђшсошђшђшђшсошђшђшђшсошђшђшђшсошђшђшђшсошђшђшђшсошђшђшAa BEF.\[auDBFт][aaa uDBFт][a Xg~€ƒ›œЗИЯабвдтуўџ     % & A B Y Z [ \ ^  ‘ Ќ ­ Ф Х Ч Щ Ы ъ ы     ! # % B C ^ _ v w y { } Б В Э Ю х ц ш ъ ь ѕ і   ) * , . 0 [ \ w x   ’ ” – Ѕ І С Т й к §ѓьщѓ§ѓ§ѓ§ѓьщѓ§ѓ§ѓ§ѓьщѓ§ѓ§ѓ§ѓьщѓ§ѓ§ѓ§ѓьщѓ§ѓ§ѓ§ѓьщѓ§ѓ§ѓ§ѓьщѓ§ѓ§ѓ§ѓьщѓ§ѓ§ѓ§ѓьщѓ§ѓ§ѓ§ѓьщѓ§ѓ§ѓ§ѓAa BEF.\[auDBFт][aa\к м о р   ! " 9 : < > @ S T o p ‡ ˆ Š Œ Ž œ  И Й а б г е з ѓ є   ' ( * , . Q R m n … † ˆ Š Œ š › Ж З Ю Я б г е ч ш  "#$9i}Žвфљ•–‰ŠјѕыщыщыщыјѕыщыщыщыјѕыщыщыщыјѕыщыщыщыјѕыщыщыщыјѕыщыщыщыјѕыщыщыщыјѕыщпнкгнЬкнЪнЪU BEFu+[&] BEFt+[&]A]]uDBFт][a auDBFт][aAa BEF.\[aPŠF\nƒ (.56IKœžёіPІжс 9ЖЙЇ§'агд,3:ctƒЗОХO+,-•™š­ #6ёѕї7>Ew §їѕ§§§ю§§§§ьхпьиььждьбЪьбУьбМьЙдьВбьжьбЋьжьбЋьь BEF{+[&V BEFЫ[[VU] BEFz+[&V BEFЃZ[V BEFy+[&VAVa U BEFЯ[[V BEFб[[ BEFб[[VV BEFw+[&]A BEFw+[&]A Јиє Ÿ Ђ Ѓ І Т _"c"d"f"‚")$*$/$…$%% %%%F%Т%з%ї%&&&%&&&(&/&>&“&­&Ў&'%'P'W'Y''A)G)I)Œ)у)ь)ё)љієљєєэієчрйгЬЦУіОУМєММУМєЕЎЇЎЕ єі єі є™Ї’МУіММєіє BEFВZ[V BEFЏZ[V BEFЊZ[V BEFБZ[V BEFАZ[V BEFЉZ[Va A]a Aa  BEF$\[ BEF$\[a  BEF%\[ BEF%\[V BEF%\[a  BEF#\[ BEF‚+[&VVAV BEF+[&V8ё)ќ)** * * ***'*5*7*8*;*<*=*?*m*‰*Ž*’*Ж*о*++$+&+8+++”+–+Б+ќ+,9,w,x,,“,–,р,с,ф,-W-X-Y-^-›-К-Л-Х-Я-.š.­.Џ./љїљєїэєэїэїышыыїєсїєсїыыїкыыїгєїЬХєЬїОєїєїшыИїБїЊЃїœ BEF5[[V BEF3[[V BEF+[[V BEFŠ+[&V BEFŠ+[& BEF)[[V BEFˆ+[&V BEF‰+[&V BEF‡+[&V BEF(\[a  BEFЛZ[VAa a  BEF†+[&VAVV BEF…+[&V:/!/$/+/,/м/ы/ѓ/0#0:0;0<0=0C0`0А0Ы0э0§0џ01171X1`1a1‰1‘1’1ž1Ї1О1П1Р1У1Ш1Ъ1н1у1222 222]2^2h2i2k2‰2Є2Љ2Ў2В2ё2ђ2ў2љієієэцэпиэєждєЭієцєЦєцПцЦцЦцПицєМддєЕЎЇЎ іє™Ў™Ї™ЇіЎє’є BEFI,[&V BEFF,[&V BEFE,[&V BEFH,[&V BEFG,[&V BEFD,[&VAa  BEFA[[V BEFB[[V BEFŒ+[&Va A BEFC[[V BEF8[[V BEFЕ+[&V BEF‹+[&VVAV BEF6[[V9ў233 3#3,3-3.3e3‡3Œ3•4%5'5*5+5,5.5e5j5›677!7#7e7š7 7І78b8c8e8i8j8k8m8Œ8Ќ8Ч8Ш8Щ8§8992939н92:4:9:;:<:x:Ћ:Џ:А:в:п:р:§:ў:љієђяэєљієэцээєпієээєіиєбєэцЮээЧэЧэєРєЙіРієэЖЮієяАЉЁBEFо[[Va  BEFн[[a  BEFс[[Ua  BEFЛ[[V BEFК[[V BEFР[[a Aa  BEFИ[[V BEFЙ[[V BEFЈ[[V BEF+\[a a Va AVAV BEFI,[&V=ў:; ; ;;;X;^;š;Ў;ћ;ќ; <<<‡<Е<И<Ъ< =-=1===G=H=I=K=M=P=z={=€=Б=В=Г=Ж=З=їячячпчпзЯЧзПИБЊБЊЃœЃœЃї”Œ…xяpŒi”aBEFи[[Va  BEFю[[a BEFъ[[Va  BEFо[[a  BEFй[[ BEFг[[a BEFю[[Va BEF,\[Va  BEFъ[[V BEFщ[[V BEFш[[V BEFч[[V BEFх[[VBEFх[[Va BEFф[[Va BEFц[[Va BEFу[[Va BEFт[[Va BEFр[[Va BEFп[[Va BEFн[[Va #З=Й=э=ђ=ѓ=‹>Љ>А>Д>Л>Ш>Щ>Я>г>є>§>??????V?W?]?m?’?В?Ч?і?@@ @ @@@Q@R@V@„@‰@@‘@’@–@Ÿ@Ё@Ђ@Ѕ@њјіѓьхьоьізазазіјЩјТЛДа­І­Ÿ­Ÿ­˜­˜а‘а­‘­˜‘Š˜Д„} BEF-\[a  BEFѓ[[ BEFљ[[V BEF\[V BEFј[[V BEFћ[[V BEFњ[[V BEFї[[V BEFђ[[V BEFђ[[a  BEF№[[a  BEF,\[a  BEF\[V BEFю[[V BEF\[V BEFэ[[V BEFь[[VAVVa  BEFи[[0Ѕ@І@Ј@Ь@в@о@ф@ A"A,A3AVAWA~AЬAЭAеAђAB=B_B`BbBdBeBgBšBеBтBфBьBѓBўBCCCACœCCžCŸCЁCЂCЄCтCуCхCцCјђ№щ№чрчнжчнчнчЯрШЯСч№К№№чШчШГШЌШЌГчЌІž›•Ž‡€ BEF.\[a  BEF\[a  BEF \[a  BEF \[Va BEF-\[Va  BEF\[ BEF\[V BEF\[V BEF-\[a  BEFі[[V BEF\[V BEFѕ[[V BEFє[[VAV BEF\[VV BEF№[[a a  BEFя[[ BEFя[[a /цCDD&D-D.D/D0D:D;D?§§§щ§§§§щчхучррР§§ž§§‚§ИlЙЛ Оl ф\(џџџџ!ИlНФџЙКЛ Оl ф\(џџџџџџџџП ИlЙКЛ Оl ф\(џџџџџџџџП +!И`ЙЛ О $ 'm(?@ABCDEFGHIVW`enopqrs§ы§§ы§§ыщчхщтттЛ§§§’(ИlНФџЙКЛ О(l  gЬ'џџџџџџџџџџџџП &ИlЙКЛ О(l  gЬ'џџџџџџџџџџџџџџП +!ИlЙЛ Оl ф\(stuvwxyz{|}~€‚ƒ„ъ4zУоППоППŠоППŠо‡‡Š…ƒ&ИlЙЛ О l  gЬ'!ИlЙЛ О(l  gЬ'џџџџџџ  4€! h˜ў 4€hУV˜н7„е _ Ь & ~ э 1 — с A  и /  ж #%&'9‘’€Ž–7Žўўќќўќўќќќќќќќќќўќќќќќќњњјіђђђјі№юђЫ" и 4€h.8!и $Žі‰ŠFGHSмќ§ ()*+,-.6GHIJKUVW`aннййжважЮЬаЩЩЩЩНЩЩЩЩЩЩНЩЩЩЩЩНЩЩЩЩЩ ИlНШОи ќж)!!xи " и 4€h.8"abuvw|}~Ž˜™š›œž­ЎЏАЙКЛЮЯаежзчшщёђѓєѕі  §§§§§§§§§§§§§§§§ё§§§§§§§§§§§§§§§§§§§§§ё§§§§ ИlНШОи ќж)+  *+,-2345EFGHPQRSTUVWXop}~Їж§§§§§§§§§§§§§§§§§§§§§§§§ёюьъшцфУ 5 и  4€5! ИlНШОи ќж) жзийклмнопр9ЗИЙКТУФХЦЧШЩЪттттттттттСттС    ›тттттттт6и  5 и ђў 4€  @ ˜ў 4џhЗ 4€ЪЫЬЭЮЯабвгдлмнопрстуфхцчя№ёђѓєѕіїјљттттттттттрТтттттттттттрттттттТТТТ 4€6 4€"љњћќ§ўџЇ§џтттттттрПЁЁЁЁЁЁƒeт 4€! 4€ 4€ 5 и  4€5 4€'абвгд     O•–—˜™§лММММ§лššššššššššš§лММММ! ъи  4€  4€!5 и  4€5™š›œ­ёђѓєѕіїxš›œžЧпОВЏnnnnnnЏknnnnk6  4€!5 и  4€5 ИlНШО”џф*Г0 Йў 4€ ъ 4€ЧШЩЪЫэюя№ёђії‘’“”ссссоссссНœkссссН!5 и  4€5 ИlНШО”џф*Г0 Йў 4€ ъ 4€6  4€”•–ЈŸ   Ё Ђ Ѓ Є Ѕ І Т _"`"a"b"c"d"e"пгаЎnnпгаЎЎЎЎЎЎп ъ 4€  4€!5 и  4€5 ИlНШО”џф*Г0 Йў 4€e"f"‚"*$+$,$-$.$/$…$%%%%%% % %F%єёЯЪЪЪЪЪІ„€€€€ztєё Йў ъ !5 и  4#5 А  4џhxЗА ъ!5 и  45 ИlНШО”џф*Г0F%Q'R'S'T'U'V'W'X'Y''B)C)D)оППППž}\PMоПП5 ИlНШО”џф*Г0 Йў 4€ ъ 4€   4€  4€!5 и  4€ D)E)F)G)H)I)Œ)7*8*9*:*;*<*=*>*?*m*+ +!+ссРŸ“nРРРРРРŸ“nсс!5 и  4€5 ИlНШО”џф*Г0 Йў 4€ ъ 4€  4€!+"+#+$+%+&+8+++‘+’+“+”+•+–+Б+X-Y-Z-[-\-]-ссРРДБссссРРДБссссс!5 и  4€5 ИlНШО”џф*Г0 Йў 4€  4€]-^-_-`-Л-<0=0>0?0@0A0B0пОВЏnnnnnL! д 3 4€  4€!5 и  4€5 ИlНŠО”џф*Г0 Йў 4€ д  4€ B0C0`0Р1С1Т1У1Ф1Х1Ц1Ч1Ш1Щ1Ъ1н1 3!3"3ѕђаББББoocђаББ ИlНШО”џф*Г0 Йў 4€   4€  4€!5 и  4€5 ИlНШО”џ`'"3#3$3%3&3'3(3)3*3+3,3-3.3/3031333сРРРРРРРРРРŸŸ“uu 4€ ИlНШО”џф*Г0 Йў 4€   4€  4€3343e3‡3'5(5)5*5+5,5-5тФСŸ€€€__> Йў 4€ ”џ 4€  4€!5 и  4€5 4€! 4€ -5.5e57777 7!7"7#7e7c8d8e8f8g8h8єёЯЎЎЎЎЎёЯbbbbb  4€ ИlНШО”џU*A+ їљ 4€ ”џ 4€!5 и  4€5 ИlНШО”џš*†+h8i8j8k8l8m8Щ84:5:6:7:8:9:::сРŸ~roMсссс~~!5 и  4€5 ИlНШО”џ|)h* Йў 4€ рў 4€   4€  4€ ::;:<:x:Ќ:­:Ў:Џ:А:Б:В:Д:Е:єгаЎЎЎгєqS! 4€ 4€5  4€!5 и  4€5 Йў 4€ ИlНШО”џ|)h* Е:р:§:I=J=K=L=M=N=O=P={=В=Г=Д=Е=Ж=З=И=Й=тпННННННœпooooooœ 5  4€ ИlНШО”џ|)h* Йў 4€!5 и  4€5 4€Й=э=????????W?Ё@Ђ@Ѓ@Є@Ѕ@І@Ї@Ј@о@`BaBbBcBdBeB§лММ››››§лллллл›§лММ››› ИlНШО”џ|)h* Йў 4€  4€!5 и  4€5eBfBgBšBCžCŸC CЁCЂCЃCЄCцC/D0DŸD D`EaE EпгаЎЎЎппппгаЎnnnnn 5  4€5  4€!5 и  4€5 ИlНШО”џ|)h* Йў 4€ EЁEFF'G(G)G*G+G,G.G/GппппННœrrT! 4€ 4€ ИlНШО”џ|)h* Йў 4€!5 и  4€ 5  4€ /GKGhGЎGЏGАGБGВGГGДGьGжHзHиHтпЛœœœ{{oпMœœ!5 и  4€ ИlНШО”џ() Йў 4€  4€#5 †ўи  4€5 4€ иHйHкHлHмHнHоHI‘I’I“I”I•I–I—I™IсссРРДБсссРДq 4€!5 и  4€5 ИlНШО”џ() Йў 4€  4€™IšIЭIЮI3JAKBKCKDKEKFKK8L9L:L;L@Ђ(Title аи x]c0\ўoёВ\BulletH  (џ<< 4џ и?ўOбТtty132c ўOвtty80]&ўOёт&hanging indent Рє$ўOђ$ Table TextU]c`ўoё` Number ListF Ј ˜ў<< 4€h.0ўO20 Heading Bar!№№/bc6ўOё"6Info Box"8& 0' 0( 0) 0* 0cўOб2tty180#0§c.ўOB. Title Bar$ аи /c$ ўOбR tty80 indent%O 0ўOb0 toc heading& и РР& аc$ўOЂq Chapter Title ўO‚ Legal(p№]"ўOЂ‘"Highlighted VariablebўOёЂInd Text*Ј &ўOёВ& Table Heading+xxUVўOБТV Checklist>,c н§ 4џh?@-@ёџв@ Macro Text!- рР €` @ р] a $@$TOC 4 .Ј `' c)@Ђё Page Number,ўO, Route Title 0аи xc$$ўOЁ$ Title-Major1UZ]fўoё"fNoteR2 Аа0§&)')()))/ 4џ8€аNote:\(/@ё2(List3Ј ˜ўPPx&ўOёB& List Indent 4Ј PP`ўoR` Bullet L1C5 @ ˜ўx 4џ З]VўOQRV Bullte L2>6  4џh-ўOrStyle17h] $@@‚$ Signature8nx] ўOЂ‘ Hyperlink^b"ўOЂЁ"FollowedHyperlink^b ' "‚"…џџџџ†џџџџ}ž Ѓgк Š ё)/ў2ў:З=Ѕ@цCF-OрaБiЗmuЮ|з‚sЩefghijklmnopqrstuvwxy‹?sУŽa жЪљ™Ч”e"F%D)!+]-B0"333-5h8::Е:Й=eB E/GиH™I{LVNУPjQ‹Sѕ\ŸktЉ}‚"…z{|}~€‚ƒ„…†‡ˆ‰Š‹ŒŽ‘’“”•–—˜™š›œžŸ ЁЂЃЄЅUnknownOracle/1œЎЪтчшј,12>Zrwx‡ЃЛРСеё   8PST^z’•–ЃПзкл§145Jf~‚›ЗЯвгтў%AY\]ЌФЩЪъ#$B^v{|БЭхъыѕ)./[w”•ЅСйоп ! 9 > ? S o ‡ Œ  œ И а е ж ѓ  ' , - Q m … Š ‹ š Ж Ю г д ч   ! # "‚O”џ•€ ”џ2%”џ•Р•@2%”џ•Р•@2%”џ•Р•@2%”џ•Р•@2%”џ•Р•@2%”џ•Р•@2%”џ•Р•@2%”џ•Р•@2%”џ•Р•@2%”џ•Р•@2%”џ•Р•@2%”џ•Р•@2%”џ•Р•@2%”џ•Р•@2%”џ•Р•@2%”џ•Р•@2%”џ•Р•@2%”џ•Р•@2%”џ•Р•@2%”џ•Р•@2%”џ•Р•@2%”џ•Р•@2%”џ•Р•@2%”џ•Р•@2%”џ•Р•@2%”џ•Р•@2%”џ•Р•@•Œ%Sjqsz}„†ˆœдUVŽ•Њп.cd™œГмпхі4EPTYjprstuvw|˜šЃ”џ•Р”џ•Р”џ•€!”џ•€ ”џ•Р ”џ•Р”џ•€ ”џ•Р ”џ•Р”џ•€”џ•€”џ•Р”џ•Р”џ”џ•Р•L•L•L”џ•Р•Œ˜DocControlNumber DocVersion _Toc428952251 _Toc428952252 _Toc428952253 _Toc428952254 _Toc428952255 _Toc428952256 _Toc428952257 _Toc428952258 _Toc428952259 _Toc428952260 _Toc428952261 _Toc428952262 _Toc428952263 _Toc428952264 _Toc428952265 _Toc428952266 _Toc428952267 _Toc428952268 _Toc428952269 _Toc428952270 _Toc428952271 _Toc428952272 _Toc428952273 _Toc428952274 _Toc428952275 _Toc428952276 _Toc428952277анEWI' € Ž Hм§Xp40Е7/DšFЃJuLЫMЃNШNŒPT№]bg}#‚ гуUd'U8 Œ • Rћn| d0в7JDЬFЊJžLиMЦNйN˜P™T^œbw}#‚Ђ и/ 0OЈ_Иo Рж€V№Ј №ѕ AIM_Version№/ DocumentName` MenuFileStack€› MenuNameStackPѓr_ Р$r_CanamИL r_Canam-ManacШKr_Claude Charbonneau`Ћr_Data Warehouse ImplementationИЯ"r_Le Groupe Canam Manac Inc.аЯ"r_Oracle№Я"r_Richard MoisanЈ”! tmp_MenuTitle+Richard MoisanClaude CharbonneauLe Groupe Canam Manac Inc.CanamOracle Data Warehouse Implementation 2.0.4Scope, Objectives, and Approach!CDM.mnu|PJM.mnu|PJM.mnu|pjmCR.mnuЪMain Menu|Project Management (PJM)|Phase Planning\'5c'5c'5c'5c'5c'5c'5c\'5c'5c'5c'5c'5c'5c\'5c'5c'5c'5c'5c\'5c'5c'5c'5c\'5c'5c'5c\'5c'5c\'5c\: Control and Reporting (CR)|Scope, Objectives, and Approach  ‡Phase Planning\'5c'5c'5c'5c'5c'5c'5c\'5c'5c'5c'5c'5c'5c\'5c'5c'5c'5c'5c\'5c'5c'5c'5c\'5c'5c'5c\'5c'5c\'5c\: Control and Reporting (CR)џ@оTimes New Roman Symbol "Arial1Courier NewWingdings"Century Gothic Tms Rmn TimesBook Antiqua 1Courier"Arial NarrowCentury SchoolbookGaramond"Р€XV Хhš(fт][ык%fE’LNh5ƒоV ƒScope, Objectives, and Approach  ;Copyright Љ 1995, Oracle Corporation. All rights reserved. PC AutomationOracle  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~€‚ƒ„…†‡ˆ‰Š‹ŒŽ‘’“”•–—˜™š›œžŸ ЁЂЃЄЅІЇЈЉЊЋЌ­ЎЏАБВўџџџ§џџџ§џџџИўџџџРўџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџўџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџRoot Entryџџџџџџџџ РFpЉ=їkСЗРWordDocumentџџџџGeCompObjџџџџџџџџџџџџjSummaryInformation(џџџџџџџџўџџџ ўџџџ ўџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџўџ џџџџ РFMicrosoft Word Document MSWordDocWord.Document.8є9Вqўџр…ŸђљOhЋ‘+'Гй0р˜ Шдьј<L \h  œ Ј ДРШаиф Scope, Objectives, and Approach knPC Automation kn<Copyright Љ 1995, Oracle Corporation. All rights reserved.NormalDocumentSummaryInformation8џџџџџџџџџџџџ јџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџўџ џџџџ РFMicrosoft Word Document MSWordDocWord.Document.8є9ВqфOracle Corporation Canada Incо5  Scope, Objectives, and ApproachOracle69Microsoft Word for Windows 95h@ь/Џ@Ј7\‰Н@H[@ЫН@|#ѕkСLNhўџеЭеœ.“—+,љЎ0Ш@Hpx €ˆ фOracle Corporation Canada Incо5  Scope, Objectives, and Approach