Reg : Data Length

Hi all ,
In the table tadir where thers is field called obn_name its length is Char 40.
& im using for all entries with table modsap where the name length is Char 08.
when i try to use for all entires for the above 2 table 's
its giving error like this .
when using the addition 'for all entries in itab"the fields "NAME" & " ITAB-OBJ_NAME must have same length.
How to resolve this ???
Regs,
Murthy

Hi
It will work only if both the fields are having same value. You can do one thing you can supress the unwanted 0's from begining of field if any.
Regards
Aditya

Similar Messages

Data length error in record 86.

Data length error in record 86.
Message no. FV147
Diagnosis
An error occurred in the processing of the data to be imported. It is highly probable that this is a data error.
Contact your data provider.
System Response
Any account statement processing currently underway and any outstanding is being terminated.
Procedure
Check the structure of the supplied data. If the statement data you have obtained is error-free, you can simply restart the program. All those statements which have already been imported correctly will not be reimported.
{1:F01SCBLINBBXXXX3446100003}{2:O9400634140719SCBLINBBXXXX34461000031407190634N}{3:{108:00000000000718}}{4:
:20:14071905fr309439
:25:52205785839
:28C:611
:60F:D140718INR792788,04
:61:1407180718CR100000,00N169NONREF
:86:IN36701407187774 VIJBH14199069837
IN36701407187774 VIJBH14199069837
AGARWAL AGENCIES
:61:1407180718CR150000,00N169NONREF
:86:IN36701407187251 SBIN414199017384
IN36701407187251 SBIN414199017384
EAGLE FOOTWERE
:61:1407180718CR100000,00N169NONREF
:86:IN36701407187052 SAA96678573
IN36701407187052 SAA96678573
TANVEER TRADERS
:61:1407180718CR98000,00N169NONREF
:86:IN36701407186828 SBIN314199982628
IN36701407186828 SBIN314199982628
MODERN AGENCY
:61:1407180718CR179000,00N169NONREF
:86:IN36701407186029 SAA96670577
IN36701407186029 SAA96670577
BALAJI ENTERPRISES
:61:1407180718CR60000,00N169NONREF
:86:IN36701407185397 367845438
IN36701407185397 367845438
SAKSHI ENTERPRISES
:61:1407180718CR2000000,00N169NONREF
:86:IN3670140718H568 SBIN414199360804
IN3670140718H568 SBIN414199360804
RELAXO FOOTWEARS LIMITED
:61:1407180718CR38000,00N169NONREF
:86:IN3670140718G554 CBINH14199566672
IN3670140718G554 CBINH14199566672
WONDER WALK AGENCIES
:61:1407180718CR113000,00N169NONREF
:86:IN3670140718F851 JAKA140718621672
IN3670140718F851 JAKA140718621672
JYOTI SALES PROP MR AMIT VOHRA S
:61:1407180718CR54200,00N169NONREF
:86:IN3670140718F006 BKIDN14199343033
IN3670140718F006 BKIDN14199343033
SHAH FOOT WEAR
:61:1407180718CR64000,00N169NONREF
:86:IN3670140718F094 BKIDN14199343132
IN3670140718F094 BKIDN14199343132
MUSKAN TRADERS
:61:1407180718CR114500,00N169NONREF
:86:IN3670140718F423 SBIN414199302946
IN3670140718F423 SBIN414199302946
GOUTAM DISTRIBUTORS
:61:1407180718CR63000,00N169NONREF
:86:IN3670140718D651 SD1141261589
IN3670140718D651 SD1141261589
M K FOOTWEAR
:61:1407180718CR67913,00N169NONREF
:86:IN3670140718D057 SBIN414199247753
IN3670140718D057 SBIN414199247753
SSS PG STORES
:61:1407180718CR130000,00N169NONREF
:86:IN3670140718D183 UTBIN14199275937
IN3670140718D183 UTBIN14199275937
GOPAL SHOES
:61:1407180718CR48000,00N169NONREF
:86:IN3670140718C628 CBINH14199546949
IN3670140718C628 CBINH14199546949
AGGARWAL FOOTWEAR
:61:1407180718DR5000000,00N506PIRLXOIN01A00468
PIRLXOIN01A00468
:86:PIRLXOIN01A00468 SCBLR12014071800003757
CASH SCBLR12014071800003757
RELAXO FOOTWEARS LIMITED
SIN09373C0000423 00001 PIRLXOIN01A0
0468
PIRLXOIN01A00468
:61:1407180718DR4000000,00N506PIRLXOIN01A00469
PIRLXOIN01A00469
:86:PIRLXOIN01A00469 SIN09373Q0000468
PIRLXOIN01A00469-SIN09373Q0000468
SB3670140718HK96
SIN09373C0000424-00001 PIRLXOIN01A0
0469
:61:1407180718DR1699195,25N699TRF
:86:316031790865 PAY001
316031790865 PAY001
GRAND WISE ENTERPRISES LIMITED
AKMP037
USD28,030.8 60.5755/INR743.76 1
DEBIT IMEX CUSTOMER A/C
:61:1407180718CR480000,00N195NONREF
:86:IL36701407182157 BARBR52014071800734481
CASH BARBR52014071800734481
APNA FOOT WEAR
SENDER IFSCBARB0CHARMI
IL36701407182157
:61:1407180718CR235000,00N195NONREF
:86:IL36701407185517 SBINR52014071801147506
CASH SBINR52014071801147506
PRAKASH FOOT WEAR
FUND TRF FRM 33174969142 TO52205785
SENDER IFSCSBIN0016310
IL36701407185517
:61:1407180718CR500000,00N195NONREF
:86:IL36701407185083 SBINR12014071801142317
CASH SBINR12014071801142317
MODERN FOOTWEARS
SENDER IFSCSBIN0001521
IL36701407185083
:61:1407180718CR800000,00N195NONREF
:86:IL36701407184746 HDFCR52014071851912408
CASH HDFCR52014071851912408
FASHION SQUARE
SENDER IFSCHDFC0000412
IL36701407184746
:61:1407180718CR332000,00N195NONREF
:86:IL36701407184713 SBINR52014071801140001
CASH SBINR52014071801140001
WINGS POLYMERS
SENDER IFSCSBIN0001581
IL36701407184713
:61:1407180718CR450000,00N195NONREF
:86:IL36701407184302 FDRLR52014071800031798
CASH FDRLR52014071800031798
ABHINAV ENTERPRISE
SENDER IFSCFDRL0001492
IL36701407184302
:61:1407180718CR650000,00N195NONREF
:86:IL36701407183976 UCBAR32014071800058993
CASH UCBAR32014071800058993
GAYLORD SHOE AND CHAPPAL
SENDER IFSCUCBA0000048
IL36701407183976
:61:1407180718CR700000,00N195NONREF
:86:IL36701407183860 SBINR52014071801134507
CASH SBINR52014071801134507
FOOTWEAR HOUSE
RTGS TGH CHQ NO 172867
SENDER IFSCSBIN0008602
IL36701407183860
:61:1407180718CR250000,00N195NONREF
:86:IL36701407183487 SBINR52014071801131379
CASH SBINR52014071801131379
PRATAP AGENCY PROP MRS SUNITA KUMRA
SENDER IFSCSBIN0014152
IL36701407183487
:61:1407180718CR254740,00N195NONREF
:86:IL36701407182511 HDFCR52014071851915942
CASH HDFCR52014071851915942
HEPHZIBAH AGENCIES
SENDER IFSCHDFC0001498
IL36701407182511
:61:1407180718CR398000,00N195NONREF
:86:IL36701407182496 BARBR52014071800726312
CASH BARBR52014071800726312
RAZA FOOT WEAR
SENDER IFSCBARB0BASTIX
IL36701407182496
:61:1407180718CR300000,00N195NONREF
:86:IL36701407182349 KKBKR52014071800664337
CASH KKBKR52014071800664337
M M DISTRIBUTORS
PAYMENT
SENDER IFSCKKBK0000958
IL36701407182349
:61:1407180718CR61136,00N169NONREF
:86:IN3670140718C504 IOBAN14199026875
IN3670140718C504 IOBAN14199026875
M S CHINNS TRADERS
:61:1407180718CR79995,00N169NONREF
:86:IN3670140718C142 SBIN414199219784
IN3670140718C142 SBIN414199219784
FRONTIER TRADING COMPANY
:61:1407180718CR100000,00N169NONREF
:86:IN3670140718B731 SBIN414199200112
IN3670140718B731 SBIN414199200112
SHRI AMBEY TRADERS
:61:1407180718CR125000,00N169NONREF
:86:IN3670140718B521 N199140025581074
IN3670140718B521 N199140025581074
SHYAM BROTHERS
:61:1407180718CR68000,00N169NONREF
:86:IN3670140718A144 1205061871400003
IN3670140718A144 1205061871400003
POPULAR TRADERS PROP PISHORI LAL SETHI
:61:1407180718CR41000,00N169NONREF
:86:IN3670140718A044 P14071849681718
IN3670140718A044 P14071849681718
AKSHAY FOOTWEARS
:61:1407180718CR50000,00N169NONREF
:86:IN3670140718A099 BARBH14199284604
IN3670140718A099 BARBH14199284604
STAR ENTERPRISE
:61:1407180718CR100000,00N169NONREF
:86:IN3670140718A002 SAA21370357
IN3670140718A002 SAA21370357
JAI OMKAR ENTERPRISES
:61:1407180718CR120000,00N169NONREF
:86:IN36701407189725 UTBIN14199269504
IN36701407189725 UTBIN14199269504
SANTI STORES
:61:1407180718CR100000,00N169NONREF
:86:IN36701407189538 SBIN414199107266
IN36701407189538 SBIN414199107266
VINAYAK TRADING
:61:1407180718CR100000,00N169NONREF
:86:IN36701407189842 SAA3564919
IN36701407189842 SAA3564919
SKY STYLE MARKETING PROP.ABHISHEK S
:61:1407180718CR120000,00N169NONREF
:86:IN36701407189384 MAHBH14199609866
IN36701407189384 MAHBH14199609866
ROYAL FOOT WEAR
:62F:D140718INR1697499,29
:64:C140718INR59273846,71
-}{5:{CHK:CHECKSUM DISABLED}{MAC:MACCING DISABLED}}

SAP REPLAY
Regarding the incidence itself, kindly consider that The 86-record
limitation is not a bug of the program, but the standard design.
The error is coded as FV147, when the Note to Payee in Record 86
exceeds 65 characters in Program RFEKA400.
You will need to contact your Bank in order to obtain a correct file:
I have attached some documentation on this message that will allow your
bank to create it.
Otherwise, you may use the following user-exit (SAP NOTE 494777):CMOD
Enhancement Exit Name FEB00004 > EXIT_RFEKA400_001.
This User Exit is called in RFEKA400 in the line: PERFORM
PROCESS_RAW_DATA TABLES SWIFT. In Include ZXF01U06, you have
the option to process the raw data.
Hope this information is useful to you.

How to retreive the max data length of a column

Hello All,
I know how to do a select to get the max data length of a column it is this :
SELECT MAX(LENGTH(COLUMN_NAME) FROM table.
However, I need this information combined with my SQL that returns the Data_type and length from the USER_TAB_COLUMNS. So taking the emp example if the ename column was 50 as VARCHAR2 but the max data entered in it was just 20 I want the information like this:
SELECT COLUMN_NAME, DATA_LENGTH, and the Max length of 20
FROM USER_TAB_COLUMNS WHERE TABLE_NAME='EMP';
I don't know how to get the Max Length of the Column in this table. Can anyone suggest me a hint? An Inline view maybe?
Thanks

Still not sure about your requirements, but how about this
SQL> CREATE OR REPLACE FUNCTION get_max_length(p_table in varchar2, p_col in varchar2) return pls_integer
2 is
3    v_cnt pls_integer;
4 begin
5    execute immediate 'select max(length('||p_col||')) from '||p_table into v_cnt;
6    return v_cnt;
7 end get_max_length;
8 /
Function created.
SQL>
SQL> SELECT COLUMN_NAME,
2         DATA_LENGTH,
3         get_max_length(TABLE_NAME, COLUMN_NAME) max_length
4 FROM USER_TAB_COLUMNS
5 WHERE TABLE_NAME='EMP'
6 AND DATA_TYPE like '%CHAR%'
7 ;
COLUMN_NAME                    DATA_LENGTH MAX_LENGTH
ENAME                                   10          6
JOB                                      9          9
SQL>

'Input data length not a multiple of blocksize' error in CUP

Hello All
I receive the error below when trying to configure CUP. I got this error whilst trying to define the password for the RFC user created in the Connector screen in CUP. CUP doesn't accept the SAP password maintained in SU01. CUP only allows a 4 character password but SU01 is configured to only accept 8 characters. Full error message below.
'com.virsa.ae.commons.utils.StringEncrypter$EncryptionException: Input data length not a multiple of blocksize.'
Can anyone shed any light on this?

Hi All,
This issue is in Version 5.3 SP 7.1 of CUP. It occurs when we are trying to change the password for the CUP connector.
Please note that testing the connectors within the Content Administrator --> Maintain JCO Connections screens works fine and the risk analysis from RAR also works without issue. However, whenever we attempt to enter the password for CUP connecotr setup, it returns an error saying "Action Failed" with the 'Input data length not a multiple of blocksize' error showing in the trace logs.
We seem to be able to store a password of 4 characters e.g. 1234 but this then naturally fails the connection test.
Can anyone suggest a parameter setting to check or a resolution for this particular issue?
Thanks,
Simon

How to over weite old data length in data clusters.

Hello All,
I'm geting short dump CONNE_IMPORT_WRONG_COMP_LENG. bcoz of new data length of one field (Host) is not reflecting in Data Clustor.
How to over write old data length with new data length....
Thanks,

suresh8 wrote:
how to copy my old data in my i6?
Back up and restore your iPhone, iPad, or iPod touch using iCloud or iTunes - Apple Support
Import photos and videos from your iPhone, iPad, or iPod touch to your Mac or Windows PC - Apple Support
As for songs that are on your iPhone, those cannot be copied from the device to another location.

Export with data length semantics

Hello,
I've following problem.
I have a table abcd which contains 2 VARCHAR2 columns with different data length semantics (one with BYTE, one with CHAR). Charset is Single Byte; let's say WE8MSWIN1252, so data length semantics should not be a problem. should not. details later.
So this would be:
create table abcd (a_char VARCHAR2(2 CHAR), a_byte VARCHAR2(2 BYTE));after that I export the table via exp. I'm not setting NLS_LENGTH_SEMANTICS environment variable, so BYTE is used.
In the dump file the data length semantics for the byte col is omitted, as I exported it with BYTE:
create table abcd (a_char VARCHAR2(2 CHAR), a_byte VARCHAR2(2));after that, I "accidently" import it with data length semantics set to CHAR, and the table looks like this now
abcd
a_char VARCHAR2(2 CHAR)
a_byte VARCHAR2(2 CHAR)Same happens vice versa when using CHAR for export and BYTE for import...
In single byte charsets this might not be so much of a problem, as one CHAR is equal to one BYTE, but...
If I compile plsql against the original table, and run against the outcoming table after export, I get an ORA-4062, and I have to recompile...
Would not be a problem if the plsql I compile would be on the database...Big problem is that the ORA-4062 occurs in forms, where it's difficult for me to recompile (I would have to transfer all the sources to customer and compile there).
Is there any possibility to export data length semantics regardless which environment variable is set?
database version would be 9.2.0.6; but if there exists a solution in higher versions I would also be happy to hear them...
many thanks,
regards

I can't reproduce your problem:
SQL> show parameter nls_length_semantics
NAME                                 TYPE        VALUE
nls_length_semantics                 string      BYTE
SQL> create table scott.demo( col1 varchar2(10 byte), col2 varchar2(10 char) );
SQL> describe scott.demo
Name                                      Null?    Type
COL1                                               VARCHAR2(10)
COL2                                               VARCHAR2(10 CHAR)
$ export NLS_LENGTH_SEMANTICS=BYTE
$ exp scott/tiger file=scott.dmp tables=demo
SQL> drop table scott.demo;
$ export NLS_LENGTH_SEMANTICS=CHAR
$ imp scott/tiger file=scott.dmp
SQL> describe scott.demo
Name                                      Null?    Type
COL1                                               VARCHAR2(10 BYTE)
COL2                                               VARCHAR2(10)
SQL> alter session set nls_length_semantics=byte;
SQL> describe scott.demo
Name                                      Null?    Type
COL1                                               VARCHAR2(10)
COL2                                               VARCHAR2(10 CHAR)Can you post a test like mine?
Enrique
PS If you have access to Metalink, read Note:144808.1 Examples and limits of BYTE and CHAR semantics usage. From 9i and up, imp doesn't read nls_length_semantics from the environment.
Edited by: Enrique Orbegozo on Dec 16, 2008 12:50 PM
Edited by: Enrique Orbegozo on Dec 16, 2008 12:53 PM

How to Compare Data length of staging table with base table definition

Hi,
I've two tables :staging table and base table.
I'm getting data from flatfiles into staging table, as per requirement structure of staging table and base table(length of each and every column in staging table is 25% more to dump data without any errors) are different for ex :if we've city column with varchar length 40 in staging table it has 25 in base table.Once data is dumped into staging table I want to compare actual data length of each and every column in staging table with definition of base table(data_length for each and every column from all_tab_columns) and if any column differs length I need to update the corresponding row in staging table which also has a flag called err_length.
so for this I'm using cursor c1 is select length(a.id),length(a.name)... from staging_table;
cursor c2(name varchar2) is select data_length from all_tab_columns where table_name='BASE_TABLE' and column_name=name;
But we're getting data atonce in first query whereas in second cursor I need to get each and every column and then compare with first ?
Can anyone tell me how to get desired results?
Thanks,
Mahender.

This is a shot in the dark but, take a look at this example below:
SQL> DROP TABLE STAGING;
Table dropped.
SQL> DROP TABLE BASE;
Table dropped.
SQL> CREATE TABLE STAGING
2 (
3          ID              NUMBER
4 ,       A               VARCHAR2(40)
5 ,       B               VARCHAR2(40)
6 ,       ERR_LENGTH      VARCHAR2(1)
7 );
Table created.
SQL> CREATE TABLE BASE
2 (
3          ID      NUMBER
4 ,       A       VARCHAR2(25)
5 ,       B       VARCHAR2(25)
6 );
Table created.
SQL> INSERT INTO STAGING VALUES (1,RPAD('X',26,'X'),RPAD('X',25,'X'),NULL);
1 row created.
SQL> INSERT INTO STAGING VALUES (2,RPAD('X',25,'X'),RPAD('X',26,'X'),NULL);
1 row created.
SQL> INSERT INTO STAGING VALUES (3,RPAD('X',25,'X'),RPAD('X',25,'X'),NULL);
1 row created.
SQL> COMMIT;
Commit complete.
SQL> SELECT * FROM STAGING;
        ID A                                        B                                        E
         1 XXXXXXXXXXXXXXXXXXXXXXXXXX               XXXXXXXXXXXXXXXXXXXXXXXXX
         2 XXXXXXXXXXXXXXXXXXXXXXXXX                XXXXXXXXXXXXXXXXXXXXXXXXXX
         3 XXXXXXXXXXXXXXXXXXXXXXXXX                XXXXXXXXXXXXXXXXXXXXXXXXX
SQL> UPDATE STAGING ST
2 SET     ERR_LENGTH = 'Y'
3 WHERE   EXISTS
4          (
5                  WITH    columns_in_staging AS
6                  (
7                          /* Retrieve all the columns names for the staging table with the exception of the primary key column
8                           * and order them alphabetically.
9                           */
10                          SELECT COLUMN_NAME
11                          ,       ROW_NUMBER() OVER (ORDER BY COLUMN_NAME) RN
12                          FROM    ALL_TAB_COLUMNS
13                          WHERE   TABLE_NAME='STAGING'
14                          AND     COLUMN_NAME != 'ID'
15                          ORDER BY 1
16                  ),      staging_unpivot AS
17                  (
18                          /* Using the columns_in_staging above UNPIVOT the result set so you get a record for each COLUMN value
19                           * for each record. The DECODE performs the unpivot and it works if the decode specifies the columns
20                           * in the same order as the ROW_NUMBER() function in columns_in_staging
21                           */
22                          SELECT ID
23                          ,       COLUMN_NAME
24                          ,       DECODE
25                                  (
26                                          RN
27                                  ,       1,A
28                                  ,       2,B
29                                  ) AS VAL
30                          FROM            STAGING
31                          CROSS JOIN      COLUMNS_IN_STAGING
32                  )
33                  /*      Only return IDs for records that have at least one column value that exceeds the length. */
34                  SELECT ID
35                  FROM
36                  (
37                          /* Join the unpivoted staging table to the ALL_TAB_COLUMNS table on the column names. Here we perform
38                           * the check to see if there are any differences in the length if so set a flag.
39                           */
40                          SELECT STAGING_UNPIVOT.ID
41                          ,       (CASE WHEN ATC.DATA_LENGTH < LENGTH(STAGING_UNPIVOT.VAL) THEN 'Y' END) AS ERR_LENGTH_A
42                          ,       (CASE WHEN ATC.DATA_LENGTH < LENGTH(STAGING_UNPIVOT.VAL) THEN 'Y' END) AS ERR_LENGTH_B
43                          FROM    STAGING_UNPIVOT
44                          JOIN    ALL_TAB_COLUMNS ATC     ON ATC.COLUMN_NAME = STAGING_UNPIVOT.COLUMN_NAME
45                          WHERE   ATC.TABLE_NAME='BASE'
46                  )       A
47                  WHERE   COALESCE(ERR_LENGTH_A,ERR_LENGTH_B) IS NOT NULL
48                  AND     ST.ID = A.ID
49          )
50 /
2 rows updated.
SQL> SELECT * FROM STAGING;
        ID A                                        B                                        E
         1 XXXXXXXXXXXXXXXXXXXXXXXXXX               XXXXXXXXXXXXXXXXXXXXXXXXX                Y
         2 XXXXXXXXXXXXXXXXXXXXXXXXX                XXXXXXXXXXXXXXXXXXXXXXXXXX               Y
         3 XXXXXXXXXXXXXXXXXXXXXXXXX                XXXXXXXXXXXXXXXXXXXXXXXXXHopefully the comments make sense. If you have any questions please let me know.
This assumes the column names are the same between the staging and base tables. In addition as you add more columns to this table you'll have to add more CASE statements to check the length and update the COALESCE check as necessary.
Thanks!

To increase the XMLtype column data length

Hi ,
I have created a Table with an XMLtype column , when I am checking the data length it is showing only 2000.
How can I increase the length.
DBMS_METADATA.GET_DDL('TABLE','CC_EVENT_MESSAGES','UNS_STAGING_DEV5')
CREATE TABLE "UNS_STAGING_DEV5"."CC_EVENT_MESSAGES"
   (    "SRC_SYSTEM_CD" VARCHAR2(10) NOT NULL ENABLE,
        "SRC_SEQUENCE_NUM" NUMBER NOT NULL ENABLE,
        "SRC_EVENT_NAME" VARCHAR2(255) NOT NULL ENABLE,
        "SRC_EVENT_XSD_NAME" VARCHAR2(255) NOT NULL ENABLE,
        "SRC_EVENT_DATE" DATE NOT NULL ENABLE,
        "INSERT_TS" TIMESTAMP (6) NOT NULL ENABLE,
        "PROCESSED_TS" TIMESTAMP (6),
        "STAGING_NUM" NUMBER NOT NULL ENABLE,
        "MESSAGE_STATE" VARCHAR2(10) NOT NULL ENABLE,
        "MESSAGE_FRAME" "SYS"."XMLTYPE" NOT NULL ENABLE
   ) SEGMENT CREATION IMMEDIATE
PCTFREE 0 PCTUSED 0 INITRANS 1 MAXTRANS 255
NOCOMPRESS LOGGING
STORAGE(INITIAL 1048576 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
TABLESPACE "UNS_STAGING_DEV5"
XMLTYPE COLUMN "MESSAGE_FRAME" STORE AS BASICFILE CLOB (
TABLESPACE "UNS_STAGING_DEV5" ENABLE STORAGE IN ROW CHUNK 8192 RETENTION
CACHE
STORAGE(INITIAL 65536 NEXT 65536 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT))
   CACHE
SQL> select OWNER,TABLE_NAME,column_name,data_type,data_length from dba_tab_columns where DATA_TYPE like '%XMLTYPE' and owner not in ('SYS','SYSTEM','XDB');
OWNER                TABLE_NAME           COLUMN_NAME     DATA_TYPE DATA_LENGTH
UNS_STAGING_DEV5     CC_EVENT_MESSAGES    MESSAGE_FRAME   XMLTYPE           2000

I have created a Table with an XMLtype column , when I am checking the data length it is showing only 2000.
Don't rely on this value, it's wrong.
XMLType datatype inherits the properties of its underlying LOB storage, in the present case CLOB, which can store TBs of data.

Data Length Semantics?

Dear memebers,
what is Data Length Semantics property of text box?
what's its behavior?
thanks
Muhammad Nadeem
[email protected]

Values CHAR, BYTE, null
Refer to Built-in
GET_ITEM_PROPERTY
Usage Notes
- If a null value is specified, then byte semantics will be used unless the environment variable NLS_LENGTH_SEMANTICS is set to CHAR when the form is compiled.
- When the Synchronize with Item property is set, DATA_LENGTH_SEMANTICS will be ignored in a subordinate mirror item. The DATA_LENGTH_SEMANTICS property is always taken from the master mirror item. A compiler (generator) warning will be issued if a non-null value is specified in a subordinate mirror item.
- A compiler (generator) warning will also be issued if a non-null value is specified in an item whose datatype is neither CHAR, ALPHA, nor LONG.

Check the Data length for the fields in the mapping

Hi,
I need to check for the data length of the below fields in mapping. And if any of the field lengh does not match with the given length then I discard the data and trigger a mail
X1_LENGTH = 9
EMail_LENGTH = 100
PrjDesc_LENGTH = 50
Regards,
Varun

Hi,
You can use following approach:
- Create UDF for length analysis and raise exception if length is not accurate Use lenght() method of string.
CheckLength(Field, Length)
If Field.lenght() >= Length then raise mapping exception
Use Alert to capture this and send mail.
- Use Enum while defining datatype to reject data at source (in adapter engine). Again use Alerts to send mail.
Regards,
Gourav

Bcp doesnt throw an error when the data length exceeds size of the column

Hi,
We are using bcp in SQL 2008 R2 to import the data from flat file. When the data length exceeds the size of the column, it doesn't throw any error instead it has ignored the row.
Please suggest me how to truncate and load the data into table.
Thanks,
Pasha

Hi Pasha,
According to your description, you want to import the data from flat file to SQL Server table with truncated data in SQL Server 2008 R2. To achieve your requirement, we can use Import and Export wizard. For more details, please refer to the following steps:
Launch SSMS by clicking SQL Server Management Studio from the Microsoft SQL Server program group.
Right click on the destination database in the Object Explorer, select Tasks, then Import Data from the context menu to launch the Import Wizard.
Choose Flat File Source as Data Source, then browser to the flat file.
Choose SQL Server Native Client 10.0 as Destination, then select the destination database.
Click Edit Mappings button to change column size or other properties.
Finish the processing.
For the example about how to use Import and Export wizard, please refer to the blog below:
http://www.mssqltips.com/sqlservertutorial/203/simple-way-to-import-data-into-sql-server/
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Javax.crypto.IllegalBlockSizeException: Input data length not a multiple

Hi All ,
M worknig with NWCE 7.1.1. I have written code for decryption for decryption. Earlier my web dynpro application was on CE7.1. We migrated it to CE 7.1.1 just week ago after migrating to CE 7.1.1 , on execution of decryption code m gtting as
javax.crypto.IllegalBlockSizeException: Input data length not a multiple of blocksize
i have written following code for decryption.
public String decrypt( String encryptedString, String encryptionKey )
     String UNICODE_FORMAT = "UTF8";
     try
          if ( encryptedString == null || encryptedString.trim().length() <= 0 )
               throw new IllegalArgumentException( "encrypted string was null or empty" );
            byte[] keyAsBytes = encryptionKey.getBytes(UNICODE_FORMAT);
            keySpec = new DESKeySpec(keyAsBytes);
            keyFactory = SecretKeyFactory.getInstance( "DES" );
            cipher = Cipher.getInstance( "DES" );
          SecretKey key = keyFactory.generateSecret( keySpec );
          cipher.init( Cipher.DECRYPT_MODE, key );
          BASE64Decoder base64decoder = new BASE64Decoder();
          byte[] cleartext = base64decoder.decodeBuffer( encryptedString );
          byte[] ciphertext = cipher.doFinal( cleartext );
          return new String( ciphertext );
     }catch (Exception e){
          IWDMessageManager messageManager = wdComponentAPI.getMessageManager();
          messageManager.reportException("Error while Decryption");
          e.printStackTrace();
          return "";
This code was working fine in CE 7.1 . After migrating to CE 7.1.1 it started giving this error.

Thank you for your answer
how the code is usedI have hardcoded key, example
byte[] key = "123456789abcdefg".getBytes();and String for crypt (Example, String in = "green";)
Then I encrypt string in with code above (in qwestion body) and get exception IllegalBlockSizeException: Input data length not a multiple of blocksize
String encrypt(String in) throws Exception{
String out="";
byte[] key = "123456789abcdefg".getBytes();
Cipher ecipher = Cipher.getInstance("AES");
ecipher.init(Cipher.ENCRYPT_MODE, new SecretKeySpec(key, "AES"));
byte[] utf8 = in.getBytes("UTF8");
byte[] enc = ecipher.doFinal(utf8);
out = (new sun.misc.BASE64Encoder().encode(enc)).toString();
return out;
}Clients use JRE1.4 or high. I have JRE1.4 and all work correctly. Also, many clients have 1.4, but only part of they get exception. Code is in the server (this is part of servlet)
This function run in one thread and doesn't use shared resources

The (maximum) expected data length is 6, while the returned data length is

I would like to connect the view via the OraOLEDB.Oracle' from linked server of the MSSQL and the following column couldn't be selected.
Msg 7347, Level 16, State 1, Line 2
OLE DB provider 'OraOLEDB.Oracle' for linked server 'PROD' returned data that does not match expected data length for column salary.LATEST_HIRE_DATE_STATUS'. The (maximum) expected data length is 6, while the returned data length is 4.
So I would like to change the following code from case method to decode method ? due to the view can be selected by decode method .
CASE
WHEN TRUNC (latest_hire_date) >= SYSDATE - 90
AND type_of_post = 'Temp'
THEN 'YES'
ELSE 'NO'
END
AS latest_hire_date_status,
CASE
WHEN last_day_of_duty IS NOT NULL THEN 'REJECTED'
ELSE 'PASSED'
END
AS last_day_of_duyty_status,
Edited by: user10605622 on 2012/2/8 上午 8:01

user10605622 wrote:
I would like to connect the view via the OraOLEDB.Oracle' from linked server of the MSSQL and the following column couldn't be selected.
Msg 7347, Level 16, State 1, Line 2
OLE DB provider 'OraOLEDB.Oracle' for linked server 'PROD' returned data that does not match expected data length for column salary.LATEST_HIRE_DATE_STATUS'. The (maximum) expected data length is 6, while the returned data length is 4.
So I would like to change the following code from case method to decode method ? due to the view can be selected by decode method .
CASE
WHEN TRUNC (latest_hire_date) >= SYSDATE - 90
AND type_of_post = 'Temp'
THEN 'YES'
ELSE 'NO'
END
AS latest_hire_date_status,
CASE
WHEN last_day_of_duty IS NOT NULL THEN 'REJECTED'
ELSE 'PASSED'
END
AS last_day_of_duyty_status,Not quiet sure what your problem is or what you are asking for?
There's no need to use a DECODE statement when a CASE will do the same, and more, certainly if you want to check for range values rather than equality values as in your ">= SYSDATE - 90".
Not quite sure what your error message means either. Seems to be nonesense as it says the maximum is 6 and it's getting 4, but 4 is not greater than 6 so it shouldn't be a problem.

Select Option with data length more than 45 character

Hi everyone,
Kindly suggest how to use select-option when the data type is of length 128 characters because it is truncating the input after 45 characters. The requirement is to pass 1-7 files in select option input.
Thanks in advance.

Hi,
Select option doest support STRING data type.
The VISIBLE LENGTH addition is also not working in this case. Also for multiple selection the input length remains the same i.e. 45 characters.
Thanks.

Custom validate data length 6 to 8

I have a form that requires a minimum of 6 characters and a maximum of 8. The only accepted input are lowercase letters and numbers. I am unable to find a way to validate this. I can check the length with "None" or with "Custom" I can validate the inputted data however this appears to work for fixed lengths only but not variable lengths. Is there any way to validate both at the same time. Thanks in advance.

<!doctype html>
<html>
<head>
<meta charset="utf-8">
<title>Untitled Document</title>
<script src="SpryAssets/SpryValidationTextField.js"></script>
<link href="SpryAssets/SpryValidationTextField.css" rel="stylesheet">
</head>
<body>
<span id="sprytextfield1">
<label for="text1"></label>
<input type="text" name="text1" id="text1">
<span class="textfieldRequiredMsg">A value is required.</span><span class="textfieldInvalidFormatMsg">Invalid format.</span></span>
<script>
var sprytextfield1 = new Spry.Widget.ValidationTextField("sprytextfield1", "custom", {validation:myValidation, validateOn:["blur", "change"]});
function myValidation(value) {
return /^([a-z0-9]{6,8})$/.test(value)
</script>
</body>
</html>

Reg : Data Length

Similar Messages

Maybe you are looking for