|
Problem IC87047
|
Status: Closed |
DB2LOOK DOES NOT WRAP THE SOURCE FUNCTIONS WITH QUOTATION MARKS WHEN GENERATES STATEMENTS FOR SOURCED FUNCTIONS |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
When db2look generates statements for sourced functions, db2look
does not wrap the schema and name of the source functions with
quotation marks. The execution of the script generated by
db2look fails with SQL0104N if the source function name contains
special characters like '+', '-', etc.
For example, db2look may generate statement for a sourced
function like below
CREATE OR REPLACE FUNCTION "SCHEMA1"."+"
(
"SCHEMA1"."INTERVAL_YEAR_TO_MONTH",
"SCHEMA1"."INTERVAL_YEAR_TO_MONTH"
)
RETURNS "SCHEMA1"."INTERVAL_YEAR_TO_MONTH"
SPECIFIC SQL120925021552703
SOURCE SYSIBM.+
(SYSIBM.DECFLOAT,SYSIBM.DECFLOAT)
In the output, the "SYSIBM.+" should be wrapped as
""SYSIBM"."+"". |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* all *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* upgrade to DB2 v10.1 fp3. *
**************************************************************** |
| Local Fix: |
Wrap the schema and name of the source function with quotation
marks, then execute the script. |
| available fix packs: |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
Fixed in DB2 v10.1 fp3. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC95504
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 08.10.2012
22.10.2013
22.10.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
