If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

java.lang.ArrayIndexOutOfBoundsException

Started by Kcog123, 02 Oct 2015 09:32:49 AM

Previous topic - Next topic

Kcog123

Hi All,
This is a strange situation.
I have a report that ran fine last month. But I changed labels for couple of field names and it's giving this error msg:
"java.lang.ArrayIndexOutOfBoundsException"
I tried to change the labels back to where they were but it still didn't work. So I tried to run the original version of the report. It didn't work either which used to work wonderful. Now it's giving this error msg.
I don't get it.
So I tried to take the sql and run in  Teradata, but what I see is there are no connections between subqueries where there are leftouter joins in cognos. I don't know why that happened. If this is how the report is from the beginning it wouldn't work in the first place. But it worked fine until now.
Please help me. Please!!

MFGF

Quote from: Kcog123 on 02 Oct 2015 09:32:49 AM
Hi All,
This is a strange situation.
I have a report that ran fine last month. But I changed labels for couple of field names and it's giving this error msg:
"java.lang.ArrayIndexOutOfBoundsException"
I tried to change the labels back to where they were but it still didn't work. So I tried to run the original version of the report. It didn't work either which used to work wonderful. Now it's giving this error msg.
I don't get it.
So I tried to take the sql and run in  Teradata, but what I see is there are no connections between subqueries where there are leftouter joins in cognos. I don't know why that happened. If this is how the report is from the beginning it wouldn't work in the first place. But it worked fine until now.
Please help me. Please!!

Does your report contain javascript? If so, what is the code doing?

MF.
Meep!

Kcog123

Thanks for the reply.
No. I mean i don't know if there is any java script. I am unfamilier with the java scripts. I don't know how to see that.

bdbits

#3
Take a deep breath, have a beverage, relaaaaaax...

That is an odd error. If it worked before it is safe to say something changed to break it. So let's work through it. I do not know your knowledge level, so please forgive me if I bring up something obvious to you. We have to start somewhere, so first things first.

Quote from: Kcog123 on 02 Oct 2015 09:32:49 AM
But I changed labels for couple of field names and it's giving this error msg:

What precisely does "labels" refer to? Are these the names of data items in Teradata itself, or Framework Manager (FM), or something else? (I am assuming you are using an FM package.)

If you changed them in Teradata, the first thing you would need to do is change the FM model to use the new names. Make sure the query subjects work in FM as you change them (right-click and Test). Use the context explorer and make sure the relationships are intact. When you are satisfied that all is proper, publish the package.

If your report is complicated, at this point I would probably open Workspace Advanced and run some test queries with the changed data items. Use this to make sure the package is working correctly. Then edit the report, drop the old now-non-existent data items and pull in the new ones, and run.

If you are still getting errors, look at the generated SQL (again). If you see multiple queries that are not related, you might be missing relationships in the FM model. Or perhaps the model is such that Cognos is unable to see that combination of data items as a normal query. So you are likely having some local process going on (in the Cognos server). That would be a different problem, though; it should still work.

A "java.lang.ArrayIndexOutOfBoundsException" points to some java-based component, probably within Cognos but potentially a data source driver, so do not worry about javascript at this time. If this is still the error you are getting, I would try removing pieces of your report one at a time. More than likely, this will point to a particular thing in the report that is leading to the error message. We might be able to help you with that once it is pinpointed.