PL/SQL Version 13.0.6.1911 (64 bit) slow opening and typing.

[bciwmac]

When opening PL/SQL Developer 13.0.6.1911 (64 bit) it is very slow to open. I sign in and open a new window and type a simple query. What I am typing does not show up on the screen for 15 seconds. The select statement only has 28 characters. When I hit execute, the expected reply does not show up. I do the same thing under PL/SQL Developer 12.0.7.1837 (32 bit) and it works fine (from the same machine) and is much faster. I don't have version 13.0.6.1911 (32 bit) installed, but have been told by a fellow employee that the 13.0.6.1911 (32 bit) version is working fine.

Can someone help me figure out why the 64 bit version is not behaving the same as the 32 bit version?

Thank you, Ian

 

[Marco Kalter]

To obtain some more diagnostic information, can you modify the PL/SQL Developer shortcut and add the DebugSQL parameter? For example:

"C:\Program Files\PLSQL Developer 13\plsqldev.exe" DebugSQL

Reproduce the problem and send me the debug.txt file that is generated in the %APPDATA%\PLSQL Developer 13 directory (e.g. C:\Users\\AppData\Roaming\PLSQL Developer 13).

 

[Tim Scott]

Marco,

Did you get your debug.txt?
I've finally got fed up with this problem and found a few things which pointed me specifically to plsdev ... and then found this!

What I've found is that in a command window for a large sql script (1,361kb, 27,013 lines) it's much slower than in a brand new command window.

Looking at the debug.txt, I could see that as I started to type the name of one of my packages (wod_general), followed by a '.' to have plsdev pop-up the list of variables, functions, procedures, ..., I could see that the program appears to pause before/at "FormResize":

00:06:23.454 CurrentStatement:
wod_general
;
00:06:24.034 TOracleQuery $0984C460 Start Query.Execute
SQL = select 'x' from dual
00:06:24.068 TOracleQuery $0984C460 End (1 record processed)
Duration = 0.031
00:06:46.428 FormResize
00:06:46.450 CurrentStatement:
wod_general.
;

If I type the same into a brand new command window, it works very quickly with virtually no perceptible delay. That's what pointed me here and away from the network, database, ...

I'll email support (at) allround... shortly, with a link to this discussion.

Thanks,
Tim

 

[bciwmac]

Hi Marco,

Sorry for the late reply to this Post. I thought that someone on our Desktop Team had run and loaded the Debug.txt file. I only noticed that it had not, when I created a new Post yesterday.

I started up plsqldev.exe DebugSQL and it took 18 seconds to get to the sign on screen to allow me to key my password.

Once I keyed my password, it tool 1 minute and 12 seconds for me to get into the tool with my user ID.

I then opened a new SQL window and typed:
select * from current_status; This took 27 seconds for the simple sentence to be put in the window before I could move over and press execute.

When I do the above in the 32 bit version, I don't have any issues.

Thank you,
Ian

PS, I have not found where I can add the Debug.txt file.

 

[bciwmac]

Is there anyway to attach the Debug.txt file that was requested? Or do I just email it to Support?

Thank you,
Ian

 

[Marco Kalter]

You can send it to support@allroundautomations.com.

 

[bciwmac]

Debug.txt file has been sent by email.

Thank you,
Ian

 

[bciwmac]

To update this post, when using version 13-64 Bit, I get to the login screen, it doesn't matter what I type for a user id, password or connections string, after I press enter, it says I am connected, but I am not really connected. Obviously, I don't see my session in the DB and when I look at the PL/SQL session, at the very top, I only get the @ and am not connected.

I have PL/SQL Developer 12 - 32 bit and it works fine. If I put garbage for the User ID, password or connection string, it returns an error and won't continue.

I had PL/SQL Developer 13 - 32 bit and it too works and it too gave an error when I put in the wrong information and wants valid credentials to be keyed before continuing.

Are other people having problems with the 64 bit install?

Thanks
Ian

 

[bciwmac]

Our desktop Technical team have figured this issue out and I will try to put in what they told me, just incase someone else comes across this. The issue came from the way the Oracle 12.1 64 bit client binaries were installed on the PC. If you are using custom install, which we did to give Oracle odbc drivers for Office queries, then we need to select the Oracle Net in the custom install order to make that connection (oracle doesn't install it as a required option). After they uninstalled the client binaries and re-installed them using the method found, all is working now.

 

[koja]

In my experience with PL/SQL Developer 13 there are 2 things that impact performance significantly:
1) Clipboard history: (Preferences - User Interface - Editor - Clipboard - Clipboard history) I disabled this.
2) Debugging: Preferences - Other - Support - Debugging. I set this to None.

Other option that sometimes impact startup performance is when option autosave desktop is enabled and windows with pinned connections try to connect to then unavailable databases...