Post to WIP generates System Error - ORA-21000
search cancel

Post to WIP generates System Error - ORA-21000

book

Article ID: 97545

calendar_today

Updated On:

Products

Clarity PPM On Premise

Issue/Introduction

When I navigate to Home > Financial Management > Post to WIP page, enter a date range then click on 'Apply' > 'Post' button
I get 'System Error. Contact system administrator' no output is generated in log file. 

When I run a Post To Wip job then the following error gets generated in the bg-ca.log file.

ERROR 2018-05-22 13:01:26,914 [Dispatch Post to WIP : bg@serverexample (tenant=clarity)] niku.njs (clarity:admin:23250649__9590FC00-4FAC-4B3C-A3BF-24BD0A725488:Post to WIP) Error executing job: 5077036
com.niku.union.persistence.PersistenceException: 
SQL error code: 21000
Error message: [CA Clarity][Oracle JDBC Driver][Oracle]ORA-21000: error number argument to raise_application_error of -1 is out of range
ORA-06512: at "SCHEMA.PAC_PRC_POSTTOWIPS_SP", line 961
ORA-06512: at "SCHEMA.PAC_PRC_POSTTOWIP_JOB_SP", line 201
ORA-06512: at "SCHEMA.PAC_PRC_POSTTOWIP_JOB_SP", line 201
ORA-06512: at line 1

Cause

The stored procedure 'PAC_PRC_POSTTOWIPS_SP' is erroring when attempting to insert data into the tables: PPA_WIP and PPA_WIP_VALUES

This could be because of wrong filtering, or database sequencing error, or environmental issue

Resolution

  • The initial step to try is to provide a  "From Date" and "To Date" in the Home > Financial Management > Post to WIP page filter.
  • Per documentation, it states: If you do not enter any dates (start date or end date), all available transactions from any past date are pulled up to the current (today’s) date. So, to post any available transactions with a future date you must specify an end date:
    Set Up Financial Transactions, Voucher Headers, and WIP Adjustments
  • If you specified the dates correctly:
    • Check the database table/sequences can be reviewed as per Sequences Issue with Clarity Database after Refresh
    • Also check if there are any other jobs that are failing such as the Post Timesheets or Post Transactions to Financials, where there is another underlying database issue such as memory.