Deadlock: select and DDL

Hello,
I have an Oracle application. We have select sql statements and statements to enable constraints (for example, foreign keys and primary Key). The Select SQL statements and statement to enable constraints may be executed in parallel. Sometimes, we get deadlock. Can someone explain to me why the deadlock happened?
Thanks,
Edited by: slsam01 on Apr 3, 2009 3:18 PM

Very bad things are happening here. Can't understand why this basic concept is being misunderstood.
1. The document you pointed is not of Oracle. It's about berkley DB which I've never used. :(
2. The truth about locking in the select query.
- Oracle never(again never!) acquires table lock(TM lock) nor row level lock(TX lock) for the select query.
- select ... for update statement needs TM lock in RS mode and TX lock in X mode. It's just like DML statement.
- The parse phase(not execute phase) needs the library cache related lock for the target table. For instance, during the soft parse phase, Oracle acquires library cache lock on the table. During the hard parse(optimization) phase, Oracle acquires the library cache pin on the table.
It's Oracle's promise that select statements never lock the table in the macro level(TM lock, TX lock). But in the micro level, it sometimes need to lock the table. Library cache lock and library cache pin are good examples.
================================
Dion Cho - Oracle Performance Storyteller
http://dioncho.wordpress.com (english)
http://ukja.tistory.com (korean)
================================

Similar Messages

Audit All DML and DDL on an Application Schema

Hello;
I have a requirement to audit all DML and DDL on an Application Schema (Lets say SCOTT). I have set:
ALTER SYSTEM SET audit_trail = XML, EXTENDED scope=spfile; -- Want my audit log on the OS with Bind and SQL.
ALTER SYSTEM SET AUDIT_SYS_OPERATIONS = TRUE scope=spfile; -- Want to audit sysdba and sysoper activity
audit create session; -- Want to see both logins and failed logins
How would I get all DML and DDL on an Application Schema (SCOTT)?
I am using 11iR1 Standard Edition.

Have look at system_privilege_map and find all the options you need to audit...
or you can use the below script..
SELECT 'audit ' ||LOWER(name) || ' by app_user;'
FROM system_privilege_map;
if you want to filter-out the one you have already audited, then use dba_priv_audit_opts ...
Hope this info will be useful to you...
Thanks,

Require DML and DDL for basic tables

Hello,
I want to pursue my oracle certification within 2-3 months. Therefore, I am eager to create basic tables those would provide me holistic idea and basic practices before my real test. Could you provide me basic tables for example, employee table, department table, sales table etc.with DML and DDL details? I do create plethora of DB objects when I build systems for clients; however, additionally, I intend to practice concepts whatever I will acquire after going through oracle books before certification.
Thanks!

Here is the sample script i took it from HR & SH Schemas.
host echo Building Oracle demonstration tables. Please wait.
set termout off
DROP TABLE EMP;
DROP TABLE DEPT;
DROP TABLE BONUS;
DROP TABLE SALGRADE;
DROP TABLE DUMMY;
DROP TABLE ITEM;
DROP TABLE PRICE;
DROP TABLE PRODUCT;
DROP TABLE ORD;
DROP TABLE CUSTOMER;
DROP VIEW SALES;
DROP SEQUENCE ORDID;
DROP SEQUENCE CUSTID;
DROP SEQUENCE PRODID;
CREATE TABLE DEPT (
DEPTNO NUMBER(2) NOT NULL,
DNAME VARCHAR2(14),
LOC VARCHAR2(13),
CONSTRAINT DEPT_PRIMARY_KEY PRIMARY KEY (DEPTNO));
INSERT INTO DEPT VALUES (10,'ACCOUNTING','NEW YORK');
INSERT INTO DEPT VALUES (20,'RESEARCH','DALLAS');
INSERT INTO DEPT VALUES (30,'SALES','CHICAGO');
INSERT INTO DEPT VALUES (40,'OPERATIONS','BOSTON');
CREATE TABLE EMP (
EMPNO NUMBER(4) NOT NULL,
ENAME VARCHAR2(10),
JOB VARCHAR2(9),
MGR NUMBER(4) CONSTRAINT EMP_SELF_KEY REFERENCES EMP (EMPNO),
HIREDATE DATE,
SAL NUMBER(7,2),
COMM NUMBER(7,2),
DEPTNO NUMBER(2) NOT NULL,
CONSTRAINT EMP_FOREIGN_KEY FOREIGN KEY (DEPTNO) REFERENCES DEPT (DEPTNO),
CONSTRAINT EMP_PRIMARY_KEY PRIMARY KEY (EMPNO));
INSERT INTO EMP VALUES (7839,'KING','PRESIDENT',NULL,'17-NOV-81',5000,NULL,10);
INSERT INTO EMP VALUES (7698,'BLAKE','MANAGER',7839,'1-MAY-81',2850,NULL,30);
INSERT INTO EMP VALUES (7782,'CLARK','MANAGER',7839,'9-JUN-81',2450,NULL,10);
INSERT INTO EMP VALUES (7566,'JONES','MANAGER',7839,'2-APR-81',2975,NULL,20);
INSERT INTO EMP VALUES (7654,'MARTIN','SALESMAN',7698,'28-SEP-81',1250,1400,30);
INSERT INTO EMP VALUES (7499,'ALLEN','SALESMAN',7698,'20-FEB-81',1600,300,30);
INSERT INTO EMP VALUES (7844,'TURNER','SALESMAN',7698,'8-SEP-81',1500,0,30);
INSERT INTO EMP VALUES (7900,'JAMES','CLERK',7698,'3-DEC-81',950,NULL,30);
INSERT INTO EMP VALUES (7521,'WARD','SALESMAN',7698,'22-FEB-81',1250,500,30);
INSERT INTO EMP VALUES (7902,'FORD','ANALYST',7566,'3-DEC-81',3000,NULL,20);
INSERT INTO EMP VALUES (7369,'SMITH','CLERK',7902,'17-DEC-80',800,NULL,20);
INSERT INTO EMP VALUES (7788,'SCOTT','ANALYST',7566,'09-DEC-82',3000,NULL,20);
INSERT INTO EMP VALUES (7876,'ADAMS','CLERK',7788,'12-JAN-83',1100,NULL,20);
INSERT INTO EMP VALUES (7934,'MILLER','CLERK',7782,'23-JAN-82',1300,NULL,10);
CREATE TABLE BONUS (
ENAME VARCHAR2(10),
JOB CHAR(9),
SAL NUMBER,
COMM NUMBER);
CREATE TABLE SALGRADE (
GRADE NUMBER,
LOSAL NUMBER,
HISAL NUMBER);
INSERT INTO SALGRADE VALUES (1,700,1200);
INSERT INTO SALGRADE VALUES (2,1201,1400);
INSERT INTO SALGRADE VALUES (3,1401,2000);
INSERT INTO SALGRADE VALUES (4,2001,3000);
INSERT INTO SALGRADE VALUES (5,3001,9999);
CREATE TABLE DUMMY (
DUMMY NUMBER );
INSERT INTO DUMMY VALUES (0);
CREATE TABLE CUSTOMER (
CUSTID NUMBER (6) NOT NULL,
NAME VARCHAR2(45),
ADDRESS VARCHAR2(40),
CITY VARCHAR2(30),
STATE VARCHAR2(2),
ZIP VARCHAR2(9),
AREA NUMBER (3),
PHONE VARCHAR2(9),
REPID NUMBER (4) NOT NULL,
CREDITLIMIT NUMBER (9,2),
COMMENTS LONG,
CONSTRAINT CUSTOMER_PRIMARY_KEY PRIMARY KEY (CUSTID),
CONSTRAINT CUSTID_ZERO CHECK (CUSTID > 0));
CREATE TABLE ORD (
ORDID NUMBER (4) NOT NULL,
ORDERDATE DATE,
COMMPLAN VARCHAR2(1),
CUSTID NUMBER (6) NOT NULL,
SHIPDATE DATE,
TOTAL NUMBER (8,2) CONSTRAINT TOTAL_ZERO CHECK (TOTAL >= 0),
CONSTRAINT ORD_FOREIGN_KEY FOREIGN KEY (CUSTID) REFERENCES CUSTOMER (CUSTID),
CONSTRAINT ORD_PRIMARY_KEY PRIMARY KEY (ORDID));
CREATE TABLE ITEM (
ORDID NUMBER (4) NOT NULL,
ITEMID NUMBER (4) NOT NULL,
PRODID NUMBER (6),
ACTUALPRICE NUMBER (8,2),
QTY NUMBER (8),
ITEMTOT NUMBER (8,2),
CONSTRAINT ITEM_FOREIGN_KEY FOREIGN KEY (ORDID) REFERENCES ORD (ORDID),
CONSTRAINT ITEM_PRIMARY_KEY PRIMARY KEY (ORDID,ITEMID));
CREATE TABLE PRODUCT (
PRODID NUMBER (6) CONSTRAINT PRODUCT_PRIMARY_KEY PRIMARY KEY,
DESCRIP VARCHAR2(30));
CREATE TABLE PRICE (
PRODID NUMBER (6) NOT NULL,
STDPRICE NUMBER (8,2),
MINPRICE NUMBER (8,2),
STARTDATE DATE,
ENDDATE DATE);
INSERT INTO CUSTOMER (ZIP, STATE, REPID, PHONE, NAME, CUSTID, CREDITLIMIT,
CITY, AREA, ADDRESS, COMMENTS)
VALUES ('96711', 'CA', '7844', '598-6609',
'JOCKSPORTS',
'100', '5000', 'BELMONT', '415', '345 VIEWRIDGE',
'Very friendly people to work with -- sales rep likes to be called Mike.');
INSERT INTO CUSTOMER (ZIP, STATE, REPID, PHONE, NAME, CUSTID, CREDITLIMIT,
CITY, AREA, ADDRESS, COMMENTS)
VALUES ('94061', 'CA', '7521', '368-1223',
'TKB SPORT SHOP',
'101', '10000', 'REDWOOD CITY', '415', '490 BOLI RD.',
'Rep called 5/8 about change in order - contact shipping.');
INSERT INTO CUSTOMER (ZIP, STATE, REPID, PHONE, NAME, CUSTID, CREDITLIMIT,
CITY, AREA, ADDRESS, COMMENTS)
VALUES ('95133', 'CA', '7654', '644-3341',
'VOLLYRITE',
'102', '7000', 'BURLINGAME', '415', '9722 HAMILTON',
'Company doing heavy promotion beginning 10/89. Prepare for large orders during
winter.');
INSERT INTO CUSTOMER (ZIP, STATE, REPID, PHONE, NAME, CUSTID, CREDITLIMIT,
CITY, AREA, ADDRESS, COMMENTS)
VALUES ('97544', 'CA', '7521', '677-9312',
'JUST TENNIS',
'103', '3000', 'BURLINGAME', '415', 'HILLVIEW MALL',
'Contact rep about new line of tennis rackets.');
INSERT INTO CUSTOMER (ZIP, STATE, REPID, PHONE, NAME, CUSTID, CREDITLIMIT,
CITY, AREA, ADDRESS, COMMENTS)
VALUES ('93301', 'CA', '7499', '996-2323',
'EVERY MOUNTAIN',
'104', '10000', 'CUPERTINO', '408', '574 SURRY RD.',
'Customer with high market share (23%) due to aggressive advertising.');
INSERT INTO CUSTOMER (ZIP, STATE, REPID, PHONE, NAME, CUSTID, CREDITLIMIT,
CITY, AREA, ADDRESS, COMMENTS)
VALUES ('91003', 'CA', '7844', '376-9966',
'K + T SPORTS',
'105', '5000', 'SANTA CLARA', '408', '3476 EL PASEO',
'Tends to order large amounts of merchandise at once. Accounting is considering
raising their credit limit. Usually pays on time.');
INSERT INTO CUSTOMER (ZIP, STATE, REPID, PHONE, NAME, CUSTID, CREDITLIMIT,
CITY, AREA, ADDRESS, COMMENTS)
VALUES ('94301', 'CA', '7521', '364-9777',
'SHAPE UP',
'106', '6000', 'PALO ALTO', '415', '908 SEQUOIA',
'Support intensive. Orders small amounts (< 800) of merchandise at a time.');
INSERT INTO CUSTOMER (ZIP, STATE, REPID, PHONE, NAME, CUSTID, CREDITLIMIT,
CITY, AREA, ADDRESS, COMMENTS)
VALUES ('93301', 'CA', '7499', '967-4398',
'WOMENS SPORTS',
'107', '10000', 'SUNNYVALE', '408', 'VALCO VILLAGE',
'First sporting goods store geared exclusively towards women. Unusual promotion
al style and very willing to take chances towards new products!');
INSERT INTO CUSTOMER (ZIP, STATE, REPID, PHONE, NAME, CUSTID, CREDITLIMIT,
CITY, AREA, ADDRESS, COMMENTS)
VALUES ('55649', 'MN', '7844', '566-9123',
'NORTH WOODS HEALTH AND FITNESS SUPPLY CENTER',
'108', '8000', 'HIBBING', '612', '98 LONE PINE WAY', '');
INSERT INTO ORD (TOTAL, SHIPDATE, ORDID, ORDERDATE, CUSTID, COMMPLAN)
VALUES ('101.4', '08-JAN-87', '610', '07-JAN-87', '101', 'A');
INSERT INTO ORD (TOTAL, SHIPDATE, ORDID, ORDERDATE, CUSTID, COMMPLAN)
VALUES ('45', '11-JAN-87', '611', '11-JAN-87', '102', 'B');
INSERT INTO ORD (TOTAL, SHIPDATE, ORDID, ORDERDATE, CUSTID, COMMPLAN)
VALUES ('5860', '20-JAN-87', '612', '15-JAN-87', '104', 'C');
INSERT INTO ORD (TOTAL, SHIPDATE, ORDID, ORDERDATE, CUSTID, COMMPLAN)
VALUES ('2.4', '30-MAY-86', '601', '01-MAY-86', '106', 'A');
INSERT INTO ORD (TOTAL, SHIPDATE, ORDID, ORDERDATE, CUSTID, COMMPLAN)
VALUES ('56', '20-JUN-86', '602', '05-JUN-86', '102', 'B');
INSERT INTO ORD (TOTAL, SHIPDATE, ORDID, ORDERDATE, CUSTID, COMMPLAN)
VALUES ('698', '30-JUN-86', '604', '15-JUN-86', '106', 'A');
INSERT INTO ORD (TOTAL, SHIPDATE, ORDID, ORDERDATE, CUSTID, COMMPLAN)
VALUES ('8324', '30-JUL-86', '605', '14-JUL-86', '106', 'A');
INSERT INTO ORD (TOTAL, SHIPDATE, ORDID, ORDERDATE, CUSTID, COMMPLAN)
VALUES ('3.4', '30-JUL-86', '606', '14-JUL-86', '100', 'A');
INSERT INTO ORD (TOTAL, SHIPDATE, ORDID, ORDERDATE, CUSTID, COMMPLAN)
VALUES ('97.5', '15-AUG-86', '609', '01-AUG-86', '100', 'B');
INSERT INTO ORD (TOTAL, SHIPDATE, ORDID, ORDERDATE, CUSTID, COMMPLAN)
VALUES ('5.6', '18-JUL-86', '607', '18-JUL-86', '104', 'C');
INSERT INTO ORD (TOTAL, SHIPDATE, ORDID, ORDERDATE, CUSTID, COMMPLAN)
VALUES ('35.2', '25-JUL-86', '608', '25-JUL-86', '104', 'C');
INSERT INTO ORD (TOTAL, SHIPDATE, ORDID, ORDERDATE, CUSTID, COMMPLAN)
VALUES ('224', '05-JUN-86', '603', '05-JUN-86', '102', '');
INSERT INTO ORD (TOTAL, SHIPDATE, ORDID, ORDERDATE, CUSTID, COMMPLAN)
VALUES ('4450', '12-MAR-87', '620', '12-MAR-87', '100', '');
INSERT INTO ORD (TOTAL, SHIPDATE, ORDID, ORDERDATE, CUSTID, COMMPLAN)
VALUES ('6400', '01-FEB-87', '613', '01-FEB-87', '108', '');
INSERT INTO ORD (TOTAL, SHIPDATE, ORDID, ORDERDATE, CUSTID, COMMPLAN)
VALUES ('23940', '05-FEB-87', '614', '01-FEB-87', '102', '');
INSERT INTO ORD (TOTAL, SHIPDATE, ORDID, ORDERDATE, CUSTID, COMMPLAN)
VALUES ('764', '10-FEB-87', '616', '03-FEB-87', '103', '');
INSERT INTO ORD (TOTAL, SHIPDATE, ORDID, ORDERDATE, CUSTID, COMMPLAN)
VALUES ('1260', '04-FEB-87', '619', '22-FEB-87', '104', '');
INSERT INTO ORD (TOTAL, SHIPDATE, ORDID, ORDERDATE, CUSTID, COMMPLAN)
VALUES ('46370', '03-MAR-87', '617', '05-FEB-87', '105', '');
INSERT INTO ORD (TOTAL, SHIPDATE, ORDID, ORDERDATE, CUSTID, COMMPLAN)
VALUES ('710', '06-FEB-87', '615', '01-FEB-87', '107', '');
INSERT INTO ORD (TOTAL, SHIPDATE, ORDID, ORDERDATE, CUSTID, COMMPLAN)
VALUES ('3510.5', '06-MAR-87', '618', '15-FEB-87', '102', 'A');
INSERT INTO ORD (TOTAL, SHIPDATE, ORDID, ORDERDATE, CUSTID, COMMPLAN)
VALUES ('730', '01-JAN-87', '621', '15-MAR-87', '100', 'A');
INSERT INTO ITEM (QTY, PRODID, ORDID, ITEMTOT, ITEMID, ACTUALPRICE)
VALUES ('1', '100890', '610', '58', '3', '58');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ( '1', '100861', '611', '45', '1', '45');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ( '100', '100860', '612', '3000', '1', '30');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ( '1', '200376', '601', '2.4', '1', '2.4');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ( '20', '100870', '602', '56', '1', '2.8');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ( '3', '100890', '604', '174', '1', '58');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ( '2', '100861', '604', '84', '2', '42');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ( '10', '100860', '604', '440', '3', '44');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ( '4', '100860', '603', '224', '2', '56');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ( '1', '100860', '610', '35', '1', '35');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ( '3', '100870', '610', '8.4', '2', '2.8');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ( '200', '200376', '613', '440', '4', '2.2');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ( '444', '100860', '614', '15540', '1', '35');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ( '1000', '100870', '614', '2800', '2', '2.8');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ( '20', '100861', '612', '810', '2', '40.5');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('150', '101863', '612', '1500', '3', '10');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('10', '100860', '620', '350', '1', '35');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('1000', '200376', '620', '2400', '2', '2.4');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('500', '102130', '620', '1700', '3', '3.4');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ( '100', '100871', '613', '560', '1', '5.6');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('200', '101860', '613', '4800', '2', '24');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('150', '200380', '613', '600', '3', '4');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('100', '102130', '619', '340', '3', '3.4');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('50', '100860', '617', '1750', '1', '35');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('100', '100861', '617', '4500', '2', '45');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('1000', '100871', '614', '5600', '3', '5.6');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('10', '100861', '616', '450', '1', '45');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('50', '100870', '616', '140', '2', '2.8');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('2', '100890', '616', '116', '3', '58');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('10', '102130', '616', '34', '4', '3.4');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('10', '200376' , '616', '24', '5', '2.4');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('100', '200380', '619', '400', '1', '4');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('100', '200376', '619', '240', '2', '2.4');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('4', '100861', '615', '180', '1', '45');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('1', '100871', '607', '5.6', '1', '5.6');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('100', '100870', '615', '280', '2', '2.8');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('500', '100870', '617', '1400', '3', '2.8');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('500', '100871', '617', '2800', '4', '5.6');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('500', '100890', '617', '29000', '5', '58');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('100', '101860', '617', '2400', '6', '24');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('200', '101863', '617', '2500', '7', '12.5');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('100', '102130', '617', '340', '8', '3.4');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('200', '200376', '617', '480', '9', '2.4');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('300', '200380', '617', '1200', '10', '4');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('5', '100870', '609', '12.5', '2', '2.5');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('1', '100890', '609', '50', '3', '50');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('23', '100860', '618', '805', '1', '35');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('50', '100861', '618', '2255.5', '2', '45.11');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('10', '100870', '618', '450', '3', '45');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('10', '100861', '621', '450', '1', '45');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('100', '100870', '621', '280', '2', '2.8');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('50', '100871', '615', '250', '3', '5');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('1', '101860', '608', '24', '1', '24');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('2', '100871', '608', '11.2', '2', '5.6');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('1', '100861', '609', '35', '1', '35');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('1', '102130', '606', '3.4', '1', '3.4');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('100', '100861', '605', '4500', '1', '45');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('500', '100870', '605', '1400', '2', '2.8');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('5', '100890', '605', '290', '3', '58');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('50', '101860', '605', '1200', '4', '24');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('100', '101863', '605', '900', '5', '9');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('10', '102130', '605', '34', '6', '3.4');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('100', '100871', '612', '550', '4', '5.5');
INSERT INTO ITEM ( QTY , PRODID , ORDID , ITEMTOT , ITEMID , ACTUALPRICE)
VALUES ('50', '100871', '619', '280', '4', '5.6');
INSERT INTO PRICE (STDPRICE, STARTDATE, PRODID, MINPRICE, ENDDATE)
VALUES ('4.8', '01-JAN-85', '100871', '3.2', '01-DEC-85');
INSERT INTO PRICE (STDPRICE, STARTDATE, PRODID, MINPRICE, ENDDATE)
VALUES ('58', '01-JAN-85', '100890', '46.4', '');
INSERT INTO PRICE (STDPRICE, STARTDATE, PRODID, MINPRICE, ENDDATE)
VALUES ('54', '01-JUN-84', '100890', '40.5', '31-MAY-84');
INSERT INTO PRICE (STDPRICE, STARTDATE, PRODID, MINPRICE, ENDDATE)
VALUES ('35', '01-JUN-86', '100860', '28', '');
INSERT INTO PRICE (STDPRICE, STARTDATE, PRODID, MINPRICE, ENDDATE)
VALUES ('32', '01-JAN-86', '100860', '25.6', '31-MAY-86');
INSERT INTO PRICE (STDPRICE, STARTDATE, PRODID, MINPRICE, ENDDATE)
VALUES ('30', '01-JAN-85', '100860', '24', '31-DEC-85');
INSERT INTO PRICE (STDPRICE, STARTDATE, PRODID, MINPRICE, ENDDATE)
VALUES ('45', '01-JUN-86', '100861', '36', '');
INSERT INTO PRICE (STDPRICE, STARTDATE, PRODID, MINPRICE, ENDDATE)
VALUES ('42', '01-JAN-86', '100861', '33.6', '31-MAY-86');
INSERT INTO PRICE (STDPRICE, STARTDATE, PRODID, MINPRICE, ENDDATE)
VALUES ('39', '01-JAN-85', '100861', '31.2', '31-DEC-85');
INSERT INTO PRICE (STDPRICE, STARTDATE, PRODID, MINPRICE, ENDDATE)
VALUES ('2.8', '01-JAN-86', '100870', '2.4', '');
INSERT INTO PRICE (STDPRICE, STARTDATE, PRODID, MINPRICE, ENDDATE)
VALUES ('2.4', '01-JAN-85', '100870', '1.9', '01-DEC-85');
INSERT INTO PRICE (STDPRICE, STARTDATE, PRODID, MINPRICE, ENDDATE)
VALUES ('5.6', '01-JAN-86', '100871', '4.8', '');
INSERT INTO PRICE (STDPRICE, STARTDATE, PRODID, MINPRICE, ENDDATE)
VALUES ('24', '15-FEB-85', '101860', '18', '');
INSERT INTO PRICE (STDPRICE, STARTDATE, PRODID, MINPRICE, ENDDATE)
VALUES ('12.5', '15-FEB-85', '101863', '9.4', '');
INSERT INTO PRICE (STDPRICE, STARTDATE, PRODID, MINPRICE, ENDDATE)
VALUES ('3.4', '18-AUG-85', '102130', '2.8', '');
INSERT INTO PRICE (STDPRICE, STARTDATE, PRODID, MINPRICE, ENDDATE)
VALUES ('2.4', '15-NOV-86', '200376', '1.75', '');
INSERT INTO PRICE (STDPRICE, STARTDATE, PRODID, MINPRICE, ENDDATE)
VALUES ('4', '15-NOV-86', '200380', '3.2', '');
CREATE INDEX PRICE_INDEX ON PRICE(PRODID, STARTDATE);
INSERT INTO PRODUCT (PRODID, DESCRIP)
VALUES ('100860', 'ACE TENNIS RACKET I');
INSERT INTO PRODUCT (PRODID, DESCRIP)
VALUES ('100861', 'ACE TENNIS RACKET II');
INSERT INTO PRODUCT (PRODID, DESCRIP)
VALUES ('100870', 'ACE TENNIS BALLS-3 PACK');
INSERT INTO PRODUCT (PRODID, DESCRIP)
VALUES ('100871', 'ACE TENNIS BALLS-6 PACK');
INSERT INTO PRODUCT (PRODID, DESCRIP)
VALUES ('100890', 'ACE TENNIS NET');
INSERT INTO PRODUCT (PRODID, DESCRIP)
VALUES ('101860', 'SP TENNIS RACKET');
INSERT INTO PRODUCT (PRODID, DESCRIP)
VALUES ('101863', 'SP JUNIOR RACKET');
INSERT INTO PRODUCT (PRODID, DESCRIP)
VALUES ('102130', 'RH: "GUIDE TO TENNIS"');
INSERT INTO PRODUCT (PRODID, DESCRIP)
VALUES ('200376', 'SB ENERGY BAR-6 PACK');
INSERT INTO PRODUCT (PRODID, DESCRIP)
VALUES ('200380', 'SB VITA SNACK-6 PACK');
CREATE SEQUENCE ORDID
INCREMENT BY 1
START WITH 622
NOCACHE;
CREATE SEQUENCE PRODID
INCREMENT BY 1
START WITH 200381
NOCACHE;
CREATE SEQUENCE CUSTID
INCREMENT BY 1
START WITH 109
NOCACHE;
CREATE VIEW SALES AS
SELECT REPID, ORD.CUSTID, CUSTOMER.NAME CUSTNAME, PRODUCT.PRODID,
DESCRIP PRODNAME, SUM(ITEMTOT) AMOUNT
FROM ORD, ITEM, CUSTOMER, PRODUCT
WHERE ORD.ORDID = ITEM.ORDID
AND ORD.CUSTID = CUSTOMER.CUSTID
AND ITEM.PRODID = PRODUCT.PRODID
GROUP BY REPID, ORD.CUSTID, NAME, PRODUCT.PRODID, DESCRIP;

Rerunning script (DML and DDL) without ora-00001 and ora-00955 errors

What is the best way to write a DML and DDL script so that it can be run multiple times without these ORA errors:
ORA-00955: name is already used by an existing object
ORA-00001: unique constraint (JILL.SYS_C00160247) violated
I have just joined a product development company using SQL Server as there primary database. They have just completed a port to Oracle.
Their product release upgrades (given to clients) include sql scripts with database changes (structure and data). They require that the client be able to rerun the scripts more than once with no errors. In SQL Server, the accomplish it this way.
For DDL:
if not exists (select * from dbo.sysobjects where id = object_id(N'[dbo].[MyTab]') and OBJECTPROPERTY(id, N'IsUserTable') = 1)
Begin
     CREATE TABLE [dbo].[MyTab] (
          [ID]int IDENTITY(1,1),
          [InvID] uniqueidentifier not null
For DML:
IF NOT EXISTS (SELECT 1 FROM [dbo].[mytab] WHERE [Name] = 'Smith' and [ID] = 3)
BEGIN
INSERT INTO [dbo].[mytab]
([ID] ,[Name]
VALUES (3,'Smith')
END
I am tasked with duplicating this logic on the Oracle side. The only way I can think of so far is using plsql and checking for existence before every insert and create statement. The other options I thought of cannot be used in this case
- "whenever sqlerror continue" - gives the same response for all errors. True errors should stop the code, so this is too risky.
- "log errors into ... reject limit unlimited" on the insert - I thought this was my best solution until I found out that it doesn't support lobs.
Do you know of any more elegant (and more efficient) solution other than plsql cursors to check for existence before running each insert/create?
Any suggestions would be greatly appreciated.

select table_name from user_tables will give you the table exist or not.
all_tables/dba_tables
http://download.oracle.com/docs/cd/B14117_01/server.101/b10755/statviews_1190.htm#i1592091

Trigger to audit DML and DDL nor working

Requirement: Application team complains that everyday within a fixed timeframe, 1 entry from a particular table is being deleted. They are unable to track it, which particular job is it doing it.
DBA: We had 3 solutions: 1. AUDIT_TRAIL
2. FGA
3. Customized TRIGGER to track the DML and DDL.
After discussion, option 3 has been implemented. Here is the code.
DML Trigger
=======
CREATE OR REPLACE TRIGGER SLCPROD.STORE_TERM_ID_HST_TRG
BEFORE INSERT OR UPDATE OR DELETE
ON SLCPROD.STORE_TERM_ID FOR EACH ROW
BEGIN
IF UPDATING THEN
INSERT INTO STORE_TERM_ID_HIST
( STR_NUM,
TERM_ID,
HOST_ENV,
USR_TERMINAL,
SESSION_USR,
OS_USER,
ACTION_DATE,
ACTION_NAME)
VALUES
( TRUNC(:OLD.STR_NUM)||','||:NEW.STR_NUM,
TRUNC(:OLD.TERM_ID)||','||:NEW.TERM_ID,
sys_context('USERENV', 'HOST'),
sys_context('USERENV', 'TERMINAL'),
sys_context('USERENV', 'SESSION_USER'),
sys_context('USERENV', 'OS_USER'),
SYSDATE,
'UPDATE');
ELSIF DELETING THEN
INSERT INTO STORE_TERM_ID_HIST
( STR_NUM,
TERM_ID,
HOST_ENV,
USR_TERMINAL,
SESSION_USR,
OS_USER,
ACTION_DATE,
ACTION_NAME)
VALUES
( :OLD.STR_NUM,
:OLD.TERM_ID,
sys_context('USERENV', 'HOST'),
sys_context('USERENV', 'TERMINAL'),
sys_context('USERENV', 'SESSION_USER'),
sys_context('USERENV', 'OS_USER'),
SYSDATE,
'DELETE');
END IF;
END;
DDL Trigger
========
CREATE OR REPLACE TRIGGER SLCPROD.STORE_TERM_ID_HST_TRG_TRUNC
AFTER DDL ON DATABASE
declare
object_name varchar2(30);
BEGIN
select distinct ora_dict_obj_name into object_name from dual;
if UPPER(object_name)= 'STORE_TERM_ID'
then
INSERT INTO STORE_TERM_ID_HIST
( STR_NUM,
TERM_ID,
HOST_ENV,
USR_TERMINAL,
SESSION_USR,
OS_USER,
ACTION_DATE,
ACTION_NAME)
VALUES
( 'NA',
'NA',
sys_context('USERENV', 'HOST'),
sys_context('USERENV', 'TERMINAL'),
sys_context('USERENV', 'SESSION_USER'),
sys_context('USERENV', 'OS_USER'),
SYSDATE,
ora_sysevent);
END IF;
END;
TABLE STORE_TERM_ID_HIST DESC
=======================
Name Null? Type
STR_NUM CHAR(25)
TERM_ID CHAR(25)
HOST_ENV VARCHAR2(50)
USR_TERMINAL VARCHAR2(50)
SESSION_USR VARCHAR2(50)
OS_USER VARCHAR2(50)
ACTION_DATE DATE
ACTION_NAME VARCHAR2(50)
Though we have these triggers in place, still we can see that 1 record is getting deleted (do not know how as I haven't been able to track it) between 8 AM - 8:50 AM. We have verified it from COUNT and also know which particular record is getting deleted.
We tried to see if any error logged due to these triggers in ALERT logs, but no error specific to it has been seen. We have tested the TRIGGERs using manuals queries, and they seem to be working fine.
Could anyone please help what could be happening here? Or any better solution of resolving it.
Thanks,
Tapan
Edited by: TapanKumar Saha on Mar 31, 2013 10:04 PM
updated the code.

Thank you all for all the help.
My issue is resolved now. Here is the analysis:
Our triggers (both for DML and DDL) were working earlier as well. However, it was not capturing the actions. We could see that last_ddl_date is being updated with the time when we are expecting the mischievous to happen. So, after having internal discussions, we concluded that "ALTER INDEX.." could also update the last_ddl_date. But it has nothing to do with the DELETE. However, to track the INDEX DDLs we added trigger on INDEX as well. Here is the modified code:
DDL Trigger
=======
CREATE OR REPLACE TRIGGER SLCPROD.STORE_TERM_ID_HST_TRG_TRUNC
AFTER DDL ON DATABASE
declare
object_name varchar2(30);
BEGIN
select distinct ora_dict_obj_name into object_name from dual;
if UPPER(object_name)= 'STORE_TERM_ID'
then
INSERT INTO STORE_TERM_ID_HIST
( STR_NUM,
TERM_ID,
HOST_ENV,
USR_TERMINAL,
SESSION_USR,
OS_USER,
ACTION_DATE,
ACTION_NAME)
VALUES
( 'NA',
'NA',
sys_context('USERENV', 'HOST'),
sys_context('USERENV', 'TERMINAL'),
sys_context('USERENV', 'SESSION_USER'),
sys_context('USERENV', 'OS_USER'),
SYSDATE,
ora_sysevent);
elsif UPPER(object_name)= 'STORE_TERM_ID_PK'
then
INSERT INTO STORE_TERM_ID_HIST
+( STR_NUM,+
TERM_ID,
HOST_ENV,
USR_TERMINAL,
SESSION_USR,
OS_USER,
ACTION_DATE,
ACTION_NAME)
VALUES
+( 'NA',+
+'NA',+
sys_context('USERENV', 'HOST'),
sys_context('USERENV', 'TERMINAL'),
sys_context('USERENV', 'SESSION_USER'),
sys_context('USERENV', 'OS_USER'),
SYSDATE,
ora_sysevent);
END IF;
END;
It started tracking the TRUNCATE on the table.
Also, we we increased the length of the data types for the temporary table to avoid any insertion errors. And finally put an INSERT trigger after seeing TRUNCATE DDLs. And we thus we resolved the issue.

Select and update with lock exclusive

Hello Everybody
In our application we have a table autonum     to handle unique keys for all other tables.
In Autonum we have a column "SUCHBEGRIFF" char(40) unique KEY and a column "WERT" fixed(10,0).
Suchbegriff has values like Rechnungsnr,Auftragsnr,Bestellnr ...
Example:
Befor inserting a record into table rechnungen we do:
Select wert from autonun where suchbegriff = "Rechnungsnr" with lock exclusive.
l_rechnrneu = wert + 1
update autonum set wert = ?l_rechnrneu where suchbegriff = "Rechnungsnr"
commit
(then l_rechnrneu is used for an insert into rechnungen command)
This technic works for all tables (250) in our application.
We have about 400 concurrent users working with maxdb 7.6 via odbc 7.6
No problems since 2 years!
Now we start some backgroundjobs from an xp-workstation.
We have scheduled 5 jobs, starting every 5 minutes, same time.(Same user,same odbc-connection)
Each job inserts records into a table joblogs and therefore needs a unique JOBLOGNR from autonum.
Now we run into problems 2 or 3 times a day?
<Sometimes the backgound jobs are running (waiting?) without inserting a record into joblogs (deadlock?)
And more worse:
Sometimes the insert into joblogs failes with "duplicate key" ??
We don't know where to begin? Maxdb Problem ? Workstation problem?
Any help welcomed
Best regards
Albert

> >Gosh - that's information overloading at it's best...
> We call this needed information.
> What does our SAP-System? We have 1 mandt,60 accounting areas and about 200 werks!
> Of course SAP uses internal unique keys for all tables, but we configured different "number intervals" for each werks.
With "information overloading" I was referring to the multiple meanings you encode in just one column (your "rechnungs-no").
SAP tables do not have this.
As you wrote, there is "MANDT", "BUKRS", "WERKS" ... and the primary key is defined over all relevant columns.
There is no primary key column where all the different meanings are concatenated together.
So there aren't any surrogate keys here (a.k.a. AUTOID) used here - (ok except the infamous DDLOG sequence...).
> >What do you do, when the value of an invoice has to be changed? Update the primary key of the table?
> Update rechnungen set amount = xyz,...... where rechnungnr = nnn
> We never change rechnungsnr,if the invoice was wrong we produce a credit for it and then write a new invoice
So, you could use a sequence here instead as well.
> > We don't use rollback when fetching logids from autonum.
> >So what do you do, when connection fails, the database crashes or the client application hits an error?
> >You use rollback. There is no way to avoid it.
> >Your application gets a "duplicate key" error - the database performs a rollback of your last action. What does your application do then? Commit?
> Sorry, i meant that we do not do rollbacks over 2 or 3 inserts or updates in different tables.
> SQL-Command,On error = messagebox,errorlog,quit
You don't handle the fetching of the new number in the same transaction as the actual insert of your application data in the same transaction?
> >What isolation level do you use?
> We use DATABASE ISOLATION LEVEL 0
Hmm... did you read the documentation on SQL Locks?
[Internals Course - SQL Locks|http://maxdb.sap.com/training/internals_7.6/locking_EN_76.pdf] :
"Isolation level 0 does not offer any protection against access anomalies."
Basically it might have happened that the same number is read twice.
Perhaps the application is not always requiring locks when reading data from this table?
> After connecting to the database via odbc we do
> =SQLSETPROP(verbindungsnr,"Transactions",2)
> 2 = Transaction processing is handled manually through SQLCOMMIT( ) and SQLROLLBACK( ). Read/write.
> =SQLSETPROP(verbindungsnr,"DisconnectRollback",.T.)
>
>
> So normal select commands are fired without a following commit.
> Insert and update commands are fired with a following commit command.
> Selects from autonum are fired with "look exclusive"
Please be more detailed here.
What is the exact sequence of actions here?
1. Fetch number from number table and update number table.
2. COMMIT
3. Insert new application data with the just fetched number.
4. COMMIT
or
1. Fetch number from number table and update number table.
2. Insert new application data with the just fetched number.
3. COMMIT
And what does your application do with its data when a rollback occurs?
Is it guaranteed that all variables are reset?
> Nevertheless you dislike our design, do you think it would be better (quicker,safer...) to use an internal databases procedure to get
> the next speaking number for a given "suchbegriff" from our autonum table? (no translation of the sql-command every time)
No, currently we don't know what is causing the problem, so we cannot tell whether such a change would help. In fact, right now it would make things more complicated because we would less understand, what's happening here.
Concerning your design: it's not about "liking" or "not liking it".
I just pointed out some problems that result from the design as it is.
> select   wert into :neuerwert FROM "BWPROGI"."AUTONUM" WHERE upper(suchbegriff)     = upper(:suchkey) WITH LOCK EXCLUSIVE;
> update "BWPROGI"."AUTONUM" set wert = wert + 1 WHERE upper(suchbegriff)     = upper(:suchkey) ;
> SET neuerwert = neuerwert + 1;
> end;
1. The WHERE clause UPPER(suchbegriff) = UPPER(...) is the best way to disable the efficient use of any index structure. Better make sure that your data is in the right format in the table when you enter it and then look it up without the UPPER() conversion.
2. I wouldn't perform the increment two times.
Get the current value into your variable, increment this variable, set the current value in the table to the variable.
> A char(10) return value would be nice and i don't know wether this would be the quicker way.
Why should it? You would have to convert it first - that's additional work.
Anyhow, to move ahead with your duplicate keys problem, you may perform a vtrace with the "stop on error" option.
As your error is a duplicate key on a primary key constraint you should set "stop on error" to the error code "200".
The next time your application hits the error, the vtrace automatically stops and we could examine what happened before.
See [MaxDB database trace|https://wiki.sdn.sap.com/wiki/x/2yg] for details on how to activate the trace.
When the error occurs next time and you caught it in the vtrace we can take a look at it.
regards,
Lars

Exporting apps and ddl

Is there an easy way to export the app and any associated ddl in one step. It looks like you export the app by itself. Then you select the ddl components separately. Is that the correct method?
Why is ddl that is generated and then exported placed into an '*.accept' file?

I would be nice if a unique directory could be created for each export consisting of ALL exportable items, plus data. (Athough more abstract datatypes like BLOBs and TIMESTAMPs might be a problem.)
Its teadious having to do it for each export type.
Also, in a import (restore) situation, I could nominate a directory that contains all the items i need to fully install/restore a HTML DB application.
Basically a magic button that does everything in one shot! I think its too fragmented.
(I think this is one of the 3 major areas of improvement, backup/recovery/installation, plus software reusability and documentation.)

ADF 11g can not select and copy data from cell of readonly table in IE

hi,
In ADF 11g, when render view object as readonly table with Single RowsSelection, using IE browser can not select and copy data from the cell, but it work in firefox.
is it a bug?
Edited by: kent2066 on 2009-5-18 上午8:46

Hi Timo,
Sorry forgot to mention versions.
We are using 11.1.1.7 and IE 9.
I tried in Google but could not get the solution.
Kindly let me know solution for this.
PavanKumar

What is the diffrence between "Key to Select" and "Selected Key" while creating Radio Buttons?

While creating radio buttons there is a confusion regarding two properties "Key to Select" and "Selected Key".Can anybody explain it with example?
Thanks,
Vimal

Hi Vimal,
Please find my explanation as below
Key to Select: This is the unique key for each radio button to identify which one is selected
Selected Key: This holds the "KEY" of selected radio button
Example:
   Let us say we have 2 radio buttons : Male & Female
     Create a context attribute SELECTED_KEY of type STRING.
     Create an action ON_SELECT for radio button select event
     Now,
     the properties for "MALE" radio button as below
          KEY_TO_SELECT = 'M'
          SELECTED_KEY = "bind to the context attribute SELECTED_KEY
          OnSelect = 'ON_SELECT'.
     The properties for 'Female" radio button as below
          KEY_TO_SELECT = 'F'
          SELECTED_KEY = "bind to the context attribute SELECTED_KEY
          OnSelect = 'ON_SELECT'.
If we select radio button 'Male', we get the key as 'M' and for 'Female' radio button 'F'.
check inside the event handler method ONACTIONON_SELECT, you get the 'KEY' of selected radio button.
So, the context attribute 'SELECTED_KEY' gets filled with the key of selected radio button
Hope this helps you in distinguishing the 'KEY TO SELECT' & 'SELECTED KEY' .
Regards,
Rama

Partition Name in Select and Group-By

Is there a function that returns the partition name a row is stored in? I'd like to use it in a SELECT statement, if it exists.
The goal is to get row counts per partition to determine skew on a hash-based partition (otherwise, I'd just select and group-by the partition key). I want to do something like this:
SELECT PARTITION_NAME, COUNT(*) as PER_PART_COUNT
FROM SOMETABLE
GROUP BY PARTITION_NAME;Obviously, I would replace the string "*PARTITION_NAME*" with whatever function returns that value.
NOTE: Before the forum sharks jump all over me, I did search the documentation and forums, but I came up empty handed.

Hi,
This is hokey - but you can use the undocumented function "tbl$or$idx$part$num" like so:
SELECT   atp.partition_name
       , COUNT (*) AS count_rows
    FROM all_tab_partitions atp
       , (SELECT tbl$or$idx$part$num ("SCOTT"."TAB1"
                                    , 0
                                    , 1
                                    , 0
                                    , partition_col1 -- your 1st partition key column
                                    , partition_col2 -- your 2nd partition key column
                                     ) AS part_num
               , 'TAB1' AS table_name
               , 'SCOTT' AS owner
            FROM scott.tab1) pt
   WHERE atp.table_name = pt.table_name
     AND atp.table_owner = pt.owner
     AND atp.partition_position = pt.part_num
GROUP BY atp.partition_name;Note - this probably won't perform well at all... but it could be an option...
Message was edited by:
PDaddy
... On 2nd thought - don't do it - it seems it is pretty unstable - brought my session to a halt a couple of times... Forget I mentioned it :)
... On 3rd thought - if you add ROWNUM - it works fine - seems you need to materialize the result set in the inner query - like so:
CREATE TABLE part_tab (part_key int
                     , a int
partition by range (part_key)
(partition p1 values less than (100)
,partition p2 values less than (200)
,partition p3 values less than (maxvalue)
insert into part_tab
select rownum
     , rownum
FROM all_objects
where rownum <= 1000; SELECT atp.partition_name
     , COUNT(*) AS count_rows
FROM all_tab_partitions atp
   , (SELECT TBL$OR$IDX$PART$NUM("PART_TAB", 0, 1, 0, part_key) AS part_num
           , 'PART_TAB' AS table_name
           , user AS owner
           , ROWNUM AS rn -- Materialize the result set by adding ROWNUM...
      FROM part_tab) pt
WHERE atp.table_name = pt.table_name
AND atp.table_owner = pt.owner
AND atp.partition_position = pt.part_num
GROUP BY atp.partition_name;

Difference between Select *    and Select single     ?

difference between Select *    and Select single     ?

HI,
DATA : IT TYPE TABLE OF MARA,
           WA TYPE MARA.
Here it selects all the record and keeps in internal table it.
Select * from mara into corresponding fields of table <b> it</b>.
Here it slects only one record that to first record.
If you wnat any specific record then use where condition.
Select single * from mara into corresponding fields of <b>wa</b>.
Message was edited by:
        Purshothaman P

Not able to select and copy from adf table in IE and chrome if we enable row selection

Hi All,
We have an adf table and user wants to select and copy table cell values.
We enabled row selection on adf table. Ifrow selection is in place, IE and Chrome are not allowing user to select and copy data. But Firefox is allowing.
Do we have any solution to this? For our customer IE is the standard browser and they do test app on IE.
Regards
PavanKumar

Hi Timo,
Sorry forgot to mention versions.
We are using 11.1.1.7 and IE 9.
I tried in Google but could not get the solution.
Kindly let me know solution for this.
PavanKumar

Unable to delete email from trash bin. How do I do this? If I select and chose delete, it doesn't. What am I doing wrong? My grand daughte is using my iPad and I don't want her to see some of the mail there.

Unable to delete email from trash bin. How do I do this? If I select and chose delete, it doesn't. What am I doing wrong? My grand daughte is using my iPad and I don't want her to see some of the mail there.

There are two ways that should work. When you are in the trash folder, you can swipe on the email in the list - left to right - and a red Delete button should pop up. Or you can select - Edit - at the top of the list of messages and then select the message and tap delete.
Not sure exactly how this works - but if you have restrictions enabled - especially since you let your grandchild use the device - that may be restricting what you can do in the mail app. Go to Settings>General>Restrictions. If you have it set to on - turn it off or see if you have mail restricted.

How to use AT LINE-SELECTION and AT USER-COMMAND in one report????

Dear all,
I have a problem in reports I want to use AT USER-COMMAND.and AT LINE-SELECTION.both in the one report.
But as soon as I use SET PF-STATUS my AT LINE-SELECTION event stop workingand only AT USER-COMMAND is working.
How can I use both of them in one report for your reference I am giving my test program below.
REPORT ZTEST111 .
SET PF-STATUS '100'.
DO 10 TIMES.
WRITE:/ SY-INDEX.
HIDE SY-INDEX.
ENDDO.
START-OF-SELECTION.
AT LINE-SELECTION.
MESSAGE I002(SY) WITH SY-INDEX.
AT USER-COMMAND.
MESSAGE I002(SY) WITH 'USER COMMAND'.
END-OF-SELECTION.
Thanks in advance
Sachin Gautam

hi
Syntax
AT USER-COMMAND.
Effect
This statement defines an event block whose event is triggered by the ABAP runtime environment if, during the display of a screen list, a function with a self-defined function code was chosen.
Note
Self-defined function codes are all those that include character combinations, except for the following:
The function codes PICK and PF## ("##" stands for 01 to 24) do not cause the event AT USER-COMMAND, but the events AT LINE-SELECTION and AT PF##.
All function codes that start with the character "%" are interpreted as system functions and do not cause the event AT USER-COMMAND. The system functions for lists are listed in the following table 1.
The function codes in the following table 2, likewise, do not cause the event AT USER-COMMAND, but are handled by the list processor.
Table 1
Function code Function
%CTX Call a context menu
%EX Exit
%PC Save to file
%PRI Print
%SC Search for ...
%SC+ Find next
%SL Search in office
%ST Save to report tree
Table 2
Function code Function
BACK Back
P- Scroll to previous page
P-- Scroll to first page
P+ Scroll to next page
P++ Scroll to last page
PFILE name Store list lines in a text file named abap.lst in standard character representation in the standard directory of the application server. If a name is entered using name, this is converted to lowercase letters and used as the file name.
PL- Scroll to first line of the page
PL-n Scroll n lines back
PL+ Scroll to last line of the page
PL+n Scroll n lines up
PNOP No effect
PP- Scroll back one page
PP-n Scroll n pages back
PP+ Scroll one page forward
PP+n Scroll n pages forwad
PPn Scroll to beginning of page n
PRI, PRINT Print
PS-- Scroll to first column
PS++ Scroll to last column
PS- Scroll one column to the left
PS-n Scroll n columns to the left
PS+ Scroll one column to the right
PS+n Scroll n columns to the right
PSn Scroll to column n
PZn Scroll to line n
RW Cancel

Report model - number of values selected in DDL param

Good afternoon,
I have created a report model that references Teradata views, and I am using this model to populate several datasets in a Report Builder report. One dataset returns actual results, and the other datasets are used to populate available values for multivalued
parameters.
The issue I'm encountering is that some of my parameters return a large number (tens or hundreds of thousands) of selectable values. When clicking "select all", I'm getting an error, since the concatenated list of values exceeds
the length limit. However, since I'm working with a report model, I cannot use T-SQL workarounds such as custom "<ALL>" values/handling. I also need to limit my result set using these values as parameters, not filters, since I want
the intensive processing handled in the DB server, not the app server.
Is there any possible way to accommodate this? As an example, I have a large (200k+) list of products, belonging to about 7,000 brands. I want both my product number and brand lists as multivalue parameters...I might want to run
the report for all products and all brands (returning 200k+ rows), or choose "select all" in the products list, but only pick a few brands (or vice versa). Cascading parameters (with the first parameter limiting the next set of values)
is not an option since there are many of these parameters that have too many values for the allowed limit (i.e. even my brand list generated the error when I choose "select all" and only picked a few products).
I have searched literally dozens of forums and tech sites, all to no avail thus far. Any assistance will be greatly appreciated...thank you!
-Chris

I have a SSRS Report with 4 multi-select parameters.
The customer has requested that they would like the drill-through to open in a new window.
I am using Java Script for that purpose.
However, there is a limit on how long a URL may be.
Is there a way in a SSRS report to limit the number of values in a multi-select parameter selected?
Thanks.
One workaround is to add a internal parameter which will count the number of selected values and will allow the navigation only if the count falls below the threshold.
For this you can use an expression like below for setting the internal parameter
Len(Join(Parameters!MultiValuedParameter.Value,","))-Replace(Join(Parameters!MultiValuedParameter.Value,","),",","")
Then use expression like below for the jump to url/report property
IIf(Val(Parameters!HiddenParameter.Value)<=<your thresholdvalue>,<report url>,Nothing)
You can also add a notification textbox on top which will show a message like "Report navigation not possible due to too many values selected" and keep it hidden by default. Then based on above parameter value you can make it visible
ie make hidden property like below
IIf(Val(Parameters!HiddenParameter.Value)<=<your thresholdvalue>,False,True)
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My Wiki User Page
My MSDN Page
My Personal Blog
My Facebook Page

Deadlock: select and DDL

Similar Messages

Maybe you are looking for