Oracle to Sybase ASE Migration Guide

ORACLE TO SYBASE ASEMIGRATION GUIDE

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.36.4 Use a 3rd-party ETL tool that supports both Oracle and Sybase ASE .......................................................................................... 326.5 Oracle datatypes requiring special attention for migration ................................................................................................................ 327 Migrating PL/SQL to Transact-SQL ....................................................................................................................................... 337.1 Locations of PL/SQL code ..................................................................................................................................................................... 337.2 3 rd -party tools for PL/SQL migration to T-SQL ................................................................................................................................ 338 Transactions and Locking, Oracle vs. Sybase ......................................................................................................................... 358.1 Oracle MVCC vs. Sybase locking ........................................................................................................................................................... 358.28.3Transaction-related migration issues ...................................................................................................................................................... 35Using ASE implicit/chained transaction mode ................................................................................................................................... 368.3.1 Transactional DDL .............................................................................................................................................................................. 368.3.2 Transaction processing in stored procedures ................................................................................................................................. 368.4 Using ASE explicit/unchained transaction mode ............................................................................................................................... 368.5 Using ASE transactional concurrency enhancements ........................................................................................................................ 368.6 Other transactional aspects ...................................................................................................................................................................... 379 Miscellaneous migration aspects ................................................................................................................................................ 399.1 Cursors ......................................................................................................................................................................................................... 399.2 Sequences .................................................................................................................................................................................................... 399.3 Error/Exception handling ....................................................................................................................................................................... 419.4 Outer join limitations ................................................................................................................................................................................ 419.5 Migrating JDBC/ODBC/… Applications ........................................................................................................................................... 429.5.1 JDBC ...................................................................................................................................................................................................... 429.6 Oracle Forms .............................................................................................................................................................................................. 4210 DBA Tasks Cross-Reference ..................................................................................................................................................... 4311 Oracle-to-Sybase Migration Cross-Reference ......................................................................................................................... 4711.1 Oracle-to-Sybase ASE migration: category "Simple Conversion" ................................................................................................... 4711.2 Oracle-to-Sybase ASE migration: category "Partial Rewrite" ........................................................................................................... 5611.3 Oracle-to-Sybase ASE migration: category "Major Rewrite" ........................................................................................................... 64Revision history:Rev.1.0: September 2011: initial versionRev.1.1: November 2011: expanded the topic on case-sensitivity; various other additionsRev.1.2: October 2012: many extensions to chapters 3 & 11; added example of sequence equivalent in ASERev.1.3: December 2012: replaced PowerDesigner and ECDA examples by pointers to a separate document© 2011-2012 Sybase, Inc.Sybase, Transact-SQL, Adaptive Server Enterprise and Replication Server are registered trademarks of Sybase, Inc.Other product or brand names may be (registered) trademarks of their respective owners.Introduction 3

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.31 INTRODUCTIONThis Migration Guide aims to provide guidance and assistance with the migration process from an Oracle database toSybase ASE (Adaptive Server Enterprise). By "migration" we mean the process of changing a client-server applicationcurrently using the Oracle database as its RDBMS, such that it uses the Sybase ASE database instead.This Migration Guide has as its primary focus to migrate functionality from Oracle to Sybase ASE. Performance-relatedaspects of Sybase ASE are not covered (also see section 2.4).1.1 Intended AudienceThis Migration Guide is intended for anyone involved in migrating an Oracle database to Sybase Adaptive ServerEnterprise (ASE).1.2 What You Should Already KnowThe reader is expected to be familiar with relational database concepts, and with Oracle in particular. In addition,introductory knowledge of the Sybase ASE RDBMS is required.For a database migration to be successful, there should be a detailed understanding of the current Oracle-based system,including its high- and low-level architecture, as well as the interaction between the client application and the Oracledatabase.1.3 About Sybase ASESybase ASE is the database that powers Wall Street. ASE has been delivering rock-solid reliability and top-levelperformance for the past 25 years. Sybase ASE has a lower total cost of ownership than Oracle, and delivers betterperformance on the same hardware. Sybase ASE is ready to be the database in any application that runs on Oracle today.1.4 Oracle systems targeted by this GuideThis Migration Guide can be used for migrations of any type of Oracle-based system. While it does not focus on aspecific type of application, workload or system design, the majority of Oracle-based migration candidate systems areexpected to be transactional systems.This Migration Guide specifically does not aim at migrating SAP Business Suite installations currently running onOracle, to run on Sybase ASE instead. Since such migrations are covered by product and service offerings by SAP,interested customers should contact SAP directly.1.5 Oracle products vs. Sybase productsBoth Oracle and Sybase provide a range of database-related products. The following list illustrates how the main highlevelOracle products compared to Sybase products. While this list is deliberately kept brief, it provides some basicguidance on how Oracle and Sybase can be aligned.The focus of this Migration Guide is on migration from Oracle Database Server to Sybase ASE. These are usuallyexpected to be OLTP-oriented systems, though this is not required.OracleOracle Database ServerOracle OLAP and DWOracle RACOracle Times TenOracle StreamsSybaseSybase ASE (Adaptive Server Enterprise)Sybase IQSybase ASE Cluster EditionSybase ASE In-Memory DatabaseSybase Replication ServerIntroduction 4

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.31.6 Oracle / Sybase database versions coveredThis document pertains to Oracle versions 9i, 10g and 11g.The migration target is assumed to be Sybase ASE version 15.7 (or later). Migration to earlier ASE versions is notrecommended and not covered by this Migration Guide.If not otherwise specified all references to "ASE" or "Adaptive Server" are considered references to "Sybase AdaptiveServer Enterprise".1.7 Sybase ASE documents and referencesFor more detailed information about Sybase ASE , see http://www.sybase.com/ase for general documents andwhitepapers.See http://www.sybase.com/support/techdocs/migration for resources specifically focused at (different types of)migrations. These include the document you are currently reading, as well as “Migrating an Oracle Database to SAP SybaseASE with PowerDesigner and ECDA (A Step-By-Step Practical Guide)” .For ASE documentation and product manuals, see http://infocenter.sybase.com . Specifically, the following ASEdocuments are relevant:Transact SQL User's GuideReference ManualSystem Administration GuideUtility GuidePerformance and Tuning GuideIn addition, Sybase provides technical training for ASE. For details on courses and availability, seehttp://www.sybase.com/education.Introduction 5

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.32 HOW TO USE THIS MIGRATION GUIDEThe focus of this Migration Guide is on the database-specific technical aspects of an Oracle to Sybase databasemigration project. In particular, it aims to help identify and assess the complexity of the migration when scoping out amigration project, so as to avoid overlooking or underestimating potentially difficult aspects of the system to bemigrated. In addition, it helps establish a migration approach by providing and suggesting technical options for variousaspects of the migration process.2.1 Migration process outlineThis Migration Guide recommends a phased approach towards migrating from Oracle to Sybase ASE. The followingphases can be identified, in order of importance and priority:1. Before starting the actual migration project, assess the complexity of the migration using the checklist inchapter 3. This activity involves identifying specific Oracle features used in the current system which may nothave a direct Sybase equivalent.It is strongly recommended to pay sufficient attention to this activity, as this helps to avoidoverlooking or underestimating the most difficult parts of a migration.2. Migrating the database schema is the necessary first step of an actual migration (described in chapter 4).This Migration Guide recommends using Sybase PowerDesigner to reverse-engineer the Oracle schema andconvert it to the Sybase ASE equivalent.3. Migrating server-level aspects such as users (described in chapter 5).4. Migrating the data itself (described in chapter 6). The approach chosen to perform the data migration is usuallydriven by the maximum tolerable downtime allowed for the application.It is recommended to consider using 3 rd -party tools for extracting data from Oracle. If minimal applicationdowntime is crucial, consider Sybase Replication Server to reduce this downtime to minutes rather than hours.5. Migrating Oracle PL/SQL code to Sybase Transact-SQL (also see chapter 7). This needs to be performed bothfor SQL located in the database (i.e. stored procedures, triggers, SQL functions) as well as for SQL code inclient applications. This step tends to be the most complex part of a migration.To assist with this migration step, chapter 11 contains cross-reference between Oracle features and their SybaseASE equivalent, in the three categories "Simple conversion possible", "Partial rewrite required" and "Majorrewrite required". This cross-reference is an extended version of the Oracle checklist in chapter 3.6. Migration of vendor-specific infrastructural components, such as JDBC drivers (see section 9.5).7. Convert the maintenance, administration and monitoring tasks. Since these aspects are highly specific for eachdatabase brand, "migration" would be a misnomer.Chapter 10 contains a cross-reference of some common DBA aspects. This is however not sufficient forperforming a migration, and specific DBA skills, both for Oracle and Sybase, will be required.8. The primary focus of this Migration Guide is to help achieve functional equivalence of the Oracle system afterbeing migrated to Sybase ASE.As a next step, Sybase ASE-specific optimization and tuning will likely be required in order to achieve desiredperformance levels. Sybase ASE-specific tuning is not covered by this Migration Guide; see section 2.4.2.2 Success factorsDatabase migrations can be complex, and costly migration failures need to be avoided. The following success factorsapply to any Oracle-to-Sybase database migration project:How to use this Migration Guide 6

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3Domain knowledge of the business application(s), system and environment. It is essential to have a full andcomplete understanding of all applications that access the Oracle database being migrated. This includes theclient applications that connect to the Oracle database directly, but also applications that indirectly access thedatabase, for example through an application server.For all these applications, it needs to be understood which data the application accesses in the database, andhow it modifies such data. Any SQL code submitted to the database by the application must be identified, aswell as how such SQL code can be changed.Availability of sufficient Oracle expertise to analyze all aspects of the database is an absolute requirement. Akey activity is to identify which specific Oracle features are used (as per the checklists in chapter 3), especiallythose which do not have a direct Sybase equivalent.Full access to all Oracle PL/SQL code being used, both in the database and in all client applications.As a minimum, sufficient understanding of Sybase ASE in order to create a functionally working migrateddatabase system. At a later stage in the migration project, more specialized Sybase expertise will likely beneeded for Sybase ASE-specific performance tuning and optimization. Having such expertise available at anearly stage may be helpful.A comprehensive testing process and production-like environment for validating the migration approach andthe affected software applications against the migrated Sybase database. For best results, it is highlyrecommended to use a copy of production data (as close as possible) as well as hardware which is similar in sizeto production.2.3 Not covered by this guide: Project aspectsThis Migration Guide does not prescribe or suggest how to organize a migration project in terms of preparation, settingup testing procedures, validating the migrated components, etc. These aspects of a migration project are left torequirements, standards, best practices and preferences of the organization undertaking the emigration effort.Please note that the absence of specific recommendations for testing and validation of migrated components does notmean that such activities should not be performed. On the contrary, these activities are essential, and it is recommendedto follow generally accepted best practices with respect to software testing and validation.2.4 Not covered by this guide: Sybase ASE-specific tuningThe primary purpose of this Migration Guide is to assist in creating a functionally equivalent Sybase ASE-based systemcompared with the original Oracle-based system. The purpose of this Migration Guide is not to provide guidance forarriving at an optimally tuned Sybase ASE system; while Sybase ASE-specific tuning will likely be necessary as part of amigration project, this Migration Guide deliberately makes no attempt to cover such tuning aspects.Since ASE-specific tuning is considered to be mostly unrelated to any Oracle-specific aspects or considerations, thereader is referred to the Sybase ASE documentation for background and recommendations about Sybase ASE tuning.,specifically the System Administration Guide and the Performance and Tuning manuals.How to use this Migration Guide 7

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.33 PRE-MIGRATION COMPLEXITY ASSESSMENTFor a database migration project, it is crucial to have an accurate assessment of the complexity of the migration ahead oftime. Here, "complexity" refers to how Oracle-specific features can be mapped to the feature set of Sybase ASE.Before starting the actual migration effort, the current Oracle system should be closely inspected and a list should bedrawn up of all types of Oracle-specific features being used, and how many times these occur.For each feature used, it should be determined in which of the following three categories it falls:Simple conversion possibleAn Oracle feature or statement can be mapped and converted directly to a (nearly) identical Sybase ASEfeature, requiring no syntax changes or only simple, local syntax changes only.Examples: most datatype mappings (Oracle VARCHAR2 Sybase VARCHAR); simple SELECT statementsPartial rewrite requiredAn Oracle feature or statement can be mapped to a partly equivalent Sybase ASE feature, requiring potentiallysignificant syntax changes and possibly partial rewriting of algorithms.Example: Oracle sequences Sybase ASE identity columnsMajor rewrite requiredAn Oracle feature or statement has no directly equivalent Sybase ASE feature, requiring rewriting orredesigning of algorithms or parts of applications.Example: Oracle Flashback; Oracle row-level triggers.Categorizing the Oracle features used by the system being migrated helps to identify the areas where most migrationcomplexity is likely to occur. Before deciding to start the migration project, there should be a clear view of the numberof occurrences of the features in the categories "Partial rewrite required" and "Major rewrite required" above, and of theeffort to migrate these, especially those in the Major rewrite required" category.To assist with this complexity assessment, below are three checklists, corresponding to the categories above, listing arange of Oracle features. Note that additional Oracle features may occur in your system that are not in these checklists;these should be taken into account just as well.The checklists below list the Oracle features only very briefly. Chapter 11 contains extended versions of these checklistswith the corresponding Sybase ASE equivalent for each Oracle feature.3.1 Oracle checklist: datatypesVerify the datatypes used in the current Oracle application; see section 4.7.Also see:section 4.7.1 for considerations that apply when migrating data rows whose length exceed an Oracle disk block;section 6.5 for considerations that apply when migrating particular datatypes.3.2 Oracle checklist: category "Simple Conversion"#cases foundOracle checklist: category "Simple Conversion"Connecting to an Oracle schemaThe Oracle SQL*Plus “slash” character sends preceding PL/SQL text to the Oracle server.Semicolon (as a statement delimiter in PL/SQL)Pre-migration complexity assessment 8

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3#cases foundOracle checklist: category "Simple Conversion"The Oracle DUAL tableSET SAVEPOINT savepoint-nameVariable/Parameter declarations; naming syntaxAssign default value in variable declarationMultiple variable declarations with a single DECLARE keywordDeclarations without DECLARE keyword in declaration section of stored procedures/functionsVariable assignmentTransferring table data into a variableConstants%TYPE denotes the datatype of a column in an existing tableDynamic SQL (Execute-immediate)Loops with LOOP/END LOOPFOR loopsCURSOR loopsOracle Outer join syntaxSET TRANSACTION READ WRITEALTER TABLE mytable TRUNCATE PARTITION partition_nameCREATE OR REPLACE PROCEDURE (or FUNCTION)ALTER PROCEDURE (or FUNCTION)CREATE PROCEDURE… IS…Stored procedure execution with named parameters (param => value)Stored procedure execution with positional parameters (:var)Stored procedure executionSQL Function declaration with DETERMINISTIC keywordExecution of a SQL FunctionDECLARE CURSOR cursor-name IS…Oracle cursorsPre-migration complexity assessment 9

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3#cases foundOracle checklist: category "Simple Conversion"Cursor Attribute %ISOPENCursor Attributes %FOUND, %NOTFOUNDCursor Attribute %ROWCOUNTAFTER triggers (on statement level)INSTEAD OF triggers (on views)SQL%ROWCOUNTBOOLEAN datatype (for PL/SQL variables only)MERGE statementPartitioned tables with composite partitioningPerformance-optimized native PL/SQL datatypes (for PL/SQL variables only)BINARY_INTEGERBINARY_DOUBLEBINARY_FLOATIF-THEN-ELSEMultiple statements in an IF-THEN-ELSE branchConditional test based on EXISTS subqueryString concatenation operator: ||userenv('sessionid')MOD(X,Y)CEIL()TRUNC(number)SUBSTR()SUBSTR() function with two parametersLENGTH()CHR()REPLACE()TO_CHAR(expression)TO_CHAR(expression, datepart)Pre-migration complexity assessment 10

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3#cases foundOracle checklist: category "Simple Conversion"TO_CHAR(expression, format-string)TO_NUMBER(expression)Date/time functions and calculationsSYSDATE, SYSTIMESTAMPTRUNC(date/time [,unit])LAST_DAY()NVL() functionInconsistent use of upper/lowercase for identifiers (Oracle is case-insenstive for identifiers)Identifiers that are Sybase ASE reserved words (see section 4.8)INSTR() function with two parametersDerived tables (also known as "inline views") without correlation nameALTER TABLE … SPLIT PARTITION…ALTER TABLE … MERGE PARTITIONS…Quoted identifiers. Oracle allows using quoted identifiers by enclosing an identifier in doublequotes.Oracle hintsPre-migration complexity assessment 11

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.33.3 Oracle checklist: category "Partial Rewrite"For the Oracle features listed below, migration to partly equivalent Sybase ASE features is possible, although potentiallysignificant syntax changes and possibly partial rewriting of algorithms may be required.#cases foundOracle checklist: category "Partial Rewrite"Database linksExternal tablesSequencesTable-valued User-defined SQL FunctionsPipelined Table FunctionsSynonymsComments on database objectsBitmap indexesTemporary tablesIS TABLE OF, AS VARRAY(n)OFNested tablesObject tables%ROWTYPEDefine a PL/SQL record type by enumerating the fields with IS RECORD OF or TYPE…ISRECORDNon-integer RETURN value in stored procedureUser-defined PackagesOverloaded stored proceduresPL/SQL Exception handling; defining exception handlersSQLCODE, SQLERRMRAISE_APPLICATION_ERRORColumn EncryptionLOB locatorsPre-migration complexity assessment 12

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3#cases foundOracle checklist: category "Partial Rewrite"Data compressionRetrieving data to the client in stored procedures usingDBMS_OUTPUT packageDBMS_*, UTL_* package calls (excl. DBMS_OUTPUT)SDO_* package callsSQL*Loader (sqlldr)Materialized ViewsGlobal variables (in a PL/SQL package)INTERSECT constructMINUS constructSpecific SQL clausesAS OFAS OF TIMESTAMPCONNECT BYDIMENSIONDIMENSION BYEXCLUDEGROUPING SETSINCLUDEMEASURESRETURN ALL ROWSRETURN UPDATED ROWSPARTITION BYREFERENCESYSTIMESTAMPCROSSCUBEFORKEEPMAINMODELNAVNOCYCLENOWAITONONLYRULESSAMPLESEEDSKIPIGNOREITERATENATURALNULLSNULLS FIRSTNULLS LASTROLLUPSIBLINGSSINGLEREFERENCELOCKEDSTART WITHUNIQUEUNPIVOTWAITINITCAP( string-expression )INSTR() function with three or four parametersNVL2() functionDECODE() functionPrimary key and foreign key with different datatypes, different precision/scale (for numericdatatypes) or different length (for character datatypes)Cluster (as created with CREATE CLUSTER)Pre-migration complexity assessment 13

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3#cases foundOracle checklist: category "Major Rewrite"Oracle FlashbackOracle Snapshot StandbyOracle SQL Plan ManagementAWR (Automatic Workload Repository)Oracle Advanced QueuingPackages for PL/SQL web accessOWA_CUSTOM, OWA_CX, OWA_OPT_LOCK, OWA_SEC, OWA_TEXT, OWA_UTILOracle FormsPre-migration complexity assessment 16

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3etc, and automatically convert the Oracle datatypes into their ASE equivalent, this is the fastest and most efficientschema migration method available.Section 4.2 describes how to use PowerDesigner for this purpose.Section 4.3 describes a possible approach to reverse-engineer the schema without PowerDesigner.4.2 Using Sybase PowerDesigner for database schema migrationSybase PowerDesigner is arguably the most advanced data modeling tool in the market. It is a stand-alone tool, runningon Windows. PowerDesigner supports over 30 database types, including Oracle and Sybase ASE.For more information on PowerDesigner, see http://www.sybase.com/powerdesigner .With PowerDesigner it is relatively straightforward to reverse-engineer most of the Oracle schema and convert it toSybase ASE. The central concept used by PowerDesigner is the PowerDesigner Physical Data Model (PDM). This is adatabase-independent model which can be converted to the SQL DDL dialect of each supported database.4.2.1 PowerDesigner schema conversion stepsFor detailed, step-by-step instructions on how to use PowerDesigner to convert the database schema from Oracle toSybase ASE, see the document “Migrating an Oracle Database to SAP Sybase ASE with PowerDesigner and ECDA (A Step-By-Step Practical Guide)” at http://www.sybase.com/support/techdocs/migration.Once the schema is reverse-engineered, run the completed DDL script in Sybase ASE and check for any errors.Note that some aspects of schema migration cannot be handled by PowerDesigner and will have to be handleddifferently. These aspects are described in section 4.4.4.3 Reverse-engineering the Oracle schema without Sybase PowerDesignerWithout using Sybase PowerDesigner, reverse-engineering the schema can be done in a number of ways:Use the Oracle SQL*Plus DESC command on all database objects, and process the output so that they arevalid DDL statements. This is likely to require significant manual script coding.Use the Oracle DBMS_METADATA package to extract DDL for the Oracle objects. This involves SQLstatements such as the following (for Oracle table 'MY_TABLE', in schema/user 'SALESAPP'). Note thatthese are only examples, this is not a complete list of all statement required to perform full reverse-engineering:SELECT DBMS_METADATA.GET_DDL('TABLE', 'MY_TABLE', 'SALESAPP') FROM DUAL;SELECT DBMS_METADATA.GET_DEPENDENT_DDL('INDEX', 'MY_TABLE', 'SALESAPP') FROMDUAL;SELECT DBMS_METADATA.GET_GRANTED_DDL('OBJECT_GRANT', 'SALESAPP') FROM DUAL;Use Oracle SQL Developer (a free Java-based tool, downloadable from oracle.com). This uses theDBMS_METADATA package (see previous bullet).Use TOAD (a low-cost tool, commonly used in many Oracle environments) to extract the object definitions,and then manually convert the Oracle datatypes into their ASE equivalent. This could be cumbersome whenlarge numbers of tables are involved.Once the Oracle schema has been reverse-engineered, the Oracle DDL needs to be converted to Sybase ASE syntax,including conversion from the Oracle datatypes to Sybase ASE datatypes. Section 4.7 describes the mapping fromOracle datatypes to Sybase ASE.In addition, some aspects of the Oracle schema require special attention; see section 4.4.4.4 Special cases in schema migrationThe following schema aspects require special attention:Database Schema Migration 18

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3Oracle allows more columns per table than Sybase ASE (the limit depends on the ASE server's page size andon the table's lock scheme). If the limit in Sybase ASE is exceeded, an error will be raised when trying to createthe table. If this occurs, either the ASE server's page size will need to be increased, or the table needs to besplit vertically into multiple tables and all queries referencing the table likely have to be modified accordinglyIf the length of a column exceeds the maximum allowed length in Sybase ASE (the limit depends on the ASEserver's pagesize and on the table's lock scheme), such columns will have to be split into multiple columns andplaced in additional tables. All queries referencing the column likely have to be modified accordingly.PowerDesigner converts the Oracle BFILE datatype to the Sybase ASE image datatype. Since BFILE is adatatype used to store a locator (link) to an external binary file stored outside of the database, this is notfunctionally equivalent so application changes may be required. If a different ASE datatype is required, forexample, to hold the name of an externally stored file, change it manually.PowerDesigner 15.x cannot automatically convert the Oracle timestamp datatype to bigdatetime inASE, so this needs to be done manually. PowerDesigner 16.0 (release expected in August 2011) does not havethis limitation and will perform the conversion automatically. PowerDesigner 15.x cannot reverse-engineer Oracle users or security details (permissions). PowerDesigner 16.0(release expected in August 2011) does not have this limitation and is capable of handling these aspects.Since the SQL reserved words are different between Oracle and Sybase ASE, before attempting a databaseschema migration, all Oracle objects need to be checked against the Sybase ASE reserved words. Any Oracleidentifiers that are also Sybase ASE reserved words, need to be changed first. For a complete list of reservedwords in Sybase ASE, see “Adaptive Server Enterprise->Reference Manual: Building Blocks->Reserved Words”.Also see section 4.8 for queries that can be used to search for the occurrence of keywords in the Oracledatabase.The mapping of Oracle user-defined datatypes to ASE can be difficult and may require extensive manualintervention. The key to user-defined datatype migration is to fully understand the underlying base datatype.Note that user-defined datatypes can be nested. For Oracle, user-defined datatypes is an add-on option to thedatabase and is not widely used.4.5 Mapping the Oracle schema to Sybase ASE databasesSybase ASE does not have an identical interpretation of the concept of "schema" as the "Oracle schema". Whenmigrating an Oracle schema to Sybase ASE, there are two basic options to map the Oracle schema to Sybase ASE.For the sake of example, let's assume there are two Oracle users john and bill who own an Oracle schema, and eachschema has a table named salesdetails.The options are:Perhaps the most straightforward way to migrate, is to map each Oracle schema to a separate ASE database,where each database is owned ('dbo') by the corresponding user. This would result in two ASE databasesnamed john_db and bill_db (different names may of course be chosen), owned by ASE logins john andbill respectively; each database has table named salesdetails, owned by the dbo database user (the fulltable name would be dbo.salesdetails).However, this results in as many ASE databases as there are users owning an Oracle schema, of which theremight be many. While an ASE server can hold up to 32786 databases, it is highly impractical from a DBAperspective to have more than 20-50 databases.Map all Oracle schemas to a single ASE database with a multi-tenancy model. This means that the ASEdatabase user (which is linked to the ASE server login, which is the equivalent of an Oracle user) is used withinthe database to identify each object's owner. This will result in a more manageable ASE system since there willbe less ASE databases.In this case, the example would result in a single ASE database, let's say sales_db, in which ASE logins johnDatabase Schema Migration 19

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3and bill have been added as database users. Under each user, a salesdetails table is created, which willhave the full name john.salesdetails and bill.salesdetails.Either option is possible; technically ASE does not favor one over the other, but the multi-tenancy model fits best withASE's methods for backup and restore.It should be noted that multi-tenancy models are sometimes incorrectly seen as security weaknesses since it would beeasier for user bill to access john's tables, since they are located in the same ASE database. This is however not justified:if standard best practices around ASE security are followed, then security can be fully guaranteed.One consideration around multi-tenancy databases is that a backup of a database contains the data from all users in thatdatabase. If this is undesirable, for example because each user wants to have a backup copy of his own database, thenthe first option above (separate ASE databases for each user) should be followed instead.Lastly, it may also be the case that there is only one Oracle schema. In that case, there is no need to qualify the ASEtables with the owner name since they will all be owned by the dbo user.4.6 Schema-related Oracle-Sybase terminologyFollowing is the high-level terminology mapping of Oracle concepts to Sybase concepts. This table is not intended to beused for direct migration purposes, but only as high-level terminology guidance.OracleDatabaseSchemaTablespaceSegmentUndo/rollback tablespaceOnline redo logsSybase ASEDatabase ServerDatabase and objects owned by the same user.Aspects of ASE database and/or database device and/orsegment(system/sysaux tablespaceASE master database;temporary tablespaceASE tempdb database;user-defined tablespacedatabase device and/or segment)A database object that has space allocated (table, index,materialized view)Transaction logTransaction logUser User, Login (see section 5.5)RoleTableTemporary tableRoleTableTemporary tableViewMaterialized ViewClusterIndexIndex-organized tableColumn-level check constraintViewNo direct equivalentNo direct equivalentNon-unique indexTable with clustered indexColumn-level check constraintDatabase Schema Migration 20

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3OracleColumn defaultUnique keyPrimary keyForeign keyConstraintsCollectionsPL/SQL ProcedurePL/SQL FunctionTriggersPackageSequencesSnapshotDatabase links, External tablesProcedureSynonymSybase ASEColumn defaultUnique key or identity property for a columnPrimary keyForeign keyConstraintsIn PL/SQL, a collection is an ordered group of elementsof the same type, such as VARRAYs or nested tables.Transact-SQL stored procedureT-SQL user-defined SQL function (SQL UDF)TriggersNo direct equivalentPartly covered by the identity property for a column ordedicated key value tableNo direct equivalentProxy Tables and Remote ServersStored procedureSimilar functionality with views for table and viewsynonyms. All other synonym references must be replacedwith fully qualified object strings (database.owner.object)or proxy tables (for synonyms to remote objects).4.7 Mapping Oracle Datatypes to Sybase ASEThe table below describes how Oracle datatypes can be mapped to Sybase ASE datatypes. In most cases the mapping ofdatatypes is straightforward.For the Oracle datatypes CHAR, VARCHAR2 and RAW, the ASE server page size determines whether or not themapping can take place; the technical background is that ASE requires a row, and therefore every column, to fit on anASE database page. By default, ASE uses a 2KB server page size, but 4KB, 8KB and 16KB are also possible.The maximum allowed column length for a column for each ASE server page size depends on various factors such aswhether the column is fixed- or variable length and the ASE table's lock scheme. To display full details, run thecommand dbcc serverlimits in ASE.Oracle Description Sybase ASE Comments / When to useNUMBER(x) Oracle NUMBER(x) datatypeswith 0 decimals can be convertedinto an equivalent Sybase ASEdatatypes.BIGINT length of NUMBER datatype > 10INTEGERSMALLINTlength of NUMBER datatype between6 and 10 and data values

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3Oracle Description Sybase ASE Comments / When to use32767NUMBER(x,y)FLOATCHAR(x)VARCHAR2(x)DATETIMESTAMP[WITH [LOCAL]TIME ZONE]alternatively to the mapping pathabove, these Sybase ASEdatatypes can be used.maximum FLOAT precision inOracle is approx. 38maximum CHAR size in Oracleis 2000 bytesmaximum VARCHAR2 size inOracle is 4000 bytes for columns(for PL/SQL variables, the max.size is 32767)date/ time precision in Oracle isup to one second.precision of Oracle‟sTIMESTAMP is 1/100000000thof a secondTINYINTlength of NUMBER datatype between2 and 3 and data values 15FLOAT precision of actual values

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3Oracle Description Sybase ASE Comments / When to useLONG RAW Oracle‟s max. storage capacity for IMAGELONG RAW is 2GBCHAR(1)BFILE4.7.1 Chained Oracle data rowsif this is a packed bit columnmaintained by a PL/SQLfunction set / unset / retrieve /query on them.BFILE stores a locator (link) to abinary file outside of the databaseBITno direct equivalentOracle allows long data rows to exceed the size of a disk block. This is known as 'chained rows'. It is possible that suchchained data rows, if they exist in the Oracle database, are too long to be stored in Sybase ASE, which requires that adata rows fits on a data page (which is 2KB, 4KB, 8KB or 16KB; use dbcc serverlimits to find the net max rowlength allowed in ASE). Also, for tables with more than 255 columns, the rows will always be chained.It is important to identify tables that have chained rows before starting the migration. To find how many chained rowsoccur in a table, run this Oracle query:SELECT owner, table_name, chain_cntFROM dba_tables WHERE chain_cnt > 0If chained rows are found, the Oracle command ANALYZE TABLE table-name LIST CHAINED ROWSINTO chained-row-table can be used to identify the actual chained rows.If chained rows are found, it may be needed to modify the data model to ensure that rows are short enough to fit on anASE page.4.8 Search for Sybase ASE reserved words and keywords in OracleBefore you can migrate an Oracle schema or Oracle stored procedure, function or trigger, there needs to be a check forreserved words (keywords) that are already identified as either problematic or non-migratable. Oracle allows SQLkeywords to be used as identifiers whereas this is not allowed in ASE. For example, the following is valid PL/SQL:CREATE TABLE case (begin VARCHAR2(100), when INT)The following query finds all object names within the Oracle database that are ASE keywords:select owner, object_name, object_typeFROM sys.dba_objectsWHERE object_name = UPPER('')The following query scans any PL/SQL object within the Oracle database for certain keywords and returns the nameand owner of the object as well as the object type for objects containing ASE keywords. This query retrieves the exactcode and line number of the occurrence within a stored procedure, function or trigger. Note that this could potentiallyreturn a lot of output since the 'line' column may be long. Also note that these keywords could be part of comments orstring constants, in which case they can be ignored:SELECT owner, name, type, line, textFROM sys.dba_sourceWHERE instr(UPPER(text), UPPER('')) > 0The queries above should be run for all Sybase ASE reserved words and keywords. The most practical way of runningthese queries for all ASE keywords is to insert the ASE keywords in an Oracle table, and then run the above queries as ajoin with this table.For a complete list of reserved words and keywords in Sybase ASE, see “Adaptive Server Enterprise->Reference Manual:Building Blocks->Reserved Words”. Reserved words can also be displayed with the following ASE query (but checkcompleteness against the ASE documentation!):Database Schema Migration 23

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3SELECT name FROM master..spt_values WHERE type = 'W'4.9 Choosing a lock scheme for Sybase ASE tablesASE offers a choice of three lock schemes for each database table: allpages, datapages or datarows.allpages is the oldest lock scheme, as well as the out-of-the-box ASE default. It is slightly more efficient for sometypes of operations. The datapages, and especially datarows, lock schemes provide fundamentally betterconcurrency characteristics. The concurrency benefits are likely to be relevant when migrating from Oracle to SybaseASE due to the difference in transaction handling (as described in chapter 8).It is recommended to configure datapages or datarows as the default lock scheme in Sybase ASE. datapages ismore efficient, but datarows provides better concurrency (datarows locking is also known as row-level locking).Changing between datarows and datapages for an existing table is instantaneous. In contrast, large tables with theallpages lock scheme may require long downtimes to if their lock schemes need to be changed to datarows ordatapages since this requires a full conversion of the table and all its indexes.4.10 The Oracle DUAL TableIn Oracle, a SELECT statement must always be executed against a table, even when retrieving system information, suchas the current date/time. For this purpose, Oracle created the DUAL table. Retrieving the system date via SQL lookslike this in Oracle:SELECT sysdate FROM DUALSybase ASE supports SELECT statements that do not have a FROM clause. The same query in Sybase ASE would looklike this:SELECT getdate()To avoid rewriting existing SELECTs that use the DUAL table, it is possible to create a table named DUAL in ASE,which must always contain one and only row:create table DUAL (dummy_col char(1) unique check (dummy_col='X'))insert DUAL values ('X')goIf Sybase ASE is created case-sensitive (see section 5.2), you may need to create additional tables named dual, Dual,etc, depending on how disciplined the Oracle developers were in using a consistent spelling for the DUAL table.Alternatively, consider editing the Oracle PL/SQL source code to use only "DUAL", or to remove all references toDUAL completely.Database Schema Migration 24

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.35 MIGRATING SERVER-LEVEL ASPECTSThe architecture of the database server, and the way it is configured and managed, are quite different between Oracleand Sybase ASE. This chapter lists some migration aspects that require attention, but without claim for completeness.The reader is urged to consult the Sybase documentation, specifically the "System Administration Guide", for full details.5.1 Character setWhen creating a new Sybase ASE server, the character set to be used by the ASE server must be chosen. It isrecommended to use the same character for ASE, as is being used for the Oracle database.While the character set in ASE can be changed at a later point in time, it is strongly recommended to avoid this, and topick the right character set before migrating any Oracle aspects to ASE.5.2 Database server case sensitivity ('sort order')A difference between Oracle and Sybase ASE is that Oracle is not case-sensitive, whereas Sybase ASE is case-sensitiveby default. ASE can be configured to be case-insensitive, by installing a case-insensitive 'sort order'.Moreover, there is also a difference in the scope of case-insensitivity between Oracle and ASE:In a case-insensitive ASE server, case-insensitivity applies to both identifiers and to data comparisons; SQLkeywords are always case-insensitive in ASE.In Oracle, case-insensitivity applies only to identifiers (table names, column names, etc), but, by default, not todata comparisons; it is likely that existing Oracle systems use this default. Note that the above applies only tounquoted identifiers; quoted identifiers are case-sensitive in Oracle, though these are not used often.As a result, the following two queries will retrieve different data in a case-insensitive Oracle system, but retrieve the samedata in a case-insensitive Sybase ASE:select * from Employees where Name = 'Johnson'select * from Employees where Name = 'JOHNSON'Also, existing Oracle SQL code refers to the table TEST in different ways - the following all refer to the same table.Inconsistent use of upper- and lower-case spelling for identifiers is not uncommon to occur in practical Oracle systems:select * from TESTselect * from Testselect * from testWhen using a case-insensitive sort order for Sybase ASE, such SQL statements do not need to be changed. When usingthe default case-sensitive ASE sort order, all references to a table must use the exact same upper/lowercase spelling, or"table not found" errors will result.Whether the ASE server should be case-sensitive or case-insensitive is a decision to be made. For ASE, there is nooverriding technical advantage to either option.In practice, the decision probably depends on whether query results may be affected by using a case-insensitive ASEserver. If this is the case, then the default case-sensitive ASE configuration should be used, and any Oracle SQLstatements referring to identifiers in mixed-case spelling (i.e. TEST and Test) should be changed to use one consistentspelling for the identifiers.Migrating server-level aspects 25

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.35.3 Server configuration parametersIn Oracle, the configuration parameters for the server and database are stored in the initialization file (init.ora) orserver parameter file (spfile). These parameters cover a diverse set of resources, such as memory, processes, network,disk, I/O, connections, files, character set, and so on.It is unlikely that Oracle configuration parameters can be mapped directly to corresponding configuration parameters forSybase ASE. It may however be useful to be aware of Oracle-specific configuration settings since in some cases somekind of Sybase ASE equivalent could be required.The non-default values of the Oracle parameters can be obtained using one of the following options:Convert the server parameter file (spfile) to an initialization parameter file as follows:CREATE pfile FROM spfileQuery the database by executing the following statement:SELECT name, value FROM sys.v$spparameterWHERE isspecified = 'TRUE'5.4 StorageMost Oracle installations enlist the help of Oracle‟s Automated Storage Manager (ASM). Sybase ASE does not have theequivalent of ASM. Storage must be managed through T-SQL commands, Sybase Control Center , or via Sybase Central(the Sybase database admin GUI tool).Generally speaking, Sybase ASE recommends the following high-level guidelines for storage:For user databases, use raw devices or filesystem devices with directio=true. Never use filesystem devices withdsync=false for user databases; filesystem devices with dsync=true can be used but carry a potentiallysignificant performance penaltyFor temporary databases, filesystem devices with dsync=false are generally recommended.For the underlying storage layer, RAID 0+1 or RAID 1+0 is recommended. Avoid RAID 5 for write-intensivepurposes such as the ASE transaction log, unless the storage solution provides a non-volatile write cache tobuffer the writes.To achieve maximum disk I/O bandwidth, read- and write-intensive data should preferably be spread over asmany physical spindles as possible.Many additional considerations with respect to storage configuration apply. Please refer to the Sybase ASE "SystemAdministration Guide" for details.5.5 Migrating the User LoginsThere are some differences in terminology between Oracle and Sybase ASE around the concept of a "user".In Oracle, on instance level: a user is used for authentication, and can also be a schema owner (and thus owndatabase objects, and have permissions on database objects)In Sybase ASE, on server level: a login is used for authentication, but does not own any objects or haveobject access permission.A special ASE login is sa - this is the 'super user' in Sybase ASE, comparable to the SYS account in Oracle.This user has access permissions on all database objects and should be restricted to the DBA. For securityreasons, applications should never use the sa login to connect to the ASE server.Migrating server-level aspects 26

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3In Sybase ASE, on database level: a user, which maps to a login, can own database objects and havepermissions on database objects.When migrating from Oracle to Sybase ASE, the most likely scenario is to migrate all Oracle application users to anidentically named Sybase ASE login. For each ASE login, a corresponding database user (typically with the same name asthe login) is then created to allow that login to access an ASE user database. A login can be given access to multiple ASEdatabases by creating a corresponding database user in each ASE database.Alternatively, the guest database user can be created in each ASE user database. However, related security implicationsshould be carefully assessed first.The resulting structure of ASE logins and database users depends on decisions about how an Oracle schema is migratedto ASE (see section 4.5).5.5.1 User passwordsEach Oracle user has a password. In ASE, a login has a password. If the Oracle user passwords are known, they can beset identically in ASE; otherwise, new passwords must be set for the ASE logins. ASE login passwords cannot be set toblanks.5.6 PermissionsIt is recommended to use PowerDesigner 16 to reverse-engineer the permissions for accessing (objects in) the Oracledatabase. If PowerDesigner 16 cannot be used, the permissions will likely have to be converted manually to the SybaseASE equivalent.Migrating server-level aspects 27

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.36 DATA MIGRATIONThis section describes the methods for migrating data from Oracle to Sybase ASE. It is assumed that the schema hasalready been migrated.The main complicating factor is that Oracle provides no tools to unload a table to a flat file in a format that can be readby non-Oracle tools.Data migration can be performed in a number of ways. Therefore, when choosing an approach, various factors need tobe considered, including:- the complexity of the chosen solution- the volume of data being migrated- the available system downtime to perform the data migration during cutover- the need to become familiar with new software or tools for the purpose of migrating the data- additional software license costsIn essence, the following options are available for data migration:Unload Oracle data into ASCII-formatted flat files, and load these files into ASE with the Sybase"bcp" utility.If Oracle data can be exported into an ASCII-formatted flat file, then ASE's high-speed loading tool "bcp" canload it into ASE. Since Oracle does not provide a way to achieve this, the user must either use a 3 rd -party toolfor this purpose, or create his own PL/SQL utility to essentially spool the data from the database into a flat file.Considerations: This option is often seen as attractive due to the transparency of the migration process: allsteps are clearly visible and can be individually developed and tested. Developing your own PL/SQL tool tounload Oracle data is simple, but will perform slowly, thus making it unsuitable for anything but relatively smalldata volumes. Using a 3 rd -party tool adds software license costs.Use Sybase's Enterprise Connect Data Access (ECDA) Option for Oracle.ECDA is a connectivity product by Sybase that enables direct connections from an ASE database into anOracle database, making it possible to transfer Oracle data directly into ASE. ECDA hooks into the ASEmechanism of "proxy tables".Considerations: This option can be used when the data volume is such that the data can be transferred in theavailable migration window. It is unlikely to be suitable for very large data volumes. An advantage is thatECDA takes care of mapping Oracle datatypes to ASE datatypes, and that the migration can be fullyperformed through SQL.Using this option requires purchasing Sybase's ECDA product.Use Sybase Replication Server Heterogeneous Edition (RSHE) for OracleSybase Replication Server captures database transactions in Oracle and applies these to ASE, thus keeping theASE database continuously up-to-date. In addition, Replication Server can also initially copy the full contentsof the Oracle tables into ASE, in order to initialize the data replication ("materialization of the replicationsystem").Considerations: Using transactional replication is the only data migration solution where activity on the Oracledatabase can continue while the data migration is in progress. This means that the migration downtime, duringwhich applications are not available because they must switch from the Oracle database to the ASE database, isindependent of the data volume being migrated; this downtime could potentially be very short (e.g. minutesrather than hours).Using this option requires purchasing Sybase's Replication Server product, as well as learning how to useReplication Server.Letting Replication Server perform the initial data copy from Oracle to ASE may not be realistic for large datavolumes. In this case, the initial materialization of the replication system might be better performed with one ofthe other options mentioned here.Use a 3 rd -party ETL tool that supports both Oracle and Sybase ASE.Data Migration 28

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3Considerations: This option is most attractive if the ETL tool is already in use so that no additional softwareneeds to be purchased for the migration alone.an be used when the data volume is such that the data can be transferred in the available migration window. Itcan be used for very large data volumes, but a sizeable migration window may be required.6.1 Unload Oracle data into ASCII files; load into ASE with "bcp" utilityASE's high-speed data loading utility "bcp" is capable of loading almost any type of appropriately formatted ASCII datafile into ASE. However, since Oracle does not provide any tools to export Oracle data into an ASCII-formatted file, theuser must either use a 3rd-party tool for this purpose, or create his own PL/SQL utility to essentially spool the data fromthe database into a flat file. FACT is an example of such a 3-rd party tool.6.1.1 Loading into ASE with "bcp"This is an example of loading data from an ASCII file into an ASE table (named mydb..mytable) with bcp:bcp mydb..mytable in mytable.txt –Ulogin –Ppassword –Sserver –cIn practical situations, bcp should also specify which row- and column delimiters are used (bcp -r and -t options) sincethe defaults (CR and tab) could also occur in the actual data file (which is ASCII, after all). When unloading data into flatASCII files, proper delimiters should be chosen.Bcp-in performance is best when all indexes on the tables being loaded, are dropped first. Of course, , depending on thesize and number of indexes and the width of the base tables, recreating them afterwards could take a long time on largetables, so this may not be realistic for all cases.It is usually best to use a large network packet size with bcp (the –A option; also requires configuring the network packetsize on the ASE server).For large tables, it may be advisable to use the bcp –b option to break the load into multiple database transactions. Thisis typically combined with enabling the "trunc log on checkpt" database option in ASE to avoid the transaction logfilling up.To load only part of a data file, or to load columns in a different order than in the file, a so-called "bcp format file" maybe used. For more information on format files, as well as on bcp in general, see the Utility Guide in the ASEdocumentation set (http://tinyurl.com/6883kx4).It is highly recommended to perform multiple bcp operations in parallel (one for each table being loaded). The optimalnumber of concurrent bcp operations will be determined by the hardware capabilities. If there is only one (or few) largetables that need to be loaded, these can still be loaded using in multiple BCP operations by adding partitioning the tableusing round robin partitioning and specifying the start and last rows of the data file being loaded into a particularpartition number of the table.Lastly, note that, on Unix/Linux, bcp can read from a "named pipe" (created with the "mkfifo" command). If the utilitythat extracts the data into a file can write to a named pipe as well, then a lot of time can potentially be saved as follows:1. Create a named pipe with the Unix/Linux "mkfifo" command2. Extract the data from Oracle, writing it to the named pipe.3. Without waiting for the data extraction to complete, start bcp to load the data from the same named pipe. Bcpwill read data from the named pipe once it is delivered by the extraction utility, and immediately insert it intoASE.Instead of first extracting the data and then loading it, the time to transfer the data is now reduced to the longer of(extracting the data, loading the data). This can represent significant time gain.For more information on bcp and named pipes, please refer to http://tinyurl.com/5urcfrt .6.1.2 Unloading from Oracle: FACT (3rd-party tool)FACT ("Fast Extract") is a 3 rd -party high speed Oracle data export tool that allows ASCII flat file creation, also inparallel mode. These files can be used as input for the Sybase ASE utility bcp.Data Migration 29

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3For more information about FACT, see http://www.iri.com/products/FACT.6.1.3 Unloading from Oracle: Roll-your-own PL/SQL utility to export Oracle dataIf you want to unload data from Oracle tables into ASCII flat files using only Oracle features, you must create your ownPL/SQL utility that essentially spools the data from the database into a flat file. This uses the DBMS_OUTPUT.put_linecommand in PL/SQL. Here's an example of exporting two columns of table emp using "~" as a column delimiter andCR as a row delimiter. The output from this PL/SQL code should be captured in a flat file:DECLARE CURSOR emp_cur IS SELECT ename, sal FROM emp;BEGINFOR emp_rec IN emp_curLOOPDBMS_OUTPUT.PUT_LINE (emp_rec.ename || '~' || TO_CHAR (emp_rec.sal) );END LOOP;END;/The downside is that this method is likely to be very slow, making it unsuitable for anything but relatively small datavolumes. In addition, care must be taken to correctly format/convert each column datatype management.6.1.4 Unloading from Oracle: use Oracle SQL DeveloperOracle SQL Developer is a free Java-based tool, downloadable from oracle.com. This can be used to create a logicalexport of the data, whereby a SQL INSERT statement is created for every row.The downside is that this method is likely to be relatively slow in exporting as well as importing the extracted data, sincethis is all done on a single-row basis. This may make it unsuitable for large data volumes.6.2 Use Sybase's Enterprise Connect Data Access (ECDA) Option for OracleECDA is a connectivity product by Sybase that acts as a gateway between Oracle and Sybase ASE. With ECDA, directconnections can be made from an ASE database into an Oracle database, making it possible to transfer Oracle datadirectly into ASE using only SQL.The ECDA functionality is exposed as an ASE "proxy table", which maps to the actual Oracle table. By selecting fromthe proxy table, data is retrieved from the Oracle table and can be inserted directly into an ASE table. Also, it is possibleto do things like joining Oracle tables (though their proxy table) with tables in Sybase ASE.The main advantage of using ECDA is that takes care automatically of the datatype conversions from Oracle to SybaseASE when the data is retrieved. It also offers the flexibility and control of using the SQL language to access to proxytables.ECDA involves starting a separate process outside the ASE server.6.2.1 ECDA ExampleFor examples of how to use ECDA in an Oracle migration context, see the document “Migrating an Oracle Database toSAP Sybase ASE with PowerDesigner and ECDA (A Step-By-Step Practical Guide)” athttp://www.sybase.com/support/techdocs/migration.6.3 Use Sybase Replication Server Heterogeneous Edition (RSHE) for OracleSybase Replication Server is often used by Sybase customers to facilitate migrations between databases. The mainattraction is that the required downtime for curring over from the "old" to the "new" database can in principle be veryshort as far as the database side of things is concerned.6.3.1 Minimal migration downtime with ReplicationReplication Server captures database transactions in Oracle by reading the Oracle redo logs, and then applies thesetransactions to ASE, thus keeping the ASE database continuously up-to-date. In addition, Replication Server can alsoData Migration 30

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3initially copy the full contents of the Oracle tables into ASE, in order to initialize the data replication ("materialization ofthe replication system"). When large tables are involved, a main decision to be made is whether this initial materializationneeds to be performed through Replication Server or through an external unload-and-load mechanism.When using Replication Server for data migration, the objective is to reach a state where the ASE database is completelyin synch with the Oracle database, at which point the applications can switch from the Oracle database to the ASEdatabase (after the cutover, the replication setup can be removed). The system downtime needs to be only as long as thisapplication cutover takes, which would typically rather be minutes rather than hours.It is essential to observe that replication is application-transparent: applications can keep working normally on the Oracledatabase until the moment of cutover comes (obviously, the applications themselves likely require modifications to runon an ASE database instead of Oracle, but that is outside the scope of this topic of data migration).Other data migration solutions than transactional replication will require significantly more downtime. This is becauseReplication Server provides a mechanism to incrementally upload data changes from Oracle to ASE allowingapplications continue to work normally. In contrast, most other migration methods essentially take a copy of an entiretable which usually requires applications to be shut down or in read-only mode since it can be very difficult to reconcileany data changes to the copied afterwards. For those other migration methods, the required system downtime istherefore roughly identical to the time required to copy the data out of Oracle and into Sybase.6.3.2 Initial materialization for the replication setupReplication Server can automatically copy the full contents of the Oracle tables into ASE, in order to initialize the datareplication ("materialization of the replication system"). However, for very large tables, this may take unacceptably long.An alternative approach may therefore be to take an initial copy from these large tables through other means, like one ofthe other options described in this section on data migration (for example, unload into an ASCII flat file and load intoASE with bcp). With Replication Server, changes made to the table afterwards will be synch'd afterwards. The high-levelapproach would be as follows:1. Set up table replication for all Oracle tables to ASE tables, but do not auto-materialize the large tables.Optionally, enable "autocorrection" for the large tables (depending on your understanding of the type of datachanges that may be made; see the Replication Server documentation for details).2. Suspend the DSI connection by Replication Server to the ASE database. Any future changes to the Oracletables will be picked up by Replication Server and are accumulated in Replication Server's "stable queues". At alater point, these changes will be applied to ASE.3. For the large tables, take a copy and load this into ASE (using your preferred method).4. Once the loading of the large tables into ASE is complete, resume the connection from Replication Server tothe ASE database. This will push out the changes that were accumulated in Replication Server's "stablequeues", and apply these to the ASE tables.5. Once all accumulated changes are pushed out to ASE, the ASE database should be in the same state as theOracle database and the applications can switch over to complete the migration.When the tables are not too large to perform automatic materialization, or when it is acceptable that such materializationtakes a long time (since the Oracle applications keep functioning normally anyway), then the above steps can be replacedby simple setting up table replication from Oracle to ASE using automatic materialization.6.3.3 Other considerationsUsing this option requires purchasing Sybase's Replication Server Heterogeneous Edition (RSHE) for Oracle, as well aslearning how to use Replication Server. Letting Replication Server perform the initial data copy from Oracle to ASEmay not be realistic for large data volumes. In this case, the initial materialization of the replication system might bebetter performed with one of the other options mentioned here.Before using Sybase Replication Server to replicate out of an Oracle database, verify whether this complies with theavailable Oracle licenses. If a full Oracle license is used, there should be no restrictions; if a more restricted OracleData Migration 31

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3license is used (like a run-time only license), this might legally prohibit use of Replication Server and additional Oraclelicensing might be needed. This is a matter outside the scope of Sybase, and should be addressed with Oracle.Oracle GoldenGate can also provide transactional replication between Oracle and Sybase ASE. If the customer alreadyhas this product available, in principle this can also be used as part of a migration, in similar ways as described above forSybase Replication Server.6.4 Use a 3rd-party ETL tool that supports both Oracle and Sybase ASEIf an ETL tool is already in use which supports both Oracle and Sybase, it may be attractive to use it to perform the datamigration. Typically this would require system downtime for the duration of transferring the data from Oracle to Sybase,unless the ETL tool is capable of sorting out any changes to the data that are made during the transfer process.Please make sure that you adhere to any license restrictions and clear the use of this tool to move data from Oracle toSybase ASE with this vendor.6.5 Oracle datatypes requiring special attention for migrationThe following Oracle datatypes require special attention when migrating the data. Oracle TIMESTAMP Sybase BIGDATETIMEOracle‟s TIMESTAMP datatype has a granularity of 1/100000000 th of a second. This exceeds the precision ofSybase‟s BIGDATETIME datatype which has a granularity of 1 microsecond. When migrating data with bcp,TIMESTAMP data may need to be edited to remove the last 3 digits to avoid bcp throwing an error. Oracle BLOB/CLOB/NCLOB Sybase IMAGE/TEXT /UNITEXTOracle stores large binary objects in the BLOB datatype and large character objects in the CLOB datatype. Bothdatatypes can store up to 128TB (4GB * database block size) of data, as of Oracle 11g. When migrating, data fromOracle‟s BLOB datatype should be mapped to Sybase IMAGE datatype and CLOB to the TEXT datatype. Themaximum size for an individual column value of the IMAGE or TEXT datatype in Sybase ASE is 2GB. If theactual Oracle data values are larger than this maximum, ASE is unable to store these values. In this case, Sybase IQmight be a solution since it supports a maximum varying between 512TB to 2PB per column value. Oracle BFILEThe Oracle BFILE datatype is used to store a locator (link) to an external binary file stored outside of the database.Sybase ASE has no direct functional equivalent, so application changes may be required.Data Migration 32

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.37 MIGRATING PL/SQL TO TRANSACT-SQLPL/SQL is Oracle's implementation of the SQL language. Transact-SQL (T-SQL) is Sybase ASE's SQL dialect.Both SQL versions are mostly ANSI-92 entry-level compliant, but both vendors have implemented extensive non-ANSI-compliant vendor-specific enhancements and extensions.In many cases both dialects will still have equivalent functionality in their vendor-specific extensions, but syntax changesor varying amounts of code changes may be required when migrating from PL/SQL to T-SQL. In cases where T-SQLdoes not have a direct equivalent of a particular PL/SQL construct, larger amounts of code rewrite or even applicationrewrite could be required.While the incompatibilities between Oracle and Sybase are quite limited when it comes to schema migration and datamigration, there is much more potential for migration complexity between the two SQL dialect. Consequently, migratingPL/SQL to T-SQL is probably the most involved part of any Oracle to Sybase migration, and will typically requiremanual conversion/migration activity.A key factor for a successful migration –or, for that matter, for avoiding a failed migration- is a realistic assessment ofthe SQL-related complexities to be migrated before starting the migration project. Chapter 3 provides checklists for thispurpose.To assist with the actual migration of PL/SQL to T-SQL, chapter 11 contains a cross-reference between Oracle featuresand their Sybase ASE equivalents, in three categories of complexity. This cross-reference is an extended version of theOracle checklist in chapter 3 but provides more detail and provides specific suggestions on how to migrate a specificOracle feature to ASE.7.1 Locations of PL/SQL codePL/SQL code can be found in the following locations:Stored procedures (in the database server)Triggers (in the database server)SQL functions (in the database server)SQL queries (submitted to the database server by client applications, for example as anonymous PL/SQLblocks)PL/SQL objects in the database server can be reverse-engineered, or, if present and up-to-date, repository scripts thatwere used to create these PL/SQL objects can be taken as a starting point.PL/SQL code located in client applications needs to be identified in a different way, for example source code inspectionWhen it comes to using existing scripts or reverse-engineering the PL/SQL objects from the database server, the sameconsiderations apply as with respect to the database schema; see the pros and cons discussed in section 4.1.Sybase PowerDesigner may also be used to reverse-engineer PL/SQL objects (see section 4.2); however PowerDesignerdoes not perform any conversion to T-SQL (for this, evaluate tools as in section 7.2 below).Since the majority of PL/SQL is typically located in stored procedures and triggers, "migrating PL/SQL" is oftenequated to "migrating stored procedures and triggers". While that definition is not formally correct (there are otherplaces where PL/SQL occurs, as shown above), it does reflect the area where most migration issues are typicallyencountered.7.2 3 rd -party tools for PL/SQL migration to T-SQLTools for migrating from PL/SQL to T-SQL would be a welcome help when undertaking Oracle to ASE migrations.However, it is unlikely that any automated tool will be capable of perfectly migrating all of the PL/SQL code in any reallifeOracle system to ASE's T-SQL. Yet, it may well be possible that a substantial percentage can be handled by a tool,but a certain amount of manual conversion/migration should be expected.Migrating PL/SQL to Transact-SQL 33

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3SwisSQL and SQLWays (both 3 rd -part tools) are among the few tools that provide assistance with automatic migrationof Oracle PL/SQL code to Sybase T-SQL. For more information, see www.swissql.com (SwisSQL) andwww.ispirer.com (SQLWays).It should be noted that for both tools, support for ASE features in general, and new features in ASE 15.0 and later inparticular, appears to be limited. It is recommended to carefully evaluate these tools before using them for PL/SQLmigration.Please note that the above neither constitutes an endorsement by SAP/Sybase of either SwisSQL or SQLWays, nor astatement about the suitability of these tools for any specific project or purpose.Migrating PL/SQL to Transact-SQL 34

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.38 TRANSACTIONS AND LOCKING, ORACLE VS. SYBASEThe topic of transaction handling, transaction isolation and locking is probably where the most profound differencesbetween Oracle and Sybase ASE occur. For this reason a separate chapter is dedicated to this topic.8.1 Oracle MVCC vs. Sybase lockingThe purpose of transactions in the database is to take the database from one consistent state to the next. Databasetransactions, both in Oracle and Sybase ASE, guarantee all of the ANSI-defined ACID characteristics. ACID is anacronym for:Atomic: Either all of the modifications in the transaction are applied or none is applied.Consistent: A transaction takes the database from one consistent state to the next, observing referentialintegrity constraints.Isolated: The effects of a user's transaction are not visible to other users until the transaction is committed.Durable: Once the transaction is successfully committed, it is permanent.Oracle's implementation of the "Isolation" aspect of transactions is different from Sybase ASE's. Oracle uses MVCC(multi-version concurrency control) where an open transaction creates a new version of the data it is modifying, suchthat other sessions reading the same data will read the unmodified version, and thus are not blocked ("writers don‟tblock readers and readers don't block writers"). In contrast, Sybase ASE maintains only a single version of the data, anduses blocking locks to implement transaction isolation.Oracle also uses locking in addition to MVCC, but Oracle's locking concept is rather different from ASE's.8.2 Transaction-related migration issuesThe different approaches towards transaction isolation by Oracle and Sybase ASE may bring up the following issueswhen migrating from Oracle to ASE:Oracle applications and queries may rely, knowingly or unknowingly, on Oracle MVCC's "writers don't blockreaders and readers don't block writers" behavior. When migrating such queries unchanged to Sybase ASE,concurrency problems (blocking) may result. In addition, since MVCC has the effect that the result of anOracle query is essentially defined at the moment then the query starts, different results could potentially bereturned.Long-running transactions: these are fine, and indeed common, in Oracle where MVCC allows transactions toremain open for longer times with fewer adverse effects (though naturally, this also has its limits; for examplewriters still block writers). With Sybase ASE designed specifically for high-performance OLTP, transactionsshould be kept as short as possible in ASE for best concurrency and performance. Long transactions in ASEcan quickly lead to issues around concurrency (blocking) and resource consumption which also affectsunrelated transactions by other users (transaction log full).Oracle uses implicit transactions (also called "chained transactions"). This means a transaction is startedautomatically whenever a SELECT, INSERT, UPDATE or DELETE statement is executed. By default SybaseASE uses explicit transactions ("unchained"), though it also supports the ANSI-compliant implicit/chainedmode as well. When migrating to ASE, it may be needed to run some transactions in chained mode whichcould involve making changes to the way some transactions are handled, notably changing the transactionmode at session or client level, or by adding explicit BEGIN TRANSACTION statements (which Oracle doesnot support nor require).Transactions and Locking, Oracle vs. Sybase 35

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3For a successful migration to Sybase ASE, it is crucial to have a thorough understanding of the behavior of the Oracleapplication on the above aspects, and of the assumptions behind the design of queries and transaction handling in theOracle application.8.3 Using ASE implicit/chained transaction modeThe most straightforward migration option with respect to Oracle's implicit/chained transaction mode is to retain thetransactional structure of the Oracle application, and operate Sybase ASE in chained transaction mode.In Sybase ASE, implicit/chained transaction mode can be achieved by:Running the T-SQL command SET CHAINED ON before starting a transaction. This statement can also beexecuted in an ASE login trigger.Setting the OpenClient connection attribute CS_OPT_CHAINXACTS to true (default=false) in the clientapplication before connecting to the ASE server (With the isql utility, this attribute is set by specifying the -Ycommand-line flag).Since some operations in Sybase ASE may not work in chained mode, for example administration procedures such assp_configure, always enabling chained mode for all connections may not be practical (although ASE 15.7 allowsvarious system sp_* procedures to run in chained mode). It is recommended to only enable chained mode for thoseconnections or stored procedures that really require it. For connections by the DBA (typically, the 'sa' user), thedefault unchained mode should always be used instead.8.3.1 Transactional DDLWhen running Sybase ASE in chained mode, it is possible that, with a straightforward migration from Oracle, DDLstatements are executed inside a transaction. By default, this will cause an error in Sybase ASE. To allow DDLstatements in a transaction in ASE, run: sp_dboption database_name,'ddl in tran', true . Note that this is notpossible for some types of DDL.In addition, Oracle issues an implicit COMMIT after each DDL statement. In ASE, an explicit COMMIT statementshould be inserted after each DDL statement that runs in a transaction to avoid concurrency issues. Alternatively,chained mode should temporarily be turned off at session level when DDL is executed.8.3.2 Transaction processing in stored proceduresIf transaction processing is performed inside stored procedures, and the transaction mode (chained/unchained) matters,Sybase ASE optionally allows enforcing that a stored procedure is executed only in chained or unchained mode (oreither mode). This can be achieved with sp_procxmode:sp_procxmode proc_name, { 'chained' |'unchained' | 'anymode' }8.4 Using ASE explicit/unchained transaction modeIf it appears that running ASE in implicit/chained transaction mode leads to too many concurrency issues, considerusing the default ASE explicit/unchained mode instead for all transaction or only for selected transactions.When using unchained transaction mode, a BEGIN TRAN[SACTION] statement needs to be added to all transactionsthat will run in unchained mode (this statement is not required in chained mode where transactions start implicitly). Todetermine the best location to add BEGIN TRANSACTION requires detailed understanding of the transaction inquestion. In general it is recommended to keep transaction in ASE as short as possible.8.5 Using ASE transactional concurrency enhancementsOracle's MVCC feature tends to be seen, especially by Oracle itself, as a vastly superior and irreplaceable transactionhandling model, compared with other database brands.Transactions and Locking, Oracle vs. Sybase 36

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3In reality, much of the concurrency benefits of MVCC can be achieved in Sybase ASE by using ASE-specific features.What is true is that concurrency issues caused by sub-optimal transaction/query design will be less immediately visible inOracle than in ASE; consequently, discipline in transaction programming is more important in Sybase ASE than inOracle since sloppy transaction handling backfires quicker in Sybase ASE than in Oracle.When migrating from Oracle, it is recommended to consider the use of the following ASE features:Choose the datapages or datarows lock scheme for database tables. These lock schemes provide betterconcurrency than the default of allpages which is likely to be relevant when migrating from Oracle to ASE (alsosee section 4.9). When using datarows locking, uncommitted inserts do not block readers; in addition, "pseudocolumn-levellocking" behavior will automatically apply in certain scenarios (see the ASE Performance and Tuningmanual, volume "Locking and Concurrency Control" for details).Consider using the readpast feature in queries. When reading data, this lets the query skip over locks that wouldotherwise have blocked the read operation. For example:select * from mytable readpast where mykey = 123When using readpast, the data page (with datapages lock scheme) or data row (with datarows) being lockedand skipped over, will not be read. In many cases however, this may be acceptable because the nature or timing ofthe query is such that the data being looked for is known not to be accessed by other users anyway. Or the skippeddata is known not to have any impact on the query result anyway.Consider using the ANSI transaction isolation level 0 (ANSI READ UNCOMMITTED) in SELECT queries. Whilereading, this lets the SELECT query read data that is currently locked, and potentially being updated, by anotheruser's transaction. On the default ANSI transaction isolation level 1 (READ COMMITTED), the SELECT querywould be blocked instead.When using ANSI isolation level 0, it is important to be aware of the implications and potential downsides, such asrequirements for unique indexing, the risk of isolation level 0 select queries being aborted in certain scenarios (seethe see the ASE Performance & Tuning manual, volume "Locking and Concurrency Control" for details).Also, since isolation level 0 does not provide true transaction isolation, there is the risk of reading data that iscurrently being updated and which may be updated again, or rolled back, after being read. However, this may beacceptable because the uncommitted data being read is known not to have any impact on the query result anyway.When using transaction isolation level 0, it is strongly recommended not to set this as the default isolation level for asession, but to add the clause AT ISOLATION READ UNCOMMITTED or AT ISOLATION 0 only to those SELECTstatements where isolation level 0 is required.8.6 Other transactional aspectsSavepoints: Sybase ASE supports savepoints in the same way as Oracle though with slightly different syntax.By default, Oracle operates on transaction isolation level 1 (READ COMMITTED), which is the same as SybaseASE. Oracle also supports transaction level 3 (SERIALIZABLE). Sybase ASE supports both isolation levels as well.(Note that Oracle does not support isolation levels 0 and 2).SQL*Plus commit behavior:o Oracle's SQL*Plus always commits when exiting normally. Sybase's isql client does not commit when itexits, and consequently the effect would be that any open transaction is rolled back – which is the oppositeof Oracle's SQL*Plus behavior.o Oracle's SQL*Plus can be configured to autocommit after every statement with SET AUTOCOMMIT ON;by default, this is disabled.Sybase's isql client does not support autocommit; to achieve the same effect, explicit COMMITstatements should be inserted.Transactions and Locking, Oracle vs. Sybase 37

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3Oracle supports the syntax SET TRANSACTION READ ONLY, which makes the data read during the transactiontransactional data read-only, thus achieving the almost the same effect as transaction isolation level 3(SERIALIZABLE).In Sybase ASE, this should be changed to using transaction isolation level 3 (SERIALIZABLE). This can be achievedwith either of the following syntax:o SET TRANSACTION ISOLATION LEVEL 3o SELECT … AT ISOLATION LEVEL 3Instead of ISOLATION LEVEL 3, ISOLATION LEVEL SERIALIZABLE can also be used.Oracle also supports the syntax SET TRANSACTION READ WRITE; this can be removed when migrating to SybaseASE since it is the default transactional behavior.Deadlocks: Oracle sometimes pictures other database brands that do not support MVCC, as a source of 'deadlocks',perhaps aiming to use this somewhat scary-sounding terminology as an argument against their competitors.Indeed, deadlocks are rare in an Oracle environment, although it should be noted (consult any computer sciencetextbook on concurrent computing) that the possibility of deadlocks can never be excluded in a multi-userenvironment – which includes Oracle databases.When following some elementary best practices, deadlocks typically do not occur at all, or very rarely at worst, inSybase ASE. The main guideline to avoid deadlocks is that when different transactions each access multiple tables,they should always do so in the same order. In addition, using the ASE datarows lock scheme will help to reducethe chance of deadlocks occurring. Finally, in the rare occasion that deadlocks do occur, it is recommended toimplement deadlock retry logic into the application where possible.In summary, deadlocks need not be a major point of concern when migrating from Oracle to Sybase ASE.Transactions and Locking, Oracle vs. Sybase 38

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.39 MISCELLANEOUS MIGRATION ASPECTS9.1 CursorsA main difference between Oracle and Sybase ASE is on how the systems handle query results. In Sybase ASE, resultsets are handles using „set processing‟, meaning that in a stored procedure result sets are typically stored in temporarytables and then further refined, whereas Oracle is based on cursor processing navigating through result sets. Theunderlying reason is that Oracle maintains the versioning of its transactions and guarantees data integrity throughcursors. By using insensitive cursors in Sybase ASE, the same effect for the cursor result set is closest Oracle‟s cursorimplementation.Both Oracle and Sybase ASE support cursors, with some –mostly small- differences in syntax and semantics.Oracle PL/SQL is implemented with an implicit cursor deallocation process. When you close an Oracle cursor, it getsautomatically deallocated. Sybase ASE requires an explicit deallocate cursor statement to do so."REF CURSOR" is an Oracle datatype. Parameters and variables can be created with this datatype (called "cursorvariables"). A cursor variable acts as a pointer to a result set, and can be associated with different queries at run-time andpassed around between stored procedures, functions etc. Thus a cursor variable can be opened in one stored procedure,and the results fetched in another stored procedure, whereby the cursor variable is passed between both procedures.Since ASE does not have the REF CURSOR concept, PL/SQL using REF CURSOR needs to be rewritten, for exampleby rewriting all stored procedures involved, or by putting query results in (temporary) tables and let the different storedprocedures access these.9.2 SequencesSybase ASE does not have a full equivalent of Oracle Sequences, but in most cases similar functionality can be achievedby using either an ASE identity column or a key counter table.A main criterium is whether the sequence values must be transactional (i.e. the sequence-generated value is rolled backwhen the enclosing transaction rolls back). If such transactionality is required, a key counter table must be used.If this is not required, then an identity column can be used.Oracle code:CREATE SEQUENCE test_seqMINVALUE 1STARTWITH 1INCREMENTED by 1CACHE 20;INSERT INTO m_table VALUES (test_seq.nextval,…);Equivalent Sybase ASE code with identity column:-- this example uses an int as the sequence counter. Use numeric or bigint as needed.CREATE PROCEDURE init_seq_nr (@seqtab varchar(30), @startwith int=1, @cache int=100)ASBEGINset nocount onDECLARE @s varchar(100), @v intif object_id('seqtab') is not nullbeginset @s = 'drop table seqtab'exec (@s)endset @s = 'create table ' + @seqtab + '(seq int identity) with identity_gap = ' +convert(varchar, @cache)Miscellaneous migration aspects 39

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3EXEC (@s)if @startwith > 1beginselect @v = convert(int, reserve_identity (@seqtab, @startwith - 1))endendgo-- you can use either the output parameter or the return value,-- though the return value can only be an 'int' datatype-- NB: the values generated here are not transactional (they cannot be rolled back)CREATE PROCEDURE get_seq_nr (@seqtab varchar(30), @incremented_by int, @v_out int output)ASBEGINset nocount onDECLARE @s varchar(100), @v intset @v = convert(int, reserve_identity (@seqtab, @incremented_by))set @v_out = @vreturn @vendgo-- Initialize the sequence tableEXEC init_seq_nr 'myseqtab', 1, 20go-- Now get the next sequence number-- you can use either the output parameter or the return value,-- though the return value can only be an 'int' datatype-- NB: the values generated here are not transactional (they cannot be rolled back)-- variant 1: use output parameterDECLARE @p_out intEXEC get_seq_nr 'myseqtab', 1, @p_out outputINSERT INTO my_table VALUES (@p_out,…)go-- variant 2: use return valueDECLARE @ret intDECLARE @p_notused intEXEC @ret = get_seq_nr 'myseqtab', 1, @p_notusedINSERT INTO my_table VALUES (@ret,…)goEquivalent Sybase ASE code with key counter table:-- create tableCREATE TABLE my_seq (seq int)go-- initialize the sequenceINSERT INTO my_seq select 0go-- create stored procedure to increment and return the value–- note that this can also be done with an OUTPUT parameterCREATE PROCEDURE get_seq (@incr int)ASUPDATE my_seq SET seq = seq + @incrSELECT @seq = seq FROM my_seqRETURN @seqgo-- execute the procedure to get the next sequence numberDECLARE @seq intMiscellaneous migration aspects 40

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3EXEC @seq = get_seq 1INSERT INTO m_table VALUES (@seq,…)goNotes: When using a step count > 1 in ORacle (= 'incremented by' > 1), the ASE configuration parameter 'identityreservation size' must be set to the maximum block size (with sp_configure) The Oracle sequence attributes 'cycle', 'minvalue', 'maxvalue' and 'noorder' are not easy to support in ASE. Toimplement 'cycle', the identity counter can be set backwards with sp_chgattribute ..., 'identity_burn_max'. Yet another approach is to replace the sequence functionality with a static Java function which is visible across allprocesses (i.e. loaded by the system ClassLoader). This is not discussed further in this Guide.9.3 Error/Exception handlingIn Oracle, each SQL statement is automatically checked for errors before proceeding with the next statement. If an erroroccurs, control immediately jumps to an exception handler if one exists. PL/SQL supports the creation of customexception handlers to deal with different types of errors. Sybase ASE passes the control from one SQL statement toanother without checking for errors. This means that in Sybase ASE, error checks must be performed after every SQLstatement.The Oracle built-in procedure RAISE_APPLICATION_ERROR notifies the client of the server error condition andreturns immediately to the calling routine. Oracle places an implicit SAVEPOINT at the beginning of a procedure. Thebuilt-in RAISE_APPLICATION_ERROR procedure rolls back to this SAVEPOINT or to the last committedtransaction within the procedure. Control is then returned to the calling routine.Sybase ASE‟s equivalent to Oracle‟s RAISE_APPLICATION_ERROR is called RAISERROR. Unlike Oracle,RAISERROR does not return the controls to the calling routine.The first step in the conversion is to replace all RAISE_APPLICATION_ERROR calls with RAISERROR calls,followed immediately with a RETURN statement to emulate the Oracle exception handling.The second step is to handle the implicit SAVEPOINTs that Oracle creates at the beginning of each procedure. If thetransaction is within one procedure this is relatively simple. But if the code uses nested stored procedures this becomesmore complex and may require additional flow-control logic.9.4 Outer join limitationsSybase ASE does not allow another join relationship on a table that already has an outer join (see example #1 below). Inaddition, for a query with an outer join and a qualification on a column from the inner table of the outer join, the resultsmay be different than expected (example #2). Ideally, the database design should be de-normalized to remove the needfor these relationships. It is generally recommended to use the ANSI outer join syntax in Sybase ASE rather than the T-SQL style syntax (*=. =*).OracleExample #1:SELECT DISTINCT a.id, b.name, c.descFROM a, b, cWHERE a.id = b.id (+)and b.id2 = c.id2 (+) ( or b.id = c.id2 )and a.code = 1ORDER BY b.nameExample #2:SELECT a.id, b.nameSybase ASEExample #1:SELECT a.id, b.name, c.descFROM a, b, cWHERE a.id = b.idand b.id2 *= c.id2and a.code = 1UNIONSELECT a.id, '', ''FROM aWHERE a.code = 1and ( NOT EXISTS ( SELECT 'X'FROM bWHERE a.id = b.id ))ORDER BY 2Example #2:SELECT a.id, b.nameMiscellaneous migration aspects 41

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3OracleFROM a, bWHERE a.id = b.id (+)AND b.name LIKE 'Bill%'Sybase ASEFROM a, bWHERE a.id *= b.idAND b.name LIKE 'Bill%'9.5 Migrating JDBC/ODBC/… ApplicationsThe data and any SQL code that are stored in the database (e.g., stored procedures and triggers) are migrated with thesteps in Section 5. This section describes the following different types of client database applications that need to bemigrated from Oracle to Sybase ASE.Embedded SQL applicationODBC client applicationJDBC client applicationDatabase-specific library applicationC ApplicationsOracle formsIn all cases, conversion of one type of application to any of the other types of applications is possible. For example,instead of converting your Oracle Embedded SQL application to a Sybase Embedded SQL application, you can convertyour Oracle Embedded SQL application to a JDBC client application.9.5.1 JDBCMigrating JDBC connections from Oracle to Sybase requires understanding how Oracle manages JDBC drivers vs.Sybase ASE. This will determine your approach on how to migrate JDBC.Oracle provides the following JDBC drivers:Thin driver: a pure Java driver used on the client-side, without an Oracle client installation. It can be used withboth applets and applications.Oracle Call Interface (OCI) driver: used on the client-side with an Oracle client installation. It can be used onlywith applications.Oracle recommends the use of its Thin JDBC driver in all and any cases when connections are made through TCP/IP.Sybase ASE provides its own JDBC driver, named jConnect.9.6 Oracle FormsOracle Forms, a component of the Oracle Developer Suite, is Oracle's approach to design and build enterpriseapplications quickly and efficiently. Oracle Forms-based applications can retrieve and manipulate data in Oracledatabases. Applications developed with Oracle Forms are unlikely to run well, or run at all, against Sybase ASE.Sybase PowerBuilder is an enterprise development tool that allows you to build many types of applications andcomponents. It is one of a group of Sybase products that together provide the tools to develop client/server, multi-tier,and Internet applications.Oracle Forms applications can be rewritten using PowerBuilder. Most of the functionality provided by Oracle forms canbe also be created by using PowerBuilder with Sybase ASE.Migration of Oracle Forms application to PowerBuilder application is not straightforward. The "form" is the basis ofuser interface (UI) in Oracle Forms while the "datawindow" is the basis of UI in PowerBuilder. Both are graphical innature and are used to present data and accept user input. Both can contain elements graphical and non-graphical innature.For more information on PowerBuilder, see http://www.sybase.com/powerbuilder .Miscellaneous migration aspects 42

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.310 DBA TASKS CROSS-REFERENCEThis chapter seeks to provide some starting points with respect to mapping DBA tasks and concepts in Oracle to theirequivalent in ASE. However, the tools and methods used for database administration and monitoring are very differentas these are highly specific to each database brand. This makes it impossible to provide more than a loose mapping.For a successful migration, availability of sufficient DBA skills will be important.Description Oracle Sybase ASEHome Directory $ORACLE_HOME $SYBASEDefault Database/Instance $ORACLE_SID $DSQUERYCommand-line tool for SQLSQL*Plus in$ORACLE_HOME/bin/sqlplusisql in $SYBASE/OCS-15_x/bin/isqlImport/export dataLoading data from external filesimp / exp command or impdp/expdp command for data pumplocated in $ORACLE_HOME/binOracle imports and exports the dataand the DDL definitions, plus all otherobjects like type definitions, indexes,procedure and views.Data exported with exp can only beimported with imp.SQL*Loader is Oracle‟s high-speedloader. It loads data into Oracle veryfast, but it cannot unloading Oracledatabase data into files.For data import and export:bcp command located in$SYBASE/OCS-15_x/binFor the definition import andexport:defncopy command in$SYBASE/OCS-15_x/binTo reverse engineering the DDL tobe recreated in anotherenvironment:ddlgen command in$SYBASE/ASEP/binbcp command located in$SYBASE/OCS-15_x/bin(bcp can also unload data intofiles)Create a new databasedbca command in$ORACLE_HOME/binSybase Central or SQL commandcreate databaseCreate new network connectionnetca command in$ORACLE_HOME/bindsedit in $SYBASE/OCS-15_x/binDBA Tasks Cross-Reference 43

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3Description Oracle Sybase ASESetup new Oracle EnterpriseManager (OEM) serveremca command in$ORACLE_HOME/binSybase Central in combination withSybase Control Center is equivalentto OEM.Setup Sybase Central: installedautomatically when Sybase ASE isinstalled. Installs as part of theclient installation.Setup Sybase Control Center:Install the software with thesupplied Sybase Installer.Load data into the databaseSQL*LOADER in$ORACLE_HOME/bin/sqlldrbcp command located in$SYBASE/OCS-15_x/binusing bcp inStart database serverManual:Start SQL*Plus as sysdbaSQL> STARTUPStarts the instance, , mounts thedatabase and opens the database.Script:dbstart command in$ORACLE_HOME/binBoth commands are using the spfileslocated in $ORACLE_HOME/dbs inthe following order:1. spfile$ORACLE_SID.ora2. spfile.ora3. init$ORACLE_SID.orastartserver command in$SYBASE/ASE-15_x/installstartserver –fRUN_$DSQUERYThe RUN_$DSQUERY file is thespfile equivalent.Start backup server N/A startserver command in$SYBASE/ASE-15_x/installstartserver –fRUN_$DSQUERY_BSThe RUN_$DSQUERY_BS filecontains the startup parameters.Start monitor serveremctl command in$ORACLE_HOME/binemctl start dbconsolestartserver command in$SYBASE/ASE-15_x/installstartserver –fRUN_$DSQUERY_MSThe RUN_$DSQUERY_MS filecontains the startup parameters.DBA Tasks Cross-Reference 44

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3Description Oracle Sybase ASEShow running processesUnix:ps –aef | grep$ORACLE_SIDWindows:pslist –d oracleshowserver command in$SYBASE/ASE-15_x/installStop database serverLogin to SQL*Plus and execute:SQL>shutdownFor normal shut downSQL>shutdown immediate;For immediate shut downSQL>shutdown abort;For emergency shut downLogin via isql and execute thecommand:shutdowngoWithout parameters the server willwait for all transactions to finish.Adding „with nowait‟ will terminateall sessions and shut down theserver immediately.Stop backup serverOracle does not have a concept of aBackup Server.Login via isql into the Sybase ASEdatabase server and execute thecommand:shutdownBackup_Server_namegoBy default this waits for all currentbackups to finish. Adding „withnowait‟ will terminate all sessionsand shut down the backup serverimmediately.DBA Tasks Cross-Reference 45

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3Description Oracle Sybase ASEDatabase BackupInformation about systemperformanceInformation about schemaOracle has the following ways ofperforming a database backup:imp / exp commands: this canimport/export the entire database(including all data), individualschemas or a single table.Data Pump: new import / exportfeature since Oracle 10g. The basicfunctionality is identical to the oldimp and exp commands, butData Pump is faster.RMAN: The Oracle RecoveryManager (RMAN), command-lineas well as Enterprise Managerbased,is the Oracle-preferredmethod of efficiently backing upand restoring an Oracle database.Various backup options exist,some of which require the Oracledatabase to be shut down first.Oracle dynamic performance viewsOracle static data dictionary viewsSybase ASE always performs a hotbackup; this requires hardly anyconfiguration. This is the samefunctionality as Oracle‟s ArchiveLog backup, but no archive filecleanup is necessary.The command dump databasebacks up an entire database (fulldump); dump transactiononly backs up the transaction logsince the previous dump(incremental backup).The command load databaserestores a full backup; loadtransaction loads anincremental backup following loadsof earlier backups.For these dump/load commands,Backup Server must be running.MDA tablesSystem tables (catalogs) and systemstored procedures (sp_*)DBA Tasks Cross-Reference 46

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.311 ORACLE-TO-SYBASE MIGRATION CROSS-REFERENCEThis chapter provides specific suggestions on how to migrate a Oracle feature to Sybase ASE. This cross-reference is anextended version of the Oracle checklist in chapter 3. Much of this type of conversion can in principle be done using atext editor with search-and-replace commands, or with tools like 'sed'.11.1 Oracle-to-Sybase ASE migration: category "Simple Conversion"OracleConnecting to an Oracle schemaCONNECT user_name/passwordSET ROLEThe Oracle SQL*Plus “slash” character sends precedingPL/SQL text to the Oracle server./The semicolon is a statement delimiter in PL/SQL;The Oracle DUAL tableSELECT sysdate FROM DUALSET SAVEPOINT savepoint-nameVariable/Parameter declarations; naming syntaxDECLARE count NUMBERAssign default value in variable declarationDECLARE blood_type char(2) := 'O';Multiple variable declarations with a single DECLAREkeywordDECLAREV1 NUMBER(10,0);V2 CHAR(20);CURSOR mycursor ISSELECT * FROM mytable;Sybase ASE ("simple conversion")Connecting to a Sybase database; also see section 4.5USE database_nameEquivalent to the ISQL go command at the end of abatch of SQL statementsgoNo statement delimiters; remove Oracle delimitersemicolonsShould be removed completely from queries in SybaseASE; but if it occurs many times in Oracle queries, itmay also be created as a dummy table in ASE; seesection 4.10SAVE TRAN[SACTION] savepoint-nameIn Sybase ASE, variable/parameter names must startwith the character @. In ASE, the maximum length is30 bytes; in Oracle, longer names are allowed.DECLARE @count INTExplicitly assign value after variable declarationDECLARE @blood_type CHAR(2)SET @blood_type = 'O'When declaring multiple variables with oneDECLARE keyword, the variables must be commaseparatedASE. Cursors must be declared separatelywith DECLARE…CURSORDECLARE@v1 int,@v2 char(20)Oracle-to-Sybase Migration Cross-Reference 47

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3OracleDeclarations without DECLARE keyword in declarationsection of stored procedures/functionsCREATE PROCEDURE pASV1 NUMBER(10,0);V2 CHAR(20);CURSOR mycursor ISSELECT * FROM mytable;BEGIN…statements…END;Variable assignmentmyvar := expression;Transferring table data into a variableSELECT my_col INTO my_variableFROM my_table WHERE id = 123;Constants%TYPE denotes the datatype of a column in an existingtableSybase ASE ("simple conversion")DECLARE keyword is required in Sybase ASE.Cursors must be declared separately withDECLARE…CURSORCREATE PROCEDURE pASBEGINDECLARE@v1 int,@v2 char(20)DECLARE mycurs CURSOR ASSELECT * FROM mytable…statements…ENDgoSET @myvar = expressionSELECT @myvar = expressionDirectly select into the variableSELECT @my_variable = my_col FROMmy_table WHERE id = 123Redefine as variables and check scope of usage (localor global).Explicitly declare the variable with the column's actualdatatypeDECLARE count my_table.id%TYPEDynamic SQLEXECUTE IMMEDIATE '…sql…';Optional clauses:EXECUTE IMMEDIATE '…sql…' USING …;EXECUTE IMMEDIATE '…sql…' INTO …;EXECUTE IMMEDIATE '…sql…' BULK COLLECTINTO …;Use Sybase ASE execute-immediateSET @cmd = '…sql…'EXECUTE (@cmd)or:EXECUTE ('…sql…')With the clauses USING (specifies parameters to thedynamic SQL), INTO (puts results into variables forsingle-row results), BULK COLLECT INTO (storesresults into Oracle collections), the query should berewritten to achieve the same effect in ASE.Oracle-to-Sybase Migration Cross-Reference 48

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3OracleLoops with LOOP/END LOOP:LOOP…statements…;EXIT [WHEN …condition…]; /*exit loop*/…statements…;/* back to top for next iteration: */CONTINUE [WHEN …condition…];…statements…;END LOOP;Sybase ASE ("simple conversion")Convert to WHILE-loops. Oracle's EXIT andCONTINUE corresponds to ASE's BREAK andCONTINUE though ASE cannot have a conditionassociated with these statements.WHILE 1=1BEGIN…sql……conditional exit…ENDOr:WHILE BEGIN…statements…ENDFOR loopsFOR i IN 1..5LOOP…statements…END LOOP;CURSOR loopsConvert to WHILE; use variables to implement FORDECLARE @i int, @i_start int, @i_endintSET @i_start = 1, @i_end = 5SET @i = @i_startWHILE @i

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3OracleOracle Outer join syntaxSybase ASE ("simple conversion")Translates to Sybase ASE T-SQL outer join syntax orto ANSI outer join syntax (preferred). Somerestrictions apply in Sybase, see section 9.4.// right outer joinSELECT * FROM t1, t2WHERE t1.col1 = t2.col2(+)SELECT * FROM t1, t2WHERE t1.col1 =* t2.col2syntax)(T-SQLSELECT * FROM t1 RIGHT [OUTER] JOIN t2ON t1.col1 = t2.col2 (ANSI syntax)// left outer joinSELECT * FROM t1, t2WHERE t1.col1(+) = t2.col2SELECT * FROM t1, t2WHERE t1.col1 *= t2.col2syntax)(T-SQLSELECT * FROM t1 LEFT [OUTER] JOIN t2ON t1.col1 = t2.col2 (ANSI syntax)SET TRANSACTION READ WRITE Remove in Sybase ASE; see chapter 8ALTER TABLE mytable TRUNCATE PARTITIONpartition_nameCREATE OR REPLACE PROCEDURE (orFUNCTION)ALTER PROCEDURE (or FUNCTION)CREATE PROCEDURE… IS…Stored procedure OUT/IN OUT parametersCREATE PROCEDURE p(a IN number, b OUT number, c IN OUT number)IS …Replace by TRUNCATE TABLE mytablePARTITION partition_nameReplace by DROP PROCEDURE (or FUNCTION)followed by CREATE PROCEDURE (orFUNCTION)Replace by DROP PROCEDURE (or FUNCTION)followed by CREATE PROCEDURE (orFUNCTION)Change to CREATE PROCEDURE… AS…Sybase ASE supports input and input+outputparameters, but no output-only parameters. Inaddition, the output keyword must be specified whencalling the procedureCREATE PROCEDURE p@a int, @b int output, @c int outputAS …EXEC p @var1, @var2 output, @var3 outputStored procedure execution with named parameters(param => value)result := proc_name(param1 => my_var, param2=> 123);Convert to ASE syntax with named parameters:EXEC @result = proc_name @param1 = @my_var,@param2 = 123Oracle-to-Sybase Migration Cross-Reference 50

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3OracleStored procedure execution with positional parameters(:var)VAR a NUMBER;VAR b NUMBER;VAR c NUMBER;EXEC proc_name (:a, :b, :c)Procedure executionIn Oracle, the EXEC[UTE] keyword is not usedCREATE PROCEDURE p1ASBEGIN…statements…END;CREATE PROCEDURE p2ASBEGINp1;END;SQL Function declaration with DETERMINISTICkeywordSybase ASE ("simple conversion")Convert to ASE syntax with named parameters:declare @a int,@b int,@c int,@return_statusEXEC @return_status = proc_name @a, @b, @cIn ASE, the EXEC[UTE] keyword is mandatory(except when the procedure is the first statement inthe batch)CREATE PROCEDURE p1ASBEGIN…statements…ENDgoCREATE PROCEDURE p2ASBEGINEXECUTE p1ENDgoIn Sybase ASE, remove DETERMINISTICCREATE FUNCTION f_func (p NUMBER)RETURN NUMBERDETERMINISTICIS…Execution of a SQL Functionselect myfunc(123);DECLARE CURSOR cursor-name IS…Oracle cursorsIn Sybase ASE, the name of the executed SQL functionmust always be preceded by the owner's nameselect dbo.myfunc(123)select jsmith.yourfunc(456)Change to DECLARE cursor-name INSENSITIVECURSOR AS…ASE's insensitive cursor is closest to Oracle's cursorimplementationOracle cursors are automatically deallocated whenclosed.ASE cursors must be deallocated explicitly withDEALLOCATE CURSOR cursor-name. This shouldbe added after every cursor CLOSE.Cursor Attribute %ISOPEN No equivalent in ASE, remove .Cursor Attributes %FOUND, %NOTFOUNDConvert to using @@sqlstatusCursor Attribute %ROWCOUNTConvert to using @@rowcountOracle-to-Sybase Migration Cross-Reference 51

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3OracleAFTER triggers (on statement level)INSTEAD OF triggers (on views)SQL%ROWCOUNTIndicates the number of rows affected by the mostrecently executed PL/SQL statementSELECT * FROM mytable WHERE id = 1234;IF SQL%ROWCOUNT = 0 THENDBMS_OUTPUT.PUT_LINE('No rowsfound.');END IF;BOOLEAN datatype (for PL/SQL variables only)Allowed values are TRUE, FALSE and NULL.MERGE statementPartitioned tables with composite partitioningCREATE TABLE mytable(...columns...)PARTITION BY RANGE(ptn_key_col)SUBPARTITION BY HASH(subptn_key_col)[...]Performance-optimized native PL/SQL datatypes (forPL/SQL variables only)Sybase ASE ("simple conversion")Similar to Sybase ASE table triggersSimilar to Sybase ASE INSTEAD-OF triggersReplace by @@rowcountDECLARE @rc INT, @err INTSELECT * FROM mytable WHERE id = 1234SELECT @rc = @@rowcount, @err = @@errorIF @rc = 0print 'No rows found.'Convert to variables of type BIT (allows only 0 and 1;NULL = 0) or TINYINT NULL. Decide on astandard encoding like 0=false; 1=true.Instead of using the numeric literals 0 and 1 in testsand assignments, two variables named @true and@false could be defined (and set to 1 and 0), so as touse these names instead.Migrate to ASE 15.7, which supports MERGEASE supports partitioned tables, but no compositepartitioning. Remove the SUBPARTITION clause.Convert to INTEGER, DOUBLE, FLOAT datatypesBINARY_INTEGERBINARY_DOUBLEBINARY_FLOATIF-THEN-ELSEIF expressionTHENstatement;ELSEstatement;END IF;In Sybase ASE, there is no THEN or END IF, soremove themIF expressionstatementELSEstatementOracle-to-Sybase Migration Cross-Reference 52

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3OracleMultiple statements in an IF-THEN-ELSE branchIF expressionTHENstatement;statement;ELSEstatement;statement;END IF;Conditional test based on EXISTS subqueryDECLAREv_x NUMBER(10,0);v_temp NUMBER(1, 0) := 0;SELECT 1 INTO v_tempFROM DUALWHERE EXISTS ( …subquery… );Sybase ASE ("simple conversion")In Sybase ASE, there can be only a single statementexpression in each branch; multiple statements mustbe grouped in a BEGIN- END block.IF expressionBEGINstatementstatementENDELSEBEGINstatementstatementENDCan be kept identical in ASE, but this can also besimplified greatly in ASE:DECLARE @x intSET @x = 0IF EXISTS ( …subquery… )SET @x = -1ENDIF v_temp = 1 THENv_x := -1;String concatenation operator: ||userenv('sessionid')MOD(X,Y)CEIL()TRUNC(number)SUBSTR()SUBSTR() function with two parametersSELECT substr('John', 2) returns 'ohn'LENGTH()CHR()REPLACE()Sybase ASE supports + as the string concatenationoperator; it also supports || though this is formallyundocumented.Equivalent to session-specific global variable @@spid(since @@spid values are re-used, thesysprocesses.kpid value can also be used to create abetter uniqueness)X % YCEILING()CONVERT(INT,..)SUBSTRING()Rewrite with the length of the expression as the 3rdparameterSELECT substring ('John', 2, len('John'))CHAR_LENGTH() or LEN() or DATALENGTH()CHAR()STR_REPLACE()Oracle-to-Sybase Migration Cross-Reference 53

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3OracleTO_CHAR(expression)TO_CHAR(expression, datepart)TO_CHAR(sysdate, 'dd')TO_CHAR(expression, format-string)TO_CHAR(some-number, '999D99')TO_CHAR(some-number, '999')TO_NUMBER(expression)Date/time functions and calculationsSELECT add_months( xyz ,3 ) FROM dualSELECT nr_days := DateEnd - DateStartSYSDATE, SYSTIMESTAMPTRUNC(date/time [,unit])LAST_DAY()Sybase ASE ("simple conversion")CONVERT(VARCHAR(n), expression)Convert to use the ASE datepart() functionCONVERT(VARCHAR,datepart(dd,getdate()))Implement the formatting explicitly with ASEfunctionsCONVERT(VARCHAR,ROUND(some-number,2))CONVERT(VARCHAR,CONVERT(INT,somenumber))CONVERT([BIG|SMALL|TINY]INT,expression)CONVERT(NUMERIC(n,m), expression)Rewrite with ASE date/time functions likeDATEADD(), DATEDIFF(), DATEPART(),DATENAME()SELECT DATEADD(month, 3, xyz)SELECT @nr_days = datediff(dd, DateStart,DateEnd)Replace by CURRENT_BIGDATETIME()Replace by CONVERT() with the date/timeformatting stylesLast day of a month function based on a date value;rewrite using ASE SQL functionsNVL() functionNVL(a,b)Inconsistent use of upper/lowercase for identifiers(Oracle is case-insensitive for identifiers)Identifiers that are Sybase ASE reserved words (seesection 4.8)INSTR() function with two parametersSELECT INSTR('abcabc', 'ab')Replace by ISNULL() functionISNULL(a,b)Either use a case-insensitive sort order in ASE, or useconsistent upper/lowercase spelling for identifiers (seesection 5.2)Change such identifiers so that they are not a reservedword.Replace by charindex()SELECT CHARINDEX('abcabc', 'ab')Oracle-to-Sybase Migration Cross-Reference 54

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3OracleDerived tables (also known as "inline views") withoutcorrelation nameselect afrom (select b as a, d as b from mytab)where b > 0ALTER TABLE … SPLIT PARTITION…ALTER TABLE … MERGE PARTITIONS…Quoted identifiers. Oracle allows using quoted identifiersby enclosing an identifier in double quotes. Quotedidentifiers are case-sensitive, unlike unquoted identifierswhich are case-insensitive.CREATE TABLE "mytable" ("mycol" NUMBER);Note that all-uppercase quoted identifiers do not need tobe quoted: "MYTABLE" (quoted) is identical toMYTABLE (without quotes) in Oracle.Oracle hints; indicated by a special comment directlyfollowing the SELECT:Sybase ASE ("simple conversion")ASE always requires a correlation name for a derivedtableselect afrom (select b as a, d as b from mytab)[as] somenamewhere b > 0Migrate to ASE 15.7 ESD#2 which supports thesestatements.Sybase ASE also allows quoted identifiers delimited bydouble quotes, but this is disabled by default. To usequoted identifiers, the command setquoted_identifiers on must be executed first. Thiscommand affects only the session executing it.Ignore quotes for all-uppercase quoted identifiers.Remove all Oracle hintsSELECT /*+ INDEX (C) */NAMEFROM CUSTOMERS CWHERE ZIPCODE = 54321Hint keywords:ALL_ROWSAPPENDCACHECLUSTERFACTFIRST_ROWSFULLHASHINDEXINDEX_ASCINDEX_DESCINDEX_FFSINDEX_JOININDEX_SSLEADINGMERGEMONITORNO_EXPANDNO_FACTNO_INDEXREWRITEUNNESTUSE_CONCATCURSOR_SHARING_EXACTDRIVING_SITEDYNAMIC_SAMPLINGMODEL_MIN_ANALYSISNATIVE_FULL_OUTER_JOINNO_NATIVE_FULL_OUTER_JOINNO_PARALLELNO_PARALLEL_INDEXNO_PUSH_PREDNO_PUSH_SUBQNO_PX_JOIN_FILTERNO_QUERY_TRANSFORMATIONNO_RESULT_CACHENO_REWRITENO_STAR_TRANSFORMATIONNO_UNNESTNO_USE_HASHNO_USE_MERGENO_USE_NLNO_XML_QUERY_REWRITENO_XMLINDEX_REWRITESTAR_TRANSFORMATIONUSE_NL_WITH_INDEXNOPARALLEL_INDEXNOAPPENDNOCACHENOPARALLELNOREWRITEOPT_PARAMORDEREDPARALLELPARALLEL_INDEXPQ_DISTRIBUTEPUSH_PREDPUSH_SUBQPX_JOIN_FILTERQB_NAMERESULT_CACHEINDEX_COMBINEINDEX_SS_ASCINDEX_SS_DESCNO_INDEX_FFSNO_INDEX_SSNO_MERGENO_MONITORUSE_HASHUSE_MERGEUSE_NLOracle-to-Sybase Migration Cross-Reference 55

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.311.2 Oracle-to-Sybase ASE migration: category "Partial Rewrite"For the Oracle features listed below, migration to partly equivalent Sybase ASE features is possible, although potentiallysignificant syntax changes and possibly partial rewriting of algorithms may be required.OracleDatabase linksCREATE DATABASE LINK SALES.PROD[ CONNECT TO CURRENT_USER ] using'SALES';SELECT * FROM salesdata@SALES;External tablescreate table my_external_tab( ...columns...)organization external( default directory external_data_diraccess parameters( records delimited by newlinefields terminated by ','location ('...pathname...') )Sybase ASE ("partial rewrite")Equivalent to ASE proxy tables, mapping to a remotetablecreate proxy_table sales_proxyat SALES.salesdb..salesdataselect * from your_proxyEquivalent to ASE proxy tables, mapping to an O/Sfilecreate proxy_table my_external_tab( ...columns...)external file at '...pathname...'column delimiter ','SequencesGenerate unique numbers, for example for primarykeysTable-valued User-defined SQL FunctionsPipelined Table Functions ( a special case of TablevaluedUser-defined SQL Functions)FUNCTION my_funcRETURN my_out_tab PIPELINED;SynonymsComments on database objectsCOMMENT ON TABLE mytab IS "This is my table";In some cases, this can be replaced by using ASEidentity columns. In other cases, the sequencefunctionality must be emulated with a key countertable and a stored procedure. See section 9.2.ASE only supports scalar User-defined SQLfunctions. Rewrite with temporary tables.Rewrite with cursors or with an ASE proxy tablemapping to a stored procedure (though theperformance of Oracle Pipelined Table Functions canprobably not be achieved)For synonyms for tables or views, replace by an ASEview; for table/view synonyms at dblinks, replace byan ASE proxy table.For synonyms for stored procedures or functions,replace by a wrapper stored procedure/function; forstored procedure synonyms at dblinks, replace by aremote procedure call.For other synonyms, application changes are required.No direct equivalent. An method for storing objectcomments in ASE is describedin http://www.sybase.com/detail?id=607Oracle-to-Sybase Migration Cross-Reference 56

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3OracleBitmap indexesCREATE BITMAP INDEX my_ix ON mytable(…)Temporary tablesCREATE GLOBAL TEMPORARY TABLE temptab[…] [ON COMMIT {PRESERVE|DELETE} ROWS]Sybase ASE ("partial rewrite")ASE does not support bitmap indexes. RemoveBITMAP and create a regular index.Sybase IQ supports bitmapped indexes.Replace by ASE temporary tables whose names startwith the # character:CREATE TABLE #temptab […]SELECT * INTO #temptab FROM my_tableNote that there are differences in scope between anOracle temporary table and a Sybase #temporarytable: an Oracle temporary table is visible by all users(though a user can only see his own data rows in thetable) whereas a Sybase #temp table is visible only tothe session that created it. In addition, an Oracletemporary table is a permanent table that must bedropped explicitly (only the data in the Oracletemporary table is automatically deleted); a Sybase#temp table is automatically dropped at the end of theprocedure or session that created it.IS TABLE OF or AS VARRAY(n)OFdefine a PL/SQL "table" (= non-database table, array).Also known as a "collection" (various types of Oraclecollections exist).Rewrite algorithm with a temporary table and useFETCH or SELECT to process rows. Alternatively,convert the table to a Java object with different dataelements, which can be stored in a table column.Oracle-to-Sybase Migration Cross-Reference 57

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3OracleNested tablesAllow a column to be defined as a table, that can holdN rows (=N column values)Also known as a "collection" (various types of Oraclecollections exist).Sybase ASE ("partial rewrite")Change to use a separate table for the nested table inthe column, with a primary key-foreign keyrelationship.CREATE TYPE address_t AS OBJECT (street VARCHAR2(30),city VARCHAR2(20),state CHAR(2),zip CHAR(10),country CHAR(30));CREATE TYPE address_tab IS TABLE OFaddress_t;CREATE TABLE customers (custid NUMBER,address address_tab )NESTED TABLE address STORE AScustomer_addresses;INSERT INTO customers VALUES (654,address_tab(address_t('148 Oak Drive','Dallas', 'TX', '75240', 'USA'),address_t('561 VirginiaRoad', 'Concord', 'MA', '01742','USA')));NB: customer_addresses is an object table as wellas a nested table at the same time.Object tablesCREATE TYPE person_type AS OBJECT (name VARCHAR2(30), addressVARCHAR2(100));Either replace with regular tables and columns, or usea Java class to define a column as a complex datatypecontaining different fields.CREATE TABLE person_obj_table OFperson_type;%ROWTYPE declares a PL/SQL record with thesame columns as a particular tableDECLARE cust customer%ROWTYPEDefine a PL/SQL record type by enumerating thefields with IS RECORD OF or TYPE…IS RECORDNon-integer RETURN value in stored procedureOracle stored procedures can return a scalar value ofany datatype.Declare each field as an individual variable and modifyall references accordingly. Alternatively, convert therecord to a Java object with different data elements,which can be stored in a table column.Declare each field as an individual variable and modifyall references accordingly. Alternatively, convert therecord to a Java object with is treated as an array.Sybase ASE stored procedures can only return aninteger value.When a different datatypes is returned, rewrite byusing an output parameter or rewrite with a SQLfunctionOracle-to-Sybase Migration Cross-Reference 58

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3OracleUser-defined PackagesOverloaded stored procedures(multiple procedures with identical names but differentparameter datatypes or different number of parameters)PL/SQL Exception handling; defining exceptionhandlersSybase ASE ("partial rewrite")Translate packages to the individual objects that thepackage consists of (stored procedures, data types,etc.)Translate to a single stored procedures or split intoseparate stored proceduresRewrite and perform checks on @@error and@@rowcount after every SQL statement.EXCEPTION WHEN ZERO_DIVIDE THEN-- handles 'division by zero' error[…]EXCEPTION WHEN TOO_MANY_ROWS-- handle case that > 1 row affected[…]EXCEPTION WHEN NO_DATA_FOUND-- handle case that no rows affected[…]EXCEPTION WHEN DUP_VAL_ON_INDEX-- handle case for duplicate index key[…](etc… other conditions existSQLCODE, SQLERRMIndicates the error status and error message text of themost recently executed PL/SQL statement; used withthe exception handling sectionEXCEPTIONWHEN OTHERS THENerror_code := SQLCODE;error_msg := substr(SQLERRM, 1, 200);INSERT INTOaudit_table(err_no,err_msg)VALUES (error_code, error_msg);END;RAISE_APPLICATION_ERRORIn stored procedures, this also rolls back until theimplicit savepoint at the start of the procedure (or afterthe last committed transaction in the procedure)Column EncryptionLOB locatorsReplace SQLCODE by @@error. ASE has noequivalent of SQLERRMDECLARE @rc INT, @err INTSELECT * FROM mytable WHERE id = 1234SELECT @rc = @@rowcount, @err = @@errorIF @err = 0BEGININSERT INTOaudit_table(err_no,err_msg)VALUES (@err, '');ENDRecode with Sybase ASE functions such asRAISERROR or PRINT immediately followed by aRETURN in stored proceduresRewrite with ASE column encryptionMigrate to ASE 15.7, which supports LOB LocatorsOracle-to-Sybase Migration Cross-Reference 59

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3OracleData compressionSybase ASE ("partial rewrite")Migrate to ASE 15.7, which supports datacompressionRetrieving data to the client in stored procedures usingDBMS_OUTPUT packageDBMS_OUTPUT.PUT_LINEDBMS_*, UTL_* package calls(excl. DBMS_OUTPUT)SDO_* package callsSQL*Loader (sqlldr)Oracle‟s high-speed data loader utility (only loading, nounloading).Materialized ViewsReplace by direct SELECT or PRINT statementsRecode with Sybase ASE features if possible,otherwise removeSpatial data features, remove/recodeRewrite using the Sybase bcp utility.Migrate to ASE 15.7 ESD#2 which supportsmaterialized views (a.k.a. "precomputed result sets").Global variables (in a PL/SQL package)INTERSECT constructSELECT a FROM tab1 WHERE b > 10INTERSECTSELECT c FROM tab2 WHERE d = 0MINUS constructSELECT a,b,c FROM tab1 WHERE …MINUSSELECT d,e,f FROM tab2 WHERE …Global variables are not supported; either pass allvariables around as parameters, or store such values ina table and read/update that table as needed.Alternatively, Java static classes can be used.Rewrite as a joinSELECT tab1.a FROM tab1, tab2WHERE tab1.a = tab2.cAND tab1.b > 10 AND tab2.d = 0Rewrite with NOT IN (single column) or NOTEXISTS (multiple columns)SELECT a,b,c FROM tab1WHERE NOT EXISTS(SELECT * from tab2WHERE tab2.d = tab1.aAND tab2.e = tab1.bAND tab2.f = tab1.c)Oracle-to-Sybase Migration Cross-Reference 60

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3OracleSybase ASE ("partial rewrite")Specific SQL clausesAS OFAS OF TIMESTAMPCONNECT BYDIMENSIONDIMENSION BYEXCLUDEGROUPING SETSINCLUDEMEASURESRETURN ALL ROWSRETURN UPDATEDROWSPARTITION BYREFERENCESYSTIMESTAMPCROSSCUBEFORKEEPMAINMODELNAVNOCYCLENOWAITONONLYRULESSAMPLESEEDSKIPIGNOREITERATENATURALNULLSNULLS FIRSTNULLS LASTROLLUPSIBLINGSSINGLEREFERENCELOCKEDSTART WITHUNIQUEUNPIVOTWAITReplace by corresponding Sybase ASE functionality, ifavailable. Otherwise, rewriting the SQL is required.Capitalize first letter of all words in a stringINITCAP( string-expression )INSTR() function with three or four parameters(3=start position, 4=n th occurrence)SELECT INSTR('abcabc', 'ab', 2)SELECT INSTR('abcabcabc', 'ab', 2, 2)NVL2() functionSELECT NVL2(salary,salary*2, 123) FROM…DECODE() functionUsed to evaluate with „if-else‟ type logicSELECTDECODE(T1.C1, 'ABC',T1.C2,T1.C3) as P_IDFROM T1Primary key and foreign key with different datatypes,different precision/scale (for numeric datatypes) ordifferent length (for character datatypes)Cluster (as created with CREATE CLUSTER)Rewrite with stored procedures or SQL functionsCreate a SQL function to perform the advancedsearches.Note that charindex() accepts a 3 rd paramter inASE 15.7, but this cannot have a negative value (forbackward search) as is allowed in OracleConvert to a CASE expressionSELECTCASE WHEN salary = NULL OR salary = ''THEN 123ELSE salary * 2 ENDFROM…Convert to a CASE expressionSELECTcase T1.C1when 'ABC' then T2.C2 else T3.C3end as P_IDFROM T1Unlike Oracle, ASE requires that a foreign key andprimary key have identical datatypes. Modify thedatatypes accordingly.Change the data model to use individual tables;consider using views to avoid making changes toexisting SQL codeOracle-to-Sybase Migration Cross-Reference 61

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3OracleVARCHAR2 variables longer than 16384 bytesDECLARE msg VARCHAR2(32767)(for columns, VARCHAR2 cannot be longer than 4000bytes)SQL functions where the last statement is notRETURNDerived tables (also known as "inline views") using"with" syntaxSybase ASE ("partial rewrite")The maximum length of string variables is 16384bytes; rewrite code, either using shorter ASE varcharstrings, or use ASSE LOB variables or LOB locatorsin ASE 15.7ASE requires that a SQL function has RETURN as itslast statement. This may require some re-coding of theflow control.Rewrite with ASE derived table syntaxwith x as (select b as a, d as b from mytab)select a from x where b > 0UNIONs in cursorsPRAGMA directivesAutonomous transactions(AUTONOMOUS_TRANSACTION)ON DELETE CASCADE constraintsXMLTYPE (XML data type)XML functions extract(), existsnode(), xmlexists(), etcROWIDAn Oracle table always contains a ROWID columnwith a unique identifier for each row, even if noprimary key was defined for the table. The ROWID canbe referenced in queries.SELECT last_name, ROWIDINTO var_lname, var_rowidFROM empWHERE empid = 98765A cursor with a UNION cannot be updatable in ASE;such code may need to be rewritten.Rewrite with ASE syntax/functionality.ASE does not support autonomous transactions;rewrite with ASE transactional semantics.Rewrite with ASE triggersRewrite with TEXT, IMAGE or VARCHARdatatatypes and with ASE functions xmlextract(),xmltable(), etc.A similar effect can be achieved by add an identitycolumn to each table, and name the column"ROWID".There can be only one identity column per table. Ifthere is already an identity column for the primarykey, for example to replace an Oracle sequence, add avirtual computed column named "ROWID", equal tothe identify column. This method can also be usedwhen existing Oracle code uses a different spelling,like "rowid":CREATE TABLE mytab(ROWID NUMERIC IDENTITY, rowid ASROWID,…other columns…)Oracle-to-Sybase Migration Cross-Reference 62

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3OracleROWNUMFor each row returned by a query, the ROWNUMpseudocolumn returns a number indicating the order ofthe row in the result set. This can be used in queries,for example to select only a subset of the result set.SELECT * FROM empWHERE state = 'CA'AND ROWNUM > 9 AND ROWNUM < 21ORDER BY last_name;Sybase ASE ("partial rewrite")When the objective is to select the top N rows, thiscan be achieved with select top N …from…When more complex selections are done (e.g. only getrows 10-20) , the an identity column (which shouldprobably be named "ROWNUM") can be added tothe result set with the identity() function, whichassigns a sequence number to every row in the resultset. This column can then be used in queries. Notethat this requires one extra query step:SELECT *, ROWNUM=identity(int)INTO #t FROM empWHERE state = 'CA'ORDER BY last_nameSELECT FROM #tWHERE ROWNUM > 9 AND ROWNUM < 21Oracle-to-Sybase Migration Cross-Reference 63

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.311.3 Oracle-to-Sybase ASE migration: category "Major Rewrite"For the Oracle features listed below, no direct equivalent is available in Sybase ASE. Consequently, rewriting orredesigning algorithms or parts of applications will be required.OracleOracle MVCC (Multi-Version Concurrency Control;"writers don‟t block readers, readers don't blockwriters")Relevant aspects:Applications or queries relying on nonblockingMVCCLong-running transactionsDDL in transactionsSET TRANSACTION READ ONLYSQL*Plus autocommit/commit-on-exitSybase ASE ("major rewrite")No direct equivalent of MVCC. Some aspects may beaddressed by using DATAROWS locking, using theREADPAST option., or running SELECT queries atisolation level 0 (READ UNCOMMITTED).For other cases, the application may need to bemodified, for example by keeping transactions as shortas possible.See section 8 for details.SQL*PlusThe Sybase ASE counterpart for SQL*Plus is theisql utility. SQL*Plus allows for more complexconfiguration settings and SQL*Plus-specific (i.e.non-PL/SQL) client-side commands insideSQL*Plus. Existing SQL*Plus-based functionalitymust be rewritten for ASE.BEFORE triggersNo direct equivalent. Some aspects of thefunctionality (like domain integrity) may be covered byrules or CHECK constraints at the table definition level;however an Oracle BEFORE trigger can perform farmore complex processing than can be handled byrules or constraints. If this functionality cannot beimplemented with Sybase ASE "after" triggers, theapplication may need to be changed to apply thefunctionality in a different way.Triggers on row level (BEFORE and AFTER)No direct equivalent; some logic may be changed tooperate on the ASE pseudo-tables inserted anddeleted; otherwise, see BEFORE triggers above.Multiple triggers for a DML type on a tableNo direct equivalent; if the functionality cannot beconsolidated in a single ASE trigger, the applicationmay need to be changed to apply the functionality in adifferent way.Oracle-to-Sybase Migration Cross-Reference 64

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3OracleREF CURSORSybase ASE ("major rewrite")No direct equivalent. In ASE, REF CURSORs needto be rewritten, for example by rewriting all storedprocedures involved, or by putting query results in(temporary) tables and let the different storedprocedures access these. Also see section 9.1.Regular Expressions; functions REGEXP_LIKE(),REGEXP_SUBSTR(), REGEXP_REPLACE(),REGEXP_INSTR()No direct equivalent since ASEdoes not supportregular expressions.Rewrite with ASE SQL usingcustom processing instead of RegExWindowing queries (SELECT…OVER(…) …)SELECT name, salary,NTILE(4) OVER (ORDER BY salary DESC)AS quartileFROM empWHERE dept_id = 123;No equivalent in Sybase ASE. Rewrite with classicASE features, possibly requiring breaking up a queryin multiple steps. Alternatively. Use Sybase IQ whichdoes support windowing queries as well as manyanalytic functions.SQL function OUT/IN OUT parametersSybase ASE supports only input parameters for SQLfunctions. If output parameters are used, rewrite withstored proceduresNon-deterministic SQL Functions (functions whoseresult may be independent of the function inputparameters)This cannot be concluded from PL/SQL keywordssince Oracle supports only the keywordDETERMINISTIC to indicate that a function isdeterministic. Non-determinism cannot be indicatedexplicitly, but only from code inspection.Sybase ASE supports only deterministic SQLfunctions. DML, DDL, procedure calls, executeimmediate,certain function calls and utilitycommands are not allowed in a SQL function.If these occur in an Oracle SQL Function, rewritewith ASE stored proceduresSQL Aggregate FunctionsCREATE FUNCTION f_aggr (p NUMBER)RETURN NUMBERAGGREGATE USING object-type;No direct equivalent. Rewrite using available ASEfeatures.BFILE datatypeA BFILE column stores a locator (link) to a binary fileoutside of the databaseNo direct equivalentOracle Streams; Oracle Data GuardUse Sybase Replication Server.Oracle-to-Sybase Migration Cross-Reference 65

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3OracleOracle RAC for high-availabilitySybase ASE ("major rewrite")Use Sybase ASE Cluster EditionOracle FlashbackOracle flashback-related pseudocolumnsORA_ROWSCN, VERSION_XID,VERSION_STARTSCN, VERSION_ENDSCN,VERSION_STARTTIME, VERSION_ENDTIME,VERSION_OPERATIONNo direct equivalent. Some aspects may be covered byusing the ASE "auditing" feature, by using ASE"archive databases", and by using the until_timeoption when loading a transaction log dump.For other cases, old data values can be retained bymeans of triggers.See "Oracle Flashback" aboveOracle Snapshot Standby (combination of datareplication and Flashback)No direct equivalent. Similar functionality can beachieved with Replication Server.Oracle SQL Plan ManagementStores and maintains query plans to support the queryoptimizer to make better decisions: every time a querygets executed, the query optimizer compares thecurrent query plan with the stored query plan andchooses the better plan automatically.(for DBA/tuning purposes, not affecting applicationquery syntax)Some aspects are covered by abstract query planassociation ('abstract plan load') as well as by theQPTune utility. However, ASE does not supportautomatic evaluation of newly generated plans versuscaptured past plans.AWR (Automatic Workload Repository)Stores every query with corresponding performanceindicators and metrics in a repository, allowingidentifying the top poorly performing queriesautomatically (for which query plans managed byOracle SQL Plan Management will be used when thequery are being executed again)(for DBA/tuning purposes, not affecting applicationquery syntax)Oracle Advanced QueuingQuery metrics are captured in ASE'ssysquerymetrics with the 'metrics capture'feature, or through the MDA tables.ASE does not support automatic actions based oncaptured dataSimilar concept as ASE's Real-Time MessagingService (RTMS), which allows direct interfacing fromSQL with message bus products like Tibco and MQSeries.Packages for PL/SQL web accessOWA_CUSTOM, OWA_CX, OWA_OPT_LOCK,OWA_SEC, OWA_TEXT, OWA_UTILNo equivalent. Custom implementation in ASErequired.Oracle-to-Sybase Migration Cross-Reference 66

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3OracleSybase ASE ("major rewrite")Oracle Forms Rewrite with Sybase PowerBuilder. See section 9.2.Oracle-to-Sybase Migration Cross-Reference 67

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3CONTACT INFORMATIONFor Europe, Middle East,or Africa inquiries:+(31) 34 658 2999For Asia-Pacific inquiries:+852 2506 8900 (Hong Kong)For Latin America inquiries:+770 777 3131 (Atlanta, GA)SYBASE, INC.WORLDWIDE HEADQUARTERSONE SYBASE DRIVEDUBLIN, CA 94568-7902 USATel: 1 800 8 SYBASEwww.sybase.comCopyright © 2012 Sybase, Inc. All rights reserved. Unpublished rights reserved under U.S.copyright laws. Sybase, and the Sybase logo are trademarks of Sybase, Inc. or its subsidiaries.All other trademarks are the property of their respective owners. ® indicates registration in theUnited States. Specifications are subject to change without notice.Oracle-to-Sybase Migration Cross-Reference 68