Production database requirements

Hi,
Please give me some suggestions for the following requirements. This for a production database. Database - Oracle 9.2.0.1.0
1. Harware reqiurements
2. Database requirements
3. OS requirements
Regards,
Mathew

Windows
http://download.oracle.com/docs/html/A95493_01/toc.htm
Unix
http://download.oracle.com/docs/html/A96167_01/toc.htm
BTW - It comes with the CD or Download

Similar Messages

ORA-10458: standby database requires recovery

hi
kindly help me... i got error when standby open in read only mode
SQL*Plus: Release 11.2.0.3.0 Production on Sat Jan 19 14:37:46 2013
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup mount
ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance
ORACLE instance started.
Total System Global Area 5344731136 bytes
Fixed Size 2237776 bytes
Variable Size 1275071152 bytes
Database Buffers 4060086272 bytes
Redo Buffers 7335936 bytes
Database mounted.
SQL> Alter Database Recover Managed Standby Database Disconnect;
Database altered.
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
Database altered.
SQL> ALTER DATABASE OPEN READ ONLY;
ALTER DATABASE OPEN READ ONLY
ERROR at line 1:
ORA-10458: standby database requires recovery
ORA-01152: file 22 was not restored from a sufficiently old backup
ORA-01110: data file 22: '/archive/data/undo01.dbf'

hi CKPT
I executed the action plan as you recommend and got below information;
SQL> recover standby database;
ORA-00279: change 5983485554580 generated at 01/01/2013 19:27:17 needed for
thread 1
ORA-00289: suggestion : /archive/PROD_1_750568044_45027.ARC
ORA-00280: change 5983485554580 for thread 1 is in sequence #45027
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
'/archive/PROD_1_750568044_45400.ARC'
ORA-00310: archived log contains sequence 45400; sequence 45027 required
ORA-00334: archived log: '/archive/PROD_1_750568044_45400.ARC'
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 22 was not restored from a sufficiently old backup
ORA-01110: data file 22: '/archive/data/undo01.dbf'
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01666: control file is for a standby database
SQL> alter system switch logfile;
alter system switch logfile
ERROR at line 1:
ORA-01109: database not open
---------------------------------- and some other activity but still not found any solution-------------
RMAN> recover database until sequence
2> 45026;
Starting recover at 23-JAN-13
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 01/23/2013 16:42:47
RMAN-06556: datafile 1 must be restored from backup older than SCN 5983484595990
RMAN> recover database until sequence 45027;
Starting recover at 23-JAN-13
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 01/23/2013 16:42:59
RMAN-06556: datafile 22 must be restored from backup older than SCN 5983485554580
RMAN> recover database until sequence 45025;
Starting recover at 23-JAN-13
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 01/23/2013 16:43:09
RMAN-06556: datafile 1 must be restored from backup older than SCN 5983484160276
RMAN> alter database open resetlogs;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 01/23/2013 16:43:25
ORA-01666: control file is for a standby database

Production database version 10.1.0.3 to 10.2

We are planning to upgrade the production database version 10.1.0.3 to 10.2 version.
Please provide the link to download the any standard document related to upgrade the oracle version 10.1.0.3 to 10.2.

You can directly upgrade 10.1.0.3 to 10.2.0.2 by using 10.2.0.2 complete software distribution but not 10.2.0.2 patch set.
10.2.0.2 Patch set requires 10.2.0.1 base release first.
To proceed with the upgrade review instructions from Oracle Database upgrade guide 10.2 from OTN.
http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14238.pdf
Regards
Vignesh Bala

RMAN-06067: RECOVER DATABASE required with a backup or created controlfile

Hi,
DB:9.2.0.8
OS: AIX 5.3
I am restoring DB with until time(12/06/2012) for needed tablespaces.
I restored the 12th date controlfile ,which is backed up with archivedlogs. I also have one more controlfile which backed up with full DB..
Restore of tablespaces are completed..
When recovery is going , failed with following error..
allocated channel: c7
channel c7: sid=22 devtype=SBT_TAPE
channel c7: VERITAS NetBackup for Oracle - Release 5.1 (2006040520)
allocated channel: c8
channel c8: sid=21 devtype=SBT_TAPE
channel c8: VERITAS NetBackup for Oracle - Release 5.1 (2006040520)
executing command: SET until clause
Starting recover at 23-06-2012 02:00:15
released channel: c1
released channel: c2
released channel: c3
released channel: c4
released channel: c5
released channel: c6
released channel: c7
released channel: c8
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 06/23/2012 03:36:57
RMAN-06067: RECOVER DATABASE required with a backup or created controlfile
RMAN>
Restore Script:
connect target /
connect catalog rmanc/recom@lgn_rmanc
run {
allocate channel c1 type 'SBT_TAPE';
allocate channel c2 type 'SBT_TAPE';
allocate channel c3 type 'SBT_TAPE';
allocate channel c4 type 'SBT_TAPE';
allocate channel c5 type 'SBT_TAPE';
allocate channel c6 type 'SBT_TAPE';
allocate channel c7 type 'SBT_TAPE';
allocate channel c8 type 'SBT_TAPE';
allocate channel c9 type 'SBT_TAPE';
allocate channel c10 type 'SBT_TAPE';
allocate channel c11 type 'SBT_TAPE';
allocate channel c12 type 'SBT_TAPE';
set until time '12-06-2012 00:01:26';
restore tablespace SYSTEM,UNDO_GEN01,UNDO_GEN02,TAB_80K_GENCON,TAB_25M_GENCON;
release channel c1;
release channel c2;
release channel c3;
release channel c4;
release channel c5;
release channel c6;
release channel c7;
release channel c8;
release channel c9;
release channel c10;
release channel c11;
release channel c12;
Recover Script:
connect catalog rmanc/recom@lgn_rmanc
connect target /
run {
allocate channel c1 type 'SBT_TAPE';
allocate channel c2 type 'SBT_TAPE';
allocate channel c3 type 'SBT_TAPE';
allocate channel c4 type 'SBT_TAPE';
allocate channel c5 type 'SBT_TAPE';
allocate channel c6 type 'SBT_TAPE';
allocate channel c7 type 'SBT_TAPE';
allocate channel c8 type 'SBT_TAPE';
set until time '12-06-2012 00:01:26';
recover tablespace SYSTEM,UNDO_GEN01,UNDO_GEN02,TAB_80K_GENCON,TAB_25M_GENCON;
release channel c1;
release channel c2;
release channel c3;
release channel c4;
release channel c5;
release channel c6;
release channel c7;
release channel c8;
Any suggestion in this is helpful to me..
Thanks in advance,

Hello;
I read your post and here's the thoughts that came to mind : ( my largest concern is you might restore something that damages your current system )
1. So you want to restore the whole DB back to 12/06/2012 to get some tablespaces from then right?
2. Are you restoring to a different system?
3. How did you start the database ( NOMOUNT, MOUNT )
4. If you are restoring the whole DB back to 12/06/2012 how did you restore the control file?
5. Your command shows :
restore tablespace SYSTEM,UNDO_GEN01,UNDO_GEN02,TAB_80K_GENCON,TAB_25M_GENCON;
COMMENT : Generally I use recover tablespace for point in time recovery and use an auxilary destination.
Meaning I don't use restore at all, in fact using restore may cause an issue.
SUMMARY : I don't see how this will work as is.
It seems you want data from five tablespaces from about six months ago including the SYSTEM tablespace.
This is an Incomplete Recovery. I believe I would rethink this completely.
Give the time that has past I would consider restoring the whole database to a different server where cannot damage anything.
Once this is done I would decide how to get the data I need.
Or I would check for a daily export file and recover the tablespace data that way.
So you have some good details on your question but it seems the plan is either missing something or you need to add a few more details.
Example
I'm recovering old tablespaces into a test system.
Here's how I'm not damaging my current production system.
I don't have an export from that date.
So take a step back and either rethink or give a few more details on how this is safe.
Best Regards
mseberg

What is the Best way to extract a subset of data from a Production database

Hi,
One of our cleint want to to extract a subset of data from a Production databases in order to build a dev or test database. Since it is a banking sector they do not want to clone the db.
Can anybdoy suggests any tool or any info
Regards
Manoj

DataBee is one option. Depending on circumstances, you may also want their DataMasker utility in addition...
Of course, depending on your particular system and your particular requirements, this sort of thing can rather quickly get quite complicated since you may need very particular types of subsets of data...
Justin

Compiling against developer database, running against production database??

Hello :-)
In our company we have a developer- , a test- and a production database, like most of us, I think... :-)
In former times it was usual to compile forms against the database, that they are running against. But nowadays this is because of new security rules very difficult. Developers have all rights on the developer database, a few on test and nearly none on the production database and even our DBA is (officially) not allowed to use/know the sys password.
The developer and the production database are very similar (both 10g Enterprise Edition Release 10.2.0.3.0 - 64bit, Linux), but not totally equal. Of course there are differences in database objects, because it's the developer database, there could be differences in installed patches, and the production database consists of 4 Clusters, the developer database not.
Is it enough to compile the forms (6i and also 10g) against the developer database and run the compiled forms against the production database or should we compile the forms, that go in production, strictly against the production database, which is a bit difficult because of our security rules???
Regards,
Udo

Hello, Francois!
Thanks for your answer, but that was not exactly what I meant...
What you describe is, how it should be :-)
We develop, deliver the forms and scripts and "someone" compiles them against the production database.
But our problem is that it would be a lot of "paperwork"(?) each time(!) to get the authorization to get the required rights on the production database to compile all objects.
We have no "production team" that has all these rights and are not allowed to do so...
So I just want to have your experiences, if it is enough to compile against the developer database???
I have made the experience that probably 98-99% works fine, but sometimes there are strange things happening (like not passing variables from one form to another, when a form is compiled against the developer database and the attached library for example is compiled against the production database)...
Regards,
Udo

If the production database i down, how to switch to standby database using the replication environment in ASsE

This question is in Business Continuity Plan (BCP)
if the production database is down, how to switch to standby database using the replication environment in ASE

Assuming you're referring to Sybase's Replication Server (repserver) product ...
Repserver moves data changes from one database to another.
Repserver can't 'switch' your application to use a different database; something outside of repserver has to do the actual switching.
If your application happens to be connecting to your ASE via Sybase's OpenSwitch (or similar) product, then OpenSwitch would be responsible for switching your application to use the standby database. Whether you have OpenSwitch perform the switch automatically, or via a manual command, is up to your BCP requirements.
If your application connects directly to ASE then you'll have to decide how/when to get your application to switch to the standby database. In the simplest form this would require shutting down the application, making sure replication is quiesced (ie, all in-flight transactions have been applied to the standby database), modify the interfaces/sql.ini file (used by your application) to point to the standby database, make any customized changes to the standby dataserver/database (eg, unlock application logins, take databases out of 'dbo use only' mode, etc), and startup the application (at this point it should connect to the standby database per the changes to the interfaces/sql.ini file).

Production database administration

What is the difference between development DBA and production DBA? Will the junior/mid level DBAs be involved in production database administration?

You can't say DEV DBA or production DBA. The word should be development environment and production environment.
Development environment- This environment is used for testing purpose for the company. In this environment developer can change/alter/deploy their code as necessary. They can change any object for the business requirements and test. If the test is successful they can apply it to the production database.
Production environment - This is the live environment for the company which is critical for business. No testing should be applied in the production environment.
Yes any junior DBA can administration the production database but in a limited domain. He/She must be guide by a senior DBA.
Regards
Asif Kabir

Oracle 11g 64 bit on Linux - Restore failure in production database

Hi guru,
We used to take full hot backup with the help of BackupExec of Symantec in our production database.We have two different oracle database (not cluster).
We defined same policy for both .We defined schedule on Symantec to take full hot backup every night of database on tap drive.At any point of time we maintain only 2 full backup for each database on tap and then recycle it.
Yesterday suddenly storage of database failed for both.?It was complete failure so we did not have any option but to restore last night full backup.
It has done successfully for one database but when we tried to restore second from last night backup it thrown error :
channel ch0: ORA-19870: error while restoring backup piece BE_9kjsfol6_1_1
ORA-19507: failed to retrieve sequential file, handle="BE_9kjsfol6_1_1", parms=""
ORA-27029: skgfrtrv: sbtrestore returned error
ORA-19511: Error received from media manager layer, error text
then we tried to restore backup of last to last night and it gave again error :
channel ch0: ORA-19870: error while restoring backup piece BE_9djsaman_1_1
ORA-19507: failed to retrieve sequential file, handle="BE_9djsaman_1_1", parms=""
ORA-27029: skgfrtrv: sbtrestore returned error
ORA-19511: Error received from media manager layer, error text
But we have seen log of Symantec at the time of backup and it said that backup has successfully completed.
right now I am in big trouble I tried almost all possible combination of symantec to restore database but got no success.I used script generated by symantec and tried to run that on RMAN directly but it is throwing same error.
Please help me if possible an throw some light on exception (as I understand it says it is not able to find some piece on tap but we have not touched tap and tap media is completely safe.)
I am pasting complete text log generated by Symantec at the time of restore attempt:
Recovery Manager: Release 11.1.0.6.0 - Production on Sun Oct 12 01:26:45 2008
Copyright (c) 1982, 2007, Oracle. All rights reserved.
# RMAN command section
RUN {
ALLOCATE CHANNEL ch0
TYPE 'SBT_TAPE';
SEND 'BSA_SERVICE_HOST=192.168.0.135,NBBSA_TOTAL_STREAMS=1,NBBSA_JOB_COOKIE={E8E38B61-7C1B-41A2-A2D7-8BB38A516AD3},NBBSA_DB_DEVICE_NAME=Oracle-Linux::\\G1-1-BLD-DSA2\sniffer2';
RESTORE
DATABASE
UNTIL TIME "TO_DATE('10-08-2008:12:00:41', 'MM-DD-YYYY:HH24:MI:SS')";
RECOVER
DATABASE
UNTIL TIME "TO_DATE('10-08-2008:12:00:41', 'MM-DD-YYYY:HH24:MI:SS')";
RELEASE CHANNEL ch0;
connected to target database: SNIFFER2 (DBID=3949735487, not open)
using target database control file instead of recovery catalog
allocated channel: ch0
channel ch0: SID=316 device type=SBT_TAPE
channel ch0: Symantec/BackupExec/1.1.0
sent command to channel: ch0
Starting restore at 12-OCT-08
channel ch0: starting datafile backup set restore
channel ch0: specifying datafile(s) to restore from backup set
channel ch0: restoring datafile 00001 to /home/oracle/app/oracle/oradata/sniffer2/system01.dbf
channel ch0: restoring datafile 00002 to /home/oracle/app/oracle/oradata/sniffer2/sysaux01.dbf
channel ch0: restoring datafile 00003 to /home/oracle/app/oracle/oradata/sniffer2/undotbs01.dbf
channel ch0: restoring datafile 00004 to /home/oracle/app/oracle/oradata/sniffer2/users01.dbf
channel ch0: restoring datafile 00005 to /home/oracle/app/oracle/oradata/sniffer2/system02.dbf
channel ch0: restoring datafile 00006 to /home/oracle/app/oracle/oradata/sniffer2/sysaux02.dbf
channel ch0: restoring datafile 00007 to /Ora2Meta/metatab01.dbf
channel ch0: restoring datafile 00008 to /home/oracle/app/oracle/oradata/sniffer2/UNDOTBS103.dbf
channel ch0: restoring datafile 00009 to /Ora2Data/blobdata01.dbf
channel ch0: restoring datafile 00010 to /Ora2Data/blobdata02.dbf
channel ch0: restoring datafile 00013 to /Ora2BTreeIndex/bindtab02.dbf
channel ch0: restoring datafile 00014 to /Ora2DomainIndex/domaintab01.dbf
channel ch0: reading from backup piece BE_9kjsfol6_1_1
channel ch0: ORA-19870: error while restoring backup piece BE_9kjsfol6_1_1
ORA-19507: failed to retrieve sequential file, handle="BE_9kjsfol6_1_1", parms=""
ORA-27029: skgfrtrv: sbtrestore returned error
ORA-19511: Error received from media manager layer, error text
channel ch0: starting datafile backup set restore
channel ch0: specifying datafile(s) to restore from backup set
channel ch0: restoring datafile 00011 to /Ora2Data/blobdata03.dbf
channel ch0: restoring datafile 00015 to /Ora2DomainIndex/domaintab02.dbf
channel ch0: reading from backup piece BE_9ljsfqm6_1_1
channel ch0: piece handle=BE_9ljsfqm6_1_1 tag=TAG20081006T155830
channel ch0: restored backup piece 1
channel ch0: restore complete, elapsed time: 00:11:35
channel ch0: starting datafile backup set restore
channel ch0: specifying datafile(s) to restore from backup set
channel ch0: restoring datafile 00012 to /Ora2Data/blobdata04.dbf
channel ch0: reading from backup piece BE_9mjsfrcb_1_1
channel ch0: piece handle=BE_9mjsfrcb_1_1 tag=TAG20081006T155830
channel ch0: restored backup piece 1
channel ch0: restore complete, elapsed time: 00:02:55
failover to previous backup
skipping datafile 1; already restored to file /home/oracle/app/oracle/oradata/sniffer2/system01.dbf
channel ch0: starting datafile backup set restore
channel ch0: specifying datafile(s) to restore from backup set
channel ch0: restoring datafile 00002 to /home/oracle/app/oracle/oradata/sniffer2/sysaux01.dbf
channel ch0: restoring datafile 00003 to /home/oracle/app/oracle/oradata/sniffer2/undotbs01.dbf
channel ch0: restoring datafile 00004 to /home/oracle/app/oracle/oradata/sniffer2/users01.dbf
channel ch0: restoring datafile 00005 to /home/oracle/app/oracle/oradata/sniffer2/system02.dbf
channel ch0: restoring datafile 00006 to /home/oracle/app/oracle/oradata/sniffer2/sysaux02.dbf
channel ch0: restoring datafile 00007 to /Ora2Meta/metatab01.dbf
channel ch0: restoring datafile 00008 to /home/oracle/app/oracle/oradata/sniffer2/UNDOTBS103.dbf
channel ch0: restoring datafile 00009 to /Ora2Data/blobdata01.dbf
channel ch0: restoring datafile 00010 to /Ora2Data/blobdata02.dbf
channel ch0: restoring datafile 00013 to /Ora2BTreeIndex/bindtab02.dbf
channel ch0: restoring datafile 00014 to /Ora2DomainIndex/domaintab01.dbf
channel ch0: reading from backup piece BE_9djsaman_1_1
channel ch0: piece handle=BE_9djsaman_1_1 tag=TAG20081004T174806
channel ch0: restored backup piece 1
channel ch0: restore complete, elapsed time: 00:29:55
Finished restore at 12-OCT-08
Starting recover at 12-OCT-08
starting media recovery
Oracle Error:
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 2 needs more recovery to be consistent
ORA-01110: data file 2: '/home/oracle/app/oracle/oradata/sniffer2/sysaux01.dbf'
released channel: ch0
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 10/12/2008 02:12:48
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of archived log for thread 1 with sequence 34786 and starting SCN of 327309500 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34785 and starting SCN of 327301335 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34784 and starting SCN of 327293588 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34783 and starting SCN of 327283177 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34782 and starting SCN of 327276129 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34781 and starting SCN of 327270761 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34780 and starting SCN of 327259154 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34779 and starting SCN of 327247460 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34778 and starting SCN of 327238239 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34777 and starting SCN of 327230121 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34776 and starting SCN of 327221510 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34775 and starting SCN of 327215378 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34774 and starting SCN of 327212076 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34773 and starting SCN of 327211654 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34772 and starting SCN of 327211171 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34771 and starting SCN of 327202005 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34770 and starting SCN of 327194156 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34769 and starting SCN of 327183755 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34768 and starting SCN of 327182026 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34767 and starting SCN of 327179450 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34766 and starting SCN of 327172246 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34765 and starting SCN of 327161460 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34764 and starting SCN of 327157752 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34763 and starting SCN of 327149852 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34762 and starting SCN of 327142049 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34761 and starting SCN of 327134814 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34760 and starting SCN of 327128948 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34759 and starting SCN of 327029461 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34758 and starting SCN of 326986719 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34757 and starting SCN of 326981601 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34756 and starting SCN of 326978697 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34755 and starting SCN of 326978093 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34754 and starting SCN of 326977904 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34753 and starting SCN of 326976801 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34752 and starting SCN of 326973891 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34751 and starting SCN of 326970649 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34750 and starting SCN of 326962803 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34749 and starting SCN of 326958315 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34748 and starting SCN of 326955232 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34747 and starting SCN of 326951908 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34746 and starting SCN of 326943909 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34745 and starting SCN of 326935460 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34744 and starting SCN of 326922741 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34743 and starting SCN of 326910246 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34742 and starting SCN of 326905072 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34741 and starting SCN of 326901097 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34740 and starting SCN of 326900178 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34739 and starting SCN of 326899668 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34738 and starting SCN of 326899106 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34737 and starting SCN of 326891014 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34736 and starting SCN of 326875443 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34735 and starting SCN of 326863782 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34734 and starting SCN of 326842985 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34733 and starting SCN of 326838670 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34732 and starting SCN of 326823584 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34731 and starting SCN of 326821851 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34730 and starting SCN of 326820427 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34729 and starting SCN of 326816378 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34728 and starting SCN of 326812324 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34727 and starting SCN of 326802760 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34726 and starting SCN of 326790469 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34725 and starting SCN of 326779939 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34724 and starting SCN of 326771711 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34723 and starting SCN of 326757052 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34722 and starting SCN of 326739164 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34721 and starting SCN of 326730107 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34720 and starting SCN of 326721606 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34719 and starting SCN of 326718543 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34718 and starting SCN of 326715249 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34717 and starting SCN of 326709503 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34716 and starting SCN of 326693713 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34715 and starting SCN of 326680021 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34714 and starting SCN of 326674022 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34713 and starting SCN of 326664781 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34712 and starting SCN of 326648917 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34711 and starting SCN of 326637659 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34710 and starting SCN of 326633287 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34709 and starting SCN of 326632166 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34708 and starting SCN of 326621042 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34707 and starting SCN of 326617608 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34706 and starting SCN of 326613463 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34705 and starting SCN of 326611471 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34704 and starting SCN of 326610305 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34703 and starting SCN of 326602873 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34702 and starting SCN of 326601517 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34701 and starting SCN of 326593022 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34700 and starting SCN of 326577874 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34699 and starting SCN of 326567243 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34698 and starting SCN of 326553641 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34697 and starting SCN of 326544480 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34696 and starting SCN of 326531815 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34695 and starting SCN of 326528717 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34694 and starting SCN of 326522442 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34693 and starting SCN of 326515260 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34692 and starting SCN of 326504255 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34691 and starting SCN of 326494511 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34690 and starting SCN of 326484165 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34689 and starting SCN of 326475207 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34688 and starting SCN of 326470137 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34687 and starting SCN of 326463888 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34686 and starting SCN of 326456866 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34685 and starting SCN of 326415614 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34684 and starting SCN of 326398980 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34683 and starting SCN of 326385176 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34682 and starting SCN of 326373763 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34681 and starting SCN of 326365337 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34680 and starting SCN of 326352830 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34679 and starting SCN of 326351732 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34678 and starting SCN of 326351526 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34677 and starting SCN of 326351228 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34676 and starting SCN of 326350869 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34675 and starting SCN of 326350236 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34674 and starting SCN of 326344630 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34673 and starting SCN of 326336226 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34672 and starting SCN of 326334353 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34671 and starting SCN of 326332206 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34670 and starting SCN of 326325188 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34669 and starting SCN of 326323615 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34668 and starting SCN of 326317656 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34667 and starting SCN of 326304700 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34666 and starting SCN of 326296332 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34665 and starting SCN of 326283118 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34664 and starting SCN of 326270792 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34653 and starting SCN of 326183189 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34652 and starting SCN of 326175000 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34651 and starting SCN of 326159778 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34650 and starting SCN of 326154245 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34649 and starting SCN of 326148100 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34648 and starting SCN of 326142540 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34647 and starting SCN of 326136812 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34646 and starting SCN of 326124534 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34645 and starting SCN of 326118922 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34644 and starting SCN of 326111890 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34643 and starting SCN of 326108132 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34642 and starting SCN of 326102908 found to restore
RMAN-00567: Recovery Manager could not print some error messages
Recovery Manager complete.

see metalink note 465558.1
https://metalink2.oracle.com/metalink/plsql/f?p=130:14:6831911279782618352::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,465558.1,1,1,1,helveticaKhurram

Creating standby database from ASM production database in standard edition

Hi,
I am using oracle 10g release 2 standard edition. I recently created a database instance and wanted to create a standby database instance. After sorting out how to achieve this without managed standby and data guard I finally got it working and the shipped archive logs are applied and working well on the standby database.
Now I am thinking of re-creating my production database and using ASM for storage managment. By doing this can a standby database still be created from a primary database using ASM? I want to be sure I can before I commit to using ASM for the production instance and manually creating a standby database from that instance.
Note: I am using standard edition not enterprise edition.

Hi
For Oracle SE standby, you can visit www.anbultechnologies.co.uk , they have a brilliant product name DRMC which is Automatic disaster recovery solution with automatic failover in case primary goes down due to any reason.
We are using this product for more than 2 years and it works like a dream using Oracle Standard Edition. We have depolyed more databases and Standby solution within the prices of 2 EE edition licenses.
You can give ma try as well.
website address is www.anbultechnologies.co.uk

SQL Server Reporting Services installed on a production database server used to support JD Edwards EnterpriseOne. What performance isses can arise

SQL Server Reporting Services installed on a production database server used to support JD Edwards EnterpriseOne. What performance isses can arise. Is it recommended. What are the pros and cons

Hi hazelannc,
I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated. Thank you for your understanding and support.
Regards,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Mount STANDBY with EE software created from SE production database

We mount (by error) our STANDBY databases with Enterprise Edition EE softare.
Our production database is Standard Edition SE.
We apply the logs without problem, but we have intention the mount the STANDBY database with SE software.
-> Could be possible mount the STANDBY database without need to recreate it? Remember the origin db are created from SE software and mount the STANDBY with EE software.
Thanks you!
Any help are welcome.
Diego.

Please read Note:139642.1 on metalink.

Changes are not reflected in Staging or Production Database - BCC

Hi,
I changed an asset from product catalog and able to see successful deployment in BCC. But, I am not able to see the changes in Staging or Production database.
I see only changes in Versioned Database.
Did the following things to see if thee is any error but there is no error during this operations.
1) Enabled all the logs for DeploymentManager, DeploymentServer.
2) Ran the CatalogMaintenanceService.
Please help me in resolving this issue.
Thanks,
DKAP

Adding to Desai, check for the repository mapping in agents, i.e in your production agent, you need to map the repositories to production repositories. For example ProductCatalog should be mapped to ProductCatalogproduction, similarly in Staging agent as well.
Cheers
R

Production database Alert log Message

Hi,
I am using oracle 10gR1 on windows.Recently i have created a physical standby database (sid=smtm) and production database (sid=mtm).My production alter log file dispaly some thing like please suggest my what it shows.
Mon Mar 02 00:18:31 2009
Private_strands 7 at log switch
Thread 1 advanced to log sequence 35722
Current log# 4 seq# 35722 mem# 0: D:\ORACLE\PRODUCT\10.1.0\ORADATA\MTM\REDO04.LOG
Current log# 4 seq# 35722 mem# 1: D:\ORACLE\PRODUCT\10.1.0\ORADATA\MTM\REDO04_A.LOG
Mon Mar 02 00:18:31 2009
ARC1: Evaluating archive   log 2 thread 1 sequence 35721
ARC1: Destination LOG_ARCHIVE_DEST_2 archival not expedited
Committing creation of archivelog 'E:\ORACLE\MTM\ARCHIVES\MTM_945F37AC_1_35721_500044525.ARC'
Invoking non-expedited destination LOG_ARCHIVE_DEST_2 thread 1 sequence 35721 host SMTM
*FAL[server, ARC1]: Begin FAL noexpedite archive (branch 500044525 thread 1 sequence 35721 dest SMTM)*
*FAL[server, ARC1]: Complete FAL noexpedite archive (thread 1 sequence 35721 destination SMTM)*Mon Mar 02 00:29:42 2009
Private_strands 7 at log switch
Thread 1 advanced to log sequence 35723
Current log# 3 seq# 35723 mem# 0: D:\ORACLE\PRODUCT\10.1.0\ORADATA\MTM\REDO03.LOG
Current log# 3 seq# 35723 mem# 1: D:\ORACLE\PRODUCT\10.1.0\ORADATA\MTM\REDO03_A.LOG
Mon Mar 02 00:29:42 2009
ARC1: Evaluating archive   log 4 thread 1 sequence 35722
ARC1: Destination LOG_ARCHIVE_DEST_2 archival not expedited
Committing creation of archivelog 'E:\ORACLE\MTM\ARCHIVES\MTM_945F37AC_1_35722_500044525.ARC'
Invoking non-expedited destination LOG_ARCHIVE_DEST_2 thread 1 sequence 35722 host SMTM
*FAL[server, ARC1]: Begin FAL noexpedite archive (branch 500044525 thread 1 sequence 35722 dest SMTM)*
*FAL[server, ARC1]: Complete FAL noexpedite archive (thread 1 sequence 35722 destination SMTM)*
Thanks

Sorry i have no metalink account.
On production database there is no any ORA error and on standby database Alert log shows.
Mon Mar 02 03:40:38 2009
RFS[1]: No standby redo logfiles created
RFS[1]: Archived Log: 'E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35728_500044525.ARC'
Committing creation of archivelog 'E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35728_500044525.ARC'
RFS[1]: No standby redo logfiles created
RFS[1]: Archived Log: 'E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35729_500044525.ARC'
Committing creation of archivelog 'E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35729_500044525.ARC'
RFS[1]: No standby redo logfiles created
RFS[1]: Archived Log: 'E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35730_500044525.ARC'
Committing creation of archivelog 'E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35730_500044525.ARC'Mon Mar 02 04:29:14 2009
RFS[1]: No standby redo logfiles created
RFS[1]: Archived Log: 'E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35731_500044525.ARC'
Committing creation of archivelog 'E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35731_500044525.ARC'
Media Recovery Log
ORA-279 signalled during: ALTER DATABASE RECOVER standby database ...Mon Mar 02 11:01:57 2009
ALTER DATABASE RECOVER CONTINUE DEFAULT
Mon Mar 02 11:01:57 2009
Media Recovery Log E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35553_500044525.ARC
ORA-279 signalled during: ALTER DATABASE RECOVER    CONTINUE DEFAULT ...Mon Mar 02 11:02:05 2009
ALTER DATABASE RECOVER CONTINUE DEFAULT
Media Recovery Log E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35554_500044525.ARC
ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
Mon Mar 02 11:02:14 2009
ALTER DATABASE RECOVER CONTINUE DEFAULT
Media Recovery Log E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35555_500044525.ARC
ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
Regards
Thanks for reply.

ORA-16005 : database requires recovery

Following error occurred while trying to open oracle datababse in read only mode
$ sqlplus /nolog
SQL> connect /as sysdba
connected
SQL>
SQL> startup nomount
ORACLE instance started
Total System Global Area 612368384 bytes
Fixed Size 1281504 bytes
Variable Size 163578400 bytes
Database Buffers 415236096 bytes
Redo Buffes 32272348 bytes
SQL>
SQL> alter database mount ;
Database altered
SQL> alter database open ready only ;
alter database open ready only
ERROR at line 1:
ORA-16005: database requires recovery
SQL>
Since database is in No Archive mode why it is giving ORA-16005 error while starting a databse in ready only mode ????

ORA-16005 database requires recovery
Cause: The database requires recovery, and therefore cannot be opened for read-only access by this instance.
Action: Perform the necessary recovery and re-open for read-only access.
Oracle says as above. Please perform the recovery and then open the database in read only mode. We are unaware about what happened before.

Production database requirements

Similar Messages

Maybe you are looking for