Agile PLM 9.3.4 – Node(*, *) does not exist in the cache

Generally this type of error points to a data issue. Which at times took simple SQL scripts or as it happened in my case Hot-Fixes from Oracle support.

I hope you have executed A-Verify and then Fix-scripts and did a bouncing of the system and then re-tried ACP. Also can you share the java-console log when you trying to open the particular criteria in Java-client. It will help in analyzing it further.

Hi Arif,

Please understand that I have really little knowledge about APLM at the moment.
I only got explanations on how to start/stop an instance, execute acp import and edit the configuration in the Java client.
I’m not the one that have installed and setup the instances but I have to understand why this error occurs when I try to alter those criterias.

Are A-Verify and Fix-scripts tools that are available in every APLM instances ?

What is a “bouncing” in this context ?!

If you are speaking of the command console used to execute the startAgile script then it does not display anything when I try to open a criteria in the Java client.
Is there a specific log file I can check for that please ?

Hi AB,

Thanks for sharing the details. Let me try to make it bit detailed :

1. A-Verify : It is a tool provided by Oracle to check various data-corruptions/issues on different tables. Once executed it lists out a report which contains various error numbers. Corresponding to those generic error numbers you will have fix scripts. In some of the cases you need to contact to oracle to get fix script for a particular issue.

If you have in-house development/dba team who handles this then you can contact them for execution. Otherwise you can check my response on this thread on How to download A-verify on the below thread
https://myagileplm.com/questions/what-is-link-to-download-aut-and-averify-i-didnt-got-it-on-oracle-edelivery-com-site/

2. How to get logs from Java-Client :
    a. Open the Java Control Panel you have installed on your computer. You can search for it in your start menu.
     b. Go to Advance tab on the control panel and click on radio button Show console
    c. Close your browser and now relaunch your Java-client. There will be a pop-up which will come up with this. When you click on your criteria it will pop-up some lines of java code in the same window. You can analyze that or just copy and paste it here.

3. Bouncing : Refers to re-starting server nodes.

4. Generally you can check for error messages in the start-up log which generally is STDOUT log while you executing this.

Regards,
Arif

1. A-Verify

I need to collect informations about our Oracle support account first so I can access the A-Verify download.

2. Java log

I’ve followed the procedure you gave me and I indeed get errors when I click on a broken criteria.

The long error chain is in attachment.

Is there a way to fix this without the tools of point 1. ?

Can I force the deletion of the broken criteria somehow so I can recreate them ?

Thanks again for your help !

Oh, Ok for the attachment, here is the log:

The first part in screenshot pretty much implies the data corruption issue. If you look for  “AWT-EventQueue” exception specific to 9.3.4, it implies application of 9.3.4.0.325 patch. In case you have applied this one recently, you can re-install it after consulting with Oracle via SR.

If you can recall previous settings, just cross check if the associated Criteria with Criteria name i.e. Attributes etc is not disabled somehow. Also just cross check if the associated privilege is available.

Coming to backend solution, i don’t recommend it. Even though you those criteria name you can get it from Nodetable, there are host of other tables like Query and Criteria  are also involved and probably and insert/delete statement gonna fix it which is again not recommended. 

So i can think of two possible solutions,  One is to run A-verify and execute fixes for errors if found Or finally open oracle SR.

I’m not familiar with APLM install and update but if I check the Install/patchinstall folder of the instance the last applied patch seems to be 9.3.4.0.112.

The privilege that are using the affected criteria can’t be displayed in the Java client. A window open when you click on them but it’s just an empty java window.

In the java console, it basically prints the first part of the picture of my previous post (ie the 20 lines above the “Exception in thread “AWT-EventQueue-2″” error).

What I would like to do is to check what is the “Object Type” associated to the broken criteria but I can’t since it’s impossible to open it in the Java Client.

Can I perform a sql select query with Oracle SQL Developer to display this Object Type ? If so what would be this query ?

Also, do you think that I can take the last valid export_*.agl file used in production environment and do an acp import of it on the “broken” dev environment ?

Arif is steering you in the correct direction. Averify is a tool you will need, and it should be run at least once a month, and it provides a lot of information if there is a data issue in the database. And if/when you open an SR with Oracle, the latest Averify log file is one of the first things they ask for. Check your Agile application server and/or database server for anything named “averify.properties”, and you have most likely found where it is installed. Open the averify.properties file, and if it says that you are at version 1.7.6 (or above, like 1.7.8), then you are at the correct version for your database.

 The attachment seems to show that the account you are using does not have permission to discover or see whatever is there. That in itself is just a bit strange, as if you are logging into Agile using the admin account (or another account that has the admin role/privilege), you have access to just about everything. And if it is in fact trying to see something outside of the Agile database, that is even more strange.

 A database/SQL fix is risky without looking at it in depth. Things (especially the configuration records) are very interconnected, and telling you to delete record X from a table might well introduce more issues, and not quite fix the issue you are seeing.

If the objective is just to find out the Object type you can try the below Query

SELECT DISTINCT Q.NAME,N.DESCRIPTION as OBJECT_TYPE FROM QUERY Q,NODETABLE N
WHERE
Q.TYPE=N.ID(+)
AND Q.NAME=’YourCriteria’

Seeing the hot fix that was last applied is 9.3.4.0.112 so possibly if you work with Oracle then they might recommend you to 9.3.4.0.325.

As said earlier, I am in 100% agreement with Kevin on the need to have A-Verify set up in place. That makes most of the stuff cleared. Even if you raise SR with Oracle the first thing they will ask is to latest A-Verify set up (1.7.8/1.7.7) in place and secondly run the scripts and execute the generic fixes.

Hope this helps.

Thanks for your answers Arif and Kevin.

1. AVerify

I’ll look into installing A-Verify as soon as I have access to the download.

I’ve checked everywhere but there is no trace of a .properties file for Averify in the instances that I now have access to.

2. Patch 325

Ok, I’ll ask the person who originally setup the instances to apply the required patch.

3. Database

I heard you about the manual modifications of the database and I don’t intend to try any.

@Arif:

I’m confused because if I look in the NAME column of the QUERY table I don”t see the name or apiname of the Settings/Data Settings/Criteria I see on the Java client.

Are we talking of the same thing when we speak about “criteria” ?