- ORA-23327: imported deferred
rpc data does not match string of
importing db
-
Cause: Deferred
rpc queues were imported from a database with a different
global name or operating system than importing database.
-
Action: Deferred
rpc data should only be imported into a database with the
same global name and hardware and operating system.
MOSC
documentation has many important aspects of ORA-23327. For
instance, on Oracle Enterprise Edition (Version: 9.2.0.6), the
MOSC docs exhibit a problem in which full import, due to
ORA-23327, can hang or fail. In Oracle 9i, an export done on a
platform, and import done on a different platform (which is included
in RPC object), causes a cross-platform of the full export/import,
which Oracle does not allow.
Though it would normally be advised to use a schema export and/or
drop all replicated objects, Oracle 9i doesn't have a script to
allow the removal of replicates objects.
Because of this, Oracle MOSC docs give a workaround so that
the ORA-23327 can still be resolved:
1. Use schema based import instead of full import
2. Do the following action to avoid the export of the RPC
objects:
on the source database:
connect / as sysdba
create table sav_expact$ as select * from expact$;
truncate expact$;
do the full export
insert into expact$ select * from sav_expact$;
commit;
drop sav_expact$;
Use the resulting dmp file to import onto the other platform.
