ODT indicates Open Document Format. It is an open standard text document created with Writer, the OpenOffice.org and StarOffice word processor; formatted using the OASIS OpenDocument XML-based standard. From OpenOffice.org, file extensions of text comes with .odt format, spreadsheet comes with .ods format and presentation comes with .odp format.
Microsoft Word by default can't open odt files. Open Document text files can be opened and edited with any OpenOffice-compatible program which are specified below.
1) OpenOffice.org Writer: You can download OpenOffice Write from the link OpenOffice.
2) Sun Microsystems Writer (included with StarOffice).
3) AbiSource AbiWord.
4) IBM Lotus Notes 8 or later.
5) On MAC OS with Apple TextEdit as well as with NeoOffice Writer.
6) On Unix OS with KOffice KWord.
7) Microsoft Word with OpenXML/ODF Translator Add-in.
Though Microsoft Word can't open odt file directly but with plugins you can open it.
If you want to open through Microsoft Word, download the ODF plugin from Sun ODF Plugin. Now you will be able to open odf files whether you use Microsoft Office 2003 or Office 2007.
8) If you don't have time to install any software or don't have administrative privilege and you have Internet connection then you can try any online converter tool such as Zamzar or Media Convert to open an odt file.
9) You can also upload odt file to Google Docs and from google docs you will be able to read the file.
10) Zoho Writer is another option to open odt file.
Sunday, February 28, 2010
Saturday, February 27, 2010
EXP-00008, ORA-04063, ORA-06508, EXP-00083 PL/SQL: could not find program unit
Problem Description
Oracle full database export fails with error stack EXP-00008, ORA-04063, ORA-06508, EXP-00083 like below.
EXP-00008: ORACLE error 4063 encountered
ORA-04063: package body "WMSYS.LT_EXPORT_PKG" has errors
ORA-06508: PL/SQL: could not find program unit being called: "WMSYS.LT_EXPORT_PKG"
ORA-06512: at line 1
EXP-00083: The previous problem occurred when calling WMSYS.LT_EXPORT_PKG.schema_info_exp
Cause of the Problem
The above problems are caused by the revoke of the execute privilege on UTL_FILE package from Public.
Oracle Workspace Manager (OWM) and some other database components (which are not installed in the database) need the privilege to execute procedure SYS.UTL_FILE.
During the creation of a default Database, the Workspace Manager gets installed by default. and the WMSYS user becomes intertwined with the export process and must be valid or at least the major parts for an export to complete properly as the export process looks for any "version-enabled" tables that Workspace Manager schema may be using.
Solution of the Problem
In order to solve above problems do following steps.
1. Grant execute privilege on SYS.UTL_FILE package to WMSYS user.
SQL> grant execute on SYS.UTL_FILE to WMSYS;
2. check for invalid objects in the WMSYS schema using following query,
SQL> select object_name,object_type,owner,status from dba_objects where status='INVALID' and owner='WMSYS';
3. Run script $ORACLE_HOME/rdbms/admin/utlrp.sql
SQL> @$ORACLE_HOME/rdbms/admin/utlrp.sql
Related Documents
http://arjudba.blogspot.com/2010/02/exp-00008-ora-06550-pls-00201-exp-00083.html
http://arjudba.blogspot.com/2010/02/ora-39127-ora-04063-ora-06508-ora-06512.html
http://arjudba.blogspot.com/2010/02/exp-00008-ora-04063-ora-06508-exp-00083.html
http://arjudba.blogspot.com/2009/12/export-fully-fails-with-pls-00201-ora.html
http://arjudba.blogspot.com/2009/12/export-fails-with-exp-00002-error-in.html
http://arjudba.blogspot.com/2009/01/ora-31655-no-data-or-metadata-objects.html
http://arjudba.blogspot.com/2009/01/expdp-fails-with-ora-31693-ora-06502.html
http://arjudba.blogspot.com/2008/12/ora-39095-dump-file-space-has-been.html
http://arjudba.blogspot.com/2008/09/expdp-fails-with-ora-31626-ora-31633.html
http://arjudba.blogspot.com/2008/07/data-pump-export-fails-with-ora-39000.html
http://arjudba.blogspot.com/2009/07/ora-39165-schema-sys-was-not-found-ora.html
http://arjudba.blogspot.com/2009/07/ora-39166-object-was-not-found-sys.html
http://arjudba.blogspot.com/2009/05/ora-39000-ora-39143-dump-file-may-be.html
http://arjudba.blogspot.com/2009/05/expdp-fails-with-ora-39001ora-39169ora.html
Oracle full database export fails with error stack EXP-00008, ORA-04063, ORA-06508, EXP-00083 like below.
EXP-00008: ORACLE error 4063 encountered
ORA-04063: package body "WMSYS.LT_EXPORT_PKG" has errors
ORA-06508: PL/SQL: could not find program unit being called: "WMSYS.LT_EXPORT_PKG"
ORA-06512: at line 1
EXP-00083: The previous problem occurred when calling WMSYS.LT_EXPORT_PKG.schema_info_exp
Cause of the Problem
The above problems are caused by the revoke of the execute privilege on UTL_FILE package from Public.
Oracle Workspace Manager (OWM) and some other database components (which are not installed in the database) need the privilege to execute procedure SYS.UTL_FILE.
During the creation of a default Database, the Workspace Manager gets installed by default. and the WMSYS user becomes intertwined with the export process and must be valid or at least the major parts for an export to complete properly as the export process looks for any "version-enabled" tables that Workspace Manager schema may be using.
Solution of the Problem
In order to solve above problems do following steps.
1. Grant execute privilege on SYS.UTL_FILE package to WMSYS user.
SQL> grant execute on SYS.UTL_FILE to WMSYS;
2. check for invalid objects in the WMSYS schema using following query,
SQL> select object_name,object_type,owner,status from dba_objects where status='INVALID' and owner='WMSYS';
3. Run script $ORACLE_HOME/rdbms/admin/utlrp.sql
SQL> @$ORACLE_HOME/rdbms/admin/utlrp.sql
Related Documents
http://arjudba.blogspot.com/2010/02/exp-00008-ora-06550-pls-00201-exp-00083.html
http://arjudba.blogspot.com/2010/02/ora-39127-ora-04063-ora-06508-ora-06512.html
http://arjudba.blogspot.com/2010/02/exp-00008-ora-04063-ora-06508-exp-00083.html
http://arjudba.blogspot.com/2009/12/export-fully-fails-with-pls-00201-ora.html
http://arjudba.blogspot.com/2009/12/export-fails-with-exp-00002-error-in.html
http://arjudba.blogspot.com/2009/01/ora-31655-no-data-or-metadata-objects.html
http://arjudba.blogspot.com/2009/01/expdp-fails-with-ora-31693-ora-06502.html
http://arjudba.blogspot.com/2008/12/ora-39095-dump-file-space-has-been.html
http://arjudba.blogspot.com/2008/09/expdp-fails-with-ora-31626-ora-31633.html
http://arjudba.blogspot.com/2008/07/data-pump-export-fails-with-ora-39000.html
http://arjudba.blogspot.com/2009/07/ora-39165-schema-sys-was-not-found-ora.html
http://arjudba.blogspot.com/2009/07/ora-39166-object-was-not-found-sys.html
http://arjudba.blogspot.com/2009/05/ora-39000-ora-39143-dump-file-may-be.html
http://arjudba.blogspot.com/2009/05/expdp-fails-with-ora-39001ora-39169ora.html
EXP-00008, ORA-06550, PLS-00201, EXP-00083 identifier 'SYS.LT_EXPORT_PKG' must be declared
Problem Description
When I try to do full database export it fails will following errors as below.
exporting post-schema procedural objects and actions
EXP-00008: ORACLE error 6550 encountered
ORA-06550: line 1, column 13:
PLS-00201: identifier 'SYS.LT_EXPORT_PKG' must be declared
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
EXP-00083: The previous problem occurred when calling SYS.LT_EXPORT_PKG.schema_info_exp
. exporting statistics
.
Cause of the Problem
The above problem happened because the Workspace Manager component is not there. You can check from querying db_registry as below.
So we see that OWM is not installed. May be WMSYS user has been dropped.
The SYS.LT_EXPORT_PKG is created by the Oracle Workspace Manager (OWM).
OWM (Oracle Worspace Manager) is now closely integrated with much of the functionality of Oracle, especially the export. The export process looks for any "version-enabled" tables that Workspace Manager may be using. The WMSYS user is used to store all the metadata information for OWM and it is recommended to not remove the OWM user.
Solution of the Problem
The error stack "EXP-00008, ORA-06550, PLS-00201, EXP-00083 identifier 'SYS.LT_EXPORT_PKG' must be declared" are just an informational messages only and you can avoid those. The export utility is throwing warnings and then proceeding ahead. The export does not error out or stop abruptly.
Note that, the versioning feature has been closely incorporated into the export utility and hence it checks the versioning repository for such version enabled tables. But as the versioning metadata information is not found (as the WMSYS user holding this metadata has been dropped), it throws this informational messages.
If you really do not bother with the Oracle Workspace Manager component, just ignore the
message. But in case you want to eliminate this warning messages as well, you can either deinstall the Oracle Workspace Manager or re-install it.
Steps to Recreate WMSYS user(Oracle Workspace Manager)
1) Execute $ORACLE_HOME/rdbms/admin/owminst.plb as SYS user from SQL*PLUS prompt.
- $sqlplus / as sysdba
- SQL> @$ORACLE_HOME/rdbms/admin/owminst.plb
Steps to uninstall Oracle Workspace Manager (OWM)
1) Disable versioning on all version-enabled tables in the database before de-installing Oracle Workspace Manager.
2) Login to SQL*Plus as SYSDBA, invoke the owmuinst.plb de-installation script as below.
$ sqlplus / as sysdba
SQL> @$ORACLE_HOME/rdbms/admin/owmuinst.plb
Note that, de-installing Oracle Workspace Manager will remove any existing workspaces and the associated metadata.
Related Documents
http://arjudba.blogspot.com/2010/02/exp-00008-ora-06550-pls-00201-exp-00083.html
http://arjudba.blogspot.com/2010/02/ora-39127-ora-04063-ora-06508-ora-06512.html
http://arjudba.blogspot.com/2010/02/exp-00008-ora-04063-ora-06508-exp-00083.html
http://arjudba.blogspot.com/2009/12/export-fully-fails-with-pls-00201-ora.html
http://arjudba.blogspot.com/2009/12/export-fails-with-exp-00002-error-in.html
http://arjudba.blogspot.com/2009/01/ora-31655-no-data-or-metadata-objects.html
http://arjudba.blogspot.com/2009/01/expdp-fails-with-ora-31693-ora-06502.html
http://arjudba.blogspot.com/2008/12/ora-39095-dump-file-space-has-been.html
http://arjudba.blogspot.com/2008/09/expdp-fails-with-ora-31626-ora-31633.html
http://arjudba.blogspot.com/2008/07/data-pump-export-fails-with-ora-39000.html
http://arjudba.blogspot.com/2009/07/ora-39165-schema-sys-was-not-found-ora.html
http://arjudba.blogspot.com/2009/07/ora-39166-object-was-not-found-sys.html
http://arjudba.blogspot.com/2009/05/ora-39000-ora-39143-dump-file-may-be.html
http://arjudba.blogspot.com/2009/05/expdp-fails-with-ora-39001ora-39169ora.html
When I try to do full database export it fails will following errors as below.
exporting post-schema procedural objects and actions
EXP-00008: ORACLE error 6550 encountered
ORA-06550: line 1, column 13:
PLS-00201: identifier 'SYS.LT_EXPORT_PKG' must be declared
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
EXP-00083: The previous problem occurred when calling SYS.LT_EXPORT_PKG.schema_info_exp
. exporting statistics
.
Cause of the Problem
The above problem happened because the Workspace Manager component is not there. You can check from querying db_registry as below.
SQL> select comp_id, version, status from dba_registry is giving the following info :
COMP_ID VERSION STATUS
------------------------------ ------------------------------ -----------
CATPROC 10.1.0.2.0 VALID
RAC 10.1.0.2.0 INVALID
CATALOG 10.1.0.2.0 VALID
XDB 10.1.0.2.0 VALID
So we see that OWM is not installed. May be WMSYS user has been dropped.
The SYS.LT_EXPORT_PKG is created by the Oracle Workspace Manager (OWM).
OWM (Oracle Worspace Manager) is now closely integrated with much of the functionality of Oracle, especially the export. The export process looks for any "version-enabled" tables that Workspace Manager may be using. The WMSYS user is used to store all the metadata information for OWM and it is recommended to not remove the OWM user.
Solution of the Problem
The error stack "EXP-00008, ORA-06550, PLS-00201, EXP-00083 identifier 'SYS.LT_EXPORT_PKG' must be declared" are just an informational messages only and you can avoid those. The export utility is throwing warnings and then proceeding ahead. The export does not error out or stop abruptly.
Note that, the versioning feature has been closely incorporated into the export utility and hence it checks the versioning repository for such version enabled tables. But as the versioning metadata information is not found (as the WMSYS user holding this metadata has been dropped), it throws this informational messages.
If you really do not bother with the Oracle Workspace Manager component, just ignore the
message. But in case you want to eliminate this warning messages as well, you can either deinstall the Oracle Workspace Manager or re-install it.
Steps to Recreate WMSYS user(Oracle Workspace Manager)
1) Execute $ORACLE_HOME/rdbms/admin/owminst.plb as SYS user from SQL*PLUS prompt.
- $sqlplus / as sysdba
- SQL> @$ORACLE_HOME/rdbms/admin/owminst.plb
Steps to uninstall Oracle Workspace Manager (OWM)
1) Disable versioning on all version-enabled tables in the database before de-installing Oracle Workspace Manager.
2) Login to SQL*Plus as SYSDBA, invoke the owmuinst.plb de-installation script as below.
$ sqlplus / as sysdba
SQL> @$ORACLE_HOME/rdbms/admin/owmuinst.plb
Note that, de-installing Oracle Workspace Manager will remove any existing workspaces and the associated metadata.
Related Documents
http://arjudba.blogspot.com/2010/02/exp-00008-ora-06550-pls-00201-exp-00083.html
http://arjudba.blogspot.com/2010/02/ora-39127-ora-04063-ora-06508-ora-06512.html
http://arjudba.blogspot.com/2010/02/exp-00008-ora-04063-ora-06508-exp-00083.html
http://arjudba.blogspot.com/2009/12/export-fully-fails-with-pls-00201-ora.html
http://arjudba.blogspot.com/2009/12/export-fails-with-exp-00002-error-in.html
http://arjudba.blogspot.com/2009/01/ora-31655-no-data-or-metadata-objects.html
http://arjudba.blogspot.com/2009/01/expdp-fails-with-ora-31693-ora-06502.html
http://arjudba.blogspot.com/2008/12/ora-39095-dump-file-space-has-been.html
http://arjudba.blogspot.com/2008/09/expdp-fails-with-ora-31626-ora-31633.html
http://arjudba.blogspot.com/2008/07/data-pump-export-fails-with-ora-39000.html
http://arjudba.blogspot.com/2009/07/ora-39165-schema-sys-was-not-found-ora.html
http://arjudba.blogspot.com/2009/07/ora-39166-object-was-not-found-sys.html
http://arjudba.blogspot.com/2009/05/ora-39000-ora-39143-dump-file-may-be.html
http://arjudba.blogspot.com/2009/05/expdp-fails-with-ora-39001ora-39169ora.html
Friday, February 26, 2010
ORA-39127 ORA-04063 ORA-06508 ORA-06512 package body "WMSYS.LT_EXPORT_PKG" has errors
Problem Description
While doing data pump full database export, in the error log following error messages are generated.
Cause of the Problem
The above error stack is generated because WORKSPACE , XDB schemas have invalid objects.
Solution of the Problem
The solution is to validate LT_EXPORT_PKG package. In order to validate LT_EXPORT_PKG package, run $ORACLE_HOME/rdbms/admin/owminst.plb script as SYS user.
- $sqlplus / as sysdba
- SQL> @$ORACLE_HOME/rdbms/admin/owminst.plb
Related Documents
http://arjudba.blogspot.com/2010/02/exp-00008-ora-06550-pls-00201-exp-00083.html
http://arjudba.blogspot.com/2010/02/ora-39127-ora-04063-ora-06508-ora-06512.html
http://arjudba.blogspot.com/2010/02/exp-00008-ora-04063-ora-06508-exp-00083.html
http://arjudba.blogspot.com/2009/12/export-fully-fails-with-pls-00201-ora.html
http://arjudba.blogspot.com/2009/12/export-fails-with-exp-00002-error-in.html
http://arjudba.blogspot.com/2009/01/ora-31655-no-data-or-metadata-objects.html
http://arjudba.blogspot.com/2009/01/expdp-fails-with-ora-31693-ora-06502.html
http://arjudba.blogspot.com/2008/12/ora-39095-dump-file-space-has-been.html
http://arjudba.blogspot.com/2008/09/expdp-fails-with-ora-31626-ora-31633.html
http://arjudba.blogspot.com/2008/07/data-pump-export-fails-with-ora-39000.html
http://arjudba.blogspot.com/2009/07/ora-39165-schema-sys-was-not-found-ora.html
http://arjudba.blogspot.com/2009/07/ora-39166-object-was-not-found-sys.html
http://arjudba.blogspot.com/2009/05/ora-39000-ora-39143-dump-file-may-be.html
http://arjudba.blogspot.com/2009/05/expdp-fails-with-ora-39001ora-39169ora.html
While doing data pump full database export, in the error log following error messages are generated.
Processing object type DATABASE_EXPORT/SCHEMA/TYPE/TYPE_SPEC
ORA-39127: unexpected error from call to export_string :=WMSYS.LT_EXPORT_PKG.system_info_exp(0,dynconnect,10.02.00.02.00',newblock)
ORA-04063: package body "WMSYS.LT_EXPORT_PKG" has errors
ORA-06508: PL/SQL: could not find program unit being called: "WMSYS.LT_EXPORT_PKG"
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5334
Processing object type DATABASE_EXPORT/SYSTEM_PROCOBJACT/PRE_SYSTEM_ACTIONS/PROCACT_SYSTEM
Processing object type DATABASE_EXPORT/SYSTEM_PROCOBJACT/PROCOBJ
ORA-39127: unexpected error from call to export_string :=WMSYS.LT_EXPORT_PKG.system_info_exp(1,dynconnect,10.02.00.02.00',newblock)
ORA-04063: package body "WMSYS.LT_EXPORT_PKG" has errors
ORA-06508: PL/SQL: could not find program unit being called: "WMSYS.LT_EXPORT_PKG"
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5334
Processing object type DATABASE_EXPORT/SYSTEM_PROCOBJACT/POST_SYSTEM_ACTIONS/PROCACT_SYSTEM
ORA-39127: unexpected error from call to export_string :=WMSYS.LT_EXPORT_PKG.schema_info_exp('SYS',0,1,'10.02.00.02.00',newblock)
ORA-04063: package body "WMSYS.LT_EXPORT_PKG" has errors
ORA-06508: PL/SQL: could not find program unit being called: "WMSYS.LT_EXPORT_PKG"
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5419
ORA-39127: unexpected error from call to export_string :=WMSYS.LT_EXPORT_PKG.schema_info_exp('SYSTEM',0,1,'10.02.00.02.00',newblock)
ORA-04063: package body "WMSYS.LT_EXPORT_PKG" has errors
ORA-06508: PL/SQL: could not find program unit being called: "WMSYS.LT_EXPORT_PKG"
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5419
ORA-39127: unexpected error from call to export_string :=WMSYS.LT_EXPORT_PKG.schema_info_exp('OUTLN',0,1,'10.02.00.02.00',newblock)
ORA-04063: package body "WMSYS.LT_EXPORT_PKG" has errors
ORA-06508: PL/SQL: could not find program unit being called: "WMSYS.LT_EXPORT_PKG"
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5419
ORA-39127: unexpected error from call to export_string :=WMSYS.LT_EXPORT_PKG.schema_info_exp('VIEWSTAR',0,1,'10.02.00.02.00',newblock)
ORA-04063: package body "WMSYS.LT_EXPORT_PKG" has errors
ORA-06508: PL/SQL: could not find program unit being called: "WMSYS.LT_EXPORT_PKG"
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5419
ORA-39127: unexpected error from call to export_string :=WMSYS.LT_EXPORT_PKG.schema_info_exp('EXP_DBA',0,1,'10.02.00.02.00',newblock)
ORA-04063: package body "WMSYS.LT_EXPORT_PKG" has errors
ORA-06508: PL/SQL: could not find program unit being called: "WMSYS.LT_EXPORT_PKG"
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5419
ORA-39127: unexpected error from call to export_string :=WMSYS.LT_EXPORT_PKG.schema_info_exp('TSMSYS',0,1,'10.02.00.02.00',newblock)
ORA-04063: package body "WMSYS.LT_EXPORT_PKG" has errors
ORA-06508: PL/SQL: could not find program unit being called: "WMSYS.LT_EXPORT_PKG"
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5419
ORA-39127: unexpected error from call to export_string :=WMSYS.LT_EXPORT_PKG.schema_info_exp('PTASUSER',0,1,'10.02.00.02.00',newblock)
ORA-04063: package body "WMSYS.LT_EXPORT_PKG" has errors
ORA-06508: PL/SQL: could not find program unit being called: "WMSYS.LT_EXPORT_PKG"
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5419
ORA-39127: unexpected error from call to export_string :=WMSYS.LT_EXPORT_PKG.schema_info_exp('VSUSER',0,1,'10.02.00.02.00',newblock)
ORA-04063: package body "WMSYS.LT_EXPORT_PKG" has errors
ORA-06508: PL/SQL: could not find program unit being called: "WMSYS.LT_EXPORT_PKG"
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5419
ORA-39127: unexpected error from call to export_string :=WMSYS.LT_EXPORT_PKG.schema_info_exp('PARTDB',0,1,'10.02.00.02.00',newblock)
ORA-04063: package body "WMSYS.LT_EXPORT_PKG" has errors
ORA-06508: PL/SQL: could not find program unit being called: "WMSYS.LT_EXPORT_PKG"
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5419
ORA-39127: unexpected error from call to export_string :=WMSYS.LT_EXPORT_PKG.schema_info_exp('WORKFLOW',0,1,'10.02.00.02.00',newblock)
ORA-04063: package body "WMSYS.LT_EXPORT_PKG" has errors
ORA-06508: PL/SQL: could not find program unit being called: "WMSYS.LT_EXPORT_PKG"
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5419
ORA-39127: unexpected error from call to export_string :=WMSYS.LT_EXPORT_PKG.schema_info_exp('QUEUEDB',0,1,'10.02.00.02.00',newblock)
ORA-04063: package body "WMSYS.LT_EXPORT_PKG" has errors
ORA-06508: PL/SQL: could not find program unit being called: "WMSYS.LT_EXPORT_PKG"
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5419
ORA-39127: unexpected error from call to export_string :=WMSYS.LT_EXPORT_PKG.schema_info_exp('CASCAN',0,1,'10.02.00.02.00',newblock)
ORA-04063: package body "WMSYS.LT_EXPORT_PKG" has errors
ORA-06508: PL/SQL: could not find program unit being called: "WMSYS.LT_EXPORT_PKG"
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5419
ORA-39127: unexpected error from call to export_string :=WMSYS.LT_EXPORT_PKG.schema_info_exp('DAADMIN',0,1,'10.02.00.02.00',newblock)
ORA-04063: package body "WMSYS.LT_EXPORT_PKG" has errors
ORA-06508: PL/SQL: could not find program unit being called: "WMSYS.LT_EXPORT_PKG"
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5419
Cause of the Problem
The above error stack is generated because WORKSPACE , XDB schemas have invalid objects.
Solution of the Problem
The solution is to validate LT_EXPORT_PKG package. In order to validate LT_EXPORT_PKG package, run $ORACLE_HOME/rdbms/admin/owminst.plb script as SYS user.
- $sqlplus / as sysdba
- SQL> @$ORACLE_HOME/rdbms/admin/owminst.plb
Related Documents
http://arjudba.blogspot.com/2010/02/exp-00008-ora-06550-pls-00201-exp-00083.html
http://arjudba.blogspot.com/2010/02/ora-39127-ora-04063-ora-06508-ora-06512.html
http://arjudba.blogspot.com/2010/02/exp-00008-ora-04063-ora-06508-exp-00083.html
http://arjudba.blogspot.com/2009/12/export-fully-fails-with-pls-00201-ora.html
http://arjudba.blogspot.com/2009/12/export-fails-with-exp-00002-error-in.html
http://arjudba.blogspot.com/2009/01/ora-31655-no-data-or-metadata-objects.html
http://arjudba.blogspot.com/2009/01/expdp-fails-with-ora-31693-ora-06502.html
http://arjudba.blogspot.com/2008/12/ora-39095-dump-file-space-has-been.html
http://arjudba.blogspot.com/2008/09/expdp-fails-with-ora-31626-ora-31633.html
http://arjudba.blogspot.com/2008/07/data-pump-export-fails-with-ora-39000.html
http://arjudba.blogspot.com/2009/07/ora-39165-schema-sys-was-not-found-ora.html
http://arjudba.blogspot.com/2009/07/ora-39166-object-was-not-found-sys.html
http://arjudba.blogspot.com/2009/05/ora-39000-ora-39143-dump-file-may-be.html
http://arjudba.blogspot.com/2009/05/expdp-fails-with-ora-39001ora-39169ora.html
Wednesday, February 17, 2010
RMAN-06900 RMAN-06901 ORA-19921: maximum number of 64 rows exceeded
Problem Description
RMAN backup completed successfully but backup logs shows warning message as,
RMAN-06900: WARNING: unable to generate V$RMAN_STATUS or V$RMAN_OUTPUT row
RMAN-06901: WARNING: disabling update of the V$RMAN_STATUS and V$RMAN_OUTPUT rows ORACLE error from target database:
ORA-19921: maximum number of 64 rows exceeded
A variant version of warning message is like below,
connected to target database: PROD1 (DBID=3378321056)
RMAN-06900: WARNING: unable to generate V$RMAN_STATUS or V$RMAN_OUTPUT row
RMAN-06901: WARNING: disabling update of the V$RMAN_STATUS and V$RMAN_OUTPUT rows
ORACLE error from target database:
ORA-19921: maximum number of 128 rows exceeded
Cause of the Problem
The RMAN-06900 RMAN-06901 ORA-19921 error stack indicates oracle RMAN bug. ORA-19921: maximum number of 64 rows exceeded is oracle bug 4659734 and ORA-19921: MAXIMUM NUMBER OF 128 ROWS EXCEEDED is oracle Bug 8264365. This bug fires when the RMAN output is too huge because it couldn't log the output in v$rman_output.
Solution of the Problem
If your RMAN goes well and you only see warning message in your RMAN log then simply you can ignore these warnings. The bug "ORA-19921: maximum number of 64 rows exceeded" is fixed in Oracle 10.2.0.4 version and in 11g. So to solve it upgrade your oracle version or apply oracle patch. If you already have oracle version 10.2.0.4 + and hit this bug then in fact you should do nothing and just to wait for oracle to resolve the issue.
Related Documents
http://arjudba.blogspot.com/2010/01/rman-00571-rman-00569-rman-00571-rman.html
http://arjudba.blogspot.com/2010/01/rman-06900-rman-06901-ora-19921-maximum.html
RMAN backup completed successfully but backup logs shows warning message as,
RMAN-06900: WARNING: unable to generate V$RMAN_STATUS or V$RMAN_OUTPUT row
RMAN-06901: WARNING: disabling update of the V$RMAN_STATUS and V$RMAN_OUTPUT rows ORACLE error from target database:
ORA-19921: maximum number of 64 rows exceeded
A variant version of warning message is like below,
connected to target database: PROD1 (DBID=3378321056)
RMAN-06900: WARNING: unable to generate V$RMAN_STATUS or V$RMAN_OUTPUT row
RMAN-06901: WARNING: disabling update of the V$RMAN_STATUS and V$RMAN_OUTPUT rows
ORACLE error from target database:
ORA-19921: maximum number of 128 rows exceeded
Cause of the Problem
The RMAN-06900 RMAN-06901 ORA-19921 error stack indicates oracle RMAN bug. ORA-19921: maximum number of 64 rows exceeded is oracle bug 4659734 and ORA-19921: MAXIMUM NUMBER OF 128 ROWS EXCEEDED is oracle Bug 8264365. This bug fires when the RMAN output is too huge because it couldn't log the output in v$rman_output.
Solution of the Problem
If your RMAN goes well and you only see warning message in your RMAN log then simply you can ignore these warnings. The bug "ORA-19921: maximum number of 64 rows exceeded" is fixed in Oracle 10.2.0.4 version and in 11g. So to solve it upgrade your oracle version or apply oracle patch. If you already have oracle version 10.2.0.4 + and hit this bug then in fact you should do nothing and just to wait for oracle to resolve the issue.
Related Documents
http://arjudba.blogspot.com/2010/01/rman-00571-rman-00569-rman-00571-rman.html
http://arjudba.blogspot.com/2010/01/rman-06900-rman-06901-ora-19921-maximum.html
ORA-00204 ORA-00202 ORA-27071 HP-UX Error: 9: Bad file number
Problem Description
RMAN backup fails with ORA-00204 ORA-00202 ORA-27071 HP-UX Error: 9: Bad file number as below.
Recovery Manager: Release 11.1.0.7.0 - Production on Fri Jan 29 00:01:15 2010
Copyright (c) 1982, 2007, Oracle. All rights reserved.
RMAN-06900: WARNING: unable to generate V$RMAN_STATUS or V$RMAN_OUTPUT row
RMAN-06901: WARNING: disabling update of the V$RMAN_STATUS and V$RMAN_OUTPUT rows
ORACLE error from target database:
ORA-00204: error in reading (block 1, # blocks 1) of control file
ORA-00202: control file: '/SID/oradata/APEXP/control01.ctl'
ORA-27071: unable to seek to desired position in file
HP-UX Error: 9: Bad file number
An another version of error message appear while starting RMAN is,
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-06003: ORACLE error from target database:
ORA-00204: error in reading (block 3, # blocks 1) of control file
ORA-00202: control file: '/SID/oradata/APEXP/control01.ctl'
ORA-27071: unable to seek to desired position in file
HP-UX Error: 9: Bad file number Additional information: 2
Cause of the Problem
The RMAN-06900, RMAN-06901 error occurs when the RMAN couldn't log the output in $rman_output. The actual investigation of the error comes in the associated additional error messages. If you look for additional error message we will see ORA-27071, HP-UX Error: 9: Bad file number. The word 'HP-UX Error: 9: Bad file number' indicates that error is coming from operating system. The OS user who is invoking RMAN don't have OS permission on the control file and hence HP-UX generates bad file number error.
Solution of the Problem
The user who is invoking RMAN don't have write permission on the controlfile. You must need to change permission from operating system. You can do so by issuing,
$chmod 666 /SID/oradata/APEXP/control01.ctl
After you change the permission now try to invoke RMAN command again.
Related Documents:
RMAN backup fails with ORA-00204 ORA-00202 ORA-27071 HP-UX Error: 9: Bad file number as below.
Recovery Manager: Release 11.1.0.7.0 - Production on Fri Jan 29 00:01:15 2010
Copyright (c) 1982, 2007, Oracle. All rights reserved.
RMAN-06900: WARNING: unable to generate V$RMAN_STATUS or V$RMAN_OUTPUT row
RMAN-06901: WARNING: disabling update of the V$RMAN_STATUS and V$RMAN_OUTPUT rows
ORACLE error from target database:
ORA-00204: error in reading (block 1, # blocks 1) of control file
ORA-00202: control file: '/SID/oradata/APEXP/control01.ctl'
ORA-27071: unable to seek to desired position in file
HP-UX Error: 9: Bad file number
An another version of error message appear while starting RMAN is,
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-06003: ORACLE error from target database:
ORA-00204: error in reading (block 3, # blocks 1) of control file
ORA-00202: control file: '/SID/oradata/APEXP/control01.ctl'
ORA-27071: unable to seek to desired position in file
HP-UX Error: 9: Bad file number Additional information: 2
Cause of the Problem
The RMAN-06900, RMAN-06901 error occurs when the RMAN couldn't log the output in $rman_output. The actual investigation of the error comes in the associated additional error messages. If you look for additional error message we will see ORA-27071, HP-UX Error: 9: Bad file number. The word 'HP-UX Error: 9: Bad file number' indicates that error is coming from operating system. The OS user who is invoking RMAN don't have OS permission on the control file and hence HP-UX generates bad file number error.
Solution of the Problem
The user who is invoking RMAN don't have write permission on the controlfile. You must need to change permission from operating system. You can do so by issuing,
$chmod 666 /SID/oradata/APEXP/control01.ctl
After you change the permission now try to invoke RMAN command again.
Related Documents:
How to Restore the Controlfile from Backup.
ORA-00214: Controlfile Version Inconsistent on Startup or Shutdown
Controlfile in Oracle Database.
New Feature of 10.2g: Eliminate Control File Re-Creation
Creating controlfile fails with ORA-01503, ORA-01161
Backup Database control file -User Managed
Recover database after only lose of all controlfiles
Tuesday, February 16, 2010
ORA-01624: log needed for crash recovery
Error Description
In the database dropping standby redo logfile fails with error ORA-01624 as below.
SQL> alter database drop standby logfile group 2;
alter database drop standby logfile group 2
*
ERROR at line 1:
ORA-01624: log 2 needed for crash recovery of instance ctl3 (thread 1)
ORA-00312: online log 2 thread 1: '/oradata3/ctl3/redo02.log'
ORA-00312: online log 2 thread 1: '/oraidx3/ctl3/redo02b.log'
Cause of the Problem
The Online redo log which is being dropped on the primary is either the current online redo log or
it has not completely been archived yet. To know more about the redo logfile status see Redo Log file status. By querying the V$LOG view you can see the status of the redo log file. In order to drop a redo log file the status column should be 'INACTIVE'.
Solution of the Problem
1) Switch the logfile on primary database so that group can become non-current.
SQL> ALTER DATABASE SWITCH LOGFILE;
2) Copy the standby logfile from primary database to standby database.
3) In the primary database move the logfile to a different location
4) Rename the logfile
5) Clear the logfile using 'alter database clear logfile group ..'
6) Drop the standby logfile using 'alter database drop standby logfile group ...'
Related Documents
In the database dropping standby redo logfile fails with error ORA-01624 as below.
SQL> alter database drop standby logfile group 2;
alter database drop standby logfile group 2
*
ERROR at line 1:
ORA-01624: log 2 needed for crash recovery of instance ctl3 (thread 1)
ORA-00312: online log 2 thread 1: '/oradata3/ctl3/redo02.log'
ORA-00312: online log 2 thread 1: '/oraidx3/ctl3/redo02b.log'
Cause of the Problem
The Online redo log which is being dropped on the primary is either the current online redo log or
it has not completely been archived yet. To know more about the redo logfile status see Redo Log file status. By querying the V$LOG view you can see the status of the redo log file. In order to drop a redo log file the status column should be 'INACTIVE'.
Solution of the Problem
1) Switch the logfile on primary database so that group can become non-current.
SQL> ALTER DATABASE SWITCH LOGFILE;
2) Copy the standby logfile from primary database to standby database.
3) In the primary database move the logfile to a different location
4) Rename the logfile
5) Clear the logfile using 'alter database clear logfile group ..'
6) Drop the standby logfile using 'alter database drop standby logfile group ...'
Related Documents
Startup fails with oracle error ORA-00119, ORA-00132
Subscribe to:
Posts (Atom)