caching of packages and objects for several schemes

Hi everybody,

We've got a very strange behavoir: we have created several schemes for different versions of our product. And now it seems, that the caching of packages / objecttypes is oracle-user independend.

take the following example ( package ):
- the frontend (fe) and the db are working fine with schema A

• I compile a buggy version of a package in schema B
• fe is still working fine on schema A
• I do a testing of the buggy package on schema B and get an error
• and now the fe is also getting the same error, even it's still working on schema A
• after logging into schema A and testing the correct code the frontend is working fine again
• ???

take the following example ( object ):
- in every schema is a object-type defined ( same name, same
declaration )
- internally we're using the object-type for a 'select cast ( ... )'

• in schema A I run a procedure and it's working fine
• if I run the same procedure in schema B I get an error 'insufficient privileges'
• additional hint: the 2 schema-owners don't have the 'execute any type'-privilege, because this is a requirement we need ( if they own this privilege, then it's working fine at least at the db )
• ???

The first problem might be a fe-problem, because when I'm working directly at the db the behavior is fine ... The second problem seems to be more a db-problem, because normally object-types should be 'global' ( isn't it, or why is it not possible to create a synonym for a object-type ? )

configuration:
Oracle 8.1.6
Bea Weblogic
Realm

Any ideas, bugfixes, workarrounds ? Thanx in advance. Tom Received on Wed Oct 24 2001 - 11:20:13 CDT