The 'Build Verity Index' Process (SAC_IDX_DATA) Fails with Error "Return: 904 - ORA-00904: "T2"."SETID": invalid identifier" when Run for the 'CS Documents' Source and Filtering Criteria have been Defined (Doc ID 2157564.1)

Last updated on SEPTEMBER 27, 2016

Applies to:

PeopleSoft Enterprise SCM Supplier Contract Management - Version 9.1 to 9.1 [Release 9]
Information in this document applies to any platform.

Symptoms

The 'Build Verity Index' process (SAC_IDX_DATA) (navigation: Supplier Contracts, Search Content, Build Search Index) fails with the below error when run for the 'CS Documents' Source and Filtering Criteria have been defined.

SQL error. Function: SQLExec

Error Position: 523

Return: 904 - ORA-00904: "T2"."SETID": invalid identifier

Statement: insert into ps_cs_doc_att_tbl (cs_doc_id, cs_doc_type, scm_attach_id, att_version, attach_descr, comments_254, ext_flag, filename, file_extension, oprid, datetime_stamp, cs_import_flg) select h.cs_doc_id, f.cs_doc_type, f.scm_attach_id, f.att_version, ' ', ' ', 'n', ' ', ' ', ' ', null, f.cs_import_flg from ps_cs_doc_hdr h, ps_cs_doc_files f, ps_cs_doc_date_tmp t1 where h.cs_doc_id = f.cs_doc_id and h.cs_doc_id = t1.cs_doc_id and (t2.setid='share') or (t1.setid='share') or (t3.setid='share') or (t1.setid='share') or (T2.SETID='SHARE')

Original Statement: %InsertSelect(CS_DOC_ATT_TBL, CS_DOC_HDR H, CS_DOC_FILES F, CS_DOC_DATE_TMP T1) FROM PS_CS_DOC_HDR H, PS_CS_DOC_FILES F, PS_CS_DOC_DATE_TMP T1 WHERE %Join(COMMON_KEYS,CS_DOC_HDR H, CS_DOC_FILES F) AND %Join(COMMON_KEYS,CS_DOC_HDR H, CS_DOC_DATE_TMP T1) AND (T2.SETID='SHARE') OR (T1.SETID='SHARE') OR (T3.SETID='SHARE') OR (T1.SETID='SHARE') OR (T2.SETID='SHARE')
2016-02-16-12.49.07.924314 AePcdExecutePeopleCode [188] Exception logged: RC=100.
2016-02-16-12.49.07.924314 GetNextStateRecord [68] Exception logged: RC=3.

SQL error in Exec. (2,280) SCM_CS_CONTENTS_SEARCH.Verity.Index.SearchIndexCommon.OnExecute Name:BuildData

Called from:SCM_CS_CONTENTS_SEARCH.Verity.Index.NewSearchIndex.OnExecute

 

Changes

 

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms