Limitations in Oracle XE with respect to SQL

Hi to all,
Is there are any limitations in SQL Queries in Oracle XE?
Because I am running a SQL query in Oracle Standard Edition which is returing results whereas I am not able to run the same query against the Oracle XE with the same table structure and same data.
In Oracle XE it is throwing the error as ERROR at line 31:
ORA-00904: "EMP"."EMPLOYEE_CODE": invalid identifier
My query is
SELECT "EMP"."EMPLOYEE_CODE",
"EMP"."NAME",
"EMP"."BIRTH_DATE",
"EMP"."FH_NAME",
"EMP"."JOINING_DATE",
"EMP"."DESIGNATION",
"EMP"."PAN_NO",
"DEPT"."DESCRIPTION",
"EMP"."DIVISION_CODE",
"DIV"."DESCRIPTION",
"LOC"."DESCRIPTION",
"EMP"."PF_NO",
"EMP"."ESI_NO",
"EMP"."CURRENT_STATUS",
"L"."CL_BALANCE",
"L"."EL_BALANCE",
"L"."ML_BALANCE" ,
"A"."ATTENDED_DAYS",
"A"."PUBLIC_HOLIDAYS",
"A"."WEEKLY_HOLIDAYS",
(SELECT SUM(CASE WHEN "LEAVE"."LEAVE_CODE"='CL' THEN "LEAVE"."LEAVE_DAYS" END ) CASUAL_LEAVE FROM LEAVE WHERE PERIOD=88 AND EMPLOYEE_CODE=EMP.EMPLOYEE_CODE) AS CASUAL_LEAVE,
(SELECT SUM(CASE WHEN "LEAVE"."LEAVE_CODE"='EL' THEN "LEAVE"."LEAVE_DAYS" END) EARNED_LEAVE FROM LEAVE WHERE PERIOD=88 AND EMPLOYEE_CODE=EMP.EMPLOYEE_CODE) AS EARNED_LEAVE,
"SICK_LEAVE",
"ON_DUTY",
"ESI_LEAVE",
(SELECT SUM(CASE WHEN "LEAVE"."LEAVE_CODE"='LP' THEN "LEAVE"."LEAVE_DAYS" END) LOSS_OF_PAY_DAYS FROM LEAVE WHERE PERIOD=88 AND EMPLOYEE_CODE=EMP.EMPLOYEE_CODE) AS LOSS_OF_PAY_DAYS,
"PAID_DAYS", "DIV"."ADDRESS2"||' '||"DIV"."ADDRESS3" AS ADDRESS,
(SELECT SUM(AMOUNT) FROM(
SELECT A.EMPLOYEE_CODE, SUM(A.AMOUNT) AS AMOUNT FROM PAYROLL A, PAY_ELEMENT B
WHERE A.PAY_ELEMENT_CODE=B.PAY_ELEMENT_CODE AND
A.PERIOD= 88 AND A.EMPLOYEE_CODE=EMP.EMPLOYEE_CODE AND B.PAY_ELEMENT_TYPE='E'
AND B.PAY_ELEMENT_CODE NOT IN('FC')
GROUP BY A.EMPLOYEE_CODE
UNION
SELECT A.EMPLOYEE_CODE, AMOUNT FROM FOOD_COUPON A, PAY_ELEMENT B
WHERE EMPLOYEE_CODE=EMP.EMPLOYEE_CODE
AND B.PAY_ELEMENT_CODE=A.PAY_ELEMENT_CODE
AND B.PAY_ELEMENT_TYPE='E'
AND PERIOD=88)D
WHERE EMPLOYEE_CODE=EMP.EMPLOYEE_CODE) AS EARNINGS,
(SELECT SUM(AMOUNT) FROM(
SELECT A.EMPLOYEE_CODE, SUM(A.AMOUNT) AS AMOUNT FROM PAYROLL A, PAY_ELEMENT B
WHERE A.PAY_ELEMENT_CODE=B.PAY_ELEMENT_CODE AND
A.PERIOD= 88 AND A.EMPLOYEE_CODE=EMP.EMPLOYEE_CODE AND B.PAY_ELEMENT_TYPE='D'
AND B.PAY_ELEMENT_CODE NOT IN('FCD')
GROUP BY A.EMPLOYEE_CODE
UNION
SELECT A.EMPLOYEE_CODE, AMOUNT FROM FOOD_COUPON A, PAY_ELEMENT B
WHERE EMPLOYEE_CODE=EMP.EMPLOYEE_CODE
AND B.PAY_ELEMENT_CODE=A.PAY_ELEMENT_CODE
AND B.PAY_ELEMENT_TYPE='D'
AND PERIOD=88)D
WHERE EMPLOYEE_CODE=EMP.EMPLOYEE_CODE) AS DEDUCTIONS,
NVL((SELECT AMOUNT FROM PAY WHERE PAY_ELEMENT_CODE='BSC' AND EMPLOYEE_CODE=EMP.EMPLOYEE_CODE),0)AS BASIC,
NVL((SELECT AMOUNT FROM PAY WHERE PAY_ELEMENT_CODE='HRA' AND EMPLOYEE_CODE=EMP.EMPLOYEE_CODE),0)AS HRA,
NVL((SELECT AMOUNT FROM PAY WHERE PAY_ELEMENT_CODE='SP2' AND EMPLOYEE_CODE=EMP.EMPLOYEE_CODE),0)AS SPECIALPAY2,
NVL((SELECT NVL(AMOUNT,0) FROM PAY WHERE PAY_ELEMENT_CODE='OA' AND EMPLOYEE_CODE=EMP.EMPLOYEE_CODE),0)AS OTHERALLOW,
NVL((SELECT AMOUNT FROM PAY WHERE PAY_ELEMENT_CODE='TA' AND EMPLOYEE_CODE=EMP.EMPLOYEE_CODE),0)AS TRANSALLOW,
NVL((SELECT AMOUNT FROM PAY WHERE PAY_ELEMENT_CODE='FC' AND EMPLOYEE_CODE=EMP.EMPLOYEE_CODE),0)AS FOODCOUPONS
FROM "EMPLOYEE" "EMP",
"DEPARTMENT" "DEPT",
"DIVISION" "DIV",
"LOCATION" "LOC",
"LEAVE_BALANCE" "L",
"PAYROLL" ,
"ATTENDANCE" "A"
WHERE ( "EMP"."DEPARTMENT_CODE" = "DEPT"."DEPARTMENT_CODE" ) and
( "EMP"."DIVISION_CODE" = "DEPT"."DIVISION_CODE" ) and
( "EMP"."DIVISION_CODE" = "DIV"."DIVISION_CODE" ) and
( "EMP"."LOCATION_CODE" = "LOC"."LOCATION_CODE" ) and
( "EMP"."EMPLOYEE_CODE" = "L"."EMPLOYEE_CODE" ) and
( "DIV"."DIVISION_CODE" = "L"."DIVISION_CODE" ) and
( "L"."EMPLOYEE_CODE" = "PAYROLL"."EMPLOYEE_CODE" ) and
( "PAYROLL"."DIVISION_CODE" = "L"."DIVISION_CODE" ) and
( ( "EMP"."CURRENT_STATUS" = 'C' ) AND
( "PAYROLL"."PAY_ELEMENT_CODE" = 'BSC' ) AND
( "PAYROLL"."PERIOD" = 88) AND
("EMP"."EMPLOYEE_CODE"="A"."EMPLOYEE_CODE") AND
("A"."PERIOD"=88))
The above query returs rows in Standard Edition but throws error in XE with the same table structure and same data.
Kindly help me in this regard,
Vijayaraghavan K

<!--[if gte mso 9]><xml>
Normal
0
MicrosoftInternetExplorer4
</xml><![endif]-->
<!--[if gte mso 10]>
<style>
/* Style Definitions */
table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman";}
</style>
<![endif]-->
CREATE TABLE "DBO"."ATTENDANCE"
( "EMPLOYEE_CODE" VARCHAR2(6
BYTE) NOT NULL ENABLE,
"PERIOD"
VARCHAR2(7 BYTE) NOT NULL ENABLE,
"DIVISION_CODE"
NUMBER(2,0) NOT NULL ENABLE,
"PUBLIC_HOLIDAYS"
NUMBER(2,0),
"WEEKLY_HOLIDAYS"
NUMBER(2,0),
"CASUAL_LEAVE"
NUMBER(5,2),
"EARNED_LEAVE"
NUMBER(5,2),
"ON_DUTY"
NUMBER(5,2),
"SICK_LEAVE"
NUMBER(5,2),
"ESI_LEAVE"
NUMBER(5,2),
"LOSS_OF_PAY_DAYS"
NUMBER(5,2),
"CANTEEN_DAYS"
NUMBER(5,2),
"WORKING_DAYS"
NUMBER(5,2),
"ATTENDED_DAYS"
NUMBER(5,2),
"PAID_DAYS"
NUMBER(5,2),
"AUTHORIZATION_TAG"
VARCHAR2(1 BYTE),
"CREATED_BY"
VARCHAR2(8 BYTE),
"CREATED_DATE"
DATE,
"LAST_MODIFIED_BY"
VARCHAR2(8 BYTE),
"LAST_MODIFIED_DATE"
DATE,
CONSTRAINT "PK_ATTENDANCE" PRIMARY
KEY ("EMPLOYEE_CODE", "PERIOD")
CONSTRAINT "ATTENDANCE_EMPLOYEE_FK1"
FOREIGN KEY ("EMPLOYEE_CODE")
REFERENCES
"DBO"."EMPLOYEE" ("EMPLOYEE_CODE") ENABLE
===============================================================
CREATE TABLE "DBO"."DEPARTMENT"
( "DIVISION_CODE" NUMBER(2,0)
NOT NULL ENABLE,
"DEPARTMENT_CODE"
NUMBER(3,0) NOT NULL ENABLE,
"DESCRIPTION"
VARCHAR2(60 BYTE) NOT NULL ENABLE,
"CREATED_BY"
VARCHAR2(8 BYTE),
"CREATED_DATE"
DATE,
"LAST_MODIFIED_BY"
VARCHAR2(8 BYTE),
"LAST_MODIFIED_DATE"
DATE,
CONSTRAINT "PK_DEPARTMENT" PRIMARY
KEY ("DIVISION_CODE", "DEPARTMENT_CODE")
CONSTRAINT "FK_DEPARTMENT_DIVISION"
FOREIGN KEY ("DIVISION_CODE")
REFERENCES
"DBO"."DIVISION" ("DIVISION_CODE") ON DELETE
CASCADE ENABLE
===============================================================
CREATE TABLE "DBO"."DIVISION"
( "DIVISION_CODE" NUMBER(2,0)
NOT NULL ENABLE,
"COMPANY_CODE"
NUMBER(2,0),
"DESCRIPTION"
VARCHAR2(30 BYTE) NOT NULL ENABLE,
"ADDRESS1"
VARCHAR2(200 BYTE),
"ADDRESS2"
VARCHAR2(30 BYTE),
"ADDRESS3"
VARCHAR2(30 BYTE),
"LOCATION"
VARCHAR2(30 BYTE),
"PINCODE"
NUMBER(6,0),
"PHONE"
VARCHAR2(20 BYTE),
"EMAIL_ID"
VARCHAR2(40 BYTE),
"FAX"
VARCHAR2(20 BYTE),
"UNIT_HEAD_DESIG"
VARCHAR2(30 BYTE),
"UNIT_HEAD_NAME"
VARCHAR2(30 BYTE),
"FINANCE_HEAD_DESIG"
VARCHAR2(30 BYTE),
"FINANCE_HEAD_NAME"
VARCHAR2(30 BYTE),
"HRS_HEAD_DESIG"
VARCHAR2(30 BYTE),
"HRS_HEAD_NAME"
VARCHAR2(30 BYTE),
"PROCUREMENT_MEMBER1"
VARCHAR2(30 BYTE),
"PROCUREMENT_MEMBER2"
VARCHAR2(30 BYTE),
"PROCUREMENT_MEMBER3"
VARCHAR2(30 BYTE),
"PAN_NO"
VARCHAR2(20 BYTE),
"GST_NO"
VARCHAR2(20 BYTE),
"CST_NO"
VARCHAR2(20 BYTE),
"CONTRA_GL_CODE"
NUMBER(6,0),
"ECC_CODE"
VARCHAR2(20 BYTE),
"ESI_NO"
VARCHAR2(15 BYTE),
"PF_NO"
VARCHAR2(15 BYTE),
"PROFESSIONAL_TAX_NO"
VARCHAR2(15 BYTE),
"SALES_TAX_NO"
VARCHAR2(15 BYTE),
"CREATED_BY"
VARCHAR2(8 BYTE),
"CREATED_DATE"
DATE,
"LAST_MODIFIED_BY"
VARCHAR2(8 BYTE),
"LAST_MODIFIED_DATE"
DATE,
"COMPANY_ID"
CHAR(3 BYTE),
"NAME"
VARCHAR2(30 BYTE),
"PIN_CODE"
NUMBER(6,0),
"PHONE_NUMBER"
VARCHAR2(20 BYTE),
"FAX_NUMBER"
VARCHAR2(20 BYTE),
"PAN_NUMBER"
VARCHAR2(20 BYTE),
"GST_NUMBER"
VARCHAR2(20 BYTE),
"CST_NUMBER"
VARCHAR2(20 BYTE),
"TAN_NO"
VARCHAR2(20 BYTE),
"STATUS"
VARCHAR2(1 BYTE),
CONSTRAINT "PK_DIVISION_CODE"
PRIMARY KEY ("DIVISION_CODE")
CONSTRAINT "FK_COMPANY_CODE" FOREIGN
KEY ("COMPANY_CODE")
REFERENCES
"DBO"."COMPANY" ("COMPANY_CODE") ON DELETE
CASCADE ENABLE
==============================================================
CREATE TABLE
"DBO"."EMPLOYEE"
( "EMPLOYEE_CODE" VARCHAR2(6
BYTE) NOT NULL ENABLE,
"NAME"
VARCHAR2(30 BYTE) NOT NULL ENABLE,
"EMPLOYEE_INITIALS"
VARCHAR2(3 BYTE),
"FH_NAME"
VARCHAR2(30 BYTE) NOT NULL ENABLE,
"BIRTH_DATE"
DATE NOT NULL ENABLE,
VARCHAR2(1 BYTE) NOT NULL ENABLE,
"STATUS"
VARCHAR2(1 BYTE) NOT NULL ENABLE,
"BLOOD_GROUP"
VARCHAR2(15 BYTE),
"ADDRESS"
VARCHAR2(30 BYTE),
"STREET"
VARCHAR2(30 BYTE),
"EMAIL"
VARCHAR2(30 BYTE),
"CITY"
VARCHAR2(30 BYTE),
"STATE"
VARCHAR2(30 BYTE),
"PINCODE"
VARCHAR2(6 BYTE),
"COUNTRY"
VARCHAR2(20 BYTE),
"PHONE"
VARCHAR2(15 BYTE),
"QUALIFICATION"
VARCHAR2(30 BYTE) NOT NULL ENABLE,
"DESIGNATION"
VARCHAR2(30 BYTE) NOT NULL ENABLE,
"GRADE"
VARCHAR2(2 BYTE),
"SUPERVISOR_CODE"
VARCHAR2(6 BYTE),
"CATEGORY_CODE"
VARCHAR2(2 BYTE) NOT NULL ENABLE,
"SUB_CATEGORY_CODE"
VARCHAR2(2 BYTE) NOT NULL ENABLE,
"SUB_CATEGORY_TYPE"
VARCHAR2(1 BYTE),
"DEPARTMENT_CODE"
NUMBER(3,0) NOT NULL ENABLE,
"LOCATION_CODE"
VARCHAR2(3 BYTE) NOT NULL ENABLE,
"DIVISION_CODE"
NUMBER(2,0) NOT NULL ENABLE,
"COST_CODE"
VARCHAR2(4 BYTE),
"JOINING_DATE"
DATE NOT NULL ENABLE,
"PROBATION_DATE"
DATE,
"CONFIRMATION_DATE"
DATE,
"PROMOTION_DATE"
DATE,
"TERMINATION_DATE"
DATE,
"TERMINATION_REASON"
VARCHAR2(30 BYTE),
"CURRENT_STATUS"
VARCHAR2(1 BYTE),
"MAX_CASUAL_LEAVE"
NUMBER(5,2),
"MAX_EARNED_LEAVE"
NUMBER(5,2),
"MAX_MEDICAL_LEAVE"
NUMBER(5,2),
"MONTH_OF_INCREMENT"
VARCHAR2(3 BYTE),
"NO_OF_INCREMENT"
NUMBER(2,0),
"LAST_INCREMENT_MONTH"
VARCHAR2(3 BYTE),
"PAN_NO"
VARCHAR2(15 BYTE),
"PF_NO"
VARCHAR2(15 BYTE),
"PF_PERCENTAGE"
NUMBER,
"VOLUNTARY_PF_PERCENTAGE"
NUMBER(3,0),
"PF_DATE"
DATE,
"ESI_INDICATOR"
VARCHAR2(1 BYTE),
"ESI_NO"
VARCHAR2(15 BYTE),
"ESI_DATE"
DATE,
"ESI_DISPENSARY"
VARCHAR2(30 BYTE),
"MODE_OF_PAYMENT"
VARCHAR2(3 BYTE),
"BANK_CODE"
VARCHAR2(3 BYTE),
"BANK_AC_NO"
VARCHAR2(15 BYTE),
"BRANCH_CODE"
VARCHAR2(3 BYTE),
"CREATED_BY"
VARCHAR2(8 BYTE),
"CREATED_DATE"
DATE,
"LAST_MODIFIED_BY"
VARCHAR2(8 BYTE),
"LAST_MODIFIED_DATE"
DATE,
"SAF_CODE"
VARCHAR2(30 BYTE),
"GSAF_CODE"
VARCHAR2(30 BYTE),
"IMAGE_LINK"
VARCHAR2(200 BYTE),
"PHONE_MOBILE"
VARCHAR2(15 BYTE),
CONSTRAINT "PK_EMP" PRIMARY KEY
("EMPLOYEE_CODE")
CONSTRAINT "FK_EMPLOYEE_CATEGORY"
FOREIGN KEY ("CATEGORY_CODE")
REFERENCES
"DBO"."CATEGORY" ("CATEGORY_CODE") ENABLE,
CONSTRAINT "FK_EMPLOYEE_DEPARTMENT"
FOREIGN KEY ("DIVISION_CODE", "DEPARTMENT_CODE")
REFERENCES
"DBO"."DEPARTMENT" ("DIVISION_CODE", "DEPARTMENT_CODE")
ON DELETE CASCADE ENABLE,
CONSTRAINT "FK_EMPLOYEE_DIVISION"
FOREIGN KEY ("DIVISION_CODE")
REFERENCES
"DBO"."DIVISION" ("DIVISION_CODE") ENABLE,
CONSTRAINT "FK_EMPLOYEE_LOCATION"
FOREIGN KEY ("LOCATION_CODE")
REFERENCES "DBO"."LOCATION"
("LOCATION_CODE") ENABLE,
CONSTRAINT "FK_EMPLOYEE_SUBCATEGORY"
FOREIGN KEY ("SUB_CATEGORY_CODE")
REFERENCES
"DBO"."SUB_CATEGORY" ("SUB_CATEGORY_CODE") ENABLE
===============================================================
CREATE TABLE "DBO"."FOOD_COUPON"
( "PAY_ELEMENT_CODE" VARCHAR2(3
BYTE),
"EMPLOYEE_CODE"
VARCHAR2(6 BYTE),
"PERIOD"
VARCHAR2(7 BYTE),
"AMOUNT"
NUMBER(10,2),
"CREATED_BY"
VARCHAR2(8 BYTE),
"CREATED_DATE"
DATE,
"LAST_MODIFIED_BY"
VARCHAR2(8 BYTE),
"LAST_MODIFIED_DATE"
DATE,
CONSTRAINT "FD_PAY_ELEMENT" FOREIGN
KEY ("PAY_ELEMENT_CODE")
REFERENCES
"DBO"."PAY_ELEMENT" ("PAY_ELEMENT_CODE") ENABLE,
CONSTRAINT "FD_EMPLOYEE_CODE"
FOREIGN KEY ("EMPLOYEE_CODE")
REFERENCES
"DBO"."EMPLOYEE" ("EMPLOYEE_CODE") ENABLE
==========================================================
CREATE TABLE
"DBO"."LEAVE"
( "EMPLOYEE_CODE" VARCHAR2(6
BYTE) NOT NULL ENABLE,
"LEAVE_CODE"
VARCHAR2(2 BYTE) NOT NULL ENABLE,
"LEAVE_FROM_DATE"
DATE NOT NULL ENABLE,
"LEAVE_TO_DATE"
DATE NOT NULL ENABLE,
"LEAVE_FROM_SESSION"
VARCHAR2(1 BYTE),
"LEAVE_TO_SESSION"
VARCHAR2(1 BYTE),
"LEAVE_REQUISITION_DATE"
DATE,
"LEAVE_DAYS"
NUMBER(3,1),
"LOP_DAYS"
NUMBER(4,1),
"SIGNED_BY"
VARCHAR2(6 BYTE),
"SANCTIONED_BY"
VARCHAR2(6 BYTE),
"LEAVE_REASON"
VARCHAR2(100 BYTE),
"PUBLIC_HOLIDAYS"
NUMBER(2,0),
"WEEKLY_HOLIDAYS"
NUMBER(2,0),
"PERIOD"
VARCHAR2(7 BYTE),
"AUTHORIZATION_TAG"
VARCHAR2(1 BYTE),
"CREATED_BY"
VARCHAR2(8 BYTE),
"CREATED_DATE"
DATE,
"LAST_MODIFIED_BY"
VARCHAR2(8 BYTE),
"LAST_MODIFIED_DATE"
DATE,
CONSTRAINT "PK_LEAVE" PRIMARY KEY
("EMPLOYEE_CODE", "LEAVE_CODE",
"LEAVE_FROM_DATE", "LEAVE_TO_DATE")
CONSTRAINT "SYS_C0037897" FOREIGN
KEY ("SANCTIONED_BY")
REFERENCES "DBO"."EMPLOYEE"
("EMPLOYEE_CODE") ON DELETE CASCADE DISABLE,
CONSTRAINT "SYS_C0037898" FOREIGN
KEY ("EMPLOYEE_CODE")
REFERENCES
"DBO"."EMPLOYEE" ("EMPLOYEE_CODE") ON DELETE
CASCADE DISABLE,
CONSTRAINT "SYS_C0037899" FOREIGN
KEY ("SIGNED_BY")
REFERENCES "DBO"."EMPLOYEE"
("EMPLOYEE_CODE") ON DELETE CASCADE DISABLE,
FOREIGN KEY ("LEAVE_CODE")
REFERENCES
"DBO"."LEAVE_TYPE" ("LEAVE_CODE") ON DELETE
CASCADE ENABLE
===============================================================
CREATE TABLE "DBO"."LEAVE_BALANCE"
( "EMPLOYEE_CODE" VARCHAR2(6
BYTE) NOT NULL ENABLE,
"DIVISION_CODE"
NUMBER(2,0),
"EL_BALANCE"
NUMBER(6,2),
"CL_BALANCE"
NUMBER(6,2),
"ML_BALANCE"
NUMBER(6,2),
"ADJ_PAISE"
NUMBER(2,0),
"CREATED_BY"
VARCHAR2(8 BYTE),
"CREATED_DATE"
DATE,
"LAST_MODIFIED_BY"
VARCHAR2(8 BYTE),
"LAST_MODIFIED_DATE"
DATE,
"YEAR"
NUMBER(4,0),
CONSTRAINT "PK_LEAVE_BALANCE"
PRIMARY KEY ("EMPLOYEE_CODE")
CONSTRAINT
"FK_LEAVE_BALANCE_DIVISION" FOREIGN KEY ("DIVISION_CODE")
REFERENCES "DBO"."DIVISION"
("DIVISION_CODE") ON DELETE CASCADE ENABLE,
CONSTRAINT "SYS_C0037900" FOREIGN
KEY ("EMPLOYEE_CODE")
REFERENCES
"DBO"."EMPLOYEE" ("EMPLOYEE_CODE") ON DELETE
CASCADE DISABLE
========================================================
CREATE TABLE "DBO"."PAY"
( "EMPLOYEE_CODE" VARCHAR2(6
BYTE) NOT NULL ENABLE,
"PAY_ELEMENT_CODE"
VARCHAR2(3 BYTE) NOT NULL ENABLE,
"AMOUNT"
NUMBER(10,2) NOT NULL ENABLE,
"CREATED_BY"
VARCHAR2(8 BYTE),
"CREATED_DATE"
DATE,
"LAST_MODIFIED_BY"
VARCHAR2(8 BYTE),
"LAST_MODIFIED_DATE"
DATE,
CONSTRAINT "PK_PAY" PRIMARY KEY
("EMPLOYEE_CODE", "PAY_ELEMENT_CODE")
CONSTRAINT "FK_PAY_EMPLOYEE_CODE"
FOREIGN KEY ("EMPLOYEE_CODE")
REFERENCES
"DBO"."EMPLOYEE" ("EMPLOYEE_CODE") ENABLE,
CONSTRAINT "FK_PAY_PAYELEMENT"
FOREIGN KEY ("PAY_ELEMENT_CODE")
REFERENCES
"DBO"."PAY_ELEMENT" ("PAY_ELEMENT_CODE") ON
DELETE CASCADE ENABLE
================================================ ======
CREATE TABLE "DBO"."PAY_ELEMENT"
( "PAY_ELEMENT_CODE" VARCHAR2(3
BYTE) NOT NULL ENABLE,
"DESCRIPTION"
VARCHAR2(30 BYTE) NOT NULL ENABLE,
"PAY_ELEMENT_TYPE"
VARCHAR2(1 BYTE) NOT NULL ENABLE,
"PARTIAL_INDICATOR"
VARCHAR2(1 BYTE),
"TAX_INDICATOR"
VARCHAR2(1 BYTE),
"CREATED_BY"
VARCHAR2(8 BYTE),
"CREATED_DATE"
DATE,
"LAST_MODIFIED_BY"
VARCHAR2(8 BYTE),
"LAST_MODIFIED_DATE"
DATE,
"SEQUENCE_NO"
NUMBER(2,0),
CONSTRAINT "PK_PAY_ELEMENT" PRIMARY
KEY ("PAY_ELEMENT_CODE")
=======================================================
CREATE TABLE "DBO"."PAYROLL"
( "EMPLOYEE_CODE" VARCHAR2(6
BYTE) NOT NULL ENABLE,
"PAY_ELEMENT_CODE"
VARCHAR2(3 BYTE) NOT NULL ENABLE,
"PERIOD"
VARCHAR2(7 BYTE) NOT NULL ENABLE,
"AMOUNT"
NUMBER(10,2) NOT NULL ENABLE,
"DIVISION_CODE"
NUMBER(2,0) NOT NULL ENABLE,
"SERIAL_CODE"
NUMBER(2,0),
"AUTHORIZATION_TAG"
VARCHAR2(1 BYTE),
"CREATED_BY"
VARCHAR2(8 BYTE),
"CREATED_DATE"
DATE,
"LAST_MODIFIED_BY"
VARCHAR2(8 BYTE),
"LAST_MODIFIED_DATE"
DATE,
CONSTRAINT "SYS_C0037906" FOREIGN
KEY ("EMPLOYEE_CODE")
REFERENCES
"DBO"."EMPLOYEE" ("EMPLOYEE_CODE") ON DELETE
CASCADE DISABLE
============================================================
these are the Table structures
Please help me in this regard

Similar Messages

  • Connect Oracle Database with help of sql server storedprocedure

    Hii,
              Is there Any way to connect Oracle Database Using sql server storedprocedure.I want access oracle database and take some data and insert into my sql server database.so is there any way to connect in one
    stored procedure to connect oracle database and take some data and insert in to my sql server database.
    Nikunj Nandaniya

    Hello,
    I am getting below error when i kust Clic k on Test Connection in SSMS:
    TITLE: Microsoft SQL Server Management Studio
    The test connection to the linked server failed.
    ADDITIONAL INFORMATION:
    An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
    Cannot initialize the data source object of OLE DB provider "OraOLEDB.Oracle" for linked server "test".
    OLE DB provider "OraOLEDB.Oracle" for linked server "test" returned message "ORA-12154: TNS:could not resolve the connect identifier specified". (Microsoft SQL Server, Error: 7303)
    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.50.4000&EvtSrc=MSSQLServer&EvtID=7303&LinkId=20476
    BUTTONS:
    OK
    Can you please guide is there any other setting i need to do after install Oracle Client ?
    Best Regards,
    Tushar Malvi

  • Unable to Create Quotations in Oracle Apps with named PL/SQL Block

    Dear All,
    I got struced while creating Qotations from the backend using oracle API in a Procedure.But the same API working fine in Anonymous block and creating Qutations in apps.But the in parameters are same in anonymous and named bolck.i have done Debugging also and its returning in parameter values.but quotations not created in apps.
    I am sending the both scripts(named plsql and anonymous blocks) please anybody knows about this correct me where iam doing mistake.
    *******anonymous bolck*********
    DECLARE
    X_ROWID VARCHAR2(200) :=NULL;
    X_PO_HEADER_ID NUMBER :=NULL;
    X_AGENT_ID NUMBER :=25;
    X_TYPE_LOOKUP_CODE VARCHAR2(200) :='QUOTATION';
    X_LAST_UPDATE_DATE DATE :=SYSDATE;
    X_LAST_UPDATED_BY NUMBER :=1318;
    X_SEGMENT1 VARCHAR2(200) :=2477;
    X_SUMMARY_FLAG VARCHAR2(200) :='N';
    X_ENABLED_FLAG VARCHAR2(200) :='Y';
    X_SEGMENT2 VARCHAR2(200);
    X_SEGMENT3 VARCHAR2(200);
    X_SEGMENT4 VARCHAR2(200);
    X_SEGMENT5 VARCHAR2(200);
    X_START_DATE_ACTIVE DATE;
    X_END_DATE_ACTIVE DATE;
    X_LAST_UPDATE_LOGIN NUMBER :=45786;
    X_CREATION_DATE DATE :=SYSDATE;
    X_CREATED_BY NUMBER :=1318;
    X_VENDOR_ID NUMBER :=5;
    X_VENDOR_SITE_ID NUMBER :=6;
    X_VENDOR_CONTACT_ID NUMBER :=181;
    X_SHIP_TO_LOCATION_ID NUMBER :=204;
    X_BILL_TO_LOCATION_ID NUMBER :=207;
    X_TERMS_ID NUMBER :=10013;
    X_SHIP_VIA_LOOKUP_CODE VARCHAR2(200) :='UPS';
    X_FOB_LOOKUP_CODE VARCHAR2(200) :='Origin';
    X_PAY_ON_CODE VARCHAR2(200);
    X_FREIGHT_TERMS_LOOKUP_CODE VARCHAR2(200) :='Due';
    X_STATUS_LOOKUP_CODE VARCHAR2(200) :='A';
    X_CURRENCY_CODE VARCHAR2(200) :='USD';
    X_RATE_TYPE VARCHAR2(200);
    X_RATE_DATE DATE;
    X_RATE NUMBER;
    X_FROM_HEADER_ID NUMBER;
    X_FROM_TYPE_LOOKUP_CODE VARCHAR2(200);
    X_START_DATE DATE;
    X_END_DATE DATE;
    X_BLANKET_TOTAL_AMOUNT NUMBER;
    X_AUTHORIZATION_STATUS VARCHAR2(200);
    X_REVISION_NUM NUMBER;
    X_REVISED_DATE DATE;
    X_APPROVED_FLAG VARCHAR2(200);
    X_APPROVED_DATE DATE;
    X_AMOUNT_LIMIT NUMBER;
    X_MIN_RELEASE_AMOUNT NUMBER;
    X_NOTE_TO_AUTHORIZER VARCHAR2(200);
    X_NOTE_TO_VENDOR VARCHAR2(200);
    X_NOTE_TO_RECEIVER VARCHAR2(200);
    X_PRINT_COUNT NUMBER;
    X_PRINTED_DATE DATE;
    X_VENDOR_ORDER_NUM VARCHAR2(200);
    X_CONFIRMING_ORDER_FLAG VARCHAR2(200);
    X_COMMENTS VARCHAR2(200);
    X_REPLY_DATE DATE;
    X_REPLY_METHOD_LOOKUP_CODE VARCHAR2(200);
    X_RFQ_CLOSE_DATE DATE;
    X_QUOTE_TYPE_LOOKUP_CODE VARCHAR2(200) :='CATALOG';
    X_QUOTATION_CLASS_CODE VARCHAR2(200) :='CATALOG';
    X_QUOTE_WARNING_DELAY_UNIT VARCHAR2(200);
    X_QUOTE_WARNING_DELAY NUMBER :=7;
    X_QUOTE_VENDOR_QUOTE_NUMBER VARCHAR2(200);
    X_ACCEPTANCE_REQUIRED_FLAG VARCHAR2(200);
    X_ACCEPTANCE_DUE_DATE DATE;
    X_CLOSED_DATE DATE;
    X_USER_HOLD_FLAG VARCHAR2(200);
    X_APPROVAL_REQUIRED_FLAG VARCHAR2(200);
    X_CANCEL_FLAG VARCHAR2(200);
    X_FIRM_STATUS_LOOKUP_CODE VARCHAR2(200);
    X_FIRM_DATE DATE;
    X_FROZEN_FLAG VARCHAR2(200);
    X_SUPPLY_AGREEMENT_FLAG VARCHAR2(200) :='L';
    X_GLOBAL_AGREEMENT_FLAG VARCHAR2(200);
    X_ATTRIBUTE_CATEGORY VARCHAR2(200);
    X_ATTRIBUTE1 VARCHAR2(200);
    X_ATTRIBUTE2 VARCHAR2(200);
    X_ATTRIBUTE3 VARCHAR2(200);
    X_ATTRIBUTE4 VARCHAR2(200);
    X_ATTRIBUTE5 VARCHAR2(200);
    X_ATTRIBUTE6 VARCHAR2(200);
    X_ATTRIBUTE7 VARCHAR2(200);
    X_ATTRIBUTE8 VARCHAR2(200);
    X_ATTRIBUTE9 VARCHAR2(200);
    X_ATTRIBUTE10 VARCHAR2(200);
    X_ATTRIBUTE11 VARCHAR2(200);
    X_ATTRIBUTE12 VARCHAR2(200);
    X_ATTRIBUTE13 VARCHAR2(200);
    X_ATTRIBUTE14 VARCHAR2(200);
    X_ATTRIBUTE15 VARCHAR2(200);
    X_CLOSED_CODE VARCHAR2(200);
    X_USSGL_TRANSACTION_CODE VARCHAR2(200);
    X_GOVERNMENT_CONTEXT VARCHAR2(200);
    X_GLOBAL_ATTRIBUTE_CATEGORY VARCHAR2(200);
    X_GLOBAL_ATTRIBUTE1 VARCHAR2(200);
    X_GLOBAL_ATTRIBUTE2 VARCHAR2(200);
    X_GLOBAL_ATTRIBUTE3 VARCHAR2(200);
    X_GLOBAL_ATTRIBUTE4 VARCHAR2(200);
    X_GLOBAL_ATTRIBUTE5 VARCHAR2(200);
    X_GLOBAL_ATTRIBUTE6 VARCHAR2(200);
    X_GLOBAL_ATTRIBUTE7 VARCHAR2(200);
    X_GLOBAL_ATTRIBUTE8 VARCHAR2(200);
    X_GLOBAL_ATTRIBUTE9 VARCHAR2(200);
    X_GLOBAL_ATTRIBUTE10 VARCHAR2(200);
    X_GLOBAL_ATTRIBUTE11 VARCHAR2(200);
    X_GLOBAL_ATTRIBUTE12 VARCHAR2(200);
    X_GLOBAL_ATTRIBUTE13 VARCHAR2(200);
    X_GLOBAL_ATTRIBUTE14 VARCHAR2(200);
    X_GLOBAL_ATTRIBUTE15 VARCHAR2(200);
    X_GLOBAL_ATTRIBUTE16 VARCHAR2(200);
    X_GLOBAL_ATTRIBUTE17 VARCHAR2(200);
    X_GLOBAL_ATTRIBUTE18 VARCHAR2(200);
    X_GLOBAL_ATTRIBUTE19 VARCHAR2(200);
    X_GLOBAL_ATTRIBUTE20 VARCHAR2(200);
    X_MANUAL BOOLEAN;
    X_PRICE_UPDATE_TOLERANCE NUMBER;
    P_SHIPPING_CONTROL VARCHAR2(200);
    P_ENCUMBRANCE_REQUIRED_FLAG VARCHAR2(200);
    BEGIN
    APPS.PO_HEADERS_SV11.INSERT_PO(X_ROWID ,
    X_PO_HEADER_ID ,
    X_AGENT_ID ,
    X_TYPE_LOOKUP_CODE ,
    X_LAST_UPDATE_DATE ,
    X_LAST_UPDATED_BY ,
    X_SEGMENT1 ,
    X_SUMMARY_FLAG ,
    X_ENABLED_FLAG ,
    X_SEGMENT2 ,
    X_SEGMENT3 ,
    X_SEGMENT4 ,
    X_SEGMENT5 ,
    X_START_DATE_ACTIVE ,
    X_END_DATE_ACTIVE ,
    X_LAST_UPDATE_LOGIN ,
    X_CREATION_DATE ,
    X_CREATED_BY ,
    X_VENDOR_ID ,
    X_VENDOR_SITE_ID ,
    X_VENDOR_CONTACT_ID ,
    X_SHIP_TO_LOCATION_ID ,
    X_BILL_TO_LOCATION_ID ,
    X_TERMS_ID ,
    X_SHIP_VIA_LOOKUP_CODE ,
    X_FOB_LOOKUP_CODE ,
    X_PAY_ON_CODE ,
    X_FREIGHT_TERMS_LOOKUP_CODE ,
    X_STATUS_LOOKUP_CODE ,
    X_CURRENCY_CODE ,
    X_RATE_TYPE ,
    X_RATE_DATE ,
    X_RATE ,
    X_FROM_HEADER_ID ,
    X_FROM_TYPE_LOOKUP_CODE ,
    X_START_DATE ,
    X_END_DATE ,
    X_BLANKET_TOTAL_AMOUNT ,
    X_AUTHORIZATION_STATUS ,
    X_REVISION_NUM ,
    X_REVISED_DATE ,
    X_APPROVED_FLAG ,
    X_APPROVED_DATE ,
    X_AMOUNT_LIMIT ,
    X_MIN_RELEASE_AMOUNT ,
    X_NOTE_TO_AUTHORIZER ,
    X_NOTE_TO_VENDOR ,
    X_NOTE_TO_RECEIVER ,
    X_PRINT_COUNT ,
    X_PRINTED_DATE ,
    X_VENDOR_ORDER_NUM ,
    X_CONFIRMING_ORDER_FLAG ,
    X_COMMENTS ,
    X_REPLY_DATE ,
    X_REPLY_METHOD_LOOKUP_CODE ,
    X_RFQ_CLOSE_DATE ,
    X_QUOTE_TYPE_LOOKUP_CODE ,
    X_QUOTATION_CLASS_CODE ,
    X_QUOTE_WARNING_DELAY_UNIT ,
    X_QUOTE_WARNING_DELAY ,
    X_QUOTE_VENDOR_QUOTE_NUMBER ,
    X_ACCEPTANCE_REQUIRED_FLAG ,
    X_ACCEPTANCE_DUE_DATE ,
    X_CLOSED_DATE ,
    X_USER_HOLD_FLAG ,
    X_APPROVAL_REQUIRED_FLAG ,
    X_CANCEL_FLAG ,
    X_FIRM_STATUS_LOOKUP_CODE ,
    X_FIRM_DATE ,
    X_FROZEN_FLAG ,
    X_SUPPLY_AGREEMENT_FLAG ,
    X_GLOBAL_AGREEMENT_FLAG ,
    X_ATTRIBUTE_CATEGORY ,
    X_ATTRIBUTE1 ,
    X_ATTRIBUTE2 ,
    X_ATTRIBUTE3 ,
    X_ATTRIBUTE4 ,
    X_ATTRIBUTE5 ,
    X_ATTRIBUTE6 ,
    X_ATTRIBUTE7 ,
    X_ATTRIBUTE8 ,
    X_ATTRIBUTE9 ,
    X_ATTRIBUTE10 ,
    X_ATTRIBUTE11 ,
    X_ATTRIBUTE12 ,
    X_ATTRIBUTE13 ,
    X_ATTRIBUTE14 ,
    X_ATTRIBUTE15 ,
    X_CLOSED_CODE ,
    X_USSGL_TRANSACTION_CODE ,
    X_GOVERNMENT_CONTEXT ,
    X_GLOBAL_ATTRIBUTE_CATEGORY ,
    X_GLOBAL_ATTRIBUTE1 ,
    X_GLOBAL_ATTRIBUTE2 ,
    X_GLOBAL_ATTRIBUTE3 ,
    X_GLOBAL_ATTRIBUTE4 ,
    X_GLOBAL_ATTRIBUTE5 ,
    X_GLOBAL_ATTRIBUTE6 ,
    X_GLOBAL_ATTRIBUTE7 ,
    X_GLOBAL_ATTRIBUTE8 ,
    X_GLOBAL_ATTRIBUTE9 ,
    X_GLOBAL_ATTRIBUTE10 ,
    X_GLOBAL_ATTRIBUTE11 ,
    X_GLOBAL_ATTRIBUTE12 ,
    X_GLOBAL_ATTRIBUTE13 ,
    X_GLOBAL_ATTRIBUTE14 ,
    X_GLOBAL_ATTRIBUTE15 ,
    X_GLOBAL_ATTRIBUTE16 ,
    X_GLOBAL_ATTRIBUTE17 ,
    X_GLOBAL_ATTRIBUTE18 ,
    X_GLOBAL_ATTRIBUTE19 ,
    X_GLOBAL_ATTRIBUTE20 ,
    X_MANUAL ,
    X_PRICE_UPDATE_TOLERANCE ,
    P_SHIPPING_CONTROL ,
    P_ENCUMBRANCE_REQUIRED_FLAG );
    END;
    ***************************plsql named block****************
    CREATE OR REPLACE Procedure p6(p_row_id IN OUT VARCHAR2
    ,p_po_header_id IN OUT NUMBER
    ,p_segment1 IN OUT VARCHAR2
    ,p_Type_Lookup_Code IN VARCHAR2
                             ,p_agent_id IN NUMBER
    ,p_vendor_id IN NUMBER
    ,p_vendor_site_id IN NUMBER
    ,p_Ship_To_Location_Id IN NUMBER
    ,p_Bill_To_Location_Id IN NUMBER
    ,p_terms_id IN NUMBER
    ,p_fob_lookup_code IN VARCHAR2
    ,p_Freight_Terms_Lookup_Code IN VARCHAR2
    ,p_Currency_Code IN VARCHAR2
    --,p_Start_Date IN DATE
                             ,p_Quote_Type_Lookup_Code IN VARCHAR2
    --,p_quote_warning_delay IN VARCHAR2
    --,p_Vendor_Quote_Number IN VARCHAR2
    ,p_last_update_date IN DATE
    ,p_last_updated_by IN NUMBER
    ,p_last_update_login IN NUMBER
    ,p_creation_date IN DATE
    ,p_created_by IN NUMBER
    ,p_Ship_Via_Lookup_Code IN varchar2
                             ,p_Vendor_Contact_Id IN NUMBER
    --,p_res_ship_via IN VARCHAR2
    ,p_Comments IN VARCHAR2
    ,P_Supply_Agreement_Flag IN VARCHAR2
    ,p_organization_id IN VARCHAR2
    --,p_procurement_channel IN VARCHAR2
    --,p_Manual IN BOOLEAN
    --,p_return_status OUT VARCHAR2
    ,P_Authorization_Status IN VARCHAR2
                             -- ,p_error_msg OUT VARCHAR2
                        ,p_Summary_Flag in varchar2
                        ,p_Enabled_Flag in varchar2
                        ,p_Status_Lookup_Code in varchar2
                        ,p_Quotation_Class_Code in varchar2
                        ,p_Approval_Required_Flag in varchar2
                        --,X_shipping_control VARCHAR2 -- <INBOUND LOGISTICS FPJ>
    --,X_encumbrance_required_flag VARCHAR2
                        ) AS
    v_segment1 varchar2(50):=null;
    v_po_header_id number:=null;
    v_row_id varchar2(50):=null;
    BEGIN
    po_headers_sv11.insert_po(X_Rowid => v_row_id --VARCHAR2
    ,X_Po_Header_Id => v_po_header_id --NUMBER
    ,X_Agent_Id => p_agent_id --NUMBER
    ,X_Type_Lookup_Code => p_Type_Lookup_Code
    ,X_Segment1 => v_segment1 --VARCAHR2
    ,X_Summary_Flag => p_Summary_Flag
    ,X_Enabled_Flag => p_Enabled_Flag
    ,X_Vendor_Id => p_vendor_id --NUMBER
    ,X_Vendor_Site_Id => p_vendor_site_id --NUMBER
    ,X_Ship_To_Location_Id => p_Ship_To_Location_Id --NUMBER
    ,X_Bill_To_Location_Id => p_Bill_To_Location_Id --NUMBER
    ,X_Terms_Id => p_terms_id --NUMBER
    ,X_Fob_Lookup_Code => p_fob_lookup_code --VARCHAR
    ,X_Freight_Terms_Lookup_Code => p_Freight_Terms_Lookup_Code --VARCHAR
    ,X_Status_Lookup_Code => p_Status_Lookup_Code -- Active
    ,X_Currency_Code => p_Currency_Code --VARCHAR
    ,X_Start_Date =>NULL--p_start_date --DATE
    ,X_Reply_Date => NULL--p_Start_Date --DATE
    ,X_Quote_Type_Lookup_Code => p_Quote_Type_Lookup_Code --VARCHAR
    ,X_Quotation_Class_Code => p_Quotation_Class_Code
    ,X_Quote_Warning_Delay => NULL--p_quote_warning_delay --VARCHAR
    ,X_Quote_Vendor_Quote_Number => NULL--p_Vendor_Quote_Number --VARCHAR
    ,X_Approval_Required_Flag => p_Approval_Required_Flag
    ,X_Last_Update_Date => p_last_update_date --DATE
    ,X_Last_Updated_By => p_last_updated_by --NUMBER
    ,X_Segment2 => NULL
    ,X_Segment3 => NULL
    ,X_Segment4 => NULL
    ,X_Segment5 => NULL
    ,X_Start_Date_Active => NULL
    ,X_End_Date_Active => NULL
    ,X_Last_Update_Login => p_last_update_login --NUMBER
    ,X_Creation_Date => p_creation_date --DATE
    ,X_Created_By => p_created_by --NUMBER
    ,X_Vendor_Contact_Id => p_vendor_contact_id --NUMBER
    ,X_Ship_Via_Lookup_Code => p_Ship_Via_Lookup_Code
    ,X_Pay_On_Code => NULL
    ,X_Rate_Type => NULL
    ,X_Rate_Date => NULL
    ,X_Rate => NULL
    ,X_From_Header_Id => NULL
    ,X_From_Type_Lookup_Code => NULL
    ,X_End_Date => NULL
    ,X_Blanket_Total_Amount => NULL
    ,X_Authorization_Status => P_Authorization_Status
    ,X_Revision_Num => NULL
    ,X_Revised_Date => NULL
    ,X_Approved_Flag => NULL
    ,X_Approved_Date => NULL
    ,X_Amount_Limit => NULL
    ,X_Min_Release_Amount => NULL
    ,X_Note_To_Authorizer => NULL
    ,X_Note_To_Vendor => NULL
    ,X_Note_To_Receiver => NULL
    ,X_Print_Count => NULL
    ,X_Printed_Date => NULL
    ,X_Vendor_Order_Num => NULL
    ,X_Confirming_Order_Flag => NULL
    ,X_Comments => NULL
    ,X_Reply_Method_Lookup_Code => NULL
    ,X_Rfq_Close_Date => NULL
    ,X_Quote_Warning_Delay_Unit => NULL
    ,X_Acceptance_Required_Flag => NULL
    ,X_Acceptance_Due_Date => NULL
    ,X_Closed_Date => NULL
    ,X_User_Hold_Flag => NULL
    ,X_Cancel_Flag => 'N'
    ,X_Firm_Status_Lookup_Code => NULL
    ,X_Firm_Date => NULL
    ,X_Frozen_Flag => NULL
    ,X_Supply_Agreement_Flag => P_Supply_Agreement_Flag
    ,X_Global_Agreement_Flag => NULL
    ,X_Attribute_Category => NULL
    ,X_Attribute1 => NULL
    ,X_Attribute2 => NULL
    ,X_Attribute3 => p_organization_id
    ,X_Attribute4 => NULL
    ,X_Attribute5 => NULL
    ,X_Attribute6 => NULL
    ,X_Attribute7 => NULL
    ,X_Attribute8 => NULL
    ,X_Attribute9 => NULL
    ,X_Attribute10 => NULL
    ,X_Attribute11 => NULL
    ,X_Attribute12 => NULL
    ,X_Attribute13 => NULL
    ,X_Attribute14 => NULL
    ,X_Attribute15 => NULL
    ,X_Closed_Code => NULL
    ,X_Ussgl_Transaction_Code => NULL
    ,X_Government_Context => NULL
    ,X_Global_Attribute_Category => NULL
    ,X_Global_Attribute1 => NULL
    ,X_Global_Attribute2 => NULL
    ,X_Global_Attribute3 => NULL
    ,X_Global_Attribute4 => NULL
    ,X_Global_Attribute5 => NULL
    ,X_Global_Attribute6 => NULL
    ,X_Global_Attribute7 => NULL
    ,X_Global_Attribute8 => NULL
    ,X_Global_Attribute9 => NULL
    ,X_Global_Attribute10 => NULL
    ,X_Global_Attribute11 => NULL
    ,X_Global_Attribute12 => NULL
    ,X_Global_Attribute13 => NULL
    ,X_Global_Attribute14 => NULL
    ,X_Global_Attribute15 => NULL
    ,X_Global_Attribute16 => NULL
    ,X_Global_Attribute17 => NULL
    ,X_Global_Attribute18 => NULL
    ,X_Global_Attribute19 => NULL
    ,X_Global_Attribute20 => NULL
    ,X_Manual => NULL
    ,X_Price_Update_Tolerance => NULL
                             ,p_shipping_control=> NULL--X_shipping_control -- <INBOUND LOGISTICS FPJ>
    ,p_encumbrance_required_flag=> NULL--X_encumbrance_required_flag
                             commit;
    dbms_output.put_line('agent_id:'||p_agent_id);
    dbms_output.put_line('segment1:'||P_segment1);
    dbms_output.put_line('SHIP_TO_LOCATION_ID:'||P_SHIP_TO_LOCATION_ID);
    dbms_output.put_line('BILL_TO_LOCATION_ID:'||P_BILL_TO_LOCATION_ID);
    dbms_output.put_line('VENDOR_SITE_ID:'||P_VENDOR_ID);
    dbms_output.put_line('VENDOR_SITE_ID:'||P_VENDOR_SITE_ID);
    dbms_output.put_line('SUPPLY_AGREEMENT_FLAG:'||P_SUPPLY_AGREEMENT_FLAG);
    dbms_output.put_line('QUOTE_TYPE_LOOKUP_CODE:'||p_QUOTE_TYPE_LOOKUP_CODE);
    dbms_output.put_line('FREIGHT_TERMS_LOOKUP_CODE:'||P_FREIGHT_TERMS_LOOKUP_CODE);
    dbms_output.put_line('AUTHORIZATION_STATUS:'||P_AUTHORIZATION_STATUS);
    dbms_output.put_line('ORGANIZATION_ID:'||p_ORGANIZATION_ID);
    dbms_output.put_line('VENDOR_CONTACT_ID:'||P_VENDOR_CONTACT_ID);
    dbms_output.put_line('Type_Lookup_Code:'||p_Type_Lookup_Code);
    dbms_output.put_line('Summary_Flag:'||p_Summary_Flag);
    dbms_output.put_line('Enabled_Flag:'||p_Enabled_Flag);
    dbms_output.put_line('Comments:'||p_Comments);
    dbms_output.put_line('Currency_Code:'||p_Currency_Code);
    dbms_output.put_line('Authorization_Status:'||P_Authorization_Status);
    dbms_output.put_line('Status_Lookup_Code:'||p_Status_Lookup_Code);
    dbms_output.put_line('Quotation_Class_Code:'||p_Quotation_Class_Code);
    dbms_output.put_line('Approval_Required_Flag:'||p_Approval_Required_Flag);
    dbms_output.put_line('last_update_login:'||p_last_update_login);
    dbms_output.put_line('created_by:'||p_created_by);
    dbms_output.put_line('last_update_date:'||p_last_update_date);
    dbms_output.put_line('Vendor_Contact_Id:'||p_Vendor_Contact_Id);
    dbms_output.put_line('fob_lookup_code:'||p_fob_lookup_code);
    EXCEPTION
    WHEN OTHERS THEN
    --p_return_status :='E';
    --p_error_msg     :='ERROR during Insert in PO_HEADERS.'||CHR(10)||SQLERRM;
    raise;
    END p6;
    Regards,
    YellaGoud

    What is your current Oracle user ?
    show userTry to identify the table owner:
    select owner from dba_tables where table_name='CE1LAOC';And add <table owner> as prefix to table name:
    CREATE INDEX Z05 ON <table_owner>.CE1LAOC (MANDT, PALEDGER, BUKRS, PERIO, VRGAR, VKORG, HZDAT);

  • Oracle InstantClient with Linked Server in Sql Server 2005

    We are trying to connect ORACLE server from sql server 2005 using Linked Server Feature in SqlServer 2005
    Generally Oracle Client software is needed for this activity in the sql server machine.
    Can we use "Oracle InstantClient" instead of "Oracle Client Software" to connect ORACLE using Linked Servers ?
    Please give us your views, any existing reports similar to this activity
    Thanks & Regards,
    Palani

    Thanks for your reply
    I agree that Oracle Client software is used to connect oracle from SQL SERVER 2005.
    But my doubt is can we use Oracle InstantClient instead of Oracle Client software to connect oracle from SQL SERVER 2005
    with respect to Oracle Instant Client - I would like to know the development steps (Not the installation steps of Oracle Instant Client in windows machine) to connect ORACLE server.
    Thanks & Regards,
    Palani

  • Haley Rules Engine - HaleyAuthority with respect to Oracle E Business Suite

    I am currently exploring on Haley Rules Engine which is recently aquired by Oracle.
    As per my investingation, i came to know that HaleyAuthority ruleEngine is available as plugin from the recent release of Siebel CRM 8.0 installation and onwards.
    Here goes my questions
    1) is this haleyAuthority rule engine available as third party tool? If so, How to integrate with Oracle E- Business Suite.
    2) Like Siebel 8.0, Is this HaleyAuthority plugged in any latest version of our oracle E- Business Suite?
    Please let me know your understanding and information on Haley Rules Engine with respect to Oracle E-Business Suite.
    Thanks in Advance.

    Praveen ,
    May be late for you (but for others looking similar information)
    haleyAuthority is different from Haley Determination Services (now Oracle Policy Automation)
    OPA (Haley's Determination Services) are available as Web Service which you can invoke from E-Business Suite or Use Fusion Middleware (SOA Suite / BPEL) as layer between OPA and E-Business Suite
    For overview of Haley Office Rules or Oracle Policy Automation check
    http://onlineappsdba.com/index.php/2009/04/27/oracle-policy-automation-modeling-earlier-haley-office-rules-determination/

  • Oracle XML Parser for PL/SQL - troubles with charset

    Hi,
    I'm using Oracle XML Parser for PL/SQL and have some troubles with charset of results xmldom.writeToBuffer and xmldom.writeToCLOB procedures.
    Some tags in my DOM documents contain text values in RUSSIAN (server nls_charset is CL8ISO8859P5). When I write document in varchar2 variable, buffer content is in UTF8 charset ( convert UTF8->CL8ISO8859P5 -OK).
    xmldom.setCharset(doc, 'ISO-8859-5') just after xmldom.newDOMDocument has no effect.
    xmldom.setCharset(doc, 'CL8ISO8859P5') has no effect also.
    Explicit charset direction in third parameter of
    xmldom.writeToBuffer and xmldom.writeToCLOB procedure has no effect.
    When I write document in CLOB, and then read part of CLOB in varchar2 buffer - result contain '?' in place of all russian text characters.
    What's a problem?
    How can I force XML Parser write XML in server charset?
    Oracle XML Parser for PL/SQL v 1.0.2

    I have the same problem. But in my case I am allowed only to use XML Parser for PL/SQL.
    Characterset 'WE8ISO8859P1' is used. And the language is latvian.
    After parsing a XML document and printing its contents, all latvian characters are replaced by "f".
    xmldom.setcharset(doc,'WE8ISO8859P1') has no effect.

  • Lock types in oracle 10g with sql examples

    can some body easily in simple words tell some thing about the table locks types in oracle 10g with some sql examples?

    Oracle locking is a complex topic that may not easily be explained with simple words.
    Please try to read above mentioned link starting from simple examples to used lock types. I don't think it's a good idea to "over simplify" the topic starting from the different lock types.
    Another way to explain some lock types can be found in following OTN discussion with Tom Kyte (who is also one of the primary author of Concepts Guide 11.2): TM / TX Locks ( Tom Kyte and Oracle Docu) ; note the different points of view about what is the row lock ...
    Edited by: P. Forstmann on 29 juin 2011 14:00

  • DB2 8.1 to Oracle 11g with SQL Developer 3.0

    Hi,
    I started migrating my DB2 8.1 to Oracle 11g, with SQL Developer 3.0
    Basically, I need to migrate TABLES.
    I followed these steps:
    1) I created a new Oracle database, tablespaces, users, etc.
    2) Then, I created both (DB2 and Oracle) connections into SQL Developer 3.0. All works fine.
    3) I start capturing one table with the "Copy to Oracle" feature. Done with no errors.
    But when I compare the table structure, I see the following problems in Oracle:
    a) All fields are NULLABLE = YES. SQL Developer show this field property correctly in DB2: NULLABLE = NO, but not migrated the same!
    SOLUTION: All I want is that SQL Developer simply migrating the same value who I have in the DB2. But how?
    b) In DB2 I have one field property called COLUM DEFAULT. In Oracle this property is called DATA_DEFAULT. The SQL Developer show this field property correctly for the DB2 tables (for example: 0.0, ' ', etc), but don't migrated the same value! All fields are configured to DATA_DEFAULT = NULL.
    SOLUTION: I think this occurs because NULLABLE is migrated with the value YES. Well, all I need is the same above...
    NOTE: I tested the SWISSQL DATA MIGRATION software, and it works fine. All tables, field properties and data are migrated sucessfull. But this program is trial version!
    Well, I think all of this are BUGS into SQL Developer.
    Please, anyone to help me?
    Regards,
    Ylram

    Welcome to the forum!
    >
    I just did right click in the procedure body and found [Debug, Compile for Debug, Compile, Run].
    >
    You listed a bunch of things but you didn't say what steps you actually performed and what the result was.
    Did you 'Compile'the procedure? until you compile the procedure you can't debug it.
    I just created a new procedure and when I select the body it displays in the 'Code' window on the right. But the 'Debug' icon is not enabled because the procedure was not compiled for debug.
    When I compile it for debug the 'Debug' icon is now enabled.

  • How to Unpivot, Crosstab, or Pivot using Oracle 9i with PL/SQL?

    How to Unpivot, Crosstab, or Pivot using Oracle 9i with PL/SQL?
    Here is a fictional sample layout of the data I have from My_Source_Query:
    Customer | VIN | Year | Make | Odometer | ... followed by 350 more columns/fields
    123 | 321XYZ | 2012 | Honda | 1900 |
    123 | 432ABC | 2012 | Toyota | 2300 |
    456 | 999PDQ | 2000 | Ford | 45586 |
    876 | 888QWE | 2010 | Mercedes | 38332 |
    ... followed by up to 25 more rows of data from this query.
    The exact number of records returned by My_Source_Query is unknown ahead of time, but should be less than 25 even under extreme situations.
    Here is how I would like the data to be:
    Column1 |Column2 |Column3 |Column4 |Column5 |
    Customer | 123 | 123 | 456 | 876 |
    VIN | 321XYZ | 432ABC | 999PDQ | 888QWE |
    Year | 2012 | 2012 | 2000 | 2010 |
    Make | Honda | Toyota | Ford | Mercedes|
    Odometer | 1900 | 2300 | 45586 | 38332 |
    ... followed by 350 more rows with the names of the columns/fields from the My_Source_Query.
    From reading and trying many, many, many of the posting on this topic I understand that the unknown number or rows in My_Source_Query can be a problem and have considered working with one row at a time until each row has been converted to a column.
    If possible I'd like to find a way of doing this conversion from rows to columns using a query instead of scripts if that is possible. I am a novice at this so any help is welcome.
    This is a repost. I originally posted this question to the wrong forum. Sorry about that.

    The permission level that I have in the Oracle environment is 'read only'. This is also be the permission level of the users of the query I am trying to build.
    As requested, here is the 'create' SQL to build a simple table that has the type of data I am working with.
    My real select query will have more than 350 columns and the rows returned will be 25 rows of less, but for now I am prototyping with just seven columns that have the different data types noted in my sample data.
    NOTE: This SQL has been written and tested in MS Access since I do not have permission to create and populate a table in the Oracle environment and ODBC connections are not allowed.
    CREATE TABLE tbl_MyDataSource
    (Customer char(50),
    VIN char(50),
    Year char(50),
    Make char(50),
    Odometer long,
    InvDate date,
    Amount currency)
    Here is the 'insert into' to populate the tbl_MyDataSource table with four sample records.
    INSERT INTO tbl_MyDataSource ( Customer, VIN, [Year], Make, Odometer, InvDate, Amount )
    SELECT "123", "321XYZ", "2012", "Honda", "1900", "2/15/2012", "987";
    INSERT INTO tbl_MyDataSource ( Customer, VIN, [Year], Make, Odometer, InvDate, Amount )
    VALUES ("123", "432ABC", "2012", "Toyota", "2300", "1/10/2012", "6546");
    INSERT INTO tbl_MyDataSource ( Customer, VIN, [Year], Make, Odometer, InvDate, Amount )
    VALUES ("456", "999PDQ", "2000", "Ford", "45586", "4/25/2002", "456");
    INSERT INTO tbl_MyDataSource ( Customer, VIN, [Year], Make, Odometer, InvDate, Amount )
    VALUES ("876", "888QWE", "2010", "Mercedes", "38332", "10/13/2010", "15973");
    Which should produce a table containing these columns with these values:
    tbl_MyDataSource:
    Customer     VIN     Year     Make     Odometer     InvDate          Amount
    123 | 321XYZ | 2012 | Honda      | 1900          | 2/15/2012     | 987.00
    123 | 432ABC | 2012 | Toyota | 2300 | 1/10/2012     | 6,546.00
    456 | 999PDQ | 2000 | Ford     | 45586          | 4/25/2002     | 456.00
    876 | 888QWE | 2010 | Mercedes | 38332          | 10/13/2010     | 15,973.00
    The desired result is to use Oracle 9i to convert the columns into rows using sql without using any scripts if possible.
    qsel_MyResults:
    Column1          Column2          Column3          Column4          Column5
    Customer | 123 | 123 | 456 | 876
    VIN | 321XYZ | 432ABC | 999PDQ | 888QWE
    Year | 2012 | 2012 | 2000 | 2010
    Make | Honda | Toyota | Ford | Mercedes
    Odometer | 1900 | 2300 | 45586 | 38332
    InvDate | 2/15/2012 | 1/10/2012 | 4/25/2002 | 10/13/2010
    Amount | 987.00 | 6,546.00 | 456.00 | 15,973.00
    The syntax in SQL is something I am not yet sure of.
    You said:
    >
    "Don't use the same name or alias for two different things. if you have a table called t, then don't use t as an alais for an in-line view. Pick a different name, like ordered_t, instead.">
    but I'm not clear on which part of the SQL you are suggesting I change. The code I posted is something I pieced together from some of the other postings and is not something I full understand the syntax of.
    Here is my latest (failed) attempt at this.
    select *
      from (select * from tbl_MyDataSource) t;
    with data as
    (select rownum rnum, t.* from (select * from t order by c1) ordered_t), -- changed 't' to 'ordered_t'
    rows_to_have as
    (select level rr from dual connect by level <= 7 -- number of columns in T
    select rnum,
           max(decode(rr, 1, c1)),
           max(decode(rr, 2, c2)),
           max(decode(rr, 3, c3)),
           max(decode(rr, 4, c3)),      
           max(decode(rr, 5, c3)),      
           max(decode(rr, 6, c3)),      
           max(decode(rr, 7, c3)),       
      from data, rows_to_have
    group by rnumIn the above code the "select * from tbl_MyDataSource" is a place holder for my select query which runs without error and has these exact number of fields and data types as order shown in the tbl_MyDataSource above.
    This code produces the error 'ORA-00936: missing expression'. The error appears to be starting with the 'with data as' line if I am reading my PL/Sql window correctly. Everything above that row runs without error.
    Thank you for your great patients and for sharing your considerable depth of knowledge. Any help is gratefully welcomed.

  • Oracle Connectivity with MS SQL Server. ORA-00972: identifier is too long

    I have linked Oracle Database with MS SQL Server using HS and DB Link.
    DB Link Script:
    CREATE DATABASE LINK "FCHH"
    CONNECT TO SA
    IDENTIFIED BY <PWD>
    USING 'LISTENER_FCHH';
    Links tested successfully.
    Now "SA" user in Microsoft SQL Server has multiple databases i.e. Master,SecurePerfect,SecurePerfectHistory. when I try following command
    select * from "SecurePerfectHistory.DBO.BadgeHistoryTable"@FCHH
    ORA-00972: identifier is too long

    ORA-00972: identifier is too long
    Cause: An identifier with more than 30 characters was specified.
    Action: Specify at most 30 charactersAman....

  • I have problem to connect oracle DB with SQL developer

    I try connect to my oracle db with oracle SQL developer and received that message:
    http://ioj.com/v/camkp
    (pictures 1 and 2)
    if i try connect with sql plus, all well.
    command : select userenv('LANGUAGE') from dual; result: Connected to: Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
    SQL> select userenv('LANGUAGE') from dual;
    *USERENV('LANGUAGE')
    RUSSIAN_RUSSIA.CL8MSWIN1251*
    in SQL DEVELOPER: (picture 3)
    check\uncheck "Skip NLS Settings", nothing changed.
    what the issue is?

    Then apparently it's still not getting the OS settings right; try to add these to \sqldeveloper\bin\sqldeveloper.conf (maybe region is enough):
    AddVMOption -Duser.language=en
    AddVMOption -Duser.country=US
    AddVMOption -Duser.region=USHope that helps,
    K.

  • Connecting Oracle DB with SQL server

    I need to connect an Oracle Data Base to a SQL Server throught a BPEL process. Somebody knows about a TUTORIAL or maybe other guide.....pls this is urgent.
    Thanks

    Reading you post, I asssume you want to select data from an Oracle database and pass this information to a BPEL processs. This process will store the data into a SQL Server database.
    Create BPEL process, with two partner links, using the DB adapater. One partner link is using the Oracle databas, the other one SQL Server.
    Therefore you must add/change your oc4j-ra.xml, to add an Oracle DB connection and an SQL Server connection: The file can be found at
    $ORACLE_HOME\j2ee\OC4J_BPEL\application-deployments\default\DbAdapter
         <connector-factory location="eis/DB/SampleSQLServerConnection" connector-name="Database Adapter">
              <config-property name="driverClassName" value="com.microsoft.jdbc.sqlserver.SQLServerDriver"/>
              <config-property name="connectionString" value="jdbc:microsoft:sqlserver://localhost\\sql2000:1433;SelectMethod=cursor;databasename=NAME"/>
              <config-property name="userName" value="NAME"/>
              <config-property name="password" value="password"/>
              <config-property name="minConnections" value="5"/>
              <config-property name="maxConnections" value="5"/>
              <config-property name="minReadConnections" value="1"/>
              <config-property name="maxReadConnections" value="1"/>
              <config-property name="usesExternalConnectionPooling" value="false"/>
              <config-property name="dataSourceName" value=""/>
              <config-property name="usesExternalTransactionController" value="false"/>
              <config-property name="platformClassName" value="oracle.toplink.internal.databaseaccess.SQLServerPlatform"/>
              <config-property name="usesNativeSequencing" value="true"/>
              <config-property name="sequencePreallocationSize" value="50"/>
              <config-property name="tableQualifier" value=""/>
              <config-property name="defaultNChar" value="false"/>
              <config-property name="usesBatchWriting" value="true"/>
         </connector-factory>

  • Integrate Oracle IDM with Sql Server 2005

    Hi Guys,
    We maintain the employees information in Oracle IDM and we want to integrate Oracle IDM with Sql server 2005.
    how we can this.

    The DB connector?
    The 9.0.1.4 version supports SQL server 2005.
    The latest version of the GTC db connector might also work.
    Best regards
    /Martin

  • XML parsing problems with Oracle XML parser for PL/SQL

    I am using the Oracle XML parser for PL/SQL to transform XML into HTML usign XSL. The parser gives me sporadic errors trying to parse various XML documents. For the same XML source, the XMLPARSER will parse without errors one day and the next day will give me errors such as "invalid char in text", "Expected ';'.", or even Java null pointer exceptions.
    I have verified that the XML sources are well formed, so I am pretty certain that the problems I am having are bugs in the XMLPARSER.
    Is there going to be a XML parser for PL/SQL version 2 that will fix these bugs? If so, when??? If not, is there anything else I could do to fix these problems?
    Thanks!

    You can use the latest version.

  • 2GB OR NOT 2GB - FILE LIMITS IN ORACLE

    제품 : ORACLE SERVER
    작성날짜 : 2002-04-11
    2GB OR NOT 2GB - FILE LIMITS IN ORACLE
    ======================================
    Introduction
    ~~~~~~~~~~~~
    This article describes "2Gb" issues. It gives information on why 2Gb
    is a magical number and outlines the issues you need to know about if
    you are considering using Oracle with files larger than 2Gb in size.
    It also
    looks at some other file related limits and issues.
    The article has a Unix bias as this is where most of the 2Gb issues
    arise but there is information relevant to other (non-unix)
    platforms.
    Articles giving port specific limits are listed in the last section.
    Topics covered include:
    Why is 2Gb a Special Number ?
    Why use 2Gb+ Datafiles ?
    Export and 2Gb
    SQL*Loader and 2Gb
    Oracle and other 2Gb issues
    Port Specific Information on "Large Files"
    Why is 2Gb a Special Number ?
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Many CPU's and system call interfaces (API's) in use today use a word
    size of 32 bits. This word size imposes limits on many operations.
    In many cases the standard API's for file operations use a 32-bit signed
    word to represent both file size and current position within a file (byte
    displacement). A 'signed' 32bit word uses the top most bit as a sign
    indicator leaving only 31 bits to represent the actual value (positive or
    negative). In hexadecimal the largest positive number that can be
    represented in in 31 bits is 0x7FFFFFFF , which is +2147483647 decimal.
    This is ONE less than 2Gb.
    Files of 2Gb or more are generally known as 'large files'. As one might
    expect problems can start to surface once you try to use the number
    2147483648 or higher in a 32bit environment. To overcome this problem
    recent versions of operating systems have defined new system calls which
    typically use 64-bit addressing for file sizes and offsets. Recent Oracle
    releases make use of these new interfaces but there are a number of issues
    one should be aware of before deciding to use 'large files'.
    What does this mean when using Oracle ?
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    The 32bit issue affects Oracle in a number of ways. In order to use large
    files you need to have:
    1. An operating system that supports 2Gb+ files or raw devices
    2. An operating system which has an API to support I/O on 2Gb+ files
    3. A version of Oracle which uses this API
    Today most platforms support large files and have 64bit APIs for such
    files.
    Releases of Oracle from 7.3 onwards usually make use of these 64bit APIs
    but the situation is very dependent on platform, operating system version
    and the Oracle version. In some cases 'large file' support is present by
    default, while in other cases a special patch may be required.
    At the time of writing there are some tools within Oracle which have not
    been updated to use the new API's, most notably tools like EXPORT and
    SQL*LOADER, but again the exact situation is platform and version specific.
    Why use 2Gb+ Datafiles ?
    ~~~~~~~~~~~~~~~~~~~~~~~~
    In this section we will try to summarise the advantages and disadvantages
    of using "large" files / devices for Oracle datafiles:
    Advantages of files larger than 2Gb:
    On most platforms Oracle7 supports up to 1022 datafiles.
    With files < 2Gb this limits the database size to less than 2044Gb.
    This is not an issue with Oracle8 which supports many more files.
    In reality the maximum database size would be less than 2044Gb due
    to maintaining separate data in separate tablespaces. Some of these
    may be much less than 2Gb in size.
    Less files to manage for smaller databases.
    Less file handle resources required
    Disadvantages of files larger than 2Gb:
    The unit of recovery is larger. A 2Gb file may take between 15 minutes
    and 1 hour to backup / restore depending on the backup media and
    disk speeds. An 8Gb file may take 4 times as long.
    Parallelism of backup / recovery operations may be impacted.
    There may be platform specific limitations - Eg: Asynchronous IO
    operations may be serialised above the 2Gb mark.
    As handling of files above 2Gb may need patches, special configuration
    etc.. there is an increased risk involved as opposed to smaller files.
    Eg: On certain AIX releases Asynchronous IO serialises above 2Gb.
    Important points if using files >= 2Gb
    Check with the OS Vendor to determine if large files are supported
    and how to configure for them.
    Check with the OS Vendor what the maximum file size actually is.
    Check with Oracle support if any patches or limitations apply
    on your platform , OS version and Oracle version.
    Remember to check again if you are considering upgrading either
    Oracle or the OS in case any patches are required in the release
    you are moving to.
    Make sure any operating system limits are set correctly to allow
    access to large files for all users.
    Make sure any backup scripts can also cope with large files.
    Note that there is still a limit to the maximum file size you
    can use for datafiles above 2Gb in size. The exact limit depends
    on the DB_BLOCK_SIZE of the database and the platform. On most
    platforms (Unix, NT, VMS) the limit on file size is around
    4194302*DB_BLOCK_SIZE.
    Important notes generally
    Be careful when allowing files to automatically resize. It is
    sensible to always limit the MAXSIZE for AUTOEXTEND files to less
    than 2Gb if not using 'large files', and to a sensible limit
    otherwise. Note that due to <Bug:568232> it is possible to specify
    an value of MAXSIZE larger than Oracle can cope with which may
    result in internal errors after the resize occurs. (Errors
    typically include ORA-600 [3292])
    On many platforms Oracle datafiles have an additional header
    block at the start of the file so creating a file of 2Gb actually
    requires slightly more than 2Gb of disk space. On Unix platforms
    the additional header for datafiles is usually DB_BLOCK_SIZE bytes
    but may be larger when creating datafiles on raw devices.
    2Gb related Oracle Errors:
    These are a few of the errors which may occur when a 2Gb limit
    is present. They are not in any particular order.
    ORA-01119 Error in creating datafile xxxx
    ORA-27044 unable to write header block of file
    SVR4 Error: 22: Invalid argument
    ORA-19502 write error on file 'filename', blockno x (blocksize=nn)
    ORA-27070 skgfdisp: async read/write failed
    ORA-02237 invalid file size
    KCF:write/open error dba=xxxxxx block=xxxx online=xxxx file=xxxxxxxx
    file limit exceed.
    Unix error 27, EFBIG
    Export and 2Gb
    ~~~~~~~~~~~~~~
    2Gb Export File Size
    ~~~~~~~~~~~~~~~~~~~~
    At the time of writing most versions of export use the default file
    open API when creating an export file. This means that on many platforms
    it is impossible to export a file of 2Gb or larger to a file system file.
    There are several options available to overcome 2Gb file limits with
    export such as:
    - It is generally possible to write an export > 2Gb to a raw device.
    Obviously the raw device has to be large enough to fit the entire
    export into it.
    - By exporting to a named pipe (on Unix) one can compress, zip or
    split up the output.
    See: "Quick Reference to Exporting >2Gb on Unix" <Note:30528.1>
    - One can export to tape (on most platforms)
    See "Exporting to tape on Unix systems" <Note:30428.1>
    (This article also describes in detail how to export to
    a unix pipe, remote shell etc..)
    Other 2Gb Export Issues
    ~~~~~~~~~~~~~~~~~~~~~~~
    Oracle has a maximum extent size of 2Gb. Unfortunately there is a problem
    with EXPORT on many releases of Oracle such that if you export a large table
    and specify COMPRESS=Y then it is possible for the NEXT storage clause
    of the statement in the EXPORT file to contain a size above 2Gb. This
    will cause import to fail even if IGNORE=Y is specified at import time.
    This issue is reported in <Bug:708790> and is alerted in <Note:62436.1>
    An export will typically report errors like this when it hits a 2Gb
    limit:
    . . exporting table BIGEXPORT
    EXP-00015: error on row 10660 of table BIGEXPORT,
    column MYCOL, datatype 96
    EXP-00002: error in writing to export file
    EXP-00002: error in writing to export file
    EXP-00000: Export terminated unsuccessfully
    There is a secondary issue reported in <Bug:185855> which indicates that
    a full database export generates a CREATE TABLESPACE command with the
    file size specified in BYTES. If the filesize is above 2Gb this may
    cause an ORA-2237 error when attempting to create the file on IMPORT.
    This issue can be worked around be creating the tablespace prior to
    importing by specifying the file size in 'M' instead of in bytes.
    <Bug:490837> indicates a similar problem.
    Export to Tape
    ~~~~~~~~~~~~~~
    The VOLSIZE parameter for export is limited to values less that 4Gb.
    On some platforms may be only 2Gb.
    This is corrected in Oracle 8i. <Bug:490190> describes this problem.
    SQL*Loader and 2Gb
    ~~~~~~~~~~~~~~~~~~
    Typically SQL*Loader will error when it attempts to open an input
    file larger than 2Gb with an error of the form:
    SQL*Loader-500: Unable to open file (bigfile.dat)
    SVR4 Error: 79: Value too large for defined data type
    The examples in <Note:30528.1> can be modified to for use with SQL*Loader
    for large input data files.
    Oracle 8.0.6 provides large file support for discard and log files in
    SQL*Loader but the maximum input data file size still varies between
    platforms. See <Bug:948460> for details of the input file limit.
    <Bug:749600> covers the maximum discard file size.
    Oracle and other 2Gb issues
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~
    This sections lists miscellaneous 2Gb issues:
    - From Oracle 8.0.5 onwards 64bit releases are available on most platforms.
    An extract from the 8.0.5 README file introduces these - see <Note:62252.1>
    - DBV (the database verification file program) may not be able to scan
    datafiles larger than 2Gb reporting "DBV-100".
    This is reported in <Bug:710888>
    - "DATAFILE ... SIZE xxxxxx" clauses of SQL commands in Oracle must be
    specified in 'M' or 'K' to create files larger than 2Gb otherwise the
    error "ORA-02237: invalid file size" is reported. This is documented
    in <Bug:185855>.
    - Tablespace quotas cannot exceed 2Gb on releases before Oracle 7.3.4.
    Eg: ALTER USER <username> QUOTA 2500M ON <tablespacename>
    reports
    ORA-2187: invalid quota specification.
    This is documented in <Bug:425831>.
    The workaround is to grant users UNLIMITED TABLESPACE privilege if they
    need a quota above 2Gb.
    - Tools which spool output may error if the spool file reaches 2Gb in size.
    Eg: sqlplus spool output.
    - Certain 'core' functions in Oracle tools do not support large files -
    See <Bug:749600> which is fixed in Oracle 8.0.6 and 8.1.6.
    Note that this fix is NOT in Oracle 8.1.5 nor in any patch set.
    Even with this fix there may still be large file restrictions as not
    all code uses these 'core' functions.
    Note though that <Bug:749600> covers CORE functions - some areas of code
    may still have problems.
    Eg: CORE is not used for SQL*Loader input file I/O
    - The UTL_FILE package uses the 'core' functions mentioned above and so is
    limited by 2Gb restrictions Oracle releases which do not contain this fix.
    <Package:UTL_FILE> is a PL/SQL package which allows file IO from within
    PL/SQL.
    Port Specific Information on "Large Files"
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Below are references to information on large file support for specific
    platforms. Although every effort is made to keep the information in
    these articles up-to-date it is still advisable to carefully test any
    operation which reads or writes from / to large files:
    Platform See
    ~~~~~~~~ ~~~
    AIX (RS6000 / SP) <Note:60888.1>
    HP <Note:62407.1>
    Digital Unix <Note:62426.1>
    Sequent PTX <Note:62415.1>
    Sun Solaris <Note:62409.1>
    Windows NT Maximum 4Gb files on FAT
    Theoretical 16Tb on NTFS
    ** See <Note:67421.1> before using large files
    on NT with Oracle8
    *2 There is a problem with DBVERIFY on 8.1.6
    See <Bug:1372172>

    I'm not aware of a packaged PL/SQL solution for this in Oracle 8.1.7.3 - however it is very easy to create such a program...
    Step 1
    Write a simple Java program like the one listed:
    import java.io.File;
    public class fileCheckUtl {
    public static int fileExists(String FileName) {
    File x = new File(FileName);
    if (x.exists())
    return 1;
    else return 0;
    public static void main (String args[]) {
    fileCheckUtl f = new fileCheckUtl();
    int i;
    i = f.fileExists(args[0]);
    System.out.println(i);
    Step 2 Load this into the Oracle data using LoadJava
    loadjava -verbose -resolve -user user/pw@db fileCheckUtl.java
    The output should be something like this:
    creating : source fileCheckUtl
    loading : source fileCheckUtl
    creating : fileCheckUtl
    resolving: source fileCheckUtl
    Step 3 - Create a PL/SQL wrapper for the Java Class:
    CREATE OR REPLACE FUNCTION FILE_CHECK_UTL (file_name IN VARCHAR2) RETURN NUMBER AS
    LANGUAGE JAVA
    NAME 'fileCheckUtl.fileExists(java.lang.String) return int';
    Step 4 Test it:
    SQL> select file_check_utl('f:\myjava\fileCheckUtl.java') from dual
    2 /
    FILE_CHECK_UTL('F:\MYJAVA\FILECHECKUTL.JAVA')
    1

Maybe you are looking for

  • Material return to vendor ( line rejection)

    Dear MM gurus, i have a scenario where material received is accepted at the time of Quality inspection. Same material issued to production but if found faulty has to be returned to vendor. Such line rejection occur daily and at the end of the weak re

  • Difference between 2 date variables

    I have a query that selects data based on : WHERE START_DATE >= &BEGIN AND start_date <= &END I need to find the difference between these 2 dates in order to use the result in a calculation in the totals area in a rtf I have, but don't know how to do

  • Configurations required for sender/ reciever mail adapter scenario...

    Hi, I have to work on few mail scenario's i.e, sender and reciever. Please let me know what all configurations are required in XI server to make the system ready to send and recieve mail like SMTP configurations... Thanks..

  • Error 403 when editing report in report builder

    Hey Guys, I have a weird issue with the SSRS (Sharepoint Server Reporting Services), which I find very undocumented hence not so easy to implement in a multi-server farm. Anyway, I have a very small 2 servers SP farm running SP2013 Enterprise and Pro

  • Switching to Icloud with Iphoto 6

    My MacBook (from 2007) has Iphoto 6 on it - can I switch to Icloud? (the photos on my MobileMe are not already in Iphoto due to a system crash)