After creating a document object in Plant it showing up very slowly

Hi All,

When I create a document object, it is coming up very slowly taking 2-3 minutes time, but document object is crated fine and showing up, how to avoid slowness in showing up, please suggest

Add Comment
2 Answer(s)

Hi All,

Could anyone help me with my issue 

“When I create a document object, it is coming up very slowly taking 2-3 minutes time, but document object is created fine and showing up, how to avoid slowness in showing up, please suggest”

Agile Angel Answered on October 26, 2016.

How are you going about creating the Documents and when are you experiencing the delay?  
Does the same delay occur when creating other objects (Parts, Changes) or is it only Document objects?

on October 26, 2016.

Hi Danny

Good Day ! we are not experiencing the same delay for other objects like Plant, Module etc.., it is only happening to Document object, it is taking 2 mins to show up after creation.

Thanks

on October 27, 2016.

I am creating Document object through Create New —>Items—>Documents.

we are using AgilePLM 9.3.1

on October 27, 2016.

Just to be thorough (apologies if this is stuff you’ve already checked):
1 – Does this delay occur EVERY time a new Document is created?
2 – Does the same delay occur if you open an existing Document and change it to Edit mode (click the Edit button)?
3 – Is the delay experienced by ALL users?
4 – Does the same delay occur when creating from the Java Client?
5 – Have you tried on different machine and/or using different (supported) browsers?
6 – Do your Document objects contain a significantly larger amount of Attributes than other objects?  (list attributes with huge number of values can impact performance)
7 – Do you have any events that are triggering large processes to be executed upon Document creation?

on October 27, 2016.

Danny

Thanks for all valuable questions, see my answers below.

Just to be thorough (apologies if this is stuff you’ve already checked):
1 – Does this delay occur EVERY time a new Document is created?
YES, it occurs every time we create a new document object
2 – Does the same delay occur if you open an existing Document and change it to Edit mode (click the Edit button)?
YES, it happening when I open existing document and change it to Edit mode
3 – Is the delay experienced by ALL users?
YES
4 – Does the same delay occur when creating from the Java Client?
I am not sure about this, I did not try this.
5 – Have you tried on different machine and/or using different (supported) browsers?
YES
6 – Do your Document objects contain a significantly larger amount of Attributes than other objects?  (list attributes with huge number of values can impact performance)
No 
7 – Do you have any events that are triggering large processes to be executed upon Document creation?
No

on October 28, 2016.
Add Comment
Best answer

Okay – it seems that your real issue is with opening a Document in edit mode rather than the object creation.  

Since you aren’t experiencing the same delay with other objects –  you might want to check the lists that are being used by the Document attributes.  

If lists contain a very large amount of values there are performance issues because Agile sorts the values before they are sent to be displayed in the web client.  I don’t think you will see the same delay in the Java Client if this is the problem.

Agile Angel Answered on October 28, 2016.

Hi Danny,

Thanks for update, in my document object I see 2 lists one is category and another one is Country which are having large number of values, except these I don’t see more values to other lists.

for country I see 180 values, for category we have 30 values, does this really makes performance issue.

on November 2, 2016.

Hi Danny,

Can you please give me steps to how to create Document using Java Client, I do using web application.

on November 2, 2016.

Hi Danny,

I created Document using Java Client, it is taking same time as it did for web client, still I am not able to understand where it is taking delay, any suggestions.

on November 3, 2016.

Sorry for the delay.  
That doesn’t seem like nearly enough values to cause performance issues like you are experiencing.  I was talking 10,000+ values.
I think you might be best opening an SR with Oracle Support.  You should probably also run Averify to see if you have any database issues.  The Averify log will most likely be requested for the SR as well.

on November 4, 2016.

Hi Danny,

thanks for update, we have created an SR with Oracle, they ask us to run Averify, we are working on it, facing path issues with oracle_home

on November 4, 2016.
Add Comment

Your Answer

By posting your answer, you agree to the privacy policy and terms of service.