My Oracle Support Banner

ELA: Data Conversion AE - DCRE25539514 Fails When Applying PI 25 (Doc ID 2335492.1)

Last updated on MARCH 01, 2018

Applies to:

PeopleSoft Enterprise FIN Lease Administration - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

On : 9.2 version, PI # 25.Lease Maintenance
Data Conversion AE - DCRE25539514 Fails when applying PI 25


ERROR
-----------------------

1) [Microsoft][SQL Server Native Client 11.0][SQL Server]Statement(s) could not be prepared. (SQLSTATE 37000) 8180
Failed SQL stmt: UPDATE PS_RE_LS_PPTY A SET A.EXISTING_ASSET = 'Y' WHERE A.EXISTING_ASSET = 'N' AND A.LS_KEY IN ( SELECT B.LS_KEY FROM PS_RE_LS B WHERE A.LS_KEY = B.LS_KEY AND B.LEASE_STAT (200,0)
Process 6605796 ABENDED at Step DCRE25539514.MAIN.Step24 (SQL) -- RC = 8601 (108,524)
 Message Set Number: 108
 Message Number: 524
 Message Reason: Process 6605796 ABENDED at Step DCRE25539514.MAIN.Step24 (SQL) -- RC = 8601 (108,524)
Process %s ABENDED at Step %s.%s.%s (Action %s) -- RC = %s

2) bug Bug 27254143 - EAM: DCRE25539514 PS_RE_LS_PPTY AND PODC26395949 was open for below issue but it si solved in bug 26863066 also    Error received:File: e:\pt85515b-retail\peopletools\src\psappeng\aedebug.hSQL error. Stmt #:1723 Error Position: 0 Return: 8601 - [Microsoft][ODBC Driver 13 for SQLServer][SQL Server]Incorrect syntax near 'A'.[Microsoft][ODBC Driver 13 for SQL Server][SQL Server]Statement(s) could notbe prepared. (SQLSTATE 37000) 8180Failed SQL stmt: UPDATE PS_RE_LS_PPTY A SET A.EXISTING_ASSET = 'Y' WHEREA.EXISTING_ASSET = 'N' AND A.LS_KEY IN ( SELECT B.LS_KEY FROM PS_RE_LS BWHERE A.LS_KEY = B.LS_KEY AND B.LEASE_STATUS IN ('2', '4', '5', '6', '8'))Message Set Number: 00Message Number: 0Message Reason: File:e:\pt85515b-retail\peopletools\src\psappeng\aedebug.hSQL error. Stmt #: 1723Error Position: 0 Return: 8601 - [Microsoft][ODBC Driver 13 for SQLServer][SQL Server]Incorrect syntax near 'A'.On analysis we found that the SQL statement at the AE program DCRE25539514step24) is not compatible with SQL server.Also the SQL statement at step 25 is also not compatible with SQL server.Please could you fix both the SQLs here so that they are compatible with SQLserver.



STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Applying Change Package for Image #25
2. "Running Data Conversion" in Change Assistant.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot apply Images.

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!


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.