Pls-801 Internal Error 1401
Contents |
and ORA-06544 pl/sql internal error After giving the finishing touches to a PL/SQL procedure that had been haunting me for the last days, pls-00801: internal error [phdcsql_print_kge_errors::parm pos] consisting primarily of one BIG implicit cursor with several subqueries and
Ora-06544 Pl/sql Internal Error Arguments
a convoluted logic, i was finally ready to compile the program when i got this terrifying error
Pls-00801: Internal Error [ph2csql_strdef_to_diana:bind]
message:Line: 1 Column: 3 Error: PLS-00801: internal error [ph2csql_strdef_to_diana:bind]Line: 7 Column: 12 Error: PL/SQL: ORA-06544: PL/SQL: internal error, arguments: [ph2csql_strdef_to_diana:bind], [], [], [], [], [], [], []Line: 7
Pls-00801: Internal Error [10902]
Column: 5 Error: PL/SQL: SQL Statement ignoredOnce i recovered from the shock, i soon realized that there must be some junk i left in the SQL statement that i was converting from the sqlplus format (where i developed and tested it) into a programmatic format, that is replacing substitution variables with procedure parameters and variables.From my past pls-00801: internal error [hshuid:lu invalid] experience i know that when Oracle 9i complaints with a PL/SQL parser internal error, although the manual suggests to call Oracle Support and report a supposed bug, usually it's much ado about nothing, it's just a matter of a construct that the parser doesn't like.Note that the parser doesn't point us to the precise spot where it found a problem, but it reports it as a generic problem regarding the whole SQL statement (line 7, where my UPDATE begins) , so it's up to us to find out where the offending bit is located....begin...UPDATE -- at line 7...AND L1.TYPE_CODE = 'MK' -- at line 25AND L2.TYPE_CODE = 'RE'AND AM.MD_NBR = &num_model_nbrAND L1.LOC_CODE = L2.LOC_CODEAND AM.MD_CODE = 'WK'AND MOG.USER_ID = i_var_userAND MOG.CONFIG_FLAG = 'X'AND MOG.MKT_NBR = L2.LOC_NBRAND MOG.PL_NBR = AM.PL_NBR...end;In my case, it was just a sqlplus substitution variable that i forgot to replace with its corresponding parameter, however i remember i saw this happen more than once with certain SQL statements involving function THE (aka TABLE function) inside t
check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection ora 06553 pls 801 below. Results 1 to 8 of 8 Thread: PL/SQL compilation error Tweet Thread Tools Show ora-06553: pls-801: internal error [pklsdlp:dependency verification] Printable Version Subscribe to this Thread… Search Thread Advanced Search Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 02-12-09,06:07 #1 sathidevi View Profile View Forum Posts Registered User Join Date May 2006 Posts 46 Unanswered: PL/SQL compilation error Hi Experts, While compiling one of my stored procedures, I am getting this peculiar error. PLS-00801: internal error [phdcsql_print_kge_errors:arm http://oraclequirks.blogspot.com/2007/05/pls-00801-internal-error-and-ora-06544.html pos] Please help me to fix this. Thanks PS Reply With Quote 02-12-09,07:00 #2 Littlefoot View Profile View Forum Posts Lost Boy Join Date Jan 2004 Location Croatia, Europe Posts 4,090 Provided Answers: 4 Without a procedure code, here you are: Originally Posted by Oracle PLS-00801: internal error [string] Cause: This is a generic internal error that might occur during compilation or execution. The first parameter is the internal error number. Action: Report this error as a http://www.dbforums.com/showthread.php?1638229-PL-SQL-compilation-error bug to your Customer Support representative. Reply With Quote 02-12-09,10:17 #3 anacedent View Profile View Forum Posts Registered User Join Date Aug 2003 Location Where the Surf Meets the Turf @Del Mar, CA Posts 7,776 Provided Answers: 1 Can you debug code you can not see? (I doubt it because it appears you can not debug code you can see.) Most folks can't. You can lead some folks to knowledge, but you can not make them think. The average person thinks he's above average! For most folks, they don't know, what they don't know. Good judgement comes from experience. Experience comes from bad judgement. Reply With Quote 02-12-09,23:12 #4 sathidevi View Profile View Forum Posts Registered User Join Date May 2006 Posts 46 I don't see any error in the code as such. I walked thru' the code of 1000 lines, but no error. Even if there is any error, that would be the compilation errors where we can fix it. But this is totally an irrelevant error. Please help. Thanks PS Reply With Quote 02-12-09,23:33 #5 anacedent View Profile View Forum Posts Registered User Join Date Aug 2003 Location Where the Surf Meets the Turf @Del Mar, CA Posts 7,776 Provided Answers: 1 >I don't see any error in the code as such. I don't see any error either. >But this is totally an irrelevant error. Then
phdcsql_print_kge_errors::parm pos is just an example that can be replcaed with any other undecipherable set characters. Oracle's official error description is: Cause: This is a generic internal error that might occur during compilation or execution. The first parameter is the http://dbtricks.com/?p=278 internal error number. Action: Report this error as a bug to your Customer Support representative. While it might be very tempting to contact Oracle Support, many users will prefer to try and solve the problem without opening a service request and waiting for an answer. Basically, what this error means is that there is a problem with this query but Oracle is having problem describing the error. The result is a internal error generic (and not really helpful ) error message. Like any generic error description, many reasons can cause the problem. The only solution is trying to identify the problem yourself by trial and error. Copy the query part of the code to a separate window and try to tweak it without changing the basics: change tables order, change aliases names, comment what you can or run it without variables. Even if this will pls-00801: internal error not solve the problem, sometimes this can provide a more informative error message. Using this method I have found several issues that caused pls-00801 internal error. I am writing a few in order to provide some list of things that can cause this error: 1) The query used a remote database using a db link and the database link user did not have proper permissions. 2) Extra not visible control characters that were added to the code during a problematic copy-paste from the web or from Word. 3) Extra characters that might have different meaning in oracle like:&,",_ etc. 4) Extra spaces 5) Invalid objects on remote database 6) Several known Oracle bugs (search metalink for the error) 7) An error on a remote database can not be displayed. 8) Your entry here … Of course, there are countless other reasons for pls-00801. If you encounter any other reason please share it in the comments to help others. This entry was posted in Uncategorized and tagged Oracle error, phdcsql_print_kge_errors, PLS-00801 on June 11, 2015 by Asaf Tal. Post navigation ← Why is Oracle query not using my index? A cheklist Can you move a table between schemas ? → One thought on “PLS-00801: internal error [string]” Sachin June 28, 2016 at 2:03 am I