Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Regexp_replace function fails in Connect-SQL



A Connect-SQL record browse operation fails with a lexical error after upgrade from Oracle 11R2, to Oracle 12C. The Oracle upgrade required a change from the Translate function to 'regexp_replace' function calls. Now a SQL query with the updated syntax fails to execute.

Error Messages

Caused by: Lexical error at line 1, column 183. Encountered: "1" (49), after : "\\" 

Steps to Reproduce

Example SQL:

regexp_replace(listagg( to_char(REQUIREDRENEWALDATE,'mm/dd/yyyy'),',') within group (order by to_char(REQUIREDRENEWALDATE,'mm/dd/yyyy')),'([^,]+)(,\1)+', '\1') as REQUIREDRENEWALDATE
. . .

Root Cause

There was a syntax error in the SQL statement: Backslash character in the function parameters is not parsed properly as it is not preceded by an escape character.


Perform the following local-change: Change occurrences of '\1' in the query to '\\1'. The backslash is a necessary escape character. 

Published March 18, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us