How to run Version AE program

cd $PS_HOME/bin

export PS_SERVER_CFG=$PS_HOME/appserv/prcs/PAPRDG/psprcs.cfg

psae -CD PAPRDG -CT ORACLE -CO JN84227 -CP 'Jibo Peoplsoft 2 tier Password' -R INSTALL  -AI VERSION

Procedure to run ae job

PROPER PROCEDURE

The proper steps to follow when running VERSION AE are:

1. Shutdown all Application Servers, Process Schedulers, and other PeopleTools clients.

2. *critical step* Ensure that all Application Designer session are logged out and shut down. If necessary, shutdown and restart the database and its communication software.

3. Establish the proper shell environment. Normally this includes logging in as your PeopleSoft id, and

changing to the PSFT bin directory (i.e. cd $PS_HOME/bin)

setting the PS_SERVER_CFG environment variable (export PS_SERVER_CFG=$PS_HOME/appserv/prcs/<dbname>/psprcs.cfg)

4. Execute the command from a command line:

psae -CD <dbname> -CT <dbtype> -CO <oprid> -CP <pswd> -R INSTALL [where INSTALL is a valid run control] -AI VERSION

(Note: INSTALL must be a valid run control for <oprid>)

5. Issue the following SQL and archive the output to ensure that the program ran (all the versions should be 1).

SELECT * FROM PSVERSION ORDER BY VERSION DESC;

6. Clear the cache files from the Application Server, Web Servers, Process Schedulers, and Client machines.

7. Restart the system per normal operational procedures. There will be expected performance impact as the system rebuilds its cache files.

8. Over the course of the following days, every 4 hours or so, rerun the SQL from Step #5. You should observe a gradual growth of the versions, typically in the order of dozens per day. The version associated with SYS should always be equal to or greater than all other values in the table.

Should you observe one of the following conditions contact the GSC immediately for further advice.

1. The version value associated with SYS is no longer greater to or equal all other value in the PSVERSION table.

2. Some of the values increase dramatically, on the order of several thousand, and then remain fairly constant. Normal behavior is for the values to increase by increments of 1. One exception would be during the migration of a project with many records. Some values will increase by the number of records migrated.

Workaround:

N/A

Running version may fix the problem, but the entire dbms will be slow for sometime because objects will need time to be recached.