Create_portlet_definition.sql probs with UDB: field "value" too long to index

We're trying to deploy the create_portlet_definition.sql on a UDB DB2
6.1.
However, we encountered some problems:
"COLUMN_ORDER" cannot be a part of the primary key because it can contain
null values:
CREATE TABLE "COLUMN_INFORMATION"
("PORTAL_NAME" VARCHAR(100) NOT NULL,
"CATEGORY_NAME" VARCHAR(100) NOT NULL,
"COLUMN_WIDTH" INT,
"COLUMN_ORDER" INT,
PRIMARY KEY(PORTAL_NAME, CATEGORY_NAME, COLUMN_ORDER));
"GROUP_ID" cannot be a part of the primary key because it can contain
null values:
CREATE TABLE "GROUP_PERSONALIZATION"
("PORTAL_NAME" VARCHAR(100) NOT NULL,
"CATEGORY_NAME" VARCHAR(100) NOT NULL,
"PORTLET_NAME" VARCHAR(100) NOT NULL,
"GROUP_ID" VARCHAR(100),
"AVAILABLE" INT,
"MANDATORY" INT,
"EDITABLE" INT,
"MOVEABLE" INT,
"MINIMIZEABLE" INT,
"MAXIMIZEABLE" INT,
"FLOATABLE" INT,
"VISIBLE" INT,
"X" INT,
"Y" INT,
"MINIMIZED" INT,
PRIMARY KEY(PORTAL_NAME, CATEGORY_NAME, PORTLET_NAME, GROUP_ID))
Will these two columns ever contain a null value ?
Anders B. Jensen
Consultant, Research & Development
[email protected]
LEC AS
Denmark
Remove the SPAMLESS to mail me.

any value that can contain null should not be a part of the primary key ever.
I would just change the script so that the columns are not nullable - however,
somebody from weblogic should confirm that this is ok.
Filip
In article <[email protected]>,
[email protected] says...
>
We're trying to deploy the create_portlet_definition.sql on a UDB DB2
6.1.
However, we encountered some problems:
"COLUMN_ORDER" cannot be a part of the primary key because it can contain
null values:
CREATE TABLE "COLUMN_INFORMATION"
("PORTAL_NAME" VARCHAR(100) NOT NULL,
"CATEGORY_NAME" VARCHAR(100) NOT NULL,
"COLUMN_WIDTH" INT,
"COLUMN_ORDER" INT,
PRIMARY KEY(PORTAL_NAME, CATEGORY_NAME, COLUMN_ORDER));
"GROUP_ID" cannot be a part of the primary key because it can contain
null values:
CREATE TABLE "GROUP_PERSONALIZATION"
("PORTAL_NAME" VARCHAR(100) NOT NULL,
"CATEGORY_NAME" VARCHAR(100) NOT NULL,
"PORTLET_NAME" VARCHAR(100) NOT NULL,
"GROUP_ID" VARCHAR(100),
"AVAILABLE" INT,
"MANDATORY" INT,
"EDITABLE" INT,
"MOVEABLE" INT,
"MINIMIZEABLE" INT,
"MAXIMIZEABLE" INT,
"FLOATABLE" INT,
"VISIBLE" INT,
"X" INT,
"Y" INT,
"MINIMIZED" INT,
PRIMARY KEY(PORTAL_NAME, CATEGORY_NAME, PORTLET_NAME, GROUP_ID))
Will these two columns ever contain a null value ?
Anders B. Jensen
Consultant, Research & Development
[email protected]
LEC AS
Denmark
Remove the SPAMLESS to mail me.--
Filip Hanik
Software Architect
XMarkstheSpot.com
[email protected]

Similar Messages

  • P13n.ddl probs with UDB: field "value" too long to index

    We're trying to deploy the p13n.ddl on a UDB DB2 6.1.
    However, we encountered some problems:
    In UDB 6.1, an indexed column can be max 255 bytes long. So, the index
    WEBLOGIC_USER_ID_INDEX cannot be created, as the column "value" is one
    byte too long.
    CREATE TABLE WEBLOGIC_USER (userid int, property varchar(100), value
    varchar(256));
    CREATE INDEX WEBLOGIC_USER_ID_INDEX ON WEBLOGIC_USER (userid, property,
    value)
    How hard will omitting the "value" column from the index hit performance?
    All the columns in the table WEBLOGIC_USER has been indexed in one index.
    Was that done to prevent the DBMS from looking into the actual table at
    all (by looking only in the index)?
    Would it be possible to use the column as a varchar(255) or must it be
    256 chars wide? (Taking into consideration that the values at present are
    far from 256 chars.)
    Anders B. Jensen
    Consultant, Research & Development
    [email protected]
    LEC AS
    Denmark
    Remove the SPAMLESS to mail me.

    What you are trying to do shouldn't be a problem.
    There is no problems creating the weblogic_user as a varchar(255).
    I am not sure about omiting the "value" column and related performance
    issues, but I don't think it will be significant.
    "Anders B. Jensen" wrote:
    We're trying to deploy the p13n.ddl on a UDB DB2 6.1.
    However, we encountered some problems:
    In UDB 6.1, an indexed column can be max 255 bytes long. So, the index
    WEBLOGIC_USER_ID_INDEX cannot be created, as the column "value" is one
    byte too long.
    CREATE TABLE WEBLOGIC_USER (userid int, property varchar(100), value
    varchar(256));
    CREATE INDEX WEBLOGIC_USER_ID_INDEX ON WEBLOGIC_USER (userid, property,
    value)
    How hard will omitting the "value" column from the index hit performance?
    All the columns in the table WEBLOGIC_USER has been indexed in one index.
    Was that done to prevent the DBMS from looking into the actual table at
    all (by looking only in the index)?
    Would it be possible to use the column as a varchar(255) or must it be
    256 chars wide? (Taking into consideration that the values at present are
    far from 256 chars.)
    Anders B. Jensen
    Consultant, Research & Development
    [email protected]
    LEC AS
    Denmark
    Remove the SPAMLESS to mail me.

  • ServiceRequest field value too long, 2000 character max (SBL-EAI-13011)

    When I enter more than 2000 characters for a particular field - description, the update : "srequest.ServiceRequestUpdate(inset_input);"
    produces the following error:
    {System.Web.Services.Protocols.SoapException: Field 'Description' in the integration component 'Service Request' contains value 'detaidd...', which is longer than allowed length of 2000 characters.(SBL-EAI-13011)
       at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse
    Does anyone know why I am getting this 2000 character limit when I know this field should support 65k characters (65k is the max when using the ondemand website) ?
    Thanks Ahead Of Time                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

    Yeah you are correct. On OnDemand the length of this field is 16 K. This field is of Type CLOB in OnDemand
    But web services / analytics / reports doesn't support this field type and we have to restrict to length of 2000 K (This is a limitation)
    Till June that limitation was in place, I don't have the latest update. May be in some of recent patch they have corrected this.

  • EXEC SQL Error: ORA-01401: Inserted value too large for column

    Getting this SQL Error: ORA-01401: Inserted value too large for column..on an EXEC SQL Insert statement when writing to an
    external Oracle DB from SAP.
    On further analysis..it appears that this happens to the fields..when the string length matches the field length.
    Example:  Plant field is defined as char(4) on the SAP side and it is a Varchar2(4) on the Oracle side.
    When a value like '1015' is passed thru a variable in the insert statement then this ORA-01401 error pops up.
    No error:
       - if the value '1015' is passed directly in the insert statement to the external table  (or)
       - when a value with 3 chars or less(like the first three chars..101) is passed thru a variable  defined as 'Plant(4) type c'.
       - when using EXEC sql within SAP
       - when reading from the external db table
    This was working ok until the  Oracle Patch P9147110 was installed recently.
    Any suggestions !

    Hello Dvas,
    what's the characterset of your external database?
    What's the column definition in your external database (byte or character based)?
    If you use a characeterset like UTF8 it is possible, that one character needs more than one byte and then you will run into such kind of issues if the definition is too small.
    Regards
    Stefan

  • Unable to evaluate workflow rule - Value too long for field

    Need help with a workflow error for a record update before the record is saved. There are 3 calculations that would be done in a particular order - all on number fields. Each time, I am overwriting existing values. The individual numbers could have up to 6 decimal spaces. When I try to update one or more fields that contain the calculation, I get an error message saying that the system is unable to evaluate the workflow rule - value too long for field (zNum6).
    This same calculation is fine when a new record is entered and the calculation is done as a default field value.
    Any ideas?

    I actually had to use a ToChar function at the beginning of the calculation and #### to indicate the number of digits to make this work. Oracle Help Desk provided the answer - quickly.

  • FRM-40831: Value too long for field ROWID.

    Hi,
    I'm a newbie in forms and I've a problem when working with index organized tables, it post me this error:
    FRM-40831: Truncation occurred : Value too long for field ROWID.
    How can I solve this problem?
    Thanks for your help.
    Raúl

    This is a bug in Forms 9i (bug 2408210). The workaround is to:
    - change block property Key Mode to Updatable or Non-Updatable
    - set item property Promary Key to Yes for all items that correspond to an index column in the index-organized table

  • Large XML Publisher reports fail with client-error-request-value-too-long

    We are running BI Publisher 5.6.3 with Oracle Applications 11.5.10.2 (ATG.H RUP 5), and are having frequent failures with client-error-request-value-too-long messages on large PDF reports that cause the entire report to not print.
    The exact error message is as follows:
    lp: unable to print file: client-error-request-value-too-long
    Pasta: Error: Print failed. Command=lp -c -dPDX_B6_1LJ5200NEAST /logs/temp/pasta3262_0.tmp
    Pasta: Error: Check printCommand/ntPrintCommand in pasta.cfg
    Pasta: Error: Preprocess or Print command failed!!!
    APP-FND-00500: AFPPRN received a return code of failure from routine FDUPRN. Program exited with status 1
    Cause: AFPPRN received a return code of failure from the OSD routine FDUPRN. Program exited with status 1.
    Action: Review your concurrent request log file for more detailed information.
    I have Google'd client-error-request-value-too-long, and found it is a common CUPS issue on Linux. The popular solutions (having /var/spool/cups and /var/spool/cups/tmp) are already in place. Also, the temp files are nowhere near 2 GB (44MB).
    Has anyone had this issue with BI Publisher on Linux?

    Thanks for the link. It looks like the sysadmins have throttled cups to low to allow large bitmapped print jobs:
    grep MaxRequestSize cupsd.conf
    # MaxRequestSize: controls the maximum size of HTTP requests and print files.
    MaxRequestSize 10M
    I am trying to get a more reasonable size limit.

  • Large BI Publisher reports fail with client-error-request-value-too-long

    We are running BI Publisher 5.6.3 with Oracle Applications 11.5.10.2, and are having frequent failures with client-error-request-value-too-long messages on large PDF reports that cause the entire report to not print.
    The exact error message is as follows:
    lp: unable to print file: client-error-request-value-too-long
    Pasta: Error: Print failed. Command=lp -c -dPDX_B6_1LJ5200NEAST /logs/temp/pasta3262_0.tmp
    Pasta: Error: Check printCommand/ntPrintCommand in pasta.cfg
    Pasta: Error: Preprocess or Print command failed!!!
    APP-FND-00500: AFPPRN received a return code of failure from routine FDUPRN. Program exited with status 1
    Cause: AFPPRN received a return code of failure from the OSD routine FDUPRN. Program exited with status 1.
    Action: Review your concurrent request log file for more detailed information.
    I have Google'd client-error-request-value-too-long, and found it is a common CUPS issue on Linux. The popular solutions (having /var/spool/cups and /var/spool/cups/tmp) are already in place. Also, the temp files are nowhere near 2 GB (44MB).
    Has anyone had this issue with BI Publisher on Linux?

    The linux sysadmins set the cups max_request_size at 10 MB, which was causing this error. Once the restriction was lifted, the reports ran without error.

  • Arrow mark with kunnr field values in alv output.

    Hi ,
    I  need to increase the column field length. I am using Function Module REUSE_ALV_LIST_DISPLAY because alv_grid display fm is not available in 4.0b version. I have used column optimization in layout. The column kunnr is coming with a small arrow though there is no data loss. Is there any way I can remove the arrow mark with kunnr field values.

    Hi,
    You can increase your column lenght in fieldcat by using Fcat-columnwidth = "SIZE OF KUNNR ".
    Set the size of kunnr field in fieldcat and get the appropiate output.
    Regards
    Abdul

  • How to find roles with open field values

    Hello SAP gurus,
    I need to find a way to find roles with open field values. Some kind of report that returns me a list of all roles that, despite having a generated profile, it still contains empty field values in it.
    Is there anything like it available on SAP?
    Thanks
    Antonio

    Some kind of report that returns me a list of all roles that, despite having a generated profile, it still contains empty field values in it
    Hey I am not sure, but seems I might have seen some report like that. Can you try search report named PFCG* / PFUD*
    Again this is either report (SE38/SA38) or may be FM (SE37). I am away from system a bit while and can't recall.
    Regards,
    Arpan Paik

  • SQL Error: ORA-01704: string literal too long

    select * from table(fn_split('some 10000 characters with comma separation .........................'))
    Error report:
    SQL Error: ORA-01704: string literal too long
    01704. 00000 - "string literal too long"
    *Cause:    The string literal is longer than 4000 characters.
    *Action:   Use a string literal of at most 4000 characters.
    how to pass my 10k record string

    933663 wrote:
    The string is through a user interface.So, that interface is using what datatype for the string? What language is the interface written in?
    insert into table
    select * from table(fn_split('2,4,2,5,7'));Do you understand what a string literal is? You cannot provide a varchar2 string that exceeds 4000 bytes from within SQL. Fact. It just cannot be done.
    If you are passing the string from a user interface using a datatype that supports more than 4000 bytes, and you pass it directly to PL/SQL code by calling the function or procedure directly (not using SQL) then you can use up to 32767 bytes for your VARCHAR2.
    The code you've posted (which happens to be some of my own code posted years ago on these forums) takes a VARCHAR2 as an input. You would have to change that to accept a CLOB datatype and work on the CLOB instead. However, you still wouldn't be able to pass in a string literal of more than 4000 bytes from SQL for it.
    Looking at your other thread: Seperate the string value
    ... it looks like the 'user' is trying to pass in a table definition. What is it your application is trying to do? Surely you are not trying to create a table at run time?
    So explain, what is the business issue you are trying to solve? We may be able to provide a better way of doing it.

  • FCC error :java.lang.Exception: Column value '   ' too long

    Hi all,
    I am using FCC on receiving File adapter...
    While executing i am getting this error in CC monitor
    com.sap.aii.af.ra.ms.api.RecoverableException: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'java.lang.Exception: Column value '   ' too long (>1 for 2. column) - must stop',
    i searched in SDN but no luck till now..
    Plz help me out..
    Thanx in advance.

    Hi,
    Check ur FCC parameters,
    File content conversion sites
    /people/venkat.donela/blog/2005/03/02/introduction-to-simplefile-xi-filescenario-and-complete-walk-through-for-starterspart1
    /people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2
    /people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
    /people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
    /people/shabarish.vijayakumar/blog/2005/08/17/nab-the-tab-file-adapter
    /people/venkat.donela/blog/2005/03/02/introduction-to-simplefile-xi-filescenario-and-complete-walk-through-for-starterspart1
    /people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2
    /people/venkat.donela/blog/2005/06/08/how-to-send-a-flat-file-with-various-field-lengths-and-variable-substructures-to-xi-30
    /people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
    /people/shabarish.vijayakumar/blog/2005/08/17/nab-the-tab-file-adapter
    /people/jeyakumar.muthu2/blog/2005/11/29/file-content-conversion-for-unequal-number-of-columns
    /people/shabarish.vijayakumar/blog/2006/02/27/content-conversion-the-key-field-problem
    /people/michal.krawczyk2/blog/2004/12/15/how-to-send-a-flat-file-with-fixed-lengths-to-xi-30-using-a-central-file-adapter
    /people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
    http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm
    Regards,
    Phani.
    Reward points if Helpful

  • Column value '        ' too long - must stop', probably configuration error

    Hi Experts,
    I have a Proxy to File Scenario when I execute it I get this error in RWB. Can you please help me on this:
    Message processing failed. Cause: com.sap.aii.messaging.adapter.trans.TransformException: Error converting Message: 'java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'java.lang.Exception: Column value '        ' too long - must stop', probably configuration error in file adapter (XML parser error)''; nested exception caused by: java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'java.lang.Exception: Column value '        ' too long - must stop', probably configuration error in file adapter (XML parser error)'
    Thanks
    Srikanth E

    Hi,
    if there is any empty tag coming from source then target structure tag will not be created and because of which ur payload structure and FCC configuration is not matching.
    To use map with default between source and target strcture so in case source tag dont have value target structure will be created because of mapwithdegfault fuction and ur FCC will not fail.
    Open SXMB_MONI output payload and compare the structre with Data type u will se for no source value target tag is not created at all and FCC is failed.
    please refer below thread,
    0 byte txt file using receiver File Adapter
    regards,
    ganesh.

  • Client-error-request-value-too-long

    What is this error???? I am trying to add an Epson 1280 printer and I get this error. I have the most current driver and not sure why this isn't working.

    My flatmate had this "client-error-request-value-too-long" problem with her (powerpc) powerbook. Nearly everything I tried didn't work:
    1) Reinstalling drivers
    2) Permissions repair
    3) Resetting print system using Fixamac's Printer Setup Repair Utility
    4) Updating from 10.4.10 to 10.4.11
    5) Using the command line to try and recreate the directory: /var/spool/cups/tmp (which told me it already existed)
    6) Using Transmit (with show invisible files turned on) to browse to /var/spool/cups/ and try and recreate the tmp folder
    On the last point I couldn't change anything about the /var/spool/cups/ directory because the permissions were corrupted in some way. It keep telling me tmp already existed but I couldn't see it.
    In the end what did work was enabling and logging in as root, browsing to /var/spool/ using Transmit and deleting the cups folder and then recreating. It took a few tries to delete too, but in the end I managed to remove it.
    Of course I wouldn't actually recommend this. I'm no Unix geek so god knows what I might have broken in the process, so I'm going to reinstall her system with the Archive and Install options when I get a chance, which is what I'd recommend doing in the first place to anyone having this problem.

  • FRM-40831 : Truncation occured: value too long for filed MAST_EMP_NAME

    Hi
    I'm using Forms 5 and getting following error.
    FRM-40831 : Truncation occured: value too long for filed MAST_EMP_NAME.
    When i checked in the column Mast_emp_name, all the values are with in the limit.
    Table contains some 9 lacs record.
    Please help me. this is very urgent

    check the maximum length - property of all those 5 columns in your form. They have to be as long as in the database. Except number. They have to be 1 char longer than in the db.
    Forms-Online-Help says:
    This property can potentially limit the amount of data that an item is allowed to contain internally (in the Forms server) when it's in native format. It can also potentially limit the number of character (or bytes) displayed or entered by the end user. That is, it can specify a data limit and/or a user interface (UI) limit. The exact effect depends upon several factors, including the item's Data type, Data Length Semantics, and Format Mask properties. For a character item (datatypes CHAR, ALPHA, LONG), the Maximum Length property specifies a data limit. The property value specifies either the maximum number of bytes or else the maximum number of characters, depending upon the value of the Data Length Semantics property. Within a group of character mirror items, the Maximum Length property is always taken from the master mirror item. A compiler (generator) warning is issued if a non-zero non-default value is specified in a subordinate mirror item. If a character item has no format mask (the Format Mask property is null), then the Maximum Length property (taken from the master mirror item) also specifies a UI limit. When the Forms server is using the UTF8 character set , this UI limit has the same semantics (byte versus character) as the data limit. When the Forms server is using a multi-byte character set other than UTF8, and the Data Length Semantics property specifies byte semantics, Forms cannot prevent the end user from typing in too many bytes. Instead, it uses character semantics for the UI limit. In such a case, the end user is allowed to type in too many bytes. When the end user attempts to navigate out of the current validation unit, one of two things will happen. If the application property FLAG_USER_VALUE_TOO_LONG is set, an error will be flagged and the excess characters on the right will be selected. If this application property is not set, the excess characters will be quietly truncated, and the navigation will succeed. If a character item has a format mask, then the item's UI limit is derived from the format mask. This limit is always a character limit. For a number item (datatypes NUMBER, INT, MONEY, RNUMBER, RINT, RMONEY), the Maximum Length property specifies a user interface limit. This limit is always a character limit. There is no data limit. The data item can always internally hold up to 23 bytes (which is the maximum size of an Oracle number in native format), regardless of the value of the Maximum Length property. For a date or time item (datatypes DATETIME, DATE, TIME, JDATE, EDATE), the Maximum Length property specified in Forms Builder has almost no effect (See the Query Length property for a discussion of the only effect). As with "number" items, there is no data limit. For DATE and DATETIME items, the internal value is 7 bytes long, and for TIME, JDATE and EDATE items, the internal value is 4 bytes long . The user interface limit is derived from the format mask. This limit is always a character limit which is what is returned by GET_ITEM_PROPERTY(item, MAX_LENGTH).

Maybe you are looking for