Exporting from Access to Oracle

Hi all,
nowadays we are dealing with an issue of exporting access tables to oracle 11g.Briefly, the problem is our former developers had defined columnnames with space characters in access tables,as you know they are not valid in oracle db.After spending hours on internet we found out that we can export tables to oracle with the same column names if we put a quotation mark (") just before and after the column name which means a column named [Customer Name] in access is gonna be changed to "Customer Name".It looks okey but still looks like an amateur ,daily solution.Dou you know any other solution for our problem and also is the putting quotation marks(") a supported solution for oracle's side.
Thank You
gokhan

Hi,
You can make use of Oracle sql Developer for exporting Access tables or database to Oracle. ORacle sql developer will capture the Access model and then convert it into the Oracle required format. Then using that model you can perform Import in the ORacle Sql Developer.
Regards

Similar Messages

  • Import/Export from Access MDB to Oracle DB

    Dear Friends,
    I need to import a huge table from access to Oracle. I tried to export the file from MS Access to Oracle, it is giving error. I tried another way of doing , i first exported the data to SQL server and then using Export/Import utility of SQL Server, it has imported succesfully. I am not sure which is the best way to import data from ACCESS to Oracle.
    Kindly suggest,
    Regards,
    Vinay

    Another approach you might try goes something like this:
    1. In Access, link the destination Oracle table (for example, via File, Get External Data, Link Tables...).
    2. In Access, create an Append Query to select rows from your Access table and insert them in to the linked Oracle table.

  • Migrating from Access to Oracle

    Hello......
    I am trying to migrate a table from Access to Oracle. It contains approx 850,000 rows, and I tried using SQL Server's DTS Import/Export tool to perform the migration. However, this export/import has been running for almost 48 hours (crazy, huh?!), and I'm only at 350,000 records loaded. This tool is obviously not sufficient for a migration of this size.
    Can anyone suggest a better way for me to go about this?
    Thanks,
    -Christine

    Hi,
    If you have DDL structures in Oracle, then you can save the access data as .csv file format. you using any opensource tool you can migrate it.
    Or you can go for sql loader also.
    Cheers,
    Moorthy.GS

  • Migration Error from Access to Oracle through SQL Developer.

    Hi,
    Actually I am trying to migrate data from MS Access 2002 to Oracle 9i database through the SQL Developer. But Whenever I go to Capture Database from Access it will show me an error.... Invalid procedure Call and then it shows an error message... >>>>>>
    ShowSplashScreen("_OracleSplashScreen",3)
    after that i wont be able to do this task anymore..... So please help me get out of it... How Cam I Maigrate data from Access to Oracle 9i...
    Is any other tool i use or you can help me for this tool to migrate date...
    Please tell me..
    If yu can send me a mail then mail me on [email protected]
    regards,
    Vishal

    Hi Vishal,
    I have responded to your related thread on the Migration Workbench forum - Migration Error from Access to Oracle through SQL Developer.
    Regards,
    Hilary

  • SQL from Access to Oracle

    Hi,
    I've been developing queries in Access, using pivot tables. Oracle SQL*Plus does not recognize either TRANSFORM or PIVOT keywords from Jet SQL.
    Can anyone help me find the necessary equivalents for SQL*Plus?
    Thanks,
    Joe

    Hi Meena,
    You mention that you have created the schema and tables in Oracle using DDL scripts. Did you use the Oracle SQL Developer Migration Workbench, creating a Migration Repository, to carry out this process? I see from your other postings that you are experiencing issues using the Exporter tool, which would lead me to believe that you haven't used the Migration Workbench to migrate your database. Obviously you will need to resolve your Exporter issues before you can proceed to the next phase of the migration process. I will aim to assist you with those issues on the seperate thread - ShowSplashScreen("_OracleSplashScreen",3) error The XML file generated by the Exporter tool forms the basis of your MS Access migration.
    In order to migrate your data from MS Access to Oracle using the Migrate Data option in Oracle SQL Developer, you will need to have access to the Migration Repository used for the migration of the MS Access database. The information contained in the Converted Model, in the Migration Repository, is used during the data migration process. The data migration requires the following connections:
    1. a source database connection i.e. a database connection to the MS Access MDB file
    2. a target database connection i.e. a database connection to the migration Oracle schema
    3. a Converted Model connection
    For further information on the creation of a Migration Repository, and the migration process, please refer to the accompanying documentation available via the online Help within Oracle SQL Developer, and also from OTN - http://download.oracle.com/docs/cd/E10405_01/doc/nav/portal_booklist.htm.
    I hope this helps.
    Regards,
    Hilary

  • Migration from Access to Oracle through SQL developer

    Hi,
    I want to migrate an mdb file which contains a set of tables to oracle. During this process, i have created schema and all the tables in Oracle using DDL scripts. I would like to transfer only the data to Oracle from access through SQL developer. How can I do that?
    Regards,
    Meena

    Hi Meena,
    You mention that you have created the schema and tables in Oracle using DDL scripts. Did you use the Oracle SQL Developer Migration Workbench, creating a Migration Repository, to carry out this process? I see from your other postings that you are experiencing issues using the Exporter tool, which would lead me to believe that you haven't used the Migration Workbench to migrate your database. Obviously you will need to resolve your Exporter issues before you can proceed to the next phase of the migration process. I will aim to assist you with those issues on the seperate thread - ShowSplashScreen("_OracleSplashScreen",3) error The XML file generated by the Exporter tool forms the basis of your MS Access migration.
    In order to migrate your data from MS Access to Oracle using the Migrate Data option in Oracle SQL Developer, you will need to have access to the Migration Repository used for the migration of the MS Access database. The information contained in the Converted Model, in the Migration Repository, is used during the data migration process. The data migration requires the following connections:
    1. a source database connection i.e. a database connection to the MS Access MDB file
    2. a target database connection i.e. a database connection to the migration Oracle schema
    3. a Converted Model connection
    For further information on the creation of a Migration Repository, and the migration process, please refer to the accompanying documentation available via the online Help within Oracle SQL Developer, and also from OTN - http://download.oracle.com/docs/cd/E10405_01/doc/nav/portal_booklist.htm.
    I hope this helps.
    Regards,
    Hilary

  • Error in Transformation from Access to Oracle

    I am getting following error while fetching data from Access in Load data.
    java.lang.ClassCastException: java.lang.Integer cannot be cast to [B
         at oracle.jdbc.driver.OraclePreparedStatement.setObjectCritical(OraclePreparedStatement.java:7839)
         at oracle.jdbc.driver.OraclePreparedStatement.setObjectInternal(OraclePreparedStatement.java:7555)
         at oracle.jdbc.driver.OraclePreparedStatement.setObject(OraclePreparedStatement.java:8028)
         at oracle.jdbc.driver.OraclePreparedStatementWrapper.setObject(OraclePreparedStatementWrapper.java:238)
         at com.sunopsis.sql.SnpsQuery.updateExecStatement(SnpsQuery.java:2027)
         at com.sunopsis.sql.SnpsQuery.addBatch(SnpsQuery.java:122)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.executeUpdate(SnpSessTaskSql.java:3034)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execCollOrders(SnpSessTaskSql.java:729)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt(SnpSessTaskSql.java:2815)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java:2515)
         at com.sunopsis.dwg.dbobj.SnpSessStep.treatAttachedTasks(SnpSessStep.java:534)
         at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java:449)
         at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:1954)
         at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$2.doAction(StartSessRequestProcessor.java:322)
         at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:224)
         at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.doProcessStartSessTask(StartSessRequestProcessor.java:246)
         at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.access$0(StartSessRequestProcessor.java:237)
         at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$StartSessTask.doExecute(StartSessRequestProcessor.java:794)
         at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:114)
         at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$2.run(DefaultAgentTaskExecutor.java:82)
         at java.lang.Thread.run(Thread.java:662)
    Unable to understand Error.
    What this error is about and whoat would i have to Do to remove it ?
    Details:-
    LKM:- SQL to Oracle (Only this is refered in this step)
    IKM:- IKM SQL Incremet Update .(It would not be refered in this step)
    Edited by: MaheshGx on Jan 9, 2012 6:24 PM

    Posting Code:-
    Source Code:-
    select     
         MTP_CONVERSION."MTP#"     as C9_MTP_,
         MTP_CONVERSION."MTP#"     as C14_MTP_,
         MTP_CONVERSION."MTP#"     as C37_MTP_,
         MTP_CONVERSION."MTP#"     as C38_MTP_,
         TABLE_BCAT_SALES."Budg_Cat_Sales"     as C2_BUDG_CAT_SALES,
         TABLE_PATTERN."Pattern"     as C7_PATTERN,
         TABLE_BCAT_SALES."Budg_Cat_Sales"     as C11_BUDG_CAT_SALES,
         TABLE_SIZE."Size_Designation"     as C24_SIZE_DESIGNATION,
         TABLE_INFL_TYPE."Infl_Type_Abr"     as C26_INFL_TYPE_ABR,
         WARRANTY."MTP_Warr"     as C27_MTP_WARR,
         TABLE_CUSTOMER."Customer"     as C30_CUSTOMER,
         MTP_CONVERSION."Year"     as C31_YEAR,
         VEHICLE."Vehicle"     as C34_VEHICLE,
         MTP_CONVERSION.IPC     as C6_IPC,
         MTP_CONVERSION.IPC     as C8_IPC,
         TABLE_BCAT_SALES."Budg_Group_Sales"     as C12_BUDG_GROUP_SALES,
         TABLE_BCAT."Brand"     as C25_BRAND,
         TABLE_LOAD_CAT.PR     as C29_PR,
         MTP_CONVERSION.IPC     as C36_IPC,
         MTP_CONVERSION.IPC     as C41_IPC,
         MTP_CONVERSION.BPC     as C5_BPC,
         TABLE_SIZE."Width"     as C18_WIDTH,
         TABLE_SIZE."Width"     as C19_WIDTH,
         TABLE_SIZE."Width"     as C32_WIDTH,
         MTP_CONVERSION."LineUp_Ind"     as C1_LINEUP_IND,
         TABLE_SIZE."Series"     as C16_SERIES,
         TABLE_SIZE."Series"     as C17_SERIES,
         TABLE_CUSTOMER.OE     as C23_OE,
         TABLE_SIZE."Series"     as C33_SERIES,
         MTP_LINEUP."Load_Single"     as C13_LOAD_SINGLE,
         TABLE_SIZE."Rim"     as C28_RIM,
         MTP_CONVERSION."Product_Description"     as C10_PRODUCT_DESCRIPTION,
         MTP_LINEUP."Load_Dual"     as C15_LOAD_DUAL,
         MTP_CONVERSION."Product_Description"     as C20_PRODUCT_DESCRIPTION,
         MTP_LINEUP."Speed"     as C3_SPEED,
         TABLE_PATTERN."Winter"     as C21_WINTER
    from     ."MTP_Conversion" as MTP_CONVERSION, ."MTP_LineUp" as MTP_LINEUP, ."Vehicle" as VEHICLE, ."Warranty" as WARRANTY, ."Table_Pattern" as TABLE_PATTERN, ."Table_BCAT_Sales" as TABLE_BCAT_SALES, ."Table_Customer" as TABLE_CUSTOMER, ."Table_BCAT" as TABLE_BCAT, ."Table_Size" as TABLE_SIZE, ."Table_Infl_Type" as TABLE_INFL_TYPE, ."Table_Load_Cat" as TABLE_LOAD_CAT
    where     (1=1)
    And (MTP_LINEUP."Infl_Type_Code"=TABLE_INFL_TYPE."Infl_Type_Code")
    AND (MTP_LINEUP."Customer_Code"=TABLE_CUSTOMER."Customer_Code")
    AND (MTP_LINEUP."BCATS_Code"=TABLE_BCAT_SALES."BCATS_code")
    AND (MTP_CONVERSION."MTP#"=WARRANTY."MTP#")
    AND (MTP_LINEUP."Pattern_Code"=TABLE_PATTERN."Pattern_Code")
    AND (MTP_LINEUP."Load_Cat_Code"=TABLE_LOAD_CAT."Load_Cat_Code")
    AND (MTP_LINEUP."BCAT_Code"=TABLE_BCAT."BCAT_code")
    AND (MTP_CONVERSION."MTP#"=MTP_LINEUP."MTP#")
    AND (MTP_CONVERSION."MTP#"=VEHICLE."MTP#")
    AND (MTP_LINEUP."Size_Code"=TABLE_SIZE."Size_Code")
    Target Code:-
    insert into OMPODI.C$_0NEWBSMASTERTYRE
         C9_MTP_,
         C14_MTP_,
         C37_MTP_,
         C38_MTP_,
         C2_BUDG_CAT_SALES,
         C7_PATTERN,
         C11_BUDG_CAT_SALES,
         C24_SIZE_DESIGNATION,
         C26_INFL_TYPE_ABR,
         C27_MTP_WARR,
         C30_CUSTOMER,
         C31_YEAR,
         C34_VEHICLE,
         C6_IPC,
         C8_IPC,
         C12_BUDG_GROUP_SALES,
         C25_BRAND,
         C29_PR,
         C36_IPC,
         C41_IPC,
         C5_BPC,
         C18_WIDTH,
         C19_WIDTH,
         C32_WIDTH,
         C1_LINEUP_IND,
         C16_SERIES,
         C17_SERIES,
         C23_OE,
         C33_SERIES,
         C13_LOAD_SINGLE,
         C28_RIM,
         C10_PRODUCT_DESCRIPTION,
         C15_LOAD_DUAL,
         C20_PRODUCT_DESCRIPTION,
         C3_SPEED,
         C21_WINTER
    values
         :C9_MTP_,
         :C14_MTP_,
         :C37_MTP_,
         :C38_MTP_,
         :C2_BUDG_CAT_SALES,
         :C7_PATTERN,
         :C11_BUDG_CAT_SALES,
         :C24_SIZE_DESIGNATION,
         :C26_INFL_TYPE_ABR,
         :C27_MTP_WARR,
         :C30_CUSTOMER,
         :C31_YEAR,
         :C34_VEHICLE,
         :C6_IPC,
         :C8_IPC,
         :C12_BUDG_GROUP_SALES,
         :C25_BRAND,
         :C29_PR,
         :C36_IPC,
         :C41_IPC,
         :C5_BPC,
         :C18_WIDTH,
         :C19_WIDTH,
         :C32_WIDTH,
         :C1_LINEUP_IND,
         :C16_SERIES,
         :C17_SERIES,
         :C23_OE,
         :C33_SERIES,
         :C13_LOAD_SINGLE,
         :C28_RIM,
         :C10_PRODUCT_DESCRIPTION,
         :C15_LOAD_DUAL,
         :C20_PRODUCT_DESCRIPTION,
         :C3_SPEED,
         :C21_WINTER
    )

  • Hyperlinks Truncating on Export from Access 2007

    I have a report in Access 2007 that includes a memo field in RTF format.  Quite often part of the text in this field will include one or more hyperlinks.  The hyperlinks work fine in Access.
    I export this report to .pdf using the following line of VBA code, attached to a button on a form:
    DoCmd.OutputTo acOutputReport, stDocName, acFormatPDF, vrtSelectedItem & "\" & title & ".pdf"
    This code works fine, and the report is exported to the selected location properly.  And if the hyperlink text all fits on one line in the .pdf file, then the link works correctly there, too.
    The problem is when the hyperlink text ends up being wrapped around to a 2nd line or more.  The entire link still LOOKS like a link in the .pdf file (it's still blue/underlined), but only the first line is actually a hyperlink.
    For example, if the link text were:
    http://forums.adobe.com/community/
    acrobat/post!input.jspa?containterType=14
    ...then the only part that would actually be a hyperlink in the .pdf document would be "http://forums.adobe.com/community/" and the 2nd line of the link is lost.
    We have thousands of these hyperlinks all throughout our data, and many of them are more than one line long.  It is not feasible for us to shorten all of them using bit.ly.  Nor is it feasible for us to make our users copy and paste the broken links from the .pdf's into their browsers.
    So, does anyone know how to fix this so that the hyperlinks we pass to .pdf from Access remain complete hyperlinks, even if they are more than one line long?

    Finally figured out the solution myself, after 2 days.  It's surprisingly simple.
    If the URL is surrounded by double quotes in the data, then it works as a complete link when exported to .pdf, even if the link wraps to a 2nd line or more.  The quotes show up in the .pdf, too, but that's a small price to pay to have working links.

  • Problems with migrating from access to oracle

    OMWB has a few problems with upper and lower case letters, when i try to modify my old access DB OMWB cant find the new table in Oracle:
    (3011 The Microsoft Jet database engine could not find the object <name>. Make sure the object exists and that you spell its name and the path name correctly. )
    the problem is that it searching for AP_BILD.A990BILDER but the correct name is AP_BILD.a990Bilder
    when i recreate the table as AP_BILD.A990BILDER it worked.
    but i cant do that for almost 400 tables!
    any suggestion how to fix this?
    also have a problem when creating the trigger:
    OMWB puts the tablename into 2 double quotation marks each side (""name"") and of course it tells me something of a tablenamelength of NULL and it doesnt work
    working with release 9.2.0.1.0 of OMWB

    update: if i try to link the table from access directly it also cant find the table, but can find other tables (the others are in upper case).
    could it be a problem with the odbc driver? does it automatically look for upper case names?
    anyone know how to fix this?
    thanks in advance

  • While migrating from access to oracle ??

    While loading data from SQL Loader, DATE is taken as dd-mmm-yy (eg: 18-MAR-02) even after specified in "mm/dd/yyyy HH24:mi:ss" in controlfile. How to resolve this problem ???
    rgds,
    manish

    Hi,
    Did you follow all the steps in the SQL*Developer documentation about preparing the Access database for migration -
    Oracle® SQL Developer User’s Guide Release 3.0 -
    2.2.4.3 Before Migrating From Microsoft Access
    and -
    Oracle® SQL Developer Supplementary Information for Microsoft Access Migrations Release 3.0
    2.4 Preparing the Microsoft Access Database for Capture
    The error also indicates there may be a problem with your Access installation so could you check that everything is okay with that ? I have found references that indicate a re-install of Office/Access will prevent the error.
    Regards,
    Mike

  • Exporting from Access / Importing to Oracle9i

    Hi
    I am trying to figure out a way of exporting an Access database to 9i. This is fine if I am just exporting text, I then use Access as the fromt end to Oracle. However I would like to export a database which hold OLE objects (i.e Word docs, and Excel sheets) into 9i and agin connect to it via ODBC with linked tables. Is this possible??? Does anyone know how to, or where I could find info on how to, I would be grateful.
    Thanks very much and have a good weekend
    John

    I think it's unlikely that this is possible. The ODBC protocol doesn't generally support the sending of LONG/ BLOB/ CLOB data, so Access is unlikely to know how to do this. Oracle's ODBC driver does provide support for these datatypes, but it is relatively unique in this regard.
    Justin

  • Transfer of files from access to oracle

    i want to transfer the data base files of ms access to oracle. without using oracle navigator how should i transfer the files?

    This forum is for feedback about the OTN program and problems with OTN accounts. Technicalquestions cannot be answered here. Please post your question in the appropriate product or technology forum

  • Data trouble when exporting data from Access to Oracle

    Hey,
    I have several tables in Access in which I am exporting to Oracle. The exporting works fine, but some of the ' are getting converted to ? during the export, so any fields that have words like government's or women's are now spelled government?s and women?s. Any ideas on why this would be happening and on how to fix it?
    Thanks

    What is your database character set in Oracle? What is your NLS_LANG parameter set to on the client?
    I'm guessing that your data contains some of Microsoft's special characters (things like curly quotes) rather than the standard ASCII apostrophe. Both the database character set and the client NLS_LANG would have to be configured to a character set that supports those characters in order for the data to be transferred correctly.
    Justin
    Distributed Database Consulting, Inc.
    http://www.ddbcinc.com/askDDBC

  • Migration from Access to Oracle 10g (Problem with migration wizard)

    Hi
    I have an access database which I want to migrate to Oracle DB.
    I have created 2 connections.
    1. Access connection with the source database
    2. Oracle connection.
    I have associated the oracle connection to the repository.
    When I go through 'MIGRATION WIZARD' process. I am not able to view the source database file while capturing. Tried it several times.
    Need a help in this
    Regards,
    Arjun
    Edited by: 919650 on Mar 9, 2012 2:47 AM

    Arjun,
    you cannot do an online migration with MS Access as you can do with other foreign datasources. You can only do an offline migration.
    The first step that you need to do is to call the Microsoft Access Exporter. Click on Tools - Migration - Microsoft Access Exporter and chose the exporter of the MS Access version that you are using.
    The exporter creates an xml file for you. After the exporter has finished you can do the migration, click on Tools - Migration - Migrate, but in Step 4 please select "Offline", and then you can select the xml file that the exporter has created. The following steps in the Migration assistant are then doing the migration for you.
    You might also want to read the chapter "Before Migrating From Microsoft Access" in the online help of SQL Developer.
    Regards
    Wolfgang

  • Export table access to oracle with Database ODBC()

    Hi,
    I export a table, access 2003, ent_tab whit  'DataBase ODBC()' to oracle.
    I open Oracle SQL Developer and i can show table ent_tab, but i go worksheet and execute:
    select * from ent_tab
    and display error: ORA-00942...
    Why??!!
    Regards
    Jomar

    Because ODBC created the table with "" which allowed lower case table name, but Oracle uses upper case table name by default. Suggest you recreate the table with upper-case name to avoid having to use "" in select statements.
    Edited by: rgeier on Oct 27, 2009 5:34 PM

Maybe you are looking for