Oracle Switch TP1996-9.2.2.1A Manuel D’Utilisation

Agile 9.2.2.1  
 
 
 

6.   Run the 

Agile9exp script again. 

The Agile9exp.dmp file created can be used as a backup of the system after the Agile PLM 
9.2.2.1 database reorganization. 

7.   Rename the agile9exp.dmp file to agile9exp_reorg9221.dmp for backup. Also rename the 

agile9exp.log file to agile9exp_reorg9221.log. 

8.   Change to the Agile9Tmp directory: 

 

9.   Start SQL*Plus from a command line and log in as 

agile/tartan or agile/tartan@agile9. 

10.   Run the agile9_check.sql file to validate the schema integrity and confirm integrity of the 

database reorganization: 

Important  If errors are displayed, contact the Agile Support Center. All errors must be fixed before 

proceeding to the next step. 

11.   Start the Oracle listener. 

The following steps should only be performed after you have upgraded the Agile PLM application: 

12.   Start the Agile application server. 

13.   Shutdown the database. 

14.   Perform a cold backup of all the database-related files. 

15.   Restart the database, listener, and application server. 

 

The Full Text Search scripts are located in $AUT_HOME\scripts\oracle\utilities\script_tools. Using 
SQL*Plus from a command line, run the following scripts on your upgraded database: 

à 

agile922_fts_prefs.sql on the CTXSYS user 

à 

agile922_fts.sql on the upgraded Agile schema 

 

If you are using the Agile SDK, delete the 

AgileSDK.cache directory from your client machines after 

you have upgraded the Agile PLM database and application server. The 

AgileSDK.cache directory is 

found under the 

temp directory (%temp%AgileSDK.cache). 

 

Page - 26 

Database Upgrade Guide