File Archive Loader Datatype Conversions (Version 5.3.4)

Transcription

1 File Archive Loader Datatype Conversions (Version 5.3.4) 2011 Informatica

2 Abstract When you archive to a file, the File Archive Loader converts datatypes between the source database and the File Archive Service. In some cases, the datatype conversion does not occur and manual intervention is required. This document describes the datatype conversions and how to resolve conversion problems. Note: Effective in version HotFix 1, the documentation changed. For more information, see the Data Archive User Guide. Supported Versions ILM Data Archive Table of Contents Overview Source Datatype Conversions Datatype Conversion Errors Manual Datatype Conversions Converting Datatypes for Parse Errors Converting Datatypes for Conversion Warnings Known Limitations Overview The File Archive Loader converts datatypes between the source database and the File Archive Service. If the source datatype is not supported in File Archive Service, then the File Archive Loader converts the datatype to a generic datatype. In some cases, the automatic datatype conversion does not occur and manual intervention is required. You must manually convert the datatypes if the log file includes parse errors or conversion warnings. Source Datatype Conversions When you archive to a file, the Data Archive project includes the File Archive Loader job. One of the tasks that the File Archive Loader job performs is the datatype conversion between the source database and the File Archive Service. The File Archive Loader can convert datatypes from Oracle, Microsoft SQL Server, IBM DB2 UDB, and Teradata databases. The following table describes the conversion between the source datatypes and the File Archive Service datatypes: Source Datatype BIGINT NUMERIC (120,40) BINARY ( ) BIT (10) BLOB ( ) BYTE ( ) 2

3 Source Datatype BYTEINT NUMERIC (120,40) ACTER CLOB ( ) DATE DATETIME DATETIME2 DATETIMEOFFSET (34) DBLOB ( ) DECIMAL DECIMAL DOUBLE NUMERIC (120,40) DOUBLE PRECISION NUMERIC (120,40) FLOAT NUMERIC (120,40) GRAPHIC ( ) IMAGE ( ) INT NUMERIC (120,40) INTEGER NUMERIC (120,40) INTERVAL (100) LONG ( ) LONG (32700) LONG RAW ( ) LONG LONG VARGRAPHIC ( ) MONEY NUMERIC (120,40) N NCLOB ( ) NTEXT ( ) 3

4 Source Datatype NUMBER NUMERIC (120,40) NUMBER (p,s) NUMERIC (p,s) N N2 NUMERIC (p,s) NUMERIC (p,s) RAW ( ) REAL NUMERIC (120,40) ROWID (100) SMALLDATETIME SMALLINT NUMERIC (120,40) SMALLMONEY NUMERIC (120,40) SQL_VARIANT (100) TEXT ( ) TIME (100) TIME WITH TIMEZONE (100) (All databases except for Microsoft SQL Server) (Microsoft SQL Server) (100) (6) (Oracle) TINYINT NUMERIC (120,40) UNIQUEIDENTIFIER (100) VARBINARY ( ) (max) ( ) 2 VARGRAPHIC ( ) XML ( ) 4

5 Datatype Conversion Errors The File Archive Loader may not always convert datatypes automatically. The File Archive Loader may not be able to find a generic datatype to convert when it creates objects on the File Archive Service. Or, the File Archive Loader may have conversion errors or warnings when it loads numeric data to the File Archive Service. In either case, you must convert the datatypes manually. Convert the datatypes if you receive a parse error or a conversion warning in the log file. Parse Error If the File Archive Loader processes an unsupported datatype and is not able to identify a generic datatype, you receive the following parse error in the log file: Parse error (line <line number>)> no viable alternative: [( SORT )?] For example: Conversion Warning Parse error (line 5449)> no viable alternative: [( SORT )?] If the File Archive Loader loads columns that have large numeric data, you receive the following conversion warning in the log file: WARNING: Warnings occurred during conversion of value <numeric value> on line <line number> for field <column name>. For example: WARNING: Warnings occurred during conversion of value on line 78 for field EXCHANGE_RATE. Manual Datatype Conversions There are several datatypes that the File Archive Loader cannot convert automatically. The following table describes datatypes that require manual conversions and the corresponding supported File Archive Service datatype: Source Database Source Datatype Oracle Microsoft SQL Server FLOATING NUMBER and NUMBER (no precision and scale) DATETIME2 File Archive Service supports maximum NUMERIC (120,40) or DOUBLE, which supports maximum of 15 significant digits. If the source column contains fixed and floating datatypes up to 15 significant digits, change to DOUBLE. If the source column contains fixed and floating datatypes that exceed 15 significant digits, change to. Change to DATETIME. Microsoft SQL Server DATETIMEOFFSET Change to. Microsoft SQL Server XML Change to CLOB. IBM DB2 DBLOB Change to CLOB. IBM DB2 GRAPHIC Change to CLOB. 5

6 Source Database Source Datatype IBM DB2 LONG VARGRAPHIC Change to CLOB. IBM DB2 VARGRAPHIC Change to CLOB. Converting Datatypes for Parse Errors Manually convert datatypes to resolve the parse error in the File Archive Loader log file. Use the parse error description to find the corresponding datatype that you need to convert. Then, change the datatype in the metadata xml file that the ILM engine generates when you run the Data Archive job. After you convert the datatype, resume the File Archive Loader job. 1. Access the log file. 2. Search the log for the parse error and find the corresponding line number that has the exception. 3. Access the metadata xml file that the ILM engine generated. You can find the file in the following location: bcp/<jobid_arc>/metadata.ddl 4. Navigate to the line that the parse error references. 5. Change the datatype to a supported File Archive Service datatype. 6. Resume the File Archive Loader job. Converting Datatypes for Conversion Warnings Manually convert datatypes to resolve the conversion warning in the File Archive Loader log file. To resolve the warning, change the datatype to either the DOUBLE or datatypes. The number conversion warning only occurs for Oracle NUMBER datatypes that do not have precision or scale. Oracle NUMBER datatype supports fixed and floating decimals up to 38 digits of precision. The default numeric File Archive Service datatype is NUMERIC (120, 40). The File Archive Service DOUBLE datatype supports up to 15 significant digits. If the source column contains up to 15 significant digits, then change the datatype to DOUBLE. Otherwise, change to. 1. Access the alter_table_column script in the following location: <Data Archive installation directory>/webapp/debug 2. Alter the script to include the server name for the File Archive Service. 3. Run the script. 4. Resume the File Archive Loader job. Known Limitations For the datatype, the File Archive Service truncates milliseconds up to three digits. The CR for this known limitation is Authors Jennifer Posivak Contract Technical Writer Rahul Gupta Senior Development Manager 6