could not save infosets

What changes are you actually making? That error parses to me to mean that something you are typing in isn't being properly escaped by the text parser and is being passed as part of an arguement to the backend.

Or in other words, I think you've accidently run into a variant of the ol' Bobby Tables issue - http://xkcd.com/327/ .

I have modified the infoset query which is querying from oracle tables. Previously the query was returning unique rows, the modified query returns duplicates row also, which is the requirement. But, when I try to revert back to the old one, that is also not getting saved resulting in the same error.

The error message that you've quoted suggests the issue isn't in the query, it's in the metadata info (e.g. the name, the description 'paragraph', and etc.) associated wtih the Infoset that is the problem.

If I were running into the issue on my end my troubleshooting flow would be the following:

1. Try creating a throwaway infoset just to make sure that the problem isn't something deeper.

2. If I can save that, then I'd edit the 'mis-behaving' infoset and blow away the description and instead of trying to save updates, save as new. If that worked then something about your description is being parsed as something other than straight data. Strip out any puncutation that isn't 'standard english' and see if that doesn't fix it.

3. If blanking the description doesn't work, then I'd make sure that the query you have is actually working, by hitting the preview link on the screen you edit the query from. Although I've never seen that error message in response to a query problem, there's always the first time. If that is the problem, you've got a SQL issue and you'll need to start breaking things down on your query to make sure you haven't introduced a typo or etc.

4. If the preview doesn't throw up an error, then I'd try to recreate the infoset from scratch. I'd be working under the assumption that something underlying in the medadata is FOOBAR and it'll be more effort to track that down than just redo the infoset and pointing anyhting using it to the new one.

5. If that didn't work, I'd be wondering what the differences are between that throwaway infoset I created and the settings I attempted to put into the 'redo' infoset were and change them, one by one, to figure out what was actually the issue.

Regarding SQL issues and the query itself. If you haven't yet and don't have a dedicated SQL editor already, download and install SQL Developer from Oracle ( http://www.oracle.com/tec...downloads/index.html ). Write and test your SQL in that first and then copy and paste it over to LBI once you have it working rather than trying to do your work in LBI directly.

90% of my headaches went away once I had a real SQL tool to work with vs typing raw text into a cramp text field.

Thank you all for your replies.

We learnt that over the weekend the network group had upgraded all our browsers from IE version 8.0.6001.18702 cipher strength 128-bit to IE version 8.0.7601.17514 cipher strength 256-bit.

I confirmed old infosets can be updated and new infosets can be created from the servers, where luckily the old IE versions were not yet upgraded.

Now my problem is how to make Smart Notifications work from the upgraded IE, because sooner or later they will be upgrading the servers too as it is more secure.

Any suggestions are welcome!

Thanks