BC4J temporary tables - default tablespace

I have database Oracle database 9i. I have created database user by CREATE USER "DBUSER" PROFILE "DEFAULT" IDENTIFIED BY "dbuser" DEFAULT TABLESPACE "MYTABLESPACE" TEMPORARY TABLESPACE "TEMP" ACCOUNT UNLOCK;
So I expect all tables are created inside ORDBS tablespace. They do - but only my application tables. BC4J temporary tables (PCOLL_CONTROL, ...) are created inside "USERS" tablespace, not MYTABLESPACE nor TEMP.
Why? I don't want they are created inside users but don't know how to change it...
Any idea?
Thank you very much for any comment
Jan Pechanec
PS. I use JDeveloper 9.0.3.4

Hi Steve/Nick,
I am facing a similar kind of problem in oracle 9iAS(90220). A few days back there was a lot of user activity in one of the application modules and 7 PS_<app.module.name(s)> tables were created with around 7GB of size which eventually filled up the entire tablespace(100%). I spoke to the developers about the attributes that need to be set for Row spill over feature discussed in this forum but they said after lots of testing they have set those values and cannot be changed.
Could you please suggest me how can I ensure that, next time any application module specific PS_ tables will get created I can route them to different tablespace based on the module name. (I donot want to move them after they are created, to a different tablespace) Please let me know asap so that I can implement it and avert any future problems.
Thanks & regards,
Ramana

Similar Messages

BC4J Temporary Tables

Is there any way to customize the way bc4j creates its temporary tables? Specifically, I would like to change how this one is created. Right now it is:CREATE TABLE "PS_WebsiteService_10"
ID        NUMBER(20),
PARENTID NUMBER(20),
COLLID    NUMBER(10),
CONTENT   BLOB,
KEYCONT   BLOB
LOGGING
NOCACHE
NOPARALLEL;
CREATE UNIQUE INDEX PS_WEBSITESERVICE_10_PK ON "PS_WebsiteService_10"
(COLLID, ID)
LOGGING
NOPARALLEL;
ALTER TABLE "PS_WebsiteService_10" ADD (
CONSTRAINT PS_WEBSITESERVICE_10_PK PRIMARY KEY (COLLID, ID));My DBAs would like to put NOLOGGING in there. Apparently there are some insane logs going on in the database. Something to do with a BLOB bug in the db version we have they tell me.

Hi Steve/Nick,
I am facing a similar kind of problem in oracle 9iAS(90220). A few days back there was a lot of user activity in one of the application modules and 7 PS_<app.module.name(s)> tables were created with around 7GB of size which eventually filled up the entire tablespace(100%). I spoke to the developers about the attributes that need to be set for Row spill over feature discussed in this forum but they said after lots of testing they have set those values and cannot be changed.
Could you please suggest me how can I ensure that, next time any application module specific PS_ tables will get created I can route them to different tablespace based on the module name. (I donot want to move them after they are created, to a different tablespace) Please let me know asap so that I can implement it and avert any future problems.
Thanks & regards,
Ramana

Alter user default tablespace and temporary tablespace

Hi guru,
target : to ensure that users don't have the SYSTEM tablespace as their TEMPORARY or DEFAULT tablespace
scenario :
user default tablespace temporary tablespace
xxyym system system
Question: How to alter user ?
tq

In a scenario, let's say you want to make USERS the default tablespace for existing users and TEMP the default temporary tablespace, you can also create the alter statements as below into one script based on the output and run it.
select 'ALTER USER '||username||' DEFAULT TABLESPACE USERS;' FROM DBA_USERS WHERE DEFAULT_TABLESPACE IN('SYSTEM')
and username not in('SYS','SYSTEM');
select 'ALTER USER '||username||' TEMPORARY TABLESPACE TEMP;' FROM DBA_USERS WHERE TEMPORARY_TABLESPACE IN('SYSTEM');As magnus mentioned, don't forget to do this(if USERS and TEMP is what you want to go with) :
ALTER DATABASE DEFAULT TABLESPACE USERS;
ALTER DATABASE DEFAULT TEMPORARY TABLESPACE TEMP;

Creating a Global Temporary Table on non-default TEMP tablespace.

Hello ,
I am using Oracle 11g.
I have a procedure which create global temporary tables for its functionality. As the data which is going in the global temporary table , mean the data which is going in the default TEMP tablesapce is too huge ..... billions of rows..
So what i want to do is , I want to create the global temporary table in another TEMP2 tablespace ( which is not the default one) so the load of billions of rows of data will be shifted to TEMP2. The default TEMP tablespace will not be affected and it can be used for other transactions.
Is this possible. Can i shift the global temporary table from TEMP( Default temp tablespace) to TEMP2 ( the non-default temp tablespace) ????
Please guide me with proper solutions and examples ....
Thanks in advance ..

DBA4 wrote:
Hello ,
I am using Oracle 11g.
I have a procedure which create global temporary tables for its functionality. As the data which is going in the global temporary table , mean the data which is going in the default TEMP tablesapce is too huge ..... billions of rows..
So what i want to do is , I want to create the global temporary table in another TEMP2 tablespace ( which is not the default one) so the load of billions of rows of data will be shifted to TEMP2. The default TEMP tablespace will not be affected and it can be used for other transactions.
Is this possible. Can i shift the global temporary table from TEMP( Default temp tablespace) to TEMP2 ( the non-default temp tablespace) ????
Global temporary tables are instantiated in the temporary tablespace of the schema that inserts the data - not into "the default" temporary tablespace.
Assume Schema1 creates a GTT and grants all on that table to schema2
Assume schema1 also creates a procedure (authid owner, the default) to insert data into the GTT and grants execute on the procedure to schema2
If schema2 executes: insert into schema1.gtt, the data will appear in the temporary tablespace of schema2
If schema2 executes: execute schema1.procedure, the data will appear in the temporary tablespace of schema1
So if you want to protect the "normal" temporary tablespace, you could just create a special temporary tablespace for the owner of the procedure.
Regards
Jonathan Lewis

TABLESPACE issue with temporary table

I am getting the error ORA-00922: missing or invalid option when compiling the following code. What seems to be causing the trouble is the line when I specified "TABLESPACE MISC". For some reason, CREATE GLOBAL TEMPORARY TABLE does not allow me to choose the tablespace "MISC" for the table. What did I do wrong here?
My code
CREATE OR REPLACE PROCEDURE Nmh_Sp_Chf_Patients(
r_to_report      IN OUT      Nmh_Pkg_Chf_Patients.TYP_PKG_CHF_PATIENTS
AS
e_table_not_exist EXCEPTION;
PRAGMA EXCEPTION_INIT (e_table_not_exist, -942);
dACTIVE_CD NUMBER := Nmh_Get_Code_Value_By('DISPLAY_KEY', 48, 'ACTIVE');
dENCNTRACTIVE_CD NUMBER := Nmh_Get_Code_Value_By('DISPLAY_KEY', 261, 'ACTIVE');
dATTENDDOCCd NUMBER := Nmh_Get_Code_Value_By('DISPLAY_KEY', 333, 'ATTENDINGPHYSPROV');
dCHFCd NUMBER := Nmh_Get_Code_Value_By('DISPLAY_KEY', 200, 'HEARTFAILUREHANDOUTS');
dORDERCOMPLETECd NUMBER := Nmh_Get_Code_Value_By('DISPLAY', 6004, 'Order Complete');
dORDEREDCd NUMBER := Nmh_Get_Code_Value_By('DISPLAY', 6004, 'Ordered');
// Populating active inpatients //
// NOTE: This approach IS proven TO be more efficient than //
// joining ENCNTR_DOMAIN TABLE //
/* Define the cursor variable type */
TYPE t_ActiveInpatient IS REF CURSOR;
/* and the variable itself. */
r_ActiveInpatient t_ActiveInpatient;
/* Variables to hold the output of r_ActiveInpatient. */
v_patient_full_name VARCHAR2(100);
v_encntr_id NUMBER;
v_person_id NUMBER;
v_mrn VARCHAR2(200);
v_fin VARCHAR2(200);
v_reg_dt_tm DATE;
v_nurse_unit VARCHAR2(40);
v_med_service VARCHAR2(40);
v_attending_physician VARCHAR2(100);
v_min_updt_cnt ENCNTR_PRSNL_RELTN.updt_cnt%TYPE;
v_tmp_sql VARCHAR2(2000);
v_tmp_char VARCHAR2(11);
BEGIN
BEGIN
     EXECUTE IMMEDIATE 'DROP TABLE NMH_SP_CHF_PATIENTS_1';
EXCEPTION
     WHEN e_table_not_exist THEN NULL;
     END;
EXECUTE IMMEDIATE 'CREATE GLOBAL TEMPORARY TABLE NMH_SP_CHF_PATIENTS_1'
|| '(patient_full_name VARCHAR2(100), encntr_id NUMBER,'
|| ' person_id NUMBER, mrn VARCHAR2(200), fin VARCHAR2(200),'
|| ' reg_dt_tm DATE, nurse_unit VARCHAR2(40),'
|| ' med_service VARCHAR2(40), attending_physician VARCHAR2(100))'
|| ' TABLESPACE MISC ' -- If I commented out this line, it would have worked fine.
|| ' ON COMMIT PRESERVE ROWS';
OPEN r_ActiveInpatient FOR
SELECT nai.patient_full_name,
nai.encntr_id,
nai.person_id,
nai.mrn,
nai.fin,
nai.reg_dt_tm,
Nmh_Get_Code_Display(nai.loc_nurse_unit_cd) NURSE_UNIT,
Nmh_Get_Code_Display(nai.med_service_cd) med_service
FROM NMH_ACTIVE_INPATIENTS nai,
          ORDERS o
WHERE o.encntr_id = nai.encntr_id
AND o.catalog_cd = dCHFCd
AND (o.order_status_cd = dORDERCOMPLETECd
OR o.order_status_cd = dORDEREDCd)
AND o.template_order_id = 0;
LOOP
FETCH r_ActiveInpatient INTO
v_patient_full_name,
v_encntr_id,
v_person_id,
v_mrn,
v_fin,
v_reg_dt_tm,
v_nurse_unit,
v_med_service;
EXIT WHEN r_ActiveInpatient%NOTFOUND;
BEGIN
SELECT MIN(epr.updt_cnt)
INTO v_min_updt_cnt
FROM ENCNTR_PRSNL_RELTN epr
     WHERE epr.encntr_id = v_encntr_id
          AND epr.encntr_prsnl_r_cd = dATTENDDOCCd;
EXCEPTION
          WHEN NO_DATA_FOUND THEN NULL;
          END;
BEGIN
     SELECT pr.name_full_formatted
     INTO v_attending_physician
     FROM ENCNTR_PRSNL_RELTN epr,
               PRSNL pr
     WHERE epr.encntr_id = v_encntr_id
               AND epr.encntr_prsnl_r_cd = dATTENDDOCCd
     AND epr.updt_cnt = v_min_updt_cnt
     AND pr.person_id = epr.prsnl_person_id;
EXCEPTION
          WHEN NO_DATA_FOUND THEN NULL;
          END;
               v_tmp_sql := 'INSERT INTO NMH_SP_CHF_PATIENTS_1 ';
               v_tmp_sql := v_tmp_sql || '(patient_full_name, encntr_id, person_id, ';
               v_tmp_sql := v_tmp_sql || 'mrn, fin, reg_dt_tm, nurse_unit, ';
               v_tmp_sql := v_tmp_sql || 'med_service, attending_physician) ';
               v_tmp_sql := v_tmp_sql || 'VALUES (:1,:2,:3,:4,:5,:6,:7,:8,:9)';
EXECUTE IMMEDIATE v_tmp_sql
               USING
               v_patient_full_name, v_encntr_id, v_person_id, v_mrn,
               v_fin, v_reg_dt_tm, v_nurse_unit,
               v_med_service, v_attending_physician;
END LOOP;
v_tmp_sql := 'SELECT * FROM NMH_SP_CHF_PATIENTS_1 t';
OPEN r_to_report FOR
v_tmp_sql;
END;
/

In looking through your code a bit more, it seems that you have a fundamental minunderstanding of how temporary tables work in Oracle (if you have a SQL Server background, Oracle temp tables and SQL Server temp tables are quite different).
The definition of a temporary table is available to every session, so you do not want to create a temporary table dynamically. You would create the temporary table once, just like any other table. The data that is inserted into a temporary table is local to that session, so you can have multiple sessions inserting data and each will see only its own data. By creating the temporary table outside of the stored procedure, you can avoid all the dynamic SQL you are currently doing, which is going to make the codea lot clearer, plus you avoid the implicit commit of a DDL operation in the procedure.
As to the error you're getting, is there an ORA-xxxxx error message being returned? If your front end is hiding that error, try running the procedure from SQL*Plus and post the error. Of course, first try moving the table declaration outside the procedure.
Justin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC

Table created by datapump imp/exp, change default tablespace?

Is there a way, without changing the users default tablespace, to force the table created by data pump import or export to go to a different tablespace than the users default? Our policy is that users must declare the tablespace they want an object created in, therefore the users tablespace is very small (6M), so if they accidently created an object in this TS it would fail. When we run expdp, this default tablespace fills up and export fails. I can't find a parameter in the documentation on giving an alternative tablespace for this table.

When you run expdp, it creates a table under the user you logged in as. This table is used to keep track of the datapump process. I am looking for a way to direct datapump to create this table in a specific tablespace instead of the users default.

DEFAULT TABLESPACE and TEMPORARY TABLESPACE for eBusiness Suite database

Hi:
What is the
DEFAULT TABLESPACE and TEMPORARY TABLESPACE
for eBusiness Suite database.
I want to create a new schema on the eBusiness Suite database.
Please help

DEFAULT TABLESPACE and TEMPORARY TABLESPACE
for eBusiness Suite database.
I want to create a new schema on the eBusiness Suite database.Create a new tablespace and temporary tablespace for your custom schema (you may use the existing temporary tablespace).
Integrating Custom Applications with Oracle Applications Release 11i [ID 176852.1]
Step By Step Guide to Creating a Custom Application in Applications 11i [ID 216589.1]
Thanks,
Hussein

Can we change the default tablespace of a table?

Hi All,
Can we change the default tablespace for any TABLE while it contains any data? If yes, how it works? If no, any workaround?
Thanx,
Zaaf

instead of moving your table after the import you could:
1)execute an import with the parameter ROWS = N
2)move the empty tables to the correct tablespace
3)execute an impot with ROWS = Y and IGNORE = Y
This way you will only have to move empty tables which will probably be much faster also there is no need to rebuild the indexes.

Moving tables to a new default tablespace

I want to move all the tables owned by a user (OUTLN) to a new tablespace.
I know that if I make an export file of that schema and then I make an import after deleting the tables and changing the default tablespace of that schema I should solve the problem (as suggested from documentation), but it isn't so.
The tablespace of the tables after the import remains the same.
Why?
Thank you

I want to move all the tables owned by a user (OUTLN) to a new tablespace.
I know that if I make an export file of that schema and then I make an import after deleting the tables and changing the default tablespace of that schema I should solve the problem (as suggested from documentation), but it isn't so.
The tablespace of the tables after the import remains the same.
Why? If you are concerned about importing large number of tables to a different tablespace, you can do it in this way. After exporting the tables, import them to a .sql file. In other words, tables does not get imported by this method to the database but the "create table" script is generated for the tables. Then you can edit this .sql file using any text editor, replace all the tablespace names with the tablespace name you want. Then run the script. Remember to remove the "Rem" comment words. The following syntax will help you to do this.
c:\>imp80 scott/tiger file=c:\tabledump.dmp indexfile=c:\tablecreate.sql full=y
Here, though we say "indexfile", it generates full create table script.
In order to import the data, re-run the import without indexfile option and with ignore=y option.
Hope this will help.
Regards,
R. Magesh.

Setting the default default tablespace and default temporary tablespace

Is there a way to set the default default tablespace and default temporary tablespace database wide? I want to assign default and temporary tablespaces other than SYSTEM to all new users without having to explicitly define the tablespace names.

Hi,
Well, I assume that OP is using 10g, but exactly what you said, in Oracle 9i, it became possible to specify the default temporary tablespace in the database. In Oracle 10g, it allows all users to set up the default permanent tablespace to set the permanent tablespace used by default. Before Oracle 10g, if the default permanent tablespace is not set up when creating the user, SYSTEM tablespace will be set up as the default permanent tablespace by default.
Cheers

Use of DEFAULT tablespace while re-enabling constraint

Using 8.1.7.2.
While trying to re-enable a constraint on a table, we hit a ORA-01630. According to the error message, Oracle was trying to use the DEFAULT tablespace (USERS) instead of the TEMPORARY tablespace (TEMP) to do the work.
Why would Oracle use a tablespace other than TEMP to do work that needed temporary space?
[email protected]

What is the 'temporary_tablespace' value when you query user_users as this user?
Oracle will use the tablespace that is specified as the users TEMPORARY_TABLESPACE for all sorts. If that tablespace does not exists, it uses SYSTEM.

Export from 8i to 11g does not create object in default tablespace

Hello
I have exported and schema from oracle 8i and i try to import it in oracle 11g in a different architecture (8i is sparc. 11g is x86)
i have created an user with default tablespace and the original tablespace does not exist in this database, but I am getting the error;
IMP-00003: ORACLE error 959 encountered
ORA-00959: tablespace 'TS_ARCCLAIMS_DAT' does not exist
if i create an indexfile and create all the objects by removing the REM from the indexfile i have countless contrains errors so i bet this is not an option.
this is how the user is created in 11g:
CREATE USER ARCCLAIMS
IDENTIFIED BY <password>
DEFAULT TABLESPACE ARCCLAIMS_DAT
TEMPORARY TABLESPACE GN_TMP
PROFILE DEFAULT
ACCOUNT UNLOCK;
-- 2 Roles for ARCCLAIMS
GRANT CONNECT TO ARCCLAIMS;
GRANT RESOURCE TO ARCCLAIMS;
ALTER USER ARCCLAIMS DEFAULT ROLE ALL;
-- 1 System Privilege for ARCCLAIMS
GRANT UNLIMITED TABLESPACE TO ARCCLAIMS;
-- 1 Tablespace Quota for ARCCLAIMS
ALTER USER ARCCLAIMS QUOTA UNLIMITED ON ARCCLAIMS_DAT;
what do i have to do in order to have the objects go to the default tablespace of the user?
thank you
Mario G,

Hello,
I believe that you are right, the tables seem to have a clob datatype..
here is it one of the tables affected:
IMP-00017: following statement failed with ORACLE error 959:
"CREATE TABLE "CLM_MAIL_INBOX" ("IBX_CODE" NUMBER(6, 0) NOT NULL DISABLE, "I"
"BX_CLM_CODE" NUMBER(10, 0), "IBX_IMP" CHAR(1), "IBX_FROM" VARCHAR2(50), "IB"
"X_SUBJECT" VARCHAR2(200), "IBX_CREATION" DATE, "IBX_ATTACH_TYPE" VARCHAR2(1"
"0), "IBX_ATTACH" BLOB, "IBX_CONTENT" VARCHAR2(1000), "IBX_RESP_STN" VARCHAR"
"2(3)) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 LOGGING STORAGE(INITIA"
"L 16384 FREELISTS 1 FREELIST GROUPS 1) TABLESPACE "TS_ARCCLAIMS_DAT" LOB (""
"IBX_ATTACH") STORE AS (TABLESPACE "TS_ARCCLAIMS_DAT" DISABLE STORAGE IN RO"
"W CHUNK 8192 PCTVERSION 10 NOCACHE STORAGE(INITIAL 24576 FREELISTS 1 FREEL"
"IST GROUPS 1))"
IMP-00003: ORACLE error 959 encountered
ORA-00959: tablespace 'TS_ARCCLAIMS_DAT' does not exist
I have already reviewed the document 1180873.1
could the DEFERRED_SEGMENT_CREATION=false be enough..
could this be done with alter system or alter session? which one is better?
thank you

Giving grant for creating temporary table only

hi...
i want to give grant for creating only temporary tables to a schema.
no other grants should not be there strictly...
I have created the following user widout any grants...plss suggest me how can i give the grants for creating only temporary tables..
create user user_name
identified by password
default tablespace table_space
temporary tablespace TEMP
profile DEFAULT
quota unlimited on table_space;
grant select on V_$SESSION to user_name;
thanks...
Edited by: user12780416 on Mar 25, 2011 8:32 AM

As has been pointed out, it would be **extremely** unusual to want to have a user that could create global temporary tables but not permanent tables. I'm very hard-pressed to imagine a scenario where that would make sense.
However, if you grant the user the CREATE TABLE privilege but do not grant the user quota on any permanent tablespace, they would be unable to create permanent tables but should be able to create global temporary tables. You'll have to make sure that you don't grant the user UNLIMITED TABLESPACE which would give them unlimited quota on all tablespaces. If you are using 11g and you have enabled deferred segment creation, the users would actually be able to create tables in tablespaces they have no quota on though they would not be able to insert any data in those tables.
Justin

Grant table create for only temporary tables

I looking for a way to allow user to create only temporary tables. The user does not need to create or drop any public tables.

Hi,
>>This is really a bad suggestion. The user1 can now only select his own tables, no insert or update. It can not be allowed in the "real world".
The OP said "I looking for a way to allow user to create only temporary tables"
I think that you didn't understand what I showed ...
SYSTEM@test> create user user1 identified by user1 default tablespace USERS quota 0 on USERS;
User created.
SYSTEM@test> create user user2 identified by user2 default tablespace USERS quota unlimited on USERS;
User created.
SYSTEM@test> grant create session,create table, create synonym to user1,user2;
Grant succeeded.
SYSTEM@test> connect user2/user2@teste
Connected.
USER2@test> create table x (id number);
Table created.
USER2@test> insert into x values (1);
1 row created.
USER2@test> grant select,delete,insert,update on x to user1;
Grant succeeded.
USER2@test> connect user1/user1@teste
Connected.
USER1@test> create synonym x for user2.x;
Synonym created.
USER1@test> insert into x values (2);
1 row created.
USER1@test> select * from x;
        ID
         1
         2
USER1@test> create table y (id number);
create table y (id number)
ERROR at line 1:
ORA-01536: space quota exceeded for tablespace 'USERS'
USER1@teste> create table user2.y (id number);
create table user2.y (id number)
ERROR at line 1:
ORA-01031: insufficient privileges
USER1@test> drop table user2.x;
drop table user2.x
ERROR at line 1:
ORA-01031: insufficient privileges
USER1@test> create global temporary table y (id number) on commit preserve rows;
Table created.
USER1@test> insert into y values (1);
1 row created.
USER1@test> select * from y;
        ID
         1
USER1@test>Cheers

How to create index on Global Temporary Table?

Hi,
Can i create index with storage parameters on global temporary table? If possible, how?
Thanks

Yes. You can create an index on a global temporary table (GTT) with the regular 'CREATE INDEX' statement.
Not sure though if you are allowed to locate it in a specific tablespace. Why would you want to do that anyway?
My guess is, like the GTT, indexes on GTT's also default to the temporary tablespace.

BC4J temporary tables - default tablespace

Similar Messages

Maybe you are looking for