Hi <please supply your name>,
"Oracle.dbtools.migration.parser.ext.ExtStringTemplate.setValue(ExtStringTemplate.java:134)" is an internal warning when we are generating the stored procedure,function,view or trigger PL/SQL code.
It will manifest itself possibly as a incorrectly converted statement/clause in the oracle model.
Some times it doesn't manifest as an issue at all, and causes no issues.
Either way its a bug, but I need a bit more detail to replicate.
Does this stop your Oracle Model from being converted?
Is there anymore to the Exception ? Is there a "details" button that can be clicked to view the entire exception stack trace?
Can you skim through some of your converted procedures to see if anything stands out. If so could you provide a small example of the SQL Server procedure.
If your Oracle Mode is generated and looks reasonably OK, the process would be to move on, as you will have to test the converted procedures anyway and you will pick up on any issues this caused then.
SQL Developer Team
Thank you very much for your Reply.
Sorry that I couldn't write earlier.
--Does this stop your Oracle Model from being converted?
The conversion process completes with a few errors that I'm going to fix by hand.
--Is there anymore to the Exception ?
Concerning the Details button: When I click Details it only shows the same exception Message as posted above. Unfortunatly no stacktrace. But maybe there is some kind of logfile outside the IDE which I am not aware of yet, since I am rather new to working with sql developer. If you could point me to the stacktrace I will be happy to post it here.
--Can you skim through some of your converted procedures to see if anything stands out
I did as you suggested. There was a strange behaviour in a Procedure where there was a construct like N'<somestring>' in the original Transact SQL. Somehow every SQL statement that follows is recognized as a String, hence the code is not compiling at all.
There are also some Prcedures which exit with the message: "unexpected end of Subtree"
Edited by: gWahl on 13.11.2009 00:43
OK I would suggest ignoring that warning , it shouldn't happen , and I will keep an eye out for it in the future.
" There was a strange behavior in a Procedure where there was a construct like N'<somestring>' in the original Transact SQL. Somehow every SQL statement that follows is recognized as a String, hence the code is not compiling at all."
Can you give me the T-SQL example of this?
Note, that I think there is a problem with the color highlighting. In that N'<something>' does mess up the color highlighting. But the SQL is fine.
SQL Developer Team