PL/SQL Developer 11.0 64 bit released
2016-01-04 00:00
609 查看
System requirements |
PL/SQL Developer 11.0 64 bit can run on any 64 bit Windows system and is compatible with all Oracle Server versions. To connect to an Oracle database you need to have a 64 bit Oracle11g or Oracle12c Client installed. |
Upgrading from a 32 bit version |
The file formats of the 32 bit and 64 bit PL/SQL Developer versions are fully compatible. All files (SQL scripts, Programs, Reports, Diagrams, and so on) can be shared between the 32 bit and 64 bit versions. When using both versions on the same system all preferences and settings will also automatically be shared. To run both PL/SQL Developer 32 bit and 64 bit on the same 64 bit Windows system you need to install both a 32 bit and 64 bit Oracle Client. If you have full Oracle Client installations PL/SQL Developer will automatically find the correct 32 bit or 64 bit client in the registry. If however you have an Oracle Instant Client installation you may need to perform the following actions: Modify the PL/SQL Developer shortcut to add the InstantClient=<directory> parameter to indicate the directory where the instant client files are located. For example: "C:\Program Files\PLSQL Developer\plsqldev.exe" InstantClient=C:\Oracle\InstantClient64 or: "C:\Program Files (x86)\PLSQL Developer\plsqldev.exe" InstantClient=C:\Oracle\InstantClient32 Create a TNS_ADMIN environment variable to indicate the directory where the tnsnames.ora file is located. For example: TNS_ADMIN=C:\Oracle\Network\Admin Create an NLS_LANG environment variable to indicate the language, territory and character set. For example: NLS_LANG=AMERICAN_AMERICA.WE8MSWIN1252 The TNS_ADMIN and NLS_LANG environment variables are shared between the 32 bit and 64 bit Oracle Client. |
Plug-Ins |
The Plug-Ins provided on our web site are all 32 bit and can therefore only be used with the 32 bit version of PL/SQL Developer. The 64 bit package includes a 64 bit version of the standard Plug-Ins, and 64 bit versions of other Plug-Ins will be provided in the future. |
相关文章推荐
- Introduction to the SQL Server Analysis Services Logistic Regression Data Mining Algorithm
- MySQL数据库的优化–运维架构师必会高薪技能,笔者近六年来一线城市工作实战经验
- mysql架构方案
- MySQL高可用架构之MHA
- 使用zabbix全方位监控MySQL
- golang mysql中timestamp,datetime,int类型的区别与优劣
- MySQL Replication 常用架构
- 1209 - The MySQL server is running with the --read-only option so it cannot execute this statement
- 分布式MySQL数据库TDSQL架构分析
- django初体验之Error: No module named _sqlite
- Operation not allowed after ResultSet closed--操作mysql数据库
- linux下备份mysql数据库,并ftp到远程linux服务器上
- MySQL复制的管理和维护
- 美图秀秀DBA谈MySQL运维及优化
- Models and Algorithms behind Spark SQL
- cacti监控mysql 主从复制
- MySQL Server has gone away报错原因汇总
- mysql的学习笔记之loop(1)
- MySQL索引使用率监控
- 运维角度浅谈MySQL数据库优化