This is not the case. These are brand new joins that have never used. We have 
validated that the views are there. 

This appears to be a bug in Remedy and how it handles this nested join with the 
Remedy User tool.

The join does not have any issues when called from outside of the Remedy User 
tool(i.e. direct Database level queries to that very same nested join).

 
Christopher Pruitt 
Consultant Specialist
EDS - Bank of America
I3-Inventory IW Infrastructure Team
Phone: +1-972-605-7702 (8-835) 
mailto:[EMAIL PROTECTED]
 
Confidentiality Notice: This message and any files transmitted with it are 
intended for the sole use of the entity or individual to whom it is addressed, 
and may contain information that is confidential, privileged, and exempt from 
disclosure under applicable law. If you are not the intended addressee for this 
e-mail, you are hereby notified that any copying, distribution, or 
dissemination of this e-mail is strictly prohibited. If you have received this 
e-mail in error, please immediately destroy, erase, or discard this message. 
Please notify the sender immediately by return e-mail if you have received this 
e-mail by mistake.

________________________________

From: Action Request System discussion list(ARSList) on behalf of Opela, Gary L 
Contr OC-ALC/ITMA
Sent: Mon 2/12/2007 4:00 PM
To: [email protected]
Subject: Re: ARERR (302) Entry does not exist in database dilemma


** 

It sounds like one of your remedy views has gotten dropped.

 

Since your remedy joins are on the views, and your oracle sql you are running 
is against the t-tables, this would agree.

 


Additionally, in the past, whenever I have had join forms that would return 
results list, but then no actual ticket data in the details section of the user 
tool window, it was always because a view form was dropped.


Try opening up each of the view forms in the user tool to make sure they all 
exist. Additionally, you might check on the database level to make sure the 
view forms are there.

 

I know that it can get tricky whenever you have nested joins. If you do 
something that causes one of the lowest level joins to be rebuilt, then you run 
the risk of remedy not properly rebuilding all joins.

 

Example:

 

                 A

     B                       C

                         D        E

 

Where A is a join of B and C, and C is a join of D and E, I've seen in the past 
where you modify form E that causes the view to be dropped/recreated, and 
occastionally A will get dropped. This gets tricky if you have other forms that 
are joins of A and, say, F, then you don't have the visibility to see that A is 
broken.

 

Check this out to see if it is the problem. This is the easiest to fix: just 
find the broken join form, open it up in admin tool, move a field and hit save.

 

If all of your forms are SQL views, then you will need to re-run your sql query 
to rebuild the view. Start at the bottom so you don't re-break everything once 
you're finished.

 

________________________________

From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] 
On Behalf Of Pruitt, Christopher J
Sent: Monday, February 12, 2007 3:48 PM
To: [email protected]
Subject: ARERR (302) Entry does not exist in database dilemma

 

I have a question that has now stumped several DBAs and Remedy Developers now 
and was hoping someone on this list may have a answer.

We have a Join that is nested with other joins, however, when we perform a 
query via the Remedy User tool it returns an "ARERR (302) Entry does not exist 
in database".

To make matters worse, on the User Tool it returns 792 records of which 60% 
display this error and the remaining 40% do not and before anyone says there 
are missing records. We have 3 primary data forms included in these joins and 
all of them have the corrected and needed data in them.

Now here is the issue. When we perform the same query at the Oracle level it 
returns all the records correctly. 

This is the query that is run from the Remedy User Tool (when I turn on SQL and 
API logging).
SELECT aradmin.T5092.C1,C8 FROM aradmin.T5092 WHERE (E0 = 'ACI-00000001025' and 
E1 = 'LOC000000005915' and E2 IS NULL and E3 = 'EBL-00000000590' ) ORDER BY 1 
ASC

It returns no record 
However, when I modify the query based on the structure of our Join it returns 
the record. 
SELECT aradmin.T5092.C1,C8 FROM aradmin.T5092 WHERE (E0 = 'ACI-00000001025' and 
E1 = 'LOC000000005915' and E2 IS NULL and E3 IS NULL and E4 = 'EBL-00000000590' 
) ORDER BY 1 ASC

E0 and E1 are from the Tele_Location_Join and E2 and E3 should be from the 
Location RecType_Join and E4 should be from the Load Data Form, however, what 
is happening via the User Tool is E0 and E1 are from the Tele_Location_Join and 
E2 and E3 should be from the Location RecType_Join and it never includes the E4 
and the E3 value should be the E4 value and E3 should be null 

This is our Join Structure: 
Reporting_Form_Join 

An outer join of: 

        *       Charge_Join (Primary) 
        *       Load Data Form (Secondary) 

 

Charge_Join 

An outer join of: 

                *       Tele_Location_Join form (Primary) 

An inner join of: 

                        *       Tele Data form (Primary) 
                        *       Location Data form (Secondary) 

                *       Location RecType_Join (Secondary) 

An inner join of: 

                        *       Location Data form (Primary) 
                        *       Location Data form (Secondary) 

 

Our environment is: 
AR System: 6.03 patch 15 
Remedy User Tool: 6.03 patch 15 
Oracle 9i - ver 9.2.0.6.0 

Christopher Pruitt 
Consultant Specialist 
EDS - Bank of America 
I3-Inventory IW Infrastructure Team 
Phone: +1-972-605-7702 (8-835)  
mailto:HYPERLINK "mailto:[EMAIL PROTECTED]"[EMAIL PROTECTED] <mailto:HYPERLINK> 
 

Confidentiality Notice: This message and any files transmitted with it are 
intended for the sole use of the entity or individual to whom it is addressed, 
and may contain information that is confidential, privileged, and exempt from 
disclosure under applicable law. If you are not the intended addressee for this 
e-mail, you are hereby notified that any copying, distribution, or 
dissemination of this e-mail is strictly prohibited. If you have received this 
e-mail in error, please immediately destroy, erase, or discard this message. 
Please notify the sender immediately by return e-mail if you have received this 
e-mail by mistake.

__20060125_______________________This posting was submitted with HTML in it___ 
__20060125_______________________This posting was submitted with HTML in it___

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the 
Answers Are"

Reply via email to