Actian Vector (Vectorwise) Database (via JDBC) - Import - Cloud

Talend Cloud Data Catalog Bridges

author
Talend Documentation Team
EnrichVersion
Cloud
EnrichProdName
Talend Cloud
EnrichPlatform
Talend Data Catalog

Note: This bridge is not available in Talend Cloud Data Catalog by default. You need to set up a remote harvesting agent to import metadata from this source. For more information, see Deploying a remote harvesting agent in Talend Cloud Data Catalog Administration guide.

Bridge Specifications

Vendor Actian
Tool Name Vector (Vectorwise) Database
Tool Version 4.2 and 5.0
Tool Web Site http://esd.actian.com/product/Vector/
Supported Methodology [Relational Database] Multi-Model, Data Store (Physical Data Model) via JDBC API
Incremental Harvesting
Multi-Model Harvesting
Remote Repository Browsing for Model Selection
Data Profiling

SPECIFICATIONS
Tool: Actian / Vector (Vectorwise) Database version 4.2 and 5.0 via JDBC API
See http://esd.actian.com/product/Vector/
Metadata: [Relational Database] Multi-Model, Data Store (Physical Data Model)
Component: JdbcActianVectorwise version 11.0.0

OVERVIEW
This bridge uses a JDBC connection to a database server to extract all its metadata (e.g. Schemas, Tables, Columns, Data Types.) and parse any SQL (e.g. Views, Stored Procedures)to produce the data flow lineage.

WARNING
The JDBC driver used by this bridge have limited implementation to extract advanced metadata such as Synonyms, View dependencies, Candidate keys, Stored Procedures, etc. In such case, more advanced queries have to be made to the proprietary system tables, which are specific to each database. Furthermore, such queries have to be performed using the native drivers provided by each database vendor.

This generic JDBC database bridge has only been tested with Oracle, IBM DB2 (DB/2 UDP databases only), Microsoft SQL Server, Sybase and Teradata, (and again provide less metadata than the specific database bridges), and no claims are made for metadata access when using this bridge with any other database.
Therefore, we recommend using the dedicated database import bridges to access metadata from Oracle, IBM DB2 (DB/2 UDP databases), Microsoft SQL Server, Sybase and Teradata.

REQUIREMENTS
See the Driver Location parameter for any JDBC driver requirements.
See the User parameter for any user permission requirements.

Driver details:
- you may use any JDBC driver that supports JDBC 4.0
- driver JARs location: ${MODEL_bridge_home}/java/Jdbc/generic

FREQUENTLY ASKED QUESTIONS
Q: How does this bridge load the JDBC driver I want to use?
A: The directory or jar file pathname must be set in the 'Driver path' bridge parameter or in the system CLASSPATH environment variable before starting this bridge.

Q: Does my driver require any java security permissions in order to run?
A: Some drivers do require additional security permissions to be granted at runtime. You can grant additional permissions to the driver by editing the 'java.policy' file as below:
grant codeBase 'file:/C:/oracle/ora9/jdbc/lib/classes12.zip' {
permission java.security.AllPermission;
};
Please read your driver documentation for details.
This 'java.policy' file needs to be created in the same directory as the executable, usually ''${MODEL_BRIDGE_HOME}/java'

LIMITATIONS
Refer to the current general known limitations at http://metaintegration.com/Products/MIMB/MIMBKnownLimitations.html or bundled in Documentation/ReadMe/MIMBKnownLimitations.html

SUPPORT
Provide a trouble shooting package with:
- the debug log (can be set in the UI or in conf/conf.properties with MIR_LOG_LEVEL=6)
- the metadata backup if available (can be set in the Miscellaneous parameter with option -backup)


Bridge Parameters

Parameter Name Description Type Values Default Scope
Driver location The JDBC driver folder location where all found JAR files will be added to the CLASSPATH.
The Generic JDBC driver default location is: ${MODEL_BRIDGE_HOME}/java/Jdbc/generic

JDBC DRIVER DETAILS
- you may use any JDBC driver that supports JDBC 4.0
- driver JARs location: ${MODEL_bridge_home}/java/Jdbc/generic
DIRECTORY      
Driver class The full name (including the package name) of the java class that implements the JDBC Driver interface.

This value is database and driver dependent, e.g.

'IBM DB2'
com.ibm.db2.jcc.DB2Driver

'IBM Netezza'
org.netezza.Driver

'Microsoft Access'
sun.jdbc.odbc.JdbcOdbcDriver

'Microsoft SQL Server'
com.microsoft.sqlserver.jdbc.SQLServerDriver

'Oracle 7'
oracle.jdbc.driver.OracleDriver

'Oracle 8 Thin'
oracle.jdbc.driver.OracleDriver

'PostgreSQL'
org.postgresql.Driver

'SAP Sybase'
com.sybase.jdbc3.jdbc.SybDriver

'Teradata'
sun.jdbc.odbc.JdbcOdbcDriver, or com.teradata.jdbc.TeraDriver if you are intending to import views
STRING   sun.jdbc.odbc.JdbcOdbcDriver Mandatory
URL The URL / fully qualified JDBC connection string used by JDBC to connect to the database server, e.g.
jdbc:URLSubProtocol:URLSubName

This value is database and driver dependent, e.g.

'IBM DB2 8.1 Net'
jdbc:db2://COMPUTER_NAME_OR_IP:PORT/DATABASE_NAME

'IBM DB2 8.1 App'
jdbc:db2:DATABASE_NAME

'IBM Netezza'
jdbc:netezza://COMPUTER_NAME_OR_IP:PORT/DBname

'IBM Informix 12.10.xC3 and earlier'
jdbc:informix-sqli://COMPUTER_NAME_OR_IP:PORT/DATABASE_NAME:INFORMIXSERVER=DATABASE_SERVER

'IBM Informix'
jdbc:informix-sqli://COMPUTER_NAME_OR_IP:PORT/DATABASE_NAME

'Microsoft Access'
jdbc:odbc:YOUR_DSN

'Microsoft SQL Server'
jdbc:sqlserver://COMPUTER_NAME_OR_IP:PORT

'MySQL'
jdbc:mysql://COMPUTER_NAME_OR_IP/DATABASE_NAME

'Oracle 7 Thin'
jdbc:oracle:thin:@COMPUTER_NAME_OR_IP:PORT:ORACLE_SID

'Oracle 8 Thin'
jdbc:oracle:thin:@(description=(address=(host=DATABASE_HOST)(protocol=tcp)(port=1521))(connect_data=(sid=SID)))

'PostgreSQL'
jdbc:postgresql://COMPUTER_NAME_OR_IP:PORT/DATABASE_NAME

'SAP Hana'
jdbc:sap://COMPUTER_NAME_OR_IP:DATABASE_TUNNEL_PORT/?autocommit=false

'SAP SyBase'
jdbc:sybase:Tds:COMPUTER_NAME_OR_IP:PORT

'Teradata'
jdbc:odbc:YOUR_DSN, or when using the TeraDriver
jdbc:teradata://COMPUTER_NAME_OR_IP/TMODE=ANSI,CHARSET=UTF8 (for native java driver)
STRING   jdbc:[jdbc-prefix]:COMPUTER_NAME_OR_IP:PORT/DATABASE_NAME Mandatory
User The user name used by JDBC to connect to the database server.
This parameter is ignored if the Host parameter is based on a fully qualified JDBC connection string that includes the user name.

USER PERMISSIONS
As with any other bridges, this bridge is warranted to be read only and only extracts metadata. Therefore the user of this bridge requires much less permissions than classic users needing to read/write data.

However, this bridge needs a user with (read only) access to system tables in order to access advanced metadata such as the SQL of views or stored procedures which are not implemented in the metadata portion of the JDBC driver, therefore the Database Administrator (DBA) needs to be involved in order get the proper user with enough permissions.

Note that there are no specific instructions as to what are the minimal set of permissions required as it varies from different database types and versions. In order to ensure that this bridge is working properly, one must first import using this bridge with a FULL Sys Admin type username (all permissions), i.e., the same type of username that is used to create and maintain the DB. Once this bridge is working properly against a given DB, then the DBA may create a user with lesser privileges that still produce a successful result.

USER IS OPTIONAL
The user parameter is optional as:

- no user credentials are needed:
for some databases such as Microsoft Access.
- the user credentials may be embedded the Host parameter:
for some databases such as Oracle and Microsoft SQL Server.

- the user credentials may be part of an integrity security:
for Microsoft SQL Server, see http://msdn.microsoft.com/en-us/library/ms378428.aspx#Connectingintegrated
In this case, this bridge will attempt to connect with this type of signature:
- with : jdbc:sqlserver://; integratedSecurity=true
- instead of: jdbc:sqlserver://; user=userid;password=userpassword
However, in order for this to work, the user must have the sqljdbc_auth.dll available on the PATH environment variable. Also the version of the library must match the version of the sqljdbc4.jar that they are using.
STRING      
Password The user password used by JDBC to connect to the database server. PASSWORD      
Catalog The name of the database catalog to import.

If left empty, this bridge will import only the first catalog found.

This parameter will be ignored for JDBC/ODBC sources which do not support database catalogs.
STRING      
Schema The subset of schemas to import expressed as a semicolon separated list of schemas, e.g.
schema1; schema2

All user schemas are imported if that list is empty.

All system schemas (e.g. SysAdmin) and objects are ignored by default. If system schemas are needed, use the Miscellaneous parameter option -s.

Schema name patterns using a SQL like expression syntax:

- Inclusion syntax:
using '%, e.g.
A%; %B; %C%; D
- start with A or
- end with B or
- contain C or
- equal D

- Exclusion syntax:
using 'NOT", e.g.
A%; %B; NOT %SYS; NOT 'SYS%'
- where (name like A% or name like %B)
- and (name NOT like %SYS)
- and (name NOT like 'SYS%')

- Special characters:
using single quote, e.g.
OneWord%; 'Two Words%'
STRING      
Tables, Views The subset of tables to import expressed as a semicolon separated list of tables, e.g.
table1; table2

All user tables are imported if that list is empty.

All system tables (e.g. SysAdmin) and objects are ignored by default. If system tables are needed, use the Miscellaneous parameter option -s.

Table name patterns using a SQL like expression syntax:

- Inclusion syntax:
using '%, e.g.
A%; %B; %C%; D
- start with A or
- end with B or
- contain C or
- equal D

- Exclusion syntax:
using 'NOT", e.g.
A%; %B; NOT %SYS; NOT 'SYS%'
- where (name like A% or name like %B)
- and (name NOT like %SYS)
- and (name NOT like 'SYS%')

- Special characters:
using single quote, e.g.
OneWord%; 'Two Words%'
STRING      
Case sensitivity Controls the database case sensitivity on names spaces (tables, views, tables, columns, stored procedures):

'Auto'
This bridge will try to use the JDBC API to find out if the database is set into the case sensitive mode.
If that API call is not implemented by the JDBC driver this bridge assumes the database is Case Insensitive.

'Case Sensitive'
Force case sensitive

'Case Insensitive
Force case insensitive
ENUMERATED
Auto
Case Sensitive
Case Insensitive
Auto  
View definition extracting SQL The database specific SQL query to retrieve the view definition.
If it is left empty, no relationships between views and their source tables will be built.
This query expects the first parameter to be the view name and, optionally, the second parameter to be the schema name.
Actual query text varies depending on the source database, e.g.

'IBM DB2 UDB'
SELECT CREATOR, NAME, TEXT FROM SYSIBM.SYSVIEWS WHERE CREATOR IN (?)

'IBM DB2 AS400'
SELECT TABLE_SCHEMA, TABLE_NAME, VIEW_DEFINITION FROM QSYS2.SYSVIEWS WHERE TABLE_SCHEMA IN (?)

'IBM Netezza'
SELECT CURRENT_SCHEMA, VIEWNAME, DEFINITION FROM _V_VIEW WHERE OBJTYPE='VIEW'

'Microsoft SQL Server':
SELECT s.name, o.name, t.definition FROM sys.sql_modules t INNER JOIN sys.objects o ON (t.object_id=o.object_id) INNER JOIN sys.schemas s ON (o.schema_id=s.schema_id) WHERE o.type IN ('V') AND s.name IN (?)

'MySQL'
SELECT '',TABLE_NAME,VIEW_DEFINITION FROM INFORMATION_SCHEMA.VIEWS

'Oracle'
SELECT OWNER, VIEW_NAME, TEXT FROM ALL_VIEWS WHERE OWNER IN (?)

'PostgreSQL'
SELECT schemaname, viewname, definition FROM pg_views WHERE schemaname IN (?)

'SAP Hana'
SELECT SCHEMA_NAME, VIEW_NAME, DEFINITION FROM VIEWS

'Teradata'
SELECT d.DatabaseName, m.TVMName, CASE WHEN m.CreateText IS NULL THEN m.RequestText ELSE m.CreateText END FROM DBC.TVM m INNER JOIN dbc.dbase d ON(m.DatabaseId=d.DatabaseId) WHERE m.TableKind IN('V') AND d.DatabaseName IN (?)
STRING      
Synonyms lineage SQL The database specific SQL query to retrieve synonym.
This query must returns two columns: full synonym name and full table name.
The Full Name must contains schema name and table name
Actual query text varies depending on the source database, e.g.

'IBM DB2'
Not supported.

'Microsoft SQL Server'
SELECT s.name, a.name, null, a.base_object_name FROM sys.schemas AS s, sys.synonyms AS a WHERE s.schema_id = a.schema_id
- Result is a result set with two columns in format:
Schema.Synonym; Catalog.Schema.Table ;

'MySQL'
Not supported.

'Oracle'
SELECT OWNER, SYNONYM_NAME, TABLE_OWNER, TABLE_NAME FROM SYS.DBA_SYNONYMS [WHERE OWNER='SCOTT']
- Please, note the query text included in '[' and ']' is optional.
- Result is a result set with two columns in format:
Schema.Synonym; Schema.Table ;

'SAP HANA'
SELECT SCHEMA_NAME, SYNONYM_NAME, OBJECT_SCHEMA, OBJECT_NAME FROM SYNONYMS

'Teradata'
Not supported.
STRING      
Import indexes Controls the import of Indexes:

'False'
Indexes are not imported

'True'
Indexes are imported
BOOLEAN
False
True
False  
Stored procedure details Controls the amount of details imported from stored procedures:

'Signature'
The name and parameters of stored procedures

'Code, signature'
The above plus code

'Lineage, code, signature'
The above plus data lineage derived from the code

'None'
stored procedure details are not included.
ENUMERATED
None
Signature
Code, signature
Lineage, code, signature
Signature  
Procedures text SQL Database specific SQL query to retrieve stored procedures text. This query must returns two columns: full synonym name and full table name.
The Full Name must contains schema name and table name
Actual query text varies depending on the source database.

'IBM DB2'
SELECT procschema, procname, text FROM syscat.procedures WHERE procschema IN (?) UNION ALL SELECT FUNCSCHEMA, FUNCNAME, BODY FROM syscat.functions WHERE FUNCSCHEMA IN (?)
- Result is a result set with three columns in format:
Schema; Procedure; Code;

'Microsoft SQL Server'
SELECT s.name, o.name, t.definition FROM sys.sql_modules t INNER JOIN sys.objects o ON (t.object_id=o.object_id) INNER JOIN sys.schemas s ON (o.schema_id=s.schema_id) WHERE o.type IN ('TF','P','FN','IF') AND s.name IN (?)
- Result is a result set with three columns in format:
Schema; Procedure; Code;

'MySQL'
SELECT '', ROUTINE_NAME, ROUTINE_DEFINITION FROM INFORMATION_SCHEMA.ROUTINES

'Oracle'
SELECT s.owner, s.name, s.text FROM sys.dba_source s INNER JOIN sys.dba_procedures p ON (p.owner=s.owner AND p.object_name=s.name AND p.object_type=s.type) WHERE s.type IN ('PROCEDURE', 'FUNCTION') AND s.owner IN (?) ORDER BY s.name, s.line
- Result is a result set with three columns in format:
Schema; Procedure; Code;

'SAP HANA'
SELECT SCHEMA_NAME, PROCEDURE_NAME, DEFINITION FROM PROCEDURES

'Teradata'
Not supported.
STRING      
Miscellaneous
INTRODUCTION
Specify miscellaneous options starting with a dash and optionally followed by parameters, e.g.
-connection.cast MyDatabase1="SQL Server"
Some options can be used multiple times if applicable, e.g.
-connection.rename NewConnection1=OldConnection1 -connection.rename NewConnection2=OldConnection2;
As the list of options can become a long string, it is possible to load it from a file which must be located in ${MODEL_BRIDGE_HOME}\data\MIMB\parameters and have the extension .txt. In such case, all options must be defined within that file as the only value of this parameter, e.g.
ETL/Miscellaneous.txt

JAVA ENVIRONMENT OPTIONS
-java.memory <Java Memory's maximum size> (previously -m)
1G by default on 64bits JRE or as set in conf/conf.properties, e.g.
-java.memory 8G
-java.memory 8000M

-java.parameters <Java Runtime Environment command line options> (previously-j)
This option must be the last one in the Miscellaneous parameter as all the text after -java.parameters is passed "as is" to the JRE, e.g.
-java.parameters -Dname=value -Xms1G
The following option must be set when a proxy is used to access internet (this is critical to access https://repo.maven.apache.org/maven2/ (and exceptionally a few other tool sites) in order to download the necessary third party software libraries.
-java.parameters -Dhttp.proxyHost=127.0.0.1 -Dhttp.proxyPort=3128 -Dhttps.proxyHost=127.0.0.1 -Dhttps.proxyPort=3128 -Dhttp.proxyUser=user -Dhttp.proxyPassword=pass -Dhttps.proxyUser=user -Dhttps.proxyPassword=pass

-java.executable <Java Runtime Environment full path name> (previously -jre)
It can be an absolute path to javaw.exe on Windows or a link/script path on Linux, e.g.
-java.executable "c:\Program Files\Java\jre1.8.0_211\bin\javaw.exe"

-environment.variable <Environment variable value> (previously -v)
None by default, e.g.
-environment.variable var1=value1 -environment.variable var2="value2 with spaces"

MODEL IMPORT OPTIONS
-model.name <model name>
Override the model name, e.g.
-model.name "My Model Name"

-prescript <script name>
The script must be located in the bin directory, and have .bat or .sh extension.
The script path must not include any parent directory symbol (..).
The script should return exit code 0 to indicate success, or another value to indicate failure.
For example:
-prescript "script.bat arg1 arg2"

-cache.clear
Clears the cache before the import, and therefore will run a full import without incremental harvesting.
Warning: this is a system option managed by the application calling the bridge and should not be set by users.

-backup <directory>
Full path of an empty directory to save the metadata input files for further troubleshooting.

DATA CONNECTION OPTIONS
Data Connections are produced by the import bridges typically from ETL/DI and BI tools to refer to the source and target data stores they use. These data connections are then used by metadata management tools to connect them (metadata stitching) to their actual data stores (e.g. databases, file system, etc.) in order to produce the full end to end data flow lineage and impact analysis. The name of each data connection is unique by import model. The data connection names used within DI/BI design tools are used when possible, otherwise connection names are generated to be short but meaningful such as the database / schema name, the file system path, or Uniform Resource Identifier (URI). The following options allows to manipulate connections. These options replaces the legacy options -c, -cd, and -cs.

-connection.cast ConnectionName=ConnectionType
Casts a generic database connection (e.g. ODBC/JDBC) to a precise database type (e.g. ORACLE) for SQL Parsing, e.g.
-connection.cast "My Database"="SQL SERVER".
The list of supported data store connection types includes:
ACCESS
CASSANDRA
DB2
DENODO
HIVE
MYSQL
NETEZZA
ORACLE
POSTGRESQL
PRESTO
REDSHIFT
SALESFORCE
SAP HANA
SNOWFLAKE
SQL SERVER
SYBASE
TERADATA
VECTORWISE
VERTICA

-connection.rename OldConnection=NewConnection
Renames an existing connection to a new name, e.g.
-connection.rename OldConnectionName=NewConnectionName
Multiple existing database connections can be renamed and merged into one new database connection, e.g.
-connection.rename MySchema1=MyDatabase -connection.rename MySchema2=MyDatabase

-connection.split oldConnection.Schema1=newConnection
Splits a database connection into one or multiple database connections.
A single database connection can be split into one connection per schema, e.g.
-connection.split MyDatabase
All database connections can be split into one connection per schema, e.g.
-connection.split *
A database connection can be explicitly split creating a new database connection by appending a schema name to a database, e.g.
-connection.split MyDatabase.schema1=MySchema1

-connection.map DestinationPath=SourcePath
Maps a source path to destination path. This is useful for file system connections when different paths points to the same object (directory or file).
On Hadoop, a process can write into a CSV file specified with the HDFS full path, but another process reads from a HIVE table implemented (external) by the same file specified using a relative path with default file name and extension, e.g.
-connection.map hdfs://host:8020/users/user1/folder/file.csv=/user1/folder
On Linux, a given directory (or file) like /data can be referred to by multiple symbolic links like /users/john and /users/paul, e.g.
-connection.map /users/John=/data -connection.map /users/paul=/data
On Windows, a given directory like C:\data can be referred to by multiple network drives like M: and N:, e.g.
-connection.map M:\=C:\data -connection.map N:\=C:\data

JDBC OPTIONS
-f <number of rows>
The database driver fetch size in number of rows. E.g.
-f 100

-s
Import system objects that are skipped by default.

-synonyms
Disable import of all synonyms.

-server.name <database identification name>

In a multitenant container database (CDB), the metadata for data dictionary tables and view definitions is stored only in the root. However, each pluggable database (PDB) has its own set of data dictionary tables and views for the database objects contained in the PDB.

It is possible that some dba_ views are not available because they are not applicable. In a PDB you cannot have external locations, because they would not be moved when the PDB is moved.

-multiModel
Imports a data store as a multi model (e.g. a database as one schema per model).
Warning: this is a system option managed by the application calling this bridge and should not be set by users.

-tt <string>
Set the JDBC table types to import. It helps when the database driver does not support some tables types like EXTERNAL_TABLE. E.g.
-tt TABLE;VIEW
STRING      

 

Bridge Mapping

Meta Integration Repository (MIR)
Metamodel
(based on the OMG CWM standard)
"Actian Vector (Vectorwise) Database (via JDBC)"
Metamodel
Jdbc
Mapping Comments
     
Name Name  
Attribute Table Column  
Comment Comments on the column If JDBC driver supports
InitialValue Default value  
Name Name  
Optional Based on the nullable property For Access databases, set to false only if the attribute is in a Unique Index
PhysicalName Name  
Position Position If position is not provided, the order in which the attributes are retrieved is used.
BaseType Types  
DataType Data Type See datatype conversion array
Length Size  
Name   The name is computed from the datatype
PhysicalName Name  
Scale Maximum scale  
Class Table of type "TABLE"
Comment Comments on the table If JDBC driver supports
CppClassType   Set to ENTITY
CppPersistent   Set to True
Name Name  
PhysicalName Name  
ClassDiagram Schema A class diagram is created for each package and contains all the elements of the package
DerivedType Column Table column, stored procedure column SQL View column or type
DataType Data Type See datatype conversion array
Length Size  
Name   The name is computed from the datatype
PhysicalName Name  
Scale Decimal digits  
UserDefined   True for Type
DesignPackage Schema A Package is created for each retrieved schema. If there is no schema a default package is created.
Name Name Set to "Schema" if there is no schema or the schema has no name.
SQLViewAttribute View Column  
Comment Comments on the column If JDBC driver supports
Name Name  
PhysicalName Name  
Position Ordinal position  
SQLViewEntity Table of type "VIEW"
Comment Comments on the table If JDBC driver supports
Name Name  
PhysicalName Name  
StoreModel Catalog The model is built using the elements contained in the catalog (e.g. the database for MS SQL server)
Name Name Set to "Catalog" if the catalog has no name.
Synonym Table Synonym If JDBC driver supports
Name Name