Oracle客户端安装配置文档
Oracle 10g 安装配置说明
Oracle 10g 安装配置说明一、安装1. 执行安装时提示：检查操作系统版本：必须是5.0，5.1，5.2 or 6.0。
实际为6.1，未通过，如图1图1需将安装目录下的oraparam.ini中[Certified Versions]修改为图2所示图2之后通过检查，如图3图32. 选择“高级安装”，点击“下一步”，如图4图43. 选择“企业版”，点击“下一步”，如图5图5图65. 勾选没有通过验证的两项，点击“下一步”，如图7图7图87. 选择“一般用途”，点击“下一步”，如图9图9图10 9. 默认设置，点击“下一步”，如图11图1110. 继续默认设置，点击“下一步”，如图12图1211. 默认设置，点击“下一步”，如图13图1312. 选择输入同一个口令“isofthome_123”，如图14图1413. 默认设置。
点击“下一步”，如图15图1514. 确认安装信息，点击“安装”，如图16图1615. 确认数据库创建信息，点击“确认”，如图17图1716. 完成安装，点击“退出”，如图18图18二、创建数据库1. 打开数据库创建程序（DBCA）2. 点击“下一步”3. 选择“创建数据库”，点击“下一步”4. 选择“一般用途”，点击“下一步”5. 输入全局数据库名“isoft”，点击“下一步”6. 默认设置，点击“下一步”7. 输入同一口令“isofthome_123”，点击“下一步”8. 默认设置，点击“下一步”9. 默认设置，点击“下一步”10. 继续默认设置，点击“下一步”11. 默认设置，点击“下一步”12. 点击“下一步”13. 点击“下一步”14. 点击“完成”15. 确认创建信息，点击“确定”16. 数据库创建完成，点击“退出”。
Oracle客户端安装步骤
Oracle客户端安装详细步骤，分为安装和配置两大块。
一安装1.进入client文件夹，如：“图1”所示。
（图1）2.鼠标双击，运行setup.exe文件。
如：“图2”所示。
（图2）3.耐心等一会，当出现下面界面是，如果你以前没装过Oracle，请单击下一步。
如：“图3”所示。
（图3）4.安装类型，选择管理员，请单击下一步。
如：“图4”所示。
（图4）5.指定你的Oracle想要装的地方，然后请单击下一步如：“图5”所示。
（图5）6. 请您注意了！！！请查看“检查”中的“状态”项，确保“状态”全部是成功。
然后，请单击下一步。
如：“图6”所示。
（图6）7.单击“安装”。
如：“图7”所示。
（图7）8.这是正在安装的时的画面。
如：“图8”所示。
（图8）9.安装完成后将出现下面的画面。
如：“图9”所示。
10.选择“执行典型配置”。
请单击“下一步”。
一直到“完成”。
如：“图10”,“图11”所示。
（图10）（图11）11.安装已经成功，请单击“退出”，并选择“是”。
如：“图12”，“图13”所示。
（图12）（图13）二配置1.如果不配置tasnames.ora文件，将会报错，如“图14”。
（图14）2.复制tasnames.ora文件。
如“图15”所示。
（图15）3.打开安装好的客户端的文件夹，如“图16”所示。
（图16）4.将第2步中复制的文件，粘贴到第3步所打开的文件夹。
如（图17）所示。
（图17）5. 在路径“C:\WINDOWS\system32\drivers\etc”中，打开用记事本打开HOSTS文件，如：“图18”,“图19”所示。
（图18）6.如果在打开的“HOSTS”中，没有下图中的蓝色部分，请你自己添加，后保存。
如：“图20”所示。
（图20）。
Oracle 官方安装文档
rpm -q grep binutils-2.* \elfutils-libelf-0.* \glibc-2.* \glibc-common-2.* \libaio-0.* \libgcc-4.* \libstdc++-4.* \make-3.* \compat-libstdc++-33 \elfutils-libelf-devel-0.* \glibc-devel-2.* \gcc-4.* \gcc-c++-4.* \libaio-devel-0.* \libstdc++-devel-4.* \unixODBC-2.* \unixODBC-devel-2.* \sysstat-7.*2.如缺少相应的补丁包，可以到系统安装盘安装相关的补丁包cd /media/Enterprise\ Linux\ dvd\ 20090127/Server/ rpm -Uvh grep binutils-2.*rpm -Uvh elfutils-libelf-0.*rpm -Uvh glibc-2.*rpm -Uvh glibc-common-2.*rpm -Uvh libaio-0.*rpm -Uvh libgcc-4.*rpm -Uvh libstdc++-4.*rpm -Uvh make-3.*rpm -Uvh compat-libstdc++-33rpm -Uvh elfutils-libelf-devel-0.*rpm -Uvh glibc-devel-2.*rpm -Uvh gcc-4.*rpm -Uvh gcc-c++-4.*rpm -Uvh libaio-devel-0.*rpm -Uvh libstdc++-devel-4.*rpm -Uvh unixODBC-2.*rpm -Uvh unixODBC-devel-2.*rpm -Uvh sysstat-7.*用户创建完了，这一步骤可以省略）# groupadd oinstall -g 501# groupadd dba -g 502# groupadd oper -g 503# useradd oracle -u 500 -g oinstall -G dba,oper# passwd oracle输入密码:oracle4.修改参数文件 sysctl.conf# cat >> /etc/sysctl.conf << EOFkernel.sem=1055 32000 100 128kernel.shmmax=2147483648kernel.shmall = 2097152net.ipv4.tcp_sack = 0net.ipv4.tcp_timestamps = 0net.ipv4.conf.default.rp_filter = 0net.core.optmem_max = 65535net.core.rmem_default = 4194304net.core.wmem_default = 262144net.core.rmem_max = 4194304net.core.wmem_max = 262144fs.file-max = 6553600net.ipv4.ip_local_port_range = 1024 65000EOF5.以下命令加载sysctl.conf文件中的内容，检查参数值是否正确设定。
oracle客户端安装指南(10g)
oracle客户端安装指南（Oracle 10g）注意：1.oracle客户端与oracle冲突，两者只能安装其一。
2.为进行说明的安装配置步骤按默认设置进行即可。
安装Oracle客户端为正常使用汇文客户端需要安装Oracle客户端，有两种安装方式，详细安装方式如下：除了下面提到的安装步骤外，其它的都用默认选项安装完成即可。
选择“自定义”安装方式选择下面的组件● Oracle Database Utilties● SQL * PLUS● Oracle Windows Interfaces● Oracle Net安装完成以后一般会自动弹出网络配置对话框，网络配置如下所述：配置连接Oracle数据库的网络服务名在Oracle客户端安装完成时，会出现配置网络服务名的界面，按照下面的方法进行配置：也可以通过“开始”●->“程序” ❍->“Oracle–OraClient10g_home1”■->“Configuration and Migration T ools”（配置和移植工具）■->“Net Configuration Assitant”配置连接Oracle数据库的网络服务名。
Net8 Configuration Assitant 的配置过程见下图1. 选择下一步2. 输入Oracle数据库的全局数据库名，一般是“orcl”3. 输入Oracle数据库的IP地址4. 输入网络服务名，可以任意填写，一般配置为“libsys”在完成上述配置后，运行SQL/PLUS看是否成功，如不成功则需手动配置监听。
手动配置监听步骤如下：1.开始- Oracle–OraClient10g_home1- Configuration and Migration Tools”（配置和移植工具）-Net Manager；这是服务器名配置完成的画面。
这是监听配置完成的情况。
2.新建服务器名，如果已存在就不需要建立，直接进行第三步。
Oracle客户端安装与配置
Oracle客 户 端 安 装 与 配 置
1.Oracle服务端配置监听。 1.1点击服务端“Oracle Net Configuration Assistant”，弹出如图所示对话框，选择“监听程序配置”
1.2.点击“重新配置”而非“添加”，弹出如图所示对话框，然后不停的点击下一步即可。
2Oracle客户端“本地网络服务名配置” 2.1点击客户端“Oracle Net Configuration Assistant”，点击“本地网络服务名配置” 点击下一步“添加”，服务名填写数据库名称如“ORCL”，如图示
2.2然后点击下一步，输入主机名，输入电脑名或IP地址。
2.3然后点击下一步，最好进行测试连接一下。测试成功后输入网络服务名即可。
Oracle Forms 12c客户端部署配置选项说明书
Oracle Forms 12cClient Deployment Configuration Options O R A C L E W H I T E P A P E R|M A Y2016Table of ContentsIntroduction 2 Oracle Forms 12c Client Deployment Configuration Options 3 Java Applet Embedded in HTML 3 JNLP Embedded in HTML 4 Java Web Start 4 Forms Standalone Launcher 5 Conclusion 8IntroductionIn the early 1990’s, the Internet (World Wide Web) began to evolve from a system designed and used by government organizations to one used globally by the public. This transition began a wave of related technologies being born. The Internet allowed people to have immediate access to information once thought to be out of reach. Web technology, specifically Web browsers, gave developers an opportunity to deliver their applications to end-users without the need to install software on the end-user’s machine.Until the 1990’s, Oracle Forms was delivered as a t wo-tier technology. With its client and server concept, Oracle Forms required that the technology’s runtime software be installed and configured on the end-user’s machine. This meant that each end-user machine would require an administrator to install runtime software one machine at a time. Often this was a difficult task given that an organization could have thousands of end-users, who could be located anywhere in the world. As we moved toward and into the twenty first century, Oracle realized that Oracle Forms customers would begin expecting to have access to their applications in the same way as so many other applications, through a web browser. Oracle Forms 6i was the first version to fully support application deployment via a web browser. Because of the need for tight integration on the client tier, it was necessary to use Java Applet technology to host the applications. So, although applications were launched from a browser, it was actually the Java Runtime Environment (JRE) on the client that ran or hosted the applications. After more than fifteen years of web browsers supporting integration with the Java Plug-in, many browser vendors are moving to a plugin-free model. As a result, Oracle Forms needs new ways of being deployed if it is to continue using Java technology on the client tier.Beginning with Oracle Forms 12c, product users can now choose from several client configuration options. With several options available, administrators can choose which option best suits their needs. This document aims to describe each of the configuration options and how to use them. It will also explain the advantages and limitations of each.Oracle Forms 12c Client Deployment Configuration OptionsBeginning with Oracle Forms 12c, there are now four supported client deployment configuration options. The available options are as follows.»Java Applet embedded in HTML»JNLP embedded in HTML»Java Web Start (JWS)»Forms Standalone Launcher (aka Standalone or FSAL)Although each option will have minimal to no impact on the appearance and behavior of any application, each will be contained slightly differently. Enabling and configuring any of these can be accomplished in the Forms Web Configuration page (i.e. formsweb.cfg) in Fusion Middleware Control.Any examples provided in this paper assume that you have properly configured Secure Socket Layer (SSL) in the server environment, as this is the most secure way to run any web deployed application. All options can also be used with non-SSL, but this is not recommended. Refer to the Oracle HTTP Server and WebLogic Server Administration Guides for details on properly configuring SSL in your environment.Java Applet Embedded in HTMLThis option was the first offered when browsers began supporting the Java Plug-in. Its configuration is the default for any Oracle Forms installation, 12.2.1 and older. This option can be used to give the appearance that the Forms application (applet) is embedded in a web page. This is often desirable when the HTML content surrounding the Forms application contains related or integrated information. This can also be helpful when using the Forms JavaScript integration feature. Single sign-on and single sign-off are also fully supported in this configuration.Disadvantages of using this option include the requirement of a Java Plug-in and the need for a certified browser that supports the Java Plug-in. The loss of usable space taken up by the browser’s window, toolbar, and menu will also need to be tolerated.Using the Applet embedded in HTML option is simple because this is the default configuration. Simply enter a URL in the browser that appears something like one of the following.»https:///forms/frmservlet»https:///forms/frmservlet?config=defaultThese parameters/values are required for this configuration and are found in the Forms Web Configuration page of Fusion Middleware Control.Non-WebUtil Enabled Forms WebUtil Enabled FormsJNLP Embedded in HTMLEmbedded JNLP is very similar to embedded Applet, however the application is treated more like a Java Web Start application although embedded within a web page. Like an embedded Applet, embedded JNLP fully supports JavaScript integration, single sign-on, single sign-off, and the ability to visually embed the form in a web page. Embedded JNLP has the added advantage of base-64 encoding the JNLP content. This content includes most of the parameter/value pairs configured for the application. Because the base-64 encoded text is not human readable, curious end-users will be discouraged from attempting to alter any of the parameters. It should be understood that the base-64 encoding is not a security mechanism. The base-64 encoding used in this configuration is required by Java and helps to improve the performance of delivery from server to client. This configuration requires the Java Plug-in and a certified browser that supports the Java Plug-in.To use this configuration you can either use the provided example configuration named “jnlp” or create your own.»https:///forms/frmservlet?config=jnlpThese parameters/values are required for this configuration and are found in the Forms Web Configuration page of Fusion Middleware Control.Non-WebUtil Enabled Forms WebUtil Enabled FormsWhen using Java Web Start or Embedded JNLP, if the application uses custom jar files (e.g. jacob.jar, icons.jar, example.jar, etc), these should be added to extensions.jnlp. The file is located in Oracle_Home\forms\java. Open this file in a text editor and make the appropriate entries. An example is included in the file. Each entry should be added on its own line.Java Web StartJava Web Start is considered a semi-browserless configuration. The use of Java Web Start will give an Oracle Forms application the appearance of being a natively installed application rather than a web app because when running, the application is not contained by the boundaries of the browser. This is often desirable with Point of Sale applications where the only application used on the device is the POS application or in cases where the application is designed to use the full screen. Different from the functionality provided by the use of separateFrame=true (available in the previous two configurations only), the use of Web Start allow you to close the browser window used to call the application once it has started.Oracle Forms’ use of Java Web Start allows applications to be called from a browser using a hyperlink or by directly entering a URL. Alternatively, the application can be run from a JNLP file stored on the end-user machine. This method eliminates the need for a browser, except when the application is single sign-on protected. Java Web Start can also be used to call an Oracle Forms application from the command line. Although there are several variations of how Java Web Start can be used, if the application requires the use of single sign-on, it must be called from a browser. Attempts to call an SSO protected application from a static JNLP file or the command line will fail.Because this is a mostly browser-less configuration, features like single sign-off and JavaScript integration are not supported when using the Java Web Start configuration.This configuration requires the Java Plug-in be installed if calling from a browser. If not calling from a browser, either the Java Plug-in or Java Development Kit (JDK) installation is required. A browser is optional and would only be required if single sign-on is used.To use this configuration you can either use the provided example configuration named “webstart” or create your own. The application can be called from a browser or you can use the command line or custom script.»jnlps:///forms/frmservlet?config=webstart»https:///forms/frmservlet?config=webstart»javaws “https:///forms/frmservlet?config=webstart”The “jnlp” and “jnlps” protocols (used in above example) are supported with Java 8u92+ on Microsoft Windows.The following are required parameters/values for this configuration and are found in the Forms Web Configuration page of Fusion Middleware Control.Non-WebUtil Enabled Forms WebUtil Enabled FormsWhen using Java Web Start or Embedded JNLP, if the application uses custom jar files (e.g. jacob.jar, icons.jar, example.jar, etc), these should be added to extensions.jnlp. The file is located in Oracle_Home\forms\java. Open this file in a text editor and make the appropriate entries. An example is included in the file. Each entry should be added on its own line.Forms Standalone LauncherThe Forms Standalone Launcher is a fully browser-less configuration. Further, it does not require that the Java Plug-in be installed. It does require Java on the client, but it can be any one of the following; JRE, JDK, or Server JRE.With this configuration, applications are launched from the command line or custom script files by calling the platform specific “java” executable. This con figuration fully isolates the application from the Java Plug-in or Java Web Start and the browser. Using the Forms Standalone Launcher can provide the appearance of a fully native application. Single sign-on, single sign-off, and JavaScript integration are not supported with this configuration.This configuration requires that a small jar file (frmsal.jar) be stored on the end-user machine. The file can be transferred to the end-user machine using any desirable method (e.g. web download, email, ftp, etc). This file is the Forms Standalone Launcher. It is version specific, so it cannot be used with other Forms versions or patch levels.The file is staged on the server in the Oracle_Home\forms\java directory. However, a helpful usage guide that includes a download link can be easily accessed when the server is running. Administrators can easily disable, remove, or edit this page if desired. Navigate to the following to display the page.»https:///forms/html/fsal.htmTo use this configuration you can either use the provided example configuration named “standaloneapp” or create your own. The application can be called from the command line or custom script. You cannot use a browser with this configuration. The command line entry would look something like the following.»java –jar frmsal.jar –url “https:///forms/frmservlet?config=standaloneapp”»java –jar frmsal.jar –url “https:///forms/frmservlet?config=standaloneapp” –t 30000Refer to the Usage Guide mentioned above for more details on command line syntax.The following are key parameters/values used by this configuration and are found in the Forms Web Configuration page of Fusion Middleware Control.Non-WebUtil Enabled Forms WebUtil Enabled FormsIn this release, the Forms Standalone Launcher does not have the ability to determine which Java version is being used. It will be up to the Administrator and/or user to ensure that an appropriate Java version is used. Refer to Figure 1 below for a simple Microsoft Windows script (batch) example.Figure 1 - Microsoft Windows script example.ConclusionOracle Forms 12c offers a variety of possible client configurations options. Choosing which is best will depend on the application’s needs and desired appearance at runtime. Because users can choose which option suits them best, no longer will they be constrained to a single possibility. If choosing the Java Web Start or Forms Standalone Launcher options, administrators no longer have to be concerned about compatibility between browser and Java versions. This should make application deployment and manageability easier.Oracle Corporation, World Headquarters Worldwide Inquiries 500 Oracle ParkwayPhone: +1.650.506.7000 Redwood Shores, CA 94065, USAFax: +1.650.506.7200Copyright © 2016, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission.Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. 0116Oracle Forms 12c Client Deployment Configuration Options May 2016Author: Michael FerranteContributing Authors: Oracle Forms DevelopmentC O N N E C T W I T H U S/oracle/oracle/oracle。
详细版oracle配置手册.doc.doc
1 安装oracle1.1安装服务1)双击oracle安装程序，开始安装，单击下一步2)选择安装路径，单击下一步3)选择安装的产品（此处选Oracle Database 9.2.0.1.0），单击下一步4)选择安装的版本（默认选企业版），单击下一步5)选择数据库配置（默认选择通用），单击下一步6)设置端口号（默认2030），单击下一步7)设置数据库名及SID名称，单击下一步(sywebserver)8)选择数据库文件目录的路径，单击下一步9)设置数据库字符集（默认），单击下一步10)单击“安装”，开始安装数据库11)安装过程中会提示插入磁盘2，选择磁盘2的路径，单击“确定”继续安装12)之后还会提示插入磁盘3，选择磁盘3的路径，单击“确定”继续安装13)安装程序对数据库进行配置并创建数据库14)设置数据库的管理员SYS、System的密码，此处分别设为sys、system。
1.2创建用户及数据库1)在开始－>程序－>Ora92－>Enterprise Manager Console打开oracle的管理界面2)选择独立启动，单击确定3)打开数据库，输入用户名、口令（system、system）登陆4)打开安全性－>用户，右键单击，在菜单中选择创建5)在弹出的窗口输入名称及口令（syportal、syportal）6)切换到角色选项卡，选择DBA角色，单击下箭头添加7)将DBA的管理选项勾选，单击创建8)提示用户创建成功9)重复步骤4）～8），分别创建用户syprivilege（用户/密码：syprivilege/syprivilege）、usm（用户/密码：usm/usm）1.3 导入数据1）开始菜单——运行——cmd2）进入到数据文件的存放路径3）执行数据恢复语句imp syportal/syportal fromuser=hljportal touser=syportal file=portaldata0115.dmp (imp 登陆用户/密码fromuser=原数据库用户名touser=现数据库用户file=数据数据文件名log=log.text)4）执行imp syprivilege/syprivilege fromuser=hljsyprivilege touser=sysyprivilege file=portaldata0115.dmp5）执行imp ums/ums fromuser=ums touser=ums file=portaldata0115.dmp。
ORACLE详细配置文档
ORALCE教学第一期（2010.05.10）本期学习ORACLE目标是让各位学员能快速进入ORACLE的世界，通过本期教学能对现有ORACLE数据库进行一些基础的操作。
所以教学过程中涉及的一些ORACLE框架与理论知识将被忽略，请各位学员不必深究，以后的教学会有涉及，也欢迎大家发挥自学能力，自己寻找答案。
本教程中不足之处还请多多指正！如果在实践过程中，请你写下你的问题发送到1127143739@！第1章ORACLE软件的选择1.1 本教程选用的ORACLE软件的版本ORACLE 10g Release 2 (10.1) for Windows1.2 下载的网址：••/technology/software/products/database/index.html第2章ORACLE数据库安装2.1 安装说明这里选用ORACLE 10g for Microsoft Windows (32-bit)版本进行演示。
以下演示过程中涉及的配置参数仅为演示，具体的参数请结合实际情况设置。
2.2 安装ORACLE软件1.运行ORACLE安装光盘install文件夹下的setup.exe；2.点击“下一步”，选择ORACLE软件的安装目录；3.下一步，选择安装类型4.选择“企业版”并点击“下一步”，；5.先安装软件，实例暂不安装，选择“不创建启动数据库”，点击“下一步”；6.查看安装概要，确认没有问题后，点击“安装”；7.ORACLE软件正在安装，等候几分钟；8.安装结束，点击“退出”；2.3 监听程序配置在ORACLE软件安装完成后会自动调出配置窗口（Net Configuration Assistant），如果没有，请在所有程序中Oracle - OraDb10g_home1\Configuration and Migration Tools\ Net Configuration Assistant；1.选择“监听程序配置”，点击“下一步”；2.选择“添加”，点击“下一步”；3.设置“监听程序名”，点击“下一步”；4.选择协议，点击“下一步”；5.选择“使用标准端口号1521”，点击“下一步”；6.选择“否”，点击“下一步”；7.完成配置，点击“下一步”；8.点击“完成”退出配置窗口；9.调出任务管理器，如果有第3步配置的监听程序名：TNSLSNER.EXE，说明配置成功。
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
Oracle客户端安装配置文档
一、安装
1、双击setup.exe进行安装。
图 1 安装图标
2、选择“管理员”安装类型，因为我们要用到其中的管理工具、联网服务等。
图 2 选择安装类型
2、选择软件安装位置，可根据需要选择合适的安装路径。
图 3 选择Oracle安装位置
3、默认选择的简体中文和英语，继续下一步。
若出现环境配置错误可选择忽略。
图 4 选择语言
4、点击“完成”开始安装程序。
图 5 安装信息
二、配置网络管理
1、点击“开始”—>“所有程序”—>“Oracle-OraClient11g_home”—>“配置和移植工具”—>“Net Manager”。
图 6 开始菜单
2、选择“本地”中的“服务命名”，然后单击左上角的“+”按钮，创建一个网络连接。
图7 创建网络连接3、填写网络服务名，可任意命名。
图8 填写网络服务名4、选择默认的“TCP/IP”协议。
图9 选择协议
5、输入服务器地址，端口号选择默认的即可。
图10 填写主机名及端口号6、输入要连接的数据库名称。
图11 填写服务名7、测试是否连接成功。
图12 测试画面8、未连接成功。
图13 连接测试结果9、更改登录，输入自己的用户名及密码。
图14 登录画面10、测试成功，点击“关闭”。
图15 连接测试结果
三、开发使用
1、点击“开始”—>“所有程序”—>“Oracle-OraClient11g_home”—>“应用程序开发”—>“SQL Developer”。
图16 开始菜单程序
2、弹出如下对话框
图17 选择java.exe程序
点击“Browse”，在安装目录下
“C:\app\Administrator\product\11.2.0\client_1\jdk\bin”选择java.exe。
3、然后选择要与SQL Developer关联的文件类型，全部选中即可，点击“确定”。
图18 文件类型关联
4、数据库连接配置。
输入连接名，与“config/HistoryInfo.xml”文件中的“Connection”
的值相对应；
用户名与“config/HistoryInfo.xml”文件中的“USERNAME”的值相对应；
密码与“config/HistoryInfo.xml”文件中的“PASSWORD_CS”的值相对应；
主机名填写数据库服务器的IP地址，与“config/HistoryInfo.xml”文件中的“ServerIp”的值相对应；
服务名填写要连接的数据库，与“config/HistoryInfo.xml”文件中的“InstanceName”的值相对应；
点击“测试”按钮检查是否连接成功。
图19 数据库连接配置
5、连接成功后，点击“连接”。
图20 测试结果
6、在文本编辑器区域输入ＳＱＬ语句就可以对数据表进行操作了，下方会显示操作的结果。
图21 数据库操作界面
若表中数据出现中文乱码，需要修改注册表中
“HEKY_LOCAL_MACHINE/SOFTWARE/ORACLE/KEY_OraClient11g_home2”中的NLS_LANG值，修改为“SIMPLIFIED CHINESE_CHINA.UTF8”。