Re: Workspace Manager Question

wrgptfan wrote:
> I have a schema of about 200 version enabled tables. What I would like
> to do is to modify one of the tables using DBMS_WM.BEGINDDL, however
> the table name is 25 characters in length. Although the documentation
> states that a table name cannot exceed 25 characters (because of adding
> _HIST and the like) it seems as if the limit is fewer than 25 if you
> ever would like to alter the table.
>
> Am I doing something wrong or is there a workaround to my problem.
>
> TIA...Dave Kent
>
>
>
> permit_at_devdb> create table WCP_ISSUING_LOCATION_CODE (pk number(5));
>
> Table created.
>
> permit_at_devdb> alter table WCP_ISSUING_LOCATION_CODE add constraint
> WCP_ISSUING_LOCATION_CODE_pk
> 2 primary key(pk);
>
> Table altered.
>
> permit_at_devdb> exec
> dbms_wm.enableversioning('WCP_ISSUING_LOCATION_CODE');
>
> PL/SQL procedure successfully completed.
>
> permit_at_devdb> exec dbms_wm.beginddl('WCP_ISSUING_LOCATION_CODE')
> BEGIN dbms_wm.beginddl('WCP_ISSUING_LOCATION_CODE'); END;
>
> *
> ERROR at line 1:
> ORA-00972: identifier is too long
> ORA-06512: at "SYS.OWM_DDL_PKG", line 1878
> ORA-06512: at "SYS.LT", line 10257
> ORA-06512: at line 1
>
>
> permit_at_devdb> select * from v$version;
>
> BANNER
> ----------------------------------------------------------------
> Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
> PL/SQL Release 9.2.0.1.0 - Production
> CORE 9.2.0.1.0 Production
> TNS for 32-bit Windows: Version 9.2.0.1.0 - Production
> NLSRTL Version 9.2.0.1.0 - Production
>
> permit_at_devdb>

The first thing that jumps out to me is 9.2.0.1.0. Why?

Oracle will say it to you so I'll save you the trip to metalink. Apply patches.

-- 
Daniel A. Morgan
University of Washington
damorgan_at_x.washington.edu
(replace x with u to respond)
Puget Sound Oracle Users Group
www.psoug.org