My Oracle Support Banner

Troubleshooting Install Base Operating Unit Access Restrictions (Doc ID 1513838.1)

Last updated on DECEMBER 04, 2019

Applies to:

Oracle Installed Base - Version 11.5.10 to 12.1.3 [Release 11.5 to 12.1]
Information in this document applies to any platform.


This note brings together the available information relating to implementing access restrictions to Install Base item instances by Operating Unit (OU). The note provides general information highlighting the way OU access restrictions are implemented in release 11i and release 12 of Install Base and goes though the various setups which are required. The note also provides steps to understand issues which may arise from this setup.

It is not uncommon for customers to log Service Requests complaining of issues with locating item instances in the Install Base user interface where the instance does exist in the CSI_ITEM_INSTANCES table and there are no errors for the instance in CSI_TXN_ERRORS. Often customers will say that in R12 they can find an instance using the old Oracle Installed Base User responsibility but are unable to find the same instance when searching using the new Oracle Install Base Agent User responsibility.

In most cases this is due to the difference in how the two responsibilities handle OU access restrictions.

Troubleshooting Steps

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Troubleshooting Steps
 Understanding Release 11i and Release 12 Install Base Responsibilities
 Understanding OU Access Restriction Setup In Release 11i
 Understanding OU Access Restriction Setup In Release 12
 Internally Owned or 'Loaner' Instances
 A Note About Counters
 A Few Useful Queries

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.