Is the path to the files fully defined in the index file???  Can you attach one file manually from the directory where they are located??
Are you using the INPLACE option and if so, have you created the custom read-only file vault??
Usually that error comes because the file name is wrong or the directory isn’t fully specified.  But a good first check is to manually attach a file and see how that works.

Just about everything in NODETABLE is part of a hierarchy. The entire configuration starts with the classes, and then proceeds down from there. Note that NODETABLE has an attribute named PARENTID. Find the ID for the Change Orders class (6000) and then execute the query “select * from NODETABLE where PARENTID=6000”. You will see LifeCycle Phases, Attributes, Actions, Tabs and User-Defined Subclasses. Run the same query but with the ID for the subclasses (6005, usually) as PARENTID. That will list the names of all of the Change Order subclasses. You can do the same for any other class.
 Note that not everything for the configuration is in NODETABLE. PROPERTYTABLE, ADMINMSATT, ADMINCRITERIA, QUERY, CRITERIA and SELECT_LIST are just a few of the other tables in which configuration data is stored. As Antonio stated, it is far easier to use the SDK, because it knows how everything is connected. Figuring it out on your own to be able to get information using SQL queries will take a lot of time and energy, and you will have to re-check those queries every time you upgrade the schema. Whereas the SDK will always be correct.

Agreed with Antonio, it is always best to get such information using the SDK.
 That said, if you want to see the status type along with the actual status value  (similar to what you see in the Signoff/Workflow tab), the following query will do so :
select change_number, n.description “STATUS”, le.entryvalue “STATUS TYPE”
  from change c, nodetable n, listentry le
 where change_number = ‘<CHG_NUM>’
     and c.status = n.id and n.objtype=107
     and c.statustype = le.entryid and le.parentid=3644;

 If you want to link in records from CHANGE_HISTORY, it gets a LOT more complicated (having just finished trying to figure it all out). SIGNOFF links to WORKFLOW_PROCESS using SIGNOFF.PROCESS_ID = WORFLOW_PROCESS.ID (as does the CHANGE table) and it then links to CHANGE_HISTORY using SIGNOFF_HISTORYID *or* HISTORY_ID (and sometimes both). Note that there are a fair number of “extra” records in both SIGNOFF and WORKFLOW_PROCESS that the GUI weeds out, but doing so using SQL*Plus is not at all obvious. And to then get the ordering of the records correct (i.e. matching what you see in Agile) is another exercise in non-obvious-ness. Note that it cannot be done with a simple query (or even a complex one), there MUST be processing involved, so it must be done using PL*SQL.
 Using the SDK API is much easier, not just because things can change between versions but because what processing Agile does behind the scenes is not documented.

What version of Agile are you working in???  The name of the subclass will be in NODETABLE, what is in PROPERTYTABLE are various properties for the subclass. PROPERTYID defines what the property is, and VALUE or SELECTION contains the value itself. Same for the workflow and status, the name will be in NODETABLE. For the most part, you do not need to be concerned with what is in PROPERTYTABLE, just get the name of  the subclass/workflow/status from NODETABLE. Workflow history is mostly in WORKFLOW_PROCESS table, but who approved/rejected what is held in SIGNOFF, and it also links to CHANGE_HISTORY.
 Please note that the Agile schema is pretty complicated, and there is  no public documentation on how it works.

DataLoad does not support loading flex attributes. I have no idea if it ever will, but I do know that there will be no major updates to the tool any time soon. I simply put the flex values into a separate table (with the associated item/change/etc. number) and then write an SQL script to manually load the values. Import also works very nicely, as would an SDK program.

select u.loginid, ug.name from agileuser u, user_group ug, user_assignment ua
 where u.id=ua.user_id and ua.class=11885 and ua.objectid = ug.id;

 Basically, USER_ASSIGNMENT holds the sites, user groups and roles that are assigned to a user. USER_ID links to AGILEUSER.ID, CLASS is how you determine which of the 3 is being referenced (11885 = user group, 11640 = roles and 11760 = sites), and then OBJECTID is the ID of the referenced object, as in, what is the ID of the object that is linked to the user.

Could you be a bit more specific??   Are you referring to attributes that have a value and those that do not, or user-defined attributes??
 I suspect the latter, so here goes. Existing attributes are in the tables in the schema, and the actual database table/attribute names (such as ITEM.SUBCLASS) are shown in the ATTRIBUTE column in the Classes Report and when viewing the schema classes in the Java client. When you create a user-defined attribute, it does not alter the structure of any tables in the database, but instead creates the necessary configuration records in NODETABLE/PROPERTYTABLE, and then stores data values in the AGILE_FLEX table using the ID of the newly created attribute. In AGILE_FLEX, it just looks like another attribute, very similar to how multi-text attributes are stored.

First, stop/start your application server. If the issue persists, run Averify against your database and if needed, have Oracle Support help you fix any issues. The issue here is that Agile is seeing something that it *always* expects to be there, and it is

REASON_CODE is a list attribute in the CHANGE table. As such, it holds the ID for a text value that is displayed in the GUI. If you can get into the Java client, look up Change Orders class, click on the Cover Page attributes, and look for REASON_CODE in a

i agree with Patrick, there is no simple or easy answer to this question. The subject mentions 9.3.4 but the message itself mentions 9.3.3. And there are *many* steps involved with upgrading an Agile environment, and downloading/installing the software is