Oracle EBS-SQL (MRP-7):检查MRP计划运行报错原因之超大数据查询2.sql

The following scripts can be used to check for huge line numbers:

-- PO Requisitions

select * from PO_REQUISITION_LINES_ALL where LINE_NUM > 1000000000;

-- PO Lines

select * from PO_LINES_ALL where LINE_NUM > 1000000000;

-- Receiving Supply

SELECT * FROM PO_RCV_SUPPLY_VIEW WHERE LINE_NUM > 1000000000;

-- Requisition Supply

SELECT * FROM PO_REQ_SUPPLY_VIEW WHERE LINE_NUM > 1000000000;

-- PO Supply

SELECT * FROM PO_PO_SUPPLY_VIEW WHERE LINE_NUM > 1000000000;

-- Intransit Shipment Supply

SELECT * FROM PO_SHIP_SUPPLY_VIEW WHERE SHIPMENT_LINE_NUM >
1000000000;

-- Intransit Receiving Supply

SELECT * FROM PO_SHIP_RCV_SUPPLY_VIEW WHERE SHIPMENT_LINE_NUM >
1000000000;

--

-- Receiving Supply

SELECT * FROM PO_RCV_SUPPLY_VIEW WHERE LINE_NUM > 1000000000;

-- Requisition Supply

SELECT * FROM PO_REQ_SUPPLY_VIEW WHERE LINE_NUM > 1000000000;

-- PO Supply

SELECT * FROM PO_PO_SUPPLY_VIEW WHERE LINE_NUM > 1000000000;

-- Intransit Shipment Supply

SELECT * FROM PO_SHIP_SUPPLY_VIEW WHERE SHIPMENT_LINE_NUM >
1000000000;

-- Intransit Receiving Supply

SELECT * FROM PO_SHIP_RCV_SUPPLY_VIEW WHERE SHIPMENT_LINE_NUM >
1000000000;

Refer to below view when running MRP with check "Net Purchase" in

plan option.

( PO_RCV_SUPPLY_VIEW, PO_REQ_SUPPLY_VIEW,
PO_PO_SUPPLY_VIEW,PO_SHIP_SUPPLY_VIEW, PO_SHIP_RCV_SUPPLY_VIEW )

SELECT * FROM MRP_PO_SUPPLY_VIEW WHERE SUPPLY_LINE_NUM > 1000000000

Oracle EBS-SQL (MRP-7):检查MRP计划运行报错原因之超大数据查询2.sql,布布扣,bubuko.com

时间: 2024-10-11 12:32:26

Oracle EBS-SQL (MRP-7):检查MRP计划运行报错原因之超大数据查询2.sql的相关文章

『ORACLE』DG搭建时备库的db_name报错

因为搭建DG时备库中的db_name为SBCD,实际应该是主库db_name的PROD1 所以在[主库]执行如下rman操作命令时会报错控制文件记录的数据库名与实际拷贝的数据库名不相同 RMAN> duplicate target database for standby from active database; Starting Duplicate Db at 01-MAY-17using target database control file instead of recovery ca

oracle 11g 手动删除表空间文件导致数据库报错处理方法

简单说下原因:当时图方便没进数据库,直接在datafile目录下删除了表空间对应的数据文件 导致后来数据库报错,并且不能删除表空间 错误如下:ORA-01116:error in opening database ****ORA-01110:data file 54:'/home3/datafile/arrange/NewArrange.dbf'ORA-27041:unable to open fileLinux Error:2: No Such file or directoryAdditio

Tips:SQL server 2012报表服务器error 40报错

在现有的SQL server 2012 SP1数据库上启用reporting services功能后,发现无法配置报表数据库,如下图报错. provider:命名管道提供程序 error:40-无法打开到SQL server的连接 解决方法: 需要打开SQL server配置管理器,找到SQL server网络配置,找到实例项目的TCP/IP协议,把静态端口修改为1433,如图. 然后就可以正常连接到SQL server配置报表数据库了.

SQL Server datetime类型转换超出范围的报错

一个很基础的插入语句: insert into table1 select col1,convert(datetime,col2),convert(datetime,col3),col4,col5 from table2 其中table1表中col2,col3是datetime类型,其他都是varchar类型,table2全部是varchar类型. table2表中全部是varchar类型,col 1 4 5都有可能是空值. 在执行时报出如下错误: 消息 242,级别 16,状态 3,第 1 行

关于在使用sparksql写程序是报错以及解决方案:org.apache.spark.sql.AnalysisException: Duplicate column(s): "name" found, cannot save to file.

说明: spark --version : 2.2.0 我有两个json文件,分别是emp和dept: emp内容如下: {"name": "zhangsan", "age": 26, "depId": 1, "gender": "male", "salary": 20000} {"name": "lisi", "ag

mybatis的报错总结_____2Error updating database. Cause: java.sql.SQLSyntaxErrorException: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the ri

在编写动态sql时 trim的属性写错了,如下图: 错误示范: (接口的xml配置文件中:) 1 <update id="modifyBill" parameterType="Bill"> 2 update smbms_bill 3 <trim suffix="set" prefixOverrides="," prefix="where id=#{id}"> 4 <if tes

Oracle database wrc运行报错ORA-15557

[[email protected] capture]$ wrc system/[email protected] REPLAYDIR=/home/oracle/cap_dir/ Workload Replay Client: Release 11.1.0.7.0 - Production on Sun Jul 19 17:16:56 2015 Copyright (c) 1982, 2007, Oracle. All rights reserved. The client could not

jbpm3.2中jbpm.jpdl.mysql.sql文件运行报错的问题

这是一个很久之前遇到的问题,就是用从官网下下载的jbpm组件,它的jbpm.jpdl.mysql.sql不能正常运行.其原因是该sql文件中有一句语句有错误.现在附上正确的jbpm.jpdl.mysql.sql文件代码: ;alter table JBPM_ACTION drop foreign key FK_ACTION_REFACT ;alter table JBPM_ACTION drop foreign key FK_CRTETIMERACT_TA ;alter table JBPM_A

ODI接口运行报错 911 : 42000 :java.sql.SQLException: ORA-00911:无效字符

参见博客http://blog.csdn.net/lzflydream/article/details/20570813 这上面这么说的,但是大神们说的太高端了我不知道怎么解决   911 : 42000 :java.sql.SQLException: ORA-00911: invalid character KM中多了一个分号,KM每一句不需要分号. 最终,在Operator监视器界面点击错误所在,勾选忽略错误,重新启动此会话.问题解决了. 错误根源:源数据库与目标数据库表对应时字段类型对应不