DB.XML Contains Missing Spaces In SAVED_QUERY.db.xml When Using Carriage Returns
(Doc ID 1593542.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Transportation Management - Version 6.3.1 and laterInformation in this document applies to any platform.
Symptoms
On OTM version 6.3.1 when you create saved_queries in OTM containing 'carriage returns', and exporting using DB.XML, the carriage returns are NOT replaced by a space, which means incorrect SQLs in DB.XML.
EXPECTED BEHAVIOR
-----------------------
Expect the return character to be replaced by a space, to maintain the integrity of the SQL.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create a Saved Query in OTM via the User Interface, ensuring the SQL has several return characters.
2. Using DB.XML triggered by integration export the Saved Queries.
3. Note the files created have not replaced the return character with a space, this means when the file is uploaded to another system the SQL will not work.
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot migrate Saved Queries with custom SQL. The workaround is to put a space before all return characters in the Saved Query.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |