Skip to main content

How to change Database Default Tablespace for users


1. Create new Tablespace <SHAH_SHAKIR_DBF> for schema SHAKIR

 create tablespace SHAH_SHAKIR_DBF datafile
'D:\ORACLE\ORA92\MUJAZORC\KAFA_ITGFIN_DBF.DBF' size 5120m autoextend on;

 2. Take Export of schema SHAKIR on Seperate drive:
EXP SYSTEM/SYSMAN@mujazorc OWNER=SHAKIR FILE=F:\Dump\kafafin_16022015.DMP GRANTS=Y BUFFER=10000 COMPRESS=Y ROWS=Y  LOG= F:\Dump\shakir_16022015.log

 3. Now create new schema or if you have already existing schema then drop and recreate it:
drop SHAKIR CASCADE;

CREATE USER SHAKIR
  IDENTIFIED BY VALUES SHAKIR
  DEFAULT TABLESPACE SHAH_ITGFIN_DBF
  TEMPORARY TABLESPACE TEMP
  PROFILE DEFAULT
  ACCOUNT UNLOCK;
  -- 1 Role for SHAKIR
  GRANT DBA TO SHAKIR WITH ADMIN OPTION;
  ALTER USER KSHAKIR DEFAULT ROLE ALL;
  -- 1 System Privilege for SHAKIR
  GRANT UNLIMITED TABLESPACE TO SHAKIR WITH ADMIN OPTION;
  -- 1 Tablespace Quota for SHAKIR
  ALTER USER SHAKIR QUOTA UNLIMITED ON SHAH_ITGFIN_DBF;

alter user SHAKIR quota 0 on SHAKIR_FIN_DBF quota unlimited on SHAH_ITGFIN_DBF;
alter user SHAKIR quota 0 on SHAH_FIN_DBF quota unlimited on SHAH_ITGFIN_DBF;
Note: Here in above example two different tablespace having the tables of same users.

In the case while changing the default tablespace for the user's in the same database, don't forget to assign
quota unlimited on new tablespace and revoke unlimited quota on old tablespace. This might not required while changing the tablespace of user's of different database.

revoke unlimited tablespace from SHAH_ITGFIN_DBF;

4. Now try to import the dump you have taken. Make sure dump is properly copied on the drive.

IMP SYSTEM/sysman@SHAHDB FILE=F:\Dump\shakir_16022015.DMP FROMUSER=SHAKIR TOUSER=AWAED LOG=F:\Dump\shakir_16022015.DMP.log
Don't forget to assign back quota unlimited on 'awaed' tablespace.
alter user shakir DEFAULT tablespace shakir_ts QUOTA UNLIMITED ON rahman;

Comments

Post a Comment

Popular posts from this blog

RMAN Different errors and their Solution

RMAN Different errors and their Solution Backup Fails with Invalid RECID Error: RMAN-20035, RMAN-6038 When you attempt a backup and receive the following error messages: RMAN-3014: Implicit resync of recovery catalog failed RMAN-6038: Recovery catalog package detected an error RMAN-20035: Invalid high RECID error It indicates the control file and the recovery catalog is not synchronized. RMAN detects that the control file currently in use is older than the control file previously used to resynchronize. Cause: This due to any of the scenario you are restore a backup controlfile through a non-oracle mechanism and then open the database through Resetlogs option or making a copy of control file through operating system utility and trying the restore on new system through RNAN. You do not use catalog so RMAN does not get any information regarding this process.  The recovery catalog indicates that the highest RECID is 100, but the control file indicates that the highe...
Post a Comment
Read more

Changing National Character Set AL16UTF16 to UTF8

Changing National Character Set AL16UTF16 to UTF8 The national character set is used for data that is stored in table columns of the types NCHAR, NVARCHAR2, and NCLOB.  In contrast, the database character set is used for data stored in table columns of the types CHAR, VARCHAR2 and CLOB. Like the database character set, the national character set is defined when the database is initially created and can usually no longer be changed, at least not easily or without involving quite a lot of work (export, recreate database, import). Except when creating the database, where the national character set is defined explicitly, it can change implicitly even when upgrading the database from Oracle8i to Oracle9i (or Oracle10g). You require SYSDBA authorization to change the national character set. Changing the national character set means changing an Oracle Dictionary entry, but no data is changed.  $sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> Select property_...
Post a Comment
Read more

How to Monitor RMAN Backup through SQL Query

To Monitor RMAN you can use OEM or any other tools such as "Quest Backup Report for Oracle". You can also used following Views in oracle 9i to check the RMAN backup status: v$rman_configuration v$backup_set v$backup_piece v$backup_spfile v$session_longops Script to check RMAN Configuration: SELECT  name "PARAMETERS", value "RMAN CONFIGURATION" FROM  v$rman_configuration ORDER BY name; PARAMETERS RMAN CONFIGURATION BACKUP OPTIMIZATION ON CHANNEL DEVICE TYPE DISK FORMAT   'H:\ORABACK\%U' CONTROLFILE AUTOBACKUP ON CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'H:\ORABACK\%F' DEFAULT DEVICE TYPE TO DISK RETENTION POLICY TO RECOVERY WINDOW OF 30 DAYS Script to List RMAN Backup Piece: SELECT bs.recid, DECODE(   bp.status, 'A', 'Available', 'D', 'De...
Post a Comment
Read more