Dropping all deployed tables in OWB 10.2.0.3.0

I am running OWB 10.2.0.3.0 and have multiple schemas containing deployed tables. This is a test instance and I would like to drop all the old tables and recapture some of the space. Is WB_RT_VERSION_FLAG the only table I need to keep intact to keep OWB functioning? Should I also leave CREATE$JAVA$LOB$TABLE and TRACE if it exists? Thanks.

Hi,
you must keep WB_RT_VERSION_FLAG, all the synonyms (created by owb) and the roles of a target user. All other objects may be dropped.
You should consider dropping the objects using control center manager (use context menu on the module an set the action to drop for all objects at once) in order to have the deployment status correctly.
Regards,
Carsten.

Similar Messages

How to delete/drop all the tables from SQL Server Database without using Enterprise Manager?

How to delete/drop all the tables from SQL Server Database without using Enterprise Manager?
I tried using DROP Tables, Truncate Database, Delete and many more but it is not working. I want to delete all tables using Query Analyzer, i.e. through SQL Query.
Please help me out in this concern.
Nishith Shah

Informative thread indeed. Wish I saw it early enough. Managed to come up with the code below before I saw this thread.
declare @TTName Table
(TableSchemaTableName
varchar
(500),
[status] int
default 0);
with AvailableTables
(TableSchemaTableName)
as
(select
QUOTENAME(TABLE_SCHEMA)
+
+
QUOTENAME(TABLE_NAME)
from
INFORMATION_SCHEMA.TABLES)
insert into @TTName
(TableSchemaTableName)
select *
from AvailableTables
declare @TableSchemaTableName varchar
(500)
declare @sqlstatement nvarchar
(1000)
while 1=1
begin
set @sqlstatement
=
'DROP TABLE '
+ @TableSchemaTableName
exec
sp_executeSQL
@sqlstatement
print
'Dropped Table : '
+ @TableSchemaTableName
update @TTName
set [status]
= 1
where TableSchemaTableName
= @TableSchemaTableName
if
(select
count([Status])
from @TTName
where [Status]
= 0)
= 0
break
end

To drop all the tables in a database

hi,
I have 25000 tables in a database.I want ot delete all the tables and then i have to import the dump.For deleting all the tables what query has to be given.
Thanks in advance,
R.Ratheesh

The code would be
BEGIN
   FOR c IN (SELECT owner,
                    table_name
               FROM all_tables
              WHERE owner IN ('YOUR_OWNER1', 'YOUR_OWNER2_ETC'))
   LOOP
      EXECUTE IMMEDIATE    'drop table '
                        || c.owner
                        || '.'
                        || c.table_name
                        || ' cascade constraints';
   END LOOP;
END;
the user ,tablespaces ,datafiles has to be recreatedbut still dropping the user would be the simplest option
you don't have to recreate tablespaces and datafiles for that.

Script for dropping all the tables

Hello:
Can somebody share with me a script that will delete all the tables in a schema?
Thanks.

I think what Justin was getting at is this: we cannot drop tables that are referenced by foreign keys. So before we can drop all tables weed to drop all referencing constraints. Which makes this script even more dangerous - you may wish to abort if other schemas reference the "droppee".
Let's be careful out there!
Cheers, APC
declare
    cursor fks is
        select owner,table_name, constraint_name
        from all_constraints
        where r_owner='&&schema_to_delete'
        and constraint_type = 'R';
    cursor tables is
        select owner,table_name
        from all_tables
        where owner='&&schema_to_delete';
    begin
        for b in fks
        loop
            dbms_output.put_line( 'drop fk constraint '||b.owner||'.'||b.table_name||'.'||b.constraint_name);
            execute immediate 'alter table '||b.owner||'.'||b.table_name||' drop constraint '||b.constraint_name;
        end loop;
        for c in tables
        loop
            dbms_output.put_line( 'drop table '||c.owner||'.'||c.table_name);
            execute immediate 'drop table '||c.owner||'.'||c.table_name;
    end loop;
end;
/

10g: Must all related tables be in the same project?

Since we will eventaully have over 500 tables to map, we would like to be able to maintain these tables/classes in different projects. How do we map foreign key references between tables/classes that we would like to maintain in different projects?
I don't know if theis is why I'm getting this error, but I initially created two projects with independent tables. Then I wanted to join some tables in one project to some tables in another project. (This is all using Offline Database Objects.) I dropped some tables managed in project A into the diagram for project B and created the foreign key relations (from B to A.) Now whenever I try to open the TopLink Mappings node for project B in the Navigator, I get the following error. I get this error even if I drop ALL the tables from project A into project B's diagram (meaning there is nothing left in the schema that could be the missing 'parent'.)
Local Exception Stack:
Exception [TOPLINK-98] (Oracle9iAS TopLink - Release 2 (9.0.4.0) (Build 030612)): oracle.toplink.exceptions.DescriptorException
Exception Description: The underlying descriptor callback method [postBuild], with parameter (DescriptorEvent), triggered an exception.
Internal Exception: java.lang.reflect.InvocationTargetException
Target Invocation Exception: java.lang.IllegalStateException: This object is missing a parent: MWTable[C14] (AVEGA.DATAMART)
Descriptor: XMLDescriptor(oracle.toplink.workbench.model.MWProject --> [DatabaseTable(project)])
     at oracle.toplink.exceptions.DescriptorException.<init>(DescriptorException.java:207)
     at oracle.toplink.exceptions.DescriptorException.<init>(DescriptorException.java:212)
     at oracle.toplink.exceptions.DescriptorException.targetInvocationWhileEventExecution(DescriptorException.java:1364)
     at oracle.toplink.publicinterface.DescriptorEventManager.executeEvent(DescriptorEventManager.java:133)
     at oracle.toplink.internal.descriptors.ObjectBuilder.buildAttributesIntoObject(ObjectBuilder.java:179)
     at oracle.toplink.internal.descriptors.ObjectBuilder.buildObject(ObjectBuilder.java:331)
     at oracle.toplink.queryframework.ObjectLevelReadQuery.buildObject(ObjectLevelReadQuery.java:227)
     at oracle.toplink.queryframework.ReadObjectQuery.execute(ReadObjectQuery.java:344)
     at oracle.toplink.queryframework.DatabaseQuery.execute(DatabaseQuery.java:498)
     at oracle.toplink.queryframework.ReadQuery.execute(ReadQuery.java:111)
     at oracle.toplink.publicinterface.Session.internalExecuteQuery(Session.java:1968)
     at oracle.toplink.publicinterface.Session.executeQuery(Session.java:1096)
     at oracle.toplink.publicinterface.Session.executeQuery(Session.java:1048)
     at oracle.toplink.publicinterface.Session.readObject(Session.java:2502)
     at oracle.toplink.workbench.ui.WorkbenchSession.getMWProjectNamed(WorkbenchSession.java:270)
     at oracle.toplink.addin.persistence.MWJDeveloperPersistence.open(MWJDeveloperPersistence.java:176)
     at oracle.toplink.tsceditor.persistence.PersistenceManager.open(PersistenceManager.java:942)
     at oracle.toplink.addin.manager.MWJDeveloperMediator.openMWProject(MWJDeveloperMediator.java:164)
     at oracle.toplink.addin.manager.MWJDeveloperMediator.locateAndOpenProjectImp(MWJDeveloperMediator.java:626)
     at oracle.toplink.addin.manager.MWJDeveloperMediator.getEditableObjectFor(MWJDeveloperMediator.java:430)
     at oracle.toplink.addin.ui.view.explorer.MWExplorer.updateExplorer(MWExplorer.java:586)
     at oracle.toplink.addin.ui.view.explorer.MWExplorer.setContext(MWExplorer.java:458)
     at oracle.ideimpl.explorer.ExplorerManagerImpl.getExplorerForHost(ExplorerManagerImpl.java:1048)
     at oracle.ideimpl.explorer.ExplorerWindowImpl.viewSelectionChanged(ExplorerWindowImpl.java:544)
     at oracle.ide.addin.AbstractPinnable.viewSelectionChanged(AbstractPinnable.java:232)
     at oracle.ideimpl.explorer.ExplorerWindowImpl.viewSelectionChanged(ExplorerWindowImpl.java:376)
... etc.

If you wish to split your project up into two projects and have some relationships between some of those objects in the projects, you could map all of the objects for each project, but do not map the relationships. For those classes with relationships to other classes in other project you can define an amendment method. An amendment method is a callback into Java code that will be called when the descriptor is loaded. In this method you can then create the mapping to the class in the other project through the descriptor and mapping code API. (see oracle.toplink.mappings, oracle.toplink.publicinterface.Descriptor)
You can also make use of descriptor deactivation to define relationships between projects. For this you would import the related classes into the project and deactivate them. This will allow you to define relationships to them, but will not export their mapping information when deploying.
In general it is probably easier to keep everything in one project and use your content/code management system and merge tools to manage the project.

How to drop all tables in perticular schema??

Hi,
I am new in oracle.
I want to drop all tables in one perticular schema,
Please tell me solution.
PratHamesh

If your few of your tables have referential intigrity constraints and trying to drop master table whithout droping child table first, oracle will produce an error.
Better option would be to drop the entire schema and then create a new schema with the same name.
on sql plus.
set long size 20000
select dbms_metadata.get_ddl('USER','USERNAME') from dual;
--then save the above output to create the user later.
drop username cascade
use the above saved script to create the user again.
Jaffar

ORA-12983: cannot drop all columns in a table

Hi,
I am creating a table with two columns.
I have modified a column as unused using ALTER statement.
After that i have tried to drop the another column by using ALTER statement.
But it throws an error ORA-12983: cannot drop all columns in a table.
is it not possible to achieve this via ALTER statement?
thanks

is there any other way to find the name of the columns which have been marked as unused?Don't think so, and you would not be able to do much about. You won't be able to reference it, you won't be able to un-unuse it, and you would even be able to add a new column having same name.
Why are you using SET UNUSED in the first place?
Regards
Peter
Quoting myself:
You won't be able to reference itMaybe not good enough:
SQL> select column_name, data_type, segment_column_id
from user_tab_cols
where table_name = 'T';
COLUMN_NAME                    DATA_TYPE   SEGMENT_COLUMN_ID
SYS_C00001_11051618:28:14$     NUMBER                      1
B                              NUMBER                      2
SYS_C00003_11051618:28:14$     NUMBER                      3
3 rows selected.
select "SYS_C00003_11051618:28:14$" from t
Error at line 1
ORA-00904: "SYS_C00003_11051618:28:14$": invalid identifier
SQL> alter table t drop column "SYS_C00001_11051618:28:14$";
Table altered.
SQL> select column_name, data_type, segment_column_id
from user_tab_cols
where table_name = 'T';
COLUMN_NAME                    DATA_TYPE   SEGMENT_COLUMN_ID
B                              NUMBER
1 row selected.
Note: Both columns "disappeared" Thanks MichaelS
Edited by: Peter on May 16, 2011 9:29 AM

How to drop all constraints on a table?

Oracle 11gR2
I tried this but no luck!
ALTER TABLE testDB.dbo.testTable1
DROP ALL CONSTRAINT
GO

Oracle 11gR2
I tried this but no luck!
ALTER TABLE testDB.dbo.testTable1
DROP ALL CONSTRAINT
GO
You never will have any 'luck' trying to execute SQL SERVER statements on an Oracle database.
There is no Oracle command to drop all constraints from a table.
1. create a new table using CTAS - CREATE newtable AS SELECT * FROM oldtable
2. drop the orginal table - DROP oldtable
3. rename the new table to the old name - RENAME newtable to oldtable
Constraints will be gone.

Versioning, Deployment, Execution in OWB 9.2

For the warehouse created using OWB versions 9.0.3, my company used a versioning tool. All the PLS generated using OWB were moved to Source control system and from there deployed to Target Schema.
Now in 9.0.4 generated code contains location information that gets replaced by physical location only when code is deployed using OWB. So the old system of versioning and deployment doesnt work. We need to deploy using OWB only. In this case we loose all the versioning of mappings.
Question 1 :
Will you please suggest a solution how can we do versioning of our code now ? Versioning is very important for us. In case it is not possible then can we go back to old system of deployment and execution by doing some manual workarounds.
Question 2 :
Is it necessary to deploy thru OWB only because of Location factor. In that case if we design such that source and target tables are in the same then these mappings will not contain location information and we should be able to deploy them without using OWB ? What are the other disadvantages of using this approach.
Question 3 :
When executing mapping using the template provided by OWB, we need to provide location name and execute it from Runtime Repository owner. I guess, When I deploy outside OWB I will not be able to use this method of execution. Default parameters and custome parameters of the mapping are stored in run time repository under the location name at the time of deployment . This information is accessed by the template to execute mapping. ( is it true ??)
We are not going to use multiple physical configuration for the same mapping, so if we deploy not using owb, can we execute directly in Target schema, without using template. How can we provide the input parameter to Main function in this case ?
Question 4 :
Will we be able to get Audit information if we do not use OWB's recommended way of deployment and execution.
Vibha

Vibha,
Question 1:
What you can do, is store the entire deployment script using the deploy to file option and version control that file. The format will be an ASCII-based XML file that versions exactly the same as you would version the files that OWB generated in previous releases.
Also, you may be interested in the version control you can do inside of OWB. That is, as of 9.0.4 we enable you to create snapshots of your design, which you could compare and restore at any point in the future. In 9.0.4, we provided a beta UI on top of this feature (scripting would be the other way to go), but in 9.2 we provide a production quality UI. To enable the UI in 9.0.4, close the product, locate preference.properties in <owb home>\owb\bin\admin and change the setting for MCMUIEnabled from false to true. Please do consider migrating to OWB92...
Question 2:
The locations were also introduced to support multi deployment (e.g. development, test, production) with potentially different physical setups of the machines, but no design changes necessary. Also, execution uses the location concepts. Did you already read http://otn.oracle.com/products/warehouse/pdf/OWB_RuntimeChanges.pdf, which contains more information about the changes and why these are there?
Question 3:
To execute directly from the database, I recommend you download http://otn.oracle.com/sample_code/products/warehouse/files/run_my_owb_stuff.sql and use that as the basis for your execution. The entire architecture changed from 9.0.3 to 9.0.4... and the runtime platform now manages the execution. Via the script above you get a wrapper around the script that OWB provides out of the box (minimum version 9.0.4.10).
Question 4:
The generated code contains all the calls to log the audits, so in principle yes. Having said that, if you do not deploy through OWB... it will be difficult to get the correct references that OWB will use during its logging to be resolved. I hope that with the explanation above you will be able to deploy and run inside the OWB context and make the entire environment work for you.
Thanks,
Mark.

Peculiar Deployment Error in OWB

Hi All,
I have a mapping (M_TEST_PROCEDURE) which has the following sequence of operators.
Source Table -> Mapping Transformation (Procedure) -> Expression -> Pivot -> Target Table.
The mapping validates without any errors. But when tried to deploy this mapping it gives me the following error.
OWB Error MappingGenerator.generate WBGeneratedObject[] in null or length 0 for M_TEST_PROCEDURE.
The detailed error message is:
oracle.wh.repos.sdk.exceptions.WBException
oracle.wh.repos.sdk.exceptions.WBException
     at oracle.wh.ui.runtime.application.WHRuntimeProgress.notifyInternalError(WHRuntimeProgress.java:180)
     at oracle.wh.ui.runtime.application.WHRuntimeGeneration.run(WHRuntimeGeneration.java:111)
\nCMPException message and stack trace:\njava.lang.NullPointerException
     at oracle.wh.ui.runtime.application.WHRuntimeCommandHandler.actionPerformed(WHRuntimeCommandHandler.java:277)
     at oracle.wh.ui.common.OWBConsumer.dataItemAvailable(OWBInfoBus.java:380)
     at javax.infobus.DefaultController.fireItemAvailable(DefaultController.java:90)
     at javax.infobus.InfoBus.fireItemAvailable(InfoBus.java:989)
     at oracle.wh.ui.common.OWBInfoBus.produce(OWBInfoBus.java:159)
     at oracle.wh.ui.common.OWBInfoBus.produce(OWBInfoBus.java:76)
     at oracle.wh.ui.runtime.application.WHRuntimeProgress.showResults(WHRuntimeProgress.java:84)
     at oracle.wh.ui.runtime.application.WHRuntimeGeneration.run(WHRuntimeGeneration.java:107)
If the mapping sequence is
Source Table -> Expression -> Pivot -> Target Table.
The mapping works fine and gets deployed without any errors.
Also if the mapping sequence is
Source Table -> Mapping Transformation (Procedure) -> Expression -> Target Table.
The mapping works fine and gets deployed without any errors.
The problem occurs only when the Mapping Transformation (using a procedure) is used with a pivot operator.
Has anybody experienced such problems before ??? If yes, can you please throw some light as to why is this happening. There is one more thread in this forum regarding the same problem, I have seen that but the problem still persists..
All your valued suggestions are welcome.
Regards
-AP

The target table loading type is INSERT, and match by constraint is set to 'No constraints'.
There is no INSERT/UPDATE or UPDATE/INSERT anywhere in the mapping.
This really seems to be a awkward problem.
You can try yourself. Make a stored procedure (doing a very simple thing ... taking an input value adding a constant value and then returning that value back).
The sequence of operators used in the mapping:
Source Table -> Mapping Transformation (using the above procedure) -> Expression Operator -> Pivot Operator -> Target Table.
Try to deploy the code ... u will get a deployment error which OWB itself does not understand.
Any more hints of help ?
Regards
-Arnab

Unable to deploy Mapping in OWB

I am using OWB 10.1.0.4.0 for development purposes.
I created a source module and a target module and then created a mapping.
The mapping references 2 tables from the source and one table from the target itself.
2 grant statements were executed from the source schema granting select on these 2 tables to the target schema.
A database link was created in the target schema using the CREATE DATABASE LINK statement.
A connector was deployed and successfully created in the target module in OWB.
When I deploy the mapping, I get the error – table or view does not exist
I checked the script that was generated as a result of the mapping deployment.
All three tables are available in the select query. But the tables referenced from the source schema do not have
the source schema name attached to them.
i.e., if EMP table is referenced from the source schema SRC, the query should have SRC.EMP in the FROM
clause. But this is not the case. Only EMP is referenced.
I tried everything I could think of , but I am unable to deploy the mapping.
Any suggestions are greatly appreciated

In your map, does the source table reside in the OWB src module, and the target table reside in the target module? And the modules are configured correctly, so src module uses src location and tgt module uses tgt location. If OWB thinks these are in the same database instance schema.table references should be generated in the code, db link will not be used. The way this same locality is determined is by comparing the host, port,service names for example. Did you create your map like this? Or did you just add unbound tables representing the source and target in the map? So with OWB you can build bottom up or top down.
Cheers
DAvid

Way to programmatically drop-and-create-tables?

Hi all,
I have a persistence unit which exists to provide lookup information to my application. It is populated by data that is available at runtime. It takes a long time to parse this data, and therefore my intention is to only parse it once at the deployment target. To do this, I have created a main method that does all the parsing, and I do not set the toplink.ddl-generation property in persistence.xml. This causes the application to fail if the database is not created.
However, this means that during the population stage, I must drop and create any existing tables. I had thought it would be possible to do this by obtaining an EntityManagerFactory which has a property map sent to it, containing the property toplink.ddl-generation set to drop-and-create-tables. But this does not work... the tables are not dropped (if they exist) and are not created (if the database is empty).
Is it possible to do the drop-and-create-tables programmatically using the JPA?
I may have another EntityManagerFactory open at the same time, which has been opened with the default options... would this be conflicting?

I don't think there is any easy way to generate the default tables once your have created the EntityManagerFactory. You could use the EclipseLink/TopLink schemaframework or TableCreator to create tables using a EclipseLink/TopLink DatabaseSession.
There is a DefaultTableGenerator in org.eclipse.persistence.tools.schemaframework, which may give you what you are looking for.
-- James : http://www.eclipselink.org

Drop and recreate table in stored procedure

Hi all
When creating tables using Transact-SQL scripts, I have always preferred to drop the table if it exists and then create it explicitly using CREATE TABLE. For two reasons:
1) It does not matter if it is the first time the SP is run ie. if I create the table manually in the first instance and just use TRUNCATE TABLE it could fail if the table is deleted
2) I have control over the data types of the table fields
Just recently though I discovered the error that can occur when dropping and creating a table in the same batch (see link below)
Microsoft Website
This causes me a problem when dropping and creating tables in stored procedures, as I understand that a stored procedure is in itself a single batch?
Can I avoid this error in a stored procedure whilst continuing to drop and create tables? Or should I be taking a different approach?
Coding best practice advice would be greatly appreciated.
Thank you

Thanks Ronen
Please see my second post immediately before your reply.
Given that I need to store the data output in a physical table for use in QlikView, would you suggest truncating the table each time the SP runs? And then having a script that handles both dropping and creating the physical table, and also creating
the SP?
>> QlikView
QlikView is an Israeli company, right?
In any case I am not familiar with QlikView's application, therefore I can only give you general information, based on assumptions regarding the application, and facts regarding the SQL Server.
>> for use in QlikView
I assume that external application use specific database structure (table
structure) and it is change only in rare situations (for example CMS interface might change the tables if and when a module s update/install). In this case there is no need to drop the table and recreate it and TRUNCATE is the solution.
>> would you suggest truncating the table each time the SP runs
I am sorry but i cant recommend on TRUNCATE a table each time you execute SP, without know the exact reason for this logic. It sound to me, at this point of time (with the information that we have), that this
is very bad logic (application architecture). As I wrote above, basing your application on TRUNCATING the table each time mean that you have problems with multi users. Thins about 2 people that try to execute the same SP at almost the same time. Think about
locking in the SQL Server and bad data (one truncate while the other already inserted the new data and get no rows, if there is no locking).
But TRUNCATE is much better in this case probably then DROP and DELETE, since it is faster, and locking will be shorter (hopefully the application use the correct locking). There are other reasons why TRUNCATE is better, and other people already mentioned
most of them, but time in this scenario might be critical.
>> having a script that handles both dropping and creating the physical table, and also creating the SP?
I do not undestand what is this second step. we said that you truncate the table, so why do you need to
dropping and creating the physical table and who
creating the SP?
Are you meaning that the application create the tables and SP?
There are lot of application that during installation create the database structure. is this what you mean?
Ronen Ariely
[Personal Site] [Blog] [Facebook]

Creating and Dropping a temporary table in Bi publisher?

Hi all.
My database is sybase.
I created a new data set in BI publisher where it creates a temporary table,
uses that temp table in a select query and then I dropped the temporary table.
I wrote all these 3 SQL statements in a single dataset.
This is executed for the first time with out any errors.
The second time I am tryiong to run the report..It says It cannot create temp table as it has one temp table with the same name.
When I execute the same query in my database (SQL developer) this works. But not working in BI publisher.
Please suggest.

I came across this thread...in this forum while looking for a solution..
Can i create temporary table with BI Publisher ?
If we have to use a data template...Does the function in data trigger necessarily needs to be a PL/SQL function? because..we donot use oracle database. we use T-SQL to write queries..

How to Drop all data in a database?

Hi There,
I'm use to dropping all the objects in a database, however, how do I drop ONLY the DATA in the database? Is all data in the database stored in tables? Do I have to TRUNCATE all the tables in the database only? Thanks in advanced.
J

You can try to:
1. disable foreign key constraints instead of dropping them.
2. truncate all tables in any order
3. enable foreign key constraints.
Short example:
SQL> truncate table parent;
truncate table parent
ERROR at line 1:
ORA-02266: unique/primary keys in table referenced by enabled foreign keys
SQL> select constraint_name, table_name from user_constraints where r_constraint_name is not null;
CONSTRAINT_NAME                TABLE_NAME
SYS_C0011060                   CHILD
JHIST_JOB_FK                   JOB_HISTORY
JHIST_EMP_FK                   JOB_HISTORY
JHIST_DEPT_FK                  JOB_HISTORY
EMP_DEPT_FK                    EMPLOYEES
EMP_JOB_FK                     EMPLOYEES
EMP_MANAGER_FK                 EMPLOYEES
DEPT_LOC_FK                    DEPARTMENTS
DEPT_MGR_FK                    DEPARTMENTS
LOC_C_ID_FK                    LOCATIONS
COUNTR_REG_FK                  COUNTRIES
11 rows selected.
SQL> alter table child disable constraint sys_c0011060;
Table altered.
SQL> truncate table parent;
Table truncated.
SQL> truncate table child;
Table truncated.
SQL> alter table child enable constraint sys_c0011060;
Table altered.
SQL>

Dropping all deployed tables in OWB 10.2.0.3.0

Similar Messages

Maybe you are looking for