Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Mailing Lists -> Oracle-L -> Re: Errors at the end of (otherwise successful) RMAN migration
I guess I missed these errors when I log in both locally and through
the listener. As you can see, in the end I get to the sqlplus prompt,
and similarly with Oracle SQL Developer, after a couple of error
dialogs, I'm logged in and can run queries. I do *not* see these
errors when I log in locally via "sqlplus / as sysdba".
$ sqlplus dts
SQL*Plus: Release 10.2.0.2.0 - Production on Tue Mar 6 09:26:52 2007
Copyright (c) 1982, 2005, Oracle. All Rights Reserved.
Enter password:
ERROR:
ORA-06553: PLS-801: internal error [56319]
ERROR:
ORA-06553: PLS-801: internal error [56319]
Error accessing package DBMS_APPLICATION_INFO
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
SQL>
On 3/6/07, Don Seiler <don_at_seiler.us> wrote:
> Good morning all. My much-anticipated x86 -> x86_64 test migration
> finished, and everything *appears* to be well (i.e., I logged in and
> did one select on an app table). Something that concerns me was this
> at the very end of the RMAN migration:
>
> --- BEGIN RMAN LOG ---
> database opened
> Finished Duplicate Db at 06-MAR-07
> RMAN-00571: ===========================================================
> RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
> RMAN-00571: ===========================================================
> RMAN-12005: error during channel cleanup
> ORA-06544: PL/SQL: internal error, arguments: [56319], [], [], [], [],
> [], [], []
> ORA-06553: PLS-801: internal error [56319]
>
> RMAN>
>
> Recovery Manager complete.
> --- END RMAN LOG ---
>
> As you can see, the database gets opened and RMAN says it is finished.
> Then I get that error about channel clean up. I'm running the RMAN
> migration from the x86_64 box (the AUXILIARY). The x86 TARGET box has
> four channels auto-allocated, on the AUX side I manually allocated 4
> disk channels. Here is my run block (with bash vars mixed in):
>
> RUN {
> ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE DISK;
> ALLOCATE AUXILIARY CHANNEL aux2 DEVICE TYPE DISK;
> ALLOCATE AUXILIARY CHANNEL aux3 DEVICE TYPE DISK;
> ALLOCATE AUXILIARY CHANNEL aux4 DEVICE TYPE DISK;
>
> DUPLICATE TARGET DATABASE to ${AUXILIARY_INSTANCE}
> UNTIL TIME "TO_DATE('${POINT_IN_TIME}','YYYY/MM/DD HH24:MI:SS')"
> LOGFILE GROUP 1 ('+ASMDG1') size 100M,
> GROUP 2 ('+ASMDG1') size 100M,
> GROUP 3 ('+ASMDG1') size 100M;
>
> }
>
> As I said, it looks like the migration was successful, but
> nasty-looking errors don't make me confident. If anyone has any
> ideas, I'm all ears.
>
> Don.
>
> --
> Don Seiler
> http://seilerwerks.blogspot.com
>
-- Don Seiler http://seilerwerks.blogspot.com -- http://www.freelists.org/webpage/oracle-lReceived on Tue Mar 06 2007 - 09:29:45 CST
![]() |
![]() |