Problem with Win2008R2 64 Bit/Oracle 11.2.0.1 64 bit
Problem with Win2008R2 64 Bit/Oracle 11.2.0.1 64 bit
Hi,
I have installed the latest Studio version, it imported my connections from OraDeveloper tools just fine...
When I try to connect I get "Can't load oci.dll - use x32 version with x32 app"... when I try to make a new connection it says that it can't find tnsnames.ora and only displays "Instant Client" as Home...
ALL other apps (like OraDeveloper, SQL Developer, SQL Plus...) and libraries (like Devart dotconnect for Oracle...) work like a charm on this machine (Windows Server 2008 R2 64 Bit)... the installed Oracle client is 64 Bit...
Am I missing something ?
Thanks in advance
Yahia
I have installed the latest Studio version, it imported my connections from OraDeveloper tools just fine...
When I try to connect I get "Can't load oci.dll - use x32 version with x32 app"... when I try to make a new connection it says that it can't find tnsnames.ora and only displays "Instant Client" as Home...
ALL other apps (like OraDeveloper, SQL Developer, SQL Plus...) and libraries (like Devart dotconnect for Oracle...) work like a charm on this machine (Windows Server 2008 R2 64 Bit)... the installed Oracle client is 64 Bit...
Am I missing something ?
Thanks in advance
Yahia
Currently, we suggest you to use either 32-bit Oracle client software or Direct mode which doesn't require installation and administration of Oracle client software. Please refer to the 'Using Direct Mode' topic in dbForge Studio for Oracle help documentation for details.
Please note that Direct mode is not accessible in the Express edition of dbForge Studio for Oracle.
You can see the features list of dbForge Studio for Oracle editions here.
Please note that Direct mode is not accessible in the Express edition of dbForge Studio for Oracle.
You can see the features list of dbForge Studio for Oracle editions here.
I am on exactly one connection... this connection is with a RAC (=Real Application Cluster) with 3 nodes.
So the same DB is running on 3 nodes in parallel...
When I use
SELECT * FROM GV$SESSION
I can see all active session of all 3 nodes of this one DB.
When I go into dbForge / Administration / Monitor sessions I don't see all, I just see those that come up when I use SELECT * FROM V$SESSION .
Difference is that the latter only shows the sessions from the node I am connected to while the first SELECT shows all sessions for all 3 nodes of this DB.
My question is: How can I configure dbForge show me all sessions in the (one) DB I am connected to ?
Thanks in advance
Yahia
So the same DB is running on 3 nodes in parallel...
When I use
SELECT * FROM GV$SESSION
I can see all active session of all 3 nodes of this one DB.
When I go into dbForge / Administration / Monitor sessions I don't see all, I just see those that come up when I use SELECT * FROM V$SESSION .
Difference is that the latter only shows the sessions from the node I am connected to while the first SELECT shows all sessions for all 3 nodes of this DB.
My question is: How can I configure dbForge show me all sessions in the (one) DB I am connected to ?
Thanks in advance
Yahia
We've just reviewed your question once again and came to the conclusion that you have to click the 'Full session information' on the Session Manager toolbar to make all sessions display in the 'Session Manager' window since they are filtered once you open the 'Session Manager' window. Please let us know if this is what you asked for.
We have put some changes connected to this functionality to our development plan and will implement them shortly.
We have put some changes connected to this functionality to our development plan and will implement them shortly.
No - that still shows the same sessions but with a different set of columns...
Please check with a RAC with at least 2 nodes... The difference lies in the used view to gather the session information... in a RAC you need to use GV$SESSION instead of V$SESSION to get really ALL sessions from ALL nodes on the DB.
Please check with a RAC with at least 2 nodes... The difference lies in the used view to gather the session information... in a RAC you need to use GV$SESSION instead of V$SESSION to get really ALL sessions from ALL nodes on the DB.
Re: Problem with Win2008R2 64 Bit/Oracle 11.2.0.1 64 bit
any news on RAC support?
Re: Problem with Win2008R2 64 Bit/Oracle 11.2.0.1 64 bit
It's still in the queue for investigation.
Re: Problem with Win2008R2 64 Bit/Oracle 11.2.0.1 64 bit
3 years ago you wrote that this feature in on your ToDo-List for a future release...
It would be really helpfull to have at least a timeframe...
It would be really helpfull to have at least a timeframe...