ORA-28234 - Key length too short

What would cause ORA-28234 to be raised by the show engine? I occasionally get this error during development, quite random and not reproducible.
Thanks

Something like that. Like I said, it is very inconsistent, not reproducible at all. The app doesn't have a login page, it uses the mod_ntlm and associated page sentry function, the same function my app (24317) on the hosted site uses.
What is your diagnosis, Dr. Scott? :-)

Similar Messages

Key Lenght too short error with dbms_crypto.encrypt

Hi Friends,
I am getting above mentioned error with dbms_crypto.encrypt.
I had created a thread in technology --> security forum but i am not getting any help from there.
ORA-28234 Key Length too short with dbms_crypto.encrypt
Appreciate if anyone help me resolve this issue.
Thanks
AT

Hi Warren,
Yes function is compiled without any compilation error.
Thanks
AT

ORA-09100 specified length too long for its datatype with Usage Tracking.

Hello Everyone,
I'm getting an (ORA-09100 specified length too long for its datatype) (a sample error is provided below) when viewing the "Long-Running Queries" from the default Usage Tracking Dashboard. I've isolated the problem to the logical column "Logical SQL" corresponding to the physical column "QUERY_TEXT" in the table S_NQ_ACCT. Everything else is working correctly. The logical column "Logical SQL" is configured as a VARCHAR of length 1024 and the physical column "QUERY_TEXT" is configured as a VARCHAR2 of length 1024 bytes in an Oracle 11g database. Both are the default configurations and were not changed.
In the the table S_NQ_ACCT we do have record entries in the field "QUERY_TEXT" that are of length 1024 characters. I've tried various configuration such as increasing the the number of bytes or removing any special character but without any sucess. Currently, my only possible workaround is reducing the "Query_Text" data entries to roughly 700 characters. This makes the error go away. Additional point my character set to WE8ISO8859P15.
- Any suggestions?
- Has anyone else ever had this problem?
- Is this potentially an issue with the ODBC drive? If so, why would ODBC not truncate the field length?
- What is the maximum length supported by BI, ODBC?
Thanks in advance for everyones help.
Regards,
FBELL
*******************************Error Message**************************************************
View Display Error
Odbc driver returned an error (SQLExecDirectW).
Error Details
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 17001] Oracle Error code: 910, message: ORA-00910: specified length too long for its datatype at OCI call OCIStmtExecute: select distinct T38187.QUERY_TEXT as c1 from S_NQ_ACCT T38187 order by c1. [nQSError: 17011] SQL statement execution failed. (HY000)
SQL Issued: SELECT Topic."Logical SQL" saw_0 FROM "Usage Tracking" ORDER BY saw_0
*******************************************************************************************

I beleieve I have found the issue for at least one report.
We have views in our production environment that call materialized views on another database via db link. They are generated nightly to reduce load for day-old reporting purposes on the Production server.
I have found that the report in question uses a view with PRODUCT_DESCRIPTION. In the remote database, this is a VARCHAR2(1995 Bytes) column. However, when we create a view in our Production environment that simply calls this materialized view, it moves the length to VARCHAR2(4000).
The oddest thing is that the longest string stored in the MV for that column is 71 characters long.
I may be missing something here.... But the view that Discoverer created on the APPS side also has a column length for the PRODUCT_DESCRIPTION column of VARCHAR2(4000) and running the report manually returns results less than that - is this a possible bug?

Ora-06502: variable length too long on report query xml schema download

on shared components/report queries/edit report query/
and downloading my queries in xml schema format (radio button).
Get
ORA-06502: PL/SQL: numeric or value error: raw variable length too long
when i click the download button.
EDIT:
i want to add that i recently changed several columns in the database from 150 to 3000 chars long.
Edited by: Manny Rodriguez on Oct 11, 2011 7:19 AM

"4000 bytes is the ultimate maximum. you can say 4000 *characters* , but it'll always be limited to 4000 *bytes* . "
http://asktom.oracle.com/pls/apex/f?p=100:11:0::::P11_QUESTION_ID:1224836384599#201073000346459201\
"The maximum length of the column is determined by the national character set definition. Width specifications of character data type NVARCHAR2 refer to the number of characters. The maximum column size allowed is 4000 bytes."
http://docs.oracle.com/cd/E11882_01/server.112/e26088/sql_elements001.htm#SQLRF50976
By the way, you're treating your numbers as STRINGS, remove the quotes around your zero's.

Channel length too short for calculation

I've just switched from 9.1 to 2010 and I was told that our VBS scripts wouldn't need updating - not so it seems.
I have the following piece of code:
Call ChnAlloc("Input PSD")
L1=Cno("RealPart")
L2=Cno("ImaginaryPart")
Call FormulaCalc("Ch('Input PSD'):=Ch(L1)^2+Ch(L2)^2")
but this doesn't work anymore. I get an error message saying that channel 7 (Input PSD) is too short for calculation. Previously I would have checked the data matrix but I can't find this anymore so I assume DIAdem works in a different way know. The help files suggest that the channel length option for ChnAlloc is optional so I don't understand why it thinks the channel is too short.
Any help appreciated.
Thanks, Si.

Hi SI,
You only need a minor addition, and you get the benefit that all new channels can have their length(s) dynamically changed. Please add this line of code after creating the channel and before the FormulaCalc() command:
ChnLength("Input PSD") = NeededNumberOfRows
Back in the dark days of the DIAdem memory matrix, DIAdem would by default launch with 60 static channels of exactly 8196 rows each. As you apparently know, you could customize the memory matrix to have fewer or more channels, and you could change their static lengths assigned when DIAdem launched. The fully dynamic channel lengths are a vast improvement, but it does mean that for FormulaCalc() commands you need to tell the channel to be big enough first. Interestingly, none of the ANALYSIS commands require you to do explicitly set the channel length before writing to them-- just the channel calculator.
Ask if you have any further trouble,
Brad Turpin
DIAdem Product Support Engineer
National Instruments

Multiple 30" Cinema Displays, cable length too short

I have two 23" Cinema Displays, and they work great! Power adapters have long clean leads and can put them away from my G5 and place the displays where I want. Then I bought a 30" Cinema Display to try in prep for a "Nehalem" machine. I discovered that the power adapter has to be 6 inches away from the back of the computer and the monitor cable is SHORT. I want to use two 30" displays, but the cables are too SHORT and I don't want those two white bricks (power adapters) behind a new Nehalem. Apple says you can run up to eight 30" displays, with the necessary video cards, but no mention how to reach the second display let alone the 8th display!! Does Apple have cables in a male-female configuration? I have looked at Gefen.com and their extensions are Male-Male for the Apple Combo Extension Cables for dual link (30"). I could say demeaning things right now, but I won't.

Thank you for the quick reply, I can place the power adapter where I want with your solution. You would have posted if you knew about an extension with an "elegant breakout for connection to DVI, USB and FireWire ports" but I will still ask if you know of that kind also so that all monitors have USB and FireWire.

IMovie '09 dv video capture clip length too short

I have a Sony DV video camera connected to my Mac with a firewire cable. When I do a video capture on most of my videos, everything is fine. On others, it captures about 1000 unique video clips for a minute or two of video. I get 1000 clips ranging from 0.1 seconds to maybe 1.5 seconds in length. Has anyone seen this? Any ideas whats causing it?

You can always download the free trial version of Veescope Live and try capturing with that. Just connect your camera to your computer, start Veescope Live, click the camera input, press play on your camera and then press the record button on Veescope Live.

ORA-06502: PL/SQL: numeric or value error: raw variable length too long

Hi All,
Oracle 9.2.0.1.0 and Oracle 10g.
I the following procedure:
CREATE OR REPLACE TYPE Resource_TT AS TABLE OF RAW(16)
CREATE OR REPLACE PROCEDURE GET_ROLEMAPPING_Temp
RoleIds IN NVARCHAR2 DEFAULT NULL ,
Application IN NVARCHAR2 DEFAULT NULL ,
MappingExixts OUT NVARCHAR2
AS
     v_Application NVARCHAR2(150) := Application;
     resource_list CONSTANT Resource_TT := Resource_TT(RoleIds);
     v_temp NUMBER(1, 0) := 0;
BEGIN
     SELECT 1 INTO v_temp
FROM DUAL
WHERE EXISTS ( SELECT SecurityGroupId
FROM SKESGResourceMapping
WHERE APPLICATION = v_Application
AND RoleId IN
                                                  select column_value
                                                  from table(resource_list)
EXCEPTION
WHEN NO_DATA_FOUND THEN
MappingExixts := 'NO';
END;
IF v_temp = 1 THEN
MappingExixts := 'YES';
     END IF;
END;
while calling the procedure from sql*plus, the calling block is :
variable MappingExixts nvarchar2(100);
execute Get_RoleMapping_Temp('2f90e7969e0a9045aeb5b5ed7b3da9d6,363aef470e10094281e5040627e3b6f8', 'repo1', :MappingExixts);
print MappingExixts;
It is throwing an error saying:
ORA-06502: PL/SQL: numeric or value error: raw variable length too long
ORA-06512: at "ORACLE1.GET_ROLEMAPPING_TEMP", line 8
Thanks for your valuable time and suggestions

Hi Binoy,
Thanks for your quick response, I increased its size to 200, but I am getting the following error
ORA-06502: PL/SQL: numeric or value error: hex to raw conversion error
ORA-06512: at "ORACLE1.GET_ROLEMAPPING_TEMP", line 8

Lightroom License Key too short

Hello
I just bought a license key online but it seems like the key I find in my Adobe-account it is too short. I am missing 2 characters.
What I also find a little strange about the key is that it starts with 5 letters, and the rest are numbers.
Does somebody know the reason and solution to this?
Thanks in advance

Hi,
Sounds like it is probably a redemption code.
Have a look at: Redemption Code Help

JPEG market segment length is too short

In copying a series of folders containing JPEGs, PSDs and RAW files (Canon .CR2 and Hasselblad .3F) to a new external drive (Mac OSX), there was a hiccup and a large number of the copied image files contain red dots next to them in the finder window. The files are named correctly and contain the full data size of the originals, but when attempting to open a JPEG I get the following error message:
Could not complete your request because a JPEG marker segment length is too short (the file may be truncated or incomplete).
When attempting to open a .PSD file the message is:
Could not complete your request because it is not a valid Photoshop document.
When attempting to open the RAW file in Bridge, the message is:
Could not complete your request because Photoshop does not recognize this type of file.
In the Get Info window, all three file types are correctly identified as Adobe Photoshop files, Adobe Photoshop JPEG files and Camera RAW files, and each is the correct size it should be.
This happened to some, but not all of the files on the drive, and it appears to have happened randomly. I have run Data Rescue on the drive, but the rescued file still have the red dots and do not open. I've also tried other file recovery programs, as well as Stellar Phoenix Photo Recovery and Jpeg Repair utilities, all to no avail.
I've tried renaming the files, and opening them from other programs such as preview, iPhoto and Lightroom. Still no luck.
I'm hoping someone has another angle for me. The data is there; it's obvious something happened that is preventing the files from opening, but it seems there should be some fix for this.
TIA

Your opening statement said you were copying, not moving the files.
If you were Moving the files, then the routine that was doing the moving erases behind unless they are coming from a CDROM or a write protected device..
Those files are essentially corrupted or incompatible with CC.
Did those files open okay where ever they lived before they were moved?
What was the "hiccup" that you mentioned? A Power Hiccup ? Then these files are toast if indeed there were in the middle of a Move..
Were you using Finder to do this task?

[b]ORA-01450: maximum key length exceeded[/b]

Hi I get this error when trying to migrate MS Access 2000 to Oracle. I get this error on foreign key and primary keys saying that the maximum key length has been exceeded.
What does this mean and how can I fix it? Can anyone help?
Thanks
Ray

Maximum key length also depends on tablespace block size. It seems that your value (1942) may be for 2K blocks.
At least for my 10.2.0.1.0 on Windoze it takes
1478 for 2k tablespace
3118 for 4k tablespace
6398 for 8k tablespace
If you have 2K blocks I'd say it is somewhat rather small blocks, I'd normally use 8K blocks.
So if you have possibility (have at least version 9, probably 9.2 don't know exactly) to create tablespaces with non default blocksize then as a temporal solution you can create tablespace with larger blocksize and create index in it.
Of course so you have to allocate also some memory for these blocksizes and so divide your memory in possibly less utilized pieces.
See example for my 8k default blocksize test DB:
SQL> create table v (a varchar2(4000), b varchar2(4000), c varchar2(4000));
Table created.
SQL> insert into v values (lpad('a', 4000, 'a'), null, null);
1 row created.
SQL> create index vidx on v (a, b, c);
create index vidx on v (a, b, c)
ERROR at line 1:
ORA-01450: maximum key length (6398) exceeded
SQL> alter system set db_16k_cache_size = 10240;
System altered.
SQL> create tablespace big datafile 'big.dbf' size 10 m blocksize 16k;
Tablespace created.
SQL> create index vidx on v (a, b, c) tablespace big;
Index created.
Gints Plivna
http://www.gplivna.eu
Message was edited by:
gintsp
Of course inserting a row was completely unnecessary :)

A jpeg marker segment length is too short

While imaging with my Canon T1i last night with my astro club I took probably 75 or 80 pics. Halfway through the session, my battery low indicator came on, so I changed the battery but may not have turned off the camera....I can't remember.....as I continued to shoot and review the images, everything looked and worked fine. When I returned home and got up this a.m. to review the pics, the last half could not be be opened. I usually insert my SD card in my laptop to review first before I transfer them over. I kept getting this error on the last half of the images I took :" a jpeg marker segment length is too short. The file may be truncated or incomplete." Anybody seen this or have any experience with this? Is there any way to recover and otherwise save these images? Any advice or help would be greatly appreciated. By not turning the camera off while changing batteries, could that be the reason for the error message? Thanks, Gary
Message was edited by: AstroLabsIdaho

It could be any one of a number of things such as the files being corrupted as the camera was writing them to the card, or a faulty card, a faulty USB connection or cable, etc.
Use only high quality cards ans cables, preferably use a card reader, be careful how you handle the camera, how you change batteries, etc. Common sense practices.
Google image recovery software.

ORA-01450: maximum key length (string) exceeded

CREATE TABLE ABC
(ADAPTERINSTID NUMBER(12),
MOTYPEID NUMBER(12),
GROUPDISCID VARCHAR(3000),
MEMBER_MOTYPEID NUMBER(12),
MEMBER_MOINSTID VARCHAR(3000),
primary key (
ADAPTERINSTID,
MOTYPEID,
GROUPDISCID,
MEMBER_MOTYPEID,
MEMBER_MOINSTID));
This is Oracle 11.2 and db_block_size is set to 8192 , Need help .
One way is use db_block_size like 16 K
thanks in advance,

From Show parameter nls_length_semantics
We come to know its --> nls_length_semantics CHAR
Will below solution works ?
ALTER SYSTEM SET NLS_LENGTH_SEMANTICS='BYTE' scope=both;
This I found at ORA-01450: maximum key length (6398) exceeded
thanks

ORA 01450 : maximum key length (1942) exceeded

hI all,
i got that message when try to create index.
ORA 01450 : maximum key length (1942) exceeded
Regards,

Maximum key length also depends on tablespace block size. It seems that your value (1942) may be for 2K blocks.
At least for my 10.2.0.1.0 on Windoze it takes
1478 for 2k tablespace
3118 for 4k tablespace
6398 for 8k tablespace
If you have 2K blocks I'd say it is somewhat rather small blocks, I'd normally use 8K blocks.
So if you have possibility (have at least version 9, probably 9.2 don't know exactly) to create tablespaces with non default blocksize then as a temporal solution you can create tablespace with larger blocksize and create index in it.
Of course so you have to allocate also some memory for these blocksizes and so divide your memory in possibly less utilized pieces.
See example for my 8k default blocksize test DB:
SQL> create table v (a varchar2(4000), b varchar2(4000), c varchar2(4000));
Table created.
SQL> insert into v values (lpad('a', 4000, 'a'), null, null);
1 row created.
SQL> create index vidx on v (a, b, c);
create index vidx on v (a, b, c)
ERROR at line 1:
ORA-01450: maximum key length (6398) exceeded
SQL> alter system set db_16k_cache_size = 10240;
System altered.
SQL> create tablespace big datafile 'big.dbf' size 10 m blocksize 16k;
Tablespace created.
SQL> create index vidx on v (a, b, c) tablespace big;
Index created.
Gints Plivna
http://www.gplivna.eu
Message was edited by:
gintsp
Of course inserting a row was completely unnecessary :)

Error "602" System error: AK Datapart too short

Hi all,
Ok, I have looked just about everywhere for an answer to this but to no avail...I even tried under a few rocks we have laying around.
Anyway here it is:
While running a compression in BW we get Error "602" System error: AK Datapart too short.
This is happening while doing a select statement during the compression of the infocube. It does not happen all the time, just kind like when ever it feels like. The only note I could find in OSS was one about Live Cache and it does not seem to apply.
Here is the dump which I really hate doing this, but it gives all the info needed :
untime Error          DBIF_DSQL2_SQL_ERROR
Except.                CX_SY_NATIVE_SQL_ERROR
Date and Time          08/15/2007 12:23:09
ShrtText
An SQL error occurred when executing Native SQL.
What happened?
Error "-602" occurred in the current database connection "DEFAULT".
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
is especially useful if you want to keep a particular message.
How to correct the error
Database error text........: "System error: AK Datapart too short"
Database error code .......: "-602"
Triggering SQL statement...: "INSERT INTO "/BIC/EZPSD_C03" ( "KEY_ZPSD_C03P",
"KEY_ZPSD_C03T", "KEY_ZPSD_C03U", "KEY_ZPSD_C031", "KEY_ZPSD_C032",
"KEY_ZPSD_C033", "KEY_ZPSD_C034", "/BIC/ZNET_ASP" ) SELECT ? ,
F."KEY_ZPSD_C03T", F."KEY_ZPSD_C03U", F."KEY_ZPSD_C031", F."KEY_ZPSD_C032","
Internal call code.........: "[DBDS/NEW DSQL]"
Please check the entries in the system log (Transaction SM21).
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"DBIF_DSQL2_SQL_ERROR" CX_SY_NATIVE_SQL_ERRORC
"GP31VIZWJDTT90894L1IA5YAC7G" or "GP31VIZWJDTT90894L1IA5YAC7G"
"TRANSFER_ALL"
If you cannot solve the problem yourself and you wish to send
an error message to SAP, include the following documents:
1. A printout of the problem description (short dump)
To obtain this, select in the current display "System->List->
Save->Local File (unconverted)".
2. A suitable printout of the system log
To obtain this, call the system log through transaction SM21.
Limit the time interval to 10 minutes before and 5 minutes
after the short dump. In the display, then select the function
"System->List->Save->Local File (unconverted)".
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, select the Editor function "Further Utilities->
Upload/Download->Download".
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
The exception must either be prevented, caught within the procedure
"TRANSFER_ALL"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
System environment
SAP Release.............. "640"
Application server....... "sdcbw03"
Network address.......... "10.64.18.76"
Operating system......... "Linux"
Release.................. "2.6.9-55.ELsmp"
Hardware type............ "x86_64"
Character length......... 16 Bits
Pointer length........... 64 Bits
Work process number...... 21
Short dump setting....... "full"
Database server.......... "sdcbw03"
Database type............ "ADABAS D"
Database name............ "BWP"
Database owner........... "SAPBWP"
Character set............ "C"
SAP kernel............... "640"
Created on............... "Nov 5 2006 19:46:34"
Created in............... "Linux GNU SLES-9 x86_64 cc3.3.3"
Database version......... "SAPDB 7.5.0.030 "
Patch level.............. "156"
Patch text............... " "
Supported environment....
Database................. "MaxDB 7.5.0"
SAP database version..... "640"
Operating system......... "Linux 2.6"
Memory usage.............
Roll..................... 16192
EM....................... 20949280
Heap..................... 0
Page..................... 24576
MM Used.................. 9235016
MM Free.................. 3331560
SAP Release.............. "640"
User and Transaction
Client.............. 011
User................ "ALEREMOTE"
Language key........ "E"
Transaction......... " "
Program............. "GP31VIZWJDTT90894L1IA5YAC7G"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
The termination occurred in the ABAP program "GP31VIZWJDTT90894L1IA5YAC7G" in
"TRANSFER_ALL".
The main program was "RSPROCESS ".
The termination occurred in line 573 of the source code of the (Include)
program "GP31VIZWJDTT90894L1IA5YAC7G"
of the source code of program "GP31VIZWJDTT90894L1IA5YAC7G" (when calling the
editor 5730).
The program "GP31VIZWJDTT90894L1IA5YAC7G" was started as a background job.
Job name........ "BI_PROCESS_COMPRESS"
Job initiator... "ALEREMOTE"
Job number...... 12185102
Processing was terminated because the exception "CX_SY_NATIVE_SQL_ERROR"
occurred in the
procedure "TRANSFER_ALL" "(FORM)" but was not handled locally, not declared in
the
RAISING clause of the procedure.
The procedure is in the program "GP31VIZWJDTT90894L1IA5YAC7G ". Its source code
starts in line 557
of the (Include) program "GP31VIZWJDTT90894L1IA5YAC7G ".
Source Code Extract
Line
SourceCde
543
ENDIF.
544
545
COMMIT WORK.   " commit and close cursors
546
547
l_str = i_max_requid.
548
PERFORM msg_append(saplrscondense)
549
USING    'S' '355' l_str space space space
550
CHANGING c_t_msg.
551
552
ENDFORM.                               " CONDENSE_FACTTABLE_NEW
553
554
555
     Form TRANSFER_ALL
556
557
FORM TRANSFER_ALL USING i_ref_update       TYPE rs_bool
558
i_pdimid           TYPE I
559
i_pdimid_ref_point TYPE rsd_sid
560
i_pdimid_normal    TYPE rsd_sid
561
i_recordtp         TYPE rsd_sid
562
CHANGING e_ref_ins_cnt TYPE I
563
e_ins_cnt     TYPE I
564
c_t_msg       TYPE rs_t_msg.
565
566
CALL FUNCTION 'RSDU_INFOCUBE_INDEXES_DROP'
567
EXPORTING
568
I_INFOCUBE = 'ZPSD_C03'
569
I_FACTTAB = '/BIC/EZPSD_C03'.
570
571
572
EXEC SQL.
>>>>>
INSERT INTO "/BIC/EZPSD_C03"
574
( "KEY_ZPSD_C03P"
575
, "KEY_ZPSD_C03T"
576
, "KEY_ZPSD_C03U"
577
, "KEY_ZPSD_C031"
578
, "KEY_ZPSD_C032"
579
, "KEY_ZPSD_C033"
580
, "KEY_ZPSD_C034"
581
, "/BIC/ZNET_ASP"
582
583
SELECT :i_pdimid_normal
584
, F."KEY_ZPSD_C03T"
585
, F."KEY_ZPSD_C03U"
586
, F."KEY_ZPSD_C031"
587
, F."KEY_ZPSD_C032"
588
, F."KEY_ZPSD_C033"
589
, F."KEY_ZPSD_C034"
590
, SUM( F."/BIC/ZNET_ASP" )
591
FROM "/BIC/FZPSD_C03" F
592
WHERE F."KEY_ZPSD_C03P" = :i_pdimid
Any thoughts would be helpful,
Thanks,
David

This error usually occurs when there is a database lock or no space in teh database. Got DB02 and Click on Space critical objects to see whether any entries are there. If yes contact your basis to increase the space.
Hope this helps
Thanks,
Satish

ORA-28234 - Key length too short

Similar Messages

Maybe you are looking for