RENAMEcommand, though it can capture it and you can catch it in a DDL handler. But, do you know why?
The answer to that question actually stands in the 2 commands below:
alter session set current_schema=scott;For some obscure reasons
rename emp to emp2;
ERROR at line 1:
ORA-03001: unimplemented feature
RENAMEcannot be used after
current_schemahas been changed. Unfortunately the apply process changes the current schema to apply DDL so that it can be executed, even if the schema impacted by the DDL command is not in the source command. So, rename does not work. Obviously you can write a DDL handler and parse the command to manage that manually. But if you think that's easy, ask yourself why the Streams development team did not to that themselves to provide the feature out-of-the-box... Then run:
create table "alter table rename"(col1 number);There is a few remaining mystery, though: If
/* alter table rename */ rename "alter table rename" to "rename";
ALTER TABLE ... RENAME TO ...doesn't suffer those limits, why do DBA and developers execute
RENAMEto rename a table? Will that change in 11g Release 2?