Generate trigger ddl

Hi there,
How do I recreate the trigger ddl without using the "exp/imp"? I've tried the DBMS_METADATA.GET_DDL and didn't work.
Thanks

Make sure you have that trigger using user_triggers view. Becuase I see dbms_metadata works.
SQL> select dbms_metadata.get_ddl('TRIGGER','PDM_BRAND_BI') from dual;
DBMS_METADATA.GET_DDL('TRIGGER','PDM_BRAND_BI')
CREATE OR REPLACE TRIGGER "XX"."PDM_BRAND_BI"
BEFORE
INSERT
ON pdm_Message was edited by:
RPuttagunta

Similar Messages

Generating Trigger DDL using OO4O (OField::GetChunk)

WINNT 4.0SP6
MS Visual C++ 6.0 (using MFC)
Oracle 8.1.7
I'm attempting to write some C++ code that will generate the DDL of a trigger using OO4O.
Here's the code (so far):-
strSQL.Format("SELECT DESCRIPTION, TRIGGER_BODY FROM ALL_TRIGGERS WHERE OWNER = '%s' AND TRIGGER_NAME = '%s'", strOwner, strName);
dyn.Open(m_pDatabase->m_database, strSQL);
int nBuffSize = 65535;
nSize = dyn.GetFieldSize(0);
const char *pValue = strValue.GetBuffer(nSize+1);
dyn.GetFieldValue(0, (char*)pValue, nSize + 1);
strValue.ReleaseBuffer();
strText.Format("CREATE OR REPLACE %s %s", pszType, strValue);
OField fld =      dyn.GetField(1);
const char *pBuffer = NULL;
unsigned short nBytesRead = 0;
long nOffset = 0;
CString strBuff;
do
     if (fld.GetChunk(&pBuffer, nOffset, nBuffSize, &nBytesRead) != OSUCCESS)
          break;
     if (nBytesRead)
          char *p = strBuff.GetBuffer(nBytesRead);
          memcpy(p, pBuffer, nBytesRead);
          strBuff.ReleaseBuffer();
          strText += strBuff;
          nOffset += nBytesRead;
while (nBytesRead);
My problem is that the GetChunk method is failing, although it still returns OSUCCESS.
If I call OField::GetErrorText() after the GetChunk call I get the error "ROWID must be selected ..". Looking at the documentation this does make sense. That is, to access LONG type field values the ROWID must be accessible.
In this case there is no ROWID available because we are selecting from a dictionary view (ALL_TRIGGERS). Attempting to "SELECT ROWID FROM ALL_TRIGGERS" results in the error "ORA-01446: cannot select ROWID from view with DISTINCT, GROUP BY, etc.".
Can anyone out there point me in the right direction to solve this one ?
Thanks in advance.
Adrian Capp
LBS Limited, UK

Thanks for that.
Can you tell me which Dictionary Table I need to query. I've tried looking at the definition of the ALL_TRIGGERS view but was still none-the-wiser.
I agree that it's not an ideal solution, but the application in question is only going to be used internally by development personel. I could also add a check as the app starts so it will only run if connected to a specific version of Oracle (just an idea).
Adrian

Suppress auto sequence and trigger DDL for surrogate keys?

Is there a way to suppress trigger and sequence creation for surrogate keys when export to DDL file?
I know most of the time the automatic sequence and trigger creation is welcome and very handy.
However I'm migrating from an old Designer model and there only the needed sequences are created.
They have a different name and trigger logic is custom (and generated outside designer).
There is a lot of package code depending on this. So I prefer to create and use different sequences.
Is there a way to achieve this? Any tips are welcome.Create

Hi,
Note that generating the DDL for Oracle 12c means that it will attempt to use your Oracle 12c Physical model. So if you normally use Oracle 10g or 11g, you will find that any details from your Oracle 10g or 11g Physical Model will not be included. So this approach may have other implications for you.
If you are not using Oracle 12c, there are some relevant properties on the Auto Increment tab of the Relational Model properties dialog for the Column which may help:
Sequence Name - allows you to specify the name of the Sequence (which can be the name of a Sequence defined in the relevant Physical Model).
Trigger Name - allows you to specify the name of a Trigger (which can be the name of a Trigger that is defined for the Table in the Physical Model).
Generate Trigger - unsetting this will stop the Trigger being generated.
David

How to generate the DDL script of all the schema objects.

Hi All,
I just wanted to make centralized repository for Oracle database and to create a base version, I need to create the DDL scripts of all the database objects so that i can check in the same ddl scripts (sql) files in to my central repository.
I need do this schedule job which will generate the ddl scripts once in a month(This should be automated process)
Please help me out about this.
Oracle version - 9i
Thanks in advance.
Thanks,
Santosh
Edited by: Santosh_Oracle on Feb 23, 2011 10:26 PM

It is definitely possible to revise the script.
Look at it, you already have 80 percent of it for free, and you didn't even need to Google.
Just ask a FAQ in a forum loaded with FAQs!
And Toad can save everything to one script per object.
Sybrand Bakker
Senior Oracle DBA

Delete rule not being generated in DDL

Hi,
I've only recently started using SQL Developer Data Modeler (coming from the Designer world), and it's been a good learning experience. There's a piece that I can't seem to figure out though, and it's related to the generation of DDL for foreign keys. In all my models (logical, relational, physical, I have the Delete Rule set to "Restrict". This isn't just the default preference I'm talking about, when I actually drill down to the properties of the FK, it says that the delete rule is restrict. However, when I generate the DDL, no delete rule is generated. The only option generated is NOT DEFERRABLE.
There are two issues with this:
1) The rule isn't going into the DB unless I manually alter the DDL, and
2) Every time I re-import the DB to generate ALTER statements, the comparison detects that the rule in the DB (NO ACTION) is different than the rule in the model (RESTRICT), so it deletes and re-generates the FK. However, it re-generates it still not having the delete rule set, so it doesn't fix the problem.
Is this a known bug, or is there some way of telling the program to generate the delete rule in DDL that I'm missing? I should add I'm using version 3.1.1.703.
Thanks in advance for your help.
Mike
Edited by: user10832262 on Apr 12, 2012 9:53 AM

I did some more research and I think I was completely misunderstanding Oracle's implementation of delete rules. Now I believe that Oracle implements the "RESTRICT" option in SQL Developer Data Modeler as "No Action", which is the default option, hence why no DDL option is generated. However, it would still be nice if Data Modeler could detect this fact when comparing two models. What I mean it, if comparing an Oracle DB to a model, treat Restrict and No Action as the same, and thus don't attempt to re-generate the DDL for this "difference". For now, I'll just change the action on my models to No Action, and this should resolve the issue.

How do you get a list of all the trigger DDLs?

I want to get a list of all the DB trigger DDLs of owner 'ABS'. I want to do it using 1 SQL statement.
This is what I ran:
SELECT
TO_CHAR(DBMS_METADATA.GET_DDL('TRIGGER', TRIGGER_NAME, 'ABS'))
FROM
ALL_TRIGGERS
WHERE
OWNER = 'ABS';
I get this error: [1]:
(Error): ORA-22835: Buffer too small for CLOB to CHAR or BLOB to RAW conversion (actual: 4414, maximum: 4000)
Then I looked up in the web and they ask to use DBMS_LOB.SUBSTR instead. So I do that:
SELECT
DBMS_LOB.SUBSTR(DBMS_METADATA.GET_DDL('TRIGGER', TRIGGER_NAME, 'ABS'), 32767, 1)
FROM
ALL_TRIGGERS
WHERE
OWNER = 'ABS';
Now I get this error:
[1]: (Error): ORA-06502: PL/SQL: numeric or value error: character string buffer too small ORA-06512: at line 1
Looks like you cannot show more than *4000* chars. There are 43 triggers whose DDL is more than 4000 chars long.
Why is this?
How can I solve my problem?
Edited by: Channa on Feb 16, 2010 9:45 PM

Herald, fantastic news. SET LONG did the trick.
But I had to put a very big value. 32000 was not enough. Otherwise some of the triggers (big ones) got cut off.
This is my complete code which did it.
SPOOL F:\Channa\zz_zzTemp\Binuka\OutPut.txt
set trimspool on
set pages 0
set long *1000000000*
set linesize 32767
SET TERMOUT OFF
SELECT DBMS_METADATA.GET_DDL('TRIGGER', TRIGGER_NAME, 'ABS')
FROM ALL_TRIGGERS
WHERE OWNER = 'ABS' AND trigger_name NOT LIKE 'BIN$%'
SPOOL OUT
THANKS A LOT. REALLY APPRECIATE IT.
P.S: I had to include the NOT LIKE 'BIN$%' in the where clause because otherwise I got this error:
ERROR:
ORA-31603: object *"BIN$cqXDSqghrFngQKjAJAovgw==$0"* of type TRIGGER not found in
schema "ABS"
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 105
ORA-06512: at "SYS.DBMS_METADATA", line 2805
ORA-06512: at "SYS.DBMS_METADATA", line 4333
ORA-06512: at line 1
no rows selected
I THINK BIN$... triggers are dropped triggers in the DB recycle bin???
Edited by: Channa on Feb 17, 2010 2:58 AM
Edited by: Channa on Feb 17, 2010 3:01 AM

SQl Developer 3.0.04 Revoke doesn't generate any DDL. Bug?

Hi everyone,
trying Revoke while rightclicking on , e.g. a stored function doesn't generate any DDL. Specifically, opening "Perform Revoke Action", selecting the Properties tab and applying the desired action doesn't do anything. Interestingly enoguh, selecting the "SQL" tab shows no generated DDL no matter what properties were set. It looks to me as another bug. Any thoughts.
Cheers,
Bob

Hi Bob,
The SQL tab will remain empty until the privileges to be revoked have been selected. In the properties tab of the revoke dialog, the drop down list for "Users" contains a list of those users for which privileges on the object have been granted. (If this list is empty then you will need to do some grants first!) Select a user. You should now see some privilege names in the right hand side of the shuttle. Shuttle one or more of these to the left pane. You should now see generated SQL in the SQL tab.
Please let me know if this doesn't resolve the problem for you.
Best regards,
Philip Richens
SQLDev Development Team

Mappingtool generates bad DDL for sybase (J2ee tutorial)

Running the mappingtool on the J2EE tutorial app (3.0.0RC1) generates bad
DDL for sybase. It's trying to create a table with a column of type
"IndexName":
C:\devtools\kodo\samples\j2ee>mappingtool -a refresh package.jdo
0 INFO [main] kodo.Tool - Mapping tool running on type "class
samples.j2ee.Car" with action "refresh".
0 INFO [main] kodo.Tool - The tool is now reading existing schema
information; this process may take some time. En
able the kodo.jdbc.Schema logging category to see messages about schema
data. Also see the -readSchema tool flag.
3716 INFO [main] kodo.Tool - Recording mapping and schema changes.
Exception in thread "main" kodo.util.FatalException:
com.solarmetric.jdbc.ReportingSQLException: Can't specify a length
or scale on type 'IndexName'.
{stmnt 7576378: CREATE TABLE CAR (COLOR IndexName(255) NULL, JDOCLASS
IndexName(255) NULL, JDOID NUMERIC(38) NOT NULL,
JDOVERSION INT NULL, MAKE IndexName(255) NULL, MODEL IndexName(255) NULL,
YEAR0 IndexName(255) NULL, UNQ_INDEX NUMERIC I
DENTITY UNIQUE, CONSTRAINT P_CAR PRIMARY KEY (JDOID))} [code=2716,
state=ZZZZZ]
NestedThrowables:
com.solarmetric.jdbc.ReportingSQLException: Can't specify a length or
scale on type 'IndexName'.
{stmnt 7576378: CREATE TABLE CAR (COLOR IndexName(255) NULL, JDOCLASS
IndexName(255) NULL, JDOID NUMERIC(38) NOT NULL,
JDOVERSION INT NULL, MAKE IndexName(255) NULL, MODEL IndexName(255) NULL,
YEAR0 IndexName(255) NULL, UNQ_INDEX NUMERIC I
DENTITY UNIQUE, CONSTRAINT P_CAR PRIMARY KEY (JDOID))} [code=2716,
state=ZZZZZ]
at kodo.jdbc.meta.MappingTool.record(MappingTool.java:431)
at kodo.jdbc.meta.MappingTool.run(MappingTool.java:790)
at kodo.jdbc.meta.MappingTool.main(MappingTool.java:729)
NestedThrowablesStackTrace:
com.solarmetric.jdbc.ReportingSQLException: Can't specify a length or
scale on type 'IndexName'.
{stmnt 7576378: CREATE TABLE CAR (COLOR IndexName(255) NULL, JDOCLASS
IndexName(255) NULL, JDOID NUMERIC(38) NOT NULL,
JDOVERSION INT NULL, MAKE IndexName(255) NULL, MODEL IndexName(255) NULL,
YEAR0 IndexName(255) NULL, UNQ_INDEX NUMERIC I
DENTITY UNIQUE, CONSTRAINT P_CAR PRIMARY KEY (JDOID))} [code=2716,
state=ZZZZZ]
at
com.solarmetric.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:67)
at
com.solarmetric.jdbc.LoggingConnectionDecorator.access$400(LoggingConnectionDecorator.java:19)
at
com.solarmetric.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingStatement.executeUpdate(LoggingConne
ctionDecorator.java:506)
at
com.solarmetric.jdbc.DelegatingStatement.executeUpdate(DelegatingStatement.java:125)
at kodo.jdbc.schema.SchemaTool.executeSQL(SchemaTool.java:1042)
at kodo.jdbc.schema.SchemaTool.createTable(SchemaTool.java:803)
at kodo.jdbc.schema.SchemaTool.add(SchemaTool.java:334)
at kodo.jdbc.schema.SchemaTool.add(SchemaTool.java:186)
at kodo.jdbc.meta.MappingTool.record(MappingTool.java:364)
at kodo.jdbc.meta.MappingTool.run(MappingTool.java:790)
at kodo.jdbc.meta.MappingTool.main(MappingTool.java:729)
Anyone else seen this? It works ok with Hypersonic (though i can't get the
tutorial app to run with hypersonic - see my earlier post).
Alex.

Some bugs in RCs sometimes don't make it into Bugzilla as it is a
release candidate and not production quality.
I would reocmmend upgrading as it fixes a number of major bug fixes and
you should be able to use the same eval key.
Alex Robbins wrote:
Abe White wrote:
I should also have asked: what JDBC driver are you using?Hi Abe,
I haven't tried with RC2 - has this been fixed in RC2? I didn't find this
bug on bugzilla.
I'm using Sybase JConnect JDBC driver (com.sybase.jdbc2.jdbc.SybDriver in
jconn2.jar) - looks like this is the version:
jConnect (TM) for JDBC(TM)/5.5(Build 25008)/P/JDK12/Tue May 29 14:37:46
2001
Should I upgrade from RC1 to RC2, and if so, can I continue to use the
same eval license key or can i download a new one?
thanks,
alex
Stephen Kim
[email protected]
SolarMetric, Inc.
http://www.solarmetric.com

Delete rule not generated in DDL

Hello,
I am using SQL Developer Data Modeler (Version 3.1.1.703) and experience the following issue:
I have a table with a foreign key and a delete rule "SET NULL". However if I generate the DDL for "SQL Server 2005" then the rule is not there. Only if I change the rule to "CASCADE" then it is generated properly. Is that a bug or am I missing something?
Thanks in advance for your help,
Michael

Hi Philip,
when can we expect a fix for that since it is kind of an important function for us because without it we can't export a valid database structure.
Thanks in advance,
Michael

How to generate incrementel DDL.

I'm an old Designer user and I appreciated very much the capability to generate incremental DDL agains a real Database.
Is it possible with SDDM ?
How?
Tks
Tullio

Hi Tullio,
Yes. It can be done by first opening your model in Data Modeler. Then use the Data Dictionary Import Wizard to import your current definitions from the database (using the "Swap target model" option in step 2) and when this shows the Compare Models dialog, use the DDL Preview button to generate the incremental DDL.
For more detail, I suggest you read this earlier message on this forum: Re: Generate DDL - change is a new column and I want to generate a alter table
David

Schematool createDB can't generate the ddl

Hi,
I am trying to run the schematool to generate the ddl to re-create the
current DB - according to the doc, I should run :
schematool -a createDB -f sql.txt
However, when I run it (after put some CLASSPATH setting before the java
execute), it gives me following exception (Note: the first line is the
output of "echo $CLASSPATH"):
[tyang@zetus UMA]$ ./schematool -a createDB -f tmp.ddl
/usr/java/jsdk/ext/JMF-2.1.1e/lib/jmf.jar:/usr/java/jsdk/ext/JMF-2.1.1e/lib/sound.jar:.:lib/commons-beanutils.jar:lib/commons-collections.jar:lib/commons-dbcp.jar:lib/commons-digester.jar:lib/commons-lang.jar:lib/commons-logging.jar:lib/commons-pool.jar:lib/cwlicense.jar:lib/db2java.jar:lib/db2j.jar:lib/jakarta-regexp.jar:lib/jaxen-full.jar:lib/jca1.0.jar:lib/jcommon-0.8.8.jar:lib/jdo-1.0.1.jar:lib/jdom.jar:lib/jfreechart-0.9.13.jar:lib/jndi.jar:lib/jta-spec1_0_1.jar:lib/kodo-jdo.jar:lib/kodo-jdo-runtime.jar:lib/license.jar:lib/log4j-1.2.8.jar:lib/msbase.jar:lib/mssqlserver.jar:lib/msutil.jar:lib/ojdbc14.jar:lib/pg72jdbc2.jar:lib/saxpath.jar:lib/servlet.jar:lib/sqlline.jar:lib/tjdo.jar:lib/xalan.jar:lib/xercesImpl.jar:lib/xml-apis.jar:build/classes:build/jdometa-dtd
Exception in thread "main" java.lang.NullPointerException
at org.postgresql.jdbc2.ResultSet.getBytes(ResultSet.java:321)
at
org.postgresql.jdbc2.DatabaseMetaData.getIndexInfo(DatabaseMetaData.java:2942)
at
com.solarmetric.jdbc.DelegatingDatabaseMetaData.getIndexInfo(DelegatingDatabaseMetaData.java:253)
at
com.solarmetric.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingDatabaseMetaData.getIndexInfo(LoggingConnectionDecorator.java:321)
at
com.solarmetric.jdbc.DelegatingDatabaseMetaData.getIndexInfo(DelegatingDatabaseMetaData.java:253)
at kodo.jdbc.sql.DBDictionary.getIndexInfo(DBDictionary.java:2921)
at
kodo.jdbc.schema.SchemaGenerator.generateIndexes(SchemaGenerator.java:568)
at
kodo.jdbc.schema.SchemaGenerator.generateIndexes(SchemaGenerator.java:577)
at
kodo.jdbc.schema.SchemaGenerator.generateIndexes(SchemaGenerator.java:357)
at
kodo.jdbc.schema.SchemaGenerator.generateSchemas(SchemaGenerator.java:188)
at
kodo.jdbc.schema.SchemaGenerator.generateSchemas(SchemaGenerator.java:168)
at
kodo.jdbc.schema.SchemaTool.getDBSchemaGroup(SchemaTool.java:1062)
at kodo.jdbc.schema.SchemaTool.createDB(SchemaTool.java:293)
at kodo.jdbc.schema.SchemaTool.run(SchemaTool.java:1383)
at kodo.jdbc.schema.SchemaTool.run(SchemaTool.java:1317)
at kodo.jdbc.schema.SchemaTool.main(SchemaTool.java:1267)
Any clue ?
Thanks,
Tao

It does appear to be a driver bug, and it looks like it is fixed in
recent versions of the Postgres JDBC driver. See:
http://archives.postgresql.org/pgsql-jdbc/2002-02/msg00179.php
In article <brsrnl$4q0$[email protected]>, Abe White wrote:
>
Exception in thread "main" java.lang.NullPointerException
at org.postgresql.jdbc2.ResultSet.getBytes(ResultSet.java:321)
at
org.postgresql.jdbc2.DatabaseMetaData.getIndexInfo(DatabaseMetaData.java:2942)
As you can see, this is a postgres error, so it's difficult to know what
is going on. Are you using Postgre's own 7.2 driver?--
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com

Conn generating link ddl but schema in same database

i have a connector which associates 2 locations in the same database. when i deploy the connector, it generates link ddl. when i deploy my mapping it uses that link. i can't get the mapping to generate schema.table_name.
any help would be appreciated.
i've searched the forum and gone through the docs. i don't know what i'm doing wrong.

Chandra,
Such document is always one and the same with all Oracle products - a User Guide that ships with a product and is available online http://www.oracle.com/technology/documentation/warehouse.html The User Guide is searchable and indexed. Look up "register locations" and you'll find "Registering Locations" section in Chapter 13 (of OWB 10g User Guide) with step-by-step instructions.
Nikolai Rochnik

"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.

On commit for mview refresh is not generated in DDL

New design > relational > new table w/ single numeric column
New Oracle 11g physical > new materialized view > on prebuilt table from above > Refresh Clause tab > select ON COMMIT action
-- add a body for grins
resulting XML in saved design:
<?xml version = '1.0' encoding = 'UTF-8'?>
<SnapshotOraclev11g class="oracle.dbtools.crest.model.design.storage.oracle.v11g.SnapshotOraclev11g" name="TABLE_1" id="E092B588-B0A8-437A-4187-9999090405D9" directorySegmentName="seg_0">
<createdBy>kdavis1</createdBy>
<createdTime>2012-07-18 15:28:57 UTC</createdTime>
<ownerDesignName>OTN_Issue_20120717a</ownerDesignName>
<action>ON COMMIT</action>
<defaultSegment>NO</defaultSegment>
<onPrebuiltTable>8332B16F-E06B-86AC-E123-DDA4F5DFF794</onPrebuiltTable>
</SnapshotOraclev11g>
Resulting DDL lacks ON COMMIT:
-- Generated by Oracle SQL Developer Data Modeler 3.1.1.703
-- at: 2012-07-18 11:47:26 EDT
-- site: Oracle Database 11g
-- type: Oracle Database 11g
CREATE TABLE "TABLE_1"
"Column_1" NUMBER
LOGGING
CREATE MATERIALIZED VIEW "TABLE_1"
ON PREBUILT TABLE
AS select sum(foo) from bar
-- Oracle SQL Developer Data Modeler Summary Report:
-- CREATE TABLE 1
-- CREATE INDEX 0
-- ALTER TABLE 0
-- CREATE VIEW 0
-- CREATE PACKAGE 0
-- CREATE PACKAGE BODY 0
-- CREATE PROCEDURE 0
-- CREATE FUNCTION 0
-- CREATE TRIGGER 0
-- ALTER TRIGGER 0
-- CREATE STRUCTURED TYPE 0
-- CREATE COLLECTION TYPE 0
-- CREATE CLUSTER 0
-- CREATE CONTEXT 0
-- CREATE DATABASE 0
-- CREATE DIMENSION 0
-- CREATE DIRECTORY 0
-- CREATE DISK GROUP 0
-- CREATE ROLE 0
-- CREATE ROLLBACK SEGMENT 0
-- CREATE SEQUENCE 0
-- CREATE MATERIALIZED VIEW 1
-- CREATE SYNONYM 0
-- CREATE TABLESPACE 0
-- CREATE USER 0
-- DROP TABLESPACE 0
-- DROP DATABASE 0
-- ERRORS 0
-- WARNINGS 0
Posts reviewed: (materialized && view) || mview || mv

Yes but then shouldn't "Refresh Type" be blank (instead of FAST) like "Refresh Action" is blank by default.
Or better yet, you already fill the mview name upon selection of a table for on prebuilt -- so should you select refresh YES upon choosing a type and/or action?
Seems to be an inconsistency here.

Error while generating trigger

The Triggers PL-SQL code generated is as follows
create trigger GROUPS_INS_TRIG before insert on GROUPS for each row begin select GBO_attr_SEQ.nextval into :new.GES_NUMBER from dual; end;;
the last ; is not waited by the compiler.
One way of coping is to copy the code in SQL worsheet and to manually correct and execute again. But it slows down the design process.

I just had this error:
DROP TABLE USERS CASCADE CONSTRAINTS;
drop sequence GBO_attr_SEQ;
create sequence GBO_attr_SEQ start with 1;
create table USERS ( GES_NUMBER NUMBER,NAME VARCHAR2(255) CONSTRAINT USERSGBO_NAME_CHECK NOT NULL,CREATOR VARCHAR2(255) CONSTRAINT USERSGBO_CREATOR_CHECK NOT NULL,OWNER VARCHAR2(255) CONSTRAINT USERSGBO_OWNER_CHECK NOT NULL,CREATION_DATE DATE CONSTRAINT USERSGBO_CREATION_DATE_CHECK NOT NULL,UPDATE_DATE DATE,UPDATE_BY VARCHAR2(255),FAMILY_NAME VARCHAR2(255) CONSTRAINT USERS_FAMILY_NAME_CHECK NOT NULL,FIRST_NAME VARCHAR2(255),COMPANY_EMAIL VARCHAR2(255),PICTURE ORDSYS.ORDIMAGE,DESKTOP_WALL_PAPER ORDSYS.ORDIMAGE,LOCATION VARCHAR2(255),OFFICE_LOCALISATION VARCHAR2(255),ACTIVE NUMBER CONSTRAINT USERS_ACTIVE_CHECK NOT NULL,PHONE_NUMBER VARCHAR2(255),PERSONNAL_PHONE_NUMBER VARCHAR2(255),COMPANY_CELL_PHONE VARCHAR2(255),PERSONNAL_CELL_PHONE VARCHAR2(255),PERSONNAL_EMAIL VARCHAR2(255),ATTR VARCHAR2(255),CURRENT_DEFAULT_DESKTOP_DIRECT VARCHAR2(255),DEFAULT_SERVER_DIRECTORY VARCHAR2(255),CURRENT_DEFAULT_SERVER_DIRECTO VARCHAR2(255),GBO_GES_NUMBER NUMBER CONSTRAINT SYS_C0015300 NOT NULL,ROLE NUMBER,COMPANY VARCHAR2(255),COMPANY_RESORT VARCHAR2(255));
ALTER TABLE USERS ADD ( CONSTRAINT USERSGBO_PRIMARY_KEY PRIMARY KEY (GES_NUMBER));
ALTER TABLE USERS ADD ( CONSTRAINT USERSGBO_UNIQUE_KEY UNIQUE (NAME));
create trigger USERS_INS_TRIG before insert on USERS for each row begin select GBO_attr_SEQ.nextval into :new.GES_NUMBER from dual; end;;
ALTER TABLE USERS ADD ( CONSTRAINT FK_USERS FOREIGN KEY (GBO_GES_NUMBER) REFERENCES GROUPS(GES_NUMBER));
ALTER TABLE USERS ADD ( CONSTRAINT FK_USERS1 FOREIGN KEY (GBO_GES_NUMBER) REFERENCES COMPANIES(GES_NUMBER));
ALTER TABLE USERS ADD ( CONSTRAINT FK_USERS12 FOREIGN KEY (GBO_GES_NUMBER) REFERENCES ENTITY_OBJECT1(null));
ALTER TABLE USERS ADD ( CONSTRAINT FK_USERS13 FOREIGN KEY (GBO_GES_NUMBER) REFERENCES LOCATIONS(null));
LINE/COL ERROR
1/71 PLS-00103: Symbole ";" rencontré
It looks like the code can't be used like that without two ;. If you remove one you get some answer like that
Erreurs pour TRIGGER USERS_INS_TRIG :
LINE/COL ERROR
3/1 PLS-00103: Symbole "ALTER" rencontré
The solution is to isolate the line, erase the second semi-colon and add an "or replace" at the beginning.
It works but it's a bit heavy.

Generate trigger ddl

Similar Messages

Maybe you are looking for