Problem solve
Get help with specific problems with your technologies, process and projects.
Cause of ORA-06550 error
I'm getting an ORA-06550 error with submessage PLS-00103, which is objecting to the word 'INSERT.' I initially thought this would be a code issue but when I backed the database up and imported it to a standard Oracle-built database the problem went away. Are there any database configuration options that can cause an ORA-06550 error?
I'm getting an ORA-06550 error with submessage PLS-00103, which is objecting to the word 'INSERT' as it is expecting a ':+.@%;.' I initially thought this would be a code issue but when I backed the database up and imported it to a standard Oracle-built database the problem went away. My question is are there any database configuration options that can cause an ORA-06550 error?
The ORA-6550 error is simply telling you which line of code is causing the error to be thrown. So this error is not the cause of your problem, just a pointer to the actual problem. The PLS-103 error is the true cause of your problem. The PLS-103 error is saying "Encountered the symbol "%s" when expecting one of the following." From your description, it looks like your PL/SQL block is expecting one of the following: ":+.@%;" instead of INSERT. Typically, this means you did not include a semicolon to terminate the command before the INSERT statement.
Without seeing your exact PL/SQL code, I am not sure why your code worked with a new database. But there are no...
Continue Reading This Article
Enjoy this article as well as all of our content, including E-Guides, news, tips and more.
Step 2 of 2:
configuration options which can cause the ORA-6550 as this error is only in response to another error.
Dig Deeper on Oracle database design and architecture
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.
Meet all of our Oracle Database / Applications experts
View all Oracle Database / Applications questions and answers
Start the conversation
0 comments