Query Database in non default Tablespace.

Hi
As I understand a Database can be spread over multiple Tablespaces (a Database can contain multiple Tablespaces).
How do I query a table that exists in a non default Tablespace?
How do I query a table in another database on a different Tablespace?
Rob.

user8803094 wrote:
Hi
As I understand a Database can be spread over multiple Tablespaces (a Database can contain multiple Tablespaces).
How do I query a table that exists in a non default Tablespace?
SQL> select table_name from dba_tables where tablespace_name not in (select default_tablespace from dba_users where username ="<your user>");
How do I query a table in another database on a different Tablespace?Pl elaborate on what you mean by this.
>
Rob.HTH
Srini

Similar Messages

Register database with non default listener

I already installed oracle 11gR2 database with asm.
The grid infrastructure is installed with the user grid and oracle software with orcl user.
The database is created with dbca with orcl user.
The default non listener is created with srvctl add listener command.
I already try to modify the parameter local_listener but I receive the following error
SQL> alter system set local_listener='LSNR_TESTDB';
alter system set local_listener='LSNR_TESTDB' SCOPE=memory
ERROR at line 1:
ORA-02097: parameter cannot be modified because specified value is invalid
ORA-00119: invalid specification for system parameter LOCAL_LISTENER
ORA-00132: syntax error or unresolved network name 'LSNR_TESTDB'
Any help.
Thanks

hi,
ORA-00132: syntax error or unresolved network name 'LSNR_TESTDBCause: Listener address has syntax error or cannot be resolved.
Action: If a network name is specified, check that it corresponds to an entry in TNSNAMES.ORA or other address repository as configured for your system. Make sure that the entry is syntactically correct.
check the exact listener name 'LSNR_TESTDB' in listener.ora file... and set the parameter..
Error with Listener. ORA-00132: syntax error or unresolved network name

Thread : created tablespace not seen wihle querying database

hi there,
I have create tablespace but when i queried database it is not showing its existence
here are steps which i used to create tablespace------
create tablespace ts_corrupt
datafile '/PGHProdDB/oradata/paceview/ts_corrupt01.dbf'
size 10m autoextend on next 5m
extent management local
segment space management auto
tablespace created.
create user usr_corrupt identified by usr_corrupt
default tablespace ts_corrupt
quota unlimited on ts_corrupt
User created.
grant connect , resource to usr_corrupt
Grant succeeded.
conn usr_corrupt/usr_corrupt
Connected.
create table t_corrupt as select * from all_objects
table created
but when i query to see the appropriate datafile
conn / as sysdba
SQL> select * from v$dbfile;
FILE#
NAME
5
/PGHProdDB/oradata/paceview/example01.dbf
4
/PGHProdDB/oradata/user00.dbf
3
/PGHProdDB/oradata/paceview/sysaux.dbf
FILE#
NAME
2
/PGHProdDB/oradata/paceview/undotbs1.dbf
1
/PGHProdDB/oradata/paceview/system.dbf
and run rman backup-------------
rman terget /
RMAN> backup incremental level 1 cumulative database;
Starting backup at 28-AUG-12
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=28 devtype=DISK
channel ORA_DISK_1: starting incremental level 1 datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=/PGHProdDB/oradata/paceview/system.dbf
input datafile fno=00003 name=/PGHProdDB/oradata/paceview/sysaux.dbf
input datafile fno=00002 name=/PGHProdDB/oradata/paceview/undotbs1.dbf
input datafile fno=00004 name=/PGHProdDB/oradata/user00.dbf
input datafile fno=00005 name=/PGHProdDB/oradata/paceview/example01.dbf
channel ORA_DISK_1: starting piece 1 at 28-AUG-12
it is not showing "t_corrupt" tablespace while taking backup
now problem is arising where is my newly created datafile ?
thanks
regards
Edited by: abdul_ora on Aug 29, 2012 11:08 AM

i did what you people suggest me---
mr. Yasir Hashmi as you asked --
If it is not in the alert log, oracle has no record of it.
Are you sure you really created it?
Create it again and verify it from alert log.so i have created it again and this time its showing in alertlog.
mr. harry76 as you asked---
It will be in uppercase in the logfile if it is there?no, not at all i havent find it .
:There must be 2 databases involved here - and the initial scripts you ran must be against the other database.I am fated that i have run that command on specific database as USER is still exist which i had created.
Can you recall your command history?history showing me that i corrupted the one of that tablespace(ts_corrupt) block to recover it from recoverblock command
by the way i know you people are helping me out so much that i learn alot from this kind of mistakes
thank you for giving me your precious consideration and scarce time :) and need more as my curiosity is increasing
Edited by: abdul_ora on Aug 28, 2012 4:52 PM

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

Restore Database to non-ASM Storage - Issue with Bigfile Tablespace

I have been testing a restore of my prod database that uses ASM (and oracle managed files) for storage to a different server and non-ASM storage. Oracle version is 10g EE. My database has one bigfile tablespace and it's datafile is about 250GB. The restore fails and it has something to do with the bigfile tablespace.
Here is the rman restore script:
run
set newname for datafile 1 to '/ora01/db/ehr/system01.dbf';
set newname for datafile 2 to '/ora01/db/ehr/undotbs01.dbf';
set newname for datafile 3 to '/ora01/db/ehr/sysaux01.dbf';
set newname for datafile 4 to '/ora01/db/ehr/undotbs02.dbf';
set newname for datafile 5 to '/ora01/db/ehr/users01.dbf';
set newname for datafile 6 to '/ora01/db/ehr/apolloaud01.dbf';
set newname for datafile 7 to '/ora01/db/ehr/apollohist01.dbf';
set newname for datafile 8 to '/ora01/db/ehr/apolloidx01.dbf';
set newname for datafile 9 to '/ora01/db/ehr/apollotab01.dbf';
set newname for datafile 10 to '/ora01/db/ehr/apollotab02.dbf';
set newname for datafile 11 to '/ora02/db/ehr/apollolob01.dbf';
set newname for datafile 12 to '/ora01/db/ehr/apollofdb01.dbf';
set newname for datafile 13 to '/ora01/db/ehr/apolloidx02.dbf';
set newname for datafile 14 to '/ora01/db/ehr/apolloidx03.dbf';
set newname for datafile 15 to '/ora01/db/ehr/apolloaud02.dbf';
set newname for datafile 16 to '/ora01/db/ehr/apollotab03.dbf';
set until sequence 60298 thread 2;
restore database;
switch datafile all;
recover database;
Datafile 11 is the datafile in the bigfile tablespace. Here are the weird things about the restore:
1. The restore output shows this:
creating datafile fno=11 name=/ora02/db/ehr/apollolob01.dbf
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to /ora01/db/ehr/system01.dbf
restoring datafile 00002 to /ora01/db/ehr/undotbs01.dbf
restoring datafile 00003 to /ora01/db/ehr/sysaux01.dbf
restoring datafile 00004 to /ora01/db/ehr/undotbs02.dbf
restoring datafile 00005 to /ora01/db/ehr/users01.dbf
restoring datafile 00006 to /ora01/db/ehr/apolloaud01.dbf
restoring datafile 00007 to /ora01/db/ehr/apollohist01.dbf
restoring datafile 00008 to /ora01/db/ehr/apolloidx01.dbf
restoring datafile 00009 to /ora01/db/ehr/apollotab01.dbf
restoring datafile 00010 to /ora01/db/ehr/apollotab02.dbf
restoring datafile 00012 to /ora01/db/ehr/apollofdb01.dbf
restoring datafile 00013 to /ora01/db/ehr/apolloidx02.dbf
restoring datafile 00014 to /ora01/db/ehr/apolloidx03.dbf
restoring datafile 00015 to /ora01/db/ehr/apolloaud02.dbf
restoring datafile 00016 to /ora01/db/ehr/apollotab03.dbf
Why at the beginning is it "creating" datafile 11? Then it doesnt even say it is "restoring" that datafile. Only restoring datafiles 1,2,3,4,5,6,7,8,9,10,12,13,14,15, and 16.
When it creates datafile 11 it is only 26GB, that is much smaller than it should be according to v$datafile view on source prod database. Also even though it says it is creating datafile 11 as /ora02/db/ehr/apollolob01.dbf it actually creates it as an oracle managed file at /ora02/db/ehr/EHR/datafile/o1_mf_apollolo_6crxyqs2_.dbf
After the datafiles are restored the "switch datafile all" command fails:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of switch command at 10/18/2010 13:58:37
ORA-19625: error identifying file /ora02/db/ehr/apollolob01.dbf
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
So my question is how do I get this database restored to non-ASM (and non omf)?

So I tried using a different scn with my "set until scn #####" then the restore created 2 datafiles. The datafile for apollolob and apollotab02.dbf. So I think I have narrowed the problem to be that I am not using the correct scn number so RMAN can successfully restore those datafiles and recreates them instead. How do I find the correct scn to use to do a successful restore of the entire database? I have seen different methods on the web, but cant figure it out. Ive used "select archivelog_change#-1 from v$database;" and I also did "list backup of archivelog all" and used the latest sequence number. How can I find the correct scn to use so the entire database will restore?
Here is the output of "list backup":
List of Backup Sets
===================
BS Key Size Device Type Elapsed Time Completion Time
19724 41.12M DISK 00:00:10 14-OCT-10
BP Key: 65840 Status: AVAILABLE Compressed: YES Tag: TAG20101014T210022
Piece Name: /mnt/migrate/rman/EHR_dbid3632734257_set113195_piece1_copy1_20101014
List of Archived Logs in backup set 19724
Thrd Seq Low SCN Low Time Next SCN Next Time
1 50439 3230234843 14-OCT-10 3230268282 14-OCT-10
1 50440 3230268282 14-OCT-10 3230286806 14-OCT-10
2 60280 3230234852 14-OCT-10 3230251419 14-OCT-10
2 60281 3230251419 14-OCT-10 3230268263 14-OCT-10
2 60282 3230268263 14-OCT-10 3230286809 14-OCT-10
BS Key Type LV Size Device Type Elapsed Time Completion Time
19725 Full 126.40G DISK 09:11:51 15-OCT-10
List of Datafiles in backup set 19725
File LV Type Ckp SCN Ckp Time Name
1 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/system.625.609259453
2 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/undotbs1.620.609259461
3 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/sysaux.768.609259463
4 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/undotbs2.632.609259467
5 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/users.257.609259471
6 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apolloaud.316.619537285
7 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apollohist.629.619538155
8 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apolloidx.312.619538169
9 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apollotab.276.619538487
10 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apollotab.576.619539331
11 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apollolob.570.619539593
12 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apollofdb.750.645974339
13 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apolloidx.429.651171265
14 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apolloidx.705.688680793
15 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apolloaud.747.699632315
16 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apollotab.330.715622123
Backup Set Copy #1 of backup set 19725
Device Type Elapsed Time Completion Time Compressed Tag
DISK 09:11:51 20-OCT-10 YES TAG20101014T210039
List of Backup Pieces for backup set 19725 Copy #1
BP Key Pc# Status Piece Name
65851 1 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece1_copy1_20101014
65862 2 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece2_copy1_20101014
65873 3 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece3_copy1_20101014
65884 4 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece4_copy1_20101014
65895 5 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece5_copy1_20101014
65901 6 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece6_copy1_20101014
65902 7 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece7_copy1_20101014
65903 8 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece8_copy1_20101014
65904 9 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece9_copy1_20101014
65841 10 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece10_copy1_20101014
65842 11 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece11_copy1_20101014
65843 12 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece12_copy1_20101014
65844 13 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece13_copy1_20101014
65845 14 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece14_copy1_20101014
65846 15 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece15_copy1_20101014
65847 16 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece16_copy1_20101014
65848 17 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece17_copy1_20101014
65849 18 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece18_copy1_20101014
65850 19 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece19_copy1_20101014
65852 20 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece20_copy1_20101014
65853 21 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece21_copy1_20101014
65854 22 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece22_copy1_20101015
65855 23 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece23_copy1_20101015
65856 24 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece24_copy1_20101015
65857 25 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece25_copy1_20101015
65858 26 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece26_copy1_20101015
65859 27 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece27_copy1_20101015
65860 28 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece28_copy1_20101015
65861 29 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece29_copy1_20101015
65863 30 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece30_copy1_20101015
65864 31 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece31_copy1_20101015
65865 32 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece32_copy1_20101015
65866 33 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece33_copy1_20101015
65867 34 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece34_copy1_20101015
65868 35 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece35_copy1_20101015
65869 36 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece36_copy1_20101015
65870 37 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece37_copy1_20101015
65871 38 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece38_copy1_20101015
65872 39 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece39_copy1_20101015
65874 40 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece40_copy1_20101015
65875 41 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece41_copy1_20101015
65876 42 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece42_copy1_20101015
65877 43 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece43_copy1_20101015
65878 44 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece44_copy1_20101015
65879 45 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece45_copy1_20101015
65880 46 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece46_copy1_20101015
65881 47 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece47_copy1_20101015
65882 48 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece48_copy1_20101015
65883 49 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece49_copy1_20101015
65885 50 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece50_copy1_20101015
65886 51 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece51_copy1_20101015
65887 52 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece52_copy1_20101015
65888 53 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece53_copy1_20101015
65889 54 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece54_copy1_20101015
65890 55 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece55_copy1_20101015
65891 56 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece56_copy1_20101015
65892 57 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece57_copy1_20101015
65893 58 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece58_copy1_20101015
65894 59 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece59_copy1_20101015
65896 60 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece60_copy1_20101015
65897 61 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece61_copy1_20101015
65898 62 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece62_copy1_20101015
65899 63 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece63_copy1_20101015
65900 64 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece64_copy1_20101015
BS Key Size Device Type Elapsed Time Completion Time
19726 228.10M DISK 00:00:49 15-OCT-10
BP Key: 65905 Status: AVAILABLE Compressed: YES Tag: TAG20101015T061242
Piece Name: /mnt/migrate/rman/EHR_dbid3632734257_set113197_piece1_copy1_20101015
List of Archived Logs in backup set 19726
Thrd Seq Low SCN Low Time Next SCN Next Time
1 50441 3230286806 14-OCT-10 3230331993 14-OCT-10
1 50442 3230331993 14-OCT-10 3230401945 14-OCT-10
1 50443 3230401945 14-OCT-10 3230469794 15-OCT-10
1 50444 3230469794 15-OCT-10 3230555010 15-OCT-10
1 50445 3230555010 15-OCT-10 3230618396 15-OCT-10
1 50446 3230618396 15-OCT-10 3230695020 15-OCT-10
2 60283 3230286809 14-OCT-10 3230304858 14-OCT-10
2 60284 3230304858 14-OCT-10 3230330891 14-OCT-10
2 60285 3230330891 14-OCT-10 3230354275 14-OCT-10
2 60286 3230354275 14-OCT-10 3230366292 14-OCT-10
2 60287 3230366292 14-OCT-10 3230399805 14-OCT-10
2 60288 3230399805 14-OCT-10 3230423577 14-OCT-10
2 60289 3230423577 14-OCT-10 3230446176 15-OCT-10
2 60290 3230446176 15-OCT-10 3230469756 15-OCT-10
2 60291 3230469756 15-OCT-10 3230496786 15-OCT-10
2 60292 3230496786 15-OCT-10 3230524710 15-OCT-10
2 60293 3230524710 15-OCT-10 3230554981 15-OCT-10
2 60294 3230554981 15-OCT-10 3230583802 15-OCT-10
2 60295 3230583802 15-OCT-10 3230610465 15-OCT-10
2 60296 3230610465 15-OCT-10 3230617887 15-OCT-10
2 60297 3230617887 15-OCT-10 3230673207 15-OCT-10
2 60298 3230673207 15-OCT-10 3230695022 15-OCT-10

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

DATABASE IMPORT IN THE DEFAULT TABLESPACE OF USER

Hi,
I have exported database into a dump file ,the exported database was using the system table space.
Now i am trying to import database from the above dump file into the new user which has default table space specified, but its the import is happening in system table space rather then the default tablespace.
On the command prompt command i am running this command to import:
imp user/password@netservicename file=filename fromuser=x1 touser=xyz ignore=y

You have to create the table in the tablespace you want before importing the datas in.
Do you know the ALTER TABLE MOVE command to move a table from one tablespace to another ?
Fred

Query from a non database item

Hi everybody,
Can anybody please tell me how can i make any query from a non data base item .
Will you please let me know where to set the trigger or something else which will solve the problem.
Thanks and Regards
Anutosh Bhattacharya

Hi,
For the block you want to query on use PRE-QUERY trigger.
In the PRE-QUERY trigger use the
SET_BLOCK_PROPERTY ('BLOCK', DEFAULT_WHERE, 'your query condition');
Hope this helps.
Regards
Arif

Error:cannot use system rollback segment for non-system tablespace

Hi,
I have created a oracle database 10.2.0 on fedora 9 system. I have created a user and assigned the default tablespace SATYA and given the permissions. But when I create a table in the user I am getting the following error.
Can anyone help me in rectifying this error.
ORA-01552: cannot use system rollback segment for non-system tablespace 'SATYA'
thankyou
satya

Undo management is either AUTO or Manual, no local
http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/undo.htm#sthref1469
Since you are using 10g, you are recommended to use Auto undo management
If you still plan to use manual undo management, make sure you have other non-system rollback segment in place.

Modifying default tablespace + implications

Suppose an Oracle user has his default tablespace set to Tablespace_Old and there are already objects stored there.
Now suppose we want to alter the user such that this default tablespace is set to Tablespace_New. What happens to the objects which were stored in Tablespace_Old? Will they still be accessible from Tablespace_New or there will be the need to migrate the old data to the new tablespace?
Moreover, in the case of a standby database scenario, will the standby database adopt such changes (i.e. will the user be assigned to tablespace Tablespace_New?)?
thanks for your time.

The default tablespace is only used to assign a location to build an object if a tablespace is not defined. The old objects will still be accessable. The more important thing is what quota's are assigned for the user on the tablespace. If the Quota is none, the user can't write in the tablespace. If it is unlimited, they can write anything and if the quota is 20 meg, then they can't create more then 20 meg of objects and rows.

A confused newbie: SQLServer database vs. ORACLE Tablespace

Guys, excuse me for asking some surely stupid questions, but I'm really confused.
In SQLServer, I can simply create a new database and it has it's own physical files. This means that - for example - it is really trivial to have multiple releases of the same database setup concurrently.
In Oracle, I'm simply blown away at the complexity of this seemingly simple requirement. Here are some of the problems I have doing this with Orcale:
- I can create a second tablespace but then my sequences clash with sequences already in place for tables in the other table space
- I can't simply drop a tablespace and the sequences drop too
- I don't know how to connect to a new database (somehow I seem to have to create a listener too)
OK, I doubt that Oracle is so useless, I'm far more convinced that the "useless" attribute is better suited to my Oracle skills. That is why I can't wait to get some pointers to how I can achieve what I want to achieve useing Oracle.
Pete
Message was edited by:
petehug

A tablespace is just a logical collection of objects that happen to reside in the data file, so there is technically no reason that you would need separate tablespaces here. Probably a good idea for organizational purposes, but not strictly necessary.
If we're going to set up version 5.12 of the database...
1) Create the tablespace (optional). Note that the exact syntax will depend on how you've configured your database (i.e. whether you're using Oracle Managed Files, ASM, etc).
CREATE TABLESPACE ts_lima_512_md
DATAFILE 'ts_lima_512_md.dbf' SIZE 100M;2) Create the user/ schema
CREATE USER lima_512_md
IDENTIFEID BY <<password>>
DEFAULT TABLESPACE ts_lima_512_md;3) Log in as the user you just created and create whatever objects you need to create. Assuming you don't specify a tablespace in your DDL, the default tablespace for the user will be used. Otherwise, it would be perfectly valid to have different users/ schemas own objects of the same name in the same tablespace.
4) Create a role that gives other users whatever permissions they'll need on objects and grant the role those privileges, i.e. for read-only access to tables
CREATE ROLE lima_512_md_read_only;
FOR x IN (SELECT * FROM user_tables)
LOOP
EXECUTE IMMEDIATE 'GRANT SELECT ON lima_512_md.' ||
x.table_name ||
' TO lima_512_md_read_only';
END LOOP;5) Grant this role to whatever other users you'd like
GRANT lima_512_md_read_only TO scott;6) Now, you can log in as scott, set the current_schema in the session, and query any of the tables in the LIMA_512_MD schema.
Justin

Changing default tablespace of SYSTEM user

Hi all,
What impact it wouuld have on database if i change the default tablespace of SYSTEM user?? actually i have got a strange env where th default tablespace for system user is tools and that for OUTLN is system
please share your view and experiences
Thanks and Regards
VD

hi thanks,
i know there is no performance issue using non system tablespace for system user, but we do follow some nomenclature structure thats why i am asking the question..so i am going to change its tablespace of user system from TOOLS to system with
SQL> alter user system default tablespace system;
command, and not expecting any complications..
Thanks and Regards
VD

Should Default Tablespace for User DIP be "SYSTEM" or "USERS"?

Oracle Enterprise Manager is giving me a warning about some non-system users who have a default tablespace of SYSTEM. One of the users is DIP. Is it OK for me to change the default tablespace for DIP to USERS, or should it remain SYSTEM?
Thank you,
Bill

To the best of my knowledge user DIP was created automatically by Oracle software when I upgraded my database from 8i to 10gR2. In my mind that means it is needed for managing some system function in the database. That is why I hesitate to change the default tablespace from SYSTEM to USERS.
If user DIP is tied to use of Oracle Directory Integration and Provisioning then I am not knowingly using the DIP account. I do not know what Directory Integration and Provisioning is and read about it only when researching this tablespace question. That being said, I expect that Oracle software does a lot of things internally that I am not aware of.
I was hoping someone familiar with user DIP could tell me that changing the default tablespace to USERS for this Oracle supplied account would do no harm.
Thank you,
Bill

How to use non default port 1521 while 11.2.0.1 grid upgrade to 11.2.0.2

Hi Team ,
We are planning 11.2.0.1 Grid infra rolling upgrade to 11.2.0.2 with out any downtime.
But while up gradation due to default scan port 1521 , 11.2.0.1 databases are not able to connect (remote connections)
We are using 1900 port for existing 11.2.0.1 grid infra scan.
While up gradation it is taking default port of 1521 insted of existing port 1900.
Please provide the solution to use non default port while 11.2.0.2 up gradation.
After upgrade the status as below.
grdoratst104:/apps/grid/grdhome:+ASM4> srvctl config scan_listener
SCAN Listener LISTENER_SCAN1 exists. Port: TCP:1521
SCAN Listener LISTENER_SCAN2 exists. Port: TCP:1521
SCAN Listener LISTENER_SCAN3 exists. Port: TCP:1521
Here I was getting TNS:no Listener errors from the client connections.
I have modifyed the scan port then it is working fine.
grdoratst104:/apps/grid/grdhome:+ASM4> srvctl modify scan_listener -p TCP:1800
grdoratst104:/apps/grid/grdhome:+ASM4> srvctl config scan_listener
SCAN Listener LISTENER_SCAN1 exists. Port: TCP:1800
SCAN Listener LISTENER_SCAN2 exists. Port: TCP:1800
SCAN Listener LISTENER_SCAN3 exists. Port: TCP:1800
grdoratst104:/apps/grid/grdhome:+ASM4>
Here the problem is we need to do the grid infra upgrade with out downtime,but due this default port issue clients are not able to connect to the database.
Thanks
Bala
Edited by: user12032334 on May 31, 2011 11:46 AM

Why are you using a non default port? It does not improve security. It makes network management more complex. And causes the type of issues that you are facing now.
So before changing defaults, make sure that your reasons are technically sound. And using port 1900 when 1521 is available, is not technically sound by any means.
As for addressing the problem you have created for yourself by mucking around with port numbers. Use a NAT firewall (on each RAC node) to rewrite packets headers received on port 1900 and send these to the server's port 1521 instead (on the VIP or static IP as required).
This can be fairly easily done using iptables if your o/s is Linux. You need to:
a) create a pre-routing NAT rule
b) create a post-routing NAT rule
c) create a forwarding filter rule for port 1900/tcp
d) create an input filter rule to accept traffic on 1900/tcp

Use of sql group function in orcl:query-database - urgent

All,
Version: 10.1.3.4
Two requirements for me:
1. I want to use sum function in orcl:query-database. How to use it?
For ex: I tried the following
<xsl:value-of select='orcl:query-database("select sum(salary) from emp",false(),false(),"jdbc/DB1")'/>
I got the following error
oracle.xml.sql.OracleXMLSQLException: Character ')' is not allowed in an XML tag name.
When I tried without sum function, it works fine
2. I used the same table, but without the sum function as below
<xsl:value-of select='orcl:query-database("select salary from emp",false(),false(),"jdbc/DB1")'/>
This time, it returns the first employees salary!! I dont understand this logic. I expected either the query returns all the rows else it throws error, but none of them were true!
Can anyone pls explain what is the behavior? I want your reply for both the queries!
Currently I'm in a project where I'm working in the similar scenario, so please guru's let me know ASAP.
Thanks,
Sen

Hi Sen,
Create a normal variable variable in XSLT.
Then use that variable.
I mean variable name='Var_1' select='Your Query'
Now use Var_1/yourcollection/...
I am giving some example
<xsl:variable name="Stopdetails" select="/ns0:MyEBM/ns0:DataArea/ns0:MyEBO/ns0:Stops/ns0:Stop[ns0:StopID=$TempStopId]"/>
<xsl:variable name="AccStopTypeVar">
<xsl:value-of select="$Stopdetails/ns0:StopType"/>
</xsl:variable>If you want you can loop on the created variable.
You can do these in XSL.
But DB calls those things ...it would be better , if u take them out. Spme debugging problems are there with XSL.
Regards
PavanKumar.M

Query Database in non default Tablespace.

Similar Messages

Maybe you are looking for