ORACLE部署流程
(完整)oracle+weblogic安装与部署
公司由C/S转向B/S，所以有了此文.oracle+weblogic的安装与部署。
一般的软件安装配置都比较的简单，而这些相对复杂点,所以在此配图详解，下面开始正文：1.下载oracle 10g，PL/SQL和Weblogic8.1.42。
安装oracle 10g前期准备首先检查机器上是否安装了其他版本的oracle，如果有请按以下步骤卸载.a,首先使用oracle自带的卸载功能卸载程序b，删除机器上oracle目录c，打开注册表开始—运行—regedit，找到HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE，全部删除。
找到HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MenuOrder\Start Menu2\Programs\Oracle — OraDb10g_home1全部删除。
开始安装a，首先解压oracle 10gb，点击解压后的setup。
exe进行安装,如图1：选择基本安装，根据自己的盘符大小情况选择安装目录路径，安装类型根据个人实际应用进行选择。
全局数据库名一般默认，口令自己设置c，点击下一步，oracle会自行检测运行环境和安装目录等等，如图2:d，经检测没有问题,点击下一步，出现如图3界面：根据本身机器的硬件，安装时间不同，一般10到20分钟如果安装过程中出现问题，会提示错误信息；否则就出现如下界面，图5：e，安装结束，图6：3。
安装PL/SQLPL/SQL的安装比较简单这里不做过去介绍.登陆界面，图7:4。
安装Weblogic8.1.4a,解压Weblogic8。
1。
4，点击platform814_zh_cn_win32。
exe文件,如图8:b,点击下一步,如图9：c，选择同意，下一步，使用默认下一步,如图10：d，选择完全安装，如图11: e,选择安装目录，如图12：f,开始安装,安装时间一般为3—5分钟如图13：g：安装完成，如图14安装已经完成下面我们以一个程序为例，进行部署,程序为公司内部程序不方便公开。
Oracle Big Data Lite 4.6.0 快速部署指南说明书
Big Data Lite includes software products that are optional on the Oracle Big Data Appliance (BDA), including Oracle NoSQL Database Enterprise Edition, Oracle Big Data SQL, Oracle Big Data Discovery, Oracle Big Data Spatial and Graph and Oracle Big Data Connectors.
Version 4.6.0
Last Updated: 10/25/2016 Please note: This appliance is for testing and educational purposes only; it is unsupported and not to be used in production. C O N T E N T S
To get started, you should perform the following high level tasks:
• Ensure your host computer meets the requirements for running the virtual machine • Download and install VirtualBox and VirtualBox Extension Pack – which is a cross-‐platform virtualiza-‐
在Linux(Rhel6.4)上安装oracle11g和was7全过程
在Linux上安装oracle11g和was7全过程目录一、安装环境 (2)1.1.IP地址 (2)1.2.硬件配置 (2)1.3.文件系统划分 (2)1.4.软件介质 (2)二、安装Linux（RedHat Enterprise Linux 6.4）操作系统 (2)2.1.系统安装过程 (2)2.2.系统参数配置 (19)2.3. yum配置 (19)三、安装Oracle11.2.0.3 (20)3.1．添加oracle用户和组 (20)3.2.创建文件夹并授权 (20)3.3.内存参数设置 (20)3.4.oracle用户环境变量设置 (20)3.5.安装oracle依赖包 (21)3.6. 安装Oracle11.2.0.3软件 (21)四、安装Websphere7.0 (28)4.1.安装过程 (28)4.2.起停脚本 (36)一、安装环境1.1.IP地址1.2.硬件配置内存8G磁盘空间：73G×41.3.文件系统划分Swap 4G/boot 512M/ 200G在/下创建/websphere、/oracle目录1.4.软件介质安装软件、应用包全部放在/home下Linux安装盘（RedHat Enterprise Linux 6.4）Oracle11.2.0.3 for linux 64bitWebsphere7.0NDXmanager4.0二、安装Linux（RedHat Enterprise Linux 6.4）操作系统2.1.系统安装过程--重起后配置界面--重起后出现登录界面2.2.系统参数配置◆关闭防火墙[root@foawas ~]# chkconfig iptables off◆Hosts配置[root@foawas ~]# vi /etc/hosts127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 10.41.130.46 foawas2.3. yum配置将安装光盘整个拷贝到/home/rhel6.4/\cp -R /media/RHEL_6.4 x86_64 Disc 1/* /home/rhel6.4/配置yum[root@foawas yum.repos.d]# vi /etc/yum.repos.d/rhel-source.repo[rhel-source]name=Red Hat Enterprise Linux $releasever - $basearch - Sourcebaseurl=file:///home/rhel6.4/enabled=1gpgcheck=1gpgkey=file:///home/rhel6.4/RPM-GPG-KEY-redhat-release三、安装Oracle11.2.0.33.1．添加oracle用户和组[root@foawas oracle]# groupadd oinstall[root@foawas oracle]# groupadd dba[root@foawas oracle]# useradd -g oinstall -G dba -m oracle[root@foawas oracle]# passwd oracle3.2.创建文件夹并授权[root@foawas oracle]# mkdir /oracle/app[root@foawas oracle]# mkdir /oracle/app/oracle[root@foawas oracle]# mkdir /oracle/app/oradata[root@foawas oracle]# mkdir /oracle/app/oracle/product[root@foawas oracle]# chown -R oracle:oinstall /oracle/app[root@foawas oracle]# ls -ldrwxr-xr-x. 4 oracle oinstall 4096 May 22 16:38 app3.3.内存参数设置[root@foawas ~]# vi /etc/security/limits.conforacle soft nproc 2047oracle hard nofile 65536oracle hard memlock 52428800oracle soft memlock 52428800[root@foawas ~]# vi /etc/sysctl.confkernel.shmmni = 4096kernel.sem = 250 32000 100 128fs.file-max = 6815744net.ipv4.ip_local_port_range = 9000 65500net.core.rmem_default = 262144net.core.wmem_default = 262144net.core.rmem_max = 4194304net.core.wmem_max = 1048576fs.aio-max-nr = 1048576[root@foawas ~]# sysctl -p3.4.oracle用户环境变量设置[root@foawas /]# su - oracle[oracle@foawas ~]$ vi .bash_profileexport ORACLE_BASE=/oracle/app/oracleexport ORACLE_HOME=$ORACLE_BASE/product/11.2.0/dbhome_1export PATH=$PATH:$HOME/bin:$ORACLE_HOME/binexport NLS_LANG=AMERICAN_AMERICA.ZHS16GBKexport LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ORACLE_HOME/lib:/usr/lib:/usr/local/lib3.5.安装oracle依赖包[root@foawas ~]# yum install -y gcc[root@foawas home]# yum install -y libaio-devel[root@foawas home]# yum install -y gcc-c++[root@foawas home]# yum install -y elfutils-libelf-devel[root@foawas home]# yum install -y compat-libstdc++-33下载pdksh-5.2.14-30.x86_64.rpm包到/home目录[root@foawas home]# rpm -ivh /home/pdksh-5.2.14-30.x86_64.rpm3.6. 安装Oracle11.2.0.3软件用oracle用户登录到图形界面，打开terminal[oracle@foawas ~]$cd /home/database[oracle@foawas database]$ ./runInstaller执行脚本[root@ foawas ~]# sh /oracle/app/oraInventory/orainstRoot.shChanging permissions of /oracle/app/oraInventory.Adding read,write permissions for group.Removing read,write,execute permissions for world.Changing groupname of /oracle/app/oraInventory to oinstall.The execution of the script is complete.[root@ foawas ~]# sh /oracle/app/oracle/product/11.2.0/dbhome_1/root.sh Performing root user operation for Oracle 11gThe following environment variables are set as:ORACLE_OWNER=oracleORACLE_HOME=/oracle/app/oracle/product/11.2.0/dbhome_1Enter the full pathname of the local bin directory: [/usr/local/bin]:Copying dbhome to /usr/local/bin ...Copying oraenv to /usr/local/bin ...Copying coraenv to /usr/local/bin ...Creating /etc/oratab file...Entries will be added to the /etc/oratab file as needed byDatabase Configuration Assistant when a database is createdFinished running generic part of root script.Now product-specific root actions will be performed.Finished product-specific root actions.验证安装是否完成[oracle@foawas ~]$ sqlplus / as sysdbaSQL*Plus: Release 11.2.0.3.0 Production on Tue Jun 3 08:05:38 2014 Copyright (c) 1982, 2011, Oracle. All rights reserved.Connected to an idle instance.SQL>四、安装Websphere7.04.1.安装过程用root用户登录图形界面[root@foawas ~]# cd /home/was7/WAS/[root@foawas WAS]# ./install安装完成输出，安装验证4.2.起停脚本[root@foawas scripts]# vi was_start.sh#!/bin/shcd /websphere/AppServer/profiles/Dmgr01/bin ./startManager.shcd /websphere/AppServer/profiles/AppSrv01/bin ./startNode.sh./startServer.sh server1[root@foawas scripts]# vi was_stop.sh#!/bin/shcd /websphere/AppServer/profiles/AppSrv01/bin ./stopServer.sh server1./stopNode.shcd /websphere/AppServer/profiles/Dmgr01/bin./stopManager.sh。
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）。
linux系统oracle 数据库创建实例
linux系统oracle 数据库创建实例在Linux系统上创建Oracle数据库实例，可以按照以下步骤进行操作：1. 安装Oracle数据库软件。
首先，下载适用于Linux系统的Oracle数据库软件，并按照安装步骤进行安装。
2. 设置环境变量。
将Oracle数据库软件的安装路径添加到PATH环境变量中，以便系统可以找到相关的Oracle命令和工具。
3. 创建数据库实例目录。
选择一个合适的目录用于存储数据库实例文件，例如：/u01/app/oracle/oradata/。
4. 使用Oracle用户登录系统。
在Linux系统上创建一个拥有合适权限的Oracle用户，并使用该用户登录系统。
5. 使用dbca命令创建数据库实例。
在终端中输入以下命令启动数据库配置助手（Database Configuration Assistant）：dbca6. 选择创建数据库实例选项。
根据实际需求，选择创建新的数据库实例或者基于现有的模板来创建数据库实例。
7. 配置数据库实例参数。
在配置向导中，按照提示设置数据库实例的名称、监听器、字符集、内存大小等参数。
8. 创建数据库。
根据向导的指示，输入数据库管理员（DBA）密码，并完成数据库的创建过程。
9. 启动数据库实例。
使用以下命令启动数据库实例：sqlplus / as sysdba，然后输入startup命令。
10. 验证数据库实例。
输入以下命令验证数据库实例是否成功创建：sqlplus / as sysdba，然后输入select * from v$version命令，查看数据库版本信息。
以上就是在Linux系统上创建Oracle数据库实例的基本步骤。
具体操作可能会因Oracle软件版本和Linux发行版的不同而略有差异，可以根据具体情况进行调整。
oracle rac 安装部署文档
oracle rac 安装部署文档oracle oracle rac搭建][常见问题汇总oracle rac 安装部署文档物理硬件配置需求：oracle 虚拟机需求：oracle rac两节点脚本搭建方法操作系统安装数据库安装oracle rac 图形界面搭建方法（适用于两个节点和多个oracle节点）创建磁盘组安装oracle数据库dbca 创建数据库配置oracle性能测试相关的参数关闭iolog常见问题汇总问题一：oracle在运行过程中，异常中断存储进程（gluster,tgtd等）会导致oracle异常报错ORA-01078。
问题二：查看数据库实例状态的时候报错ORA-01034问题三：删除问题表失败问题四：通过系统镜像安装桌面。
问题五：执行完oracle_install_rac.sh 如果oracleasm 命令未别找到，要先解压rpm文件夹问题六：rac01 和rac02 sid配置成一样的了怎么修改问题七：请求spfile错误问题八：ora 12516报错监听程序找不到符合协议堆栈要求的可用处理程序问题九:问题启动数据库报错 ORA-01078物理硬件配置需求：oracle 虚拟机需求：oracle rac两节点脚本搭建方法操作系统安装1.页面选择部署oracle rac2.选择共享盘创建，单机下一步3.配置虚拟机基本信息，– cpu改成2*16核，– 内存改成96G，– 添加一个网卡，连接心跳交换机– 磁盘添加iso redhat镜像文件– 磁盘设置为80G 预先分配网络配置第一个网口作为虚拟机的公网,第二个网口作为虚拟机的私网网口(连接heartbeat交换机的网口)4.单击下一步，安装redhat操作系统 [以下简略提示4点]1.hostname可以先不改2.创建分区的时候，选择Create Custom Layout自己配置分区大小3.创建分区/boot 分区1024M,swap 分区20480M，剩余的空间分配给/分区4.安装的时候选择带桌面的5.red hat系统安装完成后，按页面提示，安装虚拟机性能优化工具（不安装性能优化工具，会导致测试性能的时候，性能大幅下降）6.安装完成后，将虚拟机关机。
Oracle Siebel 简易部署手册
安装完成后在您的盘符下新建一个文件夹（例如 d:\f5config ） Copy lbconfig.txt 到文件夹下。 解压siebel8-bigipv9.zip文件， 把siebel-bigipv9.pl copy到文件夹 下 进入 windows 的命令行模式 进入到你的文件夹下（d:\f5config>） 执行 perl siebel8-bigipv9.pl -r （调用的 rule 名字） -v （virtual server 的 IP 地址） ： （端口，默认 2321） 例如： perl siebel8-bigipv9.pl -r seibelruletest -v 10.7.70.100:2321 生成了以下就生成了我们所需要的 bigip.cfg 文件。 文件格式内容如下：
bigpipe pool EAIObjMgr_chsRRPool { lb method rr \ member 10.7.97.3:2321 \ member 10.7.97.2:2321 \ monitor all monitor_PROD \ } bigpipe pool EAIObjMgr_SIRRPool { lb method rr \ member 10.7.97.3:2321 \ member 10.7.97.2:2321 \ monitor all monitor_PROD \ } bigpipe pool EAIObjMgr_wtRRPool { lb method rr \ member 10.7.97.3:2321 \ member 10.7.97.2:2321 \ monitor all monitor_PROD \ } bigpipe pool ADMBatchProcRRPool { lb method rr \ member 10.7.97.3:2321 \ member 10.7.97.2:2321 \ monitor all monitor_PROD \ } bigpipe pool ADMObjMgr_chsRRPool { lb method rr \ member 10.7.97.3:2321 \ member 10.7.97.2:2321 \ monitor all monitor_PROD \ } bigpipe pool ADMProcRRPool { lb method rr \ member 10.7.97.3:2321 \ member 10.7.97.2:2321 \ monitor all monitor_PROD \ } bigpipe pool 10.7.97.2ServerPool { lb method rr \ member 10.7.97.2:2321 \ monitor all monitor_PROD \ } bigpipe pool 10.7.97.3ServerPool { lb method rr \ member 10.7.97.3:2321 \ monitor all monitor_PROD \ } bigpipe rule seibelruletest { ' when CLIENT_ACCEPTED { TCP::collect 1 } when CLIENT_DATA { if { [findstr [TCP::payload] "/siebel" 0 " "] ==
OracleERP架构及流程简介
目录
• Oracle ERP 概述 • Oracle ERP 架构 • Oracle ERP 流程 • Oracle ERP 的实施与优化 • Oracle ERP 的挑战与解决方案 • Oracle ERP 的行业应用与案例分析
01 Oracle ERP 概述
效率和客户响应速度。
THANKS FOR WATCHING
感谢您的观看
引入先进技术
关注行业新技术动态，适时引入人工智能、大数据等先进技术，提 升系统性能。
建立反馈机制
建立用户反馈机制，及时收集用户意见和建议，持续优化系统功能 和操作体验。
06 Oracle ERP 的行业应用 与案例分析
制造业应用案例
总结词
实现生产计划、采购、库存、销售等环节的集成管理
详细描述
Oracle ERP在制造业中广泛应用，通过实现生产计划、采购、库存、销售等环节的集成管理，提高生 产效率，降低库存成本，优化供应链。例如，某汽车制造企业采用Oracle ERP实现生产计划与采购的 协同，有效减少了原材料的库存积压和浪费。
03 Oracle ERP 流程
财务模块流程
财务模块概述
Oracle ERP中的财务模块为企业提供了一套完整的财务管理解决方案，涵盖了财务会计、管理会计和财务分析等 各个方面的功能。
财务模块流程
财务模块流程主要包括财务计划、财务执行和财务分析三个阶段。在财务计划阶段，企业可以根据历史数据和市 场趋势制定财务预算和预测；在财务执行阶段，企业可以记录和处理日常的财务交易和凭证；在财务分析阶段， 企业可以对财务数据进行深入分析和报告，以支持决策制定。
零售业应用案例
总结词
部署ORACLE文档
部署流程：
1、安装JDK，安装TOMCAT 5.0
注：若此服务器上的端口号改为8888，则需在安装的时候将TOMCAT端口号改为8888
找到TMOCAT目录，CONF——》SERVER。
XML 搜索PORT 修改端口号
2、配置环境变量
1）新建“java_home”变量，设置jdk的安装路径，比如“e:\java\jdk1.5”，以下简称“%java_home%”
2）“path”，设置jdk中各个程序的路径，
“%java_home%\bin;%java_home%\jre\bin;”
3）“classpath”，设置java各个类的路径，
“.;%java_home%\lib;%java_home%\lib\tools.jar”。
前面的“.”不可少，它代表了我们为自己的java类建立的工作路径，其它的是jdk自带的标准类库路径。
3、安装ORACLE 、PLSQL
4、创建表空间，以SYS的用户名，密码用在安装的时候设置的密码
创建用户名
5、导入数据
Cd\
imp
6、把程序放到TOMCAT 路径下面
7、部署程序
http://localhost:8888/chssws/setup.loginInit.do
连接池下、模块设置下编辑
注：数据中心名称，ahswst ，不用8080。
oracle创建实例步骤
oracle创建实例步骤一、概述Oracle数据库是一种关系型数据库管理系统，可以通过创建实例来进行数据库的管理和操作。
本文将介绍Oracle创建实例的步骤，以帮助读者快速掌握实例创建的过程。
二、安装Oracle数据库软件在创建Oracle实例之前，首先需要安装Oracle数据库软件。
安装过程可以参考Oracle官方文档或者相关教程进行操作。
三、配置Oracle数据库参数文件1. 打开Oracle数据库软件所在的安装目录，找到数据库参数文件的位置。
一般情况下，参数文件位于$ORACLE_HOME/dbs目录下。
2. 复制一个参数文件的备份，命名为init<实例名>.ora，例如initORCL.ora。
3. 打开备份的参数文件，根据实际需求修改其中的配置项。
例如，可以修改数据库名称、监听端口、内存分配等参数。
4. 保存修改后的参数文件。
四、创建Oracle实例1. 打开命令行窗口或者终端，使用sysdba权限登录到Oracle数据库。
可以使用以下命令登录：sqlplus /nologconn / as sysdba2. 输入以下命令创建实例：create database <实例名>例如，create database ORCL3. 等待实例创建完成，创建过程中会显示进度信息。
五、配置Oracle实例参数1. 使用以下命令打开实例参数配置界面：sqlplus /nologconn / as sysdbaalter system set <参数名>=<参数值> scope=spfile;例如，alter system set memory_target=2G scope=spfile;2. 根据实际需求，修改实例的配置参数。
例如，可以修改内存分配、并发连接数、表空间大小等参数。
3. 使用以下命令使参数配置生效：shutdown immediatestartup六、创建Oracle数据库用户1. 使用以下命令登录到Oracle数据库：sqlplus /nologconn / as sysdba2. 输入以下命令创建数据库用户：create user <用户名> identified by <密码>;例如，create user test identified by test123;3. 授予用户权限：grant connect, resource to <用户名>;例如，grant connect, resource to test;4. 提交更改：commit;七、测试连接Oracle实例1. 使用以下命令登录到Oracle数据库：sqlplus <用户名>/<密码>@<实例名>例如，sqlplus test/test123@ORCL2. 如果能够成功登录到数据库，说明实例创建和配置成功。
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 Ebs R12 单点登陆部署
单点登录成功
第五：用SlGenerateKey.jar产生SL_KEY
第六：用SlGenerateKey.jar产生SL_KEY
第七：拷贝SL_KEY到文件指定位置
第八：拷贝jsp的CLASS文件到$JAVA_TOP,不过要退到上层的java/_page目录下
第九：重启服务
第六：拷贝SL_KEY到文件指定位置
cd $ADMIN_SCRIPTS_HOME $ADMIN_SCRIPTS_HOME/adoacorectl.sh stop $ADMIN_SCRIPTS_HOME/adoacorectl.sh start
测试:让本地当成外围程序
测试:本地的自动跳转页面,这个需要外围程序开发的,我们这个是JAVA写的, 可以协助提供JAVA的测试用例
Oracle Ebs R12 单点登陆部署 作者：随缘
Email:wavezhang66@
第一：找到DBC所在的位置
第一：找到DBC所在位置的记录下来
第一：找到DBC所在位置的记录下来
第三：新建一个OA WorkSpace，并配置好，这里不叙述了
第四：配置dbconfig.we文件如下
JAR包的配置 4：增加如下，然后再上传上去，上传之前一定要备份 /u01/erptest/apps/apps_st/comn/java/lib/SingleLogin.jar
JAR包的配置
5：重启服务
$ADMIN_SCRIPTS_HOME/adapcctl.sh stopall $ADMIN_SCRIPTS_HOME/adapcctl.sh startall
JAR包的配置 1：找到JAVA 的LIB路径
JAR包的配置 2：把SingleLogin.jar放到LIB路径里
部署Oracle12c企业版数据库（安装及使用）
部署Oracle12c企业版数据库（安装及使⽤）在计算机信息安全领域中，数据库系统⽆疑有着举⾜轻重的地位。
⽐如：SQL Server、MySQL、DB2、Oracle等，都是⽐较知名的数据库管理软件，由于Oracle数据库的安全性，所以在⼀些⽐较重要的场合被普遍使⽤，⽐如：电信、银⾏、政府部门等。
本次博⽂以Oracle 12c数据库的64位企业版为例，学习如何在Centos 操作系统中的安装和基本配置，包括安装的准备等。
博⽂⼤纲：⼀、安装Oracle 12c⼆、创建Oracle 12c数据库三、Oracle 12c数据库的启动与关闭四、将Oracle数据库设置为开机⾃启动⼀、安装Oracle 12c1.安装CentOS 7操作系统的注意事项由于本次安装Oracle 12c软件是在CentOS 7系统上实现的，那么⾸次安装CentOS 7操作系统有⼏点要求：防⽕墙的配置选项设置为禁⽤；SELinux设置为禁⽤；默认安装设置为软件开发；内核选择3.10.0-862.el7.x86_64及以上版本；2.前置条件的准备Oracle数据库是⼀个相对庞⼤的应⽤软件，对服务器的系统类型、内存和交换分区、硬盘空阿⾦、内核参数、软件环境、⽤户环境等都有相应的要求。
只要满⾜了这些必备的条件，才能确保Oracle 12c 安装成功并稳定运⾏。
（1）系统及配置要求Oracle 12c明确⽀持的Linux操作系统包括Oracle Linux 7、Oracle Linux 6、Oracle Linux 5、Red Hat Enterprise Linux 7、Red Hat Enterprise Linux 6、Red Hat Enterprise Linux 5等，因为Red Hat Enterprise 和CentOS属于同步并⾏的操作系统，所以Oracle 12 c同样⽀持CentOS 7、CentOS 6、CentOS 5操作系统。
ORACLE 数据库部署方案设计
ORACLE 数据库部署方案和安装配置指南1.总论1.1 目的为加强系统安装维护的规化管理，参考系统的相关文档，进行了深化、细化，力求结合实际的设计、实施工作，建立一套系统设计、实施的标准方案，对设计、实施起到规、指导作用。
文档主要从一个设计者的角度进行编写。
首先介绍了产品可实现的部署模式，如何选择部署模式，其次要考虑设计涉及到的因素，有针对性地做好数据库的设计等: 为提高数据库的性能，对程序开发提出了的要求。
文档中参数建议值是对系统设计时的指导，是针对目前系统状况所提出了的经验值，但由于应用系统的复杂性，每个系统有自己的特点，建议按建议值进行系统的初始配置，在压力测试和系统上线后根据实际需要做相应的调整，文档作为系统设计的规和参考。
1.2 受众项目设计和实施人员，部分项目组系统设计人员，相关运行维护技术人员。
1.3关键术语高可用性群集：High Availability Cluster 简称 HA Cluster:实时应用集群:Real Application Clusters 简称 RAC:Dataguard 是ORACLE 推出的一种高可用性的数据库方案, 在软件上对数据库进行设置:Recovery Time Objective，复原时间目标,是企业可容许服务中断的时间长度，简称 RTO ：Recovery Point Objective，复原点目标，是指当服务恢复后，恢复得来的数据所对应时的间点，简称RPO：2.数据库部署模式数据库服务器目前的情况：2.1 单机模式数据库服务器采用单服务器模式，满足对可用性和性能要求不高的应用，具备以下特点:1、硬件成本低。
单节点，硬件投入较低，满足非重要系统的需求。
2、安装配置简单。
由于是单节点、单实例，所以安装配置比较简单。
3、管理维护成本低。
单实例，维护成本低。
4、对应用设计的要求较低。
由于是单实例，不存在RAC 系统应用设计时需要注意的事项，所以应用设计的要求较低。
Oracle_RAC部署
Oracle 10g RAC数据库安装及维护手册目录目录 (2)第一部分系统硬件、软件配置说明及配置图 (3)一、总体配置说明 (3)二、网络设置说明 (3)三、数据库环境概况 (3)四、存储配置概况 (4)五、总体配置原理图 (4)第二部分 Windows Server2003 安装与配置 (5)一、安装Windows Server 2003 Enterprise Edition (5)二、操作系统配置（以下过程如无特殊说明，则在两节点上均进行） (5)第三部分 Cluster和数据库的安装、配置及升级 (15)一、安装Cluster ware软件 (15)二、安装database软件 (27)三、标识ASM驱动器 (32)四、升级数据库版本 (34)五、使用dbca安装数据库 (43)第四部分集群数据库的日常管理 (54)一、检查RAC各组件运行的状态。
(54)二、启动和停止RAC数据库。
(54)三、启动、停止、管理数据库EM监控 (55)四、如何增加表空间 (55)五、数据库管理注意事项 (55)第一部分系统硬件、软件配置说明及配置图一、总体配置说明二、网络设置说明三、数据库环境概况四、存储配置概况五、总体配置原理图第二部分 Windows Server2003 安装与配置一、安装Windows Server 2003 Enterprise Edition二、操作系统配置（以下过程如无特殊说明，则在两节点上均进行）1. 将两块网卡名改为public和private，检查被网络服务访问的连接顺序，确保public位于第一位，在网上邻居上右键点属性→菜单栏上点高级→点高级设置。
2. 修改Host文件和主机名，主机名分别为winRAC1和winRAC2，hosts文件位置：C:\windows\system32\drivers\etc\hosts10.1.3.105winrac110.1.3.107winrac1-vip10.10.10.1winrac1-priv10.1.3.106winrac210.1.3.108winrac2-vip10.10.10.2winrac2-priv测试节点之间的连通性：两台主机winRAC1和winRAC2互相ping公共主机名和专用节点名，看是否ping的通，这个时候是ping不通VIP地址的。
ORACLE数据库部署方案设计
ORACLE数据库部署方案设计一、引言ORACLE数据库是一款用户较为广泛的数据库管理系统，具备可扩展性、高性能、高可用性等优点，在各个行业有着广泛的应用。
为了充分利用ORACLE数据库的功能和特性，本文将针对一个典型的企业环境，设计一个ORACLE数据库部署方案。
二、系统需求分析1.系统规模：企业拥有大量的数据，需要一个可扩展的数据库系统来支持。
2.数据处理能力：需要满足高性能、高并发的数据处理需求。
3.数据安全：要求对数据进行安全的存储和访问控制。
4.可用性：要求数据库系统有高可用性，能够保证数据的连续性和可靠性。
5.数据备份与恢复：要求数据库系统能够进行定期的数据备份，并能够快速恢复。
6.系统可管理性：要求能够对数据库系统进行方便、高效的管理和维护。
三、系统设计方案1.硬件设计：为了满足系统规模大、数据处理能力强的需求，可以采用集群部署的方式。
集群包括多台服务器，通过局域网连接，形成一个数据库集群。
每台服务器都安装有ORACLE数据库，通过集群管理软件实现数据库的负载均衡与故障转移。
每台服务器都配备足够的存储空间和内存容量，以保证数据的存储和访问速度。
2.数据库设计：为了满足高性能、高并发的数据处理需求，可以将数据库划分为多个表空间，每个表空间可以单独存放不同类型的数据（如用户数据、索引数据、系统数据等），以提高读写性能。
同时，可以将数据库进行分区划分，将数据按照时间或其它规则进行分开存储，以便提高数据的查询效率。
3.数据库安全设计：为了保证数据的安全性，可以采取多层次的安全措施。
首先，可以通过对数据库进行访问控制，只允许授权用户访问数据库，并限制用户的权限。
其次，可以对敏感数据进行加密存储，以保护数据的隐私。
同时，可以定期对数据库进行安全检查和漏洞扫描，及时修补安全隐患。
4.高可用性设计：为了提高数据库的可用性，可以采用主备模式来进行数据备份与恢复。
即在集群中设置主数据库和备份数据库，主数据库用于正常的数据处理，备份数据库用于数据的备份和恢复。
ORACLE EBS账套部署实施
以Oracle EBS R12.2版本为例账套部署值集安全性设置由于R12版本值集有安全性管理，首先需要为用户授权，这样用户才能选择值集进行相关的操作。
路径：【用户管理】-> 【用户】输入用户名，点击【开始】按钮查找，选择【更新】选项点击【分配职责】按钮勾选所有权限保存后，后续所有的值集都可以选择到了。
总账(GL)会计科目结构一般公司以七段结构作为会计科目帐户结构居多，本书以通用的七段为例。
包括：公司段、部门段、科目段、往来段、项目段、备用段1、备用段2。
公司段路径：【系统管理员】-> 【应用产品】-> 【验证】-> 【请求集】输入相关信息，确认无误后，保存输入的数据。
接下来创建公司段的值。
路径：【系统管理员】-> 【应用产品】-> 【验证】-> 【值】输入或下拉选择公司段值集名称，点击【查找】按钮。
输入值和对应的说明值，保存数据。
部门段路径：【系统管理员】-> 【应用产品】-> 【验证】-> 【请求集】输入相关信息，确认无误后，保存输入的数据。
接下来创建部门段的值。
路径：【系统管理员】-> 【应用产品】-> 【验证】-> 【值】输入或下拉选择公司段值集名称，点击【查找】按钮。
输入值和对应的说明值，保存数据。
如果是父值，则需要定义子范围，鼠标选中相应的父值，点击【定义子范围】按钮科目段路径：【系统管理员】-> 【应用产品】-> 【验证】-> 【请求集】输入相关信息，确认无误后，保存输入的数据。
接下来创建科目段的值。
一般科目是多级结构，这里以三层结构为例。
先创建科目值集需要的组，然后再创建值。
路径：【系统管理员】-> 【应用产品】-> 【弹性域】-> 【关键字】-> 【组】输入组值录入科目段的值路径：【系统管理员】-> 【应用产品】-> 【验证】-> 【值】输入或下拉选择公司段值集名称，点击【查找】按钮。
oracle11grac静默安装+racADG部署搭建
oracle11grac静默安装+racADG部署搭建说明以下说描述的的安装rac是安装⼀个rac备端，只需要安装grid软件和oracle软件即可。
⼀、硬件配置：cup：Linux db51 3.10.0-1062.el7.x86_64 #1 SMP Wed Aug 7 18:08:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux内存：250GOCR:3G*3DATA:480G*6⼆、软件环境：操作系统：CentOS Linux release 7.7.1908 (Core)数据库：oracle 11.2.0.4 R2 RAC三、业务系统：业务系统四、主机规划：五、数据库安装前准备1、配置DNS内容（可忽略）：vi /etc/resolv.confnameserver 192.168.3.1nameserver 192.168.3.22、改hosts⽂件节点⼀db51和节点⼆db52：#pub192.168.3.51 db51192.168.3.52 db52#vip192.168.3.54 db51-vip10.10.10.52 db52-vip#priv10.10.10.51 db51-priv192.168.3.55 db52-priv#scan172.16.53.56 db-scan3、关闭防⽕墙systemctl status firewalldsystemctl stop firewalldsystemctl disable firewalld4、关闭selinuxSetenforce 0vi /etc/sysconfig/selinux将SELINUX值改为disabled6、关闭透明⼤页==查看：cat /sys/kernel/mm/transparent_hugepage/enabled[always] madvise never默认为always。
Oracle Eloqua Lead Scoring 快速部署指南说明书
Best Practices for Quick Deployment of Lead Scoring Oracle EloquaLeverage Lead Scoring to systematically nurture customers with automated marketing campaigns and automatically route purchase ready customers tosales.Oracle Eloqua has a predictive ranking methodology called Lead Scoring to identify where a prospect is in the buying cycle. Leverage the lead scoring technology to systematically score and rank leads based on their interests, buying intentions, and campaign interactions.You can automate the appropriate follow-up for each lead, whether that is to quickly send the lead to sales for a timely sales conversation or to nurture that lead with automated marketing campaigns.After implementing a lead scoring model, Oracle Eloqua will continuously re-score leads over time based on a contact’s (or account’s) actions and current behaviors.Considerations Before Implementing Lead ScoringStart with a clear definition of what a good lead means to the marketing and sales teams. The marketing and sales teams must work together to define the:Definition of a qualified leadAppropriate next steps for any qualified leads in the pipelineThese definitions will be used to create your company’s unique Lead Scoring models.Once a Lead Scoring model is created in Oracle Eloqua, your marketing team can systematically generate qualified leads, while the sales team works to close them.Target audienceMarketing LeaderMarketing TeamMore kit componentsVideoDo you know about Lead Scoring?Quick link to resourcesMy Oracle Support (MOS)Oracle Help CenterEloqua HubOracle UniversityOther Helpful LinksSupported EnvironmentsOracle Cloud ReadinessEloqua System StatusConnect with UsTopliners Eloqua InsidersCloud Customer Connect for CXPre-planning Checklist☐Set up a Qualification and CRM Routing Process FirstIf you are new to Eloqua or you do not already have a qualification process in place, set up a lead qualification and CRM routing process first. Lead scoring should come after this step. See CRM Integration for more information.☐Standardize Fields and Ensure Field Normalization Across Your DatabaseFor lead scoring to work properly, you must make sure your field values are consistent across the database. If required, change fields with different values to show the same value.For example, if region is one of the scoring criteria, ensure the region value is standard throughout the database and there are no variations, spelling mistakes, or abbreviations used for the same intended information (for example, UnitedKingdom/UK/Great Britain). See Fields and views for more information.Use picklists wherever possible to help standardize data. And make use of Contact Washing Machine app in programs to ensure field normalization. See implementing Contact Washing Machine App for more information.☐Have Enough Data on Your CustomersYou need enough data for each customer to rank one customer over another. Make sure you have an account and profile data collection process in place, along with multiple touchpoints for each customer to continually track engagement and new behaviors. See Creating multi-step campaigns for more information.☐Involve Sales in The ProcessIdentify key stakeholders in your sales team and ask them to provide insight on their ideal customer. Use their input to help create a lead scoring model. Use this training presentation to present to your marketing team and sales leaders.☐Determine How Many Lead Scoring Models Are RequiredYour company may have different business units, product lines, or geographies that require their own lead definitions and scoring criteria. For example, the North American team might have a different set of criteria than the European team.Determine how many lead scoring models are needed to fit your company’s specific needs.Support for multiple active lead score models is included in the Standard and Enterprise trims or as an add-on to the Basic package. See Multiple lead scoring models for more information.☐Roll Out Multiple Lead Scoring Models in a Phased ApproachIf your company requires multiple lead score models, plan to rollout each one in separate phases. Designate one model to be the first, set it up, and activate and optimize it. Then apply your learnings to define and implement additional lead scoring models.How Oracle Eloqua Lead Scoring Set Up WorksAt a high level, there are six steps to configure a new lead scoring model in Oracle Eloqua.1.Define your lead score model.2.Define the profile scoring criteria.3.Define the profile value rules and weighting.4.Define the engagement scoring criteria.5.Define the engagement recency and frequency.6.Configure your thresholds.7.Activate in Oracle Eloqua.Before you create your lead scoring model in Oracle Eloqua, define your profile criteria, rules, weightings, and engagement frequencies that fit your company’s specific needs. Be sure to work with your sales team for this process.1.Define your Lead Scoring ModelEffective lead scoring combines prospect demographic and behavioral data to prioritize and route leads. Lead scores in Oracle Eloqua will include a combination of profile and engagement criteria. For more information, see How Oracle Eloqua Evaluates Leads.☐Download the Lead Scoring Matrix WorkbookLeverage the Lead Scoring Matrix Workbook to guide you through the planning process. The matrix workbook will help you map out your lead scoring model and define your specific lead scoring criteria. See Lead Scoring Matrix to download the workbook.2.Define the Profile Scoring CriteriaProfile Criteria is explicit data about your lead, such as title, industry, or company revenue. This type of demographic data helps to identify the prospect and the prospect's fit.Based on the profile criteria, the lead is given a profile score of:ABCDA represents the best fit and D represents a poor fit.☐List Your Profile Criteria AttributesUse the Lead Scoring Matrix Workbook to list the profile criteria attributes that matter most to your company. SeeConfiguring profile criteria for more information.☐Start Out with Five or Less Categories for Profile CriteriaIt is recommended to start out with no more than five categories for the profile criteria. This keeps your matrix and lead scoring model simpler in the beginning. You can always add more categories and/or additional models in the future. See this Lead Scoring Training Course from Oracle University for more information.☐Ensure Close to 100% Field Completeness for The Field Chosen in The CriteriaIt is recommended to specify values for the fields chosen as the criteria for each contact in your database. Incompletefields for contacts can cause incorrect scoring. Create campaigns specifically to gather profile data for every lead.3.Define the Profile Values and WeightingAlong with defining the categories of leads that fit your organization, you will assign points and weights to each profile value to define the lead score.☐Use the Lead Scoring Matrix Workbook to prioritize the profile criteria attributes that matter the most to your company.See Configuring profile criteria for more information.☐Do Not Score On Open-Text FieldsField standardization ensures no mismatch between the contact field value and the value against which it is matched and measured. Using open-text fields means that it can hold a nonstandardized value or even one with a typing error, for example, matching US (in open text field) against Unites States of America (in lead scoring criterion).4.Define the Engagement Scoring CriteriaEngagement Criteria is implicit data, such as visits to your website and responsiveness to emails. This type of data helps to determine a lead's online behavior and indicates how interested the lead is.Based on the engagement criteria, the lead is given an engagement score of:12341 represents the most suitable and 4 represents the least suitable.See Configuring engagement data for more information.5.Define the engagement recency and frequencyAlong with defining the types of engagements that matter most to your organization, you will assign frequency and timeframes to each engagement category to define the lead score.6.Configure your thresholdsOracle Eloqua will evaluate a lead against the profile and engagement criteria. It will then combine the profile score and the engagement score to assign a lead score.A1 represents the most qualified lead and D4 represents the least qualified.You will configure the thresholds used to determine the profile score (A, B, C, or D) and engagement score (1, 2, 3, or 4).See Configuring thresholds for more information.7.Activate in Oracle EloquaOnce you have defined your first lead scoring model, you are ready to set it up in Oracle Eloqua. Follow the Steps To Create A Lead Scoring Model for step by step instructions.For C1 line – need to change ‘idea’ to ‘ideal’After ImplementationOnce you have activated your lead score model in Oracle Eloqua, use the following steps to maximize success with your lead scoring model.☐Define Appropriate Follow-UpsAfter defining a lead scoring model, map lead scores with the appropriate follow-up action.For example, you can map the specific lead to be sent to your CRM system for sales outreach or other lead scores to be sent to a nurturing program.☐Integrate Your Lead Scores with Your CRMOnce you have activated your lead model in Oracle Eloqua, you can send qualified ranked leads to your CRM. SeeIntegrating Lead Scores with Your CRM for more information.☐Segment Based on Lead ScoresYou can also start segmenting your contacts based on their lead score. See Segmenting Based on Lead Scores for more information.☐Monitor Your Lead Scoring ModelContinually re-evaluate your scoring system. It is important to monitor the impact on sales, each lead type and conversion rate. Assess the results every quarter and optimize as needed.Here are some metrics that you can track to evaluate your lead scoring model’s performance.☐Track status of leads by lead score:o What % of A leads are closing?o What % of B leads are converting from MQL (Marketing Qualified Lead) to SAL (Sales Accepted Lead)?☐Measure the impact on sales due to:o Increased sales acceptance rateo Decreased average number of days in the sales cycleo Increased revenue per dealSee Viewing the Performance of Your Leads Score Model for more information.☐Addressing Common Concerns with Lead ScoringHere are a few common issues you may run into with Lead Scoring and how to address them.☐I Don’t Have Any Highly Scored Leads ( ‘Hot Leads’)o Increase engagement through increased marketing activityo Ensure criteria are not too tight on the engagement scoring sideo Ensure criteria are not too tight on the profile scoring side☐I Have a ‘Trough’ of Engagemento Engagement criteria may be ‘all or none’ geared☐Evolvement Over Timeo The buyer and their journey will evolve, so should your Lead Scoring matrix. ResourcesOracle Eloqua Help Center for Lead ScoringGet a 90 Day Start Guide with Oracle Eloqua HubOracle University Oracle Eloqua Lead Scoring Training CourseConnect with usCall +1.800.ORACLE1 or visit . Outside North America, find your local office at: /contact. /oracle /oracle /cx/resourcesCopyright © 2021, 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. 0120 Disclaimer: This document is for informational purposes. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, timing, and pricing of any features or functionality described in this document may change and remains at the sole discretion of Oracle Corporation.。
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
医疗决策分析系统部署---先执行sqlplus /nologconnect / as sysdba----最后连接数据库connect ods/massunsoft009@orcl一、软件安装Oracle11gR2Informatica8.6.1 for 64bitInformatica8.6.1 Client for 32bit（可选）Tomcat6二、数据库部署1.创建表空间①注意路径需要修改②大小根据数据修改1.1创建hospital_base表空间及临时表空间create TABLESPACE HOSPITAL_ODS datafile 'F:\app\oracle\Administrator\oradata\orcl\HOSPITAL_ODS.dbf' SIZE 10GAUTOEXTEND ON NEXT 2g MAXSIZE 20Gextent management local;create temporary tablespace HOSPITAL_ODS_TEMP tempfilemanagement local;1.2创建BI_MO表空间及临时表空间create tablespace HOSPITAL_MO datafile 'E:\oracle\app\Administrator\oradata\my\HOSPITAL_MO.dbf' size 10g autoextend on next 2g maxsize 30g extent management local;create temporary tablespace HOSPITAL_MO_TEMP tempfile 'E:\app\oracle\Administrator\oradata\orcl\HOSPITAL_MO_TEMP.dbf' size 1g autoextend on next 1g maxsize 10g extent management local;1.3创建informatica表空间及临时表空间create TABLESPACE infa datafile 'E:\app\oracle\Administrator\oradata\orcl\infa.dbf' SIZE 2GAUTOEXTEND ON NEXT 1g MAXSIZE 5Gextent management local;create temporary tablespace INFA_TEMP tempfile 'E:\oracle\app\Administrator\oradata\my\INFA_TEMP.dbf' size 1g autoextend on next 1g maxsize 10g extent management local;1.4创建IN_BILL_RECORD分区表空间create TABLESPACE in_bill_2009 datafile 'E:\app\oracle\Administrator\oradata\orcl\in_bill_2009.dbf' SIZE 5G AUTOEXTEND ON NEXT 2g MAXSIZE 10Gextent management local;create TABLESPACE in_bill_2010 datafile 'E:\app\oracle\Administrator\oradata\orcl\in_bill_2010.dbf' SIZE 5G AUTOEXTEND ON NEXT 2g MAXSIZE 10Gextent management local;create TABLESPACE in_bill_2011 datafile 'E:\app\oracle\Administrator\oradata\orcl\in_bill_2011.dbf' SIZE 5G AUTOEXTEND ON NEXT 2g MAXSIZE 10Gextent management local;create TABLESPACE in_bill_2012 datafile 'E:\app\oracle\Administrator\oradata\orcl\in_bill_2012.dbf' SIZE 5G AUTOEXTEND ON NEXT 2g MAXSIZE 10Gextent management local;create TABLESPACE in_bill_2013 datafile 'E:\app\oracle\Administrator\oradata\orcl\in_bill_2013.dbf' SIZE 5G AUTOEXTEND ON NEXT 2g MAXSIZE 10Gextent management local;create TABLESPACE in_bill_2014 datafile 'E:\app\oracle\Administrator\oradata\orcl\in_bill_2014.dbf' SIZE 5G AUTOEXTEND ON NEXT 2g MAXSIZE 10Gextent management local;create TABLESPACE in_bill_2015 datafile 'E:\app\oracle\Administrator\oradata\orcl\in_bill_2015.dbf' SIZE 5G AUTOEXTEND ON NEXT 2g MAXSIZE 10Gextent management local;create TABLESPACE in_bill_2016 datafile 'E:\app\oracle\Administrator\oradata\orcl\in_bill_2016.dbf' SIZE 5G AUTOEXTEND ON NEXT 2g MAXSIZE 10Gextent management local;1.5创建INVOICE_DETAIL_CHARGE分区表空间create TABLESPACE invoice_detail_charge_2009 datafileextent management local;create TABLESPACE invoice_detail_charge_2010 datafile 'D:\app\Administrator\oradata\orcl\invoice_detail_charge_2010.dbf' SIZE 5G AUTOEXTEND ON NEXT 2g MAXSIZE 10G extent management local;create TABLESPACE invoice_detail_charge_2011 datafile 'D:\app\Administrator\oradata\orcl\invoice_detail_charge_2011.dbf' SIZE 5G AUTOEXTEND ON NEXT 2g MAXSIZE 10G extent management local;create TABLESPACE invoice_detail_charge_2012 datafile 'D:\app\Administrator\oradata\orcl\invoice_detail_charge_2012.dbf' SIZE 5G AUTOEXTEND ON NEXT 2g MAXSIZE 10G extent management local;create TABLESPACE invoice_detail_charge_2013 datafile 'D:\app\Administrator\oradata\orcl\invoice_detail_charge_2013.dbf' SIZE 5G AUTOEXTEND ON NEXT 2g MAXSIZE 10G extent management local;create TABLESPACE invoice_detail_charge_2014 datafile 'D:\app\Administrator\oradata\orcl\invoice_detail_charge_2014.dbf' SIZE 5G AUTOEXTEND ON NEXT 2g MAXSIZE 10G extent management local;create TABLESPACE invoice_detail_charge_2015 datafile 'D:\app\Administrator\oradata\orcl\invoice_detail_charge_2015.dbf' SIZE 5G AUTOEXTEND ON NEXT 2g MAXSIZE 10G extent management local;create TABLESPACE invoice_detail_charge_2016 datafile 'D:\app\Administrator\oradata\orcl\invoice_detail_charge_2016.dbf' SIZE 5G AUTOEXTEND ON NEXT 2g MAXSIZE 10G extent management local;1.6创建INVOICE_DETAIL_MED分区表空间create TABLESPACE invoice_detail_med_2009 datafile 'D:\app\Administrator\oradata\orcl\invoice_detail_med_2009.dbf' SIZE 5G AUTOEXTEND ON NEXT 2g MAXSIZE 10G extent management local;create TABLESPACE invoice_detail_med_2010 datafile 'D:\app\Administrator\oradata\orcl\invoice_detail_med_2010.dbf' SIZE 5G AUTOEXTEND ON NEXT 2g MAXSIZE 10G extent management local;create TABLESPACE invoice_detail_med_2011 datafile 'D:\app\Administrator\oradata\orcl\invoice_detail_med_2011.dbf' SIZE 5G AUTOEXTEND ON NEXT 2g MAXSIZE 10G extent management local;create TABLESPACE invoice_detail_med_2012 datafile 'D:\app\Administrator\oradata\orcl\invoice_detail_med_2012.dbf' SIZE 5G AUTOEXTEND ON NEXT 2g MAXSIZE 10G extent management local;create TABLESPACE invoice_detail_med_2013 datafile 'D:\app\Administrator\oradata\orcl\invoice_detail_med_2013.dbf' SIZE 5G AUTOEXTEND ON NEXT 2g MAXSIZE 10G extent management local;create TABLESPACE invoice_detail_med_2014 datafile 'D:\app\Administrator\oradata\orcl\invoice_detail_med_2014.dbf' SIZE 5G AUTOEXTEND ON NEXT 2g MAXSIZE 10G extent management local;create TABLESPACE invoice_detail_med_2015 datafile 'D:\app\Administrator\oradata\orcl\invoice_detail_med_2015.dbf' SIZE 5G AUTOEXTEND ON NEXT 2g MAXSIZE 10G extent management local;SIZE 5G AUTOEXTEND ON NEXT 2g MAXSIZE 10G extent management local;2.创建用户2.1创建用户hospital_basecreate user ods identified by massunsoft009 DEFAULT TABLESPACE HOSPITAL_ODS temporary TABLESPACE HOSPITAL_ODS_TEMP;创建其他公司登录系统的用户create user otherusers identified by otherusers009 DEFAULT TABLESPACE HOSPITAL_ODS temporary TABLESPACE HOSPITAL_ODS_TEMP;grant create session to otherusers;grant connect to otherusers;grant select on FALL_EVENT to otherusers;grant select on FALL_BED_EVENT to otherusers;2.2创建用户BI_MOcreate user BI_MO identified by BI_MO DEFAULT TABLESPACE HOSPITAL_MO temporary TABLESPACE HOSPITAL_MO_TEMP;2.3创建用户infacreate user infa identified by infa DEFAULT TABLESPACE infa temporary TABLESPACE INFA_TEMP;3.付权限3.1hospital_base用户grant connect to ods;grant resource to ods;grant select_catalog_role to ods;grant exp_full_database to ods;grant imp_full_database to ods;grant alter any index to ods;grant alter any sequence to ods;grant alter any table to ods;grant alter any trigger to ods;grant alter session to ods;grant alter system to ods;grant create any index to ods;grant create any sequence to ods;grant create any synonym to ods;grant create any trigger to ods; grant create any view to ods; grant create procedure to ods; grant create session to ods; grant create synonym to ods; grant create trigger to ods;grant create view to ods;grant delete any table to ods; grant drop any index to ods; grant drop any sequence to ods; grant drop any synonym to ods; grant drop any table to ods; grant drop any trigger to ods; grant drop any view to ods; grant insert any table to ods; grant select any sequence to ods; grant select any table to ods; grant unlimited tablespace to ods; grant update any table to ods;3.2infa用户grant connect to infa;grant resource to infa;grant select_catalog_role to infa; grant exp_full_database to infa; grant imp_full_database to infa; grant alter any index to infa; grant alter any sequence to infa; grant alter any table to infa; grant alter any trigger to infa; grant alter session to infa;grant alter system to infa;grant create any index to infa; grant create any sequence to infa; grant create any synonym to infa; grant create any table to infa; grant create any trigger to infa; grant create any view to infa; grant create procedure to infa; grant create session to infa; grant create synonym to infa; grant create trigger to infa;grant create view to infa;grant delete any table to infa; grant drop any index to infa; grant drop any sequence to infa; grant drop any synonym to infa; grant drop any table to infa; grant drop any trigger to infa; grant drop any view to infa; grant insert any table to infa; grant select any sequence to infa;grant unlimited tablespace to infa;grant update any table to infa;3.3 BI_MO用户grant connect to BI_MO;grant resource to BI_MO;grant select_catalog_role to BI_MO;grant exp_full_database to BI_MO;grant imp_full_database to BI_MO;grant alter any index to BI_MO;grant alter any sequence to BI_MO;grant alter any table to BI_MO;grant alter any trigger to BI_MO;grant alter session to BI_MO;grant alter system to BI_MO;grant create any index to BI_MO;grant create any sequence to BI_MO;grant create any synonym to BI_MO;grant create any table to BI_MO;grant create any trigger to BI_MO;grant create any view to BI_MO;grant create procedure to BI_MO;grant create session to BI_MO;grant create synonym to BI_MO;grant create trigger to BI_MO;grant create view to BI_MO;grant delete any table to BI_MO;grant drop any index to BI_MO;grant drop any sequence to BI_MO;grant drop any synonym to BI_MO;grant drop any table to BI_MO;grant drop any trigger to BI_MO;grant drop any view to BI_MO;grant insert any table to BI_MO;grant select any sequence to BI_MO;grant select any table to BI_MO;grant unlimited tablespace to BI_MO;grant update any table to BI_MO;grant select any sequence to BI_MO;grant select any table to BI_MO;GRANT debug any procedure, debug connect session TO BI_MO;4.表相关及初始化脚本4.1hospital_base用户(需要用此用户登录操作) 创建tables重新创建IN_BILL_RECORD;drop table IN_BILL_RECORD;create table IN_BILL_RECORD(HOSPITAL_ID VARCHAR2(50) not null,IN_BILL_ID NUMBER(18) not null,IN_BILL_MAIN_ID NUMBER(18),IN_ORDER_ID NUMBER(18),IN_BILL_TYPE INTEGER,FLAG_FIX VARCHAR2(1),ORDER_MAIN_ID NUMBER(18),IN_PAT_ID NUMBER(18),PAT_IN_HOS_ID NUMBER(18),GROUP_TYPE INTEGER,BILL_GROUP_ID NUMBER(18),BABY_ID NUMBER(18),CHARGE_PRICE_ID NUMBER(18),CHARGE_PRICE_NAME VARCHAR2(100),INVOICE_ITEM_ID VARCHAR2(5),ACCOUNT_ITEM_ID VARCHAR2(5),MED_REC_ITEM_ID VARCHAR2(5),BILL_ITEM_ID VARCHAR2(5),FINANCE_ITEM_ID VARCHAR2(5),CHARGE_UNIT INTEGER,UNIT_NAME VARCHAR2(50),SPEC VARCHAR2(100),PRICE NUMBER(18,4),QUANTITY NUMBER(18,4),PAT_IN_DEPT VARCHAR2(30),PAT_WARD_ID VARCHAR2(30),ORDER_DEPT_ID VARCHAR2(30),EXEC_DEPT_ID VARCHAR2(30),BILL_DEPT_ID VARCHAR2(30),DEPT_ACCOUNT_SEC VARCHAR2(30),NURSING_DEPT_SEC VARCHAR2(30),CHANGE_DEPT_ID NUMBER(18),CHANGE_WARD_ID NUMBER(18),ORDER_DOC_ID VARCHAR2(35),BILL_NURSE_ID VARCHAR2(35),EXEC_NURSE_ID VARCHAR2(35),EXEC_DOC_ID VARCHAR2(30),TALLY_TIME DATE,AMOUNT NUMBER(18,4),GET_AMOUNT NUMBER(18,4),PREFER_AMOUNT NUMBER(18,4),SETTLE_TIME INTEGER,DISPENSE_DETAIL_ID NUMBER(18),BILL_SOURCE INTEGER,DOC_ID1 VARCHAR2(35),DOC_ID2 VARCHAR2(35),DOC_ID3 VARCHAR2(35),DOC_ID4 VARCHAR2(35),SETTLE_DATE_TIME DATE,TALLY_TIME_SETTLE DATE,CHARGE_CLASS_ID INTEGER,SELF_BURDEN_RATIO NUMBER(18,4),FLAG_SUB VARCHAR2(1),FLAG_SUPER VARCHAR2(1),PARENT_CHARGE_ID NUMBER(18),FLAG_NETWORK_UPLOAD VARCHAR2(1),constraint PK_IN_BILL_RECORD primary key (HOSPITAL_ID, IN_BILL_ID)) PARTITION BY RANGE(create_time)(PARTITION part01 VALUES LESS THAN(TO_DATE('2009-12-31 00:00:00','yyyy-mm-dd hh24:mi:ss')) TABLESPACE in_bill_2009,PARTITION part02 VALUES LESS THAN(TO_DATE('2010-12-31 00:00:00','yyyy-mm-dd hh24:mi:ss')) TABLESPACE in_bill_2010,PARTITION part03 VALUES LESS THAN(TO_DATE('2011-12-31 00:00:00','yyyy-mm-dd hh24:mi:ss')) TABLESPACE in_bill_2011,PARTITION part04 VALUES LESS THAN(TO_DATE('2012-12-31 00:00:00','yyyy-mm-dd hh24:mi:ss')) TABLESPACE in_bill_2012,PARTITION part05 VALUES LESS THAN(TO_DATE('2013-12-31 00:00:00','yyyy-mm-dd hh24:mi:ss')) TABLESPACE in_bill_2013,PARTITION part06 VALUES LESS THAN(TO_DATE('2014-12-31 00:00:00','yyyy-mm-dd hh24:mi:ss')) TABLESPACE in_bill_2014,PARTITION part07 VALUES LESS THAN(TO_DATE('2015-12-31 00:00:00','yyyy-mm-dd hh24:mi:ss')) TABLESPACE in_bill_2015,PARTITION part08 VALUES LESS THAN(TO_DATE('2016-12-31 00:00:00','yyyy-mm-dd hh24:mi:ss')) TABLESPACE in_bill_2016,PARTITION part09 VALUES LESS THAN (MAXVALUE)TABLESPACE HOSPITAL_ODS);comment on table IN_BILL_RECORD is'住院费用记录表';comment on column IN_BILL_RECORD.HOSPITAL_ID is'所属医院的id';comment on column IN_BILL_RECORD.IN_BILL_ID is'住院患者费用主记录编号';comment on column IN_BILL_RECORD.IN_BILL_MAIN_ID is'住院费用主记录编号，每个';comment on column IN_BILL_RECORD.IN_ORDER_ID is'住院正式医嘱系统编号';comment on column IN_BILL_RECORD.IN_BILL_TYPE is'费用类型，小于100说明是药品其中10-60 说明是西药60-80说明是中成药81-90说明是中草药小于10 说明是其他类别药品大于100说明是费用1000-2000说明是化验室项目2001-3000说明是放射项目3001-4000 说明是门诊小手术类4000-5000 说明是其他';comment on column IN_BILL_RECORD.FLAG_FIX is'是否是固定费用';comment on column IN_BILL_RECORD.ORDER_MAIN_ID is'医嘱主编号';comment on column IN_BILL_RECORD.IN_PAT_ID is'入院患者的系统编号';comment on column IN_BILL_RECORD.PAT_IN_HOS_ID is'入院登记记录ID';comment on column IN_BILL_RECORD.GROUP_TYPE is'费用的套餐类型';comment on column IN_BILL_RECORD.BILL_GROUP_ID is'费用套餐使用记录编号没有则为-1';comment on column IN_BILL_RECORD.BABY_ID is'子患者编号';comment on column IN_BILL_RECORD.CHARGE_PRICE_ID is'计费项目编号(到明细)';comment on column IN_BILL_RECORD.CHARGE_PRICE_NAME is'计价项目名称';comment on column IN_BILL_RECORD.INVOICE_ITEM_ID is'发票项目';comment on column IN_BILL_RECORD.ACCOUNT_ITEM_ID is'核算项目';comment on column IN_BILL_RECORD.MED_REC_ITEM_ID is'病案项目系统编号';comment on column IN_BILL_RECORD.BILL_ITEM_ID is'收入项目';comment on column IN_BILL_RECORD.FINANCE_ITEM_ID is'财务项目';comment on column IN_BILL_RECORD.CHARGE_UNIT is'费用单位编号';comment on column IN_BILL_RECORD.UNIT_NAME is'剂量单位名称';'费用或者药品的规格';comment on column IN_BILL_RECORD.PRICE is'单价';comment on column IN_BILL_RECORD.QUANTITY is'数量';comment on column IN_BILL_RECORD.PAT_IN_DEPT is'住院科室';comment on column IN_BILL_RECORD.PAT_WARD_ID is'患者所在病区的编号';comment on column IN_BILL_RECORD.ORDER_DEPT_ID is'医嘱科室编号';comment on column IN_BILL_RECORD.EXEC_DEPT_ID is'执行科室编号';comment on column IN_BILL_RECORD.BILL_DEPT_ID is'计价科室编号';comment on column IN_BILL_RECORD.DEPT_ACCOUNT_SEC is '第二核算科室编号';comment on column IN_BILL_RECORD.NURSING_DEPT_SEC is '第二核算护理单元编号';comment on column IN_BILL_RECORD.CHANGE_DEPT_ID is '最近的一次转科记录编号';comment on column IN_BILL_RECORD.CHANGE_WARD_ID is '最近的一次转病区记录编号';comment on column IN_BILL_RECORD.ORDER_DOC_ID is'开单医生编号';comment on column IN_BILL_RECORD.BILL_NURSE_ID is'开单护士编号';comment on column IN_BILL_RECORD.EXEC_NURSE_ID is'执行护士编号';comment on column IN_BILL_RECORD.EXEC_DOC_ID is'执行医生编号,一般指的是医技项目';comment on column IN_BILL_RECORD.CREATE_TIME is'计费时间';comment on column IN_BILL_RECORD.TALLY_TIME is'记账时间';comment on column IN_BILL_RECORD.AMOUNT iscomment on column IN_BILL_RECORD.GET_AMOUNT is'实际金额';comment on column IN_BILL_RECORD.PREFER_AMOUNT is'优惠金额';comment on column IN_BILL_RECORD.SETTLE_TIME is'对应的中途结算次数相当于结算标志';comment on column IN_BILL_RECORD.DISPENSE_DETAIL_ID is'--------------- 汇总摆药的明细记录编号';comment on column IN_BILL_RECORD.BILL_SOURCE is'记账来源：1.护士执行；2.医技执行；3.发药；4.住院处执行；5.作业程序执行';comment on column IN_BILL_RECORD.DOC_ID1 is'用于核算的医生的编号';comment on column IN_BILL_RECORD.DOC_ID2 is'用于核算的医生的编号';comment on column IN_BILL_RECORD.DOC_ID3 is'用于核算的医生的编号';comment on column IN_BILL_RECORD.DOC_ID4 is'用于核算的医生的编号';comment on column IN_BILL_RECORD.SETTLE_DATE_TIME is'结算时间（再次结算不更新该字段）';comment on column IN_BILL_RECORD.TALLY_TIME_SETTLE is'记账时间（只对出院患者有效）';comment on column IN_BILL_RECORD.CHARGE_CLASS_ID is'医嘱录入时，患者的费别ID';comment on column IN_BILL_RECORD.SELF_BURDEN_RATIO is'自付比例（小数形式，如自付20%，值为0.2）';comment on column IN_BILL_RECORD.FLAG_SUB is'是否是子项目';comment on column IN_BILL_RECORD.FLAG_SUPER is'是否是组合父项目';comment on column IN_BILL_RECORD.PARENT_CHARGE_ID is'医疗项目父项目ID';comment on column IN_BILL_RECORD.FLAG_NETWORK_UPLOAD is'联网报销项目是否已经上传';重新创建INVOICE_DETAILS_MEDdrop table INVOICE_DETAILS_MED cascade constraints;create table INVOICE_DETAILS_MED(HOSPITAL_ID VARCHAR2(50) not null, INVOICE_DETAIL_ID NUMBER(18) not null, INVOICE_ID NUMBER(18),DOC_SYS_ID VARCHAR2(35),BILL_DEPT_ID VARCHAR2(30),EXE_DEPT_ID VARCHAR2(30),QUANTITY NUMBER(18,4),UNIT VARCHAR2(20),PRICE NUMBER(18,4),CHARGE_ID NUMBER(18),AMOUNT NUMBER(18,4),PREFERENTIAL_AMOUNT NUMBER(18,4),MED_INSURANCE_AMOUNT NUMBER(18,4),GET_AMOUNT NUMBER(18,4),SPEC VARCHAR2(50),DOSE NUMBER(18,4),DOSE_UNIT VARCHAR2(50),USAGE_ID INTEGER,FREQUENCY_ID INTEGER,DAYS_COUNT INTEGER,SET_COUNT INTEGER,FLAG_EXEC VARCHAR2(1),FLAG_UNDO VARCHAR2(1),CHARGE_TYPE INTEGER,ORDER_NO INTEGER,ORDER_ID NUMBER(18),FLAG_GROUP VARCHAR2(1),GROUP_AMOUNT INTEGER,ORDER_MAIN_ID NUMBER(18),REGISTER_ID NUMBER(18),FLAG_DOC VARCHAR2(1),ID2 NUMBER(18),ID1 NUMBER(18),COL1 VARCHAR2(30),COL2 VARCHAR2(30),INVOICE_ITEM_ID VARCHAR2(5),ACCOUNT_ITEM_ID VARCHAR2(5),MED_REC_ITEM_ID VARCHAR2(5),BILL_ITEM_ID VARCHAR2(5),FINANCE_ITEM_ID VARCHAR2(5),ENTER_USER_SYS_ID VARCHAR2(35),DRUG_PRODUCE_ID NUMBER(18),PRES_CODE VARCHAR2(30),OUT_PAT_ID NUMBER(18),OUT_CARD_ID NUMBER(18),FLAG_PAYMENT VARCHAR2(1),SETTLE_TIME DATE,EXE_TIME DATE,ACCOUNT_RECORDS_ID NUMBER(18),CARD_PAY_TYPE INTEGER,CHARGE_CLASS_ID INTEGER,CREATE_TIME DATE,SELF_BURDEN_RATIO NUMBER(18,4),PARENT_CHARGE_PRICE_ID NUMBER(18),FLAG_SUPER VARCHAR2(1),constraint PK_INVOICE_DETAILS_MED primary key (HOSPITAL_ID, INVOICE_DETAIL_ID))PARTITION BY RANGE(create_time)(PARTITION part01 VALUES LESS THAN(TO_DATE('2009-12-31 00:00:00','yyyy-mm-dd hh24:mi:ss')) TABLESPACE invoice_detail_med_2009,PARTITION part02 VALUES LESS THAN(TO_DATE('2010-12-31 00:00:00','yyyy-mm-dd hh24:mi:ss')) TABLESPACE invoice_detail_med_2010,PARTITION part03 VALUES LESS THAN(TO_DATE('2011-12-31 00:00:00','yyyy-mm-dd hh24:mi:ss')) TABLESPACE invoice_detail_med_2011,PARTITION part04 VALUES LESS THAN(TO_DATE('2012-12-31 00:00:00','yyyy-mm-dd hh24:mi:ss')) TABLESPACE invoice_detail_med_2012,PARTITION part05 VALUES LESS THAN(TO_DATE('2013-12-31 00:00:00','yyyy-mm-dd hh24:mi:ss')) TABLESPACE invoice_detail_med_2013,PARTITION part06 VALUES LESS THAN(TO_DATE('2014-12-31 00:00:00','yyyy-mm-dd hh24:mi:ss')) TABLESPACE invoice_detail_med_2014,PARTITION part07 VALUES LESS THAN(TO_DATE('2015-12-31 00:00:00','yyyy-mm-dd hh24:mi:ss')) TABLESPACE invoice_detail_med_2015,PARTITION part08 VALUES LESS THAN(TO_DATE('2016-12-31 00:00:00','yyyy-mm-dd hh24:mi:ss')) TABLESPACE invoice_detail_med_2016,PARTITION part09 VALUES LESS THAN (MAXVALUE)TABLESPACE HOSPITAL_ODS);comment on table INVOICE_DETAILS_MED is'药品发票明细表，记录门诊发票的明细项目';comment on column INVOICE_DETAILS_MED.INVOICE_DETAIL_ID is'门诊发票明细流水与费用发票明细表主键不能重复';comment on column INVOICE_DETAILS_MED.INVOICE_ID is'费用明细对应的发票系统号';comment on column INVOICE_DETAILS_MED.DOC_SYS_ID is'开单医生编号';comment on column INVOICE_DETAILS_MED.BILL_DEPT_ID is'开单科室编号';comment on column INVOICE_DETAILS_MED.EXE_DEPT_ID is'执行科室编号';comment on column INVOICE_DETAILS_MED.QUANTITY is'数量';comment on column INVOICE_DETAILS_MED.UNIT is'数量单位';comment on column INVOICE_DETAILS_MED.PRICE is'单价';comment on column INVOICE_DETAILS_MED.CHARGE_ID is'系统计价编号';comment on column INVOICE_DETAILS_MED.AMOUNT is'合计金额=实际支付金额+医保报销类总金额+优惠金额';comment on column INVOICE_DETAILS_MED.PREFERENTIAL_AMOUNT is'优惠金额';comment on column INVOICE_DETAILS_MED.MED_INSURANCE_AMOUNT is '医保报销类总金额';comment on column INVOICE_DETAILS_MED.GET_AMOUNT is'实际支付金额';comment on column INVOICE_DETAILS_MED.SPEC is'规格';comment on column INVOICE_DETAILS_MED.DOSE is'剂量';comment on column INVOICE_DETAILS_MED.DOSE_UNIT is'剂量单位';comment on column INVOICE_DETAILS_AGE_ID is'用法的系统id';comment on column INVOICE_DETAILS_MED.FREQUENCY_ID is'频率的系统id';comment on column INVOICE_DETAILS_MED.DAYS_COUNT is'服用天数';comment on column INVOICE_DETAILS_MED.SET_COUNT is'草药付数';comment on column INVOICE_DETAILS_MED.FLAG_EXEC is'执行标志:拿药后置1';comment on column INVOICE_DETAILS_MED.FLAG_UNDO is'退药执行标志,药房退药后置1';comment on column INVOICE_DETAILS_MED.CHARGE_TYPE is'指定类型小于100 说明是药品大于100 说明是医疗';comment on column INVOICE_DETAILS_MED.ORDER_NO is'子医嘱处方的序号';comment on column INVOICE_DETAILS_MED.ORDER_ID is'该项目所对应处方的处方编号';comment on column INVOICE_DETAILS_MED.FLAG_GROUP is'是否是一套项目，比如化验，中药等';comment on column INVOICE_DETAILS_MED.GROUP_AMOUNT is'套餐的数量';comment on column INVOICE_DETAILS_MED.ORDER_MAIN_ID is'医嘱主编号,相同医嘱主编号的代表是同一组医嘱,该组编号的生成规则';comment on column INVOICE_DETAILS_MED.REGISTER_ID is'对应的挂号ID';comment on column INVOICE_DETAILS_MED.FLAG_DOC is'是否是从医生那里下的医嘱如果是医生下的医嘱则在医生医嘱表中有数据';comment on column INVOICE_DETAILS_MED.ID2 is'备用编号2';comment on column INVOICE_DETAILS_MED.ID1 is'备用ID编号';comment on column INVOICE_DETAILS_MED.COL1 is'备用字段1';comment on column INVOICE_DETAILS_MED.COL2 is'备用字段2';comment on column INVOICE_DETAILS_MED.INVOICE_ITEM_ID is'发票项目';comment on column INVOICE_DETAILS_MED.ACCOUNT_ITEM_ID is'核算项目';comment on column INVOICE_DETAILS_MED.MED_REC_ITEM_ID is'病案项目系统编号';comment on column INVOICE_DETAILS_MED.BILL_ITEM_ID is'收入项目';comment on column INVOICE_DETAILS_MED.FINANCE_ITEM_ID is'财务项目';comment on column INVOICE_DETAILS_MED.ENTER_USER_SYS_ID is'最初录入记录的操作员编号';comment on column INVOICE_DETAILS_MED.DRUG_PRODUCE_ID is'药品到产地的系统编号';comment on column INVOICE_DETAILS_MED.PRES_CODE is'处方编号';comment on column INVOICE_DETAILS_MED.OUT_PAT_ID is'患者ID';comment on column INVOICE_DETAILS_MED.OUT_CARD_ID is'就诊卡ID';comment on column INVOICE_DETAILS_MED.FLAG_PAYMENT is'卡支付标志';comment on column INVOICE_DETAILS_MED.SETTLE_TIME is'结算时间';comment on column INVOICE_DETAILS_MED.EXE_TIME is'执行时间';comment on column INVOICE_DETAILS_MED.ACCOUNT_RECORDS_ID is'扣费流水ID';comment on column INVOICE_DETAILS_MED.CARD_PAY_TYPE is'表明当前发票的卡支付类型，根据实际情况进行扩展。