Standby database Exception
hello
when I create standby database from enterprise manager and in second step backup option I receive exception Index:3, size:3
thank you for your help
Edited by: user5581807 on Jul 8, 2010 9:44 AM
this thread is a duplicate and should be ignored by everyone.
To the OP:
Please return to the original thread.
Thank you.
Similar Messages
-
How do i install a standby database, the instruction in the backup and recovery handbook are not working, as anyone done it and how please.
Use Oracle 11.2 and check supported platforms using My Oracle Support notes:
>
As of Oracle Database 11g, Data Guard provides increased flexibility for Data Guard configurations in which the primary and standby systems may have different CPU architectures, operating systems (for example, Windows & Linux), operating system binaries (32-bit/64-bit), or Oracle database binaries (32-bit/64-bit).
This increased mixed-platform flexibility is subject to the current restrictions documented in the My Oracle Support notes 413484.1 and 1085687.1 at http://support.oracle.com.
Note 413484.1 discusses mixed-platform support and restrictions for physical standbys.
Note 1085687.1 discusses mixed-platform support and restrictions for logical standbys.
The same release of Oracle Database Enterprise Edition must be installed on the primary database and all standby databases, except during rolling database upgrades using logical standby databases.
>
quoted from http://download.oracle.com/docs/cd/E11882_01/server.112/e17022/standby.htm#i72053. -
SQL exception during creation of a physical standby database with EM
Version: EM Oracle 10.2.5 (agents running, repository running, primary db running, all targets visible and reachable with EM)
I try to create a physical standby database with the enterprise manager and each time the process is aborted with a SQL exception during the preparation of the job by the EM. I have added a part of the OMs log containing the error at the end of the excerpt.
=============
2010-04-29 16:00:39,856 [EMUI_16_00_39_/console/targets] WARN pref.SubtabPref getFolders.710 - Unknown folder id: VirtualServers retrieved from repository
2010-04-29 16:01:04,765 [EMUI_16_01_04_/console/database/dataguard/create] ERROR em.dataguard validate.1329 - CreateBean: ClassNotFoundException: null
2010-04-29 16:02:05,476 [EMUI_16_02_05_/console/database/dataguard/create] ERROR jobs.dbclone checkSetFileError.79 - DatabaseFileAttributes.checkSetFileError(): Null database file!
2010-04-29 16:02:05,476 [EMUI_16_02_05_/console/database/dataguard/create] ERROR jobs.dbclone setControlfiles.160 - DatabaseFileAttributes.setDatafiles(): Invalid control file!
2010-04-29 16:02:05,492 [EMUI_16_02_05_/console/database/dataguard/create] ERROR jobs.dbclone getControlFileNames.616 - DatabaseFileAttributes.getDatafileNames(): null datafile names!
2010-04-29 16:02:32,823 [Thread-28] ERROR em.jobs remoteOp.2389 - DBVerify.remoteOp(): Error: max_stamp# 6071384
2010-04-29 16:02:32,823 [Thread-28] ERROR jobs.dbclone submitJobPreparation.3297 - DBCloneObject.submitJobPreparation(): getMaxLogSequenceNum: Während der Vorbereitung des Jobs ist eine SQL Exception aufgetreten. Um das Problem zu diagnostizieren, legen Sie das Agent Perl-Skript-Tracing auf DEBUG fest und wiederholen den Vorgang
2010-04-29 16:02:32,823 [Thread-28] ERROR jobs.dbclone submitJobPreparation.3501 - DBCloneObject.submitJobPreparation(): Exception: java.lang.Exception: Während der Vorbereitung des Jobs ist eine SQL Exception aufgetreten. Um das Problem zu diagnostizieren, legen Sie das Agent Perl-Skript-Tracing auf DEBUG fest und wiederholen den Vorgang
2010-04-29 16:02:32,823 [Thread-28] ERROR jobs.dbclone submitDBCloneJob.3716 - DBCloneObject.submitDBCloneJob(): Exception: Während der Vorbereitung des Jobs ist eine SQL Exception aufgetreten. Um das Problem zu diagnostizieren, legen Sie das Agent Perl-Skript-Tracing auf DEBUG fest und wiederholen den Vorgang
2010-04-29 16:02:37,496 [EMUI_16_02_37_/console/database/dataguard/create] ERROR em.dataguard onEvent.1243 - CreateConfigController: Exception: oracle.sysman.db.dg.util.VxxStandbyException: Während der Vorbereitung des Jobs ist eine SQL Exception aufgetreten. Um das Problem zu diagnostizieren, legen Sie das Agent Perl-Skript-Tracing auf DEBUG fest und wiederholen den Vorgang
=========
I have set the agent perl script tracing to DEBUG, but can't find any reason, why the job preparation failed.
Has anyone an idea why the job cannot be prepared? Thanks in advance for investigation :-)Can you please tell me how can i see data gaurd on EM..
I have oracle 11gR1..i have implemmented primary as well standby database..
I have already started EM but i have no idea where to find datagaurd option..or how to create standdby db using EM..
You got error that means u did it using EM..how can i do it on EM -
Hi Friends,
I am getting the following exception in logical standby database at the time of Sql Apply.
After run the command alter database start logical standby apply sql apply services start but after few second automatically stop and getting following exception.
alter database start logical standby apply
Tue May 17 06:42:00 2011
No optional part
Attempt to start background Logical Standby process
LOGSTDBY Parameter: MAX_SERVERS = 20
LOGSTDBY Parameter: MAX_SGA = 100
LOGSTDBY Parameter: APPLY_SERVERS = 10
LSP0 started with pid=30, OS id=4988
Tue May 17 06:42:00 2011
Completed: alter database start logical standby apply
Tue May 17 06:42:00 2011
LOGSTDBY status: ORA-16111: log mining and apply setting up
Tue May 17 06:42:00 2011
LOGMINER: Parameters summary for session# = 1
LOGMINER: Number of processes = 4, Transaction Chunk Size = 201
LOGMINER: Memory Size = 100M, Checkpoint interval = 500M
Tue May 17 06:42:00 2011
LOGMINER: krvxpsr summary for session# = 1
LOGMINER: StartScn: 0 (0x0000.00000000)
LOGMINER: EndScn: 0 (0x0000.00000000)
LOGMINER: HighConsumedScn: 2660033 (0x0000.002896c1)
LOGMINER: session_flag 0x1
LOGMINER: session# = 1, preparer process P002 started with pid=35 OS id=4244
LOGSTDBY Apply process P014 started with pid=47 OS id=5456
LOGSTDBY Apply process P010 started with pid=43 OS id=6484
LOGMINER: session# = 1, reader process P000 started with pid=33 OS id=4732
Tue May 17 06:42:01 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1417, X:\TANVI\ARCHIVE2\ARC01417_0748170313.001
Tue May 17 06:42:01 2011
LOGMINER: Turning ON Log Auto Delete
Tue May 17 06:42:01 2011
LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01417_0748170313.001
Tue May 17 06:42:01 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1418, X:\TANVI\ARCHIVE2\ARC01418_0748170313.001
LOGSTDBY Apply process P008 started with pid=41 OS id=4740
LOGSTDBY Apply process P013 started with pid=46 OS id=7864
LOGSTDBY Apply process P006 started with pid=39 OS id=5500
LOGMINER: session# = 1, builder process P001 started with pid=34 OS id=4796
Tue May 17 06:42:02 2011
LOGMINER: skipped redo. Thread 1, RBA 0x00058a.00000950.0010, nCV 6
LOGMINER: op 4.1 (Control File)
Tue May 17 06:42:02 2011
LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01418_0748170313.001
Tue May 17 06:42:03 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1419, X:\TANVI\ARCHIVE2\ARC01419_0748170313.001
Tue May 17 06:42:03 2011
LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01419_0748170313.001
Tue May 17 06:42:03 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1420, X:\TANVI\ARCHIVE2\ARC01420_0748170313.001
Tue May 17 06:42:03 2011
LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01420_0748170313.001
Tue May 17 06:42:03 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1421, X:\TANVI\ARCHIVE2\ARC01421_0748170313.001
LOGSTDBY Analyzer process P004 started with pid=37 OS id=5096
Tue May 17 06:42:03 2011
LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01421_0748170313.001
LOGSTDBY Apply process P007 started with pid=40 OS id=2760
Tue May 17 06:42:03 2011
Errors in file x:\oracle\product\10.2.0\admin\tanvi\bdump\tanvi_p001_4796.trc:
ORA-00600: internal error code, arguments: [krvxbpx20], [1], [1418], [2380], [16], [], [], []
LOGSTDBY Apply process P012 started with pid=45 OS id=7152
Tue May 17 06:42:03 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1422, X:\TANVI\ARCHIVE2\ARC01422_0748170313.001
Tue May 17 06:42:03 2011
LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01422_0748170313.001
Tue May 17 06:42:03 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1423, X:\TANVI\ARCHIVE2\ARC01423_0748170313.001
Tue May 17 06:42:03 2011
LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01423_0748170313.001
Tue May 17 06:42:03 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1424, X:\TANVI\ARCHIVE2\ARC01424_0748170313.001
LOGMINER: session# = 1, preparer process P003 started with pid=36 OS id=5468
Tue May 17 06:42:03 2011
LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01424_0748170313.001
Tue May 17 06:42:04 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1425, X:\TANVI\ARCHIVE2\ARC01425_0748170313.001
LOGSTDBY Apply process P011 started with pid=44 OS id=6816
LOGSTDBY Apply process P005 started with pid=38 OS id=5792
LOGSTDBY Apply process P009 started with pid=42 OS id=752
Tue May 17 06:42:05 2011
krvxerpt: Errors detected in process 34, role builder.
Tue May 17 06:42:05 2011
krvxmrs: Leaving by exception: 600
Tue May 17 06:42:05 2011
Errors in file x:\oracle\product\10.2.0\admin\tanvi\bdump\tanvi_p001_4796.trc:
ORA-00600: internal error code, arguments: [krvxbpx20], [1], [1418], [2380], [16], [], [], []
LOGSTDBY status: ORA-00600: internal error code, arguments: [krvxbpx20], [1], [1418], [2380], [16], [], [], []
Tue May 17 06:42:06 2011
Errors in file x:\oracle\product\10.2.0\admin\tanvi\bdump\tanvi_lsp0_4988.trc:
ORA-12801: error signaled in parallel query server P001
ORA-00600: internal error code, arguments: [krvxbpx20], [1], [1418], [2380], [16], [], [], []
Tue May 17 06:42:06 2011
LogMiner process death detected
Tue May 17 06:42:06 2011
logminer process death detected, exiting logical standby
LOGSTDBY Analyzer process P004 pid=37 OS id=5096 stopped
LOGSTDBY Apply process P010 pid=43 OS id=6484 stopped
LOGSTDBY Apply process P008 pid=41 OS id=4740 stopped
LOGSTDBY Apply process P012 pid=45 OS id=7152 stopped
LOGSTDBY Apply process P014 pid=47 OS id=5456 stopped
LOGSTDBY Apply process P005 pid=38 OS id=5792 stopped
LOGSTDBY Apply process P006 pid=39 OS id=5500 stopped
LOGSTDBY Apply process P007 pid=40 OS id=2760 stopped
LOGSTDBY Apply process P011 pid=44 OS id=6816 stopped
Tue May 17 06:42:10 2011Errors in file x:\oracle\product\10.2.0\admin\tanvi\bdump\tanvi_p001_4796.trc:
ORA-00600: internal error code, arguments: [krvxbpx20], [1], [1418], [2380], [16], [], [], []submit an SR to ORACLE SUPPORT.
refer these too
*ORA-600/ORA-7445 Error Look-up Tool [ID 153788.1]*
*Bug 6022014: ORA-600 [KRVXBPX20] ON LOGICAL STANDBY* -
Standby Database - from READ-ONLY to Managed Recovery
We have a standby database set up for our production environment.
We are able to switch logfile on production and perform the managed recovery and then switch over to READ-ONLY mode. However, when the database is in READ-ONLY mode...I cannot close it if there are active connections.
There are 2 ways I can attempt to close the database...either by "shutdown immediate" or by issuing an "alter system kill session (##,##);"
If I issue the "shutdown immediate", then the RFS process does not transmit any more files...saying the connection to host is not there. Therefore this is not a valid solution.
I can use an alter system kill...to kill all active connections...but it would require to know what other connections are there.
Does anybody know how to best do this...to close the database by forcing all connections to end (except your current one) so you can "alter database close" and switch over to managed recovery?
Please HELP!
Thanks.
-Nicolasu just shutdown the server and restart in standby mode. it will apply all pending archive autometically.
-
Add Datafile in Logical Standby Database
Hi,
I have add one datafile in our primary RAC DB. We had logical standby database with file management is equal to manual. Both the primary RAC and logical standby db have the different storage structure. When the archive applied on the logical standby database its throws the error " error in creating datafile 'path'";
Would appreciate if come to know the steps to add the datafile in this kind of environment. and how can i overcome from this problem now except skip transaction for that ddl.
Thanks in advance.
DewanWhen the archive applied on the logical standby database its throws the error " error in creating datafile 'path'";Can you post the error message with the number.
From Manual..
8.3.1.2 Adding a Tablespace and a Datafile When STANDBY_FILE_MANAGEMENT Is Set to MANUAL
The following example shows the steps required to add a new datafile to the primary and standby database when the STANDBY_FILE_MANAGEMENT initialization parameter is set to MANUAL. You must set the STANDBY_FILE_MANAGEMENT initialization parameter to MANUAL when the standby datafiles reside on raw devices.
Add a new tablespace to the primary database:
SQL> CREATE TABLESPACE new_ts DATAFILE '/disk1/oracle/oradata/payroll/t_db2.dbf'
2> SIZE 1m AUTOEXTEND ON MAXSIZE UNLIMITED;
Verify the new datafile was added to the primary database:
SQL> SELECT NAME FROM V$DATAFILE;
NAME
/disk1/oracle/oradata/payroll/t_db1.dbf
/disk1/oracle/oradata/payroll/t_db2.dbf
Perform the following steps to copy the tablespace to a remote standby location:
Place the new tablespace offline:
SQL> ALTER TABLESPACE new_ts OFFLINE;
Copy the new tablespace to a local temporary location using an operating system utility copy command. Copying the files to a temporary location will reduce the amount of time the tablespace must remain offline. The following example copies the tablespace using the UNIX cp command:
% cp /disk1/oracle/oradata/payroll/t_db2.dbf
/disk1/oracle/oradata/payroll/s2t_db2.dbf
Place the new tablespace back online:
SQL> ALTER TABLESPACE new_ts ONLINE;
Copy the local copy of the tablespace to a remote standby location using an operating system utility command. The following example uses the UNIX rcp command:
%rcp /disk1/oracle/oradata/payroll/s2t_db2.dbf standby_location
Archive the current online redo log file on the primary database so it will get transmitted to the standby database:
SQL> ALTER SYSTEM ARCHIVE LOG CURRENT;
Use the following query to make sure that Redo Apply is running. If the MRP or MRP0 process is returned, Redo Apply is being performed.
SQL> SELECT PROCESS, STATUS FROM V$MANAGED_STANDBY;
Verify the datafile was added to the standby database after the archived redo log file was applied to the standby database:
SQL> SELECT NAME FROM V$DATAFILE;
NAME
/disk1/oracle/oradata/payroll/s2t_db1.dbf
/disk1/oracle/oradata/payroll/s2t_db2.dbf -
Error in starting MRP process in Standby database.
Hi All,
OS:Windows server 03
DB:11g
I am creating a Standby database, everything is fine until i fire the below command to start the MRP process to start the recovery of the database.
alter database recover managed standby database disconnect from session;MRP0 started with pid=27, OS id=6640
2013-02-07 17:59:48.515000 +05:30
started logmerger process
Managed Standby Recovery not using Real Time Apply
Errors in file d:\app\oracle\diag\rdbms\testdr\testdr\trace\testdr_dbw0_6000.trc:
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: 'D:\APP\ORACLE\ORADATA\TEST\TEST\SYSTEM01.DBF'
ORA-27086: unable to lock file - already in use
OSD-00002: additional error information
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
Errors in file d:\app\oracle\diag\rdbms\testdr\testdr\trace\testdr_dbw0_6000.trc:
ORA-01157: cannot identify/lock data file 2 - see DBWR trace file
ORA-01110: data file 2: 'D:\APP\ORACLE\ORADATA\TEST\TEST\SYSAUX01.DBF'
ORA-27086: unable to lock file - already in use
OSD-00002: additional error information
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
Errors in file d:\app\oracle\diag\rdbms\testdr\testdr\trace\testdr_dbw0_6000.trc:
ORA-01157: cannot identify/lock data file 3 - see DBWR trace file
ORA-01110: data file 3: 'D:\APP\ORACLE\ORADATA\TEST\TEST\UNDOTBS01.DBF'
ORA-27086: unable to lock file - already in use
OSD-00002: additional error information
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
Errors in file d:\app\oracle\diag\rdbms\testdr\testdr\trace\testdr_dbw0_6000.trc:
ORA-01157: cannot identify/lock data file 4 - see DBWR trace file
ORA-01110: data file 4: 'D:\APP\ORACLE\ORADATA\TEST\TEST\USERS01.DBF'
ORA-27086: unable to lock file - already in use
OSD-00002: additional error information
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
MRP0: Background Media Recovery terminated with error 1110
Errors in file d:\app\oracle\diag\rdbms\testdr\testdr\trace\testdr_pr00_7984.trc:
ORA-01110: data file 1: 'D:\APP\ORACLE\ORADATA\TEST\TEST\SYSTEM01.DBF'
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: 'D:\APP\ORACLE\ORADATA\TEST\TEST\SYSTEM01.DBF'
Recovery Slave PR00 previously exited with exception 1110
Errors in file d:\app\oracle\diag\rdbms\testdr\testdr\trace\testdr_mrp0_6640.trc:
ORA-01110: data file 1: 'D:\APP\ORACLE\ORADATA\TEST\TEST\SYSTEM01.DBF'
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: 'D:\APP\ORACLE\ORADATA\TEST\TEST\SYSTEM01.DBF'
Completed: alter database recover managed standby database disconnect from session
Can anyone tell me why is this comming?
Regards,
SphinxHi ,
Yes, it is on the same server.
I have used the below mentioned parameters to rename the files
At Primary Pfile:
*.db_file_name_convert=('D:\app\oracle\oradata\test\test\','D:\app\oracle\testdr\oradata\datafiles\')
*.log_file_name_convert=('D:\app\oracle\oradata\test\test\','D:\app\oracle\testdr\oradata\redologs\')
At Standby:
*.db_file_name_convert=('D:\app\oracle\testdr\oradata\datafiles\','D:\app\oracle\oradata\test\test\')
*.log_file_name_convert=('D:\app\oracle\testdr\oradata\redologs\','D:\app\oracle\oradata\test\test\')
But the output of v$datafile at standby is showing the path of Primary datafiles
I manually tried recovering them but it is prompting me the same error.
Regards
Edited by: $phinx19 on Feb 7, 2013 6:23 AM -
Error while setting up Standby database using Grid Control
I am getting this on grid control 10.2 on windows env while creating standby database using EM. I have checked this folder and it does exists.
any ideas?
C:\oracle\ora10.1\network\admin\listener.ora: java.io.IOException: The system cannot find the path specifiedThere is no problem tnsnames.ora & listener.ora since I am getting the same error for just standby backup also.
this is error on emoms.trc file
2007-07-18 13:19:37,318 [EMUI_13_19_37_/console/database/instance/sitemap] ERROR perf.sitemap setMaintenancePage.1812 - java.sql.SQLException: ORA-00933: SQL command not properly ended
ORA-06512: at "SYSMAN.ECM_UTIL", line 509
ORA-06512: at line 1
java.sql.SQLException: ORA-00933: SQL command not properly ended
ORA-06512: at "SYSMAN.ECM_UTIL", line 509
ORA-06512: at line 1
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:137)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:304)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:271)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:625)
at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:180)
at oracle.jdbc.driver.T4CCallableStatement.execute_for_rows(T4CCallableStatement.java:869)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1153)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:2932)
at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3023)
at oracle.jdbc.driver.OracleCallableStatement.execute(OracleCallableStatement.java:4132)
at oracle.sysman.util.jdbc.PreparedStatementWrapper.execute(PreparedStatementWrapper.java:173)
at oracle.sysman.util.jdbc.CallableStatementWrapper.execute(CallableStatementWrapper.java:135)
at oracle.sysman.eml.ecm.cloneHome.repaccess.CloneHomeSql.getClonableHomes(CloneHomeSql.java:449)
at oracle.sysman.eml.ecm.cloneHome.repaccess.CloneHomeSql.getClonableHomes(CloneHomeSql.java:561)
at oracle.sysman.eml.ecm.cloneHome.repaccess.CloneHomeSql.isHomeClonable(CloneHomeSql.java:363)
at oracle.sysman.db.adm.inst.SitemapController.setMaintenancePage(SitemapController.java:1807)
at oracle.sysman.db.adm.inst.SitemapController.setRequestAttributes(SitemapController.java:1385)
at oracle.sysman.db.adm.BaseController.handleEvent(BaseController.java:1154)
at oracle.sysman.emSDK.svlt.PageHandler.handleRequest(PageHandler.java:577)
at oracle.sysman.db.adm.RootController.handleRequest(RootController.java:174)
at oracle.sysman.db.adm.DBControllerResolver.handleRequest(DBControllerResolver.java:114)
at oracle.sysman.emSDK.svlt.EMServlet.myDoGet(EMServlet.java:781)
at oracle.sysman.emSDK.svlt.EMServlet.doGet(EMServlet.java:337)
at oracle.sysman.eml.app.Console.doGet(Console.java:318)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
at oracle.sysman.eml.app.EMRepLoginFilter.doFilter(EMRepLoginFilter.java:88)
at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:16)
at oracle.sysman.eml.app.BrowserVersionFilter.doFilter(BrowserVersionFilter.java:122)
at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:20)
at oracle.sysman.emSDK.svlt.EMRedirectFilter.doFilter(EMRedirectFilter.java:102)
at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:20)
at oracle.sysman.eml.app.ContextInitFilter.doFilter(ContextInitFilter.java:336)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:659)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:830)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:224)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:133)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
at java.lang.Thread.run(Thread.java:534)
2007-07-18 13:19:42,505 [EMUI_13_19_42_/console/database/dataguard/create] ERROR em.dataguard validate.1118 - CreateBean: ClassNotFoundException: null
2007-07-18 13:19:44,224 [EMUI_13_19_44_/console/database/dataguard/create] ERROR em.dataguard validate.1118 - CreateBean: ClassNotFoundException: null
2007-07-18 13:19:46,052 [EMUI_13_19_44_/console/database/dataguard/create] ERROR em.dataguard mapHelpPage.2002 - StandbyUtil.mapHelpPage: dghelp for database/dataguard/createSchedule not mapped to any help ID.. Defaulting to oemdba_consens_data_guard_page
2007-07-18 13:19:47,130 [EMUI_13_19_47_/console/database/dataguard/create] ERROR em.dataguard validate.1118 - CreateBean: ClassNotFoundException: null
2007-07-18 13:19:53,052 [Thread-85] ERROR jobs.dbclone createTemplate.379 - TemplateManager.createTemplate(): Exception: java.io.IOException: The system cannot find the path specified
2007-07-18 13:19:53,052 [Thread-85] ERROR jobs.dbclone submitJobPreparation.3013 - DBCloneObject.submitJobPreparation(): Exception: java.io.IOException: The system cannot find the path specified
2007-07-18 13:19:53,052 [Thread-85] ERROR jobs.dbclone submitDBCloneJob.3228 - DBCloneObject.submitDBCloneJob(): Exception: The system cannot find the path specified
2007-07-18 13:19:58,006 [EMUI_13_19_58_/console/database/dataguard/create] ERROR em.dataguard onEvent.1038 - CreateConfigController: Exception: oracle.sysman.db.dg.util.VxxStandbyException: The system cannot find the path specified -
RMAN-11001: alter database mount standby database
I'm doing a duplicate for a standby database and I'm getting this error
Oracle 8i Tru64
RMAN-03002: failure during compilation of command
RMAN-03013: command type: Duplicate Db
RMAN-03015: error occurred in stored script Memory Script
RMAN-03006: non-retryable error occurred during execution of command: sql
RMAN-07004: unhandled exception during command execution on channel clone_defaul
t
RMAN-20000: abnormal termination of job step
RMAN-11003: failure during parse/execution of SQL statement: alter database moun
t standby database
RMAN-11001: Oracle Error: ORA-03113: end-of-file on communication channel
Recovery Manager complete.
Any help pleaseCheck for parameter mismatches between parameter file and control file.
Check your parameter file. Check db_name paramter in paramter file used in the standby database. -
Standby database failover flashback restart as standby gap 1-100
Hi,
I have setup a physical standby database for a 3 node RAC primary database and configured the database to run in MAXIMUM AVAILABILITY mode. Both the primary and standby databases use ASM for managing the IO. I have enabled FLASHBACK ON on both the databases.
I did failover to standby database with primary db SHUTDOWN for doing some testing. After testing is done, I flashbacked the (standby, currently primary)database to the point when it became primary and start it as standby again and the old primary as primary.
Following are the steps:
Failover steps
.Shutdown the primary database
To finisish the recovery at standby
SQL>alter database recover managed standby database finish;
To start as primary
SQL>alter database commit to switchover to primary;
do some DML on the new primary
SQL>flashback database to scn <standby_became_primary_scn>;
SQL>alter database create standby controlfile as '/backup/standby.ctl';
Changed the spfile to point control_files to '/backup/standby.ctl';
Restarted the standby db in mount mode and
created the required stanbdy logs on it.
Then issued
SQL>alter database recover managed standby database using current logfile disconnect;
I have the following message in v$dataguard_status at standby db;
Fetching gap sequence in thread 1 branch(resetlogs_id) 653234404, gap seq 1-100
DBID 2651011616 branch 653234404
GAP - thread 1 sequence 1-100
FAL[client]: Failed to request gap sequence
FAL[client]: All defined FAL servers have been attempted.
The same error is found in alert log file also.
The status of the varioud managed standby db are as follows.
SQL> select process, status from v$managed_standby;
PROCESS STATUS
ARCH CLOSING
ARCH CLOSING
ARCH CLOSING
MRP0 WAIT_FOR_GAP
RFS IDLE
RFS IDLE
RFS IDLE
RFS IDLE
RFS IDLE
RFS IDLE
RFS IDLE
PROCESS STATUS
RFS IDLE
RFS IDLE
RFS IDLE
RFS IDLE
15 rows selected.
SQL>
Could you please help me how to resolve the above error.
Thanks,
SreekanthSreekanth,
I think your steps are right on for your requirement, except instead of
alter database create standby controlfile as '/backup/standby.ctl';
you can do this:
ALTER DATABASE CONVERT TO PHYSICAL STANDBY;
(although perhaps it achieves the same thing internally but you don't need to repoint to new controlfile).
So far as the GAP - thread 1 sequence 1-100
Let me guess, your current sequences are probably well ahead of this reported gap?
If so, this is a bogus gap in a sense that your standby has long ago applied them, but for some reason standby controlfile gets a little confused and starts asking for them again.
I have had this issue and opened multiple TAR's with Oracle since 10.2.0.1, got a few patches and advises to upgrade, but still occasionally get it now in 10.2.0.3
I strongly believe this is related to combination of RAC (i.e. multiple threads of redo) and dataguard.
It is also pretty hard to reproduce (I have not figured out how to reproduce this reliably, if you have, let me know), so I can understand why Oracle has so far been unable to fix this.
Anyway, the workaround is to re-create standby controlfile with a copy generated on primary, and move it in place of the existing (and confused) controlfiles on standby. -
Create physical standby database via grid control Errror
Hi
I wonder if anyone has seen the following problem
I am creating a standby database using EM Grid Control wizard. It all configures fine and starts the job goes through all steps including copying datafiles etc. but when it hits the step CREATE STANDBY DATABASE it fails with no explanation. In the oms log all it says is an error about cant find the sid name
EM Grid COntrol is 10.2.0.5 version
Windows Primary is Windows 2003 server 10.2.0.4 db
Trying to create on windows 2003 server with same oracle version
Thanks
DDid you search the same on Metalink ?
please also cehck
EM: Creation process for a physical standby DB failed with SQL Exception
Regards
Rajesh -
Physical standby database Version 11g Creation over grid control 10g
We are useing oracale 11g enterprise edition and want to create a physical standby database on another machine:
On primary host we've installed "standard database" and turned on archive log mode over em.
On the standby host we've installed only oracle without a database and without a listener.
On a third machine we've installed grid control and registered the primary and standby hosts. Using EM with Data Grid I'm attempting to create a Physical Standby on standby host. Everything is working except for the last part as noted here:
SQL*Plus: Release 11.1.0.6.0 - Production on Do Apr 3 11:21:17 2008
Copyright (c) 1982, 2007, Oracle. All rights reserved.
SQL> SQL> Bei einer nicht hochgefahrenen Instance angemeldet.
SQL> SQL> ORA-32004: obsolete and/or deprecated parameter(s) specified
ORACLE-Instance hochgefahren.
Total System Global Area 535662592 bytes
Fixed Size 1334380 bytes
Variable Size 167773076 bytes
Database Buffers 360710144 bytes
Redo Buffers 5844992 bytes
SQL>
Datenbank wurde geändert.
SQL> Verbindung zu Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options beendet
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\TTDB1\SYSTEM01.DBF' to 'c:\oracle\product\11.1.0\db_1\oradata\dg3\SYSTEM01.dbf'
dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = 'C:\ORACLE\ORADATA\TTDB1\SYSTEM01.DBF'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\TTDB1\SYSAUX01.DBF' to 'c:\oracle\product\11.1.0\db_1\oradata\dg3\SYSAUX01.dbf'
dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = 'C:\ORACLE\ORADATA\TTDB1\SYSAUX01.DBF'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\TTDB1\UNDOTBS01.DBF' to 'c:\oracle\product\11.1.0\db_1\oradata\dg3\UNDOTBS01.dbf'
dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = 'C:\ORACLE\ORADATA\TTDB1\UNDOTBS01.DBF'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\TTDB1\USERS01.DBF' to 'c:\oracle\product\11.1.0\db_1\oradata\dg3\USERS01.dbf'
dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = 'C:\ORACLE\ORADATA\TTDB1\USERS01.DBF'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\TTDB1\EXAMPLE01.DBF' to 'c:\oracle\product\11.1.0\db_1\oradata\dg3\EXAMPLE01.dbf'
dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = 'C:\ORACLE\ORADATA\TTDB1\EXAMPLE01.DBF'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\TTDB1\REDO01.LOG' to 'c:\oracle\product\11.1.0\db_1\oradata\dg3\REDO01.log'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\TTDB1\REDO02.LOG' to 'c:\oracle\product\11.1.0\db_1\oradata\dg3\REDO02.log'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\TTDB1\REDO03.LOG' to 'c:\oracle\product\11.1.0\db_1\oradata\dg3\REDO03.log'
dgcreate.DGrenameFiles: ALTER DATABASE CLEAR LOGFILE GROUP 1
dgcreate.DGrenameFiles: ALTER DATABASE CLEAR LOGFILE GROUP 2
dgcreate.DGrenameFiles: ALTER DATABASE CLEAR LOGFILE GROUP 3
dgcreate.DGgetRecoverySCN: SELECT MAX(NEXT_CHANGE#) FROM V$ARCHIVED_LOG
dgcreate.DGrecoverStby: ALTER DATABASE RECOVER AUTOMATIC FROM '%ORACLE_HOME%\RDBMS' STANDBY DATABASE UNTIL CHANGE 1061001
dgcreate.DGrecoverStby: ALTER DATABASE RECOVER CANCEL
dgcreate.DGrecoverStby: ALTER DATABASE OPEN READ ONLY
SQL Error: ORA-16004: Sciherungs-Datenbank muss wiederhergestellt werden
ORA-01152: Backup-Datei zum Wiederherstellen der Datei 1 war nicht alt genug
ORA-01110: Datendatei 1: 'C:\ORACLE\PRODUCT\11.1.0\DB_1\ORADATA\DG3\SYSTEM01.DBF' (DBD ERROR: OCIStmtExecute)
What is to do?
What mean's in this case:
"ORA-01152 file string was not restored from a sufficiently old backup
Cause: An incomplete recovery session was started, but an insufficient number of redo logs were applied to make the database consistent. This file is still in the future of the last redo log applied. The most likely cause of this message is forgetting to restore the file from backup before doing incomplete recovery.
Action: Apply additional redo log files until the database is consistent or restore the datafiles from an older backup and repeat recovery."Thanks for your immediate reply,
but there's a problem: We don't create the standby database manually. The creation is done by data guard over grid control. And the "automatic" creation stopps at this point.
Unfortunatly we don't know, wich steps of a manuall standby database creation are done and wich steps are not done at this point.
The oracle documentation (for release 11g) to create a manuall standby database is "B28294-02". But there's no step 5 "alter database recover managed standby database disconnect from session". Do you mean step 4 of chapter 3.2.6?
Is there no way, to create a standby database automatically over grid control? Or do we have to do something else before creating the physical standby database? Perhaps we have to create a full backup after switching to archive log mode? -
Standby Database fails to read dictionary from redo log
hi,
I am attempting to create a Logical standby database on same machine as the primary database. I have executed the steps outlined in Oracle Documentation several times, but end up with the same error. Detailes of setup and error are provided below. Please help. Thanks.
==========
OS: REdhat 8 (2.4.18-14)
RDBMS: Oracle EE Server 9.2.0.3.0
primary db init details:
*.log_archive_dest_1='LOCATION=/usr3/oracle/admin/lbsp/archive/ MANDATORY'
*.log_archive_dest_2='SERVICE=STDBY'
standby db init details:
log_archive_dest_1='LOCATION=/usr3/oracle/admin/stdby/archive/'
standby_archive_dest='/usr3/oracle/admin/lbsp/archive_pdb/'
Standby alert log file (tail)
LOGSTDBY event: ORA-01332: internal Logminer Dictionary error
Sun Jul 13 11:37:20 2003
Errors in file /usr3/oracle/admin/stdby/bdump/stdby_lsp0_13691.trc:
ORA-01332: internal Logminer Dictionary error
LSP process trace file:
Instance name: stdby
Redo thread mounted by this instance: 1
Oracle process number: 18
Unix process pid: 13691, image: oracle@prabhu (LSP0)
*** 2003-07-13 11:37:19.972
*** SESSION ID:(12.165) 2003-07-13 11:37:19.970
<krvrd.c:krvrdfdm>: DDL or Dict mine error exit. 384<krvrd.c:krvrdids>: Failed to mine dictionary. flgs 180
knahcapplymain: encountered error=1332
*** 2003-07-13 11:37:20.217
ksedmp: internal or fatal error
. (memory dump)
KNACDMP: Unassigned txns = { }
KNACDMP: *******************************************************
error 1332 detected in background process
OPIRIP: Uncaught error 447. Error stack:
ORA-00447: fatal error in background process
ORA-01332: internal Logminer Dictionary error
another trace file created by error is: stdby_p001_13695.trc
Instance name: stdby
Redo thread mounted by this instance: 1
Oracle process number: 20
Unix process pid: 13695, image: oracle@prabhu (P001)
*** 2003-07-13 11:37:19.961
*** SESSION ID:(22.8) 2003-07-13 11:37:19.908
krvxmrs: Leaving by exception: 604
ORA-00604: error occurred at recursive SQL level 1
ORA-01031: insufficient privileges
ORA-06512: at "SYS.LOGMNR_KRVRDREPDICT3", line 68
ORA-06512: at line 1
there are no errors anywhere during the creation, mounting or opening of standby database. After the initial log register, any log switch on primary is communicated to standby and visible in DBA_LOGSTDBY_LOG. Also, archived logs from primary are successfuly copied by system to directory pointed by standby db's standby_archive_dest parameter.
I noticed, somehow everytime I issue "ALTER DATABASE START LOGICAL STANDBY APPLY" command the procedures and packages related to logmnr get invalid. I compile them and again after "APPLY" they become invalid.
Invalid object list:
OBJECT_TYPE OBJECT_NAME
VIEW DBA_LOGSTDBY_PROGRESS
PACKAGE BODY DBMS_INTERNAL_LOGSTDBY
PACKAGE BODY DBMS_STREAMS_ADM_UTL
VIEW LOGMNR_DICT
PACKAGE BODY LOGMNR_DICT_CACHE
PROCEDURE LOGMNR_GTLO3
PROCEDURE LOGMNR_KRVRDA_TEST_APPLY
Anybody point out what I am doing wrong. Thanks for the helpORA-15001: diskgroup "ORAREDO3" does not exist or is not mounted
ORA-15001: diskgroup "ORAREDO3" does not exist or is not mountedhave you mentioned parameter LOG_FILE_NAME_CONVERT in standby when online redo log locations are different?
post from standby:-
SQL> select name, state From v$asm_diskgroup;
FAL[client, MRP0]: Error 1031 connecting to MKS01P_PRD for fetching gap sequence
ORA-01031: insufficient privilegesPost from primary & standby
SQL> select * from v$pwfile_users;
User Profile for 919131
919131
Handle: 919131
Status Level: Newbie
Registered: Mar 6, 2012
Total Posts: 16
Total Questions: 8 (8 unresolved)
OTN failed 100% to help you, then why you posted another question?
First close all your old answered threads and then better continue your updates in your thread.
Edited by: CKPT on Jul 9, 2012 11:45 AM -
Logs not applying on Standby Database
I am afraid I am back.
I now have a primary database and a standby database and logs are being shipped but not applied. Done some research and I have got to the point where in my alert log I find the following when I try to start MRP:
Fri Jun 29 15:03:40 2012
alter database recover managed standby database disconnect from session
Attempt to start background Managed Standby Recovery process (SAPDS)
Fri Jun 29 15:03:40 2012
MRP0 started with pid=29, OS id=23272
MRP0: Background Managed Standby Recovery process started (SAPDS)
started logmerger process
Fri Jun 29 15:03:45 2012
Managed Standby Recovery not using Real Time Apply
Read of datafile '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf' (fno 2) header failed with ORA-01206
Rereading datafile 2 header failed with ORA-01206
MRP0: Background Media Recovery terminated with error 1110
Errors in file /var/hpsrp/drforp03/oradata/u04/SAPDS/admin/diag/rdbms/drfsapds/SAPDS/trace/SAPDS_pr00_23308.trc:
ORA-01110: data file 2: '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf'
ORA-01122: database file 2 failed verification check
ORA-01110: data file 2: '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf'
ORA-01206: file is not part of this database - wrong database id
Recovery Slave PR00 previously exited with exception 1110
Errors in file /var/hpsrp/drforp03/oradata/u04/SAPDS/admin/diag/rdbms/drfsapds/SAPDS/trace/SAPDS_mrp0_23272.trc:
ORA-01110: data file 2: '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf'
ORA-01122: database file 2 failed verification check
ORA-01110: data file 2: '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf'
ORA-01206: file is not part of this database - wrong database id
MRP0: Background Media Recovery process shutdown (SAPDS)
Completed: alter database recover managed standby database disconnect from session
My question therefore is how can I get out of this and get my logs to apply on standby?Hello again;
Do you think if I tried to repeat the duplicate?
Yes I think you should do this.
Give me a few minutes and I will review my Word document and provide a step by step overview here as insurance.
I always cleanup the standby before trying another dup
OVERVIEW
Step 1 - Password file fro standby - Copy from primary and rename
Step 2 - Directory Structure on the remote server - Make sure noting is missing
Step 3 - Oracle Net Setup - entry for the CLONE in your TNSNAMES.ORA on both servers
Step 4 - SID_LIST_LISTENER addition ( assumes listener named LISTENER )
Step 5 - Timeouts set in listener.ora and sqlnet.ora Both Servers
Step 6 - Initialization Parameter File for the Auxiliary Instance
Step 7 - Set SID for Auxiliary Instance
Step 8 - Create an SPFILE for the new database by using a pfile with the INIT settings
Step 9 - Shutdown and startup nomount on new Spfile ( Auxiliary Instance )
Step 10 - Start RMAN and run the DUPLICATE Command
SID_LIST_LISTENER Example from mine
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = /u01/app/oracle/product/11.2.0.2)
(PROGRAM = extproc)
(SID_DESC =
(global_dbname = CLONE.hostname)
(ORACLE_HOME = /u01/app/oracle/product/11.2.0.2)
(sid_name = CLONE)
Prevent Timeouts
Add these to both servers
To listener.ora
INBOUND_CONNECT_TIMEOUT_ = 120
To sqlnet.ora
SQLNET.INBOUND_CONNECT_TIMEOUT = 120
Then stop and start the listener.
RMAN
$ORACLE_HOME/bin/rman target=sys/@primary auxiliary=sys/@standby
Connect should return something like this
connected to target database: RECOVER9 (DBID=3806912436)
connected to auxiliary database: CLONE (not mounted)RMAN>duplicate target database for standby from active database NOFILENAMECHECK;
INIT Extras
To avoid ORA-09925 make sure the PFILE has audit_file_dest and core_dump_dest set
Best Regards
mseberg
Edited by: mseberg on Jun 29, 2012 11:12 AM -
Creating Standby Database / Steps might be missing..
I have created standby database..
The archives are copied except one archived log and those copied archived are not applied at Standby database.
Besides this issue, I just checked the alert log file and pasting its contents here.
Do check it and let me know If I m missing any paramter[s].
Dump file c:\oracle\product\10.2.0\admin\rockstd\bdump\alert_rockstd.log
Mon May 12 15:23:42 2008
ORACLE V10.2.0.1.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3
Windows XP Version V5.1 Service Pack 2
CPU : 2 - type 586
Process Affinity : 0x00000000
Memory (Avail/Total): Ph:1194M/2038M, Ph+PgF:1368M/2641M, VA:1940M/2047M
Mon May 12 15:23:42 2008
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Autotune of undo retention is turned on.
IMODE=BR
ILAT =18
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.1.0.
System parameters with non-default values:
processes = 150
sga_target = 167772160
control_files = C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\ROCKSTD.CTL
db_block_size = 8192
compatible = 10.2.0.1.0
log_archive_dest_1 = location=C:\oracle\product\10.2.0\oradata\rockstd\Archive_rock
log_archive_dest_state_1 = ENABLE
log_archive_format = arc_%s_%t_%r.arc
fal_client = ROCKSTD
fal_server = ROCK
db_file_multiblock_read_count= 16
db_recovery_file_dest = C:\oracle\product\10.2.0\flash_recovery_area\rockstd
db_recovery_file_dest_size= 2147483648
undo_management = AUTO
undo_tablespace = UNDOTBS1
remote_login_passwordfile= EXCLUSIVE
db_domain =
dispatchers = (PROTOCOL=TCP) (SERVICE=rockXDB)
job_queue_processes = 10
audit_file_dest = C:\ORACLE\PRODUCT\10.2.0\ADMIN\ROCKSTD\ADUMP
background_dump_dest = C:\ORACLE\PRODUCT\10.2.0\ADMIN\ROCKSTD\BDUMP
user_dump_dest = C:\ORACLE\PRODUCT\10.2.0\ADMIN\ROCKSTD\UDUMP
core_dump_dest = C:\ORACLE\PRODUCT\10.2.0\ADMIN\ROCKSTD\CDUMP
db_name = rock
db_unique_name = rockstd
open_cursors = 300
pga_aggregate_target = 16777216
PMON started with pid=2, OS id=3656
PSP0 started with pid=3, OS id=504
MMAN started with pid=4, OS id=2544
DBW0 started with pid=5, OS id=3652
LGWR started with pid=6, OS id=552
CKPT started with pid=7, OS id=2688
SMON started with pid=8, OS id=3436
RECO started with pid=9, OS id=3696
CJQ0 started with pid=10, OS id=1636
MMON started with pid=11, OS id=2072
MMNL started with pid=12, OS id=3812
Mon May 12 15:23:43 2008
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 1 shared server(s) ...
Mon May 12 15:24:06 2008
alter database mount standby database
Mon May 12 15:24:11 2008
Setting recovery target incarnation to 14
ARCH: STARTING ARCH PROCESSES
ARC0 started with pid=16, OS id=3536
Mon May 12 15:24:11 2008
ARC0: Archival started
ARC1 started with pid=17, OS id=4084
Mon May 12 15:24:12 2008
ARC1: Archival started
ARCH: STARTING ARCH PROCESSES COMPLETE
Mon May 12 15:24:12 2008
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
ARC1: Thread not mounted
Mon May 12 15:24:12 2008
Successful mount of redo thread 1, with mount id 3275426006
Mon May 12 15:24:12 2008
Physical Standby Database mounted.
Mon May 12 15:24:13 2008
ARC0: Becoming the heartbeat ARCH
Completed: alter database mount standby database
Mon May 12 15:25:02 2008
Using STANDBY_ARCHIVE_DEST parameter default value as C:\oracle\product\10.2.0\oradata\rockstd\Archive_rock
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[1]: Assigned to RFS process 3444
RFS[1]: Identified database type as 'physical standby'
Mon May 12 15:25:02 2008
RFS LogMiner: Client disabled from further notification
Mon May 12 15:25:21 2008
db_recovery_file_dest_size of 2048 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Mon May 12 15:26:19 2008
alter database add standby logfile 'C:\oracle\product\10.2.0\oradata\rockstd\redo04.log' size 50m
Mon May 12 15:26:20 2008
Completed: alter database add standby logfile 'C:\oracle\product\10.2.0\oradata\rockstd\redo04.log' size 50m
Mon May 12 15:26:27 2008
alter database add standby logfile 'C:\oracle\product\10.2.0\oradata\rockstd\redo05.log' size 50m
Completed: alter database add standby logfile 'C:\oracle\product\10.2.0\oradata\rockstd\redo05.log' size 50m
Mon May 12 15:26:33 2008
alter database add standby logfile 'C:\oracle\product\10.2.0\oradata\rockstd\redo06.log' size 50m
Mon May 12 15:26:34 2008
Completed: alter database add standby logfile 'C:\oracle\product\10.2.0\oradata\rockstd\redo06.log' size 50m
Mon May 12 15:27:20 2008
alter database recover managed standby database disconnect from session
MRP0 started with pid=19, OS id=596
Managed Standby Recovery not using Real Time Apply
Mon May 12 15:27:26 2008
Errors in file c:\oracle\product\10.2.0\admin\rockstd\bdump\rockstd_dbw0_3652.trc:
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\SYSTEM01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
Mon May 12 15:27:26 2008
Errors in file c:\oracle\product\10.2.0\admin\rockstd\bdump\rockstd_dbw0_3652.trc:
ORA-01157: cannot identify/lock data file 2 - see DBWR trace file
ORA-01110: data file 2: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\UNDOTBS01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
Mon May 12 15:27:26 2008
Errors in file c:\oracle\product\10.2.0\admin\rockstd\bdump\rockstd_dbw0_3652.trc:
ORA-01157: cannot identify/lock data file 3 - see DBWR trace file
ORA-01110: data file 3: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\SYSAUX01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
Mon May 12 15:27:26 2008
Errors in file c:\oracle\product\10.2.0\admin\rockstd\bdump\rockstd_dbw0_3652.trc:
ORA-01157: cannot identify/lock data file 4 - see DBWR trace file
ORA-01110: data file 4: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\TESTING1.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
Mon May 12 15:27:26 2008
Errors in file c:\oracle\product\10.2.0\admin\rockstd\bdump\rockstd_dbw0_3652.trc:
ORA-01157: cannot identify/lock data file 5 - see DBWR trace file
ORA-01110: data file 5: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\SYSTEM03.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
Mon May 12 15:27:26 2008
Errors in file c:\oracle\product\10.2.0\admin\rockstd\bdump\rockstd_dbw0_3652.trc:
ORA-01157: cannot identify/lock data file 6 - see DBWR trace file
ORA-01110: data file 6: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\ABAMCO_TEST01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
MRP0: Background Media Recovery terminated with error 1110
Mon May 12 15:27:26 2008
Errors in file c:\oracle\product\10.2.0\admin\rockstd\bdump\rockstd_mrp0_596.trc:
ORA-01110: data file 1: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\SYSTEM01.DBF'
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\SYSTEM01.DBF'
Mon May 12 15:27:26 2008
Errors in file c:\oracle\product\10.2.0\admin\rockstd\bdump\rockstd_mrp0_596.trc:
ORA-01110: data file 1: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\SYSTEM01.DBF'
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\SYSTEM01.DBF'
Mon May 12 15:27:27 2008
Completed: alter database recover managed standby database disconnect from session
Mon May 12 15:30:18 2008
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[2]: Assigned to RFS process 2456
RFS[2]: Identified database type as 'physical standby'
Primary database is in MAXIMUM PERFORMANCE mode
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Successfully opened standby log 4: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO04.LOG'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Successfully opened standby log 4: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO04.LOG'
Mon May 12 15:30:22 2008
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[3]: Assigned to RFS process 3124
RFS[3]: Identified database type as 'physical standby'
RFS[3]: Successfully opened standby log 5: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO05.LOG'
Mon May 12 15:53:45 2008
RFS[3]: Successfully opened standby log 5: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO05.LOG'
Mon May 12 15:53:46 2008
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Successfully opened standby log 4: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO04.LOG'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Successfully opened standby log 4: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO04.LOG'
Mon May 12 15:53:58 2008
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Successfully opened standby log 4: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO04.LOG'
Mon May 12 16:00:06 2008
RFS[3]: Successfully opened standby log 4: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO04.LOG'
Mon May 12 16:00:09 2008
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Successfully opened standby log 4: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO04.LOG'
Mon May 12 16:00:14 2008
RFS[3]: Successfully opened standby log 5: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO05.LOG'
Mon May 12 16:00:18 2008
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Successfully opened standby log 4: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO04.LOG'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Successfully opened standby log 4: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO04.LOG'
Regards,
Rakesh Soni.Done, I've given the same path in Standby Database [datafiles, controlfiles] as it has been given in the Primary Database.
MoreOver, I m manually switching logfiles at primary database [alter system switch logfile] they are copied and applied sucessfully at standby database. But the archived files that I have copied with cold backup are not applied yet. Infact they are not retrieved executing the below query.
select name, applied from v$archived_log;
How can I apply those archived logs? [archives that copied with cold backup]
Regards.
Maybe you are looking for
-
Driver issue msi gtx 560 ti hawk
Which driver to use with msi 560 ti hawk currently using 275.33 but after installing battlefield 3 the game freezes in just 5 minutes of the gameplay the game requires latest drivers 285.xx from nvidia should i update to the latest driver from nvidia
-
I've this wsdl taken from the wsdl specification documentation. <?xml version="1.0"?> <definitions name="StockQuote" targetNamespace="http://example.com/stockquote.wsdl" xmlns:tns="http://example.com/stockquote.wsdl" xmlns:xsd1="http://example.com/st
-
My iTunes takes a while for it to show it, but now my iPod is recognized by iTunes. It does not show up as "Vic's iPod" anymore like I had named it, it just says "IPOD." The update option is blacked out because I already did that, but there is an opt
-
Nokias amazingly tolerant customers
I think Nokia are incredibly lucky to have such loyal, tolerant and forgiving customers. After years of bug ridden, unreliable and often poorly functioning Nokia phones I have given up and switched to Sony Ericson's. I appreciate that Sony do not see
-
Anyone tryed SR-IOV on hp proliant dl360/dl380p gen9?
hello everyone im using hp proliant dl360p Gen 8 with hp 366FLR (i350-T4 oem) and works fine (Hyper-V) but, in case of dl360/dl380p Gen9 platform 366FLR's SR-IOV does not working. (dl360 gen9 has hp 331i, known as intergrated nic/broadcom and i added