Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 16 Oracle Analytics Lounge
- 216 Oracle Analytics News
- 43 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 79 Oracle Analytics Trainings
- 15 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
OBIEE Error: ORA-01401: too big value entered for the column at OCI call OCIStmtFetch.
Hi!
I ma column in my table database with the Data Type 'VARCHAR(4000)' and I can not show your data in my OBIEE report.
(The types of column data in the database and RPD Physical Layer are identical, already checked).
Error message:
"OBIEE Error: ORA-01401: too big value entered for the column at OCI call OCIStmtFetch."
Can you help me?
Answers
-
Hi,
Is it really OBIEE giving you the error? Because "ORA-01401" is a database error, and I found it quite strange that OBIEE use a ORA code for it's own errors.
(Seeing an error in OBIEE doesn't mean the error is generated by OBIEE)
0 -
Hi Mr. @Gianni Ceresa
Yes, the error is show in OBIEE report:
If I make an select in data base, I don't have this error:
I thought it was some limitation of the base date of the RPD but found no configuration related to this problem.
Thanks,
Carina Mendes.0 -
I don't have a running 11.1.1.9 (yours seems to be a 11.1.1.9) but in a 12.2.1.1 the QUERY_TEXT column of the usage tracking table is a lot smaller than 4000 (actually it's 1024 bytes).
OBIEE varchar are limited at 4000 if I don't remember wrong, so you maybe have an error with encoding?
As you use a system in Spanish (I guess) maybe your 4000 characters in the DB actually take more than that because of encoding and so you go over the max size OBIEE manage in a varchar ....
Did you try to reduce the column to a VARCHAR3000 in the RPD and see if you still have the issue?
(Waiting for my SA to boot to check how Oracle imported it into their RPD....)
0 -
Actually few SampleApp I checked all use that column as a VARCHAR 1024 (matching the size I found in the DB).
How come yours is 4000? Where does your S_NQ_ACCT table come from?
0 -
Hi Mr. @Gianni Ceresa,
Yes, I'm using the 11.1.1.9 version of OBIEE.
I made the adjustment that recomedou to varchar (100) forcing the application to bring a smaller number of characters in the column, but the error in OBIEE continues.
Thanks,
Carin Mendes.
0 -
Ah well you should set it to what's in the DB. As Gianni said normally it's 1024 BYTE in SA.
0 -
Hi, Mr. Christian Berg
I changed the datatype in the database and the problem was solved!
Thank you!
0 -
The question is more why it was wrong in the DB?
If somebody put its hands on the table changing the type of the column to collect more content .... simply avoid that!
(I love to talk to myself ...)
Gianni Ceresa wrote:Actually few SampleApp I checked all use that column as a VARCHAR 1024 (matching the size I found in the DB).How come yours is 4000? Where does your S_NQ_ACCT table come from?
0 -
Actually the problem was dataype column in the table, but the error only appeared in OBIEE.
How is not a adminsitrado environment only for myself, I can not say why this VARCHAR (4000) was set.
Anyway, your help was of great value, thank you!
Regards!
Carina Mendes.0
