Chat now with support
Chat with Support

Stat 6.2 - System Administration Guide

Overview of Stat Administration Administrative Utilities Stat Security General Maintenance Tables
System Maintenance Service Domain Maintenance Department Maintenance Issue Tracking Maintenance Country Maintenance Customer Maintenance Object Type Maintenance PeopleSoft Environment Connection Maintenance Pre/Post Migration Steps Parameters Oracle Applications Configuration Oracle Applications Connection Maintenance Generic Application Connection Maintenance Schema Object Parameters Maintenance Data Object Maintenance PeopleSoft Search Configurations Stat Report Definition Maintenance Version Control Management Connection Maintenance
Service Domain-Specific Maintenance Configuring the Stat Central Agent Email Configuration Object Security Appendix: Sample Service Domain Configuration Appendix: User Class Rights Appendix: Creating a Staging Database Appendix: Database Tuning Appendix: Oracle Applications File Type Directory Appendix: Ports and Firewalls Appendix: REST Web Services API Appendix: SOAP-Based Web Services API Appendix: Troubleshooting Chart Appendix: stat.conf Configuration Appendix: Custom Report Files

CSRs

 
Problem
Explanation/Solution

CTRL+F Usage:

The CTRL+F keystroke that advances the user to the next entry field in the Description Tab of the CSR is not functioning.

This is caused when a space is inserted between the adjoining greater than/less than <> brackets in the Application/CSR Template. Access the template which is failing, and verify that no spaces exist between the two brackets.

Deleting CSRs:

Is there a way to delete CSRs from the environment?

With proper security rights, you can use the CSR Purge Wizard to permanently delete CSRs from the Stat Repository.

Before deleting a CSR, however, it is recommended that you first use the wizard to export the CSR to a file for backup purposes.

Deleting Objects and Archive Sets from CSRs:

How do I delete objects and archive sets from existing CSRs?

Please contact Quest Software Support for instructions on how to proceed.

CSR Locks:

After logging in to Stat, opened an existing CSR and received the following message: “This message has been locked by...”

This warning message indicates that the CSR is locked by the user noted in the message. You will also receive this error message when a user closes Stat and fails to close the CSR first. Ensure that all CSRs are closed prior to closing Stat. Not doing so will not remove the lock status in the environment and will cause this warning message to appear when another user tries to access the CSR.

The Read Project, Read CSR, Read File, and Add Objects buttons are greyed out in the Objects tab

The CSR may have a workflow that invokes object control, restricting the status where objects may be added to the CSR.

1
Open the workflow tab of the CSR.
2
Double-click on the current status.
If the Allow Object Add/lock rule exists, you should be able to add objects.

If the Allow Object Add/lock rule does not exist go to maintenance to determine if the overall Object Control feature is turned on.

1
Go to Maintenance | Domain Specific | Workflow.
2
Locate the workflow that the csr is using and look for the column called obj control. If this option is check then this functionality is enable.
3
Double-click on the workflow | right click at the workflow status and select status rule. If the option allow object add/lock is not check then the read csr, read project, add object will be grey out at that particular status of the workflow.
NOTE: If you do not want to use this feature then the obj control option need to be uncheck at the workflow level. Changes will be effective on new CSRs. Changes made now will not affect existing CSRs.

Stat Web

 
Problem
Explanation/Solution

For users running the Stat Central Agent on Unix, graphical workflow diagrams do not display properly in Stat Web.

This problem may occur when either:

•
The machine hosting the Stat Central Agent doesn’t have a windowing system installed in the operating system, as specified in the Stat system requirements
•
You are connecting to the Stat Central Agent using a telnet session that doesn’t have graphical display capability

The solution to the second case is to start the Stat Central Agent in a background mode through the telnet session. To do this, execute the following command:

./run.sh &

Archiving and Migrating

 
Problem
Explanation/Solution

Base Archive Sets:

Base archive set status remains stuck in In Process.

First, verify that the objects in the Base archive set are from the Base Object Source (Base Final). Also, verify that you selected the All on Migration Path radio button in the Lock in Environment box on the Objects tab in the PeopleSoft Change Management window.

A base archive set may remain in process if:

Any objects are locked in another CSR (for example, you have a reservation for an object in the Base database)

The Stat Central Agent lost connectivity to the environment and/or the network

There are no objects that can be archived for the base environment on the CSR.

Receive the following error in the archive log for PeopleSoft:

“Error creating SQL - [ERROR] Database is not available, please check db info”.
1
Confirm that the database is up and running.
2
Go to Maintenance | General | Peoplesoft Connect.
3
Hold down the ctrl key to select multiple PeopleSoft db for testing.

If you are getting error verify connection error--io exception: unknown host specified driver: oracle or verify connection error--listener refused the connection on the Central Agent Results, check the hostname, service name and db listener port settings in the Peoplesoft Connect window.

Receive a CSR error when migrating forms fmb object types.

Refer to the following for more information:

https://support.software.Quest.com/stat/kb/104980

Or

https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrlstate=agtl9ty5e_23&_afrLoop=138616630525556 (Oracle document 431324.1)

Printing

 
Problem
Explanation/Solution

When changing the printer (File | Print Setup) to generic text only, the font for the open description on CSRs changes to Roman 10cpi. This is the only available font listed until changing the printer back and re-opening the CSR.

Unfortunately, Stat has no control over font displays. This is a function of Windows. Similar behavior occurs in Microsoft Word.

Receive the following error message from the Stat Central Agent when printing a scheduled report “-9 error opening print job in Stat Central Agent scheduled report”

Verify that the printer to which you are trying to print your scheduled job exists on the machine where the Stat Central Agent is running. Also verify that the Host Printer name on the Stat Central Agent matches the printer name on the machine. For more information on the Stat Central Agent Printers, see Chapter 6, Configuring the Stat Central Agent .

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating