Thanks everyone for your advice. Since we'll only need be concerned with a 
couple of views that won't change often creating a custom view is the approach 
we'll use.

Mark

From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of Shelston, Patrick
Sent: Thursday, January 23, 2014 12:46 PM
To: arslist@ARSLIST.ORG
Subject: Re: Namesake Views

**
This is what we do.

We just re-create the AR view into a custom view and manage it manually from 
that point forward.  For example, HPD_HELP_DESK would have a "stable" version 
called REPORTING__HPD_HELP_DESK (just be careful you don't exceed the maximum 
length of view names in your DB).

It's very easy to setup if you just copy/paste the view SQL and rename the name 
in the statement.

I had wanted to investigate triggers to regrant on CREATE VIEW statements, but 
never got around to it.

-Patrick

From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of LJ LongWing
Sent: Wednesday, January 22, 2014 2:55 PM
To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>
Subject: Re: Namesake Views

**
Mark,
The way we combated this particular issue was to actually create a new db view, 
one that is defined specifically for your purposes, and is not re-created after 
every form change.

On Wed, Jan 22, 2014 at 12:38 PM, Brittain, Mark 
<mbritt...@navisite.com<mailto:mbritt...@navisite.com>> wrote:
**
HI All,

The move from 6.3 (custom)  to 7.6 & ITSM always seems to have more surprises 
than I care to sustain. Anyway, I have a monitoring tool that queries the 
hpd_help_desk view. The monitoring tool is granted permission to the view using 
the command "grant select on aradmin.hpd_help_desk to monitoringtool;

Before today I did not know about these namesake views. Last night I added a 
field to the HPD:HelpD Desk and this query broke. Apparently there is a script 
that runs, deletes rather than updates the view and builds a new view. The 
result is any grants assigned to the view are wiped out.  After that monitoring 
tool could not query the view and the DatabaseError: ORA-00942: table or view 
does not exist was being returned.

One solution would be to grant the permission the monitoring tool anytime the 
view is rebuilt. Not my favorite approach. Has anyone run into this and come up 
with a better solution?

ARS 7.6.04
ITSM 7.6.04
Oracle 11

Thanks
Mark


Mark Brittain
Remedy Developer
ITILv3 Foundation, Continual Service Improvement
NaviSite, Inc. - A Time Warner Cable Company
mbritt...@navisite.com<mailto:mbritt...@navisite.com>
Office: 315.634.9337<tel:315.634.9337>
Mobile: 315.882.5360<tel:315.882.5360>
[cid:image001.gif@01CF183F.1E8E4400]


________________________________
This E-mail and any of its attachments may contain Time Warner Cable 
proprietary information, which is privileged, confidential, or subject to 
copyright belonging to Time Warner Cable. This E-mail is intended solely for 
the use of the individual or entity to which it is addressed. If you are not 
the intended recipient of this E-mail, you are hereby notified that any 
dissemination, distribution, copying, or action taken in relation to the 
contents of and attachments to this E-mail is strictly prohibited and may be 
unlawful. If you have received this E-mail in error, please notify the sender 
immediately and permanently delete the original and any copy of this E-mail and 
any printout.
_ARSlist: "Where the Answers Are" and have been for 20 years_

_ARSlist: "Where the Answers Are" and have been for 20 years_
_ARSlist: "Where the Answers Are" and have been for 20 years_

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

<<inline: image001.gif>>

Reply via email to