Chat now with support
Chat with Support

Stat 6.1 - 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: Stat Web Services Appendix: Troubleshooting Chart Appendix: stat.conf Configuration Appendix: Custom Report Files

Stat Oracle Agent

 
Problem
Explanation/Solution

Could not find agent identifier for environment code.

The environment code name that is entered in the stat.conf file on the Stat OraApps computer has to exactly match (case sensitive) the Environment Cd value under Maintenance | General | Oracle Applications Connect.

Select Maintenance | General | Oracle Applications Connect and double-click the ENV in question or highlight it and click the Servers tab. The name of the server that is entered in Stat needs to be an exact match to the actual hostname of the host computer. To check the hostname, login to the host and type “hostname” at a command prompt. Then compare that hostname with the name that is entered in Stat. They need to be exactly the same.

If hostname does not work then enter the ip address.

Stat Central Agent connection unavailable
1
Verify the Stat Central Agent is up running.
2
Look at the stat.conf file and verify the stat.central_agent.server parameter. Is the hostname or ip address pointing to the correct stat central agent?
3
Query for select * from STAT_AGENT to get the central agent hostname and ip address. Pay attention to the hostname and ip address and compare this with the stat.conf file.
4
If the ip address returns 127.0.0.1 as the loopback address then have Network Admin verify what the ip address should be.
5
Modify the /etc/host file to have the additional ip address instead of just the loopback ip address.

ERROR - IOException : No more data to read from socket

This is a port error. Possibilities include:

•
Wrong port assigned
•
Firewall port closed
•
Some other application has grabbed the port

ERROR - Stat's working directory does not exist on server

FATAL - Fatal: Stat validation of environment failed. Unable to start Stat Oracle Agent
1
Login to Stat windows client and go to Maintenance | General | Oracle Applications Connect.
2
Highlight the desired Environment then open the Servers tab, scroll to the right and you will see the Working Directory column. Make sure you define the location of the working directory.

Login/Connection

 
Problem
Explanation/Solution

Receive the following error message when logging in:

“Unable to complete ‘First Pass’ login.... Invalid username/password.”

Verify that the login ID field in the Stat.ini is correct. Normally, this is “STATLOGIN.”

Verify that the STATLOGIN account is defined at the environment level.

Receive the following error message when logging in:

“Unable to complete ‘First Pass’ login.... DBMS (073/MSS) is not supported on your current installation.”

Re-install Stat, making sure that you install the appropriate native environment connectivity drivers.

Verify that the appropriate environment client software is installed on the workstation (i.e., SQL Net or SQL Server client).

In the case of Oracle, verify that the oracle/bin directory is part of the workstation’s path.

Receive the following error message when logging in:

“TNS: Could not resolve service name.”

Verify that the Server Name field in the Stat.ini file matches a valid TNSnames.ora entry

Receive the following error message when logging in:

“Unable to complete ‘Second Pass’ login.... Invalid user name/password....”

This error indicates that the LOGINID and/or LOGINPWD fields in the STAT_LOGIN table do not match those of the environment owner. Check the password in the stat.ini file.

Administrative Utilities

 
Problem
Explanation/Solution

Data Replicator:

After adding a new service domain using the Data Replicator, unable to access Applications in the Domain Specific menu and rceive the following error message:

“An application error has occurred. Please note the following information and notify the System Administrator. Error: (3) Array boundary exceeded, Winmenu: nvo_security_manager, Object: nvo_security_manager, Script: has right, Line: 21, Version 5.0.0 Click OK to continue…”

This error message indicates that the user has not been granted access to the newly added service domain. Contact your system administrator and request access to the new service domain. To grant a user access to a new service domain, refer to Chapter 3, “Stat Security.”

Users receive this error message when they have not been granted access to any service domains.

Stat INI File Editor:

Receive the following error message when attempting to save a record in the Stat INI File Editor: “Error: Some fields need to be completed!!!”

One of the fields in the Stat INI Editor has not been completed. All fields must contain a value with the exception of the Other DB Parms field.

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.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating