Specifying Case-Sensitive Database Object Names
Oracle GoldenGate supports case-sensitive names. Follow these rules when specifying case-sensitive objects.
-
Specify object names from a case-sensitive database in the same case that is used to store them in the host database. Keep in mind that, in some database types, different levels of the database can have different case-sensitivity, such as case-sensitive schema but case-insensitive table. If the database requires quotes to enforce case-sensitivity, put quotes around each object that is case-sensitive in the qualified name.
Correct:
TABLE "Sales"."ACCOUNT"
Incorrect:
TABLE "Sales.ACCOUNT"
-
Oracle GoldenGate converts case-insensitive names to the case in which they are stored when required for mapping purposes.
Table 8-10 provides an overview of the support for case-sensitivity in object names, per supported database. Refer to the database documentation for details on this type of support.
Table 8-10 Case Sensitivity of Object Names Per Database
Database | Requires quotes to enforce case-sensitivity? | Unquoted object name | Quoted object name |
---|---|---|---|
DB2 |
Yes. Differentiates between case-sensitive and case-insensitive by use of quotes. |
Case-insensitive, stores in upper case |
Case-sensitive, stores in mixed case |
MySQL (Case-sensitive database) |
No
|
No effect |
No effect |
Oracle Database |
Yes. Differentiates between case-sensitive and case-insensitive by use of quotes. |
Case-insensitive, stores in upper case |
Case-sensitive, stores in mixed case |
SQL Server (Database created as case-sensitive) |
No Always case-sensitive, stores in mixed case |
No effect |
No effect |
SQL Server (Database created as case-insensitive) |
No Always case-insensitive, stores in mixed case |
No effect |
No effect |
Teradata |
No Always case-insensitive, stores in mixed case |
No effect |
No effect |
Note:
For all supported databases, passwords are always treated as case-sensitive regardless of whether the associated object name is quoted or unquoted.