Quest® Stat
Version 5.4.0
Release Notes
January 2008
Stat is a change lifecycle solution optimized for PeopleSoft Enterprise & Oracle E-Business Suite applications. Stat makes organizations more responsive to change and increases visibility into, and control over, the change management process. Stat dramatically reduces the time required to deploy patches and critical changes throughout the various instance of a packaged application, resulting in lower total cost of ownership.
Stat 5.4.0 features the following enhancements:
The following is a list of enhancements implemented in this release of Stat.
|
Feature |
Resolved Issue |
Change Request |
|
General
|
Stat Relational Integrity - introduced primary/foreign keys into Stat database tables | CR0039596 | Support for "Apply to All" when adding file objects to a CSR and encountering case sensitivity questions. Stat will now ask the user if all files should be treated in the same manner. If the answer is yes, then the user will not have to respond to each file on the object list individually. If the user responds no, then they will be prompted again on the next file where the name doesn't match. | CR0049338 |
The Compare Wizard option is displayed on the right-click popup window of the Environment Info view of the CSR Object Management tab. This is easier to click on than reaching for the mouse to click on the compare button. |
CR0060763 | The Mass Migration archive set selection list displayed archive sets that had already been migrated to an environment when the same archive set had not been migrated to all of its targets. The user couldn't tell that it had already been migrated to this particular target. Now the wizard will only evaluate the specific target. For example, if an archive set has been marked as ready to migrate to D1, D2 and D3 and has been successfully migrated to D2, it will only display on the list for D1 and D3 the next time a mass migration is requested. | CR0066354 | The custom command window on the post migration step window can be edited by a user who has appropriate rights to do so. Associated with General Maintenance rights: Post Migration Command Edit; Post Migration Command Execution. | CR0069206 |
|
A new option is available with workflow within a CSR. Historically,
status transfer approval requests for status transfer from A to B are
generated immediately when the CSR enters Status A. Since the CSR may
sit in Status A for quite some time, the approval request may not be
valid at that time. The site administrator can set an option on system
table maintenance, Other Options, to delay Status Transfer Approval
generation until all other workflow transfer rules (tasks and
migrations/patches) have been completed. If this option is set then
the approval list will not be generated until tasks and migrations have
been completed. The list will be automatically generated at that time.
There is a new user right to allow specified users to over ride the
generation of approvals and cause them to occur on demand. (Status
Transfer Approval Generate). In addition, there is a new user right
to allow specified users to refresh/regenerate the approval list (Status
Transfer Approval Regenerate). |
CR0074776 | |
| Workflow Maintenance Date and User Id are now updated with changes to the workflow templates. | CR0079549 | |
| Post migration steps will use SSH if the server to which they are connecting has SSH configured. If the server does not have SSH, then REXEC will be invoked (on Unix servers). | CR0089364 | |
|
Automatic script parameters have been added to post migration steps for Target Environment, Login and password for that environment. In addition the user will be able to configure their own parameters for use in post migration steps. |
CR0089498 | |
| Report Library: Object Type field in the Post Migration Checklist was not displaying object types. This field is related to the change management module field at the beginning of the criteria list. If the Change Management modules is listed as None or Any, the object type list can not be changed from Any. If the Change Management Module is changed to Generic Apps, PeopleSoft or Oracle Apps, then the object type list will display the object types for that module. | CR0103969 | |
| The Stat Standalone agent supports https (SSL) on the web browser. The site must have a security certificate. Quest does not supply this. See installation/upgrade instructions for more detail. | CR0104796 | |
| Initial access to the Stat web client has been modified. All users will automatically be logged into the user console. Those users with permissions to access the job console or the new Ad Hoc report console can then click on Menu and access the other modules. | CR0105275 | |
| Clustered Indexes have been defined for all Tables in SQL Server to improve performance. | CR0108104 | |
|
Stat uses a connection pool to maintain connections to database. Connections that have been idle for a specified period of time will be closed but will be immediately re-established unless connections to different databases are needed. Some DB2 sites have their idle connection timeout set much smaller than the 15 minutes that the Stat agent uses. This causes a large number of error messages to be generated on the DB2 database. A new parameter has been added to the stat.properties file in <STAT_HOME>/CONFIG. It is listed in the section called Test Connection Properties. CONNECTION_IDLE_TIME=15. The default value is 15 minutes. This can be modified by the Stat administrator to a lower or higher value. Stop and restart the agent after the modification is made. The agent will stop any connection that has been idle for longer than that period of time. Note that the industry standard indicates it will take 1-2x the idle time indicated to close the connection. Caution: setting this value very low could have a negative effect on agent performance. |
CR0121865 | |
| The workflow tab of the CSR shows the user what needs to be done to progress the status of a CSR. As such, it did not maintain historical information regarding approvals. A feature has been added to the Transfer History tab of the Transfer Rules Status window of the workflow. Right click on a given row of transfer history and the approvals given for that status transfer will be listed. | CR0122487 | |
| Stat historically defaulted Country to USA on the customer window. The administrator can now modify the default value to any country defined on the country table. Default Country is a field on the Other Options tab of System Table Maintenance. | CR0145914 | |
| Stat reports generated from the Windows Client can only reliably be exported as a .PSR report type. There are a few exceptions where Excel is acceptable. In 5.3.x Stat provided the user with the ability to export to .PDF. The list of file types has been modified in 5.4.0 to limit the types of files that the user can choose. But the rule is still true, so, when in doubt, choose .PSR. Stat has a standalone report viewer than can be installed on any workstation regardless of whether or not the user has a Stat license. This executable can be linked to the .PSR file type to automatically open Stat reports. | CR0158480 | |
| The Stat agent has been upgraded to use Java 5. See upgrade and/or installation instructions | CR0162309 | |
| The ability to view CSR Detail Logs and the CSR History tab has been added to the Stat Web Client | CR0179243 | |
| The workflow transfer ready job has been modified to improve performance. As such, this job can now be run more frequently without adversely affecting the Stat agent. | CR0188081 | |
| A new display has been added to detail logs that allows the user to view all detail longs on one screen. This is in addition to the filtered views that have previously existed. In this summary view, the user may change the sort order to be ascending by date or descending by date. Then, if desired, they can filter on topic or time period. They can choose to display or hide confidential detail logs if they have that right. And, they can either print or export the detail log list from this window. This is available on both the Windows and the Web client. | CR0189364 | |
| Jboss has been upgraded to version 4.0.5 on the Stat Standalone agent. | CR0191538 | |
| New report: Release Mgmt-Release and Approval. This report displays which Release stamped archive sets are marked as ready to migrate and the approval status of those archive sets. | CR0191969 | |
| The Quick Search field on the CSR Objects tab has been replaced with a Quick Filter. Quick filter has been previously utilized by the Oracle Apps module and now replaces all instances of quick search. This feature filters across multiple columns in the object display. | CR0197105 | |
| CSR Object reports did not previously include unlocked objects. Unlocked objects are now included. | CR0197149 | |
| Post Migration steps for DMS scripts can be defined without a specific object type link. | CR0197312 | |
| A new report gives information on who historically approved migrations. PS Migration with Approval History is found under the Approval category. | CR0200411 | |
| Some windows have been updated for a more modern appearance | CR0202101 | |
| Object type has been added to the migration log created by the Stat agent. | CR0206919 | |
| Attachments added to CSRs via the web client showed an incorrect time stamp on the history tab if the database and agent time were different. The web client has been updated to always use the Stat repository time. | CR0207874 | |
| All fields on the user table can be templated to define the LDAP address. Many of them will probably never be used, but any of them can be used. | CR0207926 | |
| New options have been defined on System Table maintenance to allow the Stat administrator to define which CSR changes should be stored in the history tab and which can be skipped. The default is All fields. Some sites may wish to cut down on the volume of data being stored and can modified the history tab as desired. | CR0212426 | |
| The object compare wizard can now be run for multiple objects at a time when it is run the Object Management menu. The aggregate report first gives the user a list of the objects and indicates whether they match or do not match. The user can then look at objects individually for detail information. In addition the user can indicate whether to include or exclude the following fields from the compare: object version, last update userid, last update date. Blob fields with the designation of [blob] have no data in them. Blob fields with data are listed as [BLOB]. This saves the user from doing Blob compares just to tell whether or not there is data in the field. | CR0213624 | |
|
Mass migration considered the same environment on two different migration paths to be two distinct environments. This has been modified. The user will be able to migrate to a given environment regardless of which migration path it is one. There is one exception. If the environment is a distribution environment on one migration path and not the other, then they can migrate to one or the other, but not both. The same is true if both are distribution environments, but the listed of distributed DBs is different. In both cases the user will have to perform separate migrations. |
CR0216181 | |
| When a user requests an outbound email through the Windows Client, the request is now sent to the agent and the agent processes the email as opposed to the workstation client. | CR0216191 | |
| CSR attachments can now be included in outbound mail. All attachments will be included. | CR0216411 | |
| Post migration steps allow for user to define multiple statements in one command | CR0218344 | |
| Stat upgrade scripts on Oracle have been modified to include information about the number of tables existing before and after the upgrade. The outputs logs have also been cleaned up to make them easier to decipher | CR0221540 | |
| Stat upgrade scripts have been improved so that users do not have to upgrade from 5.3.0 to 5.3.1 to 5.3.2 to 5.3.x to 5.4.0. Any version of 5.3.x can use the same script to upgrade to 5.4.0. There is just one script. See upgrade instructions. | CR0221775 | |
| Reports that can be scheduled to run by the Stat agent are now available as Ad Hoc reports on the web client. The reports use the same user security that the Windows client users. The reports require that criteria groups already have been defined on the windows client. | CR0222652 | |
| If the LDAP tab on System table maintenance has been updated to use LDAP and the user clicks on OK before inserting data into the User table, the user will be warned that the user table has not been updated for LDAP. | CR0223244 | |
| The location of the LDAP keystore for the Stat agent has been split into a separate field to accommodate sites where the Stat agent is not running on Windows and needs a different directory definition. | CR0223252 | |
| The Past Due jobs run faster than in previous releases. | CR0223563 | |
| Improvements to the Oracle repository upgrade scripts including before and after counts, the ability to rerun the script, better logging. | CR0223683 | |
| Support for Red Hat release 5 | CR0225188 | |
| "Send To" for Past Due Patch Approval business rule now includes Patch Approver as a selection. | CR0227748 | |
| Stat accepts Status Transfer, Migration and Patch Approval (Oracle E-Business) via an email that is returned from a Stat email. Emails can be generated via existing past due business rules, or using a new Email button on each of the windows for Status Transfer approvals, Migration Approvals or Patch apply approvals. The emails sent from Stat contain links to approve/reject requested approvals. The email returned to Stat from those links validates the user via their email address and posts the approval/rejection. Approvals will be updated if a new email is sent via the link. The inbound approval emails will be posted to the CSR Detail logs. Replies to the original email will not be posted as approval/rejections but may be processed as new mail unless the Special Processing tab of email configuration is updated. Upgrade scripts automatically add these exclusions to the Special Processing tab of email settings. | CR0227749 | |
| PeopleSoft | A quick filter field has been added to the Read Project Wizard. This allows the user to narrow the search for project names in PeopleSoft. | CR0119355 | Support for the following PeopleSoft object types starting with PeopleTools 8.48: IB Queues, Service Operation, Service Operation Routing, Service Operation Version, Service Operation Handler, Services | CR0204926 | The Read Project wizard gives the user an indication of object types that are in the project that are not supported by Stat and are therefore not added to the CSR. | CR0205313 |
| If a migration to a distribution or distributed db is interrupted, the user will be prompted to review the project in the staging db, manually migrate the project and then mark the project execute checkbox. | CR0218314 | |
|
Oracle E-Business Suite |
Fetch events will check the merc_wake table for the status of the Oracle agent and will prompt the user if the agent is not responding. | CR0088076 | A new menu item has been added to the Tools menu that allows the user to view the status of the Stat Oracle agents in the same manner as the status of the Stat agent. The Oracle agents will update the merc_wake table every 30 seconds. This has the added advantage of keeping the port open if the agents are on the other side of a firewall. The length of time between heartbeats can be modified by changing the "Ping Multiplier" on the Oracle Apps Environment Servers maintenance window. The value can be greater than 30 seconds but not less. | CR0089506 | There are 2 new parameters that are recognized by Stat now for stopping/starting concurrent manager. %%appsusername%% will be replaced at runtime by the value in 'APPS User' of 'Oracle Applications Environment Connection Maintenance'. %%appspwd%% will be replaced at runtime by the value in 'APPS Pwd' of 'Oracle Applications Environment Connection Maintenance'. So when setting up start or stop command for any of the Oracle Apps services, users can use these parameters. For Example to start a Concurrent manager in R12, they can specify: $INST_TOP/admin/scripts %%appsusername%%/%%appspwd%% | CR0095388 |
|
Stat support for Oracle E-Business R12. This was previous available in Stat 5.3.2. |
CR0209826 | |
| The filter button on the OA patch console could produce misleading results due to a lack of focus when the user first enters the window. This has been resolved. | CR0216038 | |
| Stat for Oracle E-Business supports OAF objects | CR0219989 | |
| Stat did not recognize the return from Oracle's ADPATCH when it was running on a Linux environment. Therefore the patch was never marked as successful. This has been resolved. | CR0221433 | |
| Support for Oracle E-Business R12 XML Publisher objects | CR0222023 | |
|
The Stat client requests list of E-Business objects directly from the Stat Oracle agents (5.3.x). If the customer has invoked a firewall, they most likely modified the Oracle agent to use UIL2 communication instead of OIL. When this is done, each Stat client has to be told to use UIL2 to communicate with the Oracle agent. This can be cumbersome when there are many Stat workstations. A parameter has been added to the Stat system table to tell Stat clients to use UIL2. Now, a change need only be made on System Table maintenance rather than copying a file to every workstation. See upgrade instructions. |
CR0222532 | |
| Patch size has been added to the patch inventory display | CR0223203 | |
| The user can specify migration order of objects within an Oracle E-Business archive set. This will only be of import for SQL object types, but the user can specify all objects if they choose to. | CR0223390 | |
| A new checkbox was added to Patch Schedule screen called 'Disable Patch Backout'. This checkbox is only enabled for 'Patch Apply'. When the user checks this box, the agent does not perform a patch impact on the patch. This replaces the variable previously set in the stat.conf file of the agent. | CR0223475 |
The following is a list of issues addressed in this release of Stat.
|
Feature |
Resolved Issue |
Change Request |
|
General |
The CSR Search wizard on the Windows client has been fixed to search Archive set comments when the Stat repository is MSS. Stat-Oracle has been working correctly. | CR0059014 |
| Project Issues - Delete button doesn't remain dithered when rights revoked. If the user switched to CSR issues and then back to Project Issues, they could delete project issues. The delete right is now properly enforced. | CR0076091 | |
| Stat Database name could be modifed on the Database Login Info maintenance window. This has been fixed so that only the password can be modified. | CR0078656 | |
| On the Stat web client, attachment comments were difficult to read because the whole comment was displayed on one line. | CR0090754 | |
| The Stat agent can now be installed into a directory containing spaces in the name. | CR0092136 | |
| The "Arrange Icons" function has been removed from the Stat Window menu. | CR0134641 | |
| In Stat Web, a user without rights to the task tab could circumvent security by pasting the url for the task tab into their browser. This is no longer possible. | CR0136053 | |
| A new purge job has been added to purge old data from the merc_migr_* tables that are used by the Stat agent for mass migrations | CR0181373 | |
| The rule id and the date/time it was triggered has been added to the footer of outbound emails for Business Rules. The date/time is database time. | CR0191539 | |
| Inactive users who are still associated with a class or queue will not be included in approval requests if they are inactive at the time the approval request is made. If they are set to inactive after the approval request was generated, they will still be displayed on the approval list. | CR0191849 | |
| Release Management reports have been repaired so that they do not cause an agent error when they are scheduled through the agent | CR0192178 | |
| A fix has been made to the CSR Type/Status maintenance windows such that the window will no longer error out if a filter has been stored on it. | CR0192748 | |
| The Object Archive Search Wizard was modified to make it consistent with other wizard dialogs. | CR0193726 | |
| The Object Impact Wizard has been modified for performance improvement | CR0194112 | |
| JTDS drivers for MSSQL Server JDBC drivers have been upgraded for the Stat agent | CR0195308 | |
| Object History Wizard has been fixed to locate a file name regardless of case entered as the search criteria. | CR0200101 | |
| The Stat agent was listing an inappropriate error prior to each file object being archived. This error has been removed. | CR0200625 | |
| The file archive icon displayed a plus sign after a single archive in an environment. The plus sign now only displays when multiple archives have been taken. | CR0202110 | |
| Applications defined with APPLICATION TAB = None did not display in CSR drop-down when a new CSR was created. This has been fixed. | CR0203150 | |
| The Workflow graph on the web client displayed transfer information that had previously been removed from the template. This has been fixed. | CR0203392 | |
| The words submitter and submitted were misspelled on the CSR attachments window. Corrected. | CR0203545 | |
| Install script on MSS2005 has been corrected to have a default value for last ps_obj_id. | CR0204015 | |
| Stat-config now retains field information if it fails to connect so that the user does not have to retype the whole page. | CR0206407 | |
| Export web query as excel sometimes truncated column data on the Stat Web client. This has been corrected. | CR0206688 | |
| If a Resolution template has been defined it will be added to the resolution when the appropriate application or CSR Type is selected. It does not require any entry when the CSR is created. It will be stored in the resolution and only evaluated for required entry when the CSR enters a closed status. | CR0206939 | |
| When a CSR was closed, the user could not view any attachments to that CSR through the web client. This has been fixed. The status of the CSR does not affect whether or not attachments can be viewed. However, attachments can not be added or removed from a closed CSR unless the user has closed CSR Edit rights. | CR0207351 | |
| When an environment was removed from a migration path, the corresponding change was not displayed on workflow transfer rules. CSRs created after the migration path change still contained reference to the deleted environment in the workflow rules. A stronger message has been invoked in migration path maintenance to warn the user of possible adverse affects on workflow if they change the migration path. The administrator should always review the workflow templates after making a change to environments and/or migration paths. | CR0208572 | |
| If a user is a member of a Queue in a given service domain, that service domain can not be removed from their profile. The administrator must remove the user from the queue first. | CR0208622 | |
| When inactivating a user, a popup window occurs which lists CSRs that the user has outstanding approvals on. This window was not user friendly and sometimes it was so large that the user could not click OK to close it. The window has been reformatted with scroll bars to make more sense and such that it doesn't expand off the page. | CR0208937 | |
| The CSR History tab display is now available on the Stat web client. | CR0209499 | |
| Only one final archive set may be created per CSR. | CR0209751 | |
| The performance in displaying the workflow graphic has been improved on the web client. Customers with large numbers of CSRs in a given Service Domain were experiencing a degradation of window display. | CR0209757 | |
| When a file was not found during archive using SFTP a large stack trace was being written to the log in Error mode. This has been removed. | CR0210273 | |
| The project window has been fixed so that a CSR removed from the window remains removed after clicking save. | CR0210663 | |
| Objects Ready for migration Report did not show file objects. This has been corrected. | CR0210867 | |
| CSR Status criteria business rule did not send out mail after upgrading to Stat 5.3.1. The issue was with new column values in the upgrade script being stored as null. The upgrade scripts have been corrected to store 'N' instead of null. | CR0211023 | |
| CSR record locks occurred when Stat sat idle for more than an hour and then a CSR was opened. This timing issue has been corrected. | CR0211034 | |
| Detail Logs - Edit Own Logs was not enforced correctly on the Windows client. This has been corrected. If the user does not have this right, they can not edit a detail log after they have saved it. | CR0212219 | |
| Single quotes no longer disappear from description and resolution tabs on the Stat web client | CR0212391 | |
| Attachments can be added to a new CSR before the CSR id is generated when the CSR is first saved. This was a problem on the web client. | CR0212429 | |
| The display of CSR Priorities on the web client was not using the user defined priority order. This has been fixed. | CR0212501 | |
| Inbound email with HTML attachment did not create a CSR. This was sometimes related to the size of the email message. | CR0212608 | |
| The Object Management tab of the CSR has been corrected to retain the selected row focus when the CSR is saved. Prior to the fix, the Migration Target button appeared inactive after saving CSR, but in reality the focus had reverted to the first archive set on the list which may not have been the row marked as ready to migrate. | CR0212676 | |
| Cannot migrate more than 1000 objects with recovery wizard on Oracle 9i. This has been corrected. | CR0214878 | |
| The Cancel button on the Add objects popup window has been fixed. | CR0214906 | |
| The performance of adding related objects to a CSR has been improved. | CR0214909 | |
| Report Library: When a particular "Project Code" criteria is chosen the output from any report contains all CSRs Instead of CSRs associated to that particular project code. This has been corrected. | CR0215000 | |
| The Stat web client has been corrected to allow a user to completely remove a resolution on an open CSR. Prior to the fix, the user had to leave a minimum of one character in the resolution field. | CR0215336 | |
| Fixes were made to the General Maintenance menu to display file object maintenance when appropriate rights are selected. | CR0215400 | |
| Email is now all sent through the Stat agent. The Test connect email servers (SMTP/POP3/IMAP) has been left on the Stat client window, and has been added to the test connect page of the Web client. The test connect page has been moved from the Stat-Config window to a separate window entitled "Test Connect" which is available from the Stat Menu on the web. There are three tabs on this new page: Database, File Server, Email Server. The user has more flexibility in choosing which environments to test connect against. They can choose as few as one and as many as All to run the connection test. | CR0216412 | |
| Once a CSR was created, the CSR queue was not displayed under CSR Information on the web client. To correct this, each web user must do the following, one time. Open any CSR on the web client and click on the icon in the upper right corner of the CSR Information tab. A window will open that lists the items displayed in CSR information and allows the user to change the order. Click on the delete button. The screen will repeat and QUEUE will now be one of the listed objects. Modify the columns as desired and click save. | CR0217318 | |
| Migration Approvals on an MSS version of Stat have been fixed. Historical approvals are now being stored. | CR0217477 | |
| Clicking on Help in the Job Monitor of the web client sometimes displayed a blank screen. This has been corrected. | CR0218715 | |
| Resolution Edit rights on the web client have been fixed so that the user has access to edit the resolution at any time. | CR0219090 | |
| A user could circumvent stat-config security if they knew the actual URL and typed it into their browser. This has been fixed and will no longer allow the user access unless their workstation is is in the stat.properties file. | CR0219119 | |
| Web: Task comments and time entry notes have limited size | CR0219440 | |
| Using double quotes to create a filter in maintenance windows caused display issues when the window was reopened. This has been resolved and the user can save filter with double or single quotes. However, some existing filters with double quotes may need to be retyped. | CR0219756 | |
| When e-mailing multiple CSRs, Stat returns a duplicate key error. This error has been resolved and will no longer occur. | CR0220169 | |
| The Archive Set Sync Wizard running on Stat on MSS has been fixed so that users can migrated objects to sync up environments | CR0220467 | |
| Index Out of Bound error during Data Object migration has been fixed. | CR0221429 | |
| The open new CSR event on the web client has been fixed to stamp Object Control for Workflow correctly. | CR0222680 | |
| A misplaced text field has been removed from the LDAP window in System table maintenance. | CR0223026 | |
| The 'Filter' function has been removed from the right-click popup menu under the 'Tasks' tab of the CSR. | CR0223114 | |
| A more user friendly error message has been created on Stat-MSS approval setup | CR0223336 | |
| Null subject line in incoming email causes the email queue to hang. A blank subject line was fixed in a previous release and has been rolled forward. | CR0223374 | |
| Updating the distributed environments window via the Activate All button fails to refresh 'Last Update' column. This has been fixed. | CR0223409 | |
| Export of CSR History report in XLS with Header format has been fixed to display data in TO and FROM columns | CR0223531 | |
| Support for SSL (Standalone only; not Weblogic)- alternate stat-agent.ear. The modifications necessary to the Stat-agent.ear file to support https on the web client are risky. To that end, a separate, alternate stat-agent.ear file is being provided for those customers who wish to use https. | CR0223863 | |
| A new run.bat file is being delivered to fix the specified memory statements | CR0223948 | |
| Schema change on Stat-Oracle only to change ST_PS_ANL_MOD_DIM_FLD_8_IDX1 to a Non-unique index | CR0223973 | |
| Read Project wizard has been corrected to handle File Reference type objects correctly. | CR0224015 | |
| Corrections to both the ad-hoc and scheduled CSR History report to supply missing data. | CR0224173 | |
| The report "Graph of Activity by Type" has been modified to use the correct denominator when calculating percentages. | CR0224538 | |
| The web client reassignment of CSR User id is now triggering business rules. | CR0224727 | |
| The save event of the Report Library's Save Criteria button has been corrected to store an individual archive set id correctly. | CR0225195 | |
| If multiple CSRs with the same object on them were closed at the same time the agent might process the relock event inappropriately. The symptom was that either the objects were not unlocked on the CSRs expected, or the lock did not appear on the CSR where it was expected. This issue appears to be related to multiple CSR closures being processed by the agent at the same time. A fix has been made specifically for that event. | CR0225222 | |
| Modifications to the Object Management window. When a user adds objects to a CSR the default is to always add to all environments on the migration path and to lock the objects on all environments. ("Lock in Environment, All on Migration Path"). There are two additional lock options. One is to lock the object(s) on just the selected environment and the other is to add the objects to the CSR list but not lock them. In these alternate options, the objects were only being added from the selected environment. Therefore, if there were 8 environments on the migration path, the user would have to add the object(s) 8 different times. The protocol has been changed to more accurately reflect the title and intent of the group box options. If the option "Lock in Environment, Current Environment" is selected the object(s) will be added for all of the environments on the migration path, but only locked on the selected environment. If the option "Lock in Environment, None" is selected, the object(s) will be added for all of the environments in the migration path and will not be locked on any of them. The user can select any of the object-environment rows and change the lock/reservation status before clicking on save of the CSR. In addition, the Lock All button has been replaced by a Refresh button. The button will refresh the Object list screen and update any changes that have been made by the agent. The user will be able to see icon changes, status changes, version changes etc without having to close the CSR window and reopen it. | CR0225223 | |
| If the CSR "Record Lock Warning" screen happened to open when the Support Console was at maximum display, the window would turn to a grey box when it was closed and it would obscure part of the support console. This could be corrected by minimizing and then re-maximizing the support console. The display problem has been corrected so the user does not have to perform extra key clicks. | CR0225581 | |
| A fix has been made to the new CSR issues screen to prevent the process from taking over memory on the workstation. | CR0225648 | |
| Merge of data objects has been modified to prevent an application error. | CR0225870 | |
| Correction to the report library criteria selection for table dump reports that can not use 'Any' service domain. The user must store a specific service domain in the criteria in order for the web reports to work. | CR0225874 | |
| An invalid syntax error received when running Mass Migrations in MSS has been corrected. | CR0226246 | |
| The color coding on data objects in the Compare/Merge wizard has been fixed to reflect the correct state of the compare. Green is identical; pink or red is not identical. | CR0222949 | |
| Purge system events jobs fixed to remove log rows for Log off and Wait job and for Merc_OA_event tables. | CR0226263 | |
| Past due project business rules failed to send emails with a null pointer error. The null pointer has been resolved. | CR0226284 | |
| Upgrade JCraft component of agent to 1.3.4. This component is used for SSH processing on the agent. | CR0226345 | |
| The email generated to notify a developer that they have received object locks on a previously reserved objects was inconsistent in its content. Sometimes the objects listed actually were assigned to a different developer. | CR0226671 | |
| archive files - source 1 is inactive but agent still attempts to connect | CR0228555 | |
| Saved Report Criteria blanking-out Migration Path field. | CR0228597 | |
| Closed CSRs do not always release locks correctly. Wrong CSR ends up with lock. | CR0228716 | |
| Application error in Impact Analysis Wizard has been resolved. | CR0228719 | |
| PeopleSoft | The migration history wizard has been fixed to display PeopleSoft file objects that are migrated to distributed databases. The information was being documented during migration, just not displayed by the Migration History Wizard. | CR0090205 |
| Psoft V9 applications use Ptools 8.48 but the tools schema is different from v8.9. Modifications were made to handle blob processing in archiving and migrating. | CR0205125 | |
| The Compare/Merge Wizard will display images (PeopleTools 8.40 and higher) when comparing an image object | CR0209362 | |
| MSS Psoft database on an instance can be configured in the PS configuration maintenance table | CR0205132 | |
| Compare/Merge wizard does not grab blob data for File Layout Defn compare. This has been corrected. | CR0206101 | |
| Received error Unable to copy Project to Staging database when comparing peoplecode. This issue was related to the size of the PeopleCode and the staging db being on a different platform than Stat (ie not Oracle or MSS). This issue has been fixed. | CR0207691 | |
| Multiple users received same physical lock while using the reassign button. This has been resolved so that only the developer with the current logical lock receives the physical lock on the PeopleSoft database. | CR0208419 | |
| Stat now tracks the version and timestamps for File Type and File Reference Type objects | CR0208421 | |
| Stat has been corrected to archive/migrate Peoplesoft Roles with multiple languages | CR0213308 | |
| Application error could occur when reading in PS project with maintenance project option checked. This has been corrected. | CR0214129 | |
| The Read Project wizard has been corrected to handle Service Routings with a date of 1/1/1900. | CR0217351 | |
| The path to the PS configuration files on PeopleSoft Connection maintenance will now accept directories with spaces. | CR0218748 | |
| PeopleCode compare for 8.1x Peopletools line has been fixed. This is a binary compare only. Starting with 8.40, the PeopleCode compare displays the actual data. | CR0221458 | |
| Stat on MSS and PeopleSoft on Oracle had an issue with Blob data in objects. This was fixed in 5.3.2 and has been rolled into 5.4.0. | CR0221482 | |
| The object mover instructions for CI Property PeopleCode objects of PeopleTools 8.42 through 8.45 have been fixed. | CR0221542 | |
| When defining file locations, the drop down list of PeopleSoft environments appears to be random (depending on how well the db code and the descriptions do or do not match). Since this drop down displays the environment code, it has been modified to sort in alphabetically by code. | CR0222180 | |
| Fixed spelling error on object mover instruction window. | CR0222452 | |
| The managed PS Project drop down list was including names of data objects read into CSR. Data objects have been removed from the drop down list. | CR0222774 | |
| Read Project wizard has been corrected to handle File Reference type objects correctly. | CR0224015 | |
| When staging objects into the PeopleSoft staging database, Stat was accessing the target database to obtain the base language. This caused performance issues during staging especially if the target database was remote from the staging db. This has been corrected to obtain the base language of the staging db. The base language is cached during the staging process. | CR0224251 | |
| The Archive Set Purge wizard attempted to obtain the base language from the source database before purging an archive set. If the database was unavailable the purge failed. It has been determined that this information is not necessary to purge archive sets and the purge process will run more efficiently without trying to read the source database(s). | CR0224778 | |
| Performance improvements in locking and unlocking PeopleSoft objects on the CSR. | CR0226279 | |
| Fixed the Read Project Wizard to respect the status of object types in Object Type Maintenance. If an object type has been activated, the Project Read and Project Sync wizards will not add those object types to a CSR. The user will be notified that the objects exist in the project and are not being copied. The PeopleSoft project definition will not be visible when selecting a project name during migration. | CR0227667 | |
| Message Catalog Entries on Sybase platform now are correctly versioned on the objects list when the objects are locked and unlocked on the CSR. | CR0227863 | |
| If there are no non-app Designer objects in an archive set, DMS scripts will not be generated on migration. Previous versions of Stat generated a script with just header information. | CR0229164 | |
| Oracle E-Business Suite |
Cannot apply Oracle Apps patch in Oracle RAC environment. The connection string for Oracle Apps and the Stat environment has been modified to support RAC environments. The connection string has been modified to use [SERVICE_NAME] instead of [SID]. In addition, the environment connection maintenance values for service name need to be service name, not SID. |
CR0086483 |
|
Fixed a minor typo in the error message that occurs when a working directory has not been defined |
CR0089918 | |
|
The Oracle agent's working directory will be validated when the OA agent is started. |
CR0089923 | |
|
The Oracle E-Business object type of EXE was failing on archive/migration in multi-node environments because all of the agents were trying to process the object. The Oracle agent has been modified to look specifically for the bin directory. If it doesn't exist on a node, then the archive/migration will complete without error. |
CR0190971 | |
|
Multi-node OA environments: improvements have been made to Oracle agent processing in the area of the order of servers acknowledging successful archive |
CR0190984 | |
|
The Oracle TAR is a 15 digit number with a 3 digit decimal field. Sites where regional settings dictate the decimal separator to be a comma could not enter data into this field. The field has been modified to be alphanumeric with a mask that requires a period in the 4th space from the right. |
CR0201569 | |
|
The ORA-0001 Constraint Violation message that can occur when adding undocumented OA patches has been modified to be more user friendly |
CR0207039 | |
|
OraApps Report Request Sets - Report Request Set link added as a seeded object type. Previously available in hotfix in February 2007. |
CR0207205 | |
|
A Unique Constraint Error was generated on the merc_oa_event table when the sequence id exceeds 32767. The sequence is now tracked as a number rather than an integer. This was previously available as a hotfix to 5.2.2. |
CR0207677 | |
|
The CSR_PS_SWAT_LOG.LOGOBJECT column has been lengthened to hold 8 characters |
CR0208932 | |
| A new report has been added for Oracle E-Business migration paths. | CR0211027 | |
|
Responsibility object type was not archived or migrated if Responsibility key had a space. This has been corrected. |
CR0215082 | |
|
Re-Apply Patch status was not reflected on the "Transfer Rule" of workflow. This has been corrected. |
CR0215783 | |
|
The order that a patch object vs an AOL object are added to a CSR no longer affects what will display in the CSR window. |
CR0218588 | |
|
Maintenance mode changes when rescheduling a patch. Users can now select the mode to be used when the patch is reapplied. |
CR0223964 | |
| The patch schedule window will display the patch options stored on the patch inventory window and then allow the user to modify those options to suit the apply scenario. | CR0224766 | |
| The manual update of Patch Status has been modified to update the patch status on workflow correctly. | CR0224301 | |
|
Object fetch from Windows client not initially loading on some workstations. This is memory dependent. Installshield will now set the memory value for Powerbuilder to -Xmx480m. |
CR0226211 | |
|
A new environment parameter has been created for the Oracle agent stat.conf files to allow echo/off to be set. Then parameter is envCode.sqlplus_options:-s. |
CR0226214 | |
|
The "username.log" file created during a migration no longer references a "staging" database when the migration is of Oracle E-Business objects or file objects. |
CR0227990 |
The following is a list of issues addressed and enhancements implemented in this release of Stat.
|
Feature |
Resolved Issue |
Change Request |
| General | You may experience problems viewing a Multi-CSR report through the Report Library Viewer if the Description and Resolution fields contain a large amount of data, resulting in display overlap. Increase the window size or zoom out to correct the display. |
N/A |
If the Global Task Query is modified, users may not be able to view Tasks on a CSR and Auto-Tasks may not be created. Do not modify the Global Tasks Query to include additional filters other than what it is delivered with. Users can save their own copy of the Global Task Filter under a different name and add filters to that copy. |
N/A |
CSR templates created in the Stat Windows client are not supported in Stat Web. However, if you want to replicate a CSR template created in the Stat Windows client in Stat Web, open a CSR in Stat Web that was originally created with that template in the Stat Windows client and then save that CSR as a template in Stat Web. |
CR0087125 |
(S)FTP servers configured to accept DOS-style pathnames (e.g., C:\ftproot) are not recognized by the Stat Agent during archive and migration operations. FTP servers configured for use with Stat should be configured to use Unix-style pathnames. |
CR0090767 |
Stat Web: File attachments on a CSR prior to 5.2 using the Stat Web Client can only be deleted in the Stat Web Client. Attachments added in either client in 5.2 can be deleted in either client. |
CR0138266 |
|
Weblogic 9.2 is included in PeopleTools 8.49. Note: The Weblogic agent is not available in release 5.4.0. It will follow in a patch release and will support Weblogic 9.2. |
CR0217321 | |
| PeopleSoft | If you are running PeopleSoft v. 7 on Oracle and Stat on Sql Server, you may experience problems when comparing objects that contain blobs with no data. |
CR0132620 |
For PeopleSoft running on DB2, object definitions that contain an ellipsis character (...) cannot be archived or migrated. |
CR0082311 |
The Applied checkbox on the Dependency tab gets populated by clicking Calculate. The Calculate process analyses the PeopleSoft database's message log table. When a maintenance project is copied to a PS database, the update ids get inserted into this table. Prior to PS 8.45, the population of this table only works when importing a project from a file. |
CR0114270 |
| When using an Application Designer project to copy a Business Process that already exists in the target database, the Business Process property comments are not getting copied over to the target database | CR0126176 | |
| Large HTML objects may be copied correctly during a project migration but are not flagged as Done by Application Designer. Therefore, when Stat validates the project execution it reports the objects as not copied. The migrator should review the project in the staging database and validate whether or not the HTML objects were copied correctly to the target database. If they were copied correctly, the migrator can set the Done flags on the project in the staging db and then click on the Project Executed box on the migration wizard. A case has been logged with Oracle-Peoplesoft to determine why the Done flags are not being set. As of the release date of 5.4.0 that case was in a Pending Resolution status. | CR00228785 | |
| Archive Set Purge wizard may orphan object rows in Stat if the archive set was created against one version of Peopletools and the source database has since been upgraded to a different release. | CR0229807 | |
|
Oracle E-Business Suite |
When Stat processes an impact analysis request on a patch, it checks if an object was added to an interim or final archive set to determine if it is a custom object. If all interim and final archive sets that reference an object are deleted, the impact report will not identify the impacted object as customized. |
CR0080786 |
With RAC configurations for Oracle E-Business Suite databases, it may be necessary to disable Stat validation of the database name reported by AutoPatch. This validation can be disabled by setting the ._disable_autopatch_dbvalidation parameter to Y in the stat.conf configuration file for each Stat Agent for Oracle Apps. |
CR0086483 |
Due to a bug in version 115.1 of Oracle's LCT file used by Stat for the "AOL Forms Custom Rules" object type, customers must apply patch 4244166. Without this patch, customers will not be able to use Stat's change management capabilities for this object type. |
CR0139989 |
The following is a list of third party issues known to exist at the time of this release.
| For Windows XP SP2 users, when you perform a FTP or SFTP function in Stat, you receive a Windows message that the function is being blocked for security reasons. The message asks if you want to continue blocking or stop blocking. If you choose to stop blocking, the FTP/SFTP function works as designed. If you choose to continue blocking, the FTP/SFTP function will not work. |
CR0085945 |
| When using an Application Designer project to copy a Business Process that already exists in the target database, the Business Process property comments are not getting copied over to the target database. This issue is resolved in PeopleTools 8.46. | CR0126176 |
| Large HTML objects may be copied correctly during a project migration but are not flagged as Done by Application Designer. Therefore, when Stat validates the project execution it reports the objects as not copied. The migrator should review the project in the staging database and validate whether or not the HTML objects were copied correctly to the target database. If they were copied correctly, the migrator can set the Done flags on the project in the staging db and then click on the Project Executed box on the migration wizard. A case has been logged with Oracle-Peoplesoft to determine why the Done flags are not being set. As of the release date of 5.4.0 that case was in a Pending Resolution status. | CR00228785 |
| The dropdown list of object types that can be opened in App Designer is not consistent in PeopleTools 8.48 and 8.49. Some objects may not open correctly and it will vary depending on whether or not App Designer is left open on the workstation or closed each time. A case has been logged with PeopleSoft. | CR00230147 |
For information on upgrading Stat 5.3.x to version 5.4.0, see the 5.4.Upgrade Notes.pdf document included with this release.
Before installing Stat, ensure your system meets the following minimum hardware and software requirements:
| DBMS | Oracle: 9i version 9.0.1 and higher, 10g version 10.1.0.2 and higher (Unicode and non-Unicode support for all Oracle DBMS) MS SQL Server: 2000, 2005 (Unicode and non-Unicode: ISO Character Set with Unicode collation. Database defined with BINARY collation) Note: If you are running Stat on Microsoft SQL Server and your PeopleTools environment is 8.48 or higher, Stat must be on MSS 2005, regardless of the PeopleTools platform. Also, If PeopleSoft is configured for Unicode operation, the Stat database must be as well. |
| Hardware Requirements | Hardware independent. Must support Oracle or SQL Server. |
| Minimum Requirements | Development database: 4 GB Production database: 20 GB (size can grow dramatically) |
| Operating System | Windows 2000, Windows XP Professional (current SP recommended), and Windows Vista |
| Database Connectivity | Oracle: 9,
10 MS SQL Server: SQL Server 2000 client, 2005 client |
| Minimum Requirements | 866 MHz, 256 Mb RAM per user on same machine Disk: 500 Mb for local install (recommended) or <1 Mb w/network install with 500 Mb on the network |
| Operating System and JDK/SDK | Standalone configuration (recommended): Windows 2000 Server SP2, XP Professional, 2003 Server, Red Hat Enterprise Linux release 4 and 5, Solaris 8, Solaris 9, Solaris 10, HPUX 11.11 or 64bit AIX v5.2 or 5.3(all English-based) WebLogic configuration (optional): The Stat agent on WebLogic is not yet supported in version 5.4. WebLogic 9.2 will be supported in the next patch release of Stat 5.4, at which point WebLogic 8.1 will no longer be supported. Note: References to WebLogic in all Stat 5.4 documentation should be disregarded until support is available. |
| Minimum Requirements | 1 GHz (2GHz recommended for 20+ users) Pentium 4 (or
equivalent) RAM: 512 MB (2 GB recommended for 20+ users) DISK: 1 GB |
| SSH Server Encryption | The Stat Server currently supports the following cipher and
MAC configurations: Ciphers: Message Authentication Code (MAC): |
| Web Browser | Microsoft Internet Explorer (Windows) Versions 5.5 and 6.0 |
| Supported protocols: Outbound e-mail-SMTP, Inbound e-mail- IMAP4 and POP3 |
| PeopleTools Applications | Supports all applications that are certified by PeopleSoft to run on the following PeopleTools versions: v7.0 (all versions), v7.5 (all versions), v8.0-v8.22, and v8.4-v8.49. |
| PeopleSoft Applications | Supports all PeopleSoft Applications built on PeopleTools,
including but not limited to the following: |
| Oracle | Oracle 8i, 9i and 10g (Unicode and non-Unicode) Connectivity: Oracle Client 9i |
| MS SQL Server | 2000, 2005 (Unicode and non-Unicode: ISO Character Set
with Unicode collation. Database defined with BINARY collation)
Connectivity: SQL Server 7.0, 2000 client, 2005 client. Note: PeopleTools 8.48 and higher require Stat to be running on SQL Server 2005. |
| Sybase | ASE 12 (Unicode and non-Unicode) Connectivity: Sybase ASE ODBC client |
| DB2 | DB2 UDB for AIX V7.2, V8.2 (Unicode and non-Unicode) DB2
UDB for OS/390 v6.1, DB2 UDB for z/OS & OS/390 v7.1 (non-Unicode
only) Connectivity: DB2 Connect 7 FixPak 6 or later (for DB2 v7), DB2 Connect 8 FixPak 6 or later (for DB2 v8) Note: Stat supports the locking, archival and migration of all PeopleSoft Unicode data. Character sets other than Western cannot be entered directly into Stat through the Stat GUI interface. Also, Stat features are available for use in a Unicode environment except for File Object Impact Analysis and File Compare & Merge. |
| Releases | Stat supports all products, including custom products, in the Oracle's E-Business Suite Release 11i and 12. Some Stat features will depend on the AD product release. |
| Technology Stack | All components of the technology stack for the Oracle E-Business Suite should be in compliance with Oracle's certification requirements |
| Stat Oracle Agent - Hardware Platforms | All versions of Sun SOLARIS, HP-UX, AIX, Linux and Windows certified with Oracle E-Business Suite. Stat will be certified with most UNIX and Intel based platforms supported by Oracle. Contact Quest Software for updated platform certification. |
| Developer Object Compare | Oracle developer object comparison is an optional feature
with its own requirements. To enable object compare support for Oracle
developer objects, a compatible version of Oracle Developer and the Forms
Applet Jar Files component of the Oracle Forms product must be installed.
Additional requirements are needed for the following:
|
| Requirements | Must be NT, Unix, MVS or Netware compatible; SSH2 must use
standard format listing; OpenSSH (UNIX and Windows), SSH Communications
Corp. (UNIX and Windows), bitwise WinSSHD, and wodSSHServer are supported.
VanDyke VShell 2.1 is NOT supported. The configuration of your SSH server determines which ciphers are used when connecting to the Stat Server. The Stat Server currently supports the following cipher and MAC configurations: Ciphers: Message Authentication Code (MAC): |
The Stat release package contains the following products:
For information on installing Stat 5.4.0 see the Installation Guide included with this release.
| info@quest.com | |
| Quest Software, Inc. World Headquarters 5 Polaris Way Aliso Viejo, CA 92656 USA | |
| Web |
Refer to our Web site for regional and international office information.
Quest Support is available to customers who have a trial version of a Quest
product or who have purchased a commercial version and have a valid maintenance
contract.
Quest Support provides around the clock coverage with SupportLink,
our web self-service. Visit SupportLink at http://support.quest.com/.
From SupportLink, you can do the following:
View the Global Support Guide for a detailed explanation of support programs,
online services, contact information, and policy and procedures.
The guide
is available at: http://support.quest.com/pdfs/Global%20Support%20Guide.pdf.
This document contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written permission of Quest Software, Inc.
© 2008; Quest Software, Inc. ALL RIGHTS RESERVED.
Quest, Quest Software, the Quest Software logo, Aelita, AppAssure, Benchmark Factory, Big Brother, DataFactory, DeployDirector, ERDisk, Foglight, Funnel Web, I/Watch, Imceda, InLook, IntelliProfile, Internet Weather Report, InTrust, IT Dad, JClass, Jint, JProbe, LeccoTech, LiteSpeed, LiveReorg, NBSpool, NetBase, Npulse, PerformaSure, PL/Vision, Quest Central, RAPS, SharePlex, Sitraka, SmartAlarm, Spotlight, SQL LiteSpeed, SQL Navigator, SQLab, SQL Watch, Stat, Stat!, StealthCollect, Tag and Follow, Toad, T.O.A.D., Toad World, Vintela, Virtual DBA, Xaffire, and XRT are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. Other trademarks and registered trademarks used in this guide are property of their respective owners.
This product includes software developed by Apache Software Foundation, JCraft,Inc., James House, Pat Niemeyer, Teodor Danciu, Hypersonic SQL Group, CDS Networks, Wintertree Software Inc. and Microsoft GDI+.
If you have any questions regarding your potential use of this material, contact:
| Quest
Software World Headquarters LEGAL Dept 5 Polaris Way Aliso Viejo, CA 92656 Email: legal@quest.com |
The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document.