I am hoping you can give me some clue as to why the following should happen. I am working in Designer and need to insert new tables in current universes that have a go live date of this coming weekend. There are universes that require the same tables so after inserting the tables in one universe and creating classes/objects/meta data, I then had hoped to copy that same class/folder to the other universes as the tables would be the same, etc.
What I am getting when I go to parse the objects in the table after copying them over is the following error: Parse Failed:Invalid definition (UNV0023). The only way to get rid of it has been to go into each object and copy, delete and then past the table object name. It then parses o.k. Needless to say this is a huge problem when you have 15 or more universes to modify. I am running out of things to try and was hoping someone had run into this problem before. My company uses DB2.
Good shout. Open the first object that errors and try and create the sql for it manually, by clicking on >> arrow button to the right of the select clause. Now try and find the table and column you want. This should point you in the right direction.
Hi! Anita, Thank you, thank you, thank you for your quick reply. I wasn’t sure if the sequence of adding tables and then doing the joins before adding the objects was needed but it sure is. This will really help me timewise and especially frustration wise. This forum is really helpful.
Hello BOB,
We have existing universe ,I just imported it and checked integrity then got this error Parse Failed:Invalid definition (UNV0023) for all objects in one of the class. I simply did Ctr+C and Ctr+V (cut and paste) in select statement then its working .I dont know why its behaving like this ,please let me know if anybody have alternate solution for this, because we have more than 500 objects giving same parsing error.
Thank you for posting this!! Two objects in one of our universes just started returning the UNV0023 error. They’re just a Select of table.column from the database. I did everything I could think of to fix them, but nothing was working. Then I saw your post and decided to try it. Just copying and pasting what was already in the Select box got rid of the error!
The change that I had made was this.
My universe was built on a view.
I modified the underlying view - applying joins and other business logic to the view instead of in the universe.
I used find/replace to change the SQL in all objects that referenced the now defunct other table.
I removed the joins and the other table.
Checking the universe revealed that annoying error (I know the SQL was correct)
The easiest way that I found to fix it was this.
With the check list showing the errors open, double click the first error
Click ANYWHERE in the SQL edit window and press space, then immediately press backspace. (trick the editor into thinking you have made a real change so that it will activate the ‘Apply’ button)
Click Apply button
Single click on the next error object.
Repeat steps 2 - 4 until all errors are dealt with.
The problem with me was different and your space method didn’t helped.
The problem was that I added the objects before I added the tables to the universe and Ctrl-C Ctrl-V method didn’t worked. But when I put all the tables into the universe and then deleted and copyed the objects again, the error disappeared.
So the conclusion is that first one has to add the tables and after adding the tables should add the objects, not before. I don’t have joins in the universe, because it will be linked into an other universe, where I will add the joins.
Unfortunately an other error occured, when I start parsing some of the objects: ORA-00918 column ambiguosly defined. I know that the exoression is good. I tried to add the joins, but it didn’t help. I copy here the expression which gives this error:
sum(case
when (DENOM_DEV_VETT.DEV_ISO_KOD != 'HUF' AND DENOM_DEV_ELADOTT.DEV_ISO_KOD != 'HUF') then
(((JEL.FCT_FORGALOM.ERTEK_VETT*(ARFOLYAM_VETT.ARFOLYAM/ARFOLYAM_VETT.ARF_EGYS))+(JEL.FCT_FORGALOM.ERTEK_ELAD*(ARFOLYAM_ELADOTT.ARFOLYAM/ARFOLYAM_ELADOTT.ARF_EGYS)))/2*( CASE
WHEN JEL.FCT_FORGALOM.TORLES_MODOS='T' THEN (-1) ELSE 1
END ))
Same table in 2 universes. But I can’t copy an object from one to the other without getting the same error message. Like you say, you copy the object definition, delete it, close the object, open it again, paste the definition back and save it and it works fine.
I’m getting this error on a universe that is created using a stored procedure. It says that the error is in the 7th parameter, but I have only 1 parameter in the stored procedure. I am now very confused as to how to fix this error.
This is in R3. If I take out the WHERE bit of the object definition, it goes away. If I paste it back in, it returns. It’s same whether the object is referencing an alias or a base table.
And yet I can use the object in a query with no errors at all.
I am facing similar error in R3 now.
I have a conditional object in universe as below,
@Select(Az Organisation Units\Org Unit Sub Level) IN @Prompt(‘Select one or more Organisation Unit Sub Levels’,‘C’,‘Org LOV\Org Unit Sub Level LOV’,multi,constrained,Persistent,{’ All Sub Levels’},USER:5)
When I parse this object it is giving me an error message like,
“Parse failed: Invalid definition (UNV0023). Error parsing default value parameter (7th parameter)”
The same prompt definition get parsed in R2 but throwing error in R3. Any clue?
It seems that BO caches prompt definitions. So if you have a new definition for a prompt - for ex. @Prompt(‘MY_PROMPT’, ‘abc’, , mono, free) instead of @Prompt(‘MY_PROMPT’, ‘abc’, , mono, free), the parsing will fail EVEN IF YOU UPDATE ALL OF THE PROMPT DEFINITIONS EXISTING IN THE UNIVERSE.
The fix to that is: rename the prompt, for ex. @Prompt(‘MY_PROMPT_2’, ‘abc’, , mono, free), export universe to server, import, and put the new definition back in @Prompt(‘MY_PROMPT’, ‘abc’, , mono, free). That will remove the (UNV0023) error.
Hi!
(BOB member since 2002-06-17)
(BOB member since 2002-08-15)
Hi! Anita, Thank you, thank you, thank you for your quick reply. I wasn’t sure if the sequence of adding tables and then doing the joins before adding the objects was needed but it sure is. This will really help me timewise and especially frustration wise. This forum is really helpful.
(BOB member since 2007-05-16)
(BOB member since 2003-08-19)
(BOB member since 2009-06-23)
(BOB member since 2005-03-01)
(BOB member since 2007-12-11)