My Oracle Support Banner

OSM 7.0.3 P22 - Scheduled Order Purge Not Working (Doc ID 1668681.1)

Last updated on MARCH 27, 2019

Applies to:

Oracle Communications Order and Service Management - Version 7.0.3 and later
Information in this document applies to any platform.


What causes the error below when running a scheduled orderPurge?


The execution:
orderPurge ./config/config_uat.xml schedulePurge "purge_before=2013-05-07T0:0:0 CST" "order_states=ALL" "namespace=ALL" "version=ALL" "start_date=2014-03-13T11:00:00 CST" "stop_date=2014-03-13T11:10:00 CST"

ORA-12012: error on auto execute of job 65345284
ORA-06550: line 1, column 285:
PLS-00103: Encountered the symbol ",10); :mydate := next_date; IF broken THEN :b := 1; ELSE :b := 0" when expecting one of the following:

  ( - + case mod new not null
  continue avg count current exists max min prior sql stddev
  sum variance execute forall merge time timestamp interval

  Thu Mar 13 11:00:56 2014
Thread 1 advanced to log sequence 244968 (LGWR switch)
  Current log# 6 seq# 244968 mem# 0: +RDO_DBQ383/dbq383/onlinelog/group_6.261.768581321
Thu Mar 13 11:00:56 2014
Archived Log entry 243084 added for thread 1 sequence 244967 ID 0xffffffff83f60205 dest 1:
Thu Mar 13 11:02:00 2014

Executing orderPurge ./config/config_uat.xml after the expired date results in:
Starting to list pending order purges ...



To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.