Current Process Diagram
DDL Generation
Problematic Data types
Running Status Report
DSS Schema and Tablespace Information
Oustanding Issues and 'Todo's'
Accomplishments
Transforming Sybase Group Privileges to Oracle Roles - An Overview
Sybase to Oracle Name Changes (excel)
Convert Tables from Sybase to Oracle
Datatype Mapping Rules for Sybase to Oracle
FIS DSS/ODS Sybase to Oracle Data Conversion
Information Regarding Diversions from Data Mapping Rules
Usage of Oracle Instances - General description
DSS1DEV - To be used by DSS team in testing scripts converted from the HP/Sybase environment to the AIX/Oracle environment. Once the DBA2DEV environment is completely reconciled the DSS developers will be dropping, recreating and repopulating tables in this environment as they test their batch scripts. The following tablespaces are ready for this use in DSS1DEV:DSS_BCR01
DSS_CA01
DSS_CA_HIST01
DSS_CG01
DSS_PS01
DSS_LD01
DSS_TR01
DBA2DEV(alias DSS2DEV) - To be used by FIS developers for testing SQRs which have been converted to work in the AIX/Oracle environment. They should not be modifying any of the data in these tables, just performing selects. This environment is in part being loaded by export/import from DSS1DEV and transportable tablespaces also from DSS1DEV. The reasoning behind this is that DSS1DEV is not a shared instance while DBA2DEV is shared. Performing loads via these Oracle methods in DBA2DEV is the safest approach. /
Current Process Diagram
/
DDL Generation
- FIS DDL is generated in Uniface. The file that results from this generation is then parsed via uniface_parser.pl before tables are created in Oracle.
- DSS DDL is generated by two different methods, one method each for ODS and DSS.
- ODS - DDL is generated by parsing the Unface generated DDL from FIS. HOWEVER, a flag must be used with this script to prevent public synonyms from being generated.
- DSS - DDL is generated from a Sybase source by running tables_s2o.pl and indexes_s2o.pl. This DDL is unique in that it incorporates a call to M. Riley's tablespace mapping function so that the tablespace name does not have to be hard coded into the DDL. Also, the index DDL is broken up into 1 DDL file per index. Instead the tablename to tablespace name mapping information is retrieved from an Oracle table, dss_tblspc_map_t.
Problematic Data types (text, image, ... )
Current Solution - Chris Shelton modified the 'data pumping' script sybase2oracle.pl to simply place NULL in columns with this data type for the time being. Bill Coulter is working on a perl process that would run after sybase2oracle.pl to fill in the data for these columns. He hopes to test this script next week (2/22 - 2/26). /
Running Status Report
February 17, 2000 /
DSS Schema and Tablespace Information
SCHEMA NAMES:DSS
DSS_CM_PY
ODS_FIS
/
Oustanding Issues and 'Todo's'
- Run reconciliation (rowcount) against DSS tables in DSS1DEV and DBA2DEV.
- Resolve data conversion problem surrounding problematic data types. Bill Coulter is working on a perl script to solve this problem.
- Meet with Terry to see step by step how loads and reconciliations are being performed
- Get current DSS load status from Terry RE: DSS1DEV and DBA2DEV.
- Discussion and testing needs to occur to see how and where we will pull data from the Sybase source for test and production.
OPTIONS:
--Perform Sybase dump from prodcution and create frozen Sybase source on SP node
--Pull data across network from Production Sybase source