Output columns too long

Hi,
I've a join over two tables with about 150 columns. This was never a problem.
Now I have two MAXDB databases from two customers (7.6.06.03). In one of them my statement says "output columns too long", running the same application on the second db works fine.
Any ideas?
I guess there is a problem with maximum record length of about 8000 bytes. Can this be extended in any way?
Any help will be appreciated.

>
Christoph Schwerdtner wrote:
> Thank you all for your help.
>
> In fact I tried even further. I fixed the current problem by reducing the amount of some columns and also I did a redesign of to user functions. Output was 1000 chars, i reduced it to 200. Now it works fine.
> I realized that SQLStudio has more restrictions than my own ODBC connection from inside my application.
> Statements that doesn't work with SQLStudio are running without problems from my app.
> Strange things are going on...
Hmm.. this sounds a bit odd.
Do you use prepared statements in your application?
Concerning the change of limitations, just compare the documentation
[Restrictions for 7.6|http://maxdb.sap.com/doc/7_6/f6/069940ccd42a54e10000000a1550b0/content.htm]
>>> Internal length of a table row: 8088 bytes
[Restrictions for 7.7|http://maxdb.sap.com/doc/7_7/45/470c541fb54e2de10000000a114a6b/content.htm]
>>> Internal length of a table row: 32767 Bytes
@Lars Breddemann: do you suggest to move to 7.7? Are there any problems? How do i the update?
Yes, absolutely.
7.7 has been out for years now and it's pretty stable.
To perform the upgrade, I'd go for simply using SDBSETUP.
Alternatively you may use SDBUPD (textbased interface).
Ok, now you've got a project for the early days in 2011
Have a nice holiday season!
Lars

Similar Messages

Text in column too long to display

I've 2 column that contain text. I wish to show both the columns full text along with other column in a single page. Text to show up in a few lines is expected. Hope someone can give me a clue.
Thanks

Hi Ranjeeth,
For example I have 5 columns to show up. Column 3 and 4 contains text that have 50 char set to them. View limit is 80 chars. I wish to have the view to show all the columns, each record can be in more than 1 row. Is this possible?

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.

Limitation for CLOB columns? - ORA-01704: string literal too long

Hello!
I'm trying to update a CLOB column with more than 35000 characteres, but I get "ORA-01704: string literal too long".
The code:
declare
l_clob clob;
begin
update test set test = empty_clob()
WHERE ID = 1
returning test into l_clob;
dbms_lob.write( l_clob, length('A...here 35000xA...A'), 1,'A...here 35000xA...A');
end;
Is there any limitation for CLOB columns?
Thanks for help.
Daniel

user605489 wrote:
32768 characteres :)Actually it's 1 character less than 32K...
*32767*
SQL> declare
2 v_vc varchar2(32768);
3 begin
4 null;
5 end;
6 /
v_vc varchar2(32768);
ERROR at line 2:
ORA-06550: line 2, column 17:
PLS-00215: String length constraints must be in range (1 .. 32767)
SQL>I guess it comes from a legacy thing where signed words (2 bytes) are/were used to represent a value. As the most significant bit of the word is used to represent the sign of the number the range goes from -32768 to 32767.

How to Update a clob column..it gives error string literal too long

I am trying to update a clob column of a table but it gives error string literal too long plz tell me what's the issue
ORA-01704: string literal too long

Peeyush wrote:
I am trying to update a clob column of a table but it gives error string literal too long plz tell me what's the issue
ORA-01704: string literal too longThere's a problem with my car. It won't start. Why won't it start? Please tell me!
Oh wait, you can't, because I haven't given you nearly enough information...
In other words, if you would like help in trying to work out where you've gone wrong, you should provide a small enough example of your code that demonstrates the error. We might then actually stand a chance of being able to help you!

Importing a table with a BLOB column is taking too long

I am importing a user schema from 9i (9.2.0.6) database to 10g (10.2.1.0) database. One of the large tables (millions of records) with a BLOB column is taking too long to import (more that 24 hours). I have tried all the tricks I know to speed up the import. Here are some of the setting:
1 - set buffer to 500 Mb
2 - pre-created the table and turned off logging
3 - set indexes=N
4 - set constraints=N
5 - I have 10 online redo logs with 200 MB each
6 - Even turned off logging at the database level with disablelogging = true
It is still taking too long loading the table with the BLOB column. The BLOB field contains PDF files.
For your info:
Computer: Sun v490 with 16 CPUs, solaris 10
memory: 10 Gigabytes
SGA: 4 Gigabytes

Legatti,
I have feedback=10000. However by monitoring the import, I know that its loading average of 130 records per minute. Which is very slow considering that the table contains close to two millions records.
Thanks for your reply.

FCC Receiver Error :Column value '   ' too long

Hi Experts
I am getting data from SAP for which i should create a file which is fixed length on the target side
My structure is :
File----1.....Unbound
----->Header --- -1..1
>RecordType
>Transcode
>PO_Num
>Vend_ID
>Crea_date
>WHS_ID
>POM_Status
>Cancel_date
>Delv_date
>Ord_type
>POM_Char
---->Record_Detail---1..Unbound
>Record_typ
>PO_Num
>Line_no
>Itm_no
>Sch_No
>QTY
>UOM
>Vend_itm_no
>Delv_Date
>Buyer_name
>WHS_ID
---->var1-0..1
---->var2-0..1
var1 and var2 I am using for variable substitution.
I have configured the receiver FCC as below
Record Structure HeaderRecord,Record_Detail
HeaderRecord.fieldFixedLengths     1,1,30,10,8,2,1,8,8,8,1
Record_Detail.fieldFixedLengths     1,30,5,30,3,8,2,20,8,25,2
And I have given var1 and var2 in varaible substitution.
But I am getting the following error when recevier receiving the file
Could not process due to error: java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'java.lang.Exception: Column value '0811200613.WAPONUM' too long (>1 for 0. column) - must stop', probably configuration error in file adapter (XML parser error)'
Please help me
Regards
Sowmya

Hi,
If u have added Trailer Node ( And Var1 & Var2 inside it) then try adding this:
Trailer.fieldFixedLengths     0,0
Trailer.fixedLengthTooShortHandling     Cut
Hope it will solve ur problem.
For reference check:
http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
Check ur final structure is like this:
Recordset Structure: File,Header,Record_Detail,Trailer
Header.fieldFixedLengths: 1,1,30,10,8,2,1,8,8,8,1
Header.fieldNames: RecordType,Transcode,PO_Num,Vend_ID,Crea_date,WHS_ID,POM_Status,Cancel_date,Delv_date,Ord_type,POM_Char
Record_Detail.fieldFixedLengths: 1,30,5,30,3,8,2,20,8,25,2
Record_Detail.fieldNames: Record_typ,PO_Num,Line_no,Itm_no,Sch_No,QTY,UOM,Vend_itm_no,Delv_Date,Buyer_name,WHS_ID
Trailer.fieldFixedLengths: 0,0
Trailer.fieldNames: var1,var2
Trailer.fixedLengthTooShortHandling: Cut
File.fieldSeparator: 'nl'
Thanks,
Mahi
Edited by: Maheshwari Morbale on Nov 21, 2008 6:33 AM

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 Name too long

While loading the data from XML source I am getting following error
ORA-00972: identifier is too long
I understand that some of the Column name are more then 30 char (Oracle Limit) inmy source but I like to know what needs
to be modified in the IKM to pick only first thirty characters of column name in case of column name is more then 30 Char.
The LKM works fine as it take only the first 30 char to create the table name, I think it take that setting from topology manger.
but what need to modify in IKM to take only first 30 char for column name.
I am creating target table on the fly and I dont wanna modify each column name in the target table, It'll be alot of work for me.
Please let me know your thoughts on this.
Thanks

Yes its erroring out for IKM step for creating target table.
The step is ignoring the error on Create Target Table because of following error
972 : 42000 : java.sql.SQLException: ORA-00972: identifier is too long
java.sql.SQLException: ORA-00972: identifier is too long
ofcourse the column name is longer then Oracle limitation that is 30 Chars.
In the next step for inserting data it is also failing because of same error.
LKM steps work fine as it strip the column name longer then 30 char.

Sort key too long - maximum number of columns in select statement

the sort key too long is caused by either too many group
functions or too many columns selected. Does anyone know the
maximum number of columns that can be selected in one statement ?

The Oracle 9i reference states ...
The GROUP BY expression and all of the
nondistinct aggregates functions (for example,
SUM, AVG) must fit within a single database
block.
... and the Oracle 9i SQL Reference states that ...
An order_by_clause can contain no more than 255
expressions.
You could check your own documentation, but i think it will
be the same.

Imp-00020 long column too large for column buffer size (22)

Hi friends,
I have exported (through Conventional path) a complete schema from Oracle 7 (Sco unix patform).
Then transferred the export file to a laptop(window platform) from unix server.
And tried to import this file into Oracle10.2. on windows XP.
(Database Configuration of Oracle 10g is
User tablespace 2 GB
Temp tablespace 30 Mb
The rollback segment of 15 mb each
undo tablespace of 200 MB
SGA 160MB
PAGA 16MB)
All the tables imported success fully except 3 tables which are having AROUND 1 million rows each.
The error message comes during import are as following for these 3 tables
imp-00020 long column too large for column buffer size (22)
imp-00020 long column too large for column buffer size(7)
The main point here is in all the 3 tables there is no long column/timestamp column (only varchar/number columns are there).
For solving the problem I tried following options
1.Incresed the buffer size upto 20480000/30720000.
2.Commit=Y Indexes=N (in this case does not import complete tables).
3.first export table structures only and then Data.
4.Created table manually and tried to import the tables.
but all efforts got failed.
still getting the same errors.
Can some one help me on this issue ?
I will be grateful to all of you.
Regards,
Harvinder Singh
[email protected]
Edited by: user462250 on Oct 14, 2009 1:57 AM

Thanks, but this note is for older releases, 7.3 to 8.0...
In my case both export and import were made on a 11.2 database.
I didn't use datapump because we use the same processes for different releases of Oracle, some of them do not comtemplate datapump. By the way, shouldn't EXP / IMP work anyway?

IMP-000200: long column Too larege for column buffer size 22

IMP error: long column too large for column buffer size
IMP-000200: long column Too larege for column buffer size <22>
imp hr/hr file=/home/oracle/hr.dmp fromuser=hr touser=hr buffer=10000 and try also 100000000
and still the same error please any body can help me with detials please

Providing more information/background is probably the wise thing to do.
Versions (databases, exp, imp), commands and parameters used - copy&paste, relevant part of logs - copy&paste, describe table, etc.
Some background, like what's the purpose, did this work before, what has changed, etc.
Also you might check the suggested action for the error code per documentation:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14219/impus.htm#sthref10620
Edited by: orafad on Dec 5, 2010 7:16 PM

4.2 Import Faild ORA-06550: line 3, column 1: PLS-00114: identifier 'WWV_FLOW_API#REMOVE_RESTFUL_SE' too long

Execution of the statement was unsuccessful. ORA-06550: line 3, column 1: PLS-00114: identifier 'WWV_FLOW_API#REMOVE_RESTFUL_SE' too long
begin wwv_flow_api#remove_restful_service ( p_id => 13033226431752970 + wwv_flow_api.g_id_offset ,p_name => 'oracle.example.hr' ); null; end;
ORA-06550: line 3, column 1: PLS-00114: identifier 'WWV_FLOW_API#REMOVE_RESTFUL_SE' too long

i'm having the same problem as well.. here's my context:
Apex 4.2.2.00.11 Oracle 11g
we're in the midst of upgrading from 4.0
we have an apex 4.0 runtime only instance in production.
each night, we restore the the oracle instance with 4.0 to another instance and run a script to upgrade to 4.2.2 full function (development plus runtime) on this restored instance,. it has about 20-some workspaces, each with one app.
on the restored instance, yesterday i created a new workspace, gave it access to a couple of schemas, defined a couple of users. i imported a couple of apps, themes, css, images, etc. from our current development instance, which is 4.0. after this import, i was able to do development stuff with the app just fine.
so i exported the workspace yesterday, in anticipation of importing it this morning after the nightly refresh.
refresh ran, i logged in this morning as the apex admin user, and try to import the workspace. and get the
2. Re: 4.2 Import Faild ORA-06550: line 3, column 1: PLS-00114: identifier 'WWV_FLOW_API#REMOVE_RESTFUL_SE' too long
message.

[ SOLVED ] [ bar ] xtitle output too long, covers other parts

Setup:
bspwm
bar
I followed bspwm for dummies and everything is working great except the fact that window titles very often are too long to fit into the space between workspace names and other stuff on the rigtht.
Normal:
Not normal:
Is there any way to truncate it to a certain length?
Update:
I upgraded xtitle a bit and added a new command line option for this. Everything works as expected now.
Last edited by GM (2014-01-16 22:11:19)

Welp guys, it wasn't alsa at all actually. More of a PEBKAC actually. Somehow, my cable for my headphones wasn't plugged all the way in to my computer. Thanks anyways!

Report script taking too long

My report script execution time is too long - Previously it used to complete with in 5 mins when costcenter was in page def not being in rows, but the business requirements changed and we need data corresponding to level zero cost cnetr in row def,
I have tried optimizing databuffer size (increased to 100k) and sorbuffer size but the script takes too long to complete can some bosy review the report def and see am i missing anything its on prod enviroment it is a beffy env with quad processors and 8 gb ram
/ESS_LOCALE English_UnitedStates.Latin1@Binary
// Report Script Name - FY09 Extract
<ACCON
<SUPSHARE
{TABDELIMIT}
{DECIMAL 9}
<QUOTEMBRNAMES
{SUPEMPTYROWS}
{SUPMISSINGROWS}
{SUPZEROROWS}
{MISSINGTEXT "0"}
{ROWREPEAT}
{NOINDENTGEN}
<SPARSE
<PAGE("Years","Project","Currency")
<COLUMN("Time Periods")
<ROW("Accounts","Entity","SubAccount","Cost Center")
// Page Members
// Selection rules and output options for dimension: Years
{OUTMBRNAMES}
"FY-2009"
// Selection rules and output options for dimension: Currencies
{OUTMBRNAMES}
"Local"
// Selection rules and output options for dimension: Project
{OUTMBRNAMES}
"Project"
// Column Members
// Selection rules and output options for dimension: Time Periods
{OUTMBRNAMES}
"Feb"
"Mar"
"Apr"
"May"
"Jun"
"Jul"
"Aug"
"Sep"
"Oct"
"Nov"
"Dec"
"Jan"
// Row Members
// Selection rules and output options for dimension: Account
"LEV0,Accounts"
// Selection rules and output options for dimension: Entities
"LEV0,Entity"
// Selection rules and output options for dimension: SubAccount
"LEV0,SubAccount"
// Selection rules and output options for dimension: CostCenter
"LEV0,Cost Center"
// End of Report

There's probably no silver bullet for this beast. Going to level 0 on 4 dimensions is going to be tough in the reporting engine. You could probably get some improvement by using the link approach rather than the Lev0 approach.
The only other way I could think of is taking the report and breaking it into different sections for one of the smaller row dimensions, but it doesn't look like the ones you listed fit that category (they all appear to have more than a handful of members).
One note: I don't think you need to list the {OUTMBRNAMES} for each dimension up top, but that's cosmetic and you might want it that way (to change one without affecting the others later).
The reason the report will run for a long time is that it has to build a row index up front so they can be sorted, even if you don't request a sort. You could try SORTNONE, but I don't think it removes the step entirely from the sequence so the report engine burns a lot of timing creating the row indexes anyway.

Output columns too long

Similar Messages

Maybe you are looking for