Export tables with lowercase names

Has anyone ever done a table export on a table with a lower case name?
I have set up a parameter file with the entry:
tables=USER."table_name"
but I get a:
EXP-00011: USER."table_name" does not exist
The table DOES exist, and if I ever find the person who designed an entire schema with lower case table names I'll strangle him...
The syntax, with the double quotes, is what's shown in the Docs I have to hand.
Anyone?

Yes, so have I. But they still translate to uppercase when the export actually happens.
I actually have a schema full of tables, all with lowercase names, and I can't export them explicitly.
I have tried it with 8.1.5 and 8.1.6 (Solaris).
I'll try it with 9i and 8.0.6 when I get the instances up, but I'd really like it if someone else could try this and tell me I'm hallucinating. (I'd like to see your parameter syntax too of course!)
BTW, if you do try experimenting with lowercase table names, be prepared for things like TOAD and some of the OEM software to screw up too.

Similar Messages

How to import a table with renamed name

If I want to import a table from a DMP on UNIX towards my user where I already have a new version but I don't want to drop this new version 'cause I have only to move some records from one to the other, is there an import option for importing the table with another name? I mean I want to import on the same user, where there already exists the table MYTABLE, an old version of MYTABLE by impoting it with the new name MYTABLE_OLD, so afterwards I can update MYTABLE with some of old records of its old versione MYTABLE_OLD. Is it possible?

You cannot directly do this.
You can import the Table into a different schema and then rename the table.
export and import back into the required schema.
Import DataPump: How to Import Table Data into a Table that has Different Name ? [ID 342314.1]
Regards
Rajesh

Exporting Table with CLOB Columns

Hello All,
I am trying to export table with clob columns with no luck. It errors saying EXP-00011TABLE do not exist.
I can query the table and the owner is same as what i am exporting it from.
Please let me know.

An 8.0.6 client definitely changes things. Other posters have already posted links to information on what versions of exp and imp can be used to move data between versions.
I will just add that if you were using a client to do the export then if the client version is less than the target database version you can upgrade the client or better yet if possilbe use the target database export utility to perform the export.
I will not criticize the existance of an 8.0.6 system as we had a parent company dump a brand new 8.0.3 application on us less than two years ago. We have since been allowed to update the database and pro*c modules to 9.2.0.6.
If the target database is really 8.0.3 then I suggest you consider using dbms_metadata to generate the DDL, if needed, and SQLPlus to extact the data into delimited files that you can then reload via sqlldr. This would allow you to move the data with some potential adjustments for any 10g only features in the code.
HTH -- Mark D Powell --

Migrating from Sql Server tables with column name starting with integer

hi,
i'm trying to migrate a database from sqlserver but there are a lot of tables with column names starting with integer ex: *8420_SubsStatusPolicy*
i want to make an offline migration so when i create the scripts these column are created with the same name.
can we create rules, so when a column like this is going to be migrated, to append a character in front of it?
when i use Copy to Oracle option it renames it by default to A8420_SubsStatusPolicy
Edited by: user8999602 on Apr 20, 2012 1:05 PM

Hi,
Oracle doesn't allow object names to start with an integer. I'll check to see what happens during a migration about changing names as I haven't come across this before.
Regards,
Mike

Export table with LOB column

Hi!
I have to export table with lob column (3 GB is the size of lob segment) and then drop that lob column from table. Table has about 350k rows.
(I was thinking) - I have to:
1. create new tablespace
2. create copy of my table with CTAS in new tablespace
3. alter new table to be NOLOGGING
4. insert all rows from original table with APPEND hint
5. export copy of table using transport tablespace feature
6. drop newly created tablespace
7. drop lob column and rebuild original table
DB is Oracle 9.2.0.6.0.
UNDO tablespace limited on 2GB with retention 10800 secs.
When I tried to insert rows to new table with /*+append*/ hint operation was very very slow so I canceled it.
How much time should I expect for this operation to complete?
Is my UNDO sufficient enough to avoid snapshot too old?
What do you think?
Thanks for your answers!
Regards,
Marko Sutic

I've seen that document before I posted this question.
Still I don't know what should I do. Look at this document - Doc ID: 281461.1
From that document:
FIX
Although the performance of the export cannot be improved directly, possible
alternative solutions are:
+1. If not required, do not use LOB columns.+
or:
+2. Use Transport Tablespace export instead of full/user/table level export.+
or:
+3. Upgrade to Oracle10g and use Export DataPump and Import DataPump.+
I just have to speed up CTAS little more somehow (maybe using parallel processing).
Anyway thanks for suggestion.
Regards,
Marko

[Function] Declare a internal table with structure name (entry parameter)

Hi all,
I'm explaining my problem :
I want to create a function with two parameters in entry :
(IMPORT) - structure_name with type DD02L-TABNAME
(TABLES) - t_outtab with empty type
t_outtab will be in structure_name type.
Now, in my source function, I want to retrieve all contain of t_outtab in another internal table or field-symbol. I don't know in advance the used structures in my function entries.
I don't manage to get this contain, cause I can't do :
DATA : internal_table TYPE structure_name*
OR
DATA : internal_table TYPE (structure_name)
OR used field-symbol
DATA : internal_table TYPE <fs>* where <fs> had structure name value.
To do more later :
*DATA : line LIKE LINE OF internal_table. *
*internal_table][ = t_outtab][. *
And work with this table.
_ I tried different solutions like : _
Get the structure of the table.
ref_table_des ?= cl_abap_typedescr=>describe_by_name( I_STRUCTURE_NAME ).
idetails[] = ref_table_des->components[].
Get the first structure table of result table
LOOP AT idetails INTO xdetails.
    CLEAR: xfc.
    xfc-fieldname = xdetails-name .
    xfc-datatype = xdetails-type_kind.
    xfc-inttype = xdetails-type_kind.
    xfc-intlen = xdetails-length.
    xfc-decimals = xdetails-decimals.
    APPEND xfc TO ifc.
ENDLOOP.
Create dynamic internal table and assign to FS
CALL METHOD cl_alv_table_create=>create_dynamic_table
    EXPORTING
      it_fieldcatalog = ifc
    IMPORTING
      ep_table        = dy_table.
ASSIGN dy_table->* TO <dyn_table>.
Create dynamic work area and assign to FS
CREATE DATA dy_line LIKE LINE OF <dyn_table>.
ASSIGN dy_line->* TO <dyn_wa>.
and retrieve to <dyn_table>[] = t_outtab[].
the but I don't try the solution. If someone have an idea.
Thanks and regards.
Romain
Edited by: Romain L on May 14, 2009 11:35 AM

Hi,
We can acheive this using dynamic internal tables.
Please find sample below.
*Creating Dynamic internal table
PARAMETERS : p_table(10) TYPE C.
DATA: w_tabname TYPE w_tabname,
        w_dref TYPE REF TO data,
        w_grid TYPE REF TO cl_gui_alv_grid.
FIELD-SYMBOLS: <t_itab> TYPE ANY TABLE.
w_tabname = p_table.
CREATE DATA w_dref TYPE TABLE OF (w_tabname).
ASSIGN w_dref->* TO <t_itab>.
* Populating Dynamic internal table
SELECT *
    FROM (w_tabname) UP TO 20 ROWS
    INTO TABLE <t_itab>.
* Displaying dynamic internal table using Grid.
CREATE OBJECT w_grid
    EXPORTING i_parent = cl_gui_container=>screen0.
CALL METHOD w_grid->set_table_for_first_display
    EXPORTING
      i_structure_name = w_tabname
    CHANGING
      it_outtab        = <t_itab>.
CALL SCREEN 100.
* Scenario 2:
*Create a dynamic internal table with the specified number of columns.
* Creating Dynamic internal table
TYPE-POOLS: slis.
FIELD-SYMBOLS: <t_dyntable> TYPE STANDARD TABLE, u201C Dynamic internal table name
               <fs_dyntable>,                     u201C Field symbol to create work area
               <fs_fldval> type any.              u201C Field symbol to assign values
PARAMETERS: p_cols(5) TYPE c.                     u201C Input number of columns
DATA:   t_newtable TYPE REF TO data,
        t_newline TYPE REF TO data,
        t_fldcat   TYPE slis_t_fldcat_alv,
        t_fldcat   TYPE lvc_t_fcat,
        wa_it_fldcat TYPE lvc_s_fcat,
        wa_colno(2) TYPE n,
        wa_flname(5) TYPE c.
* Create fields .
DO p_cols TIMES.
    CLEAR wa_it_fldcat.
    move sy-index to wa_colno.
    concatenate 'COL'
                wa_colno
           into wa_flname.
    wa_it_fldcat-fieldname = wa_flname.
    wa_it_fldcat-datatype = 'CHAR'.
    wa_it_fldcat-intlen = 10.
    APPEND wa_it_fldcat TO t_fldcat.
ENDDO.
* Create dynamic internal table and assign to FS
CALL METHOD cl_alv_table_create=>create_dynamic_table
    EXPORTING
      it_fieldcatalog = t_fldcat
    IMPORTING
      ep_table        = t_newtable.
ASSIGN t_newtable->* TO <t_dyntable>.
* Create dynamic work area and assign to FS
CREATE DATA t_newline LIKE LINE OF <t_dyntable>.
ASSIGN t_newline->* TO <fs_dyntable>.
*Populating Dynamic internal table
DATA: fieldname(20) TYPE c.
DATA: fieldvalue(10) TYPE c.
DATA: index(3) TYPE c.
DO p_cols TIMES.
    index = sy-index.
    MOVE sy-index TO wa_colno.
    CONCATENATE 'COL'
                wa_colno
           INTO wa_flname.
* Set up fieldvalue
    CONCATENATE 'VALUE' index INTO
                fieldvalue.
    CONDENSE    fieldvalue NO-GAPS.
    ASSIGN COMPONENT wa_flname
        OF STRUCTURE <fs_dyntable> TO <fs_fldval>.
    <fs_fldval> = fieldvalue.
ENDDO.
* Append to the dynamic internal table
APPEND <fs_dyntable> TO <t_dyntable>.
* Displaying dynamic internal table using Grid.
DATA: wa_cat LIKE LINE OF fs_fldcat.
DO p_cols TIMES.
    CLEAR wa_cat.
    MOVE sy-index TO wa_colno.
    CONCATENATE 'COL'
                wa_colno
           INTO wa_flname.
    wa_cat-fieldname = wa_flname.
    wa_cat-seltext_s = wa_flname.
    wa_cat-outputlen = '10'.
    APPEND wa_cat TO fs_fldcat.
ENDDO.
* Call ABAP List Viewer (ALV)
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
    EXPORTING
      it_fieldcat = fs_fldcat
    TABLES
      t_outtab    = <t_dyntable>.
Thanks,
Jyothi
Edited by: Jyothi on May 14, 2009 11:42 AM
Edited by: Jyothi on May 14, 2009 11:43 AM

InDesign CS6 ePub Export : Tables with header and footer in HTML

Hey there,
does anyone know, whether InDesign CS6 also exports Table Headers and footers correctly into the XHTML-File of the ePub.
What I mean, is whether the elements <thead> and <tfoot> are created?
Or is it only possible to steer this via the CSS-Classnames which can be given in the tableformats?
Generally I think it would be better if the user had the chance to map other exporttags to its elements than just p, em, strong, h1-h6.
it would be useful to also put in other elements by hand.
Best regrads.

Magnolee2 wrote:
does anyone know, whether InDesign CS6 also exports Table Headers and footers correctly into the XHTML-File of the ePub.
What I mean, is whether the elements <thead> and <tfoot> are created?
By "also", do you mean the behavior is changed with respect to CS5/CS5.5? In those, thead and tfoot are created correctly. (Although, quite disconcerting, in the order "thead / tfoot / tbody". ePub renderers based on Webkit display them correctly nevertheless, but others do not. An extremely annoying free interpretation of the W3C rules.)

Funny bug in SQLDev 2.1EA - tables with same name...

Hi,
i opened two session in SQLDev 2.1EA, on two distinct instances.
These sessions are open against the same user and i am clicking on a table with the same name.
This happens only when the "pin" icon is not set.
Apparently SQLDev doesn't not distinguish between the two connections when it comes to display the object attributes like columns, data, indexes and so on.
So, practically, if i click on object 1 (instance 1), click on data tab, then i click on object 1 (instance 2), i still see the data for instance 1, no matter if i ask to refresh.
This doesn't happen if i open each object in a separate tab.
This happens on SQLDev on Mac OS X.
Flavio
http://oraclequirks.blogspot.com

Sorry to drop in, but I suppose many have this setup: the same users/connections on both development and production databases.
However I'm not able to reproduce now on my 10g DBs, I did see the same problem a couple of versions ago (when I was on 9i), but AFAIK that got fixed. Maybe regression anyway?
Regards,
K.

Import and Export variables with same name

The nco3 throws and exception when a function has Import and Export variables with the same name.
An example is BAPI_BATCH_CREATE.
At the moment my solution is create a ZBAPI_BATCH_CREATE that wraps the original BAPI but has diferent names for import and export variables (IBATCH and OBATCH for BATCH variable).
Anyone has another more clean solution?
VB.NET CODE:
pFunct = foRFCDest.Repository.CreateFunction(fsFunctionName)
This is the error message:
SAP.Middleware.Connector.RfcInvalidStateException was unhandled
Message=Lookup of function BAPI_BATCH_CREATE metadata failed for destination SAPTST
Source=sapnco
StackTrace:
       en SAP.Middleware.Connector.RfcRepository.LookupFunctionMetadataClassic(String name)
       en SAP.Middleware.Connector.RfcRepository.LookupFunctionMetadata(String name)
       en SAP.Middleware.Connector.RfcRepository.GetFunctionMetadata(String name)
       en SAP.Middleware.Connector.RfcRepository.CreateFunction(String name)
       en SapNetConnectorWrapper.FunctionBase..ctor(RfcDestination foDest, String fsFunctionName) en C:00_Compac201101_LibreriasSapNetConnectorWrapperFunctionBase.vb:línea 11
       en SapNetConnectorWrapper.BAPIS.Bapi_Batch_Create..ctor(RfcDestination foDest) en C:00_Compac201101_LibreriasSapNetConnectorWrapperBAPISBapi_Batch_Create.vb:línea 16
       en clsEtiquetadoTNPCommon.BLLEtiquetadoTNP.CrearLote(DynamicSqlEntity& foRegCabecera, DynamicSqlEntity& foRegNotificacion) en C:00_Compac201100_EtiquetadoTNP_PTEtiquetadoTNP_PTclsEtiquetadoTNPCommonBLLEtiquetadoTNP.vb:línea 515
       en clsEtiquetadoTNPCommon.BLLEtiquetadoTNP.CrearLotesPendientes() en C:00_Compac201100_EtiquetadoTNP_PTEtiquetadoTNP_PTclsEtiquetadoTNPCommonBLLEtiquetadoTNP.vb:línea 602
       en WAEtiquetadoTNP.Form1.Timer1_Tick(Object sender, EventArgs e) en C:00_Compac201100_EtiquetadoTNP_PTEtiquetadoTNP_PTWAEtiquetadoTNPForm1.vb:línea 25
       en System.Windows.Forms.Timer.OnTick(EventArgs e)
       en System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
       en System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
       en System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
       en System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
       en System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
       en System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
       en System.Windows.Forms.Application.Run(ApplicationContext context)
       en Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun()
       en Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel()
       en Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run(String[] commandLine)
       en WAEtiquetadoTNP.My.MyApplication.Main(String[] Args) en 17d14f5c-a337-4978-8281-53493378c1071.vb:línea 81
       en System.AppDomain._nExecuteAssembly(Assembly assembly, String[] args)
       en System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence assemblySecurity, String[] args)
       en Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()
       en System.Threading.ThreadHelper.ThreadStart_Context(Object state)
       en System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       en System.Threading.ThreadHelper.ThreadStart()
InnerException: SAP.Middleware.Connector.RfcInvalidParameterException
       Message=Cannot add BATCH to FUNCTION BAPI_BATCH_CREATE: an element with that name already exists
Source=sapnco
       StackTrace:
            en SAP.Middleware.Connector.RfcContainerMetadata`1.AddElement(T element)
            en SAP.Middleware.Connector.RfcFunctionMetadata.AddParameter(RfcParameterMetadata parameterMetadata)
            en SAP.Middleware.Connector.RfcRepository.LookupFunctionMetadataClassic(String name)
       InnerException:

Hi Raul
Even I am getting the same error for below BAPI
Lookup of function BAPI_FAMILY_CREATE metadata failed for destination
Inner Exception: Message     "Cannot add EMPLOYEENUMBER to FUNCTION BAPI_FAMILY_CREATE: an element with that name already exists"     string
I am using the new NCO 3.0.2.0 x64 version.
Is there any other solution other than creation of Z BAPI.

AMDP exporting table with fields from various sources

I am writing an AMDP that has an output table a list of employees and attributes. These attributes have various sources with various keys. If I cannot with any practicality construct this table with a single select statement, which given my search criteria, I probably can't, must I break my output table into multiple output tables that can be created with a single select?
I declare the structure of output table et_employees in the class as something like
      BEGIN OF ty_employee,
        emp_id(12)    TYPE c,
        emp_name(80) TYPE c,
        org_unit(8)   TYPE c,
        region(5)     TYPE c,
        country(3)    TYPE c,
        jb_prf_as     TYPE c,
        sol_gr_as     TYPE c,
        snippet(1000) TYPE c,
        score         TYPE integer,
      END OF ty_employee,
      tt_employes type table of ty_employee.
As far as I can tell, I cannot do an update et_employees in the method to modify individual fields. I can only do the select statement.
I see my choices as
elaborate select statement that I may or may not be able to construct (haven't thought this through but it may be doable)
more than one output table
create multiple local tables and then do a join on them for the output table.
I am seeing the last one as my best option.
To throw in an unrelated issue, AMDP procedure cannot seem to cope with a table that begins with a slash, e.g., /MRSS/D_SQP_ESTR. The USING statement is o.k. but any access in a select or inner join gets an error.

Hi Deborah,
let me do some assumptions on your problem and then try to help you:
Assumption A: You only like to query data from tables, which, I simply assume, are available in the ABAP data dictionary. In this case, I don't think there is a performance gain with AMDPs compared to OpenSQL, so just use OpenSQL and do joins on the relevant tables, leading to exaclty one resultset in the output.
Assumption B: You need the AMDP because you have a good reason and you like to query data from tables employee_source_a and employee_source_b for your resultset. In case yes, you can e.g. use "temporary" tables (don't declare them explicitly), e.g. use the construct like:
lt_employee_source_a = select ...from employee_source_a ...;
lt_employee_source_b = select ... from employee _source_b...;
et_employee = select ... from :lt_employee_source_a ... (inner/left outer) join lt_employee_source_b on...;
Or you could use the CE_JOIN function if that suits your SQLScript development better.
To elaborate a query statement for et_employee for without the lt_xxx tables is hard to say from your question - it should be posible if there are no nasty aggregations/calculations which prevent it :-).
There's no need to use two resultsets in the output in case that's not what you need in the application.
The option to have several resultsets is rather a feature of DB Procedures, which allow for several resultsets while a view/OpenSQL query can only give you one resultset.
Conclusion: You answered your question yourself, the last option seems to be the best option :-).
Concerning the "slash issue": Guessing around I'd propose to use quote the table name like "/MRSS/D_SQP_ESTR"... but just a guess. Could you please post the error message or open a second discussion on the issue?
Cheers,
Jasmin

Concatenate tables with same name from different servers - CR2013

Hello,
I need some help. I need data from 2 tables with the same name on different SQL servers thru an ODBC connection. When I try to get the data by adding both to my datasource I get data from one or the other. I have considered creating a view, but not sure how to handle this. Thanks.

Hi,
Linked Servers are pretty simple and straightforward, just do a search for the procedure.
I do have an additional comment, though. Depending on what tables you're gathering, I've found noticeable differences in performance when I use a connector to a DB on Server Instance "A" linked to "B" versus Server Instance B linked to A. I haven't determined the circumstances affecting one over the other.
If I'm not happy with speed using a connector A, I try switching to B. I like to use as much SQL code as possible, but you can't get around the connector still being a factor.
Matt

EA3 export table with SDO types

Hi!
I've tried export table from user (not mdsys) with mdsys.sdo_geometry column (build 1.5.0.53.04, tools export wizard, all checks except storage).
got in log:
SEVERE 40 0 oracle.dbtools.db.DBUtil
ORA-31603: объект "SDO_ELEM_INFO_ARRAY" с типом TYPE не найден в схеме "MDSYS" ORA-06512: на "SYS.DBMS_SYS_ERROR", line 105 ORA-06512: на "SYS.DBMS_METADATA", line 2805 ORA-06512: на "SYS.DBMS_METADATA", line 4333 ORA-06512: на line 1
SEVERE 41 641 oracle.dbtools.db.DBUtil ORA-31603: объект "SDO_GEOMETRY" с типом TYPE не найден в схеме "MDSYS" ORA-06512: на "SYS.DBMS_SYS_ERROR", line 105 ORA-06512: на "SYS.DBMS_METADATA", line 2805 ORA-06512: на "SYS.DBMS_METADATA", line 4333 ORA-06512: на line 1
SEVERE 42 94 oracle.dbtools.db.DBUtil ORA-31603: объект "SDO_ORDINATE_ARRAY" с типом TYPE не найден в схеме "MDSYS" ORA-06512: на "SYS.DBMS_SYS_ERROR", line 105 ORA-06512: на "SYS.DBMS_METADATA", line 2805 ORA-06512: на "SYS.DBMS_METADATA", line 4333 ORA-06512: на line 1
SEVERE 43 3093 oracle.dbtools.raptor.ddl.DDLGenerator getDDL - null
In SQL script i've got some strange result (see bold):
-- File created - среда-Апрель-09-2008
DROP TABLE "TEST" cascade constraints;
DROP SEQUENCE "MDRS_C0A4$";
-- DDL for Sequence MDRS_C0A4$
CREATE SEQUENCE "MDRS_C0A4$" MINVALUE 1 MAXVALUE 999999999999999999999999999 INCREMENT BY 1 START WITH 101 CACHE 100 ORDER NOCYCLE ;
-- DDL for Type SDO_ELEM_INFO_ARRAY
-- Unable to Render DDL with DBMS_METADATA using internal generator.
CREATE TYPE SDO_ELEM_INFO_ARRAY
AS VARRAY (1048576) of NUMBER
GRANT EXECUTE ON "SDO_ELEM_INFO_ARRAY" TO PUBLIC WITH GRANT OPTION;
GRANT EXECUTE ON "SDO_ELEM_INFO_ARRAY" TO PUBLIC WITH GRANT OPTION;
-- DDL for Type SDO_GEOMETRY
-- Unable to Render DDL with DBMS_METADATA using internal generator.
CREATE TYPE MDSYS.SDO_GEOMETRY;
CREATE TYPE SDO_GEOMETRY AS OBJECT
( SDO_GTYPE NUMBER,
SDO_SRID NUMBER,
SDO_POINT SDO_POINT_TYPE,
SDO_ELEM_INFO SDO_ELEM_INFO_ARRAY,
SDO_ORDINATES SDO_ORDINATE_ARRAY,
MEMBER FUNCTION GET_GTYPE RETURN NUMBER DETERMINISTIC,
MEMBER FUNCTION GET_DIMS RETURN NUMBER DETERMINISTIC,
MEMBER FUNCTION GET_LRS_DIM RETURN NUMBER DETERMINISTIC,
MEMBER FUNCTION GET_WKB RETURN BLOB DETERMINISTIC,
MEMBER FUNCTION GET_WKT RETURN CLOB DETERMINISTIC,
MEMBER FUNCTION ST_CoordDim RETURN SMALLINT DETERMINISTIC,
MEMBER FUNCTION ST_IsValid RETURN INTEGER DETERMINISTIC,
CONSTRUCTOR FUNCTION SDO_GEOMETRY(wkt IN CLOB, asrid IN INTEGER DEFAULT NULL)
RETURN SELF AS RESULT,
CONSTRUCTOR FUNCTION SDO_GEOMETRY(wkt IN VARCHAR2, asrid IN INTEGER DEFAULT NULL)
RETURN SELF AS RESULT,
CONSTRUCTOR FUNCTION SDO_GEOMETRY(wkb IN BLOB, asrid IN INTEGER DEFAULT NULL)
RETURN SELF AS RESULT
GRANT EXECUTE ON "SDO_GEOMETRY" TO PUBLIC WITH GRANT OPTION;
GRANT EXECUTE ON "SDO_GEOMETRY" TO PUBLIC WITH GRANT OPTION;
-- DDL for Type SDO_ORDINATE_ARRAY
-- Unable to Render DDL with DBMS_METADATA using internal generator.
CREATE TYPE SDO_ORDINATE_ARRAY
AS VARRAY(1048576) OF NUMBER
GRANT EXECUTE ON "SDO_ORDINATE_ARRAY" TO PUBLIC WITH GRANT OPTION;
GRANT EXECUTE ON "SDO_ORDINATE_ARRAY" TO PUBLIC WITH GRANT OPTION;
-- DDL for Table TEST
CREATE TABLE "TEST"
( "NUM" NUMBER,
"GEOLOC" "SDO_GEOMETRY"
-- Constraints for Table TEST
ALTER TABLE "TEST" MODIFY ("NUM" NOT NULL ENABLE);
ALTER TABLE "TEST" ADD PRIMARY KEY ("NUM") ENABLE;
-- DDL for Index TEST_SX
CREATE INDEX "TEST_SX" ON "TEST" ("GEOLOC")
INDEXTYPE IS "MDSYS"."SPATIAL_INDEX" PARAMETERS ('SDO_INDX_DIMS=2 LAYER_GTYPE="COLLECTION"');
-- DDL for Index SYS_C004552
CREATE UNIQUE INDEX "SYS_C004552" ON "TEST" ("NUM")
Why it create all grant twice?
Why it try to recreate type SDO_GEOMETRY twice - once in MDSYS schema second in users schema?
Why it recreate types SDO_ELEM_INFO_ARRAY and SDO_ORDINATE_ARRAY only once in user schema?

Why it create all grant twice?
Why it try to recreate type SDO_GEOMETRY twice - once in MDSYS schema second in users schema?
Why it recreate types SDO_ELEM_INFO_ARRAY and SDO_ORDINATE_ARRAY only once in user schema?
All of these seem to be an issue with the older internal ddl generator. While I will log a bug on this we do not actually own the code so I am not able to fix it. The easiest way to make this work correctly would be to fix your DBMS_METADATA to work for those other user objects...
Try granting your export user SELECT_CATALOG_ROLE.
Although I'm not sure why you are including the dependencies for that table as you know it's going to just get you the MDSYS objects, try unchecking the "Automatically Include Dependent Objects" option on the first page of wizzard.

EXP 11.2.0.1 export tables with at leat 1 row

I have oracle db 11.2.0.1 and user the export utility to export
tables, and row dati from the database to a file dmp.
I have notice that mow it extract the table with at leat 1 row
and do not export table empty
and so when i execute an import i lost a lot of tables...
Very dangerous ....
There is and explanations ???

You may get this effect in release 11.2.0.1 if the table has no segment. You probably have deferred_segment_creation=true. This query may help identify the tables without segments:
select table_name from user_tables
minus
select segment_name from user_segments where segment_type='TABLE';
(you will of course have to modify the query to handle more complex table structures).
Data Pump does not have this problem.
John Watson
Oracle Certified Master DBA

Problem Export tables with data pump

Hi,
I want to export a 300 tables with datapump. But a received this message:
ORA-39001: invalid argument value
ORA-39071: Value for TABLES is badly formed.
when i put only half of the tables i have neither any problem and it works ..
anyone know this problem, i need to put all this tables to export?
Thanks in advance.

the file (*.dat) semble of this:
DIRECTORY=PUMPDIR
DUMPFILE=MyFile.dmp
LOGFILE=MylogFile.log
TABLES= User.Mytbale:partition1_0
User.Mytbale:partition1_1
User.Mytbale:partition1_2
User.Mytbale:partition1_3
OtherUser.Table:partition1_1
in order 300 tables

Iphoto exporting images with no name and mail with no reply info

One of our Macbook pros, running osx 10.8.5, is sending email via iphoto that ,
#1) creates a photo with NO NAME that cannot be saved no matter what you do,
and
#2) the email can not be forwarded, seems like because there is not "reply to" information.
the Prefs are filled out correctly in the iPhoto email settings.
Why did they configure iphoto to do the "send" FROM iphoto in this OSX version? This worked fine before as it would open up your mail whereby you could arrange and double check things.
So i was trying to do a work around by sending the email to myself but the email and the attachment can not be forwarded. As well the image CAN NOT be dragged to the desktop to be saved. USELESS!
just a Ghost email and attachment.
very frustrating.

InDesign has a feature that will automatically search for other missing links when you fix a missing link. When you relinked the first of your grayscale images, you may have accidentally relinked to the saturated image. When this happened it searched the directory that the newly re-linked file was in for all the other missing files. Since your image names all matched up to images in that directory, they all got re-linked.
This auto-relink feature can be toggled in the relink dialog:
If you have a backup of your file, you can revert to that version, and try to relink your images from that one. In the future you should make sure that images all have unique identifiers, it is bad practice to have images with identical names.

Export tables with lowercase names

Similar Messages

Maybe you are looking for