This content has been marked as final. Show 3 replies
What version of Workspace Manager are you using? Also, if possible, execute the following alter session prior to the dbms_wm.MergeTable command and post the call stack from the resulting trace file.
SQL> alter session set events '20171 trace name errorstack level 1, forever';
We are using version 10.2.0.4.3 of OWM.
The call stack you asked for:
----- PL/SQL Call Stack -----
object line object
handle number name
0x1c37310b8 342 package body WMSYS.WM_ERROR
0x1c37310b8 359 package body WMSYS.WM_ERROR
0x1c37787d8 8643 package body WMSYS.LTUTIL
0x1c36e6ef8 17 package body WMSYS.OWM_ASSERT_PKG
0x1c450d8c8 5057 package body WMSYS.LTADM
0x1c450d8c8 6999 package body WMSYS.LTADM
0x1c450d8c8 7158 package body WMSYS.LTADM
0x1c450d8c8 9094 package body WMSYS.LTADM
0x1c48f5910 2743 package body WMSYS.LT
0x1c48f5910 2467 package body WMSYS.LT
0x1c48f5910 2409 package body WMSYS.LT
0x1c48f5910 7191 package body WMSYS.LT
0x1a9d70c70 7 anonymous block
----- Call Stack Trace -----
Any idea? Thanks.
Thanks for providing the stack. I was able to replicate that, but not the error itself. Do you get the error for all tables, or just this one? If just this table, does it depend on the where_clause being specified? What about when you do not use an anonymous block?