Agile 9.3.1.2 is only certified to run on an Oracle 10g or 11g database server. But you can certainly import the database onto an 12c database server and update the Agile configuration to point to it instead of your usual server, and I would expect that it would most likely work just fine. But you may want to inquire at Oracle Support as to what their recommendation is.

Thnaks Kevin,
Please give some more details on this, how to update the Agile connfiguration to point,  if not we can upgrade the Agile PLM to 9.3.3? if yes means  is there any perfect document for Agile upgrade from 9.3.1 to 9.3.3 please provide the documents regarding this

Read the AUT manual for Agile 9330 (Database Upgrade Guide E39282-01), it contains everything you need to know. It isn’t necessary to always use the  latest version of AUT (1780), but at least use the AUT version released for the version of Agile that you are upgrading to (9330 = 1750). Using AUT is pretty straightforward. You run Averify on your current database and fix all the reported errors. Then you edit the AUT properties file so it knows what you wish done, start AUT running, it reads the properties file and does it’s stuff, and you end up with a database at the specified schema level. Always review the log files, just in case.

 One of the things you need to do IMMEDIATELY after installing Agile 9330 is to save the keystore value (script attached), because if you lose it, you *MUST* install Agile again, as the value is specific to your Agile server. You can then export the upgraded database from above, import it to your 9330 database server, set the keystore value in the database using the SQL script generated from your installation database, and start things up. If the keystore value is incorrect, Agile WILL NOT START.

 Note that you do not update the configuration, you upgrade the entire database using AUT. Tables can have new attributes (or have old ones removed), there are additional records added to support new functionality for the application, and existing stuff is updated or modified as needed. The AUT utility handles all of this, all you need to do is make sure that all Averify errors are fixed (some will cause errors in the configuration or data, and some will make AUT crash).

Thanks Kevin,

it means for database side we need to follow AUT, and then application side we need to do uninstall 9.3.1 and then fresh installation of  9.3.3 ?
we are using Linux platform, if possible could you please provide the documents regarding this .

Yes, although I would install Agile 9330 on another server altogether so you have a valid 9310 environment until you get everything done.
 The Agile installation documents for 9330 are :
Security Guide                                E39280-01  reviews firewall/DMZ considerations for protecting the Agile servers.
Capacity Planning Guide             E29278-01  discusses how big of a server you might want to use, given  data and user estimates.
Application Installation Guide    E39279-01  leads you through installing Agile on both Windows and Linux
Database Upgrade Guide               E39282-01  reviews how to use AUT to upgrade a database to the 9330 schema
Database Install Guide                   E39281-01  guides you through installing Oracle for your Agile application

 You could also look for E50306_04 as the overall documentation set for Agile 9330. It contains all of the above, and a lot more.

Kevin

Thanks Kevin,

Could you please provide how to save the keystore value, previous attached file showing some jpeg images only not related to Agile.

Here is what was in the script file that somehow got screwed up :

— DIRECTIONS :
— 1) Open an SQL*Plus session and log into the Agile schema account
— 2) Create a spool/log file for the script results SQL> SPOOL <directory>/RestoreKeystore.sql
— 3) Run this script SQL> START <directory>/GenerateRestoreKeystore.sql.txt
— 4) Close the spool/log file SQL> SPOOL OFF
— 5) Exit the SQL*Plus session SQL> EXIT
— 6) Put the “RestoreKeystore.sql” file in the Agile import directory (<ORACLE_HOME>adminagile9createagile)
— and also save it to a separate safe place

set pagesize 0
set linesize 1000
set trimspool on

spool RestoreKeystore.sql
prompt — Restores Agile keystore and administrator passwords
SELECT ‘UPDATE propertytable SET value=’||CHR(39)||value||CHR(39)||’ WHERE parentid=5004 AND propertyid=1008;’ FROM propertytable WHERE parentid=5004 AND propertyid=1008;

prompt — admin user
SELECT ‘UPDATE agileuser SET login_pwd=’||CHR(39)||login_pwd||CHR(39)||’ WHERE id=704;’ FROM agileuser WHERE id=704;
SELECT ‘UPDATE agileuser SET login_pwd=’||CHR(39)||login_pwd||CHR(39)||’ WHERE loginid=”superadmin”;’ FROM agileuser WHERE loginid=’superadmin’;
SELECT ‘UPDATE agileuser SET login_pwd=’||CHR(39)||login_pwd||CHR(39)||’ WHERE loginid=”ifsuser”;’ FROM agileuser WHERE loginid=’ifsuser’;
SELECT ‘UPDATE agileuser SET login_pwd=’||CHR(39)||login_pwd||CHR(39)||’ WHERE loginid=”agileuser”;’ FROM agileuser WHERE loginid=’agileuser’;

prompt commit;;
spool off;
quit

Thanks Kevin..

this all should follow before the database upgrade 11g to 12c ? or else after database upgrade from 11g to 12c ?

Means, we can upgrade Agile PLM before Database upgrade 11g to 12c or after database upgrade from 11g to 12c ?

The steps are pretty simple :
1) Install Agile 9330 on a new server (this *will* include creating a database).
2) Run the GenerateKeystoreRestore script against the database created during the installation.
3) Run AUT to upgrade the existing database in your test or dev environment.
4) Import the upgraded database into the new 9330 environment.
5) Run the RestoreKeystore script (generated in step 2) on the upgraded database.
6) Start Agile.

 Note that you can be installing Agile 9330 and upgrading the database at the same time, as those 2 tasks are (or should be) taking place on separate servers.