Showing results for 
Search instead for 
Did you mean: 

Performance issue with elaborate partition definition

Former Member
0 Kudos

Has anyone noticed a dramatic performance issue when a complex partition strategy is defined against an Oracle table?  I am running PowerDesigner 16.5.  I have a few tables that have monthly (12 months for 3 years right now) partitions and system code  (9 systems) subpartitions.  When I open the property window for these tables, it takes 2 or 3 minutes to respond.  And clicking among the tabs in the property window also takes 2 to 3 minutes to respond.  All other tables with more simplified partition strategy all open normally.

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

And it gets worse... now the check-in times to the repository (via direct or portal) are dramatically longer.  What used to take a few minutes... takes 45 minutes now...with a model that has an elaborate sub-partition strategy.  I am fearing I am at a dead end with this...

Former Member
0 Kudos

What specific version/EBF are you on? I'm running (4313)

I'd create an incident.

Former Member
0 Kudos

We are running 16.5 SP02  (  Yes, I think that creating an incident is the next step.

Former Member
0 Kudos

Hi Jonathan,

I opened incident 392323/2013 after we started experiencing difficulty opening table property sheets for tables with large numbers of partitions after upgrading from v15.3 to v16.1.

I received the following solution, which I considered to be a workaround -
If a table contains a huge number of partitions, then PowerDesigner will consume huge amount of
time to parse the partition information and put to the table's physical option tab.
To resolve the issue, you can use the following method:
1) Close PowerDesigner.
2) Open registry.
    Go to HKEY_CURRENT_USER\Software\Sybase\PowerDesigner 16\General
    Set (Default) to No
    Create a new value(32bit) PDMPhysOptionsTimeOut and set its vaule to 0
3) Restart PowerDesigner. Run check in.

The side effect is that partition data will not display in your table's property sheet.
If you still want to see the data in table's property sheet, you can set PDMPhysOptionsTimeOut= 2

Note PDMPhysOptionsTimeOut can be set from 0 to 5.
0 means do not parse partition other value means time out setting (wait for X second(s)).

After this, I received a note back from SAP indicating they had opened a technical escalation,
and that the issue was under review. I didn't realize that placed the incident back to Customer
Action, and it was subsequently confirmed automatically.

I later opened incident 76824/2014 when I had the same problem after upgrading to v16.5.3.0 (4284), because I had also gotten a new machine and thus lost the registry update.

I recently received the following reply, but I feel this is still a workaround, that I should not
have to update the registry. I'm hoping for a permanent fix.

Have you set up the time out registry key?
You need to add a registry key to provide a time out when opening the table properties.
Make certain PowerDesigner is closed before doing the following steps.
To create the Registry key:
1) Run Regedit.exe (start->run->regedit)
2) Navigate to HKEY_CURRENT_USERS\software\Sybase\PowerDesigner16\General
3) Add a new string by right clicking in the right pane and
    selecting New and select String Value
    Name the string value PDMPhysOptionsTimeOut
    Double click on the name of the string and
    enter a value between 2 and 5 for the number of seconds for the time out
     (this can be modified for your needs).
4) Exit the registry
5) Restart PowerDesigner

You will be able to edit the 'sql' of the physical options but in general the following will be true:
1) When parsing is cancelled or times out, the physical options text is displayed as plain text and
    all depending attributes are irrelevant and shown grayed out.
2) Criterion based on these attributes is evaluated to False (which may be a limitation for you).
3) The classical Physical option page is also changed to plain text field.
4) You are unable to modify the Physical Options for this object unless the table
    does not time out or unless you edit the 'sql'

Hope this helps.

What's your feeling on this? Should I consider updating the registry to be a fix?

0 Kudos

IMO this is a workaround


Active Contributor
0 Kudos

I agree, editing the registry is never a fix, only a work-around