KSC Copy Request is not allowing Name field with apostrophe (') (155 Views)
Reply
Respected Contributor
Niraj Prabhu
Posts: 240
Registered: ‎03-28-2008
Message 1 of 2 (155 Views)

KSC Copy Request is not allowing Name field with apostrophe (')

Hi,

We are on PPM 9.14.0009 and are facing issue while creating request using KSC Copy Request which gives following error,

Beginning command: KSC Copy Request
Running PL/SQL procedure KCRT_REQUEST_UTIL.COPY_REQUEST
Summary of parameters:
FROM_REQUEST_ID=109448
REQUEST_TYPE_ID=30683
WORKFLOW_ID=33904
COPY_FIELDS=Y
COPY_NOTES=N
CREATE_REFERENCE=Y
REF_RELATIONSHIP_ID=15
STATUS_NAME=Not Submitted
SUBMIT=Y
PROCESS_RULE=N
USER_ID=32971
VALIDATION_NAME=
Exception occured during execution: ORA-20000: Request(109600) import failed with ORA-00917: missing comma {KCRT_CREATE_FS_SHELL_INT-10340}
ORA-06512: at "AQC0001.KCRT_REQUEST_UTIL", line 2342
ORA-06512: at line 1

On further investigation, I found that the name field has an apostrophe (') causing this error.

Support case engineer told me about having some fix in 9.2 version. Here’s the link for that documentation

https://support.openview.hp.com/selfsolve/document/FID/DOCUMENTUM_QCCR1L49735

 

But do you have any hot fix for this issue as we are currently on PPM 9.14.

Regards,
Niraj

Niraj P.
Please use plain text.
Honored Contributor
Jim Esler
Posts: 715
Registered: ‎05-09-2008
Message 2 of 2 (135 Views)

Re: KSC Copy Request is not allowing Name field with apostrophe (')

Since you are getting an Oracle error because of an apostrophe, it is reasonable to assume the data is being passed directly to Oracle and the apostrophe is being treated as a string delimiter instead of as the apostrophe character itself. Oracle uses the convention that two consecutive apostrophes (not to be confused with a quote (") character) is to be processed as a single apostrophe character instead of as string delimiters. Try specifying the validation name as Validation''Name instead of Validation'Name.

Please use plain text.
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation