Export.ddl

Hi friends...
please anybody can help to solve the following question..this question was ask me in my last interview.
The attached DDL (“export.ddl”) has been written to work on Oracle 10g,11g
But it doesn’t work on Oracle 9i, for example when we try to add user it gives the attached error “error.txt”
The questions are:
1- Where are the errors (which table, view , trigger …etc. )
2- How to fix it one by one
3- The new script after fixing the errors
the error.txt file is:
ORA-04068: existing state of packages has been discarded
ORA-04063: has errors
ORA-04063: package body "TBS_DPL.SQLSERVER_UTILITIES" has errors
ORA-06508: PL/SQL: could not find program unit being called
ORA-06512: at "TBS_DPL.TBST_USERS_US_UID_TRG", line 19
ORA-04088: error during execution of trigger 'TBS_DPL.TBST_USERS_US_UID_TRG'
ORA-06512: at "TBS_DPL.TBSP_INSERTUSERDATA", line 47
ORA-06512: at line 1
Edited by: JIC on Feb 7, 2012 12:46 PM
Edited by: JIC on Feb 7, 2012 12:53 PM

10g and 11g support Data Pump where 9i doesn't. Don't know if they used 9i or not, but ...
The program unit being called not found is either a new feature in 10g or it's an add on that was not installed on 9i.
Having the script would help a lot.
Dean

Similar Messages

3.0.0-665 - Export DDL is empty

I have a relational model in DM and select menu Export / DDL File.
I leave the selection Oracle Database 11g and click Generate.
In the new dialog I leave everything as is (all tables and other items selected) and click OK.
The result is just some comments:
-- Generated by Oracle SQL Developer Data Modeler 3.0.0.665
-- at: 2011-02-24 18:45:45 CET
-- site: Oracle Database 11g
-- type: Oracle Database 11g
-- Oracle SQL Developer Data Modeler Summary Report:
-- CREATE TABLE 0
-- CREATE INDEX 0
-- ALTER TABLE 0
-- more here, I deleted for brevity
-- DROP TABLESPACE 0
-- DROP DATABASE 0
-- ERRORS 0
-- WARNINGS 0
With some other model, it works.
Any idea what to look for?
I also tried Oracle SQL Developer 3.0 Early Adopter 4 (3.0.03.97), but it is the same there too (just comments are created).
I also tried to export just one table, but the result is same, just the above comments.
Regards,
David

Thanks for the picture. That all looks fine. Its contents tells me that you have not got the relevant Physical Model open. (If the Physical Model is open, the Tables do not appear on the "Tree View" tab that is shown in your picture; instead you need to go to the Tables tab to see the list of Tables.)
Physical Models allow you to provide additional information relevant to a specific database type (e.g. Oracle 10g or 11g). Physical Models appears in the Data Modeler Browser as a node below a specific Relational Model.
To create one you can select "New" on the right-click drop-down menu for Physical Models. Import from Data Dictionary will also create a Physical Model of the relevant type.
Reopening a saved Design does not automatically reopen its Physical Models; nodes for those that are included in the saved design will appear as a component of the Physical Models node, but to open one you need to select "Open" from the right-click drop-down menu for the relevant physical model.
David

SQL Developer 3.2 - Export DDL challenge

Hi,
I would like to Export DDL for approximately 300 of 1000 objects in a schema. I have the names of all required tables for which I'd like to get the DDL in a table in my personal schema. Is there a way that I can use this table as a driver for the built-in Export DDL utility or will I need to either go to the schema browser and hand-pick each of the 300 tables and/or from the Tools-Export DDL "Specify Objects" window?
I would like to make this more automated so that I dont have to keep clicking, scrolling, clicking my way through the list of required objects. Any thoughts are appreciated, thanks.

1008686 wrote:
Hi,
I would like to Export DDL for approximately 300 of 1000 objects in a schema. I have the names of all required tables for which I'd like to get the DDL in a table in my personal schema. Is there a way that I can use this table as a driver for the built-in Export DDL utility or will I need to either go to the schema browser and hand-pick each of the 300 tables and/or from the Tools-Export DDL "Specify Objects" window?
I would like to make this more automated so that I dont have to keep clicking, scrolling, clicking my way through the list of required objects. Any thoughts are appreciated, thanks.
There is no way to use sql developer to do that.
You can:
1. do it manually as you suggest
2. do it manually by writing a script that makes the appropriate DBMS_METADATA calls
3. use expdp to extract the metadata and create a DDL file.
The full DDL for a table will include a lot of components that many people don't even want, for example storage clauses.
The bigger issue you should address is why you don't already have the DDL to begin with. Best practices are to create the DDL and keep it in a version control system; not extract it after the fact.
I suggest you use the EXPDP utility to extract the DDL into a file so that you have it for future use.
If you plan to write a script there are plenty of examples on the web that show how to do that. Here is one:
http://www.colestock.com/blogs/2008/02/extracting-ddl-from-oracle-2-approaches.html

BUG: Export DDL and Data fails for mixed case table/column names

Hi there,
I have found a bug in SQL Developer. See details below.
Description:
When "Export DDL and Data) function is used on a table/columns not named in UPPERCASE, sql generated by SQL Developer is invalid.
Steps to reproduce:
- open SQL Developer, connect to DB
- make a table named "lowerCase" (in double quotes, so it won't be automatically changed to capital letters)
- you may also add some columns, for example "lowerCol1", "UpCol2", ALLUPCOL3
- add some data rows to the table
- choose Tools -> Export DDL and Data
- check exporting of tables and data, on "filter" tabs choose your "lowerCase" table
- press "Apply"
Error:
Generated SQL contains invalid INSERTs: mixed-case table and columns are referenced without obligatory double quotes, which yields an error when generated script is executed (see below, relevant line is underlined)
-- DDL for Table lowerCase
CREATE TABLE "DBO_HT"."lowerCase"
(     "lowerCol1" VARCHAR2(100),
     "UpCol2" VARCHAR2(100),
     "ALLUPCOL3" VARCHAR2(100)
-- DATA FOR TABLE lowerCase
-- FILTER = none used
-- INSERTING into lowerCase
Insert into lowerCase (lowerCol1,UpCol2,ALLUPCOL3) values ('lc','uc','auc');
-- END DATA FOR TABLE lowerCase
Remarks
SQL Developer: version 1.2.1, build MAIN-32.13
Oracle DBs: 9.2 & Express
OS: Windows 2000 Professional
If you need any more details/testing, let me know. I'd really appreciate a quick patch for this issue...
Alternatively, do you know of any other simple way of copying a single database (it's called a schema in Oracle, right?) from one computer to another? Possibly something so simple like detaching->copying->reattaching mdf (data) files in SQL Server... I thought that this "Export DDL&Data" function will do, but as you can see I couldn't use it.
I just need a simple solution that works - one operation on source to stuff, get the resulting files to other computer and one operation to have it running there... I think that such scenario is very basic, yet I just can't achieve it and I am simply not allowed to spend more time on it (read: our test project fails, my company rejects my "lobbying" and stays with MSSQL :/ )
Thanks a lot & bye

Thanks for your reply.
ad. 1)
You're right. I just wanted to give some very short feedback on my experiences with SQL Developer, so I didn't think starting new threads would be necessary, but as I was writing it became much bigger than I initially planned - sorry about that. I will make proper threads as soon as possible. Having "Edit post" button on this forum would also be useful.
ad. 2)
Generally, you're right - in most cases it's true that "switching DBMS is a major commitment" and "you will produce terrible code" if you don't learn the new one.
However, I think that you miss one part of market here - the market that I think Express is also targeted on. I'd call it a "fire&forget databases" market; MySQL comes to mind as possibly most common solution here. It's the rather small systems, possibly web-accessed, whose data-throughput requirements are rather modest; the point is to store data at all, and not necesarily in fastest way, because given the amount of data that is used, even on low-end hardware it will work well enough. What's important here is its general ease of use - how easy is to set up such system, connect and access data, develop a software using it, how much maintenance is needed, how easy this maintenance is, how easy are the most common development tasks as creating a DB, moving a DB from test to production server etc. There, "how easy" directly translates to "how much time we need to set it up", which translates to "how much will the development will cost".
Considering the current technology, switching the DBMS in such systems is not necesarily a major commitment and believe me that you will not produce terrible code. In many cases it's as simple as changing a switch in your ORM toolkit: hibernate.dialect = Hibernate.Dialect.OracleDialect vs MySQLDialect vs MsSql2005Dialect
Therefore, in some part of market it's easy to switch DBMS, even on project-by-project basis. The reason to switch will appear when other DBMS makes life easier => development faster. From that point of view, I can understand my colleagues giving me an embarassing look and saying "come on, I won't read all these docs just to have db copied to test server". And it doesn't mean "they are not willing to learn anything new", it's just that they feel such basic task should have self-explaining solution that doesn't require mastering any special knowledge. And if they get such simple solutions somewhere else, it costs them nothing to change the hibernate dialect.
I think Oracle did the great job with introducing the Express to this "fire&forget" market. The installation is a snap, it just works out of the box, nothing serious to configure, opposite to what I remember from installing and working on Oracle 9 a few years ago. In some places it's still "you need to start SQL*Plus and enter this script", but it's definitely less than before. I also find the SQL Developer a great tool, it can do most of what we need to do with the DB, it's also much better and pleasant to use over Oracle 9 tools. Still, a few basic things still require too much hassle, and I'd say taking your schema to another machine is one of them. So I think that, if you do it well, the "schema copy wizard" you mentioned might be very helpful. If I was to give any general advice for Express line of DB/tools, I'd say "make things simple" - make it "a DB you can't see".
That's, IMHO, the way to attract more Express users.

SQL Tab & Export DDL Crapped Out in Version 1.1.3

SO now the SQL tab for a table and the Export DDL option under the Tools menu are not working. The Export DDL option does nothing short of error our when trying to select individual options. (Getting a table or view does not exist error) The SQL tab for tables now no longer shows the associated constraints and in some cases no indexes either. The previous version didn't seem to have these problems. I really think the things that were working need to be verified to not be broken before releasing a new version. As an end user it's pretty frustrating to lose functionality when you think you are gaining new features.
OS Version: Windows XP SP2
Oracle DB: 10.1.5

tnolte,
I'm going to stick to this thread to respond to your queries.
I see from (Re: [1.1.3.27.66] create ddl statement that you are running into the ora-942 errors. No-one in that thread mentions that they have switched to the latest release of SQL Developer, i.e. 1.2. Though both you and MRM posted after we released 1.2., so I assume you are. If not, that's a good place to start.
Please can you confirm, that you are on 1.2 and that you are still running into this error? As mentioned we did have logged and now fixed, the ora-942 errors you mention, so I'd like to track down your specifics. It looks like a permissions issue.
In terms of the new Export DDL:
1. We had a request for a 1 button click to export everything for a single schema. To do this, after you have specified the files name and schema, all you need to do is click Apply and all objects, with all the data will be exported.
So this is: Set file name, select schema, Apply.
2. To export a specific category, I start by unchecking "Export Object Types", this unchecks all and I can then check only those I require, say tables and sequences. Now if I select Apply, ALL Tables and ALL sequences for that schema are exported.
So this is: Set file name, select schema, uncheck Export Object Types, Check specific object type categories, Apply.
3. Now, if you want to only export certain, say Tables or Sequences then use the filter tabs. The first is Filter Objects.
If my Connection is for HR and I want to export HR objects, then there is no privilege issue:
After you have taken the steps in #2 above, go to the Filter Objects tab, make sure that the user is HR at the top of the left hand panel and then click GO. (You can use the Object Type drop list on the right to filter for object types.)
Shuttle the objects you want to the right and repeat for the next object type.
If, your connection is HR, but you want to export[i] OE objects, and you have read/select access, then only those objects you have access to will display.
If your access is HR, but you want to export object you have no access to, no objects are displayed.
Is the ora-942 displayed for all your connections? Can you try another connection? Of all my connections, one displays the 942 and I will have a developer look into that. There does not appear to be a permissions issue.
One last thing. If you just want to export the DDL of a selection of tables, expand the Tables node, ctrl select the tables you want the DDL for and use the context menu. There is a new Export option that allows you to export the tables to file, clipboard or the worksheet.
Hope this helps.
I will be doing a blog entry on this, this evening.
Sue

Materialized Views indexed are not excluded when exporting ddl

Hello,
When exporting ddl of the schema, through the export function of the gui, if I disabled materialized views from the objects to be exported, then the indexes of materliazied view are not excluded of the final DDL.
This happens on Version 4.0.3.16, Build MAIN-16.84

Hello,
When exporting ddl of the schema, through the export function of the gui, if I disabled materialized views from the objects to be exported, then the indexes of materliazied view are not excluded of the final DDL.
This happens on Version 4.0.3.16, Build MAIN-16.84

Re: Can't do Export - DDL Script

Greetings!
I am currently using Build 1.1.0.23 Build Main-23.64 against a 9i database.
I too am unable to get the Export->DDL to work. It creates the "export.sql" file, but the contents are empty. I am getting the following error message:
DBMS_METADATA is unable to use TABLE_EXPORT to generate sql.
It tells me to test by entering the following sql statement:
select dbms_metedata.get_ddl('TABLE', 'DUAL', 'SYS') from dual;
This fails:
ORA-31603: object "DUAL" of type TABLE not found in schema "SYS"
I'm no expert, but this looks like a fairly severe bug. I've followed the thread, but I haven't seen anything mentioned about a patch/fix.
Anyone know if there is something out there on the horizon?
Thanks, John

What version of Oracle 9i are you running?
I am guessing here, but I think the Oracle 9i databases available for download have to be patched. However, I think these patches are only available via MetaLink which requires licenses and a current paid contract.
I think people running what is available for Oracle 9i download have the issues while the patched version of the 9i database works. Is my thinking correct here?
What is the minimum patch point release to get Oracle SQL Developer to run out-of-the-box?

"Generate in DDL" checked back after Export DDL

I have a table COUNTRY in a relational model with "Generate in DDL" flag unset. When I export the model with "File > Export > DDL File" the flag is set back and table is exported.
1) Is there a way to "convince" Data Modeler to leave the "Generate in DDL" flag unset and do not export the table?
2) Is this a bug?
There is a Foreign Key to table COUNTRY with the "Generate in DDL" flag set, but I would say this should not change the flag.

I found the problem. When I do "File > Export > DDL File" , then Generate a small window shows with ticks for:
- Whole model
- - Assigned to Schemas
- - Not Assigned to Schemas
- - Schemas
- - Structured Types
- - Collection Types
All are selected and I only need to export objects "Not Assigned to Schemas". If I untick the "Whole Model" then I tick only "Not Assigned to Schemas" it will set all the tables/objects from the model, without using the "Generate in DDL" flag. More than this, it will set back the "Generate in DDL" flag for all objects in the model. Imagine that I have 100 objects into the model, how is to need to tick back the "Generate in DDL" flag for 30 objects of 100 all the time. This is an annoying bug if you agree.

EA2 Export DDL - Save to file issues

Hi,
Export DDL/Save to file, defaults a "/" as file name.
After you have saved a file in a directory the directory is not memorized anymore for the second export, e. g. saving spec and body have to select the same directory twice.
Juergen

Hi Juergen,
Yes, I see the exact same behaviour on my Windows XP SP2 installation when I perform the following steps:
(1) Right click on a, for example, procedure in the Navigator
(2) Select "Export DDL > Save to File..." from the context menu
(3) The "Choose Directory" dialog is displayed, with "/" in the "File name:" field and the starting directory being the root of my C: drive
Preferred behaviour would be:
(1) Default "File name:" field to procedure name
(2) Default starting directory to last used
Thanks,
Chris

Export DDL doesn't work (OS X 10.4)

Hi, when i try to export DDL (from Tools menu) and hit the Apply button nothing append.
I get the following error in the logs :
Exception in thread "AWT-EventQueue-0" java.lang.NoSuchMethodError: oracle.jdbc.OraclePreparedStatement.setStringAtName(Ljava/lang/String;Ljava/lang/String;)V
     at oracle.dbtools.db.DBUtil.bind(DBUtil.java:377)
     at oracle.dbtools.raptor.metadata.MetaData.printDDL(MetaData.java:170)
     at oracle.dbtools.raptor.controls.ExportPanel.export(ExportPanel.java:190)
     at oracle.dbtools.raptor.controls.ExportPanel.actionPerformed(ExportPanel.java:109)
etc...
That looks like a jdbc related issue. SQL developer doesn't use his own jdbc driver ?
client : Mac OS X 10.4 , JDK 5, SQL Developper 1.0.0.14
server : Oracle XE production
Thanks for your help
Message was edited by:
user503346

On the server side yes, ORACLE_HOME is set :
echo $ORACLE_HOME
/usr/lib/oracle/xe/app/oracle/product/10.2.0/server

Export DDL for current schema (feature request "Creation of Object script")

Hello Raptor-Team,
to generate a DDL script for my current schema, I tried your suggestion on SQL Developer Exchange to click on "other users" and then select my user. Wait a minute... where is my current user in this menu? Am I missing something? ;-)
As this technique seems to make sense only with DBA users exporting other schemas, I'll log a new request for the often-desired one-button-current-schema-DDL-generator...
Best regards,
--==/ Uwe \==--

Nope - you're not missing something. I've logged it. Sorry. I know suggesting connecting as SYSTEM and then selecting other users is not what you are after, but if you have access to SYSTEM, that's be a solution. Alternatively, you just have to expand each node type and select the top level category.
Sue

Exported DDL don't run in SQL Plus

Greetings,
I'm using SQL Developer to export the DDL from my DB to a script .sql.
When I try to run it into SQL Plus I get errors because of the <cr> caracters from the INSERT INTO statements generated.
Example:
Insert into CNAE_110_CLASSE (CODIGO_SEC,CODIGO_DIV,CODIGO_GRP,CODIGO_CLA,DESCRICAO_CLA,CCOMPRE_CLA,TCOMPRE_CLA,NCOMPRE_CLA,NOTAS_CLA) values ('D','19','191','19100','CURTIMENTO E OUTRAS PREPARAÇOES DE COURO','# A fabricaçao de couros curtidos, envernizados, metalizados, camurças, atanados, cromos, etc.','# A regeneraçao, tingimento e pintura de couro','# As atividades de secagem e salga de couros e peles desenvolvidas em matadouros (15.11)<cr>
# A confecçao de vestuário de couro (18.12)',null);
This returns:
SP2-0734: unknown command beginning "A confecçao ..." - rest of line ignored.
I'm using Oracle 10g XE and SQL Developer 1.2.0.29.98 on a Fedora CORE 6 linux.
Does someone has a clue to solve this? Is it a bug or I forgot to configure something?
Thanks in advance.

The label <<outer>> does not work in SQL Developer, neither does labels on loops.Yes, they do.
I imagine you've got this example in an SQL worksheet. There are a few issues with the worksheet delimiting statements, and apparently this is one of them.
The workaround here is very simple: encapsulating the lot in another anonymous block. Like this, impossible the <<outer>> falls off...
Enjoy,
K.

EXPORT DDL in 1.0.0.14

I am trying to export the DDL for a particular table. Option is not generating any script into the file.
Oracle 9.0.2.4/Linux AS

Well, I had 20 minutes this morning to install and then get to work! To be honest, I wasn't holding my breath as I never saw a resolution posted in the Beta NG regarding many of us crashing when trying to access the library. Imagine my delight when I could access the Library! I just grabbed a rejected RAW image from a shoot I did a few nights ago (I had manipulated these in ACR at that time)...developed it and then hit the Export button. Crash.
I reopened and used Export previous settings (and was impressed that my develop settings were presereved). This worked and I got a jpg out.
I went back to Export button. Crash.
Export previous always works, but Export always crashes. Thats just not gonna cut it, because I have no access to export options.
Very disappointing.

Error when Exporting DDL script for whole schema

When I right click connection, Select "Export" then "DDL Script", the following error occur (Exception Stack Trace)
java.lang.ClassNotFoundException: oracle.dbtools.raptor.dialogs.actions.UserDDLExport
     at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
     at java.security.AccessController.doPrivileged(Native Method)
     at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
     at oracle.ideimpl.IdeClassLoader.loadClass(IdeClassLoader.java:140)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
     at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:164)
     at oracle.dbtools.raptor.dialogs.BasicObjectModifier.launch(BasicObjectModifier.java:142)
     at oracle.dbtools.raptor.dialogs.BasicObjectModifier.handleEvent(BasicObjectModifier.java:210)
     at oracle.dbtools.raptor.dialogs.actions.XMLBasedObjectAction$DefaultController.handleEvent(XMLBasedObjectAction.java:265)
     at oracle.ide.controller.IdeAction.performAction(IdeAction.java:530)
     at oracle.ide.controller.IdeAction$1.run(IdeAction.java:785)
     at oracle.ide.controller.IdeAction.actionPerformedImpl(IdeAction.java:804)
     at oracle.ide.controller.IdeAction.actionPerformed(IdeAction.java:499)
     at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1849)
     at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2169)
     at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420)
     at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
     at javax.swing.AbstractButton.doClick(AbstractButton.java:302)
     at javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1000)
     at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:1041)
     at java.awt.Component.processMouseEvent(Component.java:5488)
     at javax.swing.JComponent.processMouseEvent(JComponent.java:3126)
     at java.awt.Component.processEvent(Component.java:5253)
     at java.awt.Container.processEvent(Container.java:1966)
     at java.awt.Component.dispatchEventImpl(Component.java:3955)
     at java.awt.Container.dispatchEventImpl(Container.java:2024)
     at java.awt.Component.dispatchEvent(Component.java:3803)
     at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4212)
     at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3892)
     at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3822)
     at java.awt.Container.dispatchEventImpl(Container.java:2010)
     at java.awt.Window.dispatchEventImpl(Window.java:1774)
     at java.awt.Component.dispatchEvent(Component.java:3803)
     at java.awt.EventQueue.dispatchEvent(EventQueue.java:463)
     at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
     at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)

This is actually in our release notes as not implemented yet.
The following capabilities are currently planned to be added by the production release:
Tools > Export - Will be a DDL generator.
I will mention in the release notes when this function is operational. The menu item is just there now as a placeholder.
-- Sharon

Export ddl to file

Guys,
Is there a package that export all ddl to file?
If not then I will use dbms_metadata but I thought maybe there is something build in,
We want to copy the ddl into svn.

You can do this 1 of 2 ways with datapump
perform your normal export to a dumpfile
expdp system/manager directory=dpump_dir dumpfile=full.dmp full=y content=metadata_only
This creates a dumpfile. From here, you can run this through import with a parameter of 'sqlfile=mysql.sql'
impdp system/manager directory=dpump_dir dumpfile=full.dmp sqlfile=mysql.sql
You now have a sqlfile of all of the objects that were in the dumpfile.
If you don't want a dumpfile, you can skip it by setting up a network link (make it a loopkback database link that points to the same system that you are on. Then issue this command.
impdp system/manager directory=dpump_dir network_link=my_loopback_link full=y sqlfile=mysql.sql
All of this requires that you are on verison 10.1 or greater.
Dean

Export.ddl

Similar Messages

Maybe you are looking for