Impdp Fails With ORA-39126 ORA-31604 Iinvalid Transform NAME Parameter "MODIFY" For Object Type PROCACT_INSTANCE in function ADD_TRANSFORM (Doc ID 1596495.1)

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
SYMPTOMS
DataPump shows following errors :
 
Starting "<LOGIN_SCHEMA>"."SYS_IMPORT_FULL_14":  <LOGIN>/******** parfile=<PARFILE_NAME>.par logfile=<LOG_NAME>.log dumpfile=<DUMPFILE_NAME>.dmp parallel=1
Processing object type TABLE_EXPORT/TABLE/PROCACT_INSTANCE
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.LOAD_MD_TRANSFORMS []
ORA-31604: invalid transform NAME parameter "MODIFY" for object type PROCACT_INSTANCE in function ADD_TRANSFORM
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 86
ORA-06512: at "SYS.KUPW$WORKER", line 8996
  
 
CHANGES
  
 
CAUSE
The cause of this problem has been identified in
Bug 16551094 - DATAPUMP IMPORT REMAP_TABLE FAILS WITH ORA-39126, ORA-31604
 
The bug is fixed in 12c.
 
 
SOLUTION
Download and apply the patch 16551094 if available for your version and platform.
 
Or
 
You can workaround the issue by specifying exclude=PROCACT_INSTANCE.
To implement the fix, please execute the following step:
 
 
Use an additional parameter that is exclude=PROCACT_INSTANCE during impdp
 
- OR -
 
Redo the export with exclude=PROCACT_INSTANCE and perform import using new dumpfiles.
 
The use of the exclude=PROCACT_SYSTEM will exclude the resource manager objects such as resource plans and groups.
That means that if you had resource plans and groups, you will need to recreate them after the import.

  

posted @   阿西吧li  阅读(756)  评论(0编辑  收藏  举报
编辑推荐:
· 开发者必知的日志记录最佳实践
· SQL Server 2025 AI相关能力初探
· Linux系列:如何用 C#调用 C方法造成内存泄露
· AI与.NET技术实操系列(二):开始使用ML.NET
· 记一次.NET内存居高不下排查解决与启示
阅读排行:
· 开源Multi-agent AI智能体框架aevatar.ai,欢迎大家贡献代码
· Manus重磅发布:全球首款通用AI代理技术深度解析与实战指南
· 被坑几百块钱后,我竟然真的恢复了删除的微信聊天记录!
· 没有Manus邀请码?试试免邀请码的MGX或者开源的OpenManus吧
· 园子的第一款AI主题卫衣上架——"HELLO! HOW CAN I ASSIST YOU TODAY
点击右上角即可分享
微信分享提示