Operations on Table Instances

Oracle LSH has the following blinding-related object security operations on Table instances:

• Blind Break allows access to real data in a Table instance whose Blinding Status is currently either Blinded or Unblinded as follows:
  • If a user has Blind Break privileges on all blinded and unblinded Table instances that serve as a data source or target for a job, the user can run the job on real data to produce an output and/or write data to one or more target Table instances.
  • If a user has Blind Break privileges on all blinded and unblinded Table instances in the underlying Business Area, the user can view real data when he or she launches a data visualization tool such as Oracle Business Intelligence Enterprise Edition.
  • If a user has Blind Break privileges on a blinded or unblinded Table instance, the user can choose to view real data in the Table instance using the Browse Data feature.
  • If a user has Blind Break privileges on all blinded and unblinded Table instances mapped to a Program instance, the user can choose to view real data when he or she launches an integrated development environment (IDE) such as SAS to work on the Program instance.

    Note:

    The functionality described in the last two points is intended for Definers, and users must also have the LSH Definer application role to see the Applications tab in the user interface and use these features.
• Read Unblind allows access to real data in the Table instances in all the same situations as Blind Break above, but only if all the relevant Table instances have been unblinded.
• Read Data allows access only to dummy data in the blinded and unblinded Table instances in all the same situations as Blind Break above.
• Unblind allows the user to unblind and reblind Table instances.

  Note:

  Unblinding Table instances also requires the LSH Definer application role to see the Applications tab in the user interface.