PB 12.5.1 Build 4015
When going into the DW SQL Painter PB will execute the following Constraint Select:
SELECT SYS.ALL_CONS_COLUMNS.COLUMN_NAME, SYS.ALL_CONSTRAINTS.CONSTRAINT_NAME FROM SYS.ALL_CONSTRAINTS, SYS.ALL_CONS_COLUMNS WHERE ....
These selects will cause my DW to not return for minutes. Is it possible to tell PB NOT to execute the Constraint Select when going into the DW SQL Painter or is there a way to have it use a different table instead of the SYS ones? I might understand why it needs it for Graphics mode but I am in Syntax mode.
Hopefully someone has a workaround for this because I am getting really tired of waiting minutes every time I go into the SQL.
Thanks,
Chris Craft
4 Answers
-
Former MemberPosted on Nov 21, 2014 at 08:50 PMChris,
You did not mention Oracle version nor way you connect to it.
Did you try to run this sql from sqlplus? Might be you need some stats being refreshed.Have you checked explain plan for this sql?
I must admit sometimes I just modify sql in Edit source, if there's not many changes it might work.
Add a comment
-
Posted on Nov 24, 2014 at 01:54 PM
Try to execute this Oracle command at the schema level for the SYS owner:
exec dbms_stats.gather_schema_stats(ownname => ‘SYS’,cascade => TRUE);
Add a comment
-
Former MemberPosted on Dec 09, 2014 at 02:27 PM
Have you looked at the PBODB125.ini file?
In the [Rdb_SYNTAX] section there exists a PBFKeyListSyntax item. It's contents are only place in the entire file with the word "CONSTRAINTS" (plural) in it.
Try commenting out the line completely, or making a copy of the line to try changes to it to see what you can make happen. Just make sure you comment out the original. A comment is a semi-colon at the beginning of the line ";".
Add a comment
Add a comment