[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 5658
  • Last Modified:

error when using expdp to export full database

Hi,

oracle 10.1.0.3.0, redhat el3

when using expdp with the 'full=y' option, i get the following error...


...
Processing object type DATABASE_EXPORT/SCHEMA/TYPE/GRANT/OBJECT_GRANT
ORA-39127: unexpected error from call to export_string :=SYS.LT_EXPORT_PKG.system_info_exp(0,dynconnect,10.01.00.03.00',newblock)
ORA-06537: OUT bind variable bound to an IN position
ORA-06512: at "SYS.DBMS_METADATA", line 5107
Processing object type DATABASE_EXPORT/DE_SYSTEM_PROCOBJACT/DE_PRE_SYSTEM_ACTIONS/PROCACT_SYSTEM
ORA-39127: unexpected error from call to export_string :=SYS.LT_EXPORT_PKG.system_info_exp(1,dynconnect,10.01.00.03.00',newblock)
ORA-06537: OUT bind variable bound to an IN position
ORA-06512: at "SYS.DBMS_METADATA", line 5107
Processing object type DATABASE_EXPORT/DE_SYSTEM_PROCOBJACT/DE_POST_SYSTEM_ACTIONS/PROCACT_SYSTEM
Processing object type DATABASE_EXPORT/SCHEMA/PROCACT_SCHEMA
...

however, the export seems to continue without problems from this point. I have searched the web and the oracle forums for an answer, but couldn't find one. I found some stuff related to the SYS.LT_EXPORT_PKG package for people using oracle 9i, where the package could not be found, however my problem seems to be different.

I'm exporting using the SYSTEM user, a la
expdp system/tmi_4now full=y dumpfile=database.dmp logfile=database.log directory=TMPDIR

where I have created TMPDIR using

create directory TMPDIR as '/tmp';

anyone seen this? Is it safe to ignore?

thanks,
simon
0
simonsta1000
Asked:
simonsta1000
1 Solution
 
peterside7Commented:
Check if the status is valid :

QL> SELECT version, status FROM dba_registry
  WHERE comp_name = 'Oracle Workspace Manager';

  VERSION STATUS
  ------------------------------ -----------
  10.1.0.2.0 VALID


Fix

  1. If the Oracle Workspace Manager feature is not used in this database: ignore the errors during
  export. The impact of this bug is that if there are any Oracle Workspace Manager (OWM) objects
  in the database, and a full export of that database is done, those OWM objects will not be included
  in the export dumpfile.
  The dumpfile is still useable - it will import correctly/properly for all the objects that are in the
  dumpfile(s). However, the Oracle Workspace Manager feature may have unexpected results.

  or:

  2. If the Oracle Workspace Manager feature is not used in this database: de-install the Workspace
  Manager:
  SQL> CONNECT / AS SYSDBA
  SQL> @$ORACLE_HOME/rdbms/admin/owmuinst.plb
  Afterwards, re-run the export.

  or:

  3. Apply the 10.1.0.3.0 Oracle Workspace Manager patch set. This patchset can be downloaded
  from MetaLink as patch 3564144 (generic for all platforms).

  or:

  4. Use the traditional export (exp).

  References

  <NOTE:263428.1> - How to De-install Oracle Workspace Manager

This is all coming from metalink.
0
 
simonsta1000Author Commented:
i get
  VERSION STATUS
  ------------------------------ -----------
  10.1.0.2.0 VALID

and don't use oracle workspace manager, so I guess I'll just ignore it. Thanks
0

Featured Post

Prep for the ITIL® Foundation Certification Exam

December’s Course of the Month is now available! Enroll to learn ITIL® Foundation best practices for delivering IT services effectively and efficiently.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now