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.
Similar Messages
-
Errors in Database Alert Log... Please Help
Hi All,
This database is on Oracle 8i but I found errors in the alert Log.
These errors are relating to archiving.
Please take a look at this file to see the details;
http://us.f13.yahoofs.com/bc/47aff3ab_a145/bc/My+Documents/Database+Alert+Log.LOG?bfUw9sHBkd_LbjY0
ARC0: Beginning to archive log# 11 seq# 301
Wed Feb 13 14:57:45 2008
ARC0: Completed archiving log# 11 seq# 301
Wed Feb 13 15:46:26 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA03852.TRC:
Wed Feb 13 15:46:26 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA03208.TRC:
Wed Feb 13 15:46:30 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA03340.TRC:
Wed Feb 13 15:46:30 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA00784.TRC:
Wed Feb 13 15:46:31 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA03748.TRC:
Wed Feb 13 15:46:32 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA01228.TRC:
Wed Feb 13 16:18:57 2008
Thread 1 advanced to log sequence 303
Current log# 13 seq# 303 mem# 0: E:\ORACLE\ORADATA\MUKREC\LOGS\REDO13.LOG
Wed Feb 13 16:18:57 2008
ARC2: Beginning to archive log# 12 seq# 302
Wed Feb 13 16:19:25 2008
ARC2: Completed archiving log# 12 seq# 302
Wed Feb 13 18:40:13 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA03872.TRC:
Please help out. What is exactly the cause of this error and how can I avoid it next time from occuring.>> Please paste the output of E:\Oracle\admin\MUKREC\udump\ORA03872.TRC
Click on the link below to get the output of the ORA03872.TRC trace file
http://us.f13.yahoofs.com/bc/47aff3ab_a145/bc/My+Documents/ORA03872.TRC?bfMq_sHBSRis64KA
>> and last 100 lines of alert log
the last 100 lines of the alert log are here under;
Wed Feb 13 11:50:27 2008
Thread 1 advanced to log sequence 296
Current log# 13 seq# 296 mem# 0: E:\ORACLE\ORADATA\MUKREC\LOGS\REDO13.LOG
Wed Feb 13 11:50:27 2008
ARC0: Beginning to archive log# 12 seq# 295
Wed Feb 13 11:51:02 2008
ARC0: Completed archiving log# 12 seq# 295
Wed Feb 13 12:27:18 2008
Thread 1 advanced to log sequence 297
Current log# 7 seq# 297 mem# 0: E:\ORACLE\ORADATA\MUKREC\LOGS\REDO07.LOG
Wed Feb 13 12:27:18 2008
ARC0: Beginning to archive log# 13 seq# 296
Wed Feb 13 12:27:59 2008
Thread 1 advanced to log sequence 298
Current log# 8 seq# 298 mem# 0: E:\ORACLE\ORADATA\MUKREC\LOGS\REDO08.LOG
Wed Feb 13 12:27:59 2008
ARC1: Beginning to archive log# 13 seq# 296
ARC1: Failed to archive log# 13 seq# 296
ARC1: Beginning to archive log# 7 seq# 297
Wed Feb 13 12:28:33 2008
Thread 1 advanced to log sequence 299
Current log# 9 seq# 299 mem# 0: E:\ORACLE\ORADATA\MUKREC\LOGS\REDO09.LOG
Wed Feb 13 12:29:10 2008
Thread 1 advanced to log sequence 300
Current log# 10 seq# 300 mem# 0: E:\ORACLE\ORADATA\MUKREC\LOGS\REDO10.LOG
Wed Feb 13 12:29:11 2008
ARC0: Completed archiving log# 13 seq# 296
ARC0: STARTING ARCH PROCESSES
ARC2 started with pid=166
Wed Feb 13 12:29:11 2008
ARC0: STARTING ARCH PROCESSES COMPLETE
Wed Feb 13 12:29:11 2008
ARC0: Beginning to archive log# 7 seq# 297
ARC0: Failed to archive log# 7 seq# 297
ARC0: Beginning to archive log# 8 seq# 298
Wed Feb 13 12:29:12 2008
ARC2: Archival started
Wed Feb 13 12:29:32 2008
ARC1: Completed archiving log# 7 seq# 297
ARC1: Beginning to archive log# 8 seq# 298
ARC1: Failed to archive log# 8 seq# 298
ARC1: Beginning to archive log# 9 seq# 299
Wed Feb 13 12:29:48 2008
ARC0: Completed archiving log# 8 seq# 298
Wed Feb 13 12:29:48 2008
ARC2: Beginning to archive log# 9 seq# 299
ARC2: Failed to archive log# 9 seq# 299
Wed Feb 13 12:30:03 2008
ARC1: Completed archiving log# 9 seq# 299
Wed Feb 13 14:46:05 2008
Thread 1 advanced to log sequence 301
Current log# 11 seq# 301 mem# 0: E:\ORACLE\ORADATA\MUKREC\LOGS\REDO11.LOG
Wed Feb 13 14:46:05 2008
ARC1: Beginning to archive log# 10 seq# 300
Wed Feb 13 14:46:41 2008
ARC1: Completed archiving log# 10 seq# 300
Wed Feb 13 14:57:10 2008
Thread 1 advanced to log sequence 302
Current log# 12 seq# 302 mem# 0: E:\ORACLE\ORADATA\MUKREC\LOGS\REDO12.LOG
Wed Feb 13 14:57:10 2008
ARC0: Beginning to archive log# 11 seq# 301
Wed Feb 13 14:57:45 2008
ARC0: Completed archiving log# 11 seq# 301
Wed Feb 13 15:46:26 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA03852.TRC:
Wed Feb 13 15:46:26 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA03208.TRC:
Wed Feb 13 15:46:30 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA03340.TRC:
Wed Feb 13 15:46:30 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA00784.TRC:
Wed Feb 13 15:46:31 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA03748.TRC:
Wed Feb 13 15:46:32 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA01228.TRC:
Wed Feb 13 16:18:57 2008
Thread 1 advanced to log sequence 303
Current log# 13 seq# 303 mem# 0: E:\ORACLE\ORADATA\MUKREC\LOGS\REDO13.LOG
Wed Feb 13 16:18:57 2008
ARC2: Beginning to archive log# 12 seq# 302
Wed Feb 13 16:19:25 2008
ARC2: Completed archiving log# 12 seq# 302
Wed Feb 13 18:40:13 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA03872.TRC:
Thu Feb 14 08:03:54 2008
Thread 1 advanced to log sequence 304
Thu Feb 14 08:03:54 2008
Current log# 7 seq# 304 mem# 0: E:\ORACLE\ORADATA\MUKREC\LOGS\REDO07.LOG
Thu Feb 14 08:03:55 2008
ARC1: Beginning to archive log# 13 seq# 303
Thu Feb 14 08:04:45 2008
ARC1: Completed archiving log# 13 seq# 303
Thu Feb 14 08:24:29 2008
Thread 1 advanced to log sequence 305
Current log# 8 seq# 305 mem# 0: E:\ORACLE\ORADATA\MUKREC\LOGS\REDO08.LOG
Thu Feb 14 08:24:29 2008
ARC0: Beginning to archive log# 7 seq# 304
Thu Feb 14 08:25:01 2008
ARC0: Completed archiving log# 7 seq# 304
------------------------------------------------------------------------------------------------------------------------------------ -
Error in primary database alert log
Dear all i am getting the following error in my primary database alert log
oracle 10.2.0.3
Os/ rhel 4
Errors in file /u01/app/oracle/admin/PROSVR1/bdump/prosvr1_arc0_26151.trc:
ORA-00088: command cannot be executed by shared server
Tue Jul 7 23:20:37 2009
PING[ARC0]: Heartbeat failed to connect to standby 'DRSVR1'. Error is 88.
Tue Jul 7 23:25:38 2009
Errors in file /u01/app/oracle/admin/PROSVR1/bdump/prosvr1_arc0_26151.trc:
ORA-00088: command cannot be executed by shared server
Tue Jul 7 23:25:38 2009
PING[ARC0]: Heartbeat failed to connect to standby 'DRSVR1'. Error is 88.
Please let me know what needs to be done.
THanks in advance,
Aj00088, 00000, "command cannot be executed by shared server "
// *Cause: Debug command issued on shared server.
// *Action: Reissue the command using a dedicated server. -
I am geting errors in my database alert log file ora-12012 and ora 44003
Hi all,
I am using oracle 10g ...10.2.0.1.0 and OS is solaris 10.......
i am geting these errors in my database alert log file last two days..i am not geting why it is coming?
ORA-12012: error on auto execute of job 8887
ORA-44003: invalid SQL name
and trace file is i got i am posting here please help any one is aware about this....
System name: SunOS
Node name: obrmzone1
Release: 5.10
Version: Generic_137111-06
Machine: sun4v
Instance name: ------
Redo thread mounted by this instance: 1
Oracle process number: 144
Unix process pid: 26874, image:--------- (J000)
*** ACTION NAME:(AUTO_SPACE_ADVISOR_JOB) 2011-06-10 22:00:49.372
*** MODULE NAME:(DBMS_SCHEDULER) 2011-06-10 22:00:49.372
*** SERVICE NAME:(SYS$USERS) 2011-06-10 22:00:49.372
*** SESSION ID:(110.7114) 2011-06-10 22:00:49.372
*** 2011-06-10 22:00:49.372
ORA-12012: error on auto execute of job 8887
ORA-44003: invalid SQL name
thank you in advance,
DavI just google with "ORA-44003: invalid SQL name" and found below link:
http://www.oracle-base.com/articles/10g/dbms_assert_10gR2.php
SIMPLE_SQL_NAME
The SIMPLE_SQL_NAME function checks the input string conforms to the basic characteristics of a simple SQL name:
The first character of the name is alphabetic.
The name only contains alphanumeric characters or the "_", "$", "#"
Quoted names must be enclosed by double quotes and may contain any characters, including quotes provided they are represented by two quotes in a row ("").
The function ignores leading and trailing white spaces are ignored
The length of the input string is not validated. -
The database alert log has errors. Please help me
Hi all
I have an Oracle 8i Database that seams to be functioning well but when I
Checked the Database alert Log I realized that something is not fine
Part of the alert log content is here under. What can be problem and how can I
Resolve it. Please I need you assistance...
Thu Feb 07 08:50:37 2008
Thread 1 advanced to log sequence 266
Thu Feb 07 08:50:37 2008
Current log# 11 seq# 266 mem# 0: E:\ORACLE\ORADATA\MUKREC\LOGS\REDO11.LOG
Thu Feb 07 08:50:38 2008
ARC0: Beginning to archive log# 10 seq# 265
Thu Feb 07 08:51:07 2008
ARC0: Completed archiving log# 10 seq# 265
Thu Feb 07 09:23:22 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA03976.TRC:
Thu Feb 07 09:23:23 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA04092.TRC:
................................................................................................................I'll just throw a shameless copy-paste from Metalink note : 164839.1 , hope you can use it to get further ? :
Subject: FATAL ERROR IN TWO-TASK SERVER: error = 12571 Found in Alert File
Doc ID: Note:164839.1 Type: PROBLEM
Last Revision Date: 17-DEC-2007 Status: PUBLISHED
fact: Oracle Server - Enterprise Edition
symptom: Errors appear in alert file
symptom: FATAL ERROR IN TWO-TASK SERVER:
symptom: ERROR = 12571
symptom: trace file generated
symptom: Database operations continue successfully
cause: The most common cause for the above error is an ungraceful
disconnection of a session from the oracle db while the db is currently running
a dml statement issued by that session. The error is recorded when oracle
attempts to reply back to the session with the results of the dml and cannot
access the session. Overall database operations are usually not affected.
An ungraceful disconnection could cause by but is not limited to any of the
following:
- the client machine crashed
- the network connection crashed
- the user exited the session improperly (not issuing the 'exit' command)
- the user application allows the user to exit the application without properly
terminating the session.
The above can cause problems with corrupted rollback segments if occurring on a
regular basis and is not addressed. This would require db recovery and
possibly a db rebuild (not a light matter)
PMON will usually rollback most transactions in the rollback segments for a
session if it finds that the session has been ungracefully disconnected, but
there is always a chance that it cannot and this will lead to rollback segment
corruption.
fix:
The dml and the user that issued the dml can be determined from the trace file.
The current dml is in the tracefile header section. The user can be found in
the process state dump of the trace. The process state shows the machine,
o/suser, and user for the session.
The DBA can use this information to determine what the user was doing at the
time and if there was an ungraceful exit from the session the user was
utilizing.
The DBA should then address the cause of the ungraceful exit to reduce the
possibility of recurrence. -
Hi ,
following is the message from Alert log file and trace files.
This error encountered during RMAN backup but the backup was fine.
Didn't get any errors in RMAN log file.
Can anybody tell me what's the problem and solution?
----------- alert log file --------------------
Thu Mar 9 02:14:13 2006
Errors in file /app/oracle/admin/SOFPDWB4/udump/sofpdwb4_ora_950328.trc:
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 4
Thu Mar 9 02:14:13 2006
Errors in file /app/oracle/admin/SOFPDWB4/udump/sofpdwb4_ora_1769540.trc:
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 4
Thu Mar 9 02:14:13 2006
Errors in file /app/oracle/admin/SOFPDWB4/udump/sofpdwb4_ora_1392642.trc:
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 4
----------- trace files -------------------
/app/oracle/admin/SOFPDWB4/udump/sofpdwb4_ora_950328.trc
Oracle9i Enterprise Edition Release 9.2.0.5.0 - 64bit Production
With the Partitioning and Oracle Data Mining options
JServer Release 9.2.0.5.0 - Production
ORACLE_HOME = /app/oracle/product/9.2.0
System name: AIX
Node name: sof016
Release: 1
Version: 5
Machine: 000CEF9C4C00
Instance name: SOFPDWB4
Redo thread mounted by this instance: 1
Oracle process number: 24
Unix process pid: 950328, image: oracle@sof016 (TNS V1-V3)
*** 2006-03-09 02:14:13.053
*** SESSION ID:(77.60408) 2006-03-09 02:14:13.040
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 4
~
/app/oracle/admin/SOFPDWB4/udump/sofpdwb4_ora_1769540.trc
Oracle9i Enterprise Edition Release 9.2.0.5.0 - 64bit Production
With the Partitioning and Oracle Data Mining options
JServer Release 9.2.0.5.0 - Production
ORACLE_HOME = /app/oracle/product/9.2.0
System name: AIX
Node name: sof016
Release: 1
Version: 5
Machine: 000CEF9C4C00
Instance name: SOFPDWB4
Redo thread mounted by this instance: 1
Oracle process number: 25
Unix process pid: 1769540, image: oracle@sof016 (TNS V1-V3)
*** 2006-03-09 02:14:13.311
*** SESSION ID:(53.5721) 2006-03-09 02:14:13.310
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 4
/app/oracle/admin/SOFPDWB4/udump/sofpdwb4_ora_1392642.trc
Oracle9i Enterprise Edition Release 9.2.0.5.0 - 64bit Production
With the Partitioning and Oracle Data Mining options
JServer Release 9.2.0.5.0 - Production
ORACLE_HOME = /app/oracle/product/9.2.0
System name: AIX
Node name: sof016
Release: 1
Version: 5
Machine: 000CEF9C4C00
Instance name: SOFPDWB4
Redo thread mounted by this instance: 1
Oracle process number: 27
Unix process pid: 1392642, image: oracle@sof016 (TNS V1-V3)
*** 2006-03-09 02:14:13.549
*** SESSION ID:(59.52476) 2006-03-09 02:14:13.548
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 4Hello looks like when backing up database using RMAN it did not find the archivelogs hence you got the errors. Try doing "Crosscheck archivelog all" and see.
-Sri
<< Symptoms >>
Archivelog backup using RMAN failed with error :
RMAN-03002: failure of backup command at 08/18/2005 14:51:16
RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
ORA-19625: error identifying file /arch/arch2/1_266_563489673.dbf
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: A file or directory in the path name does not exist.
Additional information: 3
<<Cause>>
RMAN get the information about what archivelog files are required to back up from the v$archived_log view.
RMAN cannot find the file archivelog in the archivelog destination. So itscannot continue taking the backup because this file does not exist.
<<Solution>>
Check if the archivelog exist in the log archive destination. If the is moved to some other location then restore the file back to its original location and then do RMAN back.
else
RMAN> crosscheck archivelog all;
After the crosscheck all take the rman backup. -
Db_writer_processes alert log message
Oracle 11.2.0.3 running on HP-UX Itanium RX8640 with 16 CPUs and OS B.11.31
Upgraded to 11.2.0.3 last night and now I am receiving the following message in alert.log when starting database:
"NOTE: db_writer_processes has been changed from 4 to 1 due to NUMA requirements"
Any thoughts on what this means?Is your system NUMA-enabled?
In a NUMA-enabled box, the minimum number of DBWR process is the number of processor groups, oracle MUST start this minimum of DBWR no matter the parameter you set.
You seem to have the opposite case, as in oracle is forcing it to 1. In this case, I'm led to believe that maybe oracle is mistakenly identifiying your system as NUMA perphaps.
Upload the results for this:
select a.ksppinm "Parameter",
b.ksppstvl "Session Value",
c.ksppstvl "Instance Value"
from x$ksppi a, x$ksppcv b, x$ksppsv c
where a.indx = b.indx and a.indx = c.indx
and a.ksppinm = '_db_block_numa';You may try to do this:
- Set the following OS variable in your database OS owner user profile: DISABLE_NUMA = true
- Set the DBWR to 4 in the SPFILE and bounce the database.
- Verify if the issue continues. In the OS: ps -ef | grep dbwr to see how many dbwr the instance spawned. -
RMAN ALert Log Message: ALTER SYSTEM ARCHIVE LOG
Created a new Database on Oracle 10.2.0.4 and now seeing "ALTER SYSTEM ARCHIVE LOG" in the Alert Log only when the online RMAN backup runs:
Wed Aug 26 21:52:03 2009
ALTER SYSTEM ARCHIVE LOG
Wed Aug 26 21:52:03 2009
Thread 1 advanced to log sequence 35 (LGWR switch)
Current log# 2 seq# 35 mem# 0: /u01/app/oracle/oradata/aatest/redo02.log
Current log# 2 seq# 35 mem# 1: /u03/oradata/aatest/redo02a.log
Wed Aug 26 21:53:37 2009
ALTER SYSTEM ARCHIVE LOG
Wed Aug 26 21:53:37 2009
Thread 1 advanced to log sequence 36 (LGWR switch)
Current log# 3 seq# 36 mem# 0: /u01/app/oracle/oradata/aatest/redo03.log
Current log# 3 seq# 36 mem# 1: /u03/oradata/aatest/redo03a.log
Wed Aug 26 21:53:40 2009
Starting control autobackup
Control autobackup written to DISK device
handle '/u03/exports/backups/aatest/c-2538018370-20090826-00'
I am not issuing a log swiitch command. The RMAN commands I am running are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u03/exports/backups/aatest/%F';
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET;
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/u03/exports/backups/aatest/%d_%U';
BACKUP DATABASE PLUS ARCHIVELOG;
DELETE NOPROMPT OBSOLETE;
DELETE NOPROMPT ARCHIVELOG UNTIL TIME 'SYSDATE-2';
I do not see this message on any other 10.2.0.4 instances. Has anyone seen this and if so why is this showing in the log?
Thank you,
Curt SwartzlanderThere's no problem with log switch. Please refer to documentation for more information on syntax "PLUS ARCHIVELOG"
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/bkup003.htm#sthref377
Adding BACKUP ... PLUS ARCHIVELOG causes RMAN to do the following:
*1. Runs the ALTER SYSTEM ARCHIVE LOG CURRENT command.*
*2. Runs BACKUP ARCHIVELOG ALL. Note that if backup optimization is enabled, then RMAN skips logs that it has already backed up to the specified device.*
*3. Backs up the rest of the files specified in BACKUP command.*
*4. Runs the ALTER SYSTEM ARCHIVE LOG CURRENT command.*
*5. Backs up any remaining archived logs generated during the backup.*
This guarantees that datafile backups taken during the command are recoverable to a consistent state. -
Hi , I am having release Release 11.2.0.3.0 of oracle. Got database crash tuesday morning, and i am trying to get the reason for the crash. Given below is the alert.log for same. I can see Process RSM0 is getting killed , triggered the crash but could not relate it to the event follwed.
--------------------------------- ALERT.LOG---------------------------
Tue Aug 13 00:20:51 2013
Thread 1 advanced to log sequence 9737 (LGWR switch)
Current log# 3 seq# 9737 mem# 0: +DATA01/sid1004/onlinelog/group_3.379.817601969
Current log# 3 seq# 9737 mem# 1: +DATA02/sid1004/onlinelog/group_3.5858.817601983
Tue Aug 13 00:20:51 2013
LNS: Standby redo logfile selected for thread 1 sequence 9737 for destination LOG_ARCHIVE_DEST_2
Tue Aug 13 00:21:11 2013
Archived Log entry 20595 added for thread 1 sequence 9736 ID 0xe56c03af dest 1:
Tue Aug 13 00:30:48 2013
Thread 1 advanced to log sequence 9738 (LGWR switch)
Current log# 4 seq# 9738 mem# 0: +DATA01/sid1004/onlinelog/group_4.378.817601995
Current log# 4 seq# 9738 mem# 1: +DATA02/sid1004/onlinelog/group_4.7210.817602007
Tue Aug 13 00:30:48 2013
LNS: Standby redo logfile selected for thread 1 sequence 9738 for destination LOG_ARCHIVE_DEST_2
Tue Aug 13 00:30:55 2013
Archived Log entry 20597 added for thread 1 sequence 9737 ID 0xe56c03af dest 1:
Tue Aug 13 00:40:41 2013
Thread 1 advanced to log sequence 9739 (LGWR switch)
Current log# 5 seq# 9739 mem# 0: +DATA01/sid1004/onlinelog/group_5.377.817602019
Current log# 5 seq# 9739 mem# 1: +DATA02/sid1004/onlinelog/group_5.10031.817602031
Tue Aug 13 00:40:42 2013
LNS: Standby redo logfile selected for thread 1 sequence 9739 for destination LOG_ARCHIVE_DEST_2
Tue Aug 13 00:40:47 2013
Archived Log entry 20599 added for thread 1 sequence 9738 ID 0xe56c03af dest 1:
Tue Aug 13 00:50:41 2013
Thread 1 advanced to log sequence 9740 (LGWR switch)
Current log# 6 seq# 9740 mem# 0: +DATA01/sid1004/onlinelog/group_6.376.817602043
Current log# 6 seq# 9740 mem# 1: +DATA02/sid1004/onlinelog/group_6.6026.817602057
Tue Aug 13 00:50:41 2013
LNS: Standby redo logfile selected for thread 1 sequence 9740 for destination LOG_ARCHIVE_DEST_2
Tue Aug 13 00:50:46 2013
Archived Log entry 20601 added for thread 1 sequence 9739 ID 0xe56c03af dest 1:
Tue Aug 13 01:00:40 2013
Thread 1 advanced to log sequence 9741 (LGWR switch)
Current log# 7 seq# 9741 mem# 0: +DATA01/sid1004/onlinelog/group_7.375.817602069
Current log# 7 seq# 9741 mem# 1: +DATA02/sid1004/onlinelog/group_7.10703.817602081
Tue Aug 13 01:00:41 2013
LNS: Standby redo logfile selected for thread 1 sequence 9741 for destination LOG_ARCHIVE_DEST_2
Tue Aug 13 01:00:46 2013
Archived Log entry 20603 added for thread 1 sequence 9740 ID 0xe56c03af dest 1:
Tue Aug 13 01:09:02 2013
minact-scn: useg scan erroring out with error e:12751
Tue Aug 13 01:10:38 2013
Thread 1 advanced to log sequence 9742 (LGWR switch)
Current log# 8 seq# 9742 mem# 0: +DATA01/sid1004/onlinelog/group_8.374.817602093
Current log# 8 seq# 9742 mem# 1: +DATA02/sid1004/onlinelog/group_8.12060.817602105
Tue Aug 13 01:10:39 2013
LNS: Standby redo logfile selected for thread 1 sequence 9742 for destination LOG_ARCHIVE_DEST_2
Tue Aug 13 01:10:51 2013
Archived Log entry 20605 added for thread 1 sequence 9741 ID 0xe56c03af dest 1:
Tue Aug 13 01:15:55 2013
Time drift detected. Please check VKTM trace file for more details.
Tue Aug 13 01:16:27 2013
Thread 1 advanced to log sequence 9743 (LGWR switch)
Current log# 1 seq# 9743 mem# 0: +DATA01/sid1004/onlinelog/group_1.381.817601921
Current log# 1 seq# 9743 mem# 1: +DATA02/sid1004/onlinelog/group_1.5144.817601933
Tue Aug 13 01:17:51 2013
Process RSM0, PID = 8562, will be killed
Tue Aug 13 02:19:38 2013
Starting ORACLE instance (normal)While you're at MetaLink/MyOracle support, you'd probably want to read the following doc id's as well:
Time Drift Detected. Please Check Vktm Trace File For More Details. (Doc ID 1347586.1)
Alert log shows: "Minact-scn: Useg Scan Erroring Out With Error E:12751" Warning (Doc ID 1478691.1) -
10.2.0.4 Streams Alert log message
Good afternoon everyone,
Wanted to get some input on a message that ocasionally is logged to alert log of the owning QT instance in our RAC environment. In summary we have two RAC environments and perform bi-directional replication between the two environments. The message in question is usually logged in the busier environment.
krvxenq: Failed to acquire logminer dictionary lock
During that time it it seems that the Logminer process in not mining for changes, which could lead to latency between the two environments.
I have looked at AWR reports for times during the occurence of these errors and its common to see the following procedure running.
BEGIN dbms_capture_adm_internal.enforce_checkpoint_retention(:1, :2, :3); END;
This procedure, which I assume purges Capture chekcpoints that exceed the retention duration, takes between 10-20 minutes to run. The table which stores the checkpoints is logmnr_restart_ckpt$. I suspect that the issue could be caused by the size of the logmnr_restart_ckpt$ whcih is 12GB in our environemnt. A purge job needs to be scheduled to shrink the table.
If anyone has seen anything similar in her or his environment please offer any additional knowledge you may have about the topic.
Thank you,There are 2 possibilities : either you have too much load on the table LOMNR_RESTART_CKPT$
due to the heavy system load or there is a bad streams query.
At this stage I would not like to admit the 'we-can't-cope-the-load' without having investigated more common issues.
Let's assume optimistically that one or many streams internal SQL do not run as intended. This is our best bet.
The table LOMNR_RESTART_CKPT$ is big is a perfect suspect.
If there is a problem with one of the queries involving this table, we find it using sys.col_usage$,
identify which columns are used and from there jump to SQL_ID checking plans:
set linesize 132 head on pagesize 33
col obj format a35 head "Table name"
col col1 format a26 head "Column"
col equijoin_preds format 9999999 head "equijoin|Preds" justify c
col nonequijoin_preds format 9999999 head "non|equijoin|Preds" justify c
col range_preds format 999999 head "Range|Pred" justify c
col equality_preds format 9999999 head "Equality|Preds" justify c
col like_preds format 999999 head "Like|Preds" justify c
col null_preds format 999999 head "Null|Preds" justify c
select r.name ||'.'|| o.name "obj" , c.name "col1",
equality_preds, equijoin_preds, nonequijoin_preds, range_preds,
like_preds, null_preds, to_char(timestamp,'DD-MM-YY HH24:MI:SS') "Date"
from sys.col_usage$ u, sys.obj$ o, sys.col$ c, sys.user$ r
where o.obj# = u.obj# and o.name = 'LOMNR_RESTART_CKPT$' -- and $AND_OWNER
c.obj# = u.obj# and
c.col# = u.intcol# and
o.owner# = r.user# and
(u.equijoin_preds > 0 or u.nonequijoin_preds > 0)
order by 4 desc
For each column predicate checks for full table scan :
define COL_NAME='col to check'
col PLAN_HASH_VALUE for 999999999999 head 'Plan hash |value' justify c
col id for 999 head 'Id'
col child for 99 head 'Ch|ld'
col cost for 999999 head 'Oper|Cost'
col tot_cost for 999999 head 'Plan|cost' justify c
col est_car for 999999999 head 'Estimed| card' justify c
col cur_car for 999999999 head 'Avg seen| card' justify c
col ACC for A3 head 'Acc|ess'
col FIL for A3 head 'Fil|ter'
col OTHER for A3 head 'Oth|er'
col ope for a30 head 'Operation'
col exec for 999999 head 'Execution'
break on PLAN_HASH_VALUE on sql_id on child
select distinct
a.PLAN_HASH_VALUE, a.id , a.sql_id, a.CHILD_NUMBER child , a.cost, c.cost tot_cost,
a.cardinality est_car, b.output_rows/decode(b.EXECUTIONS,0,1,b.EXECUTIONS) cur_car,
b.EXECUTIONS exec,
case when length(a.ACCESS_PREDICATES) > 0 then ' Y' else ' N' end ACC,
case when length(a.FILTER_PREDICATES) > 0 then ' Y' else ' N' end FIL,
case when length(a.projection) > 0 then ' Y' else ' N' end OTHER,
a.operation||' '|| a.options ope
from
v$sql_plan a,
v$sql_plan_statistics_all b ,
v$sql_plan_statistics_all c
where
a.PLAN_HASH_VALUE = b.PLAN_HASH_VALUE
and a.sql_id = b.sql_id
and a.child_number = b.child_number
and a.id = b.id
and a.PLAN_HASH_VALUE= c.PLAN_HASH_VALUE (+)
and a.sql_id = c.sql_id
and a.child_number = c.child_number and c.id=0
and a.OBJECT_NAME = 'LOMNR_RESTART_CKPT$' -- $AND_A_OWNER
and (instr(a.FILTER_PREDICATES,'&&COL_NAME') > 0
or instr(a.ACCESS_PREDICATES,'&&COL_NAME') > 0
or instr(a.PROJECTION, '$COL_NAME') > 0
order by sql_id, PLAN_HASH_VALUE, id
now for each query with a FULL table scan check the predicate and
see if adding and index will not improveAnother possibility :
One of the structure associated to streams, that you don't necessary see, may have remained too big.
Many of these structures are only accessed by streams maintenance using Full table scan.
They are supposed to remain small tables. But after a big streams crash, they inflate and whenever
the problem is solved, These supposed-to-be-small remain as the crash made them : too big.
In consequence, the FTS intended to run on small tables suddenly loop over stretches of empty blocks.
This is very frequent on big streams environment. You find these structures, if any exists using this query
Note that a long running of this query, imply big structures. You will have to assess if the number of rows is realistic with the number of blocks.
break on parent_table
col type format a30
col owner format a16
col index_name head 'Related object'
col parent_table format a30
prompt
prompt To shrink a lob associated to a queue type : alter table AQ$_<queue_table>_P modify lob(USER_DATA) ( shrink space ) cascade ;
prompt
select a.owner,a.table_name parent_table,index_name ,
decode(index_type,'LOB','LOB INDEX',index_type) type,
(select blocks from dba_segments where segment_name=index_name and owner=b.owner) blocks
from
dba_indexes a,
( select owner, queue_table table_name from dba_queue_tables
where recipients='SINGLE' and owner NOT IN ('SYSTEM') and (compatible LIKE '8.%' or compatible LIKE '10.%')
union
select owner, queue_table table_name from dba_queue_tables
where recipients='MULTIPLE' and (compatible LIKE '8.1%' or compatible LIKE '10.%')
) b
where a.owner=b.owner
and a.table_name = b.table_name
and a.owner not like 'SYS%' and a.owner not like 'WMSYS%'
union
-- LOB Segment for QT
select a.owner,a.segment_name parent_table,l.segment_name index_name, 'LOB SEG('||l.column_name||')' type,
(select sum(blocks) from dba_segments where segment_name = l.segment_name ) blob_blocks
from dba_segments a,
dba_lobs l,
( select owner, queue_table table_name from dba_queue_tables
where recipients='SINGLE' and owner NOT IN ('SYSTEM') and (compatible LIKE '8.%' or compatible LIKE '10.%')
union
select owner, queue_table table_name from dba_queue_tables
where recipients='MULTIPLE' and (compatible LIKE '8.1%' or compatible LIKE '10.%')
) b
where a.owner=b.owner and
a.SEGMENT_name = b.table_name and
l.table_name = a.segment_name and
a.owner not like 'SYS%' and a.owner not like 'WMSYS%'
union
-- LOB Segment of QT.._P
select a.owner,a.segment_name parent_table,l.segment_name index_name, 'LOB SEG('||l.column_name||')',
(select sum(blocks) from dba_segments where segment_name = l.segment_name ) blob_blocks
from dba_segments a,
dba_lobs l,
( select owner, queue_table table_name from dba_queue_tables
where recipients='SINGLE' and owner NOT IN ('SYSTEM') and (compatible LIKE '8.%' or compatible LIKE '10.%')
union
select owner, queue_table table_name from dba_queue_tables
where recipients='MULTIPLE' and (compatible LIKE '8.1%' or compatible LIKE '10.%')
) b
where a.owner=b.owner and
a.SEGMENT_name = 'AQ$_'||b.table_name||'_P' and
l.table_name = a.segment_name and
a.owner not like 'SYS%' and a.owner not like 'WMSYS%'
union
-- Related QT
select a2.owner, a2.table_name parent_table, '-' index_name , decode(nvl(a2.initial_extent,-1), -1, 'IOT TABLE','NORMAL') type,
case
when decode(nvl(a2.initial_extent,-1), -1, 'IOT TABLE','NORMAL') = 'IOT TABLE'
then ( select sum(leaf_blocks) from dba_indexes where table_name=a2.table_name and owner=a2.owner)
when decode(nvl(a2.initial_extent,-1), -1, 'IOT TABLE','NORMAL') = 'NORMAL'
then (select blocks from dba_segments where segment_name=a2.table_name and owner=a2.owner)
end blocks
from dba_tables a2,
( select owner, queue_table table_name from dba_queue_tables
where recipients='SINGLE' and owner NOT IN ('SYSTEM') and (compatible LIKE '8.%' or compatible LIKE '10.%')
union all
select owner, queue_table table_name from dba_queue_tables
where recipients='MULTIPLE' and (compatible LIKE '8.1%' or compatible LIKE '10.%' )
) b2
where
a2.table_name in ( 'AQ$_'||b2.table_name ||'_T' , 'AQ$_'||b2.table_name ||'_S', 'AQ$_'||b2.table_name ||'_H' , 'AQ$_'||b2.table_name ||'_G' ,
'AQ$_'|| b2.table_name ||'_I' , 'AQ$_'||b2.table_name ||'_C', 'AQ$_'||b2.table_name ||'_D', 'AQ$_'||b2.table_name ||'_P')
and a2.owner not like 'SYS%' and a2.owner not like 'WMSYS%'
union
-- IOT Table normal
select
u.name owner , o.name parent_table, c.table_name index_name, 'RELATED IOT' type,
(select blocks from dba_segments where segment_name=c.table_name and owner=c.owner) blocks
from sys.obj$ o,
user$ u,
(select table_name, to_number(substr(table_name,14)) as object_id , owner
from dba_tables where table_name like 'SYS_IOT_OVER_%' and owner not like '%SYS') c
where
o.obj#=c.object_id
and o.owner#=u.user#
and obj# in (
select to_number(substr(table_name,14)) as object_id from dba_tables where table_name like 'SYS_IOT_OVER_%' and owner not like '%SYS')
order by parent_table , index_name desc;
"I hope it is one of the above case, otherwise thing may become more complicates. -
Dear All
My database is running on RAC configuration and the version is 10.1.0.5
Everyday i come across this error in the alert log of both the instances,
Unable to restore resource manager plan to '':
ORA-02097: parameter cannot be modified because specified value is invalid
ORA-00439: feature not enabled: Database resource manager
pls help me if u have come across this errorCheck metalink note 735798.1
HTH... -
Alert log message : Load Indicator not supported by OS
I am running Oracle 8.1.5 on Red Hat Linux 6.1 , I am getting an alert message
"Load Indicator not supported by OS"
Kindly help me urgently on the below email address
[email protected]
ThanksTry turning of the Multi-threaded server option (i.e. comment out "mts" references in the init[SID].ora file). This appears to be an MTS-related bug.
HTH
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by (Viral Shah):
I am running Oracle 8.1.5 on Red Hat Linux 6.1 , I am getting an alert message
"Load Indicator not supported by OS"
Kindly help me urgently on the below email address
[email protected]
Thanks<HR></BLOCKQUOTE>
null -
Hello Experts,
i am seeing following error messages in database alert log. based on error message OS process was not able to connect one of the cell server. is there any way to find why it is failing to connect cell server?
OSPID: 27669: connect: ossnet: connection failed to server 192.168.10.11, result=5 (login: sosstcpreadtry failed) (difftime=1953)
Mon Nov 05 17:35:16 2012
OSPID: 27665: connect: ossnet: connection failed to server 192.168.10.11, result=5 (login: sosstcpreadtry failed) (difftime=1953)
Mon Nov 05 17:35:17 2012
OSPID: 18681: connect: ossnet: connection failed to server 192.168.10.11, result=5 (login: sosstcpreadtry failed) (difftime=1953)
Mon Nov 05 17:42:22 2012
OSPID: 12134: connect: ossnet: connection failed to server 192.168.10.11, result=5 (login: sosstcpreadtry failed) (difftime=1953)
Mon Nov 05 17:42:24 2012
OSPID: 20097: connect: ossnet: connection failed to server 192.168.10.11, result=5 (login: sosstcpreadtry failed) (difftime=1954)
OSPID: 12134: connect: ossnet: connection failed to server 192.168.10.11, result=5 (login: sosstcpreadtry failed) (difftime=1953)
OSPID: 20097: connect: ossnet: connection failed to server 192.168.10.11, result=5 (login: sosstcpreadtry failed) (difftime=1954)
OSPID: 12134: connect: ossnet: connection failed to server 192.168.10.11, result=5 (login: sosstcpreadtry failed) (difftime=1954)
please adviceHi 892564,
i was wonder, how do you determine this is Cell server #7 ?The private network of your first exadata has a default range starting from 192.168.10.1 from the lowest compute node (db01).
A halfrack contains 11 components in the private network (4 nodes and 7 cells).
Hence 192.168.10.11 would be cell 7.
For a full rack this IP would match to cell 3.
Regards,
Tycho -
DG Observer triggering SIGSEGV Address not mapped to object errors in alert log
Hi,
I've got a Data Guard configuration using two 11.2.0.3 single instance databases. The configuration has been configured for automatic failover and I have an observer running on a separate box.
This fast-start failover configuration has been in place for about a month and in the last week, numerous SEGSEGV (address not mapped to object) errors are reported in the alert log. This is happening quite frequently (every 4/5 minutes or so).
The corresponding trace files show the process triggering the error coming from the observer.
Has anyone experienced this problem? I'm at my wits end trying to figure out how to fix the configuration to eliminate this error.
I must also note that even though this error is occurring a lot, it doesn't seem to be affecting any of the database functionality.
Help?
Thanks in advance.
BethHi.. The following is the alert log message, the traced file generated, and the current values of the data guard configuration. In addition, as part of my research, I attempted to apply patch 12615660 which did not take care of the issue. I also set the inbound_connection_timeout parameter to 0 and that didn't help either. I'm still researching but any pointer in the right direction is very much appreciated.
Error in Alert Log
Thu Apr 09 10:28:59 2015
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x9] [PC:0x85CE503, nstimexp()+71] [flags: 0x0, count: 1]
Errors in file /u01/app/oracle/diag/rdbms/<db_unq_name>/<SID>/trace/<SID>_ora_29902.trc (incident=69298):
ORA-07445: exception encountered: core dump [nstimexp()+71] [SIGSEGV] [ADDR:0x9] [PC:0x85CE503] [Address not mapped to object] []
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Thu Apr 09 10:29:02 2015
Sweep [inc][69298]: completed
Trace file:
Trace file /u01/app/oracle/diag/rdbms/<db_unq_name>/<SID>/trace/<SID>_ora_29902.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning and Oracle Label Security options
ORACLE_HOME = /u01/app/oracle/product/11.2.0.3/dbhome_1
System name: Linux
Node name: <host name>
Release: 2.6.32-431.17.1.el6.x86_64
Version: #1 SMP Wed May 7 14:14:17 CDT 2014
Machine: x86_64
Instance name: <SID>
Redo thread mounted by this instance: 1
Oracle process number: 19
Unix process pid: 29902, image: oracle@<host name>
*** 2015-04-09 10:28:59.966
*** SESSION ID:(416.127) 2015-04-09 10:28:59.966
*** CLIENT ID:() 2015-04-09 10:28:59.966
*** SERVICE NAME:(<db_unq_name>) 2015-04-09 10:28:59.966
*** MODULE NAME:(dgmgrl@<observer host> (TNS V1-V3)) 2015-04-09 10:28:59.966
*** ACTION NAME:() 2015-04-09 10:28:59.966
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x9] [PC:0x85CE503, nstimexp()+71] [flags: 0x0, count: 1]
DDE: Problem Key 'ORA 7445 [nstimexp()+71]' was flood controlled (0x6) (incident: 69298)
ORA-07445: exception encountered: core dump [nstimexp()+71] [SIGSEGV] [ADDR:0x9] [PC:0x85CE503] [Address not mapped to object] []
ssexhd: crashing the process...
Shadow_Core_Dump = PARTIAL
ksdbgcra: writing core file to directory '/u01/app/oracle/diag/rdbms/<db_unq_name>/<SID>/cdump'
Data Guard Configuration
DGMGRL> show configuration verbose;
Configuration - dg_config
Protection Mode: MaxPerformance
Databases:
dbprim - Primary database
dbstby - (*) Physical standby database
(*) Fast-Start Failover target
Properties:
FastStartFailoverThreshold = '30'
OperationTimeout = '30'
FastStartFailoverLagLimit = '180'
CommunicationTimeout = '180'
FastStartFailoverAutoReinstate = 'TRUE'
FastStartFailoverPmyShutdown = 'TRUE'
BystandersFollowRoleChange = 'ALL'
Fast-Start Failover: ENABLED
Threshold: 30 seconds
Target: dbstby
Observer: observer_host
Lag Limit: 180 seconds
Shutdown Primary: TRUE
Auto-reinstate: TRUE
Configuration Status:
SUCCESS
DGMGRL> show database verbose dbprim
Database - dbprim
Role: PRIMARY
Intended State: TRANSPORT-ON
Instance(s):
DG_CONFIG
Properties:
DGConnectIdentifier = 'dbprim'
ObserverConnectIdentifier = ''
LogXptMode = 'ASYNC'
DelayMins = '0'
Binding = 'optional'
MaxFailure = '0'
MaxConnections = '1'
ReopenSecs = '300'
NetTimeout = '30'
RedoCompression = 'DISABLE'
LogShipping = 'ON'
PreferredApplyInstance = ''
ApplyInstanceTimeout = '0'
ApplyParallel = 'AUTO'
StandbyFileManagement = 'MANUAL'
ArchiveLagTarget = '0'
LogArchiveMaxProcesses = '4'
LogArchiveMinSucceedDest = '1'
DbFileNameConvert = ''
LogFileNameConvert = ''
FastStartFailoverTarget = 'dbstby'
InconsistentProperties = '(monitor)'
InconsistentLogXptProps = '(monitor)'
SendQEntries = '(monitor)'
LogXptStatus = '(monitor)'
RecvQEntries = '(monitor)'
SidName = ‘<sid>’
StaticConnectIdentifier = '(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=<db host name>)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=<service_name>)(INSTANCE_NAME=<sid>)(SERVER=DEDICATED)))'
StandbyArchiveLocation = 'USE_DB_RECOVERY_FILE_DEST'
AlternateLocation = ''
LogArchiveTrace = '0'
LogArchiveFormat = '%t_%s_%r.dbf'
TopWaitEvents = '(monitor)'
Database Status:
SUCCESS
DGMGRL> show database verbose dbstby
Database - dbstby
Role: PHYSICAL STANDBY
Intended State: APPLY-ON
Transport Lag: 0 seconds
Apply Lag: 0 seconds
Real Time Query: ON
Instance(s):
DG_CONFIG
Properties:
DGConnectIdentifier = 'dbstby'
ObserverConnectIdentifier = ''
LogXptMode = 'ASYNC'
DelayMins = '0'
Binding = 'optional'
MaxFailure = '0'
MaxConnections = '1'
ReopenSecs = '300'
NetTimeout = '30'
RedoCompression = 'DISABLE'
LogShipping = 'ON'
PreferredApplyInstance = ''
ApplyInstanceTimeout = '0'
ApplyParallel = 'AUTO'
StandbyFileManagement = 'AUTO'
ArchiveLagTarget = '0'
LogArchiveMaxProcesses = '4'
LogArchiveMinSucceedDest = '1'
DbFileNameConvert = ''
LogFileNameConvert = ''
FastStartFailoverTarget = 'dbprim'
InconsistentProperties = '(monitor)'
InconsistentLogXptProps = '(monitor)'
SendQEntries = '(monitor)'
LogXptStatus = '(monitor)'
RecvQEntries = '(monitor)'
SidName = ‘<sid>’
StaticConnectIdentifier = '(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=<db host name>)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=<service_name>)(INSTANCE_NAME=<sid>)(SERVER=DEDICATED)))'
StandbyArchiveLocation = 'USE_DB_RECOVERY_FILE_DEST'
AlternateLocation = ''
LogArchiveTrace = '0'
LogArchiveFormat = '%t_%s_%r.dbf'
TopWaitEvents = '(monitor)'
Database Status:
SUCCESS -
Dead lock detected in alert log for HTMLDB application
We have a HTMLDB application newly impletemented in our database. One day, I found a ORA-000060 deadlock detected message in database alert log. Our developer said that the application is only for users to query something and will not insert, update or delete anything. I have created a tar but still not found any problem cause this. Can anyone tell why this occur?
Thanks in advance,
Antony
*** SESSION ID:(289.143) 2005-11-17 10:35:48.976
DEADLOCK DETECTED
Current SQL statement for this session:
DELETE FROM WWV_FLOW_DATA WHERE FLOW_INSTANCE = :B1 AND ITEM_ID IN (SELECT ID FROM WWV_FLOW_PAGE_PLUGS WHERE FLOW_ID = :B3 AND PAGE_ID = :B2 AND PLUG_SOURCE_TYPE IN ( 'SIMPLE_CHART', 'UPDATABLE_SQL_QUERY', 'DBMSSQL_CURSOR', 'FUNCTION_RETURNING_DBMSSQL_CURSOR', 'FUNCTION_RETURNING_SQL_QUERY_CACHED', 'FUNCTION_RETURNING_SQL_QUERY', 'STRUCTURED_QUERY', 'SQL_QUERY'))
----- PL/SQL Call Stack -----
object line object
handle number name
7000000bb989300 228 package body FLOWS_020000.WWV_FLOW_DISP_PAGE_PLUGS
7000000bbc922c8 8961 package body FLOWS_020000.WWV_FLOW
7000000bbd00000 236 procedure FLOWS_020000.F
7000000bdf1baa0 8 anonymous block
The following deadlock is not an ORACLE error. It is a
deadlock due to user error in the design of an application
or from issuing incorrect ad-hoc SQL. The following
information may aid in determining the deadlock:
Deadlock graph:
---------Blocker(s)-------- ---------Waiter(s)---------
Resource Name process session holds waits process session holds waits
TX-00050005-00756507 308 289 X 295 276 X
TX-0002000f-006fc0df 295 276 X 308 289 X
session 289: DID 0001-0134-00000005 session 276: DID 0001-0127-00000002
session 276: DID 0001-0127-00000002 session 289: DID 0001-0134-00000005Rakesh,
Please see if (ora-600 [12333] / ora-3137 [12333] Troubleshooting [ID 828123.1]) and/or (ORA-600 [12333] "Fatal Two-Task Protocol Violation" [ID 35928.1]) is applicable.
Did you try to bounce the database and see if you can reproduce the issue?
If you still encounter the same error, please log a SR.
Thanks,
Hussein
Maybe you are looking for
-
2011 Macbook pro painfully slow, but CPU usage is almost nothing
I brought this macbook almost a year ago now and expect that my warranty has almost run out. At first the computer was fine and i could run almost every program on the computer without effecting performance, the almost suddenly the computer became sl
-
Problem installing flash player 10
I have had a prompt on 2 windows since yesterday, that I must install the Flash Player latest version. I tried several times unsuccess fully to install. It shows in my control panel, but I'm still being told that I do not have it. I am running a 3
-
My 'mighty' mouse acts possessed
Ahoy all! A random thing has begun to happen on my mighty wireless mouse, but only in the evenings: I will be moving it and it will go in a random direction. If I leave it still, the cursor will remain in the same place, but when I move the mouse...i
-
I want to get the worksheet IDs for a workbook. I know the ID will show up in EUL5_BATCH_SHEETS and EUL5_QPP_STATS, but if a sheet has never been scheduled or "run", it will not be in those 2 tables. I am creating a portlet to access workbooks/worksh
-
Mac keys on Microsoft keyboard
I have a Microsoft wireless desktop 7000 and the Intellipoint 6.2 drivers for the Mac. The keyboard and mouse are recognized by my iMac but how but what is the equivalent of the "command" key on a non-Apple keyboard?