OnDemand Users Group

Support Forums => CMOD for Multiplatforms => Topic started by: pankaj.puranik on September 24, 2015, 06:51:48 AM

Title: Issue with search.
Post by: pankaj.puranik on September 24, 2015, 06:51:48 AM
I have this strange situation.
I have 2 pair of Application Group and Application.
Both the pairs are exactly same except for their names and retention periods.

The two application groups are mapped to the same folder.
The Folder to AG mapping is also the same for both application groups.

I then loaded the same document with same dates but with different account numbers.
Note that this is online upload using ODWEK.

When I do individual  search by account number (say account 123 and 456), I get the results from both the AGs in subsequent queries.
When I use the Account number and Date combination (say account 123 and date 20150924) I get the expected result.
When I use the Account number and Date combination (say account 456 and date 20150924) I get no results.
A search by just account number = 456, returns the result. On analyzing the result, I do see the date column populated with 20150924.

I am not able to understand the reason for no results when I use the Account number and date combination for AG1 while the same search combination returns results from AG2!!

Thanks
Pankaj.
Title: Re: Issue with search.
Post by: ewirtz on September 24, 2015, 07:33:35 AM
Hi Pankaj,

you could activate message 226 and look for the generated SQLs. Maybe this helps to see the difference between the different searches.

regards

Egon
Title: Re: Issue with search.
Post by: pankaj.puranik on September 24, 2015, 09:36:59 AM
Yeah I already checked that and there is no issue with the SQL at all.
Title: Re: Issue with search.
Post by: pankaj.puranik on September 28, 2015, 11:10:54 AM
Apparently there had been a bad date in the input data that caused the DOC START DATE in the ARSSEG table to be set to 0 which is an invalid arsdate value. This was causing the issue.
However just updating the ARSSEG table did not help.
I had to move the entire data from old AG to new AG.
I am sure that would be a better way of doing it. But since I did not had much time for R&D, just created a new AG and migrated data after removing the entry that had a bad date.