ORA-00368: checksum error in redo log block

Hi all

We have two node RAC instance.
11 GR 1 material [11.1.0.7] with R12.1.3 Apps

In the two journal alerts nodes with errors such as:
ORA-00368: checksum error in redo log block
ORA-00353: journal corruption near block 163842 change 3809154858 time 03/31/2013 16
: 30: 29
ORA-00334: archived log: ' / arch/1_19685_696638733.dbf '
ORA-00700: soft internal error, arguments: [kesqsMakeSql - invstat:cpuTime], [],]
], [], [], [], [], []

IAM see this error frequently,
Please help me solve the problem.

Thank you
Shaik

Shaik wrote:
Hi Hussein.

I checked, not applied the patch.

Thank you
Shaik

Please apply the patch and see if you see the same entries in the log file.

Thank you
Hussein

Tags: Oracle Applications

Similar Questions

recommended OS size for redo log block
Hello

AIX platform
Oracle 10.2.0.4

Is there any system recommended filesystem blocksize where redo log should be placed?
We tested with 512 bytes to 4 096 bytes. We got the best performance over 512 bytes in terms of waiting avg on synchronization of log file.
There's recommendation on the same oracle/AIX?
978881 wrote:
Hello

AIX platform
Oracle 10.2.0.4

Is there any system recommended filesystem blocksize where redo log should be placed?
We tested with 512 bytes to 4 096 bytes. We got the best performance over 512 bytes in terms of waiting avg on synchronization of log file.
There's recommendation on the same oracle/AIX?

The recommendation is to create logs of recovery on a mount with agblk = 512bytes. Please refer following link (page 60) which is an oracle + IBM technical brief:

http://www-03.IBM.com/support/techdocs/atsmastr.nsf/5cb5ed706d254a8186256c71006d2e0a/bae31a51a00fa0018625721f00268dc4/ $FILE/Oracle%20Architecture%20and%20Tuning%20on%20AIX%20 (v%202.30) .pdf

Kind regards
S.K.

ORA-16038, ORA-00354, ORA-00312 block header corrupt redo log
Hi all

I'm Ann. I'm not an Oracle DBA. Please bear with me. However, I have to accelerate to become a DBA during the time that the dedicated DBA is on maternity leave.
As usual, we have the online site and test site.
She gave me some notes about how to take care of the database of active and application (Oracle 10 g).
But so far, I can't do a lot of command calls the site online because we have plenty of space for the server, also the biggest part of the task has been scripted. So, it can work automatically.

However, the test database is not like that. There is not automatically restart scripts as in the live system.
Recently I canont access to the test database. So I connect to the test server, find the folder that contains the Archive Log files is nearly 98%.
So I remove some of the old dbf files (I did based on the Advisor to the Chief of this last time, it happened a long time ago)

After clear some old files, make a df h the rate at 58%.
However, the database is still not available (can't open I think)
I connect to the database, making an immediate halt, but Hung Server.
So, I ask a network engineer to restart the database server.
Of course, the machine is stop so the database must be completed.
After the machine restarts, I connect as sysdba but still cannot open the database.
The error is as below

Mounted database
ORA-16038: log 1 sequence # 1013 cannot be archived
ORA-00354: corrupted redo log block header
ORA-00312: thread 1 1 online journal:
*'/Data/oradata/barn/onlinelog/o1_mf_1_2658nhd4_.log'*
ORA-00312: thread 1 1 online journal:
*'/arclogs/oradata/BARNTEST/onlinelog/o1_mf_1_2658nhd4_.log'*

I search and I get these
ORA-16038, ORA-00354, ORA-00312 block header corrupt redo log

+ (http://arjudba.blogspot.co.nz/2008/05/ora-16038ora-00354ora-00312-corrupt.html) +.
Error description:
------------------------
Normal users could not connect to the database. He messaged ORA-00257: internal connection only up to this just released. When you try to archive the redo log, it returns the message.

ORA-16038: log %s sequence # %s cannot be archived
ORA-00354: corrupted redo log block header
ORA-00312: ' %s % s: "%s '" thread online journal

Explanation of the problem:
-------------------------------
Whenever the normal user tried to connect to the database returns the error as it is designed in

ORA-00257. But you've noticed that there is enough space in the V$ RECOVERY_FILE_DEST. Whenever you look at alerts log, you will see the ORA-16038, ORA-00354, error ORA-00312 serial. Produced error as because it doesn't have archives online redolog due to an alteration in the online redo file.

Solution of the problem:
--------------------------------
Step 1) while making your database running clearly non archived redo log.
SQL > alter the clear database untarred logfile "logilename";

What makes corruption disappear which causes the contents of the redo online deleted file.
Step 2) make a full backup of the database

Is my question here safe to apply the following steps:
We have 2 logs online that cause the error, until I need to erase the 2 files.

For step 2, how to make a backup with RMAN.
Can you suggest a command line safe for me to use. (The EM console surrently do not work on the test database server)

I really need that test database managed as my apps APEX run on this need to be exported to the live system.

Really appreciate any help here, once again, it's an Oracle 10 g release 1.

Kind regards

Published by: Ann586341 on April 30, 2012 15:40

Published by: Ann586341 on April 30, 2012 15:40
Your problem is with redolog 1

SQL > select * v log$;

check the status of the Group 1 regardless of whether ACTIVE or INACTIVE.

If it is INACTIVE, then run the command below

SQL > ALTER DATABASE CLEAR NO ARCHIVED LOGFILE GROUP 1;

then

SQL > alter database open

Published by: Vishwanath on April 30, 2012 10:11

SIZE OF THE REDO LOG FILE

Hello
I got an error message when I add me new group. log files I searched and found the answer on the form. Ago 4 M minimum size of 11 g R2 log file size.
My question is why a log file size depends on DB_BLOCK_SIZE? This parameter is set to the component structures of memory that create an instance when a log file is an operating system file that depend on the version of the OS not DB_BLOCK_SIZE.
Thank you.

SQL > alter database add logfile group 4 'c:\app\asif\oradata\employee\redo04.log' size 1 m;
alter database add logfile group 4 'c:\app\asif\oradata\employee\redo04.log' size 1 m
*
ERROR on line 1:
ORA-00336: 2048 blocks the size of the log file is minimum lower than 8192 blocks

SQL > show parameter db_block_size
VALUE OF TYPE NAME
------------------------------------ ----------- ------------------------------
Whole DB_BLOCK_SIZE 8192
SQL >

You are assuming that the redo log block size is the same as the database block size. This is not correct.

The error indicates that 8192 is the minimum number of blocks of a redo log file. The documentation states that the minimum size is 4 M. For example, you can deduct your redo log block size is 512 bytes.

Here's some more information about the size of redo log, the documentation block.

Unlike the database block size, which can always be between 2 K and 32 K, redo log default files to a block size that is equal to the size of physical sector of the disk. Historically, it is usually 512 bytes (512 b).

Some new large disks offer 4K sizes byte (4K) to increase sector efficiency improved format and ECC capabilities. Most of the Oracle database platforms are able to detect this bigger sector size. The database then automatically creates files redo log with a block size of 4 K of these discs.

Files redo log by using the optimal_logfile_size to design view.
Concerning

I have a specific question about the size of the log file. I have deployed a database of test and I was exploring some aspects regarding the selection of the optimal size of recovery for performance logs by using the view v$ instance_recovery optimal_logfile_size. My main goal is necessary for example to reduce the bytes redo recovery. Currently I have not been able to optimize the size of redo log file. Here are the steps I followed: -.

In order to use the view v$ instance_recovery, I had to put the fast_start_mttr_target parameter which is by default do not then I did as follows: -.

(1) SQL > sho parameter fast_start_mttr_target;

VALUE OF TYPE NAME
------------------------------------ --------------------------------- ------------------------------
fast_start_mttr_target integer 0

(2) setting the fast_start_mttr_target requires destroy deferred to the following parameters: -.
SQL > show parameter log_checkpoint;

VALUE OF TYPE NAME
------------------------------------ --------------------------------- ------------------------------
log_checkpoint_interval integer 0
log_checkpoint_timeout around 1800
log_checkpoints_to_alert boolean FALSE

SQL > select ISSES_MODIFIABLE, ISSYS_MODIFIABLE, ISINSTANCE_MODIFIABLE, ISMODIFIED parameter of $ v where name like 'log_checkpoint_timeout;

ISSES_MODIFIABL ISSYS_MODIFIABLE ISINSTANCE_MODI ISMODIFIED
--------------- --------------------------- --------------- ------------------------------
IMMEDIATE FALSE TRUE FALSE

SQL > alter system set log_checkpoint_timeout = 0 scope = both;

Modified system.

SQL > show parameter log_checkpoint_timeout;

VALUE OF TYPE NAME
------------------------------------ --------------------------------- ------------------------------
log_checkpoint_timeout integer 0

(3) setting fast_start_mttr_target now

SQL > select ISSES_MODIFIABLE, ISSYS_MODIFIABLE, ISINSTANCE_MODIFIABLE, ISMODIFIED parameter of $ v where name like 'fast_start_mttr_target;

ISSES_MODIFIABL ISSYS_MODIFIABLE ISINSTANCE_MODI ISMODIFIED
--------------- --------------------------- --------------- ------------------------------
IMMEDIATE FALSE TRUE FALSE

Definition of the fast_mttr_target to 1200 = 20 minutes of the control point of switching on the recommendation of the Oracle

Ask the view v instance_recovery $

(4) SQL > select ACTUAL_REDO_BLKS, TARGET_REDO_BLKS, TARGET_MTTR, ESTIMATED_MTTR, OPTIMAL_LOGFILE_SIZE, CKPT_BLOCK_WRITES from v$ instance_recovery;

ACTUAL_REDO_BLKS TARGET_REDO_BLKS TARGET_MTTR ESTIMATED_MTTR OPTIMAL_LOGFILE_SIZE CKPT_BLOCK_WRITES
---------------- ---------------- ----------- -------------- -------------------- -----------------
276 165888 * 93 * 59 361 16040

Here target MTTR was 93 so I put the fast_mttr_target to 120

SQL > alter system set fast_start_mttr_target = 120 scope = both;

Modified system.

The size of the log file suggested by v$ instance_recovery is now 290 MB

SQL > select ACTUAL_REDO_BLKS, TARGET_REDO_BLKS, TARGET_MTTR, ESTIMATED_MTTR, OPTIMAL_LOGFILE_SIZE, CKPT_BLOCK_WRITES from v$ instance_recovery;

ACTUAL_REDO_BLKS TARGET_REDO_BLKS TARGET_MTTR ESTIMATED_MTTR OPTIMAL_LOGFILE_SIZE CKPT_BLOCK_WRITES
---------------- ---------------- ----------- -------------- -------------------- -----------------
59 165888 93 59 290 16080

After you change the size of the logfile to 290 as indicated below by v$ log view;

SQL > select GROUP #, THREAD #, SEQUENCE #, BYTES of the log v$.

GROUP # THREAD # SEQUENCE # BYTES
---------- ---------- ---------- ----------
1 1 24 304087040
2 1 0 304087040
3 1 0 304087040
4 1 0 304087040
(5) after you change the size, I observed the anomaly as redo log blocks to be applied for the recovery went to * $ 59 to 696 * v instance_recovery view is now also now offers the size of the log file of * 276 MB *. Have I misunderstood something

SQL > select ACTUAL_REDO_BLKS, TARGET_REDO_BLKS, TARGET_MTTR, ESTIMATED_MTTR, OPTIMAL_LOGFILE_SIZE, CKPT_BLOCK_WRITES from v$ instance_recovery;

ACTUAL_REDO_BLKS TARGET_REDO_BLKS TARGET_MTTR ESTIMATED_MTTR OPTIMAL_LOGFILE_SIZE CKPT_BLOCK_WRITES
---------------- ---------------- ----------- -------------- -------------------- -----------------
* 696 * 646947 120 59 * 276 * 18474

If please specify the output above, that I'm unable to optimize the size of the log file and have not been able to achieve the goal of reducing the redo log blocks to apply for recovery, any help is appreciated in this regard.
I don't think that test for the optimum size of redo's CTD. Maybe if you did each week, as a regular or something, but the unique initial setup and sometimes check in production? N ° but it will be iterative as part of a deployment of init.ora Exchange.

In addition, it is part of the DBA job to understand the recovery and what to expect. Which includes the understanding of all these parameters, init and tests for the environment. It also includes an understanding of the characteristics of the application and its load.

ORA-38754: FLASHBACK DATABASE not started; required redo log is not available

Hello
I am getting below error when executing the activities of flashback. Currently we have backups, so when I tried the command flashback in RMAN my question solved.
But if I want to do the same thing using SQLPLUS what steps should I take?
ERROR:
ORA-38754: FLASHBACK DATABASE not started; required redo log is not available
ORA-38762: redo logs needed for SNA to SNA 20062842936 20062842926
ORA-38761: redo log sequence 4 in thread 2, 65 incarnation cannot
consulted
DATABASE:11.2.0.3.0 (UAT)

RMAN will automatically restore logs archived redo required for the operation of blowback when they are not present on the drive, while (as meyssoun said) when using sqlplus required archived redo logs must be available on the disc.

Concerning

AJ

ORA-19504: failed to create the file, ORA-00270: creation of the archiving log error
Hello

Oracle 11 g 2 on windows 7, I of primary and standby on the same system (learning).

When I check on status of primary and secondary use under request it gives applied log is 'NO '.

SQL > select sequence #, used from v$ archived_log;

SEQUENCE # APPLIED
---------- ---------
516 NO.
517 NO.
NO. 523
NO. 524
525 NO.
531 NO.
NO. 532
533 NO.
NO. 541
544 NO.

When I checked error on DB primary .he give me more erro.
SQL > SELECT 'ID', 'DB_status' STATUS DEST_ID, EXCURSION place "Archive_dest', 'ERROR' OF V$ ARCHIVE_DEST WHERE DEST_ID < = 5;
---------- ---------
Error Archive_dest
------------------------------------------------------------------------------------------------------------------------------------------------------
1 D:\app\kamdarvg\flash_recovery_area\test\ARCHIVELOG ORA-19504: cannot create the file «»

2 STAND ORA-00270: creation of the archiving log error

I checked the space on the system... is there enough free space on the disk.

On primary DB (destination of the journal archive)

SQL > list of archive logs
Database log mode Archive Mode
Active AutoArchive
Destination of archive D:\app\kamdarvg\flash_recovery_area\test\ARCHIVELOG
More old sequence of journal online 564
Log sequence archive 566
Current log sequence 566

On standby DB (list of newspapers of record)

SQL > list of archive logs
Database log mode Archive Mode
Active AutoArchive
Destination of archive D:\app\kamdarvg\flash_recovery_area\test\ARCHIVELOG
More old sequence of journal online 564
Log sequence archive 566
Current log sequence 566

Please guide it's because of the destination of the journal archive even shared by the standby and primary?

If yes how do I change the destination of the newspaper archive on standby DB?

Thank you.

Edited by: 977220 April 18, 2013 20:49
change initialization parameter

error in the extension of redo logs
Dear friends,

I just tried a few measures to extend some redologs and it worked.

Applied to a different database and problems.

Please guide me.

alter database drop logfile Group 1;

change the database
Add logfile group 1 ('F:\DEV\REDO01.) LOG ') SIZE 20 M;

error: ORA-00301: Error adding the log file ' F:\DEV\REDO01. NEWSPAPER "-could not create the file"
ORA-27038: created file already exists
OSD-04010: < create > option specified, the file already exists

But the first line was a success.

Please help me.

Nith
alter database add logfile group 1 ('F:\DEV\REDO01.) LOG ') SIZE 20 M REUSE;

Checksum error ORA-20503 after update
Hello

in my application, I have a page with a form based on a table. With a button I run a stored procedure in the database via javascript. This procedure changes the value of a column that is indicated in the form table. When I want to make changes in the form of the application generates an error of ORA-20503 checksum which is OK because the checksum has changed.

How is it possible to do an automatic requery after the execution of the stored procedure?

Thanks in advance.

Martin
Martin:

I think that the document on page 50 is re-loading. However, I think that reloading happens even before that your stored procedure did its thing to update the database. We can check if it in fact the case.
Change your Javascript as below
```
function waitSome()
{
clearTimeout();
window.location.reload();
}

function callReport(p_href,p_url)
{
var url;
// window.location.href = document.getElementById(p_href).value;  // dont reload here
url = document.getElementById(p_url).value;
w = open(url,"winRep","Scrollbars=1,resizable=1,width=800,height=900");
if (w.opener == null)
w.opener = self;
w.focus();
setTimeout("waitSome()",5000)   // wait 5 seconds before reloading
}
```
With these changes, doing just that now your function callReport is in the PDF window popup and then wait 5 seconds before running the 'waitSome' function which, once exected will reload the main window. You can change the amount of time waited by changing the second parameter of the function "setTimeout". The expected time is specified in milliseconds.

CITY

Redo log sizing

Hi all

OEL 5.6

Oracle 9.2.0.6

Are just my recovery for his number and connects the size based on the delay time of switching? Thank you

-rw-r--r-- 1 oraprod dba    10486272 Jan  3 23:24 log01a.dbf
-rw-r--r-- 1 oraprod dba    10486272 Jan  3 23:24 log01b.dbf
-rw-r--r-- 1 oraprod dba    10486272 Jan  3 23:09 log02a.dbf
-rw-r--r-- 1 oraprod dba    10486272 Jan  3 23:09 log02b.dbf

In the alerts log switching frequency:

Beginning log switch checkpoint up to RBA [0x21186.2.10], SCN: 0x056e.66a6d05f
Thread 1 advanced to log sequence 135558
  Current log# 1 seq# 135558 mem# 0: /u02/oracle/oaproddata/log01a.dbf
  Current log# 1 seq# 135558 mem# 1: /u02/oracle/oaproddata/log01b.dbf
Thread 1 cannot allocate new log, sequence 135559
Checkpoint not complete
  Current log# 1 seq# 135558 mem# 0: /u02/oracle/oaproddata/log01a.dbf
  Current log# 1 seq# 135558 mem# 1: /u02/oracle/oaproddata/log01b.dbf
Wed Jan  2 20:37:01 2013
Completed checkpoint up to RBA [0x21186.2.10], SCN: 0x056e.66a6d05f
Wed Jan  2 20:37:01 2013
Beginning log switch checkpoint up to RBA [0x21187.2.10], SCN: 0x056e.66a6d5e4
Thread 1 advanced to log sequence 135559
  Current log# 2 seq# 135559 mem# 0: /u02/oracle/oaproddata/log02a.dbf
  Current log# 2 seq# 135559 mem# 1: /u02/oracle/oaproddata/log02b.dbf
Thread 1 cannot allocate new log, sequence 135560
Checkpoint not complete
  Current log# 2 seq# 135559 mem# 0: /u02/oracle/oaproddata/log02a.dbf
  Current log# 2 seq# 135559 mem# 1: /u02/oracle/oaproddata/log02b.dbf
Wed Jan  2 20:37:07 2013
Completed checkpoint up to RBA [0x21187.2.10], SCN: 0x056e.66a6d5e4
Wed Jan  2 20:37:07 2013
Beginning log switch checkpoint up to RBA [0x21188.2.10], SCN: 0x056e.66a6e3f2
Thread 1 advanced to log sequence 135560
  Current log# 1 seq# 135560 mem# 0: /u02/oracle/oaproddata/log01a.dbf
  Current log# 1 seq# 135560 mem# 1: /u02/oracle/oaproddata/log01b.dbf
Wed Jan  2 20:37:18 2013
Thread 1 cannot allocate new log, sequence 135561
Checkpoint not complete
  Current log# 1 seq# 135560 mem# 0: /u02/oracle/oaproddata/log01a.dbf
  Current log# 1 seq# 135560 mem# 1: /u02/oracle/oaproddata/log01b.dbf
Wed Jan  2 20:37:18 2013
Completed checkpoint up to RBA [0x21188.2.10], SCN: 0x056e.66a6e3f2
Wed Jan  2 20:37:18 2013
Beginning log switch checkpoint up to RBA [0x21189.2.10], SCN: 0x056e.66a6f0a4
Thread 1 advanced to log sequence 135561
  Current log# 2 seq# 135561 mem# 0: /u02/oracle/oaproddata/log02a.dbf
  Current log# 2 seq# 135561 mem# 1: /u02/oracle/oaproddata/log02b.dbf
Wed Jan  2 20:40:14 2013
Completed checkpoint up to RBA [0x21189.2.10], SCN: 0x056e.66a6f0a4
Wed Jan  2 20:40:53 2013
Beginning log switch checkpoint up to RBA [0x2118a.2.10], SCN: 0x056e.66a70cb2
Thread 1 advanced to log sequence 135562
  Current log# 1 seq# 135562 mem# 0: /u02/oracle/oaproddata/log01a.dbf
  Current log# 1 seq# 135562 mem# 1: /u02/oracle/oaproddata/log01b.dbf
Wed Jan  2 20:43:24 2013
Completed checkpoint up to RBA [0x2118a.2.10], SCN: 0x056e.66a70cb2

And also I see frequently repeated ORA-1555 on the same statement in the alerts log, how can I avoid this?
Is this cause also of small redo logs?

Beginning log switch checkpoint up to RBA [0x211b2.2.10], SCN: 0x056e.70580afc
Thread 1 advanced to log sequence 135602
  Current log# 1 seq# 135602 mem# 0: /u02/oracle/oaproddata/log01a.dbf
  Current log# 1 seq# 135602 mem# 1: /u02/oracle/oaproddata/log01b.dbf
Wed Jan  2 21:26:14 2013
Completed checkpoint up to RBA [0x211b2.2.10], SCN: 0x056e.70580afc
Wed Jan  2 21:26:16 2013
ORA-01555 caused by SQL statement below (Query Duration=2913 sec, SCN: 0x056e.66a6f853):
Wed Jan  2 21:26:16 2013
 INSERT INTO RA_INTERFACE_ERRORS
 (INTERFACE_LINE_ID,
  MESSAGE_TEXT,
  INVALID_VALUE)
SELECT
INTERFACE_LINE_ID,
:b_err_msg6,
'trx_number='||T.TRX_NUMBER||','||'customer_trx_id='||TL.CUSTOMER_TRX_ID
FROM RA_INTERFACE_LINES_GT IL, RA_CUSTOMER_TRX_LINES TL, RA_CUSTOMER_TRX T
WHERE  IL.REQUEST_ID = :b1
AND    IL.INTERFACE_LINE_CONTEXT = 'ORDER ENTRY'
AND    T.CUSTOMER_TRX_ID =TL.CUSTOMER_TRX_ID
AND  IL.INTERFACE_LINE_CONTEXT = TL.INTERFACE_LINE_CONTEXT
AND IL.INTERFACE_LINE_ATTRIBUTE1 = TL.INTERFACE_LINE_ATTRIBUTE1
AND IL.INTERFACE_LINE_ATTRIBUTE2 = TL.INTERFACE_LINE_ATTRIBUTE2
AND IL.INTERFACE_LINE_ATTRIBUTE3 = TL.INTERFACE_LINE_ATTRIBUTE3
AND IL.INTERFACE_LINE_ATTRIBUTE4 = TL.INTERFACE_LINE_ATTRIBUTE4
AND IL.INTERFACE_LINE_ATTRIBUTE5 = TL.INTERFACE_LINE_ATTRIBUTE5
AND IL.INTERFACE_LINE_ATTRIBUTE6 = TL.INTERFACE_LINE_ATTRIBUTE6
AND IL.INTERFACE_LINE_ATTRIBUTE7 = TL.INTERFACE_LINE_ATTRIBUTE7
AND IL.INTERFACE_LINE_ATTRIBUTE8 = TL.INTERFACE_LINE_ATTRIBUTE8
AND IL.INTERFACE_LINE_ATTRIBUTE9 = TL.INTERFACE_LINE_ATT
Wed Jan  2 21:26:22 2013
Beginning log switch checkpoint up to RBA [0x211b3.2.10], SCN: 0x056e.7062ba10
Thread 1 advanced to log sequence 135603
  Current log# 2 seq# 135603 mem# 0: /u02/oracle/oaproddata/log02a.dbf
  Current log# 2 seq# 135603 mem# 1: /u02/oracle/oaproddata/log02b.dbf
Wed Jan  2 21:26:22 2013

How can I configure management automatic cancellation in 9i?

Thank you

If UNDO_RETENTION has no impact on the ORA-01555 error, this error message you will get in this scenario?

UNDO_RETENTION = 1800
Query running time = 1900

Works SQL and requires a block of data to read cancellation that has been updated there are 1900. Meanwhile, other users are using the system and the cancellation expired (anything above 1800) was crushed. User request will be error, and I would say that this will be an ORA-01555? Correct me if I'm wrong.

As pointed out by bby Viswarayar Maran, your UNDO_RETENTION must be on the longer duration of the query. It's what he's there for. Yes, it can happen when you commit inside a loop, but it may happen in this case, too, I think.

Actions:

1 increase the size of REDO logs
2. take another report statspack for the same period of time on a comparable day (in terms of workload, running processes, etc.) and see what it looks like

Question: Your statspack report is from 22:00 - midnight, what are your pics to load? You have a working window batch during the night which is and then charge during the day? If so, we will need to look at this time for the statspack report, too.

Waiting for redo log file missing when restore main database using RMAN backup that was taken on the database physical standby

Here's my question after tons of research and test without have the right solutions.
Target:
(1) I have a 12.1.0.2 database unique main enterprise 'testdb' as database instance running on the server "node1".
(2) I created physical standby database "stbydb" on the server "node2".
(3) DataGuard running on the mode of MaxAvailability (SYNC) with roll forward in real time 12 default c apply.
(4) primary database has 3 groups of one-man redo. (/oraredo/testdb/redo01.log redo02.log redo03.log)
(5) I've created 4 standby redo logfiles (/oraredo/testdb/stby01.log stby02.log stby03.log stby04.log)
(6) I do RMAN backup (database and archivelog) on the site of relief only.
(7) I want to use this backup for full restore of the database on the primary database.
He is a DR test to simulate the scenario that has lost every primary & Eve total servers.
Here is how to save, on the database pending:
(1) performance 'alter database recover managed standby database Cancel' to ensure that compatible data files
(2) RMAN > backup database;
(3) RMAN > backup archivelog all;
I got elements of backup and copied to primary db Server something like:
/Home/Oracle/backupset/o1_mf_nnndf_TAG20151002T133329_c0xq099p_.BKP (data files)
/Home/Oracle/backupset/o1_mf_ncsnf_TAG20151002T133329_c0xq0sgz_.BKP (spfile & controlfile)
/Home/Oracle/backupset/o1_mf_annnn_TAG20151002T133357_c0xq15xf_.BKP (archivelogs)
So here's how to restore, on the main site:
I clean all the files (data files, controlfiles oder all gone).
(1) restore spfile from pfile
RMAN > startup nomount
RMAN > restore spfile from pfile ' / home/oracle/pfile.txt' to ' / home/oracle/backupset/o1_mf_ncsnf_TAG20151002T133329_c0xq0sgz_.bkp';
(2) modify pfile to convert to db primary content. pFile shows below
*.audit_file_dest='/opt/Oracle/DB/admin/testdb/adump '
* .audit_trail = "db".
* full = '12.1.0.2.0'
*.control_files='/oradata/testdb/control01.ctl','/orafra/testdb/control02.ctl'
* .db_block_size = 8192
* .db_domain = "
*.db_file_name_convert='/testdb/','/testdb /'
* .db_name = "testdb".
* .db_recovery_file_dest ='/ orafra'
* .db_recovery_file_dest_size = 10737418240
* .db_unique_name = "testdb".
*.diagnostic_dest='/opt/Oracle/DB '
* .fal_server = "stbydb".
* .log_archive_config = 'dg_config = (testdb, stbydb)'
* .log_archive_dest_2 = "service = stbydb SYNC valid_for = (ONLINE_LOGFILE, PRIMARY_ROLE) db_unique_name = stbydb'"
* .log_archive_dest_state_2 = 'ENABLE '.
*.log_file_name_convert='/testdb/','/testdb /'
* .memory_target = 1800 m
* .open_cursors = 300
* runoff = 300
* .remote_login_passwordfile = "EXCLUSIVE."
* .standby_file_management = "AUTO".
* .undo_tablespace = "UNDOTBS1.
(3) restart db with updated file pfile
SQLPLUS > create spfile from pfile='/home/oracle/pfile.txt'
SQLPLUS > the judgment
SQLPLUS > startup nomount
(4) restore controlfile
RMAN > restore primary controlfile to ' / home/oracle/backupset/o1_mf_ncsnf_TAG20151002T133329_c0xq0sgz_.bkp';
RMAN > change the editing of the database
(5) all elements of backup catalog
RMAN > catalog starts by ' / home/oracle/backupset / '.
(6) restore and recover the database
RMAN > restore database;
RMAN > recover database until the SNA XXXXXX; (this YVERT is the maximum in archivelog backups that extends beyond the scn of the backup of the data file)
(7) open resetlogs
RMAN > alter database open resetlogs;
Everything seems perfect, except one of the file log roll forward pending is not generated
SQL > select * from v$ standby_log;
ERROR:
ORA-00308: cannot open archived log ' / oraredo/testdb/stby01.log'
ORA-27037: unable to get file status
Linux-x86_64 error: 2: no such file or directory
Additional information: 3
no selected line
I intended to use the same backup to restore primary basic & helps record traffic and the downtime between them in the world of real output.
So I have exactly the same steps (except STANDBY restore CONTROLFILE and not recover after database restore) to restore the database pending.
And I got the same missing log file.
The problem is:
(1) complete alert.log filled with this error, not the concern here
(2) now repeat it in real time apply won't work since the Party shall LGWR shows always "WAITING_FOR_LOG."
(3) I can't delete and re-create this log file
Then I tried several and found:
The missing standby logfile was still 'ACTIVE' at present RMAN backup was made.
For example, on db standby, under Group #4 (stby01.log) would be lost after the restoration.
SQL > select GROUP #, SEQUENCE #, USE (s), the STATUS from v$ standby_log;
GROUP # SEQUENCE # USED STATUS
---------- ---------- ---------- ----------
4 19 ACTIVE 133632
5 0 0 UNASSIGNED
6 0 0 not ASSIGNED
7 0 0 UNASSIGNED
So until I take the backup, I tried on the primary database:
SQL > alter system set log_archive_dest_state_2 = delay;
This was the Group of standby_log side Eve #4 was released:
SQL > select GROUP #, SEQUENCE #, USE (s), the STATUS from v$ standby_log;
GROUP # SEQUENCE # USED STATUS
---------- ---------- ---------- ----------
4 0 0 UNASSIGNED
5 0 0 UNASSIGNED
6 0 0 not ASSIGNED
7 0 0 UNASSIGNED
Then, the backup has been restored correctly without missing standby logfile.
However, to change this primary database means break DataGuard protection when you perform the backup. It's not accept on the production environment.
Finally, my real questions come:
(1) what I do may not do on parameter change?
(2) I know I can re-create the control file to redo before delete and then recreate after. Is there any simple/fast to avoid the standby logfile lost or recreate the lost one?
I understand that there are a number of ways to circumvent this. Something to keep a copy of the log file waiting restoration progress and copy up one missing, etc, etc...
And yes I always have done no real-time applies "to the aid of archived logfile" but is also not accept mode of protection of production.
I just want proof that the design (which is displayed in a few oracle doc Doc ID 602299.1 is one of those) that backs up data backup works effectively and can be used to restore the two site. And it may be without spending more time to resume backups or put the load on the primary database to create the database before.
Your idea is very much appreciated.
Thank you!

Hello

1--> when I take via RMAN backup, RMAN does not redo log (ORL or SRL) file, so we cannot expect ORLs or SRL would be restored.

2nd--> when we opened the ORL database should be deleted and created

3rd--> Expecting, SRL should not be an issue.we should be able to do away with the fall.

DR sys@cdb01 SQL > select THREAD #, SEQUENCE #, GROUP #, STATUS from v$ standby_log;

THREAD # SEQUENCE # GROUP # STATUS

---------- ---------- ---------- ----------

1 233 4 ACTIVE

1 238 5 ACTIVE

DR sys@cdb01 SQL > select * from v$ logfile;

GROUP # STATUS TYPE MEMBER IS_ CON_ID

---------- ------- ------- ------------------------------ --- ----------

3 /u03/cdb01/cdb01/redo03.log no. 0 online

/U03/cdb01/cdb01/redo02.log no. 0 2 online

1 /u03/cdb01/cdb01/redo01.log no. 0 online

4 /u03/cdb01/cdb01/stdredo01.log WATCH No. 0

/U03/cdb01/cdb01/stdredo02.log EVE 5 No. 0

DR sys@cdb01 SQL > ! ls - ltr /u03/cdb01/cdb01/stdredo01.log

method: cannot access the /u03/cdb01/cdb01/stdredo01.log: no such file or directory

DR sys@cdb01 SQL >! ls - ltr /u03/cdb01/cdb01/stdredo02.log

-rw - r-. 1 oracle oinstall 52429312 17 Oct 15:32 /u03/cdb01/cdb01/stdredo02.log

DR sys@cdb01 SQL > alter database force claire logfile 4;

change the database group claire logfile 4

*

ERROR on line 1:

ORA-01156: recovery or current flashback may need access to files

DR sys@cdb01 SQL > alter database recover managed standby database cancel;

Database altered.

DR sys@cdb01 SQL > change the database group claire logfile 4;

Database altered.

DR sys@cdb01 SQL > ! ls - ltr /u03/cdb01/cdb01/stdredo01.log

-rw - r-. 1 oracle oinstall 52429312 17 Oct 15:33 /u03/cdb01/cdb01/stdredo01.log

DR sys@cdb01 SQL >

If you do, you can recreate the controlfile without waiting for redo log entry...

If you still think it's something is not acceptable, you must have SR with support to analyze why he does not abandon SRL when controlfile_type is "underway".

Thank you

Will the DB down if INACTIVE redo log group is deleted?

Platform: Oracle Linux 6.5

DB version: 11.2

If I delete one or all members of a Redo Log group online that is IDLE, manually (using the rm command) will be the DB crash?

Instead of everybody speculating, why not just run a test?

Oracle 11.2.0.1, Enterprise Edition, 64-bit on OL 5, running in archivelog mode

SQL> select group#,
  2 sequence#,
  3 archived,
  4 status
  5  from v$log
  6 order by group#
  7  ;
    GROUP# SEQUENCE# ARC STATUS
---------- ---------- --- ----------------
 1    1 YES INACTIVE
 2    2 YES INACTIVE
 3    3 NO  CURRENT
3 rows selected.
SQL> --
SQL> insert into scott.mytest values (sysdate);
1 row created.
SQL> commit;
Commit complete.
SQL> alter system switch logfile;
System altered.
SQL> select * from v$logfile;
    GROUP# STATUS  TYPE MEMBER  IS_
---------- ------- ------- ------------------------------ ---
 3 ONLINE /oradata/tulsa/redo03.rdo  NO
 2 ONLINE /oradata/tulsa/redo02.rdo  NO
 1 ONLINE /oradata/tulsa/redo01.rdo  NO
3 rows selected.
SQL>
SQL> select group#,
  2 sequence#,
  3 archived,
  4 status
  5  from v$log
  6 order by group#
  7  ;
    GROUP# SEQUENCE# ARC STATUS
---------- ---------- --- ----------------
 1    4 NO  CURRENT
 2    2 YES INACTIVE
 3    3 NO  ACTIVE
3 rows selected.

Group 2 is inactive, so delete the

SQL> !rm /oradata/tulsa/redo02.rdo
SQL> !ls -l /oradata/tulsa/redo02.rdo
ls: /oradata/tulsa/redo02.rdo: No such file or directory

And continue the activity of db. Keep an eye on the #2 group

SQL> select group#,
  2 sequence#,
  3 archived,
  4 status
  5  from v$log
  6 order by group#
  7  ;
    GROUP# SEQUENCE# ARC STATUS
---------- ---------- --- ----------------
 1    4 NO  CURRENT
 2    2 YES INACTIVE
 3    3 YES ACTIVE
3 rows selected.
SQL> insert into scott.mytest values (sysdate);
1 row created.
SQL> commit;
Commit complete.
SQL> alter system switch logfile;
System altered.
SQL> --
SQL> select group#,
  2 sequence#,
  3 archived,
  4 status
  5  from v$log
  6 order by group#
  7  ;
    GROUP# SEQUENCE# ARC STATUS
---------- ---------- --- ----------------
 1    4 NO  ACTIVE
 2    5 NO  CURRENT
 3    3 YES ACTIVE
3 rows selected.
SQL> insert into scott.mytest values (sysdate);
1 row created.
SQL> commit;
Commit complete.
SQL> alter system switch logfile;
System altered.
SQL> --
SQL> select group#,
  2 sequence#,
  3 archived,
  4 status
  5  from v$log
  6 order by group#
  7  ;
    GROUP# SEQUENCE# ARC STATUS
---------- ---------- --- ----------------
 1    4 YES INACTIVE
 2    5 NO  ACTIVE
 3    6 NO  CURRENT
3 rows selected.
SQL> insert into scott.mytest values (sysdate);
1 row created.
SQL> commit;
Commit complete.
SQL> alter system switch logfile;
System altered.
SQL> --
SQL> select group#,
  2 sequence#,
  3 archived,
  4 status
  5  from v$log
  6 order by group#
  7  ;
    GROUP# SEQUENCE# ARC STATUS
---------- ---------- --- ----------------
 1    7 NO  CURRENT
 2    5 NO  ACTIVE
 3    6 NO  ACTIVE
3 rows selected.
SQL> insert into scott.mytest values (sysdate);
1 row created.
SQL> commit;
Commit complete.
SQL> alter system switch logfile;

At this point, the SWTICH LOGFILE command has been attached, and in the alerts log, we see this:

CJQ0 started with pid=26, OS id=4817
Sat Sep 19 10:48:11 2015
Thread 1 advanced to log sequence 4 (LGWR switch)
  Current log# 1 seq# 4 mem# 0: /oradata/tulsa/redo01.rdo
Sat Sep 19 10:48:11 2015
Archived Log entry 1 added for thread 1 sequence 3 ID 0xdaf1e381 dest 1:
Sat Sep 19 10:48:44 2015
Thread 1 advanced to log sequence 5 (LGWR switch)
  Current log# 2 seq# 5 mem# 0: /oradata/tulsa/redo02.rdo
Sat Sep 19 10:48:44 2015
Archived Log entry 2 added for thread 1 sequence 4 ID 0xdaf1e381 dest 1:
Thread 1 cannot allocate new log, sequence 6
Checkpoint not complete
  Current log# 2 seq# 5 mem# 0: /oradata/tulsa/redo02.rdo
Thread 1 advanced to log sequence 6 (LGWR switch)
  Current log# 3 seq# 6 mem# 0: /oradata/tulsa/redo03.rdo
Sat Sep 19 10:48:48 2015
Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc3_4789.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc3_4789.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Thread 1 advanced to log sequence 7 (LGWR switch)
  Current log# 1 seq# 7 mem# 0: /oradata/tulsa/redo01.rdo
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance tulsa - Archival Error
Thread 1 cannot allocate new log, sequence 8
Checkpoint not complete
  Current log# 1 seq# 7 mem# 0: /oradata/tulsa/redo01.rdo
ORA-16038: log 2 sequence# 5 cannot be archived
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc3_4789.trc:
ORA-16038: log 2 sequence# 5 cannot be archived
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
Sat Sep 19 10:48:48 2015
Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc0_4777.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc0_4777.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Sat Sep 19 10:48:48 2015
Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_m000_4864.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Checker run found 2 new persistent data failures
ORACLE Instance tulsa - Can not allocate log, archival required
Thread 1 cannot allocate new log, sequence 8
All online logs needed archiving
  Current log# 1 seq# 7 mem# 0: /oradata/tulsa/redo01.rdo
Sat Sep 19 10:48:59 2015
Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc2_4785.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc2_4785.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Sat Sep 19 10:48:59 2015
Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc1_4781.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc1_4781.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Sat Sep 19 10:49:59 2015
Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc2_4785.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc2_4785.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Sat Sep 19 10:49:59 2015
Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc3_4789.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc3_4789.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Sat Sep 19 10:49:59 2015
Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_m000_5163.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3

ORA-00600: internal error code, arguments: [qmcxeExUseLoc93] with xmltable and big bows in the CLOB column

Hi all
Running the following:
Oracle Database 11 g Enterprise Edition Release 11.2.0.2.0 - 64 bit Production
PL/SQL Release 11.2.0.2.0 - Production
"CORE 11.2.0.2.0 Production."
AMT for IBM/AIX RISC System/6000: Version 11.2.0.2.0 - Production
NLSRTL Version 11.2.0.2.0 - Production
Create a view of a relational table and XMLTABLE and extract nodes from voluminous of the xmltable, mapped text using COLUMNS. I concatenate the text nodes in an xml element in the XQuery xmltable, simple sequencing:
```
<CONTENT>
{$i/summary/text(),$i/know/text(),$i/considerations/text(),$i/look_for/text(),
$i/nc//text(),$i/level1//text(),$i/level2//text(),$i/ipocc//text()}
</CONTENT>
```
SQLDeveloper query execution and right on when I scroll the 50th outcome accordingly set or... DB connection is closed and stack following error appears:
[ORA-00600: internal error code, arguments: [qmcxeExUseLoc93], [], [], [], [], [], [], [], [], [], []]
00600 00000 - "internal error code, arguments: [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s] '.
* Cause: It's the generic internal error for Oracle program number
exceptions. This indicates that a process has encountered a
Exceptional condition.
* Action: Report as a bug - the first argument is the internal error number
I went site Oracle Support to use the 'search' for these types of errors, but he found nothing to the argument: "qmcxeExUseLoc93"... any ideas short of opening an SR with Oracle support? S/n reports that no problems with memory or tablespace... trace files report a stack trace is complete:
[ORA-00600: internal error code, arguments: [qmcxeExUseLoc93], [], [], [], [], [], [], [], [], [], []]
= Dump for incident 32114 (ORA 600 [qmcxeExUseLoc93]) =.
2014-04-08 07:31:51.369
dbkedDefDump(): from the default crash dumps (flags = 0x2, level = 3, mask = 0 x 0)
-Run SQL statement for the current session (sql_id = 0qn4zxr0stgjh).
SELECT ID, CONTENT of ort_active_content_en_vw
-Call trace stack memory-
call call entered the argument values in hex
location point type (? means dubious value)
-------------------- -------- -------------------- ----------------------------
skdstdst () + 40 bl 107ca 9980 FFFFFFFFFFD99A8? 000002004?
000000001? 000000003?
000000000? 000000002?
000000001? 000000000?
ksedst1 () + 104 call skdstdst() FFFFFFFFFFD89B0? 000002004?
110641000? 1098C 1164?
110641000? 000000000?
FFFFFFFFFFD8AE0? 700000007?
ksedst () + 40 call ksedst1() 3030000000000? 002050033?
1098C 1158? 700000000025C?
000000000? 000000000?
1098C07B8? 000000000?
dbkedDefDump (+ 2828) call ksedst() FFFFFFFFFFD8B90? 000000000?
000000000? 000000000?
000000000? 000000000?
000000000? 300000003?
…….
-Binary stack dump-
= FRAME [1] (skdstdst () + 40 - > 107ca 9980) =.
defined by pointers frame 0xffffffffffd88b0 and 0xffffffffffd8840
CALL TYPE: bl ERROR REPORTED: no COMPONENT: (null)
0xffffffffffd8840 to 0xffffffffffd88b0 memory dump
FFFFFFFFFFD8840 0FFFFFFF FFFD88B0 42422220 098C 1158 [...] BB '... X]
08EBE70C FFFFFFFFFFD8850 00000001 00000001 10641000 [... d..]
FFFFFFFFFFD8860 00000000 00000000 0FFFFFFF FFFD89E8 [...]
FFFFFFFFFFD8870 0FFFFFFF FFFD99A8 00000000 00002004 [...].
FFFFFFFFFFD8880 00000003 00000000 00000000 00000001 [...]
FFFFFFFFFFD8890 00000000 00000000 00000000 00000002 [...]
FFFFFFFFFFD88A0 00000000 00000001 00000000 00000000 [...]
= SETTING [2] (ksedst1 () + 104-> skdstdst()) =.
defined by pointers frame 0xffffffffffd89b0 and 0xffffffffffd88b0
TYPE of CALL: call ERROR REPORTED: no COMPONENT: KSE
0xffffffffffd88b0 to 0xffffffffffd89b0 memory dump
FFFFFFFFFFD88B0 0FFFFFFF FFFD89B0 42422220 10317 68 A... 1zh BB"]
FFFFFFFFFFD88C0 1033F758 00000001 00000001 0014963C [... <...] 3.X]
FFFFFFFFFFD88D0 09ED0CA9 1873F04F 28422848 73743231... Sagna (B (Hst21]
FFFFFFFFFFD88E0 0FFFFFFF FFFD89B0 00000000 00002004 [...].
FFFFFFFFFFD88F0 00000001 00000001 10641000 098C 1164 [... d...d]
FFFFFFFFFFD8900 00000001 10641000 00000000 00000000 [... d...]
……
-Status of the Dump process (2).
===================================================
STATE OF THE PROCESS
-------------
Global information process:
process: 0x700000012b18de8, call: 0x70000000b880ee0, xact: 0x0, curses: 0x700000012bf11f0, usrses: 0x700000012bf11f0
in_exception_handler: no
----------------------------------------
SO: 0x700000012b18de8, type: 2, owner: 0x0, flag: INIT /-/-/ 0x00 if: 0 x 3 c: 0 x 3
proc = 0x700000012b18de8, name = process, queue = ksu.h LINE: 12451 ID:, pg = 0
(process) Oracle pid:42, ser:153, called heart/high: 0x70000000b880ee0/0x70000000b880ee0
flags: (0x0).
Flags2: (0 x 800), flags3: (0x0)
Intr error: call error 0,: 0, sess error: error of txn, 0, 0
queue intr: vacuum
ksudlp FALSE to the location: 0
(post info) last message received: 0 0 0
Last message received-card: no post
last process affect me: no
Last message sent: 0 0 26
Last message sent-map: ksa2.h LINE: 282 ID:ksasnd
last process posted by me: 6 1 700000012af9058
(info from latch) wait_event = 0 bits = 0
Process group: by DEFAULT, proc pseudo: 0x700000012b4db88
Info of the o/s: user: tst214, duration: UNKNOWN, ospid: 4370650
OSD pid Info: Unix process pid: 4370650, image: oracle@mldb2385
----------------------------------------
SO: 0x700000010430ba0, type: 10, owner: 0x700000012b18de8, flag: INIT /-/-/ 0x00 if: c: 0x1 0x1
proc = 0x700000012b18de8, name = FileOpenBlock, leader is ksfd.h LINE: 6337 ID:, pg = 0
(FOB) flags = 2050 fib = 700000010de3758 incno = 0 waiting for IO cnt = 0
fname=/tst214_01/oradata/TST214/temp01.dbf
FNO = 201 lblksz = 8192 fsiz = 36608
----------------------------------------
SO: 0 x 700000010430578, type: 10, owner: 0x700000012b18de8, flag: INIT /-/-/ 0x00 if: c: 0x1 0x1
proc = 0x700000012b18de8, name = FileOpenBlock, leader is ksfd.h LINE: 6337 ID:, pg = 0
(FOB) flags = 2050 fib = 700000010de2b40 incno = 0 waiting for IO cnt = 0
fname=/tst214_03/oradata/TST214/ort_data01.dbf
FNO = 6 lblksz = 8192 fsiz = 25600
----------------------------------------
SO: 0x70000001042ff38, type: 10, owner: 0x700000012b18de8, flag: INIT /-/-/ 0x00 if: c: 0x1 0x1
proc = 0x700000012b18de8, name = FileOpenBlock, leader is ksfd.h LINE: 6337 ID:, pg = 0
(FOB) flags = 2050 fib = 700000010de1310 incno = 0 waiting for IO cnt = 0
fname=/tst214_01/oradata/TST214/sysaux01.dbf
FNO = 2 lblksz = 8192 fsiz = 89600
----------------------------------------
SO: 0x70000001042f910, type: 10, owner: 0x700000012b18de8, flag: INIT /-/-/ 0x00 if: c: 0x1 0x1
proc = 0x700000012b18de8, name = FileOpenBlock, leader is ksfd.h LINE: 6337 ID:, pg = 0
(FOB) flags = 2050 fib = 700000010de0d10 incno = 0 waiting for IO cnt = 0
fname=/tst214_01/oradata/TST214/System01.dbf
FNO = 1 lblksz = 8192 fsiz = 96000
----------------------------------------
SO: 0x700000012bf11f0, type: 4, owner: 0x700000012b18de8, flag: INIT /-/-/ 0x00 if: 0 x 3 c: 0 x 3
proc = 0x700000012b18de8, name = session, lead = ksu.h LINE: 12459 ID:, pg = 0
(session) sid: 41 ser: 1263 trans: 0x0, creator: 0x700000012b18de8
indicators: (0 x 8000045) USR /-flags_idl: (0 x 1) BSY /-/ - /-/ - / -.
Flags2: (0 x 40008) - / -.
DID:, DID in the short term:
TXN branch: 0x0
Oct: 3, prv: 0, sql: 0x70000000c59dbd0, psql: 0x70000000b196c38, user: 73/ORT_READ
ksuxds FALSE to the location: 0
name of the service: the USERS of SYS$
Customer details:
Info of the o/s: user: norman.jonker, duration: unknown, ospid: 6224
machine: G4021165 program: SQL Developer
application name: SQL Developer, hash value = 1012150930
Battery active waiting:
No waiting; last waiting ended 2,617517 sec ago
Wait state:
fixed_waits = 0 flags = 0 x 21 limit = 0 x 0 /-1
History of waiting for session:
elapsed time of 2,617552 sec from last wait
0: waiting for 'direct path read '.
number = 0 x 6, first s/n = 0 x 2901, block cnt = 0 x 2
wait_id = 2222 seq_num = 2223 snap_id = 1
wait time: snap = 0,000035 s, exc = 0,000035 s, total s = 0,000035
wait time: max = infinite
wait charges: calls = 0 os = 0
After 0,029003 seconds time elapsed
1: expected "asynch descriptor resize.
#aio in circulation = 0 x 0, the current limit of aio = 0xc8, this capping aio = 0 x 145
wait_id = 2221 seq_num = 2222 snap_id = 1
wait time: snap = 0,000003 s, exc = 0,000003 s, total s = 0,000003
wait time: max = 307445734561 min 49sec
wait charges: calls = 0 os = 0
After 0,000710 seconds time elapsed
"2: expected ' SQL * Net message to client"
pilot-id = 0 x 54435000, #bytes = 0 x 1, = 0x0
wait_id = 2220 seq_num = 2221 snap_id = 1
wait time: snap = 0,000005 dry, exc = 0,000005, total = 0,000005 sec
wait time: max = infinite
wait charges: calls = 0 os = 0
After 0,001452 seconds time elapsed
3: expected ' SQL * Net client message'
pilot-id = 0 x 54435000, #bytes = 0 x 1, = 0x0
wait_id = 2219 seq_num = 2220 snap_id = 1
wait time: snap = 0,499033 s, exc = 0,499033 s, total s = 0,499033
wait time: max = infinite
wait charges: calls = 0 os = 0
After 0,000034 seconds time elapsed
"4: expected ' SQL * Net message to client"
pilot-id = 0 x 54435000, #bytes = 0 x 1, = 0x0
wait_id = 2218 seq_num = 2219 snap_id = 1
wait time: snap = 0,000003 s, exc = 0,000003 s, total s = 0,000003
wait time: max = infinite
wait charges: calls = 0 os = 0
After 0,000048 seconds time elapsed
5: expected ' SQL * Net client message'
pilot-id = 0 x 54435000, #bytes = 0 x 1, = 0x0
wait_id = 2217 seq_num = 2218 snap_id = 1
wait time: snap = 0,061319 s, exc = 0,061319 s, total s = 0,061319
wait time: max = infinite
wait charges: calls = 0 os = 0
After 0,000028 seconds time elapsed
"6: expected ' SQL * Net message to client"
pilot-id = 0 x 54435000, #bytes = 0 x 1, = 0x0
wait_id = 2216 seq_num = snap_id 2217 = 1
wait time: snap = 0,000003 s, exc = 0,000003 s, total s = 0,000003
wait time: max = infinite
wait charges: calls = 0 os = 0
After 0,000048 seconds time elapsed
7: expected ' SQL * Net client message'
pilot-id = 0 x 54435000, #bytes = 0 x 1, = 0x0
wait_id = 2215 seq_num = 2216 snap_id = 1
wait time: snap = 0,063435 s, exc = 0,063435 s, total s = 0,063435
wait time: max = infinite
wait charges: calls = 0 os = 0
After 0,000045 seconds time elapsed
"8: expected ' SQL * Net message to client"
pilot-id = 0 x 54435000, #bytes = 0 x 1, = 0x0
wait_id = 2214 seq_num = 2215 snap_id = 1
wait time: snap = 0,000003 s, exc = 0,000003 s, total s = 0,000003
wait time: max = infinite
wait charges: calls = 0 os = 0
After 0,000070 seconds time elapsed
9: expected ' SQL * Net client message'
pilot-id = 0 x 54435000, #bytes = 0 x 1, = 0x0
wait_id = 2213 seq_num = 2214 snap_id = 1
wait time: snap = 0,060780 s, exc = 0,060780 s, total s = 0,060780
wait time: max = infinite
wait charges: calls = 0 os = 0
After 0,000030 seconds time elapsed
The Session history sampled session 1263 series 41
---------------------------------------------------
History of the sampled session is built by sampling
the session target all the 1 second. The sampling process
capture to each sample, if the session is in an active waiting.
a wait inactive, or not in a wait. If the session is in a
active wait interval then one is indicated for all samples
the session was in the same active waiting. If the
session is in an inactive waiting or not waiting for
consecutive samples then one interval is indicated for all
consecutive samples. If we post these consecutive
samples in a single interval session may NOT be permanently
inactive or not in a wait (the sampling process is unclear).
The history is displayed in reverse chronological order.
sampling interval: 1 s, max 120 sec history
---------------------------------------------------
[3 samples, 07:31:51 - 07: 31:53]
not waiting at each sample
[18 samples, 07:31:33 - 07: 31:50]
waiting in each sample slowed
[2 samples, 07:31:31 - 07: 31:32]
not waiting at each sample
[42 samples, 07:30:49 - 07:31:30]
waiting in each sample slowed
[4 biopsies, 07:30:45 - 07: 30:48]
not waiting at each sample
[7 samples, 07:30:38 - 07: 30:44]
waiting in each sample slowed
[sample 1, 07:30:37]
waited for ' SQL * Net break/reset for customer ', seq_num: 1149
P1: 'driver id' = 0 x 54435000
P2: 'pause '? = 0 x 0
P3: "= 0x0
time_waited: 0,013444 sec (sampling interval: 0 sec)
[14 samples, 07:30:23 - 07: 30:36]
waiting in each sample slowed
[4 biopsies, 07:30:19 - 07: 30:22]
not waiting at each sample
[26 samples, 07:29:53 - 07:30:18]
waiting in each sample slowed
---------------------------------------------------
History of the sampled plenary:
longest_non_idle_wait: ' SQL * Net break/reset for customer '
[sample 1, 07:30:37]
time_waited: 0,013444 sec (sampling interval: 0 sec)
---------------------------------------------------
the temporary object counter: 2
----------------------------------------
Virtual discussion:
kgskvt: 700000011f06658, sess: 700000012bf11f0 sid: 41 ser: 1263
VC: 0, proc: 700000012b18de8, id: 41
News consumer group: OTHER_GROUPS (upd? 0) maps: DEFAULT_CONSUMER_GROUP, orig:
vt_state: 0x100, vt_flags: 0xA030, blkrun: 0, numa: 1
inwait: 0
place where last insched series: kgskthrrun
place where insched last reset: kgskthrrun2
place where inwait the last value: NULL
place where inwait last reset: kgskbindfast
is_assigned: 1, in_sched: 0 (0)
QCLs: 0, qlink: FALSE
vt_active: 0 (pending: 1).
vt_pq_active: 0, dop: 0
used quanta: 0 (cg: 0) usec, num penalty: 0
start of CPU time: 0
idle time: 0, time: 0 (cg: 0)
yields of processor: 0 (cg: 0), expected: 0 (cg: 0), wait time: 0 (cg: 0) usec
e/s expected: 0 (cg: 0), wait time: 0 (cg: 0) usec
ASL in queue wait times: 0, time: 0 (NEWS 0, 0 cg)
PQQ in queue wait times: 0, time: 0 (NEWS 0, 0 cg)
Violation of the time to wait in queue: 0
aborted calls: 0, num is exec hit limit: 0
Cancel current: max k 0: 0 k
I/O credits: small = 0 General = 0
I/O waiting credits: small = 0 General = 0
KTU Session Commit Cache Dump for IDLs:
XID: 0x0009.008.00002025 RCS: flg 0x0000.00cd4e90 = 0x1
XID: 0x0006.018.00001f5a RCS: flg 0x0000.00cd4e90 = 0x1
XID: 0x0009.015.00002024 RCS: flg 0x0000.00cd4e90 = 0x1
XID: 0x0005.004.00001f30 RCS: flg 0x0000.00cd4e90 = 0x1
XID: 0x0006.021.000011ed RCS: flg 0x0000.00cd4e90 = 0x1
KTU Session Commit Cache Dump for Non-IDLs:
----------------------------------------
KKS - UOL used: 0 locks (used = 19, free = 3)
KGX atomic operation Log 70000000b30a840
Mutex 0 (0, 0) oper idn 0 NONE
Cursor Parent uid 41 DTS 4 w/h 7 slp 0
Oper = pt1 NONE = 0 pt2 pt3 0 = 0 =
PT4 = 0 = 0 = 0 stt u41
KGX atomic operation Log 70000000b30a890
Mutex 0 (0, 0) oper idn 0 NONE
parasite of the slp whr 6 table uid 41 DTS torrent 4 0
Oper = NONE pt1 = 70000000d1485e8 pt2 = pt3 148678 = 0 70000000d
PT4 = 0 = 0 = 0 stt u41
KGX atomic operation Log 70000000b30a8e0
Mutex 0 (0, 0) oper idn 0 NONE
FSO uid 41 DTS mutex 0 w/h 0 slp 0
KGX atomic operation Log 70000000b30a930
Mutex 0 (0, 0) oper idn 0 NONE
FSO uid 41 DTS mutex 0 w/h 0 slp 0
----------------------------------------
KGL - UOL SO Cache (total = 182, free = 107)
KGX atomic operation Log 70000000 b 045538
Mutex 0 (0, 0) oper idn 0 NONE
Library Cache uid 41 DTS 5 w/h 85 slp 0
Oper = 0 = 70000000b 227350 pt2 = pt3 = 0 70000000c5df180 pt1
PT4 = 0 = 0 = 0 ub4 pt5
KGX atomic operation Log 70000000 b 045590
Mutex (0, 0) 70000000c5b11d8 idn 69fd5d60 oper NONE
Library Cache uid 41 DTS 4 w/h 77 slp 0
Oper = pt1 pt2 70000000934fb60 0 = = 0 = 0 pt3
PT4 = 0 = 0 = 0 ub4 pt5
KGX atomic operation Log 70000000b0455e8
Mutex 0 (0, 0) oper idn 0 NONE
Library Cache uid 41 DTS 4 w/h 79 slp 0
Oper = 0 = 70000000b 225950 pt2 = pt3 = 0 70000000c382cb8 pt1
PT4 = 0 = 0 = 0 ub4 pt5
KGX atomic operation Log 70000000 b 045640
Mutex (0, 0) 70000000b225a80 idn ae8e84f6 oper NONE
Library Cache uid 41 DTS 4 w/h 70 slp 0
Oper = 0 = 70000000b 225950 pt2 = 0 = 0 pt3, pt1
PT4 = pt5 0 = 0 ub4 = 4
KGX atomic operation Log 70000000 b 045698
Mutex (0, 0) 70000000b225a80 idn ae8e84f6 oper NONE
Library Cache uid 41 DTS 4 w/h 70 slp 0
Oper = 0 = 70000000b 225950 pt2 = 0 = 0 pt3, pt1
PT4 = 0 = 0 = 0 ub4 pt5
KGX atomic operation Log 70000000b0456f0
Mutex 0 (0, 0) oper idn 0 NONE
Library Cache 41 DTS uid 0 w/h 0 slp 0
Oper = pt1 pt2 = pt3 0 = 0 0 = 0
PT4 = 0 = 0 = 0 ub4 pt5
KGX atomic operation Log 70000000 b 045748
Mutex 0 (0, 0) oper idn 0 NONE
Library Cache 41 DTS uid 0 w/h 0 slp 0
Oper = pt1 pt2 = pt3 0 = 0 0 = 0
PT4 = 0 = 0 = 0 ub4 pt5
KGL SO hide
SO = 70000000c5df180 link = 70000000c5df1f0 [70000000b115e38, b 70000000, 045520]
FLG = 8000 use its 700000012bf11f0 = 700000012bf11f0 =
SO = 70000000b115dc8 link = 70000000b115e38 [70000000c5df380, 70000000c5df1f0]
FLG = 8000 use its 700000012bf11f0 = 700000012bf11f0 =
SO = 70000000c5df310 link = 70000000c5df380 [70000000c7abab8, 70000000b115e38]
FLG = 8000 use its 700000012bf11f0 = 700000012bf11f0 =

Hello

I'm not saying that it will solve the problem, but you must use XMLCast in this case, not XMLSerialize.

Try also with fn:local - name instead (unless you need information namespace as well):

Select (xmlcast)

XMLQUERY)

"for $dcrContent in fn:collection("oradb:/PUBLIC/DATA_CAPTURE_RECORD_CONTENT") / ROW.

where $dcrContent/DATA_CAPTURE_RECORD_CONTENT_ID = xs:decimal ($id)

"return fn:local - name($dcrContent/CONTENT_XML/*)"

from 608 as "id".

contents of return

)

as varchar2 (100)

)

Double;

waiting for redo log deleted

Oracle 11 g 2 (11.2.0.3) Linux x86_64
A silly mistake was made. While recreate redo standby logfiles, I managed to remove (rm command) waiting for redo log file in progress (before the end of the application) of the BONE. Now I see in the log of alerts:
```
ORA-00313: open failed for members of log group 7 of thread 1
ORA-00312: online log 7 thread 1: ..../standby_redo7.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
```
What are my options at this point? I have to any cancelled transaction? The settlement seems to be moving right on the property. Where am I people?
Thanks to you all.

Hello

1 ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;

2. ALTER LOGFILE GROUP 7 CLEAR DATABASE;

3 ALTER DATABASE DROP STANDBY LOGFILE GROUP 7;

4. ALTER DATABASE ADD STANDBY LOGFILE GROUP 7; OR ALTER DATABASE ADD LOGFILE MEMBER '' HELPS GROUP 7;

5. START AGAIN APPLY: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CURRENT LOGFILE USING DISCONNECT FROM THE SESSION;

HTH

Tobi

REDO LOG STOP TRANSPORT MARITIMES TO THE BACKUP SITE

Hi guru,.
After physical creation Eve redologs are shipped and applied to standby mode. But suddenly stopped shipping redo log. I checked the main site from the log file it log archiving generates here but that is not delivered to the backup site. As I checked the pwd file is same on both sites, so I am able to connect to the db of the main site backup site.
Can any of clarify you why it happens so.
Thanks in advance

From point 1 to 3, I check that all are defined

But for pt 4 when I run the above command is as below:

STATE ERROR

------------------- ---------------------------------------------------------------------

VALID

DISABLED ORA - 16057:DGID OF THE SERVER NOT IN THE CONFIG OF DATA HOLD

OK, I got the error where is is LOG_ARCHIVE_CONFIG check box enabled on db primary

I correct and now delivery is correct, but one thing which still confuse me, is that when I run the command to check the archiev applied

SEQUENCE # FIRST_TIME NEXT_TIME APP

APP COLUMN ALWAYS SHOWS NO standby, as well as on the primary, but before it shows why Yes

ORA-00368: checksum error in redo log block

Similar Questions

Maybe you are looking for