After upgrading to Fuji, customers on Oracle may experience issues with creating ACLs for database views, or creating reports on database views. This stems from an issue with the sys_scope field in sys_metadata being a CHAR 32 datatype, which gets padded with whitespace to be 32 characters long and causes a join query to fail.

Steps to Reproduce

  1. Install Fuji on Oracle.
  2. Try to create an ACL using a database view as a table. Note that no database views appear in name drop-down.
  3. Try to create a report using a database view as the table. Note that no database views appear in table drop-down.


  1. Navigate to ACL.
  2. Click New.
  3. At the bottom right of the Name field, there is an arrow. Click the arrow to change from two drop-down selectors to a text box. Then, use normal ACL notation to create the ACLs you need:
    • database_view_name
    • database_view_name.*
    • database_view_name.field_name
    • etc.

For reports:

  1. Run the script below to create a "blank" report with a database view name as the table, which you can then edit as necessary.

r = new GlideRecord("sys_report");




This record is then created with a name as follows, which you can then search for and edit using standard report process:

user_name_goes_here: timestamp_of_record_creation_goes_here



Related Problem: PRB650194

Seen In

Fuji Patch 2 Hot Fix 1
Fuji Patch 8

Fixed In

Fuji Patch 11
Geneva Patch 1

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2015-12-21 13:19:19