Varchar2 length
Hi All
I want to know the maximom length of varchar2 variable in formbuilder 6i .
In its Help it was said max 2000 character.
but in report builder the width of a user parameter could be 1 through 64K.
64k=64*1024 byte=65536 byte ---> 65536 char
So i 'd like to pass a parameter from formbuilder to the report with width=8000 character
Is it possible?
Am i wrong?
Thanks in advance.
Ahmad,
actually i searched the online help for Reports9i and couldn't find it in there. All I could find is a maximum field length that can be 64k. However, teh length of the parameters you pass to reports depends on how you pass them. If e.g. using web.show_document() built-in in Forms to pass teh command, then you are limited to 255 characters at all (limitation of a GET request). I didn't stree run_reports_object too much, but think that 8000 characters is far to long and that a cmd file should be used instead. I suggest to give it a try and test 8000 characters.
Frank
Similar Messages
-
Performance impact due to varchar2 length
hi,
We know varchar2 stores data dynamically. means it takes storage space only for the data it has. Then what is the requirement of defining varchar2 length. It shd be default to 4000. Pls take data consistency /security/maintenence etc fundas as another issue.
Take an e.g
Is there any other performance/storage/etc impact of given table designs ?
SQL>Create table T1
(sex varchar2(1));
SQL>Create table T2
(sex varchar2(4000));
SQL>Insert into T1 values('M');
SQL>Insert into T2 values('M');
SQL>select * from t1;
s
M
SQL>select * from t2;
sex
M
Is there any other performance/storage/etc impact of given table designs ?
Any comments.... ?
Rgds,
RupWell Pls chk this explain plan.
SQL> desc test1;
Name Null? Type
A1 VARCHAR2(1)
A2 VARCHAR2(1)
A3 VARCHAR2(1)
A4 VARCHAR2(1)
A5 VARCHAR2(1)
A6 VARCHAR2(1)
A7 VARCHAR2(1)
A8 VARCHAR2(1)
A9 VARCHAR2(1)
A10 VARCHAR2(1)
A11 VARCHAR2(1)
A12 VARCHAR2(1)
A14 VARCHAR2(1)
A15 VARCHAR2(1)
SQL> desc test2;
Name Null? Type
A1 VARCHAR2(4000)
A2 VARCHAR2(4000)
A3 VARCHAR2(4000)
A4 VARCHAR2(4000)
A5 VARCHAR2(4000)
A6 VARCHAR2(4000)
A7 VARCHAR2(4000)
A8 VARCHAR2(4000)
A9 VARCHAR2(4000)
A10 VARCHAR2(4000)
A11 VARCHAR2(4000)
A12 VARCHAR2(4000)
A13 VARCHAR2(4000)
A14 VARCHAR2(4000)
SQL> set autotrace on
SQL> select a1 from test1 where rownum<=1;
A
a
Execution Plan
0 SELECT STATEMENT Optimizer=ALL_ROWS (Cost=2 Card=1 Bytes=2)
1 0 COUNT (STOPKEY)
2 1 TABLE ACCESS (FULL) OF 'TEST1' (TABLE) (Cost=2 Card=80 Bytes=160)
SQL> select a1 from test2 where rownum<=1;
A1
a
Execution Plan
0 SELECT STATEMENT Optimizer=ALL_ROWS (Cost=2 Card=1 Bytes=2002)
1 0 COUNT (STOPKEY)
2 1 TABLE ACCESS (FULL) OF 'TEST2' (TABLE) (Cost=2 Card=80 Bytes=160160)
what is this??? Explain plan has major difference in the Bytes accessed field.
Is this a major performance issue...
Rgds, -
HS VIEW Incorrect Datatype VARCHAR2 Lengths Object Type
Hello,
One more question please.
I created a view in Oracle10gr2 to which pulls from an HS ODBC using a database link.
The problem is that the source database sets a particular column to VARCHAR2 (100) for a length, however the view when pulled only displays VARCHAR2(56).
Which is the actual length of the longest row of data for that column.
So this will be a problem if a row is inserted that is longer than (56) and I query the same view, I assume it will truncate.
Rather than creating an Object View and setting the lengths explicity, then calling the Object View from the View, as shown below. Is there a setting to force the view to use the columns constraints from the source??
Example using the Object View:
Creating an Object View: Example The following example shows the creation of the type inventory_typ in the oc schema, and the oc_inventories view that is based on that type:
CREATE TYPE inventory_typ
OID '82A4AF6A4CD4656DE034080020E0EE3D'
AS OBJECT
( product_id NUMBER(6)
, warehouse warehouse_typ
, quantity_on_hand NUMBER(8)
CREATE OR REPLACE VIEW oc_inventories OF inventory_typ
WITH OBJECT OID (product_id)
AS SELECT i.product_id,
warehouse_typ(w.warehouse_id, w.warehouse_name, w.location_id),
i.quantity_on_hand
FROM inventories i, warehouses w
WHERE i.warehouse_id=w.warehouse_id;
Any suggestions are appreciated.
ThanksI'm not sure if it is really a good idea to store time information in a string (And why is this string 16 chars long?)
But anyway here is a sample that worked for me:
create or replace type hour as object(
hhmmss varchar2(16),
member function HourToSysdate return date
create or replace type body hour as
member function HourToSysdate return date is
begin
return to_date(to_char(sysdate, 'dd/mm/yyyy') || ' ' || self.hhmmss , 'dd/mm/yyyy hh24:mi:ss');
end HourToSysdate;
end;
create table labor (
id number,
hora hour
insert into labor values(1, hour('12:13:14'));
insert into labor values(2, hour('09:10:11'));
select id, to_char(hour.hourtosysdate(hora), 'DD.MM.YYYY HH24:MI:SS')
from labor
order by id;
or
select l.id, to_char(l.hora.hourtosysdate(), 'DD.MM.YYYY HH24:MI:SS')
from labor l
order by l.id; -
How to perform Text length more than 4000 bytes
I want to read each row from txt file
and used utl_file pacage to concat contents into a variable,
the variable datatype is varchar2(4000), so text length can't more than 4000 bytes,
but I wish get full text from txt file, How can I do?Thans! Detlev.
I have a code :
PROCEDURE read_file( path in varchar2, filename in varchar2, msg in out varchar2) AS
data_line varchar2(4000);
ifile utl_file.file_type;
BEGIN
ifile := utl_file.fopen(path,filename,'R');
LOOP
utl_file.get_line( ifile, data_line);
msg := msg | | rtrim(data_line);
END LOOP;
utl_file.fclose(ifile);
EXCEPTION
WHEN no_data_found THEN
utl_file.fclose(ifile);
END;
My question is
1. The msg length can't more than 4000
2. I use utl_raw.cast_to_raw function, that can't cast varchar2 to raw if varchar2 length more than 2048
3. If I want to change the data type varchar2 to raw,
the utl_raw.concat function can't use Loop ....end loop clause,
So that only use utl_raw.concat(ra1, ra2,ra3,ra4,ra5, ... ra12)
I want to concat all line to a raw datatype from text file , How can I do? -
Can not display long derived measure - ORA-33674
I would need calculated measures for compiling some special URL, but there seems to be now way to have results longer than 60 characters. I tried creating the measure using AWM and using OLAP API. Both will result in:
ORA-33674: Data block exceeds the maximum size of 60 bytes.
... so its not possible to view the auto-generated view any more. The whole thing seems to be similar to this [Cannot view dimension if description is more than 60 characters|http://wiki.oracle.com/thread/2121955/Cannot+View+Dimension+If+Description+Is+More+Than+60+Characters]
But here it is about DerivedMeasures, so the workaround is not applicable. There is no corresponding option. Unfortunate this has not been fixed by BugFix 6940809 as described in [AWM 11.1.0.7.0B Readme|http://www.oracle.com/technology/products/bi/olap/11g/awm/awm11.1.0.7b_readme.html]
I also tired to create the DerivedMeasure via OLAP API and casting it an CLOB. No success either, different Error.
MdmDerivedMeasure msTemp = mdmCube.findOrCreateDerivedMeasure("TEST");
StringExpression strexTemp = new StringExpression("Toooooooooooooooo Loooooooooooooooooooooong Txxxxxxxxxxxxxxxxxxt");
+msTemp.setMeasureExpression( strexTemp.toCLOB() );+
Exception in thread "main" Die Transaktion kann nicht festgeschrieben werden: "Auf dem Server ist ein Fehler aufgetreten
Fehlerklasse: Express-Fehler
Server-Fehlerbeschreibungen:
DPR: Server-Cursor kann nicht erstellt werden, Allgemein in TxsOqDefinitionManager::generic<CommitRoot>
+INI: XOQ-01600: OLAP DML-Fehler "Analytisches Arbeitsbereichsobjekt TO_CLOB ist nicht vorhanden." bei der Ausführung von DML "SYS.AWXML!R11_MANAGE_CALC_MEASURE('SALES_CUBE.URImdm.MEASURE' 'ALTER' 'TEXT' SYS.AWXML!___R11_LONG_ARG_VALUE(SYS.AWXML!___R11_LONG_ARG_DIM 1) NA NA)", Allgemein in TxsOqStdFormCommand::execute"+
+ at oracle.olapi.transaction.BaseTransaction.commit(Unknown Source)+
+ at oracle.olapi.transaction.BaseTransactionProvider.commitCurrentTransaction(Unknown Source)+
+ at daemz.eval.createExpression.main(createExpression.java:103)+
Translating from German: While writing to the DB he finds out he doesn't actually have some object called TO_CLOB. Does they API offer functionality not supported by the DB?
Played around with this for quite a while - suggestions more than welcome.
I'm evaluating on the OLAP Option, using AWM 11.1.0.7.0B, Oracel DB & OLAP 11.1.0.7.0, OLAP API 11.1.0.6.0 (delivered with AWM 11.1.0.7.B) and the Oracle OLAP 11g Sample Schema.
Edited by: user7008111 on Jun 27, 2009 11:27 AM
Edited by: user7008111 on Jun 27, 2009 11:27 AMThis is similar, bot not quite the same problem as for attributes. In the case of attributes, the problem was bad defaulting of the VARCHAR2 length by AWM. To fix it is was just necessary to give an appropriate length.
Your issue is more serious since it lies in the server itself, which attempts (badly in this case) to derive the data type from the expression. In this it determines that the data type is VARCHAR2, but it defaults the data length to 60 instead of deriving the length from the contents. I am not aware of any workarounds in 11.1.0.7 for this problem. CAST, for example, does not solve the problem. The bug is addressed in 11.2 beta releases, but it was a non-trivial project that is no likely to be back ported to 11.1.0.7. It may be possible to bump up the default of 60 to something higher, but this is not a general solution.
The TO_CLOB error is due to the fact that the CLOB data type (and hence TO_CLOB function) is not supported by the AW. It is supported by relational tables, which is why it is listed in the OLAP API. It can be used, for example, in the mapping between cube and table as long as you resolve the CLOB into an AW data type again. -
Discoverer with OWB generated EULs
i configure my warehouse star schema using OWB (warehouse builder 9i release 2) and generated the EUL. the were some warnings but they were pointing to some invalid characters in the names of the objects but the import succeeded.
i could see all the imported definition from OWB using Discoverer Admin (also iDS Release 2 - EUL version 5).
sample of my star schema:-
fact table
salesman_id
product_id
sales_amt
dimension
salesman (which also contains salesman name attribute)
product (which also contains product description attribute)
so, i can see the Discoverer joins from the fact to the dimension tables.
when i create a workbook (report) using Discoverer Desktop, i faced the following problems:-
if i just have Salesman (ID or Description) as a row, everything is fine.
if i add in the Product ID, it still works as per normal.
but when i add Product Description into the report, i experienced a weird behaviour. somehow, the Salesman ID field will be automatically filtered to show only a certain number of records in the result (less than what it initially was) !
usually if you put field in the Page Items section you will have to select to view <All> records, right ? citing the scenario i just mentioned above, i will only see some record values ... i won't see the <All> displayed for me to choose.
has this got to do with the foreign key relationship from the Fact table's Product ID field to the Product Dimension table ? it worked for the Salesman dimension !!
the only thing different about the product dimension is the product id field is VARCHAR2 length 18. you could have numeric values like 000000000012345678 (numbers are padded with zeros to make up 18 chars) and alphanumeric values like MAT_TG12345 (which are not padded with anything - left-justified). i could set that the report would only retrieve the records which has product id matching the numeric values !
any ideas ?
thanks to anyone who is kind enough to read this lengthy post and reply it :)It would appear that you do not have integrity between the fact and the product dimension.
Does the foriegn key exisit in the database (deployed) or is it only in the OWB repository (not deployed).
Two thing:-
Try changin the join to an outer join.
Take the sql from the View SQL drop down option and run in another SQL Editor.
Neil -
Calling a Stored Procedure with output parameters from Query Templates
This is same problem which Shalaka Khandekar logged earlier. This new thread gives the complete description about our problem. Please go through this problem and suggest us a feasible solution.
We encountered a problem while calling a stored procedure from MII Query Template as follows-
1. Stored Procedure is defined in a package. Procedure takes the below inputs and outputs.
a) Input1 - CLOB
b) Input2 - CLOB
c) Input3 - CLOB
d) Output1 - CLOB
e) Output2 - CLOB
f) Output3 - Varchar2
2. There are two ways to get the output back.
a) Using a Stored Procedure by declaring necessary OUT parameters.
b) Using a Function which returns a single value.
3. Consider we are using method 2-a. To call a Stored Procedure with OUT parameters from the Query Template we need to declare variables of
corresponding types and pass them to the Stored Procedure along with the necessary input parameters.
4. This method is not a solution to get output because we cannot declare variables of some type(CLOB, Varchar2) in Query Template.
5. Even though we are successful (step 4) in declaring the OUT variables in Query Template and passed it successfully to the procedure, but our procedure contains outputs which are of type CLOB. It means we are going to get data which is more than VARCHAR2 length which query template cannot return(Limit is 32767
characters)
6. So the method 2-a is ruled out.
7. Now consider method 2-b. Function returns only one value, but we have 3 different OUT values. Assume that we have appended them using a separator. This value is going to be more than 32767 characters which is again a problem with the query template(refer to point 5). So option 2-b is also ruled out.
Apart from above mentioned methods there is a work around. It is to create a temporary table in the database with above 3 OUT parameters along with a session specific column. We insert the output which we got from the procedure to the temporary table and use it further. As soon the usage of the data is completed we delete the current session specific data. So indirectly we call the table as a Session Table. This solution increases unnecessary load on the database.
Thanks in Advance.
RajeshRajesh,
please check if this following proposal could serve you.
Define the Query with mode FixedQueryWithOutput. In the package define a ref cursor as IN OUT parameter. To get your 3 values back, open the cursor in your procedure like "Select val1, val2, val3 from dual". Then the values should get into your query.
Here is an example how this could be defined.
Package:
type return_cur IS ref CURSOR;
Procedure:
PROCEDURE myProc(myReturnCur IN OUT return_cur) ...
OPEN myReturnCur FOR SELECT val1, val2, val3 FROM dual;
Query:
DECLARE
MYRETURNCUR myPackage.return_cur;
BEGIN
myPackage.myProc(
MYRETURNCUR => ?
END;
Good luck.
Michael -
Nullpointer exception while multiple users reading from XML DOM object
We are getting a null pointer exception when we are trying to read from a Static XML DOM object . We are getting the exception in weblogic 7.1 very rarely but started getting the exception in weblogic 9.2 more frequently. When multiple users are trying to access the Static variable we are getting null pointer exception. I think it is a memory related issue. Making the whole method synchronized is resolving the issue. But that is not the right thing to do. Can any one know what might be the issue here?
I am giving the code and the XML. I have tried to give the latest Xerces parser from the Apache site but got the same exception. Please help me in this regard.
The XML is also provided below along with the code.
package com.test;
import java.beans.BeanInfo;
import java.beans.Introspector;
import java.util.ArrayList;
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.DocumentBuilderFactory;
//import org.apache.xml.serialize.XMLSerializer;
import org.w3c.dom.Document;
import org.w3c.dom.Node;
import org.w3c.dom.NodeList;
public class ObjectPersistanceXMLParser {
public static volatile Document configXML;
* @param objectName
* @param attributeName
* @return
* @throws Throwable
public static ArrayList getData(String objectName,String attributeName) throws Exception
Node ndDoc = getXMLDoc();
Node ndRoot = ndDoc.getFirstChild();
NodeList ndFirstList = ndRoot.getChildNodes();
BeanInfo bi = Introspector.getBeanInfo(ndFirstList.getClass());
System.out.println("****** "+bi.getBeanDescriptor().getBeanClass().getName());
System.out.println("This is the number of child nodes present:"+ndFirstList.getLength()+":::"+ndFirstList.item(0).getNodeValue());
ArrayList returnResult = null;
String strReturnResult = null;
for(int i=0;i<ndFirstList.getLength();i++)
if(ndFirstList.item(i).getNodeName().equals("ObjectDBMapping"))
NodeList ndObjectList = ndFirstList.item(i).getChildNodes();
for(int j=0;j<ndObjectList.getLength();j++)
if(ndObjectList.item(j).getNodeName().equals("Object"))
if(ndObjectList.item(j).getAttributes().getNamedItem("NAME").getNodeValue().equalsIgnoreCase(objectName))
NodeList ndFieldList = ndObjectList.item(j).getChildNodes();
for(int k=0;k<ndFieldList.getLength();k++)
if(ndFieldList.item(k).getNodeName().equals("field"))
if(ndFieldList.item(k).getAttributes().getNamedItem("NAME").getNodeValue().equalsIgnoreCase(attributeName))
returnResult = new ArrayList();
returnResult.add(ndFieldList.item(k).getAttributes().getNamedItem("SOURCE_TABLE").getNodeValue());
returnResult.add(ndFieldList.item(k).getAttributes().getNamedItem("SOURCE_COLUMN").getNodeValue());
returnResult.add(ndFieldList.item(k).getAttributes().getNamedItem("TYPE").getNodeValue());
returnResult.add(ndFieldList.item(k).getAttributes().getNamedItem("PERSIST").getNodeValue());
returnResult.add(ndFieldList.item(k).getAttributes().getNamedItem("DEFAULT_VALUE").getNodeValue());
returnResult.add(ndFieldList.item(k).getAttributes().getNamedItem("PRIMARY_KEY").getNodeValue());
returnResult.add(ndFieldList.item(k).getAttributes().getNamedItem("VERSIONABLE").getNodeValue());
returnResult.add(ndFieldList.item(k).getAttributes().getNamedItem("PRECISION").getNodeValue());
returnResult.add(ndFieldList.item(k).getAttributes().getNamedItem("FOREIGN_KEY").getNodeValue());
returnResult.add(ndFieldList.item(k).getAttributes().getNamedItem("PARENT_TABLE").getNodeValue());
returnResult.add(ndFieldList.item(k).getAttributes().getNamedItem("PARENT_COLUMN").getNodeValue());
returnResult.add(ndFieldList.item(k).getAttributes().getNamedItem("LEVEL").getNodeValue());
//return returnResult;
if(strReturnResult == null){
System.out.println("This is the current state of dom: ");
//printDom((Document)ndDoc);
if(!attributeName.trim().equalsIgnoreCase("class") &&
!attributeName.trim().equalsIgnoreCase("operationFlag")&&
!attributeName.trim().equalsIgnoreCase("primaryKeyColumnName")&&
!attributeName.trim().equalsIgnoreCase("tableName"))
System.out.println("No DB Mapping found for Object "+objectName+" and attribute "+attributeName);
return returnResult;
* @param objectName
* @param tableName
* @return
* @throws Throwable
public static int getMaxFields(String objectName,String tableName) throws Throwable
Node ndDoc = getXMLDoc();
Node ndRoot = ndDoc.getFirstChild();
NodeList ndFirstList = ndRoot.getChildNodes();
int returnResult = 0;
for(int i=0;i<ndFirstList.getLength();i++)
if(ndFirstList.item(i).getNodeName().equals("ObjectDBMapping"))
NodeList ndObjectList = ndFirstList.item(i).getChildNodes();
for(int j=0;j<ndObjectList.getLength();j++)
if(ndObjectList.item(j).getNodeName().equals("Object"))
if(ndObjectList.item(j).getAttributes().getNamedItem("NAME").getNodeValue().equalsIgnoreCase(objectName))
NodeList ndFieldList = ndObjectList.item(j).getChildNodes();
for(int k=0;k<ndFieldList.getLength();k++)
if(ndFieldList.item(k).getNodeName().equals("field"))
if(ndFieldList.item(k).getAttributes().getNamedItem("SOURCE_TABLE").getNodeValue().equalsIgnoreCase(tableName) &&
ndFieldList.item(k).getAttributes().getNamedItem("PERSIST").getNodeValue().equalsIgnoreCase("Y"))
returnResult++;
return returnResult;
/*This method returns a Document Object of the ObjectConfig.xml file. This method is separated
* out from the calling method to keep an option OPEN in case it is later decided to read XML
* from memory instead of physical location.*/
public static Document getXMLDoc() throws Exception
if(configXML == null)
synchronized (ObjectPersistanceXMLParser.class)
if(configXML == null)
if(System.getProperty("OBJECT-CONFIG-XML") == null){
System.out.println("System Property OBJECT-CONFIG-XML not found");
String filePath = System.getProperty("OBJECT-CONFIG-XML");
System.out.println("Reading CONFIG Xml from file - "+filePath);
DocumentBuilderFactory docBuilderFactory = DocumentBuilderFactory.newInstance();
BeanInfo bi = Introspector.getBeanInfo(docBuilderFactory.getClass());
System.out.println("****** "+bi.getBeanDescriptor().getBeanClass().getName());
try
DocumentBuilder docBuilder = docBuilderFactory.newDocumentBuilder();
configXML = docBuilder.parse(filePath);
}catch(Throwable t)
int errorCode = 111;
String errorMsg = "Problem in parsing OBJECT-CONFIG-XML file";
System.out.println(errorMsg);
else
System.out.println("Config XML Loaded from memory.....new");
return configXML;
public static void main(String args[]) throws Throwable
/*public synchronized static void printDom(Document doc){
XMLSerializer ser = new XMLSerializer(System.out, null);
try {
ser.serialize(doc);
} catch (Throwable e) {
e.printStackTrace();
System.out.flush();
<?xml version="1.0"?><root>
<ObjectDBMapping>
<Object NAME="com.los.common.entity.LoanTask">
<field NAME="loanTaskId" SOURCE_TABLE="UW_LOAN_TASKS"
SOURCE_COLUMN="LOAN_TASK_ID" TYPE="NUMBER" LENGTH="20"
PRECISION="" PERSIST="Y" LEVEL="1" DEFAULT_VALUE="" PRIMARY_KEY="Y"
VERSIONABLE="Y" FOREIGN_KEY="N" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="taskId" SOURCE_TABLE="UW_LOAN_TASKS"
SOURCE_COLUMN="TASK_ID" TYPE="NUMBER" LENGTH="20"
PRECISION="" PERSIST="Y" LEVEL="1" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="Y" PARENT_TABLE="UWM_TASK_MASTER" PARENT_COLUMN="TASK_ID">
</field>
<field NAME="taskName" SOURCE_TABLE="UW_LOAN_TASKS"
SOURCE_COLUMN="TASK_NAME" TYPE="VARCHAR2" LENGTH="100"
PRECISION="" PERSIST="Y" LEVEL="1" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="taskStatus" SOURCE_TABLE="UW_LOAN_TASKS"
SOURCE_COLUMN="TASK_STATUS" TYPE="VARCHAR2" LENGTH="20"
PRECISION="" PERSIST="Y" LEVEL="1" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="taskCreationDate" SOURCE_TABLE="UW_LOAN_TASKS"
SOURCE_COLUMN="TASK_CREATION_DATE" TYPE="DATE" LENGTH=""
PRECISION="" PERSIST="Y" LEVEL="1" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="taskClosureDate" SOURCE_TABLE="UW_LOAN_TASKS"
SOURCE_COLUMN="TASK_CLOSURE_DATE" TYPE="DATE" LENGTH=""
PRECISION="" PERSIST="Y" LEVEL="1" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="taskClosedBy" SOURCE_TABLE="UW_LOAN_TASKS"
SOURCE_COLUMN="TASK_CLOSED_BY" TYPE="VARCHAR2" LENGTH="20"
PRECISION="" PERSIST="Y" LEVEL="1" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="updatedDate" SOURCE_TABLE="UW_LOAN_TASKS"
SOURCE_COLUMN="UPDATED_DATE" TYPE="DATE" LENGTH=""
PRECISION="" PERSIST="Y" LEVEL="1" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="updatedBy" SOURCE_TABLE="UW_LOAN_TASKS"
SOURCE_COLUMN="UPDATED_BY" TYPE="VARCHAR2" LENGTH="20"
PRECISION="" PERSIST="Y" LEVEL="1" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="createdDate" SOURCE_TABLE="UW_LOAN_TASKS"
SOURCE_COLUMN="CREATED_DATE" TYPE="DATE" LENGTH=""
PRECISION="" PERSIST="Y" LEVEL="1" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="createdBy" SOURCE_TABLE="UW_LOAN_TASKS"
SOURCE_COLUMN="CREATED_BY" TYPE="VARCHAR2" LENGTH="20"
PRECISION="" PERSIST="Y" LEVEL="1" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
</Object>
<Object NAME="com.los.common.entity.LOSUnderwritingRules">
<field NAME="undwRunRuleId" SOURCE_TABLE="UW_UNDERWRITING_RULES"
SOURCE_COLUMN="UNDW_RUN_RULE_ID" TYPE="NUMBER" LENGTH="20"
PRECISION="" PERSIST="Y" LEVEL="1" DEFAULT_VALUE="" PRIMARY_KEY="Y"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="underwritingRunNo" SOURCE_TABLE="UW_UNDERWRITING_RULES"
SOURCE_COLUMN="UNDERWRITING_RUN_NO" TYPE="NUMBER" LENGTH="20"
PRECISION="" PERSIST="Y" LEVEL="1" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="underwritingRunId" SOURCE_TABLE="UW_UNDERWRITING_RULES"
SOURCE_COLUMN="UNDERWRITING_RUN_ID" TYPE="NUMBER" LENGTH="20"
PRECISION="" PERSIST="Y" LEVEL="1" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="ruleGroup" SOURCE_TABLE="UW_UNDERWRITING_RULES"
SOURCE_COLUMN="RULE_GROUP" TYPE="VARCHAR2" LENGTH="20"
PRECISION="" PERSIST="Y" LEVEL="1" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="ruleName" SOURCE_TABLE="UW_UNDERWRITING_RULES"
SOURCE_COLUMN="RULE_NAME" TYPE="VARCHAR2" LENGTH="20"
PRECISION="" PERSIST="Y" LEVEL="1" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="messageCode" SOURCE_TABLE="UW_UNDERWRITING_RULES"
SOURCE_COLUMN="MESSAGE_CODE" TYPE="VARCHAR2" LENGTH="20"
PRECISION="" PERSIST="Y" LEVEL="1" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="messageText" SOURCE_TABLE="UW_UNDERWRITING_RULES"
SOURCE_COLUMN="MESSAGE_TEXT" TYPE="VARCHAR2" LENGTH="20"
PRECISION="" PERSIST="Y" LEVEL="1" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="passFail" SOURCE_TABLE="UW_UNDERWRITING_RULES"
SOURCE_COLUMN="PASS_FAIL" TYPE="VARCHAR2" LENGTH="20"
PRECISION="" PERSIST="Y" LEVEL="1" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="overrideAuthorityLevel" SOURCE_TABLE="UW_UNDERWRITING_RULES"
SOURCE_COLUMN="OVERRIDE_AUTHORITY_LEVEL" TYPE="VARCHAR2" LENGTH="20"
PRECISION="" PERSIST="Y" LEVEL="1" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="overrideYN" SOURCE_TABLE="UW_UNDERWRITING_RULES"
SOURCE_COLUMN="OVERRIDE_Y_N" TYPE="VARCHAR2" LENGTH="20"
PRECISION="" PERSIST="Y" LEVEL="1" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="overrideBy" SOURCE_TABLE="UW_UNDERWRITING_RULES"
SOURCE_COLUMN="OVERRIDE_BY" TYPE="VARCHAR2" LENGTH="20"
PRECISION="" PERSIST="Y" LEVEL="1" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="overrideOn" SOURCE_TABLE="UW_UNDERWRITING_RULES"
SOURCE_COLUMN="OVERRIDE_ON" TYPE="DATE" LENGTH=""
PRECISION="" PERSIST="Y" LEVEL="1" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="createdBy" SOURCE_TABLE="UW_UNDERWRITING_RULES"
SOURCE_COLUMN="CREATED_BY" TYPE="VARCHAR2" LENGTH="20"
PRECISION="" PERSIST="Y" LEVEL="1" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="updatedBy" SOURCE_TABLE="UW_UNDERWRITING_RULES"
SOURCE_COLUMN="UPDATED_BY" TYPE="VARCHAR2" LENGTH="20"
PRECISION="" PERSIST="Y" LEVEL="1" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="createdDate" SOURCE_TABLE="UW_UNDERWRITING_RULES"
SOURCE_COLUMN="CREATED_DATE" TYPE="DATE" LENGTH=""
PRECISION="" PERSIST="Y" LEVEL="1" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="updatedDate" SOURCE_TABLE="UW_UNDERWRITING_RULES"
SOURCE_COLUMN="UPDATED_DATE" TYPE="DATE" LENGTH=""
PRECISION="" PERSIST="Y" LEVEL="1" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="processName" SOURCE_TABLE="UW_UNDERWRITING_RULES"
SOURCE_COLUMN="PROCESS_NAME" TYPE="VARCHAR2" LENGTH="100"
PRECISION="" PERSIST="Y" LEVEL="1" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="overrideReason" SOURCE_TABLE="UW_UNDERWRITING_RULES"
SOURCE_COLUMN="OVERRIDE_REASON" TYPE="VARCHAR2" LENGTH="1000"
PRECISION="" PERSIST="Y" LEVEL="1" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="messageModule" SOURCE_TABLE="UW_UNDERWRITING_RULES"
SOURCE_COLUMN="MESSAGE_MODULE" TYPE="VARCHAR2" LENGTH="30"
PRECISION="" PERSIST="Y" LEVEL="1" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
</Object>
<Object NAME="com.los.common.entity.Applicant">
<field NAME="applicantId" SOURCE_TABLE="UW_APPLICANT_MASTER"
SOURCE_COLUMN="APPLICANT_ID" TYPE="NUMBER" LENGTH="20"
PRECISION="" PERSIST="Y" LEVEL="1" DEFAULT_VALUE="" PRIMARY_KEY="Y"
VERSIONABLE="N" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="registrationNumber" SOURCE_TABLE="UW_APPLICANT_MASTER"
SOURCE_COLUMN="REGISTRATION_NUMBER" TYPE="NUMBER" LENGTH="20"
PRECISION="" PERSIST="Y" LEVEL="1" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="N" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="cifNumber" SOURCE_TABLE="UW_APPLICANT_MASTER"
SOURCE_COLUMN="CIF_NUMBER" TYPE="NUMBER" LENGTH="20"
PRECISION="" PERSIST="Y" LEVEL="1" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="N" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="customerStatus" SOURCE_TABLE="UW_APPLICANT_MASTER"
SOURCE_COLUMN="CUSTOMER_STATUS" TYPE="VARCHAR2" LENGTH="20"
PRECISION="" PERSIST="Y" LEVEL="1" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="N" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="customerType" SOURCE_TABLE="UW_APPLICANT_MASTER"
SOURCE_COLUMN="CUSTOMER_TYPE" TYPE="VARCHAR2" LENGTH="20"
PRECISION="" PERSIST="Y" LEVEL="1" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="N" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="applicantLastName" SOURCE_TABLE="UW_APPLICANT_DETAILS"
SOURCE_COLUMN="APPLICANT_LAST_NAME" TYPE="VARCHAR2" LENGTH="100"
PRECISION="" PERSIST="Y" LEVEL="2" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="applicantFirstName" SOURCE_TABLE="UW_APPLICANT_DETAILS"
SOURCE_COLUMN="APPLICANT_FIRST_NAME" TYPE="VARCHAR2" LENGTH="100"
PRECISION="" PERSIST="Y" LEVEL="2" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="applicantMiddleName" SOURCE_TABLE="UW_APPLICANT_DETAILS"
SOURCE_COLUMN="APPLICANT_MIDDLE_NAME" TYPE="VARCHAR2" LENGTH="100"
PRECISION="" PERSIST="Y" LEVEL="2" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="applicantNameSuffix" SOURCE_TABLE="UW_APPLICANT_DETAILS"
SOURCE_COLUMN="APPLICANT_NAME_SUFFIX" TYPE="VARCHAR2" LENGTH="20"
PRECISION="" PERSIST="Y" LEVEL="2" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="nationality" SOURCE_TABLE="UW_APPLICANT_DETAILS"
SOURCE_COLUMN="NATIONALITY" TYPE="VARCHAR2" LENGTH="100"
PRECISION="" PERSIST="Y" LEVEL="2" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="age" SOURCE_TABLE="UW_APPLICANT_DETAILS"
SOURCE_COLUMN="AGE" TYPE="NUMBER" LENGTH="5"
PRECISION="2" PERSIST="Y" LEVEL="2" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="dateOfBirth" SOURCE_TABLE="UW_APPLICANT_DETAILS"
SOURCE_COLUMN="DATE_OF_BIRTH" TYPE="DATE" LENGTH=""
PRECISION="" PERSIST="Y" LEVEL="2" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="identificationType1" SOURCE_TABLE="UW_APPLICANT_DETAILS"
SOURCE_COLUMN="IDENTIFICATION_TYPE1" TYPE="VARCHAR2" LENGTH="20"
PRECISION="" PERSIST="Y" LEVEL="2" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="identificationType2" SOURCE_TABLE="UW_APPLICANT_DETAILS"
SOURCE_COLUMN="IDENTIFICATION_TYPE2" TYPE="VARCHAR2" LENGTH="20"
PRECISION="" PERSIST="Y" LEVEL="2" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="identificationType" SOURCE_TABLE="UW_APPLICANT_DETAILS"
SOURCE_COLUMN="IDENTIFICATION_TYPE" TYPE="VARCHAR2" LENGTH="20"
PRECISION="" PERSIST="Y" LEVEL="2" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="identificationNumber1" SOURCE_TABLE="UW_APPLICANT_DETAILS"
SOURCE_COLUMN="IDENTIFICATION_NUMBER1" TYPE="VARCHAR2" LENGTH="100"
PRECISION="" PERSIST="Y" LEVEL="2" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="identificationNumber2" SOURCE_TABLE="UW_APPLICANT_DETAILS"
SOURCE_COLUMN="IDENTIFICATION_NUMBER2" TYPE="VARCHAR2" LENGTH="100"
PRECISION="" PERSIST="Y" LEVEL="2" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="identificationNumber" SOURCE_TABLE="UW_APPLICANT_DETAILS"
SOURCE_COLUMN="IDENTIFICATION_NUMBER" TYPE="VARCHAR2" LENGTH="100"
PRECISION="" PERSIST="Y" LEVEL="2" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="guarantorIndicator" SOURCE_TABLE="UW_APPLICANT_DETAILS"
SOURCE_COLUMN="GUARANTOR_INDICATOR" TYPE="VARCHAR2" LENGTH="50"
PRECISION="" PERSIST="Y" LEVEL="2" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="separateCobDisclosureRequir" SOURCE_TABLE="UW_APPLICANT_DETAILS"
SOURCE_COLUMN="SEPARATE_COB_DISCLOSURE_REQUIR" TYPE="VARCHAR2" LENGTH="20"
PRECISION="" PERSIST="Y" LEVEL="2" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="domesticRisk" SOURCE_TABLE="UW_APPLICANT_DETAILS"
SOURCE_COLUMN="DOMESTIC_RISK" TYPE="VARCHAR2" LENGTH="20"
PRECISION="" PERSIST="Y" LEVEL="2" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="crossBorderRisk" SOURCE_TABLE="UW_APPLICANT_DETAILS"
SOURCE_COLUMN="CROSS_BORDER_RISK" TYPE="VARCHAR2" LENGTH="20"
PRECISION="" PERSIST="Y" LEVEL="2" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="title" SOURCE_TABLE="UW_APPLICANT_DETAILS"
SOURCE_COLUMN="TITLE" TYPE="VARCHAR2" LENGTH="20"
PRECISION="" PERSIST="Y" LEVEL="2" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="previousSurname" SOURCE_TABLE="UW_APPLICANT_DETAILS"
SOURCE_COLUMN="PREVIOUS_SURNAME" TYPE="VARCHAR2" LENGTH="50"
PRECISION="" PERSIST="Y" LEVEL="2" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="legalName" SOURCE_TABLE="UW_APPLICANT_DETAILS"
SOURCE_COLUMN="LEGAL_NAME" TYPE="VARCHAR2" LENGTH="200"
PRECISION="" PERSIST="Y" LEVEL="2" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="preferredName" SOURCE_TABLE="UW_APPLICANT_DETAILS"
SOURCE_COLUMN="PREFERRED_NAME" TYPE="VARCHAR2" LENGTH="50"
PRECISION="" PERSIST="Y" LEVEL="2" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="gender" SOURCE_TABLE="UW_APPLICANT_DETAILS"
SOURCE_COLUMN="GENDER" TYPE="VARCHAR2" LENGTH="20"
PRECISION="" PERSIST="Y" LEVEL="2" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="seniorCitizenStatus" SOURCE_TABLE="UW_APPLICANT_DETAILS"
SOURCE_COLUMN="SENIOR_CITIZEN_STATUS" TYPE="VARCHAR2" LENGTH="20"
PRECISION="" PERSIST="Y" LEVEL="2" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="staffIndicator" SOURCE_TABLE="UW_APPLICANT_DETAILS"
SOURCE_COLUMN="STAFF_INDICATOR" TYPE="VARCHAR2" LENGTH="20"
PRECISION="" PERSIST="Y" LEVEL="2" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="warVeteranIndicator" SOURCE_TABLE="UW_APPLICANT_DETAILS"
SOURCE_COLUMN="WAR_VETERAN_INDICATOR" TYPE="VARCHAR2" LENGTH="20"
PRECISION="" PERSIST="Y" LEVEL="2" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="noOfDependants" SOURCE_TABLE="UW_APPLICANT_DETAILS"
SOURCE_COLUMN="NO_OF_DEPENDANTS" TYPE="NUMBER" LENGTH="20"
PRECISION="" PERSIST="Y" LEVEL="2" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="maritalStatus" SOURCE_TABLE="UW_APPLICANT_DETAILS"
SOURCE_COLUMN="MARITAL_STATUS" TYPE="VARCHAR2" LENGTH="20"
PRECISION="" PERSIST="Y" LEVEL="2" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="educationStatus" SOURCE_TABLE="UW_APPLICANT_DETAILS"
SOURCE_COLUMN="EDUCATION_STATUS" TYPE="VARCHAR2" LENGTH="20"
PRECISION="" PERSIST="Y" LEVEL="2" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="detApplicantId" SOURCE_TABLE="UW_APPLICANT_DETAILS"
SOURCE_COLUMN="APPLICANT_ID" TYPE="NUMBER" LENGTH="20"
PRECISION="" PERSIST="Y" LEVEL="2" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="Y" PARENT_TABLE="UW_APPLICANT_MASTER" PARENT_COLUMN="APPLICANT_ID">
</field>
<field NAME="detApplicantDetailId" SOURCE_TABLE="UW_APPLICANT_DETAILS"
SOURCE_COLUMN="APPLICANT_DETAIL_ID" TYPE="NUMBER" LENGTH="20"
PRECISION="" PERSIST="Y" LEVEL="2" DEFAULT_VALUE="" PRIMARY_KEY="Y"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="usResidentIndicator" SOURCE_TABLE="UW_APPLICANT_DETAILS"
SOURCE_COLUMN="US_RESIDENT_INDICATOR" TYPE="VARCHAR2" LENGTH="1"
PRECISION="" PERSIST="Y" LEVEL="2" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="employeeNumber" SOURCE_TABLE="UW_APPLICANT_DETAILS"
SOURCE_COLUMN="EMPLOYEE_NUMBER" TYPE="VARCHAR2" LENGTH="20"
PRECISION="" PERSIST="Y" LEVEL="2" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="isdefaulter" SOURCE_TABLE="UW_APPLICANT_DETAILS"
SOURCE_COLUMN="ISDEFAULTER" TYPE="VARCHAR2" LENGTH="20"
PRECISION="" PERSIST="Y" LEVEL="2" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
</Object>
<Object NAME="com.los.common.entity.ApplicantContact">
<field NAME="applicantId" SOURCE_TABLE="UW_APPLICANT_CONTACT_INFO"
SOURCE_COLUMN="APPLICANT_ID" TYPE="NUMBER" LENGTH="20"
PRECISION="" PERSIST="Y" LEVEL="1" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="Y" PARENT_TABLE="UW_APPLICANT_MASTER" PARENT_COLUMN="APPLICANT_ID">
</field>
<field NAME="contactId" SOURCE_TABLE="UW_APPLICANT_CONTACT_INFO"
SOURCE_COLUMN="CONTACT_ID" TYPE="NUMBER" LENGTH="20"
PRECISION="" PERSIST="Y" LEVEL="1" DEFAULT_VALUE="" PRIMARY_KEY="Y"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="addressType" SOURCE_TABLE="UW_APPLICANT_CONTACT_INFO"
SOURCE_COLUMN="ADDRESS_TYPE" TYPE="VARCHAR2" LENGTH="20"
PRECISION="" PERSIST="Y" LEVEL="1" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="applicantAddressLine1" SOURCE_TABLE="UW_APPLICANT_CONTACT_INFO"
SOURCE_COLUMN="APPLICANT_ADDRESS_LINE_1" TYPE="VARCHAR2" LENGTH="100"
PRECISION="" PERSIST="Y" LEVEL="1" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="applicantAddressLine2" SOURCE_TABLE="UW_APPLICANT_CONTACT_INFO"
SOURCE_COLUMN="APPLICANT_ADDRESS_LINE_2" TYPE="VARCHAR2" LENGTH="100"
PRECISION="" PERSIST="Y" LEVEL="1" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="applicantAddressLine3" SOURCE_TABLE="UW_APPLICANT_CONTACT_INFO"
SOURCE_COLUMN="APPLICANT_ADDRESS_LINE_3" TYPE="VARCHAR2" LENGTH="100"
PRECISION="" PERSIST="Y" LEVEL="1" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="applicantAddressLine4" SOURCE_TABLE="UW_APPLICANT_CONTACT_INFO"
SOURCE_COLUMN="APPLICANT_ADDRESS_LINE_4" TYPE="VARCHAR2" LENGTH="100"
PRECISION="" PERSIST="Y" LEVEL="1" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="residingSince" SOURCE_TABLE="UW_APPLICANT_CONTACT_INFO"
SOURCE_COLUMN="RESIDING_SINCE" TYPE="DATE" LENGTH=""
PRECISION="" PERSIST="Y" LEVEL="1" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="residentialStatus" SOURCE_TABLE="UW_APPLICANT_CONTACT_INFO"
SOURCE_COLUMN="RESIDENTIAL_STATUS" TYPE="VARCHAR2" LENGTH="20"
PRECISION="" PERSIST="Y" LEVEL="1" DEFAULT_VALUE="" PRIMARY_KEY="N"
VERSIONABLE="Y" FOREIGN_KEY="" PARENT_TABLE="" PARENT_COLUMN="">
</field>
<field NAME="applicantEMaCould you please provide the stack trace?
-
Varchar Type column value too large ERROR (ORA-12899)
Hi,
I'm using Build *"ODI_11.1.1.3.0_GENERIC_100623.1635"*
I'm trying to move data from SQL SERVER 2005 to Oracle DB 11.2.
Integration Knowledge Module is : IKM SQL INCREMENTAL UPDATE
Loading Knowledge Module : LKM SQL TO ORACLE
The problem is in VARCHAR type column with length 20.
The target column type is VARCHAR2 , length 20.
Integration fails on the LOADING STEP with message : java.sql.BatchUpdateException: ORA-12899: value too large for column "DW_WORKUSER"."C$_10PLFACT"."C65_SOURCENO" *(actual: 26, maximum: 20)*
Column mapping is executed on the Source.
In column mapping I'm not using any convertion, casting or any other logic, I'm just moving my column to the target table.
Can anyone make some suggestions ?Hi,
This is due to bytes not chars. On your SQL server db you can have multibyte characters (as you can elsewhere). You may need to modify the C$/I$ and your target tables to bytes rather than chars. You may also want to check the CHARACTER_SETS that are used on the source and target.
eg
VARCHAR2(20 BYTE)
Cheers
Bos
Edited by: Bos on Apr 13, 2011 8:36 AM -
Using in clause having more than 4000 chars in a VO.
Hi Experts,
JDEV version 11.1.1.5.0
I have a problem passing a bind variable having length of more than 4000 chars in ADF for use in a IN clause.
For e.g the query is
select user_id from employees where user_name in (
SELECT column_value
FROM TABLE (CAST (in_list_char (nvl( 'apple,oranges',user_name) ) AS ChartableType)) A)
in_list_char is function returning an array of type ChartableType.
ChartableType is a type
create or replace TYPE "CHARTABLETYPE" as table of varchar2(4000);
It works if the bind value that I pass is of length less than 4000 chars.
Anything higher it breaks and throws ORA-01460: unimplemented or unreasonable conversion requested.
Have even tried changing the ChartableType varchar2 length to 32767..but no luck.
Any help would be appreciated.Hi Timo,
I am using a in clause as the value that I pass as a bind variable is not stored anywhere in the db for me to have a join or a subselect.
It's a comma separated string (comma separated user names) for which I would need to check against the employee table to fetch the user_id's .
An alternative would be to store those values in temp table and have a join.
But then I was trying to find an alternative , either having a OR clause or UNION dynamically appended to my VO
Any help is much appreciated. -
External Table error: KUP-04043: table column not found in external source
I am trying to get the syntaxc correct for an external table.
I keep getting this error:
ORA-29913: error in executing ODCIEXTTABLEOPEN callout
ORA-29400: data cartridge error
KUP-04043: table column not found in external source: SITE
29913. 00000 - "error in executing %s callout"
*Cause: The execution of the specified callout caused an error.
*Action: Examine the error messages take appropriate action.
Data looks like: (some of one of many files, where the character field widths are variable)
ZZ,ANYOLDDATA,77777,25002000,201103,12,555.555,11.222
ZZ,ANYOLDDATA,77777,25002300,201103,34,602.162,8.777
ZZ,ANYOLDDATA,77777,25002400,201103,12,319.127,9.666
ZZ,OTHERDATA,77121,55069600,201103,34,25.544,1.332
ZZ,OTHERDATAS,77122,55069600,201103,22, 1.011,0.293
External table def I have:
CREATE TABLE MY_INPUT (
FIRST_CODE VARCHAR2(10),
SECOND_CODE VARCHAR2(20),
MY_NUMBER VARCHAR2(20),
THIRD_CODE VARCHAR2(20),
YEARMO VARCHAR2(6),
N NUMBER,
MEAN NUMBER,
SD NUMBER
ORGANIZATION EXTERNAL (
TYPE ORACLE_LOADER
DEFAULT DIRECTORY INPUT_DIR
ACCESS PARAMETERS (
RECORDS DELIMITED BY newline
BADFILE INPUT_LOGDIR:'bad.bad'
LOGFILE INPUT_LOGDIR:'log.log'
DISCARDFILE INPUT_LOGDIR:'discards.log'
fields terminated by ',' LRTRIM
MISSING FIELD VALUES ARE NULL
REJECT ROWS WITH ALL NULL FIELDS
( THIRD_CODE,N,MEAN,SD) )
LOCATION ( 'myfile.rpt')
NOPARALLEL
REJECT LIMIT UNLIMITED;
I have the directories INPUT_DIR and INPUT_LOGDIR defined, and read/write access granted to the user who creates the table and tried to query from it.
I have tried various combinations of VARCHAR2 lengths and NUMBER vs VARCHAR2 for some of the numeric fields.
I am not getting any Bad, Log or Discard files.
I can do a GET from the SQL prompt, and see the data:
SQL> GET 'C:\temp\input_dir'myfile.rpt'
and I see the data.
Windows 7
Oracle 11.2
I am not positive of the newline record delimiter - these files are generated by an automated system. Probably generated on a UNIX machine.
Any suggestions on what to try would be helpful.
KUP-04043 error message says to check the syntax .. .I am running out of thigns to check.
Thank you - KarenAnd the get ( I created the sanitized file, so we have a real working, failing, santiized example):
SQL> get c:\Inputfiles\myfile.rpt
1 ZZ,ANYOLDDATA,77777,25002000,201103,12,555.555,11.222
2 ZZ,ANYOLDDATA,77777,25002300,201103,34,602.162,8.777
3 ZZ,ANYOLDDATA,77777,25002400,201103,12,319.127,9.666
4 ZZ,OTHERDATA,77121,55069600,201103,34,25.544,1.332
5* ZZ,OTHERDATAS,77122,55069600,201103,22, 1.011,0.293
So the full series is:
CREATE DIRECTORY INPUT_DIR AS 'C:\InputFiles';
-- grant READ and WRITE
GRANT READ ON DIRECTORY INPUT_DIR TO ILQC;
GRANT WRITE ON DIRECTORY INPUT_DIR TO ILQC;
-- As SYS, create the bad/log/discard directory:
CREATE DIRECTORY LOGDIR AS 'C:\InputFiles\Logs';
-- grant READ and WRITE
GRANT READ ON DIRECTORY LOGDIR TO ILQC;
GRANT WRITE ON DIRECTORY LOGDIR TO ILQC;
CREATE TABLE MY_INPUT (
FIRST_CODE VARCHAR2(10),
SECOND_CODE VARCHAR2(20),
MY_NUMBER VARCHAR2(20),
THIRD_CODE VARCHAR2(20),
YEARMO VARCHAR2(6),
N NUMBER,
MEAN NUMBER,
SD NUMBER
ORGANIZATION EXTERNAL (
TYPE ORACLE_LOADER
DEFAULT DIRECTORY INPUT_DIR
ACCESS PARAMETERS (
RECORDS DELIMITED BY newline
BADFILE INPUT_LOGDIR:'bad.bad'
LOGFILE INPUT_LOGDIR:'log.log'
DISCARDFILE INPUT_LOGDIR:'discards.log'
fields terminated by ',' LRTRIM
MISSING FIELD VALUES ARE NULL
REJECT ROWS WITH ALL NULL FIELDS
( THIRD_CODE,N,MEAN,SD) )
LOCATION ( 'myfile.rpt')
NOPARALLEL
REJECT LIMIT UNLIMITED;
SELECT * FROM my_input;
and GET is as above. -
oracle 11.2.0
I have a procedure in a package that has an "OUT" variable as a varchar2. For example ...
PROCEDURE myproc(abc IN varchar2, xyz OUT varchar2);
I can pass in a string that is larger than 4000 characters into "abc" and it works fine. I can then store it as a CLOB no problem. When I read that CLOB and put it into "xyz", I can't do it. If I try to put it into xyz using DBMS_LOB.read(myclob, clobsize, 1, xyz), then I get saying that there is a size constraint on xyz. If I create an internal variable called ...
MNO VARCHAR2(32000);
And say DBMS_LOB.read(myclob, clobsize, 1, MNO), then that works fine. When I try to pass it back into xyz, it truncates and only sends back the first 4000 characters. I have tried making it a function, and all kind of variations, but I cannot send back more than 4000 characters. I have also searched the web for an explanation, but nowhere does it say there is a size restriction on either incoming or outgoing variables.
To get around this, I can send back a CLOB and let the calling program do the work, or I can send back 2 smaller variables that are less than 4000 chars each and let the calling program concat them together. I am looking for any solutions to make the original setup work. Do you know of any limitations or something I can try?You have to look at the caller procedure that calls myproc. What variable do you use in this procedure to retrieve the result of the OUT parameter?
create or replace procedure dropme (xyz out varchar2)
is
begin
xyz := 'Hello world';
end;
declare
abc varchar2(1);
begin
dropme(abc);
end;
Error at line 1
ORA-06502: PL/SQL: numeric or value error: character string buffer too small
ORA-06512: at "PROD.DROPME", line 4
ORA-06512: at line 4This rang a bell, and apparently I posted this question myself a long time ago B-)
Maximum VARCHAR2 length in stored procedure parameter
Edited by: InoL on Aug 31, 2011 1:31 PM -
Sdo_geometry bind variables in trace file
If I run trace on oracle spatial queries, how can I get the detailed information of the sdo_geometry objects (the content of the sdo_geometry objects, e.g. coordinates... ) in the queries?
Thanks!Hi Rob
Haven't checked the bind variable issue specifically here, but just a by-pass-reflex-of-fixed-implementations, have you tried passing the geometry as WKT?
Obviously, this can also have some constraints on the varchar2 length etc, but depending on the type of geometries (and consequent length of the WKT) it might help you working around it.
Check this section for the appropriate sdo_geometry constructor based on a WKT input.
http://docs.oracle.com/cd/B19306_01/appdev.102/b14255/sdo_objrelschema.htm#CBBFGHAE
Just a thought
Luc -
Hi,
I have code as below
Scenario1
FOR i in (Select .................... from table1 Where id in(select id from Sample_table where status='Submit'))
Loop
End loop;
Scenario2
FOR i in (Select .................... from table1 Where id in(select id from Sample_table where status='Saved'))
Loop
End loop;
Scenario3
FOR i in (Select .................... from table1 Where id in(select id from Sample_table where status='Inprogress'))
Loop
End loop;Query is same here but only chage is where clause
Total length of this query is exceeding varchar2 length. so i cant use variable to hold this query and append where clause dynamically.
Do we have any other method to change where clause dynamically?>
We have around 200 columns to select from multiple tables...Here I gave sample code...
so its exceeding length
>
So 200 columns at 30 bytes per column name is only 6000 bytes. That means the rest of the query is using over 26000 bytes: 260 lines of query if each line was 100 bytes long.
You need to rethink what you are doing. So far your queries are too big, your row-by-row processing is a terrible way to process data and repeating that process multiple times just aggravates the performance even more.
I can't imagine there is ANY justification for doing things that way.
Even if you HAD to do things that way you couldn't exceed the CLOB length so why aren't you using a CLOB variable?
http://docs.oracle.com/cd/B28359_01/appdev.111/b28370/openfor_statement.htm
>
OPEN-FOR StatementThe OPEN-FOR statement executes the SELECT statement associated with a cursor variable. It allocates database resources to process the statement, identifies the result set (the rows that meet the conditions), and positions the cursor variable before the first row in the result set.
With the optional USING clause, the OPEN-FOR statement processes a dynamic SELECT statement that returns multiple rows: it associates a cursor variable with the SELECT statement, executes the statement, identifies the result set, positions the cursor before the first row in the result set, and zeroes the rows-processed count kept by %ROWCOUNT.
dynamic_string
A string literal, string variable, or string expression that represents any SQL statement. It must be of type CHAR, VARCHAR2, or CLOB. -
Import Spreadsheet Long value error
Hi folks,
I'm trying to Import Text or Spreadsheet Data into a table in Htmldb.
It should create a new-table with some column names and it's data. I converted a Excel list and saved it to .txt.
When I try to import it into htmldb (al columns Varchar2) I get the following error message.
ORA-20001: Load csv data error: ORA-01461: can bind a LONG value only for insert into a LONG column ORA-01461: can bind a LONG value only for insert into a LONG column
Does Anyone know what I can do about this problem?
regards,
RichardRichard,
I ran into a similar problem. I found that APEX is not to fond of 'cr + lf' characters in my spreadsheet.
Option 1:
Used the clean function (in excel) to remove all of the special characters. Also, check the length of the fields in excel and make sure your VARCHAR2 length is larger than the max entry length.
Option 2:
Change from VARCHAR2 to CLOB.
Derek
Maybe you are looking for
-
My husband and I share an i cloud account but each have our own separate ipads. We were told this would work, but now I can't find a book that I've downloaded on my ipad anymore. Where would I find it?
-
Here is an example of what my google "menubar" looks like: http://gyazo.com/c9ee92acb805bf6ede3b8fe0d975b6e6 Normal text is easy enough to read but any text in bold seems smudged. Is there any option that may or may not be selected to fix this? It's
-
Credit control with Groups of Customers and individul customer
Hello,everyone. I want to realize the credit control for the groups of customers and each individul customer belongs to it. how can i do ? thanks first
-
I loaded two security updates today and restarted my comp. The only thing that now shows on the screen is the dock. Help
-
Table bk_logmnr_contents consists of the 150000 rows. And below block takes 90 minutes to execute the block. What changes i can do so that below block will tune? DECLARE CURSOR c_logmnr IS SELECT row_id,sql_redo FROM bk_logmnr_contents; text VARCHAR2