Embed Size (px)
Citation preview
Stat 520 to 521
• Windows Client
• Install 5.21 exe
• Next Step: Run DB Script before logging into client
Stat 520 to 521
• Database
• 5.2 to 5.21
– Porav521.sql
• Check Logs for errors
Stat 520 to 521
• Stat Server: re-installed during 5.3.0 upgrade
• Nothing needed for 521 if upgrading directly to 5.3.0
Stat 5.21 to 5.30
• Windows Client
• Install 5.3 exe
• Next Step: Run DB Script before logging into client
Stat 5.21 to 5.30
• DATABASE• 5.21 to 5.3
• UORAv521-530.sql• UORAv530ps8x.sql• UORAv530ps8L.sql
• After executing the upgrade scripts, you need to recompile invalid PL/SQL modules in the Stat
• Database. To do this, run the script, utlrp.sql located in <ORACLE_HOME>/rdbms/admin directory.
• Check Logs for Errors
Stat 5.21 to 5.30
• Windows Client
• Log-In as system user
• Check Database Script entry under
– Maintenance, general, system, dbscripts
– Verify upgrade entry
• Run Object Mover Instructions
Stat 5.21 to 5.30
• STAT SERVER
• Stat 5.3
• For 5.3.0, you need to have a Java 2, Standard Edition, Java Development Kit (aka Java SDK) v1.4.x
• Rename Existing Server Directory (Stat Home) to reflect version increase (statserver_521)
• Copy New Server Files from Patch Standalone.zip to Stat Home location
• Start Agent via run.bat in server bin directory
Stat 5.21 to 5.30
• Stat Configuration Assistant (SEE NEXT PAGE FOR SCREENSHOT)
• Once Agent Is Started open browser and enter address below
• http://<stat_server_host_machine>:8080/stat-config. (USE LOCALHOST)
• Enter appropriate info for the Stat database: Host Name, Port, DBName [SID], Login ID, Password.
• Database Connection Test: Prod Only• File Server Connection Test: Prod Only
• Test Web Client• http://<stat_server_host_machine>:8080/stat.
Stat 5.21 to 5.30
• New User Rights to Update
• Attachments add/delete • Assigned Developer (Default Developer)
• Update Object Control if they Want it on File Server Connection Test
• Test Web Client• http://<stat_server_host_machine>:8080/stat.• Test Windows Client Agent Status
Stat 5.30 to 5.3.1
• Windows Client
• Copy dll’s and exe from client patch location over existing install directory for client
• Next Step: Run DB Script before logging into client
Stat 5.30 to 5.3.1
• 5.3 to 5.3.1 (Shut Down Agent First)
• Database -PORAv531.sql
Stat 5.30 to 5.3.1
• STAT SERVER 5.3.1
• Backup stat-config.war and stat-agent.ear below– To statsever_53 directory containing just those files
• copy \standalone\stat-config.war• to \app\server\default\deploy\stat-config.war
• copy \standalone\stat-agent.ear• \app\server\default\deploy\stat-agent.ear
• This file could be skipped if upgrading to 5.3.2 without starting agent server (it will just get replaced in 5.3.2 and is only needed to test)
Stat 5.30 to 5.3.1
• Windows Client
• Log-In
• Check Database Script entry under
– Maintenance, general, system, dbscripts
– Verify upgrade entry
• No Object Mover Instructions Needed
Stat 5.31 to 5.32
• Windows Client
• Copy dll’s and exe from client patch location over existing install directory for client
• Next Step: Run DB Script before logging into client
Stat 5.31 to 5.32
• DATABASE (shutdown agent first)• 5.31 to 5.3.2
• PORAv532.sql
• The following scripts apply only to PeopleSoft users running PeopleTools 8.40 or higher, or
• users who plan on running PeopleSoft in the future:
• • For users on Oracle Stat (non-Unicode) databases, run the script PORAv532ps8F.sql
Stat 5.31 to 5.32
• STAT SERVER 5.3.2
• Backup stat-agent.ear below– To statsever_531 directory containing just those files
• Copy \standalone\stat-agent.ear from patch directory
• to app\server\default\deploy\stat-agent.ear
Stat 5.31 to 5.32
• Windows Client
• Log-In as system user
• Check Database Script entry under
– Maintenance, general, system, dbscripts
– Verify upgrade entry
• Run Object Mover Instructions
