| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Usenet -> c.d.o.server -> Re: Workspace Manager Question
DA Morgan wrote:
> wrgptfan wrote:
> > DA Morgan wrote:
> >> 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
> >
> > Doh! I was doing the test on my Windows laptop version instead of the
> > Unix version. Sorry about that. Here is the actual output:
> >
> > permit_at_devdb> @conn permit_at_devdb
> > Enter password: ******
> > Connected.
> >
> > Session altered.
> >
> > 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.5.0 - 64bit Production
> > PL/SQL Release 9.2.0.5.0 - Production
> > CORE 9.2.0.6.0 Production
> > TNS for HPUX: Version 9.2.0.5.0 - Production
> > NLSRTL Version 9.2.0.5.0 - Production
> >
> > permit_at_devdb>
>
>
> >
>
>
>
>
>
>
>
>
>
>> WCP_ISSUING_LOCATION_CODE_PKDC VIEW
> OBJECT_NAME OBJECT_TYPE
> ------------------------------ -------------------
> WCP_ISSUING_LOCATION_CODE VIEW
> WCP_ISSUING_LOCATION_CODE_AP1$ INDEX
> WCP_ISSUING_LOCATION_CODE_AP2$ INDEX
> WCP_ISSUING_LOCATION_CODE_AUX TABLE
> WCP_ISSUING_LOCATION_CODE_BASE VIEW
> WCP_ISSUING_LOCATION_CODE_BPKC VIEW
> WCP_ISSUING_LOCATION_CODE_CONF VIEW
> WCP_ISSUING_LOCATION_CODE_CONS VIEW
> WCP_ISSUING_LOCATION_CODE_DIFF VIEW
> WCP_ISSUING_LOCATION_CODE_HIST VIEW
> WCP_ISSUING_LOCATION_CODE_LOCK VIEW
> WCP_ISSUING_LOCATION_CODE_LT TABLE
> WCP_ISSUING_LOCATION_CODE_LTS TABLE
> WCP_ISSUING_LOCATION_CODE_MW VIEW
> WCP_ISSUING_LOCATION_CODE_PKC VIEW
> WCP_ISSUING_LOCATION_CODE_PKD VIEW
> WCP_ISSUING_LOCATION_CODE_PKDB VIEW
>
Things went from bad to worse! By the way, thanks for the help Daniel and Sybrand.
...Dave Kent
permit_at_devdb> select * from v$version;
BANNER
permit_at_devdb> create table XXX_ISSUING_LOCATION_CODE 2 (testcol VARCHAR2(5));
Table created.
permit_at_devdb>
permit_at_devdb> alter table XXX_ISSUING_LOCATION_CODE
2 add constraint pk_test
3 primary key (testcol);
Table altered.
permit_at_devdb>
permit_at_devdb> exec
dbms_wm.enableversioning('XXX_ISSUING_LOCATION_CODE',
'VIEW_WO_OVERWRITE')
PL/SQL procedure successfully completed.
permit_at_devdb>
permit_at_devdb> exec dbms_wm.BeginDDL('XXX_ISSUING_LOCATION_CODE')
BEGIN dbms_wm.BeginDDL('XXX_ISSUING_LOCATION_CODE'); END;
*
ERROR at line 1:
ORA-01422: exact fetch returns more than requested number of rows ORA-06512: at "SYS.OWM_DDL_PKG", line 1878 ORA-06512: at "SYS.LT", line 10257 ORA-06512: at line 1 permit_at_devdb>
OBJECT_NAME OBJECT_TYPE ------------------------------ ------------------ AUX_XXX_ISSUING_LOCATION_CODE INDEX XXX_ISSUING_LOCATION_CODE VIEW XXX_ISSUING_LOCATION_CODE_AP1$ INDEX XXX_ISSUING_LOCATION_CODE_AP2$ INDEX XXX_ISSUING_LOCATION_CODE_AUX TABLE XXX_ISSUING_LOCATION_CODE_BASE VIEW XXX_ISSUING_LOCATION_CODE_BPKC VIEW XXX_ISSUING_LOCATION_CODE_CONF VIEW XXX_ISSUING_LOCATION_CODE_DIFF VIEW XXX_ISSUING_LOCATION_CODE_HIST VIEW XXX_ISSUING_LOCATION_CODE_LOCK VIEW XXX_ISSUING_LOCATION_CODE_LT TABLE XXX_ISSUING_LOCATION_CODE_MW VIEW XXX_ISSUING_LOCATION_CODE_PKC VIEW XXX_ISSUING_LOCATION_CODE_PKD VIEW XXX_ISSUING_LOCATION_CODE_PKDB VIEW
permit_at_devdb>
permit_at_devdb> exec
dbms_wm.DisableVersioning('XXX_ISSUING_LOCATION_CODE')
PL/SQL procedure successfully completed.
permit_at_devdb>
permit_at_devdb> drop table XXX_ISSUING_LOCATION_CODE;
Table dropped.
permit_at_devdb> Received on Tue Aug 01 2006 - 15:36:01 CDT
 |
 |