Create selection table

Hi guys,.

There I am facing a problem I need to create the table in the select statement result 0 records as output.

Sue, the error displayed is:

SQL error: ORA-01723: columns null are not allowed

01723 00000 - "columns null are not allowed.

* Cause: Columns with a length zero could not.

* Action: Correct use of the column.

no selected line

Can you please suggest a way?

I need to create several tables like that of the select statement.

As Johan has picked up on, if the VEL_CEM_ALL_CONTENT is a point of view, then the data types will be those of the columns returned in the select from this point of view, and if one of those is null then you will get the error.

Tags: Database

Similar Questions

Could not commit: ORA-00928: lack of creating the table SELECT keyword
Hello guys.
I tried to create the table with web interface on oracle 11g.

I just follow this path on interface: schema-> table-> create-> standard (lot organized)-> SQl select on (set using the)->
and I just use these scripts to create the table:

CREATE TABLE suppliers
(the number (10) of supplier_id not null,)
supplier_name varchar2 (50) not null,
Contact_Name varchar2 (50)
);

but this error occurred: failed to commit: ORA-00928: lack of SELECT key word!
Please lock on this picture for more information: http://s17.postimg.org/kgoumzmvz/attachment.jpg

could you help me please?
and I could not find any manual for working with the web interface in oracle 11g.
Please give me somesources to start.
Thank you.
1003778 wrote:
Thank you sybrand_b
but I already read this document.
Unfortunately, there is nothing on the creation of table with sql scripts in this document!

and I really don't understand how to create table with SQL commands! My question has not yet been answered.
you please give me little details about it?
for example, how can create table using this sql command:

CREATE TABLE suppliers
(the number (10) of supplier_id not null,)
supplier_name varchar2 (50) not null,
Contact_Name varchar2 (50)
);

Thank you.

Edited by: 1003778 may 3, 2013 11:43

When you got to the CREATE TABLE screen, you have selected "set using the--> SQL.
Did you notice in the window that appears, just above this entry field is this text: "enter a SQL * select * statement below.» ' + This query results will be used to fill the table with Canada.* + "(underlining)
And hip, just to the left of this field is this text: «CREATE TABLE AS»

He tries to build a ' CREATE TABLE AS SELECT... ». Creates a table with the same structure as the table in which you SELECT and fills with the results of this SELECT '. With your entry, you create a CREATE TABLE AS CREATE TABLE to read statement...

If you want to create your tables with a simple CREATE TABLE command, go to sqlplus and do it. You want to have a graphical interface to help build a simple CREATE table, when you get to the CREATE TABLE page, just to stay there with the default "use Define-> column specification." If you want, after completing "build" your table specification here, you will have a "Show sql" option to show you the actual sql statement that will be executed to create your table.

Create the table in select * from the other table
DB: 11.2.0.2

How to create a table with structure only not empty the data that we do not generally create table in select * from... But the command will pull the data also. How to create without data?
create table foo
in select * bar
where 1 = 0

create the table in SELECT (question)

Hello

In regards to create the table as subquery, I read that:

The data type of column definitions and the NOT NULL constraint are passed to the new table. Note that only the explicit NOT NULL constraint is inherited. The PRIMARY KEY column will not function NOT NULL column null. Any other rule of constraint is not passed to the new table. However, you can add constraints in the column definition.

Can someone explain to me how to do this? Or, how we need to specify the constraints (and also the default values for columns, because it is possible) for the columns in the column definition?

In addition, I do not understand this: the PRIMARY KEY column will not function NOT NULL column zero.
Can someone give me some small examples regarding these?
For example, it generates an error:

create table test1 (a, b, c default sysdate) 
as 
select 1, 'b' from dual

Thank you!

Edited by: Roger22 the 01.09.2011 11:37

Hello

When you set a primary key consists of a unique constraint and a constraint not null, but they are both implicit with the primary key. When you create the table because it will copy only the explicitly declared NOT NULL constraints so it isn't look upward than the implicit NOT NULL primary key.

SQL> create table dt_pk
  2  (   id      number primary key,
  3      col1    number not null,
  4      col2    number
  5  )
  6  /

Table created.

SQL> desc dt_pk
 Name                                      Null?    Type
 ----------------------------------------- -------- ----------------------------
 ID                                        NOT NULL NUMBER
 COL1                                      NOT NULL NUMBER
 COL2                                               NUMBER

SQL> create table dt_pk2 as select * from dt_pk;

Table created.

SQL> desc dt_pk2;
 Name                                      Null?    Type
 ----------------------------------------- -------- ----------------------------
 ID                                                 NUMBER
 COL1                                      NOT NULL NUMBER
 COL2                                               NUMBER

SQL> select constraint_name,constraint_type from user_constraints where table_name='DT_PK'
  2  /

CONSTRAINT_NAME                C
------------------------------ -
SYS_C006935772                 C
SYS_C006935773                 P

SQL> select constraint_name,constraint_type from user_constraints where table_name='DT_PK2'
  2  /

CONSTRAINT_NAME                C
------------------------------ -
SYS_C006935774                 C

However, a primary key can reuse existing constraints and indexes instead of declaring new. For example, we can explicitly declare a constraint not null on the column id and then create a primary key. This means that we will now inherit the constraint not null in the ETG, as it has been explicitly declared and is a constraint separate in there own right that has been 'borrowed' by the pk constraint.

SQL> create table dt_pk3 (id number not null, col1 number not null, col2 number);

Table created.

SQL> alter table dt_pk3 add constraint dt_pk3_pk primary key (id);

Table altered.

SQL> select constraint_name,constraint_type from user_constraints where table_name='DT_PK3'
  2  /

CONSTRAINT_NAME                C
------------------------------ -
SYS_C006935775                 C
SYS_C006935776                 C
DT_PK3_PK                      P

SQL> create table dt_pk4 as select * from dt_pk3;

Table created.

SQL> desc dt_pk3;
 Name                                      Null?    Type
 ----------------------------------------- -------- ----------------------------
 ID                                        NOT NULL NUMBER
 COL1                                      NOT NULL NUMBER
 COL2                                               NUMBER

SQL> desc dt_pk4;
 Name                                      Null?    Type
 ----------------------------------------- -------- ----------------------------
 ID                                        NOT NULL NUMBER
 COL1                                      NOT NULL NUMBER
 COL2                                               NUMBER

Regarding the definition of the default values, you must always specify the column in the select, but doing so means follow you the semantics of a default in a standard INSERT statement, i.e. you specified the column, you must provide a value, in which case even if the value is null, the default value will not be used. However, the new inserted rows where the column with the default value is not specified will revert to the default.

SQL> create table test1 (a, b, c default sysdate)
  2  as
  3  select 1, 'b' from dual
  4  /
create table test1 (a, b, c default sysdate)
                    *
ERROR at line 1:
ORA-01730: invalid number of column names specified

SQL> create table test1 (a, b, c default sysdate)
  2  as
  3  select 1, 'b', null c from dual
  4  /
select 1, 'b', null c from dual
               *
ERROR at line 3:
ORA-01723: zero-length columns are not allowed

SQL> create table test1 (a, b, c default sysdate)
  2  as
  3  select 1, 'b', cast(null as date) c from dual
  4  /

Table created.

SQL> select * from test1;

         A B C
---------- - ---------
         1 b

SQL> insert into test1(a,b) values(2,'b');

1 row created.

SQL> select * from test1;

         A B C
---------- - ---------
         1 b
         2 b 01-SEP-11

To create a constraint, you must list all columns without the data types and constraints list online.

SQL> create table dt_cons (id number, col1 number, col2 number, constraint chk2 check(col2 IS NULL or col2>10))
  2  as select * from dt_pk3
  3  /
create table dt_cons (id number, col1 number, col2 number, constraint chk2 check(col2 IS NULL or col2>10))
                      *
ERROR at line 1:
ORA-01773: may not specify column datatypes in this CREATE TABLE

SQL> create table dt_cons (constraint chk2 check(col2 IS NULL or col2>10))
  2  as select * from dt_pk3
  3  /
create table dt_cons (constraint chk2 check(col2 IS NULL or col2>10))
                     *
ERROR at line 1:
ORA-00904: : invalid identifier

SQL> create table dt_cons (col2 constraint chk2 check(col2 IS NULL or col2>10))
  2  as select * from dt_pk3
  3  /
create table dt_cons (col2 constraint chk2 check(col2 IS NULL or col2>10))
                      *
ERROR at line 1:
ORA-01730: invalid number of column names specified

SQL> create table dt_cons (id,col1,col2 constraint chk2 check(col2 IS NULL or col2>10))
  2  as select * from dt_pk3
  3  /

Table created.

SQL> desc dt_cons
 Name                                      Null?    Type
 ----------------------------------------- -------- ----------------------------
 ID                                        NOT NULL NUMBER
 COL1                                      NOT NULL NUMBER
 COL2                                               NUMBER

SQL> insert into dt_cons values(2,2,2);
insert into dt_cons values(2,2,2)
*
ERROR at line 1:
ORA-02290: check constraint (JJACOB_APP.CHK2) violated

SQL> insert into dt_cons values(2,2,10);
insert into dt_cons values(2,2,10)
*
ERROR at line 1:
ORA-02290: check constraint (JJACOB_APP.CHK2) violated

SQL> insert into dt_cons values(2,2,11);

1 row created.

SQL> insert into dt_cons values(2,2,null);

1 row created.

SQL>

HTH

David

error on 'create a table in select... '. "table with nested columns

My Oracle 11.1 database, I have a problem with the nested table.

on table with script

CREATE TABLE TXV.IS_PODACI209
(
  ID_OBJEKTA_IDENTIFIKACIJA  NUMBER(10),
  ID_OBJEKTA                 NUMBER(20),
  DATUM                      TIMESTAMP(6),
  TZ                         NUMBER(3),
  DATA1                      NUMBER(10),
  DATA2                      NUMBER(6),
  DATA3                      NUMBER(10),
  DATA4                      NUMBER,
  DATA5                      TXV.T_NTCIP_ILLUM_TABLE,
  DATA6                      NUMBER(10)
)
NESTED TABLE DATA5 STORE AS IS_PODACI209_STORE_TABLE
TABLESPACE TXV_DATA
PARTITION BY RANGE (DATUM)
(  
  PARTITION P_201012 VALUES LESS THAN (TIMESTAMP' 2011-01-01 00:00:00')
    LOGGING
    NOCOMPRESS 
    TABLESPACE TXV_DATA,  
  PARTITION P_MAXVALUE VALUES LESS THAN (MAXVALUE)
    LOGGING
    NOCOMPRESS 
    TABLESPACE TXV_DATA
)
NOCOMPRESS 
NOCACHE
NOPARALLEL
MONITORING;


CREATE INDEX TXV.IDX_IS_PODACI209_KOMPLEKS ON TXV.IS_PODACI209
(ID_OBJEKTA_IDENTIFIKACIJA, ID_OBJEKTA, DATUM)
  TABLESPACE TXV_DATA
LOCAL (  
  PARTITION P_201012
    LOGGING
    NOCOMPRESS 
    TABLESPACE TXV_DATA,  
  PARTITION MAXX
    LOGGING
    NOCOMPRESS 
    TABLESPACE TXV_DATA
)
NOPARALLEL;

that has a nested type column:

CREATE OR REPLACE TYPE TXV.t_ntcip_ILLUM_FMT as object
(  BRIGHTNESS_LEVEL FLOAT
,   PHOTOCELL_DOWN   FLOAT
,   PHOTOCELL_UP  FLOAT
);

and I create a table (to copy table partitions in a third table) step to help:

CREATE TABLE TXV.IS_PODACI209_STAGE NESTED TABLE DATA5 STORE AS IS_PODACI209_STAGE_1 AS SELECT * FROM TXV.IS_PODACI209 WHERE 1=2

The problem is when I try to move using the partition:

ALTER TABLE TXV.IS_PODACI209 EXCHANGE PARTITION P_201012 WITH TABLE IS_PODACI209_STAGE EXCLUDING INDEXES WITHOUT VALIDATION UPDATE GLOBAL INDEXES

I get an error:

ALTER TABLE TXV.IS_PODACI209
  EXCHANGE PARTITION P_201012
  WITH TABLE IS_PODACI209_STAGE
  EXCLUDING INDEXES
  WITHOUT VALIDATION
  UPDATE GLOBAL INDEXES
Error at line 3
ORA-00604: error occurred at recursive SQL level 1
ORA-00932: inconsistent datatypes: expected NUMBER got BINARY

but these tables are the same...

someone had such a problem?

concerning

I think the UPDATE GLOBAL INDEXES is the origin of the problem.

Try this,

ALTER TABLE IS_PODACI209 EXCHANGE PARTITION P_201012 WITH TABLE IS_PODACI209_STAGE EXCLUDING INDEXES WITHOUT VALIDATION

Rebuild the indexes manually.

And if I see your profile, you

Messages total: 25
Total issues: 16 (* 14 pending *)

Always mark a thread as answered once you get the answer. It can save a lot of time for volunteers.

creating a table from a select statement
is it possible to run a select statement that creates a table based on the statement of execution? in MSSQL I can include 'in {tablename}"in a select statement and it will automatically create the table field names / on the fly?

I know I can run "insertion in {tablename} select * from foo" to fill an existing table, but I want something that creates the table as well.
```
create table 
as select ...
```
Is that what you are looking for?

Nicolas.

Trying to create the table using Clause any Union with Select multiple stmts
The motion seeks to get the substring of the value to for example.
If the value is * ASA 2 * then so do ASA
where as if the value is * 1.5 TST * it sholud come as TST as wise for others too.
I am trying to execute stmt SQL written but in error as below:

* ' ORA-00998 must appoint this expression with the alias column 00998.00000 - must appoint this expression with the column alias. "

CREATE TABLE TEST_CARE AS
(
SELECT row_id, old_care_lvl, SUBSTR(old_care_lvl,3), len test_care_lvl FROM
WHERE LENGTH (old_care_lvl) = 5
UNION ALL
SELECT row_id, old_care_lvl, SUBSTR(old_care_lvl,3), len test_care_lvl FROM
WHERE LENGTH (old_care_lvl) = 7
UNION ALL
SELECT row_id, old_care_lvl, SUBSTR(old_care_lvl,3), len test_care_lvl FROM
WHERE LENGTH (old_care_lvl) = 14
UNION ALL
Row_id SELECT, old_care_lvl, SUBSTR (old_care_lvl, 3), LEN test_care_lvl
WHERE LENGTH = 7 AND old_care_lvl (old_care_lvl) = "Regular."
);

I want to create the table using the above given the multiple selection by using the Union ALL clause, but trying to create run query error like "ORA-00998 must appoint this expression with the alias column 00998.00000 - must appoint this expression with the column alias.

Please guide me how to approach to solve this problem.
Thanks in advance.
Try this->
```
CREATE TABLE TEST_CARE
AS
  select *
  from (
          SELECT row_id, old_care_lvl,SUBSTR(old_care_lvl,3), len FROM test_care_lvl
          WHERE LENGTH(old_care_lvl) =5
          UNION ALL
          SELECT row_id, old_care_lvl,SUBSTR(old_care_lvl,3), len FROM test_care_lvl
          WHERE LENGTH(old_care_lvl) =7
          UNION ALL
          SELECT row_id, old_care_lvl,SUBSTR(old_care_lvl,3), len FROM test_care_lvl
          WHERE LENGTH(old_care_lvl) =14
          UNION ALL
          SELECT row_id, old_care_lvl,SUBSTR(old_care_lvl,3),LEN FROM test_care_lvl
          WHERE LENGTH(old_care_lvl) =7 AND old_care_lvl ='Regular'
      );
```
N.B.: Not tested...

Kind regards.

LOULOU.

How to create a table with strings active by Boolean button

Hello.
I have a problem to create a table and did not find any topic in the forum that could help me solve this problem.
I need to create a table of alarm.
In other words, every time an alarm has been triggered (Boolean button), the table shows the time, date and where the alarm has occurred.
For example, when garage alarm is activated, it will be at table:

Date / / Time / / Garage / / presence ON

And so on, when the alarm is activated the room:

Date / / Time / / room / / presence ON

If anyone can help, I would appreciate it enough.

Thank you.

Giuliano06 wrote:

So I can show the alarm, but when the button is not selected, it sends the null value (empty string) for the table through the registry to offset.

Also, when I choose for example the 2 bedrooms, it is moved to another column in the table and not just below the last alarm obtained.

My VI is attached cases someone might have an idea.

your constantly questioning the value to your table, ofcoarse, this vi is designed according to the mechanical action of the Boolean switch...

creating the table

Hello experts;
I know that I cannot create a table like this but y at - it a solution for it
create table like tp
with t as)
Select 1 as id, to_date (' 04 / 01/2015 ', ' DD/MM/YYYY') as d_from, to_date (' 07 / 01/2015 ', ' DD/MM/YYYY') as the double d_to
)
SELECT id, level + d_from - 1
t
connect by level < = d_to - d_from + 1;

Alias is missing...

Try this: (this one works)
```
CREATE TABLE tp
AS
   WITH t
        AS (SELECT 1 AS id,
                   TO_DATE ('1/4/2015', 'MM/DD/YYYY') AS d_from,
                   TO_DATE ('1/7/2015', 'MM/DD/YYYY') AS d_to
              FROM DUAL)
       SELECT id, LEVEL + d_from - 1 dt
         FROM t
   CONNECT BY LEVEL <= d_to - d_from + 1;
```
See you soon,.

Manik.

Syntex to create the table with the long data type

I'm looking to create a table based on another table that having the column long data type. Throw the error ORA-00997: illegal use of the LONG data type

I tired it
create table abc_long (ag bgd long number);
create table abc_long_dummy as ( ) Select *of abc_long); - ORA-00997 error: illegal use of the LONG data type
How to get there?

I'm looking to create a table based on another table that having the column long data type.

You really don't want to do that.

LONG data type has been deprecated for some time now, use CLOB.

The TO_LOB() function will do the conversion on the fly:
```
create table abc_long_dummy
as
select ag
     , to_lob(bgd) as bgd
from abc_long ;
```

What is better/more quick method to create a table (Oracle 11 g 2 dB)?

Assuming that there are no statistics for the source tables - tables are deleted and recreated every day
My paintings have a few million lines
I'm trying to create a filled with data as quickly as possible via
1 createtable_name as SELECT * from emp;
2. create table_name
Parallel degree 4
in SELECT * from EMP ;

I have 1 case I had some time 34 Sec
In case 2, the table was created in 15 Sec

In oracle other possibilities to create a much faster with this DEC?

Or it will be faster when I create a table using create table_name
(
column1datatype [NULL |] NOT NULL],
column2datatype [NULL |] NOT NULL],
...
column_ndatatype [NULL |] NOT NULL]
);
or maybe I should use this method
```
INSERT /*+ APPEND */ INTO empSELECT * FROM all_objects; 
INSERT /*+ APPEND_VALUES */ INTO emp SELECT * FROM all_objects; 
```
or it is better to simply creating a table
and to use the FORALL in BULK IN THE COLLECTION instruction
combination of Pentecost of the
INSERT / * + APPEND * / INTO emp;

I encourage you to test different options - as you did for the first two variants: personally, I think that it is much easier to remember these things if I did the tests myself - instead of trusting in the results of others. IE I don't think that there is something more fast parallelized ETG (perhaps with a clause (*)) additional nologging by using path direct inserts (although that INSERT APPEND select should do the same). I expect the operations in PL/SQL block to be slower.

(*), but you should consider the consequences of NOLOGGING for your backup strategies + recovery

create the table, otherwise there is?

I need to run a script that includes create table and insert some in this table, but it fails after the second run because the table exists.
Is it possible to have a command like.., create the table, otherwise it is..., which does not give me of the errors after the second run?
CREATE TABLE BREND
(
ID VARCHAR2 (10) PRIMARY KEY NOT NULL,
NAME VARCHAR2 (100) NOT NULL
);
INSERT IN BREND (ID, NAME) VALUES ('1 ', 'o2');
CREATE TABLE USER_BREND
(
ACTIVATE THE 'USER_ID' NUMBER (19.0) NOT NULL,
ACTIVATE THE "BREND_ID" VARCHAR2 (10) NOT NULL,
'USER_BREND_PK' CONSTRAINT PRIMARY KEY ('USER_ID', 'BREND_ID'),
"USER_BREND_USER_FK' FOREIGN KEY ('USER_ID') CONSTRAINT
ACTIVATE THE REFERENCE 'USER' ('ID') ON DELETE CASCADE,
"USER_BREND_BREND_FK' FOREIGN KEY ('BREND_ID') CONSTRAINT
SELECT REFERENCES "BREND' ('ID') ON DELETE CASCADE
);
COMMENT ON THE COLUMN "USER_BREND." ' ' User_id ' IS "associated Foreign key for the user;
COMMENT ON THE COLUMN "USER_BREND." "BREND_ID" IS "foreign key for the associated brend ';
INSERT INTO 'USER_BREND' (SELECT ID as USER_ID, '1' user BREND_ID')

Hello

Try the code below, I placed an exception for no data found:
```
DECLARE
v_emp int:=0;
BEGIN
  SELECT count(*) into v_emp FROM dba_tables where table_name = 'BREND' and owner ='ME'; 

 EXCEPTION WHEN NO_DATA_FOUND then
     EXECUTE IMMEDIATE 'create table BREND ( ID VARCHAR2(10) PRIMARY KEY NOT NULL, NAME VARCHAR2(100) NOT NULL)';
END;
/
```
Kind regards.

Transformation of Scripts that run only on the selected Tables

I'm relatively new to Data Modeler, but found almost everything to be very intuitive. I'm now doing use custom transformation scripts to dynamically add custom DDL elements. I wrote a transformation script that adds a sequence at the end of my DDL trigger successfully, and I'm happy with the results. The problem I run into is that we have two different categories of tables that require slightly different sequence triggers, but as my model is set to the level of database, my transformation scripts are applied to all arrays regardless they come what schema. Do you have any suggestions on how to limit the tables which proceeds by a transformation script? I thought to add if statements to check what schema tables are coming from, but if I have a situation where I have two different tables that require two different processing scripts, but they are in the same pattern, how can that I manage that? Ideally, I'd like to just pick a table and apply a transformation script for this table individually. Is this possible?
I work in a relational model with Data Modeler 4.0.

to dynamically add items customized to DDL

you need to check the custom of DDL in DM 4.1 features - "tools > rules and design transformations > Table DDL transformations"-DM 4.1 comes with example to generate tables of the newspaper and associated trigger.

. I wrote successfully in a transformation script that adds a sequence at the end of my DDL trigger

Data Modeler can generate the sequence and relaxation for you - you need to define the column as 'auto increment' / identity and set in preferences, you want "trigger" put in place. 4.1 DM added support for z/OS, DB2 LUW DB2 and MS SQL Server 2012.

Do you have any suggestions on how to limit the tables which proceeds by a transformation script? I thought to add if the instructions to check the schema, the tables are coming, but if I have a situation where I have two different tables that require two different processing scripts, but they are in the same schema

Well you need to sort it out on yourself - you can use classification types, dynamic properties user defined properties (in DM 4.1) or put paintings in various subviews or use the search feature (4.0.3 DM / DM 4.1 comes for example how to use the search results to create subview).

Ideally, I'd like to just pick a table and apply a transformation script for this table individually. Is this possible?

Here is an example of how get selected tables:
```
appv = model.getAppView();
dpv = appv.getCurrentDPV();
//check there is a diagram selected and it belongs to the same model
if(dpv!=null && dpv.getDesignPart() == model){
 tvs = dpv.getSelectedTopViews();
 for(var i=0;i
Philippe
		   
```

Audit to create any table

SQL > select * from v version $;
BANNER
--------------------------------------------------------------------------------
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
PL/SQL Release 11.2.0.1.0 - Production
CORE 11.2.0.1.0 Production
AMT for 32-bit Windows: Version 11.2.0.1.0 - Production
NLSRTL Version 11.2.0.1.0 - Production
SQL > select audit_option in the dba_stmt_audit_opts;
no selected line
SQL > see the parameter checking.
VALUE OF TYPE NAME
------------------------------------ ----------- ------------------------------
audit_file_dest string C:\APP\ADMINISTRATOR\ADMIN\ORC
L\ADUMP
audit_sys_operations boolean FALSE
AUDIT_TRAIL DB string
SQL > select count (*) in the dba_audit_trail;
COUNT (*)
----------
4132
SQL > audit create any table Scott.
Verification succeeded.
SQL > select audit_option in the dba_stmt_audit_opts;
AUDIT_OPTION
----------------------------------------
CREATE A TABLE
SQL > create table dummy (a number);
Table created.
SQL > insert into values dummy (1);
1 line of creation.
SQL > commit;
Validation complete.
SQL > select count (*) in the dba_audit_trail;
COUNT (*)
----------
4132
SQL >
So, my question is why I see no + 1 in dba_audit_trail while the user scott has been audit to create any table that is before activation of the audit and creating the table there are 4132 lines in dba_audit_trail and they are same even after activation of the audit and create the table. Kindly help me to understand.
Thank you.

It seems the user scott created table in its own schema, you must check create table as well.

Thank you

Bigot

Generate the DDL to create the table in the database

Hi all
I want to create the new fact and Stadium as being under the statement:
(1) in the designer, access the models > Oracle BI Applications (folder) > (model) Oracle BI Applications > done (sub-model) step, right click on the WC_SAMPLE_FS data store and select duplicate the selection.
2) double-click the new data store, and then rename it. Name and resource name must match the name of the actual table. Alias can be the same or greater value easy to use.
(3) in the sub-tab of the columns, add all columns.
(4) repeat the same steps to create the fact Table by copying the data store WC_SAMPLE_F under the submodel of "facts".
(5) for the fact table, define the type of OLAP to "fact Table.
(6) generate the DDL to create the table in the database.
In step 6, I don't know where and how to generate the DDL to create the database table. Please help me. If you have another tutorial with screenshot, please share with me. Thank you.
Kind regards
Cong

Hi Cong,

Please see section 6.3 DDL generation of scripts in this link:

Working with the Designer of the common Format - 11g Release 1 (11.1.1)

I hope this helps.

Thank you!

Saran.

Create selection table

Similar Questions

Maybe you are looking for