Row Security Acting Differently or Different Environments

Hello all,

I have a client on Xe SP18 that is experiencing a unique error. They have split out processing on two UNIX enterprise servers, one for dev and system test and one for production. They have specified for a specific group a few company records that they want that user group to see using OW row security. When a report using company names is run in system test or dev, the row security does its job and filters out all of the companies but those that are specifically defined in row security. When the same report is run in production, ALL companies show up in the report and row security has no effect. This is opening up a pretty big security hole. We have built a full production package (C&S), but this did not help. Any suggestions would be appreciated!

Thanks,

Tony
[email protected]

Try refreshing the global tables and data dictionary specs on the Production
server (just delete them and they'll JITI down or use TAM FTP).


Colin

Re: RE: Row Security Acting Differently or Different Environments

Wouldn't the full server package handle this? The timestamps seem to jive.

Re: RE: Row Security Acting Differently or Different Environments

Tony,

actually Colin responded your question. Let me add another 1 cent.

What is a little confusing here is that a full client package clears out
the glbltbl, dddict and ddtext files for workstations. O full server
package does NOT do the same! If you look at the <serverpackage>\pack
directory on your DS you will NOT find any glbltbl.pak, dddict.pak nor
ddtext.pak.

I think it would be good practice to refresh these files on servers with
each full package, at least if any DD changes are involved at all.

Thanks, Gerd