Is this a bug in table operator

I have an Oracle function that is invoked by the select statement as follow:
select count(*)
into i
from table(
select depts -- depts is a varray of dept_obj
from table(company_package.f_getCompany(k))
the function f_getCompany(k) gets invoked twice.
but if I change the SQL to
select depts
into dept_array
from table(company_package.f_getCompany(k));
then function f_getCompany(k) will be invoked just once.
Is this a bug within Oracle ? How can I get around that, I just want the function execute ONCE.
Any help would be appricated.
Thanks
Here are the rest of the code
create or replace type company_obj as object
company_id number,
company_name varchar2(20),
depts dept_arr
CREATE OR REPLACE
type company_arr is VARRAY(10000) of company_obj;
create or replace type dept_obj as object
dept_id number,
dept_name varchar2(30)
CREATE OR REPLACE
type dept_arr is VARRAY(10000) of dept_obj;
create or replace package company_package is
number_of_times int := 0;
function f_getCompany(company_id number) return company_arr;
end company_package;
create or replace package body company_package is
function f_getCompany(company_id number) return company_arr is
comp_array company_arr;
comp_object company_obj;
dept_array dept_arr;
dept_object dept_obj;
begin
dept_object := dept_obj(100, 'Dept 1');
dept_array := dept_arr();
dept_array.extend;
dept_array(1) := dept_object;
dept_object := dept_obj(110, 'Dept 2');
dept_array.extend;
dept_array(2) := dept_object;
comp_object := company_obj(1, 'Company A', dept_array);
comp_array := company_arr();
comp_array.extend;
comp_array(1) := comp_object;
number_of_times := number_of_times + 1;
dbms_output.put_line('number of times = ' || number_of_times);
return comp_array;
end;
end company_package;
----------------------------------------------------------------------------------------------------

I noticed that myself in our project.
Our varchars2 are defined as VARCHAR2(xxx CHAR) - OWB puts the size*4
In fact if you have special characters like umlauts (ü,ä,ö,...) it will use 4 bytes per character.
You can try it yourself. Define a Varchar2(1 CHAR) and manually change the size of the Column in your mapping inside OWB (in filters, joins or your target table).
Then shoot an umlaut through the mapping and will end up with a "too small" error.
Dont mind the size*4 issue - we totally ignored it and run without error since 4 years now.

Similar Messages

  • Is this a bug in OWB 11.2 - importing table metadata for character columns

    The Oracle® Warehouse Builder Data Modeling, ETL, and Data Quality Guide provides an overview of the data types supported.
    http://docs.oracle.com/cd/E11882_01/owb.112/e10935/orcl_data_objx.htm
    It says that for VARCHAR2 data type it saws (http://docs.oracle.com/cd/E11882_01/owb.112/e10935/orcl_data_objx.htm#CHDFIADI )
    "Stores variable-length character data. How the data is represented internally depends on the database character set. The VARCHAR2 data type takes a required parameter that specifies a maximum size up to 4,000 characters"
    That means , I guess, it says that when I import a table, any columns of type VARCHAR2(10) in the database should have its length show as characters in OWB, so a column of type Varchar2(10) in the Oracle database, should be shown as Varchar2(10) when imported into OWB table metadata via the OWB import function.
    However, if I have a database that set-up as a single-byte and import a table using the OWB import function a column that has a size of e.g. 10 in the database, is imported as OWB table metadata and the size is 10. Correct, I am happy.
    However, if the database is modified to support multi-byte characters, ALTUF16 encoding with the semantics set to "CHAR", then when I import the same table into OWB, OWB reports the size as 40, I guess its 40 bytes as in 10 characters @ 4 bytes per character.
    Is this a bug in OWB, as the datatype in the Oracle DB is varchar2(10), should OWB after importing a table not also report the column as VARCHAR2(10) ? Currently, is shows the column as varchar2(40).

    I noticed that myself in our project.
    Our varchars2 are defined as VARCHAR2(xxx CHAR) - OWB puts the size*4
    In fact if you have special characters like umlauts (ü,ä,ö,...) it will use 4 bytes per character.
    You can try it yourself. Define a Varchar2(1 CHAR) and manually change the size of the Column in your mapping inside OWB (in filters, joins or your target table).
    Then shoot an umlaut through the mapping and will end up with a "too small" error.
    Dont mind the size*4 issue - we totally ignored it and run without error since 4 years now.

  • Not able to change the name of the attribute of the Table operator.

    We are trying to create OMB scripts to automate certain tasks. As a part of this, there is a requirement to change the attribute name of table operators (which by default gets the name of the column). It is possible to change the attribute name from the GUI. But I was not able to do the same using OMB Scripting. Here is the script I used.
    OMBALTER MAPPING 'TEST' \
    MODIFY ATTRIBUTE 'GEOGRAPHY_ID' OF GROUP 'INOUTGRP1' OF OPERATOR 'TEST' \
    SET PROPERTIES(BUSINESS_NAME,PRECISION,DESCRIPTION) \
    VALUES('MEMBER_ID',2,'MEMBER')
    This script was to change the name of the attribute - GEOGRAPHY_ID of the table operator TEST.
    From what I can make out from the Scripting reference, changing BUSINESS_NAME of the attribute should do the trick but it is not happening. The syntax looks correct as the precision of the column changes.
    Am I missing something? Or is it a limitation or a bug?
    I use OWB client 10.2.0.1.25 and OWB repository 10.2.0.1.0.

    Hi!
    I'm using successfully
    OMBALTER MAPPING '$mapName' MODIFY ATTRIBUTE '$attrName' OF GROUP '$groupName' OF OPERATOR '$joinName' RENAME TO '$newName'
    Regards,
    Carsten.

  • Partition name length problem at DML in Table operator

    Hello experts
    In our datawarehouse we have a table with a high number of partitions (each partition corresponding to a different business object) for solving an issue with data quality. Every time the data quality mapping is run, a truncate on the corresponding partition is performed. But Insert operations on that table are not set on a particular partition and, therefore, lock the table and have a conflict with the truncates if parallel operations are run.
    We would like to used the Partition DML functionality at the Table Operator in order to insert just into one partition and prevent locking all of them. Although none of the partition names are longer than 30 characters, OWB (even at the GUI) adds the string "partition: " in front of each name, which causes the length limit to be surpassed.
    Any idea about how could we use this functionality without renaming the partitions?

    Hey there,
    I'm a colleague of the thread starter and like to jump in as this is an issue for us which we need to solve.
    Some more infos which might help:
    We are running the OWB 11.2.0.3.0 on Windows 32 Bit
    We have the following patches installed:
    13257502
    13473205
    None of the later patches has been installed, since none of the Bugs that were fixed affected us.
    In a Mapping on a table-Operator we'd like to use "PARTITION DML" for an Insert.
    On the GUI when selecting the Partition the data should be inserted to (Field: DML Partiton Name), we get the following error (in this instance the partition name is 24 characters long)
    "API0407: The minimum length of this filed is 0 and its maximum length is 32. You have 35 characters."
    In the Drop-down Menu of DML Partition Name it says "Partition: " in front of every partition there is. Together with a Partition name of 24 Characters it sums up to 35 characters.
    So it appears that the maximum length of the partition is limited to 21 characters only because "Partition: " is put in front of it.
    This error also appears when editing the Properties of the table operator by OMB*PLUS (from tcl) with
    OMBALTER MAPPING 'mapname' MODIFY OPERATOR 'operatorname' SET PROPERTIES (DML_PARTITION_NAME, DML_PARTITION_TYPE, PARTITION_KEY_VALUE_LIST, IS_PARTITION_INDEXED_BY_NAME) VALUES ('$partition', 'PARTITION', '$someEmptyList', 'true')
    where it does not make a difference whether $partition is of the form
    set partition "Partition: SOMEPARTITIONNAME"
    or
    set partition "SOMEPARTITIONNAME"
    Renaming the Partitions is not an option for us, since our warehouse is running in multiple productive systems and became quite large in the last years.
    Is it necessary, that "Partition: " is put infront of the partition name? Is there a way around this? Isn't the field DML_PARTITION_TYPE supposed to store the Information whether it is a partion or a subpartition?
    If you wanted to use subpartitions, does the name of the subpartition then need to be even shorter since "Subpartiton: " is put infront?
    Thanks in advance for any help or suggestions. If you need further Information, feel free to ask, I am more than happy to supply it.
    Best Regards
    Thorsten

  • WCF-SQL table operation on tables with the same name.

    Hello,
    My situation involves generating table operation schemas (Insert, Update, Delete, Select) for tables in two different SQL databases.  These tables happen to have the same name.  For the sake of discussion lets call the tables dbo.Customer.  However,
    these tables have different fields in them.  When generating the schemas to be used by BizTalk, they end up as the same message type like so:
    Database1: http://schemas.microsoft.com/Sql/2008/05/TableOp/dbo/Customer#Update
    Database2: http://schemas.microsoft.com/Sql/2008/05/TableOp/dbo/Customer#Update
    To my understanding, I can't simply change the namespaces or root nodes to be unique since this structure is expected by the SQL Adapter (shown here: https://msdn.microsoft.com/en-us/library/dd788023.aspx).  I had a couple thoughts on a solution: 
    Use schema versions to differentiate between the two different table schemas.
    Use a unique namespace and root node for the schemas.  Then, create a custom pipeline component to modify them to the standard as it is sent to SQL server.
    Modify the schema so support both tables with all columns in both tables.
    I don't really like any of these solutions, so I am hoping somebody in the community has run into this situation before and has something better.
    -Richard

    You don't really have to do anything other than make sure the particular message gets routed always to the correct database.
    Having duplicate MessageType's is only a problem if you're relying on the automatic resolution of the XmlDisassembler and that would only be a concern on the Response side.
    To get around that, just create a custom Pipeline with the XmlDisassembler and set the Document Schemas list to only the one for that Port.

  • Is this a "bug" on this group by matrix report?

    Is this a bug in Reports (10g Release2)?
    We need to create a report which will display country and gender wise arrival totals for every flight but Arrival method wise (i.e. grouped by arrival method), with grand totals for the flight number (i.e. total people in the flight).
    The output comes out correct only if 1 group (i.e. Arrival method ) is selected. But when all arrival methods are shown, we get this wrong output.
    TABLE + DATA
    --  DDL + data for Table KR_TABLE1
      CREATE TABLE "KR_TABLE1"
       (     "PK" NUMBER PRIMARY KEY,
         "ARRIVAL_METHOD" VARCHAR2(10 BYTE),
         "COUNTRY_CODE" VARCHAR2(2 BYTE),
         "COUNTRY_NAME" VARCHAR2(10 BYTE),
         "ARRIVAL_GENDER" VARCHAR2(1 BYTE),
         "FLIGHT_NUMBER" VARCHAR2(10 BYTE),
         "FLIGHT_DATE" DATE,
         "COUNT1" NUMBER
    REM INSERTING into KR_TABLE1
    SET DEFINE OFF;
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (1,'Swipe','In','India','M','UL 123',to_date('01-APR-13','DD-MON-RR'),5);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (2,'Swipe','In','India','F','UL 123',to_date('01-APR-13','DD-MON-RR'),6);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (3,'Swipe','In','India','C','UL 123',to_date('01-APR-13','DD-MON-RR'),2);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (6,'Swipe','Cn','China','M','UL 123',to_date('01-APR-13','DD-MON-RR'),123);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (7,'Swipe','Cn','China','C','UL 123',to_date('01-APR-13','DD-MON-RR'),73);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (11,'Swipe','In','India','M','AB 546',to_date('02-APR-13','DD-MON-RR'),15);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (12,'Swipe','In','India','F','AB 546',to_date('02-APR-13','DD-MON-RR'),16);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (13,'Swipe','In','India','C','AB 546',to_date('02-APR-13','DD-MON-RR'),12);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (16,'Swipe','Cn','China','M','AB 546',to_date('02-APR-13','DD-MON-RR'),133);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (17,'Swipe','Cn','China','C','AB 546',to_date('02-APR-13','DD-MON-RR'),83);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (21,'Swipe','In','India','M','cx 956',to_date('03-APR-13','DD-MON-RR'),26);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (22,'Swipe','In','India','F','cx 956',to_date('03-APR-13','DD-MON-RR'),27);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (23,'Swipe','In','India','C','cx 956',to_date('03-APR-13','DD-MON-RR'),23);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (26,'Swipe','Cn','China','M','cx 956',to_date('03-APR-13','DD-MON-RR'),144);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (27,'Swipe','Cn','China','C','cx 956',to_date('03-APR-13','DD-MON-RR'),94);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (31,'Swipe','In','India','M','QL1234',to_date('04-APR-13','DD-MON-RR'),36);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (32,'Swipe','In','India','F','QL1234',to_date('04-APR-13','DD-MON-RR'),37);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (33,'Swipe','In','India','C','QL1234',to_date('04-APR-13','DD-MON-RR'),33);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (36,'Swipe','Cn','China','M','QL1234',to_date('04-APR-13','DD-MON-RR'),154);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (37,'Swipe','Cn','China','C','QL1234',to_date('04-APR-13','DD-MON-RR'),104);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (41,'Swipe','In','India','M','BF 176',to_date('05-APR-13','DD-MON-RR'),46);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (42,'Swipe','In','India','F','BF 176',to_date('05-APR-13','DD-MON-RR'),47);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (43,'Swipe','In','India','C','BF 176',to_date('05-APR-13','DD-MON-RR'),43);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (46,'Swipe','Cn','China','M','BF 176',to_date('05-APR-13','DD-MON-RR'),164);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (47,'Swipe','Cn','China','C','BF 176',to_date('05-APR-13','DD-MON-RR'),114);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (51,'Swipe','In','India','M','JR 671',to_date('06-APR-13','DD-MON-RR'),56);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (52,'Swipe','In','India','F','JR 671',to_date('06-APR-13','DD-MON-RR'),57);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (53,'Swipe','In','India','C','JR 671',to_date('06-APR-13','DD-MON-RR'),53);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (56,'Swipe','Cn','China','M','JR 671',to_date('06-APR-13','DD-MON-RR'),174);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (57,'Swipe','Cn','China','C','JR 671',to_date('06-APR-13','DD-MON-RR'),124);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (61,'Swipe','In','India','M','M3 999',to_date('07-APR-13','DD-MON-RR'),66);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (62,'Swipe','In','India','F','M3 999',to_date('07-APR-13','DD-MON-RR'),67);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (63,'Swipe','In','India','C','M3 999',to_date('07-APR-13','DD-MON-RR'),63);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (66,'Swipe','Cn','China','M','M3 999',to_date('07-APR-13','DD-MON-RR'),184);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (67,'Swipe','Cn','China','C','M3 999',to_date('07-APR-13','DD-MON-RR'),134);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (71,'Swipe','In','India','M','V3 111',to_date('18-APR-13','DD-MON-RR'),76);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (72,'Swipe','In','India','F','V3 111',to_date('18-APR-13','DD-MON-RR'),77);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (73,'Swipe','In','India','C','V3 111',to_date('18-APR-13','DD-MON-RR'),73);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (76,'Swipe','Cn','China','M','V3 111',to_date('18-APR-13','DD-MON-RR'),194);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (77,'Swipe','Cn','China','C','V3 111',to_date('18-APR-13','DD-MON-RR'),144);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (161,'Manual','In','India','M','UL 123',to_date('01-APR-13','DD-MON-RR'),4);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (162,'Manual','In','India','F','UL 123',to_date('01-APR-13','DD-MON-RR'),5);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (163,'Manual','In','India','C','UL 123',to_date('01-APR-13','DD-MON-RR'),1);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (164,'Manual','Pk','Pakistan','M','UL 123',to_date('01-APR-13','DD-MON-RR'),12);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (165,'Manual','Pk','Pakistan','F','UL 123',to_date('01-APR-13','DD-MON-RR'),6);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (166,'Manual','Cn','China','M','UL 123',to_date('01-APR-13','DD-MON-RR'),122);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (167,'Manual','Cn','China','C','UL 123',to_date('01-APR-13','DD-MON-RR'),72);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (168,'Manual','US','America','M','UL 123',to_date('01-APR-13','DD-MON-RR'),7);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (169,'Manual','US','America','F','UL 123',to_date('01-APR-13','DD-MON-RR'),0);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (170,'Manual','US','America','C','UL 123',to_date('01-APR-13','DD-MON-RR'),2);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (171,'Manual','In','India','M','AB 546',to_date('02-APR-13','DD-MON-RR'),14);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (172,'Manual','In','India','F','AB 546',to_date('02-APR-13','DD-MON-RR'),15);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (173,'Manual','In','India','C','AB 546',to_date('02-APR-13','DD-MON-RR'),11);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (174,'Manual','Pk','Pakistan','M','AB 546',to_date('02-APR-13','DD-MON-RR'),22);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (175,'Manual','Pk','Pakistan','F','AB 546',to_date('02-APR-13','DD-MON-RR'),16);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (176,'Manual','Cn','China','M','AB 546',to_date('02-APR-13','DD-MON-RR'),132);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (177,'Manual','Cn','China','C','AB 546',to_date('02-APR-13','DD-MON-RR'),82);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (178,'Manual','US','America','M','AB 546',to_date('02-APR-13','DD-MON-RR'),17);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (179,'Manual','US','America','F','AB 546',to_date('02-APR-13','DD-MON-RR'),10);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (180,'Manual','US','America','C','AB 546',to_date('02-APR-13','DD-MON-RR'),12);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (181,'Manual','In','India','M','cx 956',to_date('03-APR-13','DD-MON-RR'),25);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (182,'Manual','In','India','F','cx 956',to_date('03-APR-13','DD-MON-RR'),26);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (183,'Manual','In','India','C','cx 956',to_date('03-APR-13','DD-MON-RR'),22);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (184,'Manual','Pk','Pakistan','M','cx 956',to_date('03-APR-13','DD-MON-RR'),33);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (185,'Manual','Pk','Pakistan','F','cx 956',to_date('03-APR-13','DD-MON-RR'),27);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (186,'Manual','Cn','China','M','cx 956',to_date('03-APR-13','DD-MON-RR'),143);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (187,'Manual','Cn','China','C','cx 956',to_date('03-APR-13','DD-MON-RR'),93);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (188,'Manual','US','America','M','cx 956',to_date('03-APR-13','DD-MON-RR'),28);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (189,'Manual','US','America','F','cx 956',to_date('03-APR-13','DD-MON-RR'),21);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (190,'Manual','US','America','C','cx 956',to_date('03-APR-13','DD-MON-RR'),23);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (191,'Manual','In','India','M','QL1234',to_date('04-APR-13','DD-MON-RR'),35);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (192,'Manual','In','India','F','QL1234',to_date('04-APR-13','DD-MON-RR'),36);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (193,'Manual','In','India','C','QL1234',to_date('04-APR-13','DD-MON-RR'),32);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (194,'Manual','Pk','Pakistan','M','QL1234',to_date('04-APR-13','DD-MON-RR'),43);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (195,'Manual','Pk','Pakistan','F','QL1234',to_date('04-APR-13','DD-MON-RR'),37);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (196,'Manual','Cn','China','M','QL1234',to_date('04-APR-13','DD-MON-RR'),153);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (197,'Manual','Cn','China','C','QL1234',to_date('04-APR-13','DD-MON-RR'),103);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (198,'Manual','US','America','M','QL1234',to_date('04-APR-13','DD-MON-RR'),38);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (199,'Manual','US','America','F','QL1234',to_date('04-APR-13','DD-MON-RR'),31);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (200,'Manual','US','America','C','QL1234',to_date('04-APR-13','DD-MON-RR'),33);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (201,'Manual','In','India','M','BF 176',to_date('05-APR-13','DD-MON-RR'),45);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (202,'Manual','In','India','F','BF 176',to_date('05-APR-13','DD-MON-RR'),46);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (203,'Manual','In','India','C','BF 176',to_date('05-APR-13','DD-MON-RR'),42);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (204,'Manual','Pk','Pakistan','M','BF 176',to_date('05-APR-13','DD-MON-RR'),53);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (205,'Manual','Pk','Pakistan','F','BF 176',to_date('05-APR-13','DD-MON-RR'),47);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (206,'Manual','Cn','China','M','BF 176',to_date('05-APR-13','DD-MON-RR'),163);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (207,'Manual','Cn','China','C','BF 176',to_date('05-APR-13','DD-MON-RR'),113);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (208,'Manual','US','America','M','BF 176',to_date('05-APR-13','DD-MON-RR'),48);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (209,'Manual','US','America','F','BF 176',to_date('05-APR-13','DD-MON-RR'),41);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (210,'Manual','US','America','C','BF 176',to_date('05-APR-13','DD-MON-RR'),43);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (211,'Manual','In','India','M','JR 671',to_date('06-APR-13','DD-MON-RR'),55);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (212,'Manual','In','India','F','JR 671',to_date('06-APR-13','DD-MON-RR'),56);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (213,'Manual','In','India','C','JR 671',to_date('06-APR-13','DD-MON-RR'),52);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (214,'Manual','Pk','Pakistan','M','JR 671',to_date('06-APR-13','DD-MON-RR'),63);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (215,'Manual','Pk','Pakistan','F','JR 671',to_date('06-APR-13','DD-MON-RR'),57);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (216,'Manual','Cn','China','M','JR 671',to_date('06-APR-13','DD-MON-RR'),173);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (217,'Manual','Cn','China','C','JR 671',to_date('06-APR-13','DD-MON-RR'),123);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (218,'Manual','US','America','M','JR 671',to_date('06-APR-13','DD-MON-RR'),58);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (219,'Manual','US','America','F','JR 671',to_date('06-APR-13','DD-MON-RR'),51);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (220,'Manual','US','America','C','JR 671',to_date('06-APR-13','DD-MON-RR'),53);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (221,'Manual','In','India','M','M3 999',to_date('07-APR-13','DD-MON-RR'),65);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (222,'Manual','In','India','F','M3 999',to_date('07-APR-13','DD-MON-RR'),66);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (223,'Manual','In','India','C','M3 999',to_date('07-APR-13','DD-MON-RR'),62);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (224,'Manual','Pk','Pakistan','M','M3 999',to_date('07-APR-13','DD-MON-RR'),73);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (225,'Manual','Pk','Pakistan','F','M3 999',to_date('07-APR-13','DD-MON-RR'),67);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (226,'Manual','Cn','China','M','M3 999',to_date('07-APR-13','DD-MON-RR'),183);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (227,'Manual','Cn','China','C','M3 999',to_date('07-APR-13','DD-MON-RR'),133);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (228,'Manual','US','America','M','M3 999',to_date('07-APR-13','DD-MON-RR'),68);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (229,'Manual','US','America','F','M3 999',to_date('07-APR-13','DD-MON-RR'),61);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (230,'Manual','US','America','C','M3 999',to_date('07-APR-13','DD-MON-RR'),63);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (231,'Manual','In','India','M','V3 111',to_date('18-APR-13','DD-MON-RR'),75);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (232,'Manual','In','India','F','V3 111',to_date('18-APR-13','DD-MON-RR'),76);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (233,'Manual','In','India','C','V3 111',to_date('18-APR-13','DD-MON-RR'),72);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (234,'Manual','Pk','Pakistan','M','V3 111',to_date('18-APR-13','DD-MON-RR'),83);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (235,'Manual','Pk','Pakistan','F','V3 111',to_date('18-APR-13','DD-MON-RR'),77);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (236,'Manual','Cn','China','M','V3 111',to_date('18-APR-13','DD-MON-RR'),193);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (237,'Manual','Cn','China','C','V3 111',to_date('18-APR-13','DD-MON-RR'),143);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (238,'Manual','US','America','M','V3 111',to_date('18-APR-13','DD-MON-RR'),78);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (239,'Manual','US','America','F','V3 111',to_date('18-APR-13','DD-MON-RR'),71);
    Insert into KR_TABLE1 (PK,ARRIVAL_METHOD,COUNTRY_CODE,COUNTRY_NAME,ARRIVAL_GENDER,FLIGHT_NUMBER,FLIGHT_DATE,COUNT1) values (240,'Manual','US','America','C','V3 111',to_date('18-APR-13','DD-MON-RR'),73);
    CREATE SEQUENCE kr_table_seq START WITH 1
    CREATE OR REPLACE TRIGGER "kr_table1_PK_GEN_TRIG"
       before insert on "KR_TABLE1"
       for each row
    begin 
       if inserting then
          if :NEW."PK" is null then
             select kr_table_seq.nextval into :NEW."PK" from dual;
          end if;
       end if;
    end;
    /REPORT QUERY
    SELECT arrival_method,
    country_code, country_name, arrival_gender,
    flight_number , flight_date, SUM(count1) sum_count1
    FROM kr_table1
    GROUP BY arrival_method, country_code, country_name, arrival_gender, flight_number , flight_date
    ORDER BY arrival_method,country_code, country_name, arrival_gender,flight_number , flight_dateReport data model (created using reports wizard and not manually):
    http://www.freeimagehosting.net/newuploads/6alll.jpg
    Erroneous report output:
    http://www.freeimagehosting.net/newuploads/2gx4a.jpg
    Edited by: 957072 on Apr 23, 2013 3:51 AM
    Edited by: 957072 on Apr 23, 2013 3:52 AM

    You can set the Default Type before you send the message under SENDING options to TEXT (default is automatic)
    But then all it does it will not send the message if more than 20 recipients are there it will tell you how many recipients over 20 you have entered.
    Say you have a group of 26 contacts and then you enter that and then select Options -> Sending options -> Message Type
    Set to TEXT
    Then if you try to send it will tell you that you have to remove 6 recipients.
    640K Should be enough for everybody
    El_Loco Nokia Video Blog

  • Is this a bug or a simple Newbie mistake?

    Hi.
    I'm brand new to JavaFX, so I'm probably misunderstanding something. I've searched the web looking for information concerning it, but since it involves the 'new' operator, it's hard to filter down.
    Anyhow, here is the problem:
    I'm getting different results when I instantiate an object
    using the 'new' operator vs. the declaring it the more
    accepted JavaFX way.
    This is how I found the "problem".
    In order to learn how to program in JavaFX, I found a simple game from the Internet, "Blasteroids", to look at (http://www.remwebdevelopment.com/dev/a41/Programming-Games-in-JavaFX-Part-1.html). I copied and pasted this into:
    NetBeans IDE 6.9 (Build 201006101454)
    JavaFX 1.3 and got the game to work.
    In playing around with it, I converted instantiating an object from the "normal" way:
        var a: Asteroid = Asteroid
            type: type
            posX: x
            posY: y
            moveAngle: moveAngle
            velocityX: Math.sin(Math.toRadians(moveAngle))
                * randomVelocity
            velocityY: -Math.cos(Math.toRadians(moveAngle))
                * randomVelocity
            rotation_increment: rotation_increment
            active: true;
            return a;To using the "new" operator:
            var a:Asteroid = new Asteroid();
            a.type = type;
            a.posX = x;
            a.posY = y;
            a.moveAngle = moveAngle;
            a.velocityX = Math.sin(Math.toRadians(moveAngle)) * randomVelocity;
            a.velocityY = -Math.cos(Math.toRadians(moveAngle))* randomVelocity;
            a.rotation_increment = rotation_increment;
            a.active = true;
            return a;This is the only changes I made. I would "toggle" back and forth between the two, and I would always get the same results.
    When I did this conversion, the ship would show up, but the asteroids were gone. Actually, I think they were invisible because every once and a while, my ship would "blow up" and get reset to it's starting position. I tried adding:
    a.visible = true;
    But that didn't help.
    Indecently, I did the same thing with defining the "Stage" using a new operator, and got differing results:
    1. the window would open in the bottom right of my screen (vs filling up
    most of my screen. I would have to drag it up to play.
    2. it had a regular windows border with the minimize, maximize, close
    buttons in the top right (vs. a non-movable, border less window with no
    maximize, minimize, close buttons.)
    Is this a bug, or am I doing something wrong?
    Thank you

    I suspect you've run into bugs in the Blasteroids program and possibly in Stage in the JavaFX runtime.
    For simple cases one would think there should be no difference between this:
    var so = SomeObject {
        a: 1
        b: 2
        c: 3
    }and this:
    var so = SomeObject { }; // or var so = new SomeObject();
    so.a = 1;
    so.b = 2;
    so.c = 3;However, these cases do run through different code paths. In the first case, the init-block of SomeObject sees all the values provided by the caller. In the second case, the triggers on the a, b, and c variables would have to modify the internal state of the object appropriately. If the object has a lot of complex state, the result at the end of setting the three variables (and running their triggers) might not be identical to the object literal after initialization. This is most likely a bug. If an object isn't prepared to have its state variables modified after initialization, it should make them public-init instead of public.
    Depending on the object, though, initializing things via an object literal vs. setting variables after initialization might actually have different semantics. This seems to be the case with Stage. The Stage's size is established by its contents at initialization time, and its location at initialization time is determined by using its contents' size and the screen size to center the Stage on the screen. If you create the Stage empty, and then later add contents, the sizing/centering calculations will be based on an empty Stage and will thus give a different result.
    Using the object literal technique is idiomatic JavaFX Script, and it's probably more efficient than setting variables after initialization, so I'd recommend sticking with object literals.

  • Is this a bug in Jdeveloper 11g (11.1.2.1.0)

    Hello,
    I am using Jdeveloper 11g (11.1.2.1.0). I am using employee table. In my EO for HIREDATE attribute, I am choosing default value radio button SQL; entered valid SQL statement (Ex. Select Sysdate from dual). As soon as I save, the HIREDATE column becoming Transient. It is not allowing the attribute to Persistent. Is this a Bug.
    Thanks
    Edited by: Surendranath Kumar on Apr 18, 2012 10:27 AM
    Edited by: Surendranath Kumar on Apr 20, 2012 12:44 PM

    It is confirmed as bug. See link Bug in Jdeveloper 11g (11.1.2.1.0)

  • Is this a bug in APEX or I'm missing something

    Hi,
    I have a table chr10bug( id number , sample_text varchar2(4000)).
    I am using simple form with textarea to populate sample_text.
    I have a report based on above table.
    The report query is select id , sample_text from chr10bug. The Link tab has Target as URL. URL is javascript:void(0); and Link attribute has a very simple function
    onmouseover="alter('#SAMPLE_TEXT#')"
    Now, my question is when a user hits enter in the textarea eg.
    User enter some text **User Press Enter**
    User enter some text again
    In the reports the onmouseover="alert('#SAMPLE_TEXT#')" does not work for recrod where users pressed enter key. (In fact none of the function which accept string is working) . If we do not press enter while entering data in textarea... the above function is working...
    Example is here....
    http://apex.oracle.com/pls/apex/f?p=32555:1 ( report)
    http://apex.oracle.com/pls/apex/f?p=32555:2 ( form to enter data via text area)
    Is this a bug...
    Regards,
    Shijesh
    Edited by: Apex_Noob on Nov 18, 2010 12:18 PM

    Hi,
    Thanks once again for reply.
    I create two report with same javascript function alert('#sample_text#')
    CASE1 >> Javascript function call is placed in Link attribute section as ** onmouseover="alert('#sample_text#')" >>> This is not working
    CASE2 >> Javascript function call is place in URL section as ** javascript:alert('#sample_text#') >>>> This is working however I'm not able to have onmouseover feature.
    Any alternative to have onmouseover=myFunction('#COLUMN_NAME#').
    http://apex.oracle.com/pls/apex/f?p=32555:1:8742069995710311:::::
    thanks,
    Shijesh
    Edited by: Apex_Noob on Nov 18, 2010 12:45 PM

  • Is this a bug in CF 8

    I have the following code (just as a sample):
    <CFQUERY NAME="MyProjects" DATASOURCE="DSN_Name">
    select PID, PName from projects
    </CFQUERY>
    Assume the above query will bring only one record, I'm using
    CF 8 with latest hot fix, running on windows server 2003 machine,
    with MSSQL 2005.
    Now if I try simply just to print this PID (PID is a primary
    key set by the table) as below:
    <cfoutput>
    <cfloop query="MyProjects">
    #PID#
    </cfloop>
    <cfoutput>
    Now to run the above code in a stress test with 10 concurrent
    users, this PID could bring NULL, while if I write it this way with
    same type of test it doesn't break and it doesn't bring NULL
    <cfoutput>
    <cfloop query="MyProjects">
    #MyProjects.PID#
    </cfloop>
    <cfoutput>
    Is this a bug in CF or maybe the JDBC drivers ? Is it scoping
    issue ? ... anyone notice this before ?.

    Qais wrote:
    > Thanks for your reply, I know I can do it as
    <cfoutput query= ......> but I
    > have a friend which told me that if you don't scope a
    column name by the name
    > of the query, like query_name.column_name and this
    column name just by chance
    > exists as a variable in another scope (like session or
    application or ...etc.)
    > and with a stress test it could jump and read that other
    value in the other
    > scope.
    >
    > My understanding for CF since before until today that
    when you print a query
    > like
    > <cfoutput query= ......>
    > #column_name#
    > </cfoutput>
    > then CF will look into ONLY that recordset and will not
    go further and make a
    > search into other scopes.
    If there is someone here in this forum from Adobe
    > can I get a clear answer if this SHOULD scoped or
    not.
    >
    Yes, scoping is considered a best practice. Inside an
    <cfoutput...>
    block, ColdFusion will look in the named query *first*, but
    it does not
    stop there. If the value is not found in the query, then it
    will look
    into other scopes in a defined and documented order.
    Outside of an <cfoutput...>, i.e., in your first
    example with a
    <cfloop...> I suspect the query is not the first scope
    looked into.
    http://www.adobe.com/devnet/server_archive/articles/using_cf_variables2.html#scopes
    http://www.chapter31.com/2008/03/28/evaluating-coldfusion-unscoped-query-variables/
    http://www.oreillynet.com/pub/a/oreilly/web/news/coldfusion_0701.html
    Not exactly a hidden secret here.

  • Is this a bug in Safari for iOS ??

    http://www.clfsrpm.net/sample/
    The control buttons above playlist display just fine in every Android, Linux, and Windows browser I have used - including Safari for Windows.
    However they do not display properly in Safari for iOS as tested on my iPod (but they do display correctly in Opera Mini for iPod)
    Is this a bug in Safari for iOS ??

    Why was this moved to "Using iPhone" ??
    It is a question about Safari for iOS - not iPhone/iPod usage.

  • Is this a bug in Java!

    int i=0;
    i=i++;
    System.out.println(i);
    What should this code print.
    I guess 1.
    But it prints 0.
    Can anyone explain the logic behind this, or is this a bug in Java.
    Thanks for your time in advance.

    What did the mackerel do to deserve that?it wrote Sun's search function !!!!!! :pPlease, a mackerel would of done a better job.
    All I can say is "JTable project", smiles.
    (Gah, Please kill me)mlk BANG BANG*
    *Post decease operator.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

  • IMPORT_TABLE_STATS - Is this a Bug in 9i ?

    Oracle Database 9.2.0.1.0 on REHL 8.0
    exec DBMS_STATS.import_table_stats ('scott', 'ABC_XYZ', stattab =>'savestats' );The above statement executed successfully without any error.
    The funny part is that there is no table with name 'ABC_XYZ' in SCOTT schema.
    Whereas,
    the same statement gives an error ORA-06512 on Oracle Database 10.2.0.1.0
    Is this a bug in 9i ?

    Hi,
    I tried in 9.2.0.5 and it returned me an error same like you got
    Tintin:/home/oracle>sqlplus '/ as sysdba'
    SQL*Plus: Release 9.2.0.5.0 - Production on Thu Dec 6 17:44:37 2007
    Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
    Connected to:
    Oracle9i Enterprise Edition Release 9.2.0.5.0 - 64bit Production
    With the Partitioning option
    JServer Release 9.2.0.5.0 - Production
    sys@DBVDASM>exec DBMS_STATS.import_table_stats ('scott', 'ABC_XYZ', stattab =>'savestats' );
    BEGIN DBMS_STATS.import_table_stats ('scott', 'ABC_XYZ', stattab =>'savestats' ); END;
    ERROR at line 1:
    ORA-06512: at "SYS.DBMS_STATS", line 4805
    ORA-06512: at "SYS.DBMS_STATS", line 5435
    ORA-06512: at line 1
    cheers

  • Is this a Bug or Feature?

    I would not expect this to work at all, but it does:
    CREATE TABLE WDD.TABLE_1
    ID_1 NUMBER NOT NULL
    CREATE TABLE WDD.TABLE_2
    ID_2 NUMBER NOT NULL
    SELECT
    TAB.ID_1,
    TAB.ID_2
    FROM
    TABLE_1 TAB,
    TABLE_2 TAB
    WHERE
    TAB.ID_1 = TAB.ID_2
    I guess that it works because the column names in each table are different. Even so, I would have thought that using the same alias name twice in the same query would have caused an error.
    So, is it supposed to work this way, or is this a bug?

    It's a wonderfull SQL feature (of which there are many)...

  • Table Operator In PL/SQL

    Sir,
    This is srinivas from India
    Recently I started working with Objects in Pl/SQL
    I am facing problem with table operator in pl/sql
    my Query is
    Select s.rollno,s.Name,column_value from student s,table(marks)
    above query working fine in at SQL Prompt
    but the same thing if I am trying to use at Cursors in PL/SQL it is giving error
    please suggest me how to use Table operator in PL/SQL
    student
    srinivas

    I suggest you post your problem to the Products->Database->SQL/PLSQL discussion Forum.
    This Forum is meant for the Apple Macintosh OS.

Maybe you are looking for