Clarity: If nls_date_format is incorrect, you cannot filter for timesheets by prior time period or current time period as it throws a system error.

Products

• CLARITY PPM FOR ITG
• CLARITY PPM FEDERAL
• CA Identity Manager
• CA Identity Governance
• CA Identity Portal
• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

Description:

When trying to filter for a timesheet in a prior or current time period, a "System Error. Contact system administrator." error is thrown.

Solution:

Make sure the NLS_DATE_FORMAT is set to "YYYY-MM-DD HH24:MI:SS"

How-to:

1. Run the following SQL queries against your Databases:
   
   select 1 as id, parameter, value from nls_database_parameters
   where parameter = 'NLS_DATE_FORMAT'
   union
   select 2 as id, parameter, value from nls_instance_parameters
   where parameter = 'NLS_DATE_FORMAT'
   union
   select 3 as id, parameter, value from nls_session_parameters
   where parameter = 'NLS_DATE_FORMAT'
   
   
2. Log as sysdba and then run this query:
   
   alter system set nls_date_format="yyyy-mm-dd hh24:mi:ss" scope=spfile;
   
   
3. Restart Oracle Services.

For SQL Database:

The Clarity administration account must be added to the SQLAgentUserRole role (Microsoft SQL Server) in order to use the "SQL Server Agent" in Microsoft SQL Server 2005. Users added to the role will have the same SQL Server Agent experience as they had in SQL Server 2000. These users can create jobs and manage only jobs that they created. The SQL Server Enterprise Manager tool can be used to add the Clarity administrator to the SQLAgentUser Role role by using the following steps:

Here are the steps:

1. Login as 'sa' user
   
   
2. Open SQL Server 2005 Management Console
   
   
3. Open the Security folder
   
   
4. Open Logins folder
   
   
5. Right click on user SQLSERVER2005SQLAGENTUSER
   
   
6. Select Properties
   
   
7. Select User Mapping
   
   
8. Check Map box for MSDB Database
   
   
9. Confirm that the roles db_owner and public are checked
   
   
10. Right click on the Clarity schema owner, for example "niku"
    
    
11. Select Properties
    
    
12. Select User Mapping
    
    
13. Check Map box for MSDB Database
    
    
14. Confirm that the roles db_owner and public are checked
    
    
15. Click OK to save changes

Keywords: CLARITYKB, how-to, configuration.

Environment

Release: ESPCLA99000-12.1-Clarity-Extended Support Plus
Component: