ITPub博客

首页 > 数据库 > Oracle > 一个schema备份日志发现ORA-39097,ORA-39065,ORA-12801,ORA-01460 异常

一个schema备份日志发现ORA-39097,ORA-39065,ORA-12801,ORA-01460 异常

原创 Oracle 作者:呱呱牛 时间:2015-12-09 10:15:10 0 删除 编辑
在检查逻辑备份的时候,发现了一个schema备份未成功,在自己运维的RAC环境中, 只有两个实例。 每一个实例下有4个schema,唯独这个天天被并行访问的schema产生异常。

点击(此处)折叠或打开

  1. ;;;
  2. Export: Release 11.2.0.3.0 - Production on 星期一 12月 7 02:30:00 2015
  3. Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
  4. ;;;
  5. 连接到: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
  6. With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
  7. Data Mining and Real Application Testing options
  8. ;;; 由于以下参数, 旧有模式处于活动状态:
  9. ;;; 旧有模式参数: "log=********20151207.log" 位置: Command Line, 替换为: "logfile=********20151207.log"
  10. ;;; 旧有模式设置了 reuse_dumpfiles=true 参数。
  11. 启动 "********"."SYS_EXPORT_SCHEMA_14": ********/******** DIRECTORY=dpdata DUMPFILE=********20151207.dmp SCHEMAS=******** EXCLUDE=TABLE:" LIKE('LOCATION%')" logfile=********20151207.log reuse_dumpfiles=true
  12. 正在使用 BLOCKS 方法进行估计...
  13. 处理对象类型 SCHEMA_EXPORT/TABLE/TABLE_DATA
  14. 使用 BLOCKS 方法的总估计: 49.35 GB
  15. 处理对象类型 SCHEMA_EXPORT/USER
  16. 处理对象类型 SCHEMA_EXPORT/SYSTEM_GRANT
  17. 处理对象类型 SCHEMA_EXPORT/ROLE_GRANT
  18. 处理对象类型 SCHEMA_EXPORT/DEFAULT_ROLE
  19. 处理对象类型 SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
  20. 处理对象类型 SCHEMA_EXPORT/SEQUENCE/SEQUENCE
  21. 处理对象类型 SCHEMA_EXPORT/TABLE/TABLE
  22. 处理对象类型 SCHEMA_EXPORT/TABLE/COMMENT
  23. 处理对象类型 SCHEMA_EXPORT/PACKAGE/PACKAGE_SPEC
  24. 处理对象类型 SCHEMA_EXPORT/PROCEDURE/PROCEDURE
  25. 处理对象类型 SCHEMA_EXPORT/PACKAGE/COMPILE_PACKAGE/PACKAGE_SPEC/ALTER_PACKAGE_SPEC
  26. 处理对象类型 SCHEMA_EXPORT/PROCEDURE/ALTER_PROCEDURE
  27. 处理对象类型 SCHEMA_EXPORT/TABLE/INDEX/INDEX
  28. 处理对象类型 SCHEMA_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
  29. 处理对象类型 SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
  30. 处理对象类型 SCHEMA_EXPORT/TABLE/CONSTRAINT/REF_CONSTRAINT
  31. 处理对象类型 SCHEMA_EXPORT/TABLE/TRIGGER
  32. 处理对象类型 SCHEMA_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
  33. ORA-39097: 数据泵作业出现意外的错误 -12801
  34. ORA-39065: MAIN 中出现意外的主进程异常错误
  35. ORA-12801: 并行查询服务器 PZ99, instance inds-02:inds2 (2) 中发出错误信号
  36. ORA-01460: 转换请求无法实施或不合理
  37. 作业 "********"."SYS_EXPORT_SCHEMA_14" 因致命错误于 02:35:37 停止
  38. 查询了下资料 , RAC的双节点的 PARALLEL_DEGREE_POLICY 也都是manual的
  39. SQL> select * from v$version;
  40. BANNER
  41. ----------------------------------------------------------------------------------------------------------------------------------------------------------------
  42. Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
  43. PL/SQL Release 11.2.0.3.0 - Production
  44. CORE 11.2.0.3.0 Production
  45. TNS for Solaris: Version 11.2.0.3.0 - Production
  46. NLSRTL Version 11.2.0.3.0 - Production
  47. SQL> show parameter PARALLEL_DEGREE_POLICY;
  48. NAME TYPE VALUE
  49. ------------------------------------ ---------------------- ------------------------------
  50. parallel_degree_policy string MANUAL
  51. SQL>
无法备份成功的原因,官方给出的解释

点击(此处)折叠或打开


  1. Changes
  2. The fix for Bug 9375300 is applied (this fix is included starting with 11.2.0.2 PSU 5 and in 11.2.0.3).

  3. The workaround from:
  4. Note 1427537.1 - DataPump Import (IMPDP) Fails With Errors ORA-39097 ORA-39065 ORA-12801 ORA-1460 In RAC Environment
  5. to set PARALLEL_DEGREE_POLICY=MANUAL in all instances was used without success.
  6. Cause
  7. The errors are caused by:
  8. Bug 13099577 - ORA-1460 with parallel query

  9. This is a regression introduced in 11.2.0.2.5 and 11.2.0.3 by the fix for Bug 9375300

  10. The bug is fixed a.o. fixed in
  11. 12.1.0.1 (Base Release)
  12. 11.2.0.4 (Server Patch Set)
  13. For the above and other fixed versions, refer to:
  14. Please also refer to
  15. Note 13099577.8 - Bug 13099577 - ora-12801 and ORA-1460 with parallel query
运维的RAC 环境是通过修改参数值PARALLEL_FORCE_LOCAL解决的,也可以通过PSU方式解决

点击(此处)折叠或打开

  1. A possible workaround is to set (in all instances):
  2.     PARALLEL_FORCE_LOCAL=TRUE
  3.     By setting PARALLEL_FORCE_LOCAL to TRUE, the parallel server processes are restricted.
  4.     This way, they can only operate on the same RAC node where the DW coordinator process resides.

点击(此处)折叠或打开

  1. SQL> alter system set parallel_force_local=true;

  2. 系统已更改。

  3. SQL> show parameter parallel

  4. NAME TYPE VALUE
  5. ------------------------------------ ---------------------- ------------------------------
  6. fast_start_parallel_rollback string LOW
  7. parallel_adaptive_multi_user boolean TRUE
  8. parallel_automatic_tuning boolean FALSE
  9. parallel_degree_limit string CPU
  10. parallel_degree_policy string MANUAL
  11. parallel_execution_message_size integer 16384
  12. parallel_force_local boolean TRUE
  13. parallel_instance_group string
  14. parallel_io_cap_enabled boolean FALSE
  15. parallel_max_servers integer 985
  16. parallel_min_percent integer 0

  17. NAME TYPE VALUE
  18. ------------------------------------ ---------------------- ------------------------------
  19. parallel_min_servers integer 0
  20. parallel_min_time_threshold string AUTO
  21. parallel_server boolean TRUE
  22. parallel_server_instances integer 2
  23. parallel_servers_target integer 512
  24. parallel_threads_per_cpu integer 2
  25. recovery_parallelism
在负责RAC数据库中的解决方法:

点击(此处)折叠或打开

  1. alter system set parallel_force_local=FALSE;
  2. expdp XXX/XXX@DS133 DIRECTORY=dpdata DUMPFILE=XXX`date +'%Y%m%d'`.dmp PARALLEL=1 CLUSTER=N SCHEMAS=XXX EXCLUDE=TABLE:\" LIKE\(\'LOCATION%\'\)\" log=XXX`date +'%Y%m%d'`.log





来自 “ ITPUB博客 ” ,链接:https://blog.itpub.net/27039319/viewspace-1868836/ ,如需转载,请注明出处,否则将追究法律责任。

请登录后发表评论 登录
全部评论

注册时间:2014-05-29

  • 博文量
    96
  • 访问量
    286799