This topic shows you how to specify case-sensitive names in the configuration file, for example when specifying table names or if you need to specify column names explicitly in a column mapping.
If the owner or name of an object is case-sensitive in the database, you must enclose that name within quotes in the SharePlex configuration file.
Important: This applies whether the database itself requires a case-sensitive name to be within quotes, such as Oracle, or whether the database accepts names that are spelled out in their case-sensitive form without quotes, like SQL Server.
To enforce case-sensitive object names
Specify the name in its correct case and enclose it within double quotes.
This is how to specify an object where both the owner and object names are both case-sensitive:
"Owner"."Object"
This is how to specify an object where only one of the components is case-sensitive:
owner."Object" or "Owner".object
The name that is not case-sensitive can be specified in any case.
Examples of both ways:
Datasource o.oraA |
|
|
sales."Emp" |
"Sales"."Emp" |
sysB@o.oraB |
This is not correct, because both components are within one set of quotes:
"Sales.Employees"
Ordinarily, column names are not specified in the configuration file, unless source column names need to be mapped to different target column names by means of a column mapping (see Map source and target columns). However, if the names of any pair of source and target columns have difference cases, you may need to include them in a column mapping to enforce their case sensitivity. Whether or not a column mapping is required depends on the target type: Oracle or Open Target.
To enforce case-sensitive column names to Oracle targets
The Oracle Post process does not perform case conversion of column names automatically. If the case is different between source and target columns, you must use a column map to map the case of the source names to the case of the target names. To get Post to enforce the case, specify the name in its correct case and enclose it within double quotes.
This is an example of case-sensitive column name mapping in a column map:
Datasource o.oraA |
|
|
sales.emp(ID,"first","last") |
sales.emp(ID,"First","Last") |
sysB@o.oraB |
To enforce case-sensitive column names to Open Target
The Open Target Post process performs case conversion of column names automatically. If replicating to target columns that have a different case from their source columns, no column mapping is needed.
© ALL RIGHTS RESERVED. 이용 약관 개인정보 보호정책 Cookie Preference Center