I have designed a table that will be used to determine impact:
Impact Table
__________
Id
ProductID
ClientID
Data in this table looks like this:
ID ProductID ClientID
1 1 1
2 NULL 2
Product ID maps to the Instance ID in AST:BusinessService and ClientID maps to
AST:Organization. We have scenerios where a Client can be impacted but no
products are actually affected. In order to do this I have to use outer joins.
AST:BusinessService is outer joined to Impact table. The resulting
AST:BusinessServiceToImpactTable_Join form is then outer joined to
AST:Organization. So the data for example would look like this:
RequestID ProductName Product ID ClientName
Client ID
1|1|1 Product1 1
Client1 1
2|NULL|2 NULL NULL Client2
2
**Note the "NULL" values are actual NULLs and not the word "NULL". The two
joins exist just to pull in the names.
The problem I am encountering is this:
If I select the "2|NULL|2" record the arserverd will do a hard crash. In my
opinion this is a Remedy bug. It should allow for outer joins like this.
Here is an actual request ID of a join form that is causing the crash:
000000000000197||000000000018595|000000000021403|000000000018595|000000000021403
Notice the "||"????
I am doing it this way to normalize the data. I shouldn't have to copy the
names into my impact table. That makes no sense to me but I do have a
workaround (Oracle View).
I am on ARS 7.01 patch 6 (Linux) on Oracle 10g. Has anyone encountered this
issue before and if so do they know if there is a later patch that fixes it?
Thanks,
Sean
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
