When Loading Relationships Using the P6 REST API the Error "Invalid Request" Occurs or Performance Is Slow (Doc ID 3006015.1)

Last updated on FEBRUARY 23, 2024

Applies to:

Symptoms

When attempting to run a P6 REST API request to retrieve relationships, the following error occurs or performance is very slow.

CLIENT ERROR
-----------------------
Status 400

Invalid request

SERVER ERROR
-----------------------
ORA-00913: too many values


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create a request to read relationships. e.g.
{{P6_REST_HOST}}/p6ws/restapi/relationship?Filter=PredecessorProjectObjectId IN (382,383,384,394,385,395,396,401,413,415,416,433,434,417,435,436,437,438,439,440,441,442,443,444,445,446,447,448,449,450,451,452,453,454,455,456,457,458,459,460,461)
&Fields=Aref,Arls,Comments,CreateDate,CreateUser,Driving,IsPredecessorBaseline,IsSuccessorBaseline,IsSuccessorTemplate,Lag,LastUpdateDate,LastUpdateUser,ObjectId,PredActPercentCompleteType,PredActualFinishDate,PredActualStartDate,PredEarlyFinishDate,
PredEarlyStartDate,PredFreeFloat,PredLateFinishDate,PredLateStartDate,PredTotalFloat,PredecessorActivityId,PredecessorActivityName,PredecessorActivityObjectId,PredecessorActivityType,PredecessorFinishDate,PredecessorProjectId,PredecessorProjectName,
PredecessorProjectObjectId,PredecessorStartDate,PredecessorWbsName,PredecessorWbsShortName,SuccessorActivityId,SuccessorActivityName,SuccessorActivityObjectId,SuccessorActivityType,SuccessorFinishDate,SuccessorProjectId,SuccessorProjectObjectId,
SuccessorStartDate,SuccessorWbsName,Type
2. If there are a large number of values this request will fail.

Changes

Cause

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