Database refresh on Tablespace Level

Hi Guys,
Please can you advise if for refreshing database on tablespace level we require to move the source tablespaces in read only mode? Is there any workaround?
Cheers,
Shaz

If you want to use TTS as mentioned above, you have to put the source in READONLY and take the dump and import in the other database with remap_tablespace option.
You can do it by taking the dump pf all objects in the source tablespace and import them in the target. But if your transactions are underway on the objects in the intended tablespace in the source database, you won't be getting a logically consistent data. to get a logically consistent data you have to use consistent=y if you are using exp and use parameters FLASHBACK_SCN and FLASHBACK_TIME with the Data Pump.
CSM

Similar Messages

Force logging at tablespace level for standby database

Hi
Can we create a standby database by enabling force logging at tablespace level instead of enabling it at database level.I want to out the tablespace containing indexes in nologging mode so that when I rebuild the indexes no logs will be generated.

Technically, you can create a Standby without having set FORCELOGGING at the Primary database.
You can also then selectively FORCELOGGING for all your important tablespaces (beginning with SYSTEM, SYSAUX, UNDO ....)
However, for a Physical Standby Redo Apply will mark the blocks (e.g. those populated by the CREATE INDEX .. NOLOGGING) as "corrupt". You will get Read Errors (ORA-1578 and ORA-26040) when you attempt to read the index (e.g. for a Table query).
So you have to monitor your NOLOGGING operations and the datafiles where NOLOGGING is applied. You can take Incremental RMAN Backups of such datafiles and restore them to the Standby immediately after the NOLOGGING operations.
Hemant K Chitale

Tablespace level restore on different database

We have to do a restore but our database is over 4TB. Is there a way to do just a tablespace level restore but to a different database?

Hi,
Can you elaborate more about the Requrirement and What version you are working on.. ??
What is the reason behind for restoring.. ??
Still, try to think about Transportable Tablespace Option Might work (As I had not able understand the Clear requirement)
- Pavan Kumar N
Edited by: Pavan Kumar on Jan 7, 2009 10:57 PM

How to set database default temporary tablespace in 8i?

SQL> alter database default temporary tablespace temp3;
alter database default temporary tablespace temp3
ERROR at line 1:
ORA-02231: missing or invalid option to ALTER DATABASE

As far as I know, in Oracle 8i, you can not set the temporary tablespace as default at the database level; rather you can set it at the user level.
SQL> alter user scott default temporary tablespace temp3;
In Oracle 8i, the created users without specifying the default temporary tablespace, those users will by default assign to SYSTEM as default temporary tablespace.
You may need to assign the temp3 temporary tablespace to all the users.
Regards,
Sabdar Syed.

Full database refresh

Hello Gurus,
I am need to take make full database refresh from one database to other, Can someone let me know step how to do it?
select * from V$VERSIONBANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bi
PL/SQL Release 10.2.0.5.0 - Production
CORE     10.2.0.5.0     Production
TNS for HPUX: Version 10.2.0.5.0 - Production
NLSRTL Version 10.2.0.5.0 - Production

CKPT wrote:
jgarry wrote:
I'm with Ed and Brendan on this. 3 main reasons:
1. Legacy has some special requirements.
2. Definitely want different schema names, this has saved my bacon sooo many times. Even so, people still get it wrong (including me, and I'm totally paranoid about it to begin with).
3. There are many more copies of production than actual production, for various reasons (test, several dev, special projects, future app versions...) . We would rather have one db with many schemata than many db's, right?
Now if we could just rename user...Agreed some extent, I can say to refresh entire database the preferred method is RMAN restore, where it can manage very easily
how?
1) To import again we need to create a new database
2) Need to create all the tablespaces with same names or we can use REMAP option
3) need to monitor entire import process,
4) need to take care of other things like , temp utilization and all.
5) need to perform export, Need to copy those dumpfiles, We should have enough space on mount points of both source & destinations. ;-)
I would just caution there that you shouldn't think that because you are taking rman backups you have no need to also regularly export the db. A good backup policy includes both physical backup (rman) and logical backup of the data (export).
If you talk with couple of schemas the preferred method is EXPDP/IMPDP, totally agreed.
If in case of database size is huge, then better to go with RMAN to refresh database. Either DUPLICATE or manual way restore.
as ED said, still we could have chance to test RMAN backups too. Multiple advantages.
Let me know if I'm wrong. :)

Rman backup on tablespace level.

Hi,
I plan to backup at tablespace level instead of whole database. Other than the tablespaces used for the application, do I have to backup system and other tablespaces in 9i to guarantee recovery like the ones we did without rman, alter tablesapce....? The DB is on archivelog mode. Thanks.
Tracy

The SYSTEM tablespace is the most critical and important tablespace. That is good practice to ever have a backup of this tablespace.
If you don't have a backup of the other tablespaces you can recover your database too, but that isn't so easy. BUT YOU MUST HAVE ALL ARCHIVELOG!
This type of backup is suitable only for advanced DBAs. You must know what are you doing and what is your real goal; and that is not only to recover the database!!! that is much more.
I think that the best command for you is backup database.
After that you can evaluate incremental backup.
Bye, Aron

Flashback database and nologging tablespaces

DB Versions
Oracle 11.2.0.3
2 other DBs at 11.2.0.3 with 10.2.0.3 compatibility mode.
We are using flashback database in our dev/test environments so we can flashback and apply builds again. I am ok if we lose data and can't roll forward. We are running out of archive space. Lately we have been going over a month or more between builds. Is it possible to set tablespaces to nologging and still have flashback work? I dont need the data. I just need to be able to reset to the structure before the last build. I am 100% ok with losing test data. I have no say over when builds get done.
Reason I am asking not just testing (I did do some google searches):
Testing this isn't that simple due to process issues. I have to get a build scheduled which can take a week or more(no extra DB for me to test this) and the build team generally doesn't listen, so if I tell them to wait for me for the test, it generally doesn't happen, then it can be another week before I get a build and so on. Restoring from backup isn't an easy change because that is a process change and I have to go through incredible amounts of 'process' and approval to get any kind of change to a process (think dilbert on steroids). So I have to ask ahead of even running a test.

Hi,
Doc Ref:ALTER TABLESPACE
Changing Tablespace Logging Attributes: Example The following example changes the default logging attribute of a tablespace to NOLOGGING:
ALTER TABLESPACE tbs_03 NOLOGGING;
Altering a tablespace logging attribute has no affect on the logging attributes of the existing schema objects within the tablespace. The tablespace-level logging attribute can be overridden by logging specifications at the table, index, and partition levels.
So if you want to Nologging then you have to go at table level.
i'd suggest use the the different location for Archive and Flashback log. and clean the Archive area using some OS job. Flashback database required only the flashback log files during restore.
HTH

Database Refresh Failed

Hi All,
I am working on a database refresh and it failed with the following errors
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 04/15/2011 16:27:41
RMAN-03015: error occurred in stored script Memory Script
ORA-00283: recovery session canceled due to errors
RMAN-11003: failure during parse/execution of SQL statement: alter database recover logfile '/srv/database/arch2/1_65508_689972797.dbf'
ORA-00283: recovery session canceled due to errors
ORA-00368: checksum error in redo log block
ORA-00353: log corruption near block 256 change 43879018791 time 04/12/2011 04:30:54
ORA-00334: archived log: '/srv/database/arch2/1_65508_689972797.dbf'
Do you have any idea of how to solve this error.
Please help.

Hi;
What is your OS? If its solaris than please see:
Duplicate Fails with Corruption Errors on Solaris QFS Filesystem [ID 764113.1]
Regard
Helios

Tablespace level backup using data pump

Hi,
Im using 10.2.0.4 on RHEL 4,
I have one doubt, can we take a tablespace level backup using data pump,
bt i dnt wnt to use it for transportable tablespace.
thanks.

Yes, you can only for the tables in that tablespace only.
Use the TABLESPACES option to export list of tablespaces.*here all the tables in that tablespaces will be exported*.
and you must have the EXP_FULL_DATABASE role to use tablespace mode.
Have a look at this,
http://stanford.edu/dept/itss/docs/oracle/10g/server.101/b10825/dp_export.htm#i1007519
Thanks
Edited by: Cj on Dec 12, 2010 11:48 PM

Startup database with bad tablespace

Hi, for a mistake delete a physical tablespace file and now my database not startup. how can i drop that bad tablespace and put my database ok
thanks

If you do not have backup of your database/tablespace/datafile, data that was in that tablespace is gone.
Now you would need to drop file definition from data dictionary in order to allow you to open database
startup mount
alter database datafile 'name of file that you dropped' offline drop;
alter database open;
DROP TABLESPACE tablespace_name INCLUDING CONTENTS'Regards
Mike N

Risks associated with database refresh.

Hi experts,
I need to clarify a doubt .I have a cloned SAP BW system (from another system i.e SAn to SAN copy)and then after few months after the first clone I need to refresh the database(Oracle 10 G).The reason being I will have some changes in data at the source system from where it was copied earlier.I shall be applying the application changes by tracking the transport requests(from the original system).
I need to clarify if we don't refresh the whole system again by SAN to SAN copy and then do a database refresh will there be any problem .Is there any risk associated with it.
Will the requests be available to me on the monitor with the new data or there will be some issues.
A quick response shall be very useful.
Shailja.

Hello,
Orders for Production , Maintenance, Deliveries, Transfer Order etc. are created according to the factory calendar .
You must be sure that all operations can be carried out in the seven days of the week (e.g. deliveries), because SAP can be scheduling aTransfer Order for a Sunday and somebody can be calling you for fixing the issue!
The normal case is that some operations can take place in the weekend (Production, Maintenance) but other Logistic Operations ( Deliveries) are done only from Mo to Fr. If this is your case, I would create an additional seven days calendar and assign it to the work centers in Production and maintenance, but the Plant would remain linked to the old five days calendar
Hope this can solve your issue.
Dario

Database refresh from Prod to UAT

Please check whether i have missed out any step in database refresh in 11.5.10.2
Step 1 preclone executed on source Instance
Step 2 copied all datafiles in backup mode to UAT instance
Step 3 controlfile create and opened db in resetlogs.
Step 4 adcfgclone.pl dbconfig <target context file>
Step 5 Autoconfig executed on both db aswell apps
Is it required to execute adcfgclone.pl dbTechstack and adcfgclone.pl appsTier
environment is apps 11.5.10.2
db 10g
os AIX 5.3

Hello,
You will need to run:
perl adcfgclone.pl dbTier [Database Target Context File]
perl adcfgclone.pl appsTier [Appltop Target Context File]
and other tasks as per Section 4: Advanced Cloning Options / 1. Refreshing a Target System
of Note 230672.1 : "Cloning Oracle Applications Release 11i with Rapid Clone"
Regards, Carlo.

Database Refresh From ASM Filesystem to Local Filesystem

Hi ALL,
I am performing a database refresh from production server to a demo server. Our Production database is 11.2.0.1 and it is using ASM filesystem to keep the data, redo and other files in ASM disks.
On the other hand demo server is not having ASM, all the database files are stored in a local filesytem.
I have taken a fresh backup of our production database, but I am not sure to perform the restore part as the demo server is not having ASM.
Can anyone suggest me how to perform this, I mean datafile restore from ASM to local filesystem.
Any usefull links will be helpful.
Regards,
Arijit

Hello,
You can restore the backup of your Production database which is using ASM to your demo server (using file system).
Make sure that the control_files parameter in the pfile/spfile is pointing to the file system location where you want to have contol files located on the demo server.
Next, before you use the restore command to restore the database, provide the location of the datafile where you need to restore using the "set newname" clause.
run
set newname for datafile 1 to '<file-system-location-on-demo-server>';
set newname for datafile 2 to '<file-system-location-on-demo-server>';
restore database;
switch datafile all;
recover database;
}

Database Refresh Status log (Info)

Dear All,
Is there thing that can help to find out completion status for database refresh.
Application log like hyplive.log located in the following location
Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\essbase\essbase_0\app\HypLive
the log file says this
"[Wed Apr 04 14:53:50 2012]Local/HypLive/Plan1/admin@Native Directory/Info(1013091)
Received Command [Restructure] from user [admin@Native Directory]
[Wed Apr 04 14:53:50 2012]Local/HypLive/Plan1/admin@Native Directory/Info(1019017)
Reading Parameters For Database [Drxxxxxx]
[Wed Apr 04 14:53:50 2012]Local/HypLive/Plan1/admin@Native Directory/Info(1019012)
Reading Outline For Database [Drxxxxxx]
[Wed Apr 04 14:53:50 2012]Local/HypLive/Plan1/admin@Native Directory/Info(1019024)
Reading Outline Transaction For Database [Drxxxxxx]
[Wed Apr 04 14:53:50 2012]Local/HypLive/Plan1/admin@Native Directory/Info(1007043)
Declared Dimension Sizes = [1408 4 82 2 2 3 10 14 16 17 33 66 183 193 265 852 922 920 2 1 4 3 3 3 6 ]
[Wed Apr 04 14:53:50 2012]Local/HypLive/Plan1/admin@Native Directory/Info(1007042)
Actual Dimension Sizes = [1395 4 81 1 1 3 10 12 16 8 26 64 145 163 245 848 898 914 0 0 0 0 0 0 5 ]
[Wed Apr 04 14:53:50 2012]Local/HypLive/Plan1/admin@Native Directory/Info(1007125)
The number of Dynamic Calc Non-Store Members = [191 0 54 0 0 0 0 2 0 9 6 2 34 20 19 4 0 5 ]
[Wed Apr 04 14:53:50 2012]Local/HypLive/Plan1/admin@Native Directory/Info(1007126)
The number of Dynamic Calc Store Members = [0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ]
[Wed Apr 04 14:53:50 2012]Local/HypLive/Plan1/admin@Native Directory/Info(1007127)
The logical block size is [112995]
[Wed Apr 04 14:53:50 2012]Local/HypLive/Plan1/admin@Native Directory/Info(1010008)
Maximum Declared Blocks is [26928283342271066000000000] with data block size of [115456]
[Wed Apr 04 14:53:50 2012]Local/HypLive/Plan1/admin@Native Directory/Info(1010007)
Maximum Actual Possible Blocks is [5868290301232498000000000] with data block size of [32508]
[Wed Apr 04 14:53:50 2012]Local/HypLive/Plan1/admin@Native Directory/Info(1200481)
Formula for member [2050103] will be executed in [CELL] mode
[Wed Apr 04 14:53:51 2012]Local/HypLive/Plan1/admin@Native Directory/Info(1007067)
Total Restructure Elapsed Time : [0.235] seconds
[Wed Apr 04 14:53:52 2012]Local/HypLive/Plan2/admin@Native Directory/Info(1007067)
Total Restructure Elapsed Time : [0.266] seconds
but i am looking for the status of database refresh failed or succeeded?
Any suggestions.
Regards
Ace

If it failed then you would of got an error generated in the essbase application log and the planning log.
Cheers
John
http://john-goodwin.blogspot.com/

Database refresh from standby database

All,
OS : Sun version : 11.1.0.7
I'm doing database refresh using stand by database datafiles in different server.
1)Disabled Data guard broker in standby database .
2)Copied all datafiles in mount stage to target server (different server)
3)created controlfile and started the database in mount stage in different server
4)Applied all archive log files .
5)But still the database not recovered .
SQL> recover database using backup controlfile until cancel;
ORA-00279: change 10401147296308 generated at 01/13/2012 09:03:43 needed for
thread 1
ORA-00289: suggestion :
/u01/app/oracle/admin/qecgdeva/arch/qecgdeva_727091849_1_57879.arc
ORA-00280: change 10401147296308 for thread 1 is in sequence #57879
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
/u01/app/oracle/admin/qecgdeva/arch/qecgdeva_727091849_1_57879.arc
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
/u01/app/oracle/admin/qecgdeva/arch/qecgdeva_727091849_1_57885.arc
ORA-00279: change 10401156453328 generated at 01/13/2012 10:48:01 needed for
thread 1
ORA-00289: suggestion :
/u01/app/oracle/admin/qecgdeva/arch/qecgdeva_727091849_1_57886.arc
ORA-00280: change 10401156453328 for thread 1 is in sequence #57886
ORA-00278: log file
'/u01/app/oracle/admin/qecgdeva/arch/qecgdeva_727091849_1_57885.arc' no longer
needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
CANCEL
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01196: file 1 is inconsistent due to a failed media recovery session
ORA-01110: data file 1:
'/mounts/qecgdeva_data/oradata/qecgdeva/dbfiles/qecgprod_system.dbf'
ORA-01112: media recovery not started
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01196: file 1 is inconsistent due to a failed media recovery session
ORA-01110: data file 1:
'/mounts/qecgdeva_data/oradata/qecgdeva/dbfiles/qecgprod_system.dbf'Am I missing any steps here ? Please advice me on this .
Thanks.

Hi,
When you copy files of standby server to another target server ? - Yesterday.
Is standby is SYNC with primary? or MRP is still running? - ---------yes, standby db is running fine .
Even you can open database with resetlogs after recreating controlfile, no need of recovery too -- >I was unable to open . So went to apply arch files.
Do you have archive of thread 1 is in sequence #57887, -- No , Because sequence 57887 yet generate. I have applied all recent available archive log files.
ORA-00289: suggestion :
/u01/app/oracle/admin/qecgdeva/arch/qecgdeva_727091849_1_57886.arc
ORA-00280: change 10401156453328 for thread 1 is in sequence #57886
ORA-00278: log file
'/u01/app/oracle/admin/qecgdeva/arch/qecgdeva_727091849_1_57885.arc' no longer
needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
CANCEL
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01196: file 1 is inconsistent due to a failed media recovery session
ORA-01110: data file 1:
'/mounts/qecgdeva_data/oradata/qecgdeva/dbfiles/qecgprod_system.dbf'
ORA-01112: media recovery not started
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01196: file 1 is inconsistent due to a failed media recovery session
ORA-01110: data file 1:
'/mounts/qecgdeva_data/oradata/qecgdeva/dbfiles/qecgprod_system.dbf'Edited by: 805877 on Jan 12, 2012 10:43 PM

Database refresh on Tablespace Level

Similar Messages

Maybe you are looking for