Query Builder isn't working

@paul harland No it just displays spinning wheel.

Thanks

Hi @Tj12 ,

My team is facing the same issue with no data in the query builder and spinning icon.

Do you have more details about how this issue was resolved? 

@Tj12 @ChaMylesC 

Good day to you both.

In our case we had an Operational Report developed by a third party and unfortunately the LU_NAME was around 27-28 characters however when converted to a DB_NAME it was taken of the maximum limit of 30.

This could be seen by opening the Logical Units view and populating, if this is the case an error will be displayed with the issue.

i.e.

ERROR MESSAGE

The client name  [XXShpmntHandlUnitLabelRep] is too long to be converted into a 30 character database name.

Regards

John

Hi @johnw66 and @ChaMylesC,

This error might be most probably caused due to Dictionary_SY_LU being corrupted as @Tj12mentioned.

I came across a similar issue and the observations are as follows,
1. There might be database objects in the dictionary more than 30 characters.

2. There might be LU_NAMES given in incorrect format, when converted to DB object name it would exceed the 30 character limit even though the actual database object deployed is within the 30 character limit.
eg: LU_NAME=XSAMPLESOrderReport, DB_OBJECT=XSAMPLE_ORDER_REPORT_RPT
Here, when converting the LU_NAME to DB_OBJECT name it generates, X_S_A_M_P_L_E_S_ORDER_REPORT_RPT which violates the 30 character limit.
Hence, the actual problem is with the incorrect standard used for the LU_NAME, and should be corrected as LU_NAME=XSamplesOrderReport

Execute the below script to see if there are any LU_NAME issues,

declare
  lu_name_ VARCHAR2(30);
  pck_     VARCHAR2(2000);
begin
  FOR rec_ IN (SELECT lu_name lu_name FROM dictionary_sys_tab) LOOP
    BEGIN
      lu_name_ := rec_.lu_name;
      pck_     := Dictionary_SYS.Get_Base_Package(lu_name_);
    EXCEPTION
      WHEN OTHERS THEN
        Dbms_Output.Put_line(lu_name_);
    END;
  END LOOP;
end;

If there's an output, you need to go to the database object and rectify the LU_NAME and fix the same in the harvest and if you decide to drop a package, make sure that you need to reflect this on your build home and harvest as well.

Thereafter, you could try performing a full Dictionary Storage rebuild with a cleanup.

Cheers !
Dhananjaya.