Internal Error 56319
Contents |
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
Ora-06553: Pls-801: Internal Error [56327]
error [56319]After searching a little bit, I found this is related migration error between ora-06553: pls-801: internal error [pklsdlp:dependency verification] 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. 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 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) ► January 2009 (3) ▼ 2008 (33) ▼ December 2008 (5) Unregister Database From Catalog EXP-00056, ORA-31600 Recover Database with Only RMAN Hot Backup File ORA-06553: PLS-801: internal error [56319] Recompiling Invalid Schema Objects ► November 2008 (9) ► October 2008 (12) ► June 2008 (5) ► May 2008 (2) Awesome Inc. template. Powered by Blogger.
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 platform and then you move/restore same database to a 32-bit platform, or vice versa, 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 http://jaycheunge.blogspot.com/2008/12/ora-06553-pls-801-internal-error-56319.html objects (functions, 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 http://salmandba.blogspot.com/2015/03/ora-06553-pls-801-internal-error-56319.html option 2. Invalidate the 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) ► 201
but got it sorted out. in the end. 2) Had to run utlirp.sql when database is http://hemora.blogspot.com/2011/01/ora-06553-pls-801-internal-error-56319.html in migration mode. (remember I ported the db from 32 http://manpreet-dba.blogspot.com/2014/01/ora-06553-pls-801-internal-error-56327.html 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 I am fine. now. before this the error was with 64 bit and internal error 32 bit was clean. -------------- Other Scenario--------------------------------------------------------- Worked great, I had to restore a 32 bit database on a 64 bit system. After restore/recover operations with RMAN I did the following. 1) startup upgrade; 2) @?/rdbms/admin/utlirp.sql 3) shutdown immediate; 4) startup;------------Other Scenario-----------------------------------------------------Received the "ORA-06553: PLS-801: internal error [56319]" error after cloning a db, ora-06553: pls-801: internal while trying to drop a user. SQL> drop user QCSITEADMIN_DB0 cascade; drop user QCSITEADMIN_DB0 cascade * ERROR at line 1: ORA-00604: error occurred at recursive SQL level 1 ORA-06553: PLS-801: internal error [56319] and it got resolved after executing "utlirp.sql". ---------------------------------------------------My scenario -----------------SYS @ bsqrac >>conn volume/traceERROR:ORA-06553: PLS-801: internal error [56327]Error accessing package DBMS_APPLICATION_INFOConnected.VOLUME @ bsqrac >>VOLUME @ bsqrac >>@utlirp.sqlVOLUME @ bsqrac >>WHENEVER SQLERROR EXIT;VOLUME @ bsqrac >>DOCDOC>#######################################################################DOC>#######################################################################DOC> The following statement will cause an "ORA-01722: invalid number"DOC> error if there the database was not opened in UPGRADE modeDOC>DOC> If you encounter this error, execute "SHUTDOWN", "STARTUP UPGRADE" andDOC> re-execute utlirp.sqlDOC>#######################################################################DOC>#######################################################################DOC>#VOLUME @ bsqrac >>SELECT TO_NUMBER('MUST_BE_OPEN_UPGRADE') FROM v$instance 2 WHERE status != 'OPEN MIGRATE';SELECT TO_NUMBER('MUST_BE_OPEN_UPGRADE') FROM v$instance *ERROR at line 1:ORA-00942: table or view does not exist Disconnected from Oracle Database 11g Release 11.2.0.1.0 - ProductionWith the Automatic Storage Management option[oracle@VOL-ORATEST admin]$ sSQL*Plus: Release 11.2.0.1.0 Production on Mon Jan 24 12:35:48 2011Copyright (c) 1982, 2009, Oracle. All rights reserved.
the alert log: Errors in file d:\oracle\product\10.2.0\admin\maxnips1\bdump\maxnips1_cjq0_5812.trc:
ORA-00604: error occurred at recursive SQL level 1
ORA-06544: PL/SQL: internal error, arguments: [56319], [], [], [], [], [], [], []
ORA-06553: PLS-801: internal error [56319] Cause:- The database on the new location was built using datafiles from a different word-size database. For example, you used the datafiles from a 64-bit database for your new 32-bit database OR you used the datafiles from a 32-bit database for your new 64-bit database. Either of these scenarios results in PL/SQL objects that are inconsistent with the Oracle executable. Solution:- SQL> shutdown immediate; SQL> startup upgrade; SQL> @$ORACLE_HOME/rdbms/admin/utlirp; SQL> shutdown immediate; SQL> startup; SQL> @@$ORACLE_HOME/rdbms/admin/utlrp; Posted by Manpreet Singh at 22:40 Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: ORA Errors No comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Labels 11gR2 Clusterware Startup Order (1) Add Node on Oracle RAC 11gR1 - Step by Step (1) Add VIP in Oracle RAC (1) ARCHIVE GAP IN STANDBY SERVER (1) Automatic Storage Management (ASM) - Architecture (1) AWR Reports Vs. ASH Reports (1) Basic Linux Commands (1) Change Archive log mode of RAC database (1) Change the bonding mode in Linux (1) Deleting a Node from 11gR2 RAC (1) Disable Archive log in Oracle RAC (1) Disable NUMA parameter (1) DNS Configuration on Linux (1) expdp/impdp without table data (1) Grant Read Only Access to User (1) Hot Backup Script (1) How to change SGA in Oracle RAC (1) How to check cluster name (1) How to Tune Shared Pool Cache (1) IP Bonding in Linux 6 (1) IP Bonding on Linux (1) Java Heap Space error (Addnode.sh) (1) NID Utility in Oracle (1) OC4J Configuration issue (1) OCFS (1) OPEN RESETLOGS WITHOUT RECOVERY (1) ORA Errors (13) ORA-00845 : MEMORY_TARGET not supported on this system (1) ORA-15056 / ORA-15046 (1) Orac