Ora-06553 Pls-801 Internal Error 56319
CommunityOracle User Group CommunityTopliners CommunityOTN Speaker BureauJava CommunityError: You don't have JavaScript enabled. This tool uses JavaScript and much of it will not work correctly without it enabled. Please turn JavaScript back on and reload this page. Please enter a title. You can not post a ora-06553: pls-801: internal error [pklsdlp:dependency verification] blank message. Please type your message and try again. More discussions in General ora-06553: pls-801: internal error [56327] Database Discussions All PlacesDatabaseGeneral Database Discussions This discussion is archived 3 Replies Latest reply on Dec 6, 2005 7:02 AM by ora-06553 pls-801 internal error 55018 sunilchoudhary ORA-06553: PLS-801: internal error [56319] sunilchoudhary Dec 2, 2005 12:24 PM Hi Folks, Trying to port my database from 32 bit to 64 bit while connection getting error as -------------- SQL*Plus: Release 9.2.0.1.0 - Production on Fri Dec 2 17:20:11 2005 Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved. Enter password: ERROR: ORA-00604: error occurred at recursive SQL level 1 ORA-06553: PLS-801: internal error [56319] -------------- Have tried running catalog.sql catproc.sql and utlrp.sql from sys before as well as after making systemtrigger_enabled=false in init.ora Still can not get across this issue.. Anyone .. having any insights pls .. enlighten. 33289Views Tags: none (add) This content has been marked as final. Show 3 replies 1. Re: ORA-06553: PLS-801: internal error [56319] sunilchoudhary Dec 5, 2005 4:59 AM (in response to sunilchoudhary) Any ideas.. Like Show 0 Likes(0) Actions 2. Re: ORA-06553: PLS-801: internal error [56319] A.D. Dec 5, 2005 9:25 AM (in response to sunilchoudhary) some times back I received the same message and after a great deal of R&D I landedup with the following solution.. execute dbms_stats.delete_database_stats Like Show 0 Likes(0) Actions 3. Re: ORA-06553: PLS-801: internal error [56319] sunilchoudhary Dec 6, 2005 7:02 AM (in response to A.D.) Hi Anirban, Thanks for your update. Did not had a chance to check your solution ..as i got it worked out. Few things 1) Running utlirp.sql (this is going to invalidate most (for me around 80,000 objects) and then recompiles them again) Took a helluva time.. but got it sorted out. in the end. 2) Had to run utlirp.sql when database is in migration mode. (remember I ported the db from 32 bit to 64 bit). I am sure that this "IS A" solutions as now, I am getting the same error with 32bit version of oracle software. However with 64 bit
is a backup from the database on RHEL 64 bit platform.After all the process, I could bring up the database running with the following error:ORA-06553: PLS-801: internal error [56319]After searching a little bit, I found this is related migration error between 64 bit and 32 bit platform. The oracle suggestion is to run utlrp.sql in the process of migration.Well, a solution worked out for me perfectly:1. shutdown immediate2. startup upgrade3. @$ORACLE_HOME/rdbms/admin/utlirp.sql4. shutdown immediate5. startup6. @$ORACLE_HOME/rdbms/admin/utlrp.sql7. https://community.oracle.com/thread/346960 shutdown immediate8. startupMetalink document '272322.1 Difference between UTLRP.SQL - UTLIRP.SQL - UTLIP.SQL'recommends running utlirp.sql script which would do both regeneration of compiledcode of PL/SQL modules (which UTLIP.SQL does) and then recompiles all invalid PL/SQLmodules again (which UTLRP.SQL does). Posted by Jason at 4:15 PM 5 comments: sumeet said... Gr8 notes Than its resolved my problem 12/05/2011 7:14 AM http://jaycheunge.blogspot.com/2008/12/ora-06553-pls-801-internal-error-56319.html Rob said... Thanks so much for this! Saved me a bunch of debugging. Worked like a charm. 1/31/2012 2:47 AM Tom said... Thanks , worked for me too, I had restore a 64 bit backup to a 32 bit system and this fixed the problem 12/17/2012 11:48 AM Songhu Yan said... I moved my datanbase from Windows 32 bit to LINUX 64 bit, Got same problem. This solution is worked perfictly!Thanks, 7/09/2013 12:21 PM Menusa said... great jobs... thx 12/16/2014 4:44 AM Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Blog Archive ► 2012 (1) ► July 2012 (1) ► 2011 (4) ► April 2011 (2) ► February 2011 (1) ► January 2011 (1) ► 2010 (3) ► September 2010 (1) ► August 2010 (1) ► February 2010 (1) ► 2009 (38) ► December 2009 (2) ► September 2009 (3) ► August 2009 (4) ► July 2009 (1) ► June 2009 (3) ► April 2009 (2) ► March 2009 (14) ► February 2009 (6) `
while connecting to a database which has word size (32-bit or 64-bit) different than the actual installation binaries (32-bit or 64-bit). It means that if database was created (and running) on a 64-bit http://salmandba.blogspot.com/2015/03/ora-06553-pls-801-internal-error-56319.html platform and then you move/restore same database to a 32-bit platform, or vice versa, http://www.dba-village.com/village/dvp_forum.OpenThread?ThreadIdA=62560&DestinationA=RSS you will be facing this problem. You may also face this error if you have a standby database running on a platform which has Oracle binaries different than the binaries of primary database platform, and you perform a switchover. After the switchover, you might be facing same error. Reason of this error is that PL/SQL objects (functions, internal error procedures, packages) were compiled using a different word size (suppose 32-bit) when database was created/running, and now you restore/move this database to a 64-bit platform and hence these objects code is inconsistent with the binaries. To solve this problem, you first need to invalidate all PL/SQL objects and then re-compile them so that new compiled code becomes consistent with the available binaries. 1. Startup database with STARTUP UPGRADE option 2. Invalidate the ora-06553 pls-801 internal PL/SQL objects by running $ORACLE_HOME/rdbms/admin/utlip.sql 3. Validate the PL/SQL objects by running $ORACLE_HOME/rdbms/utlrp.sql 4. Shutdown the database 5. Startup the database at 9:14 PM Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: ORA-06553: PLS-801: internal error [56319] No comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Search Oracle Community Forums Search This Blog Salman Ahmed Qureshi I am from Pakistan, living and working in Singapore. Click Here to view my complete profile. Please click here for the complete list of my Articles Blog Archive ► 2016 (20) ► October (2) ► September (2) ► August (1) ► July (1) ► June (1) ► May (3) ► April (2) ► March (3) ► February (2) ► January (3) ▼ 2015 (81) ► December (6) ► November (5) ► October (3) ► September (3) ► August (5) ► July (9) ► June (5) ► May (6) ► April (6) ▼ March (7) ORA-01157: cannot identify/lock data file Manual upgrading Oracle database 11g to 12c ORACLE.EXE (SHAD) Processes Keep Increasing ORA-00020: maximum number of processes exceeded The OracleService service terminated unexpectedly ORA-06553: PLS-801: internal error [56319] OEM Database Control Setup fails with ACCESS DENIE... ► February (6) ► January (20) ► 2014 (32) ► December (5) ► November (1)