Current log group corruption

Check out whether u can solve this issue:
This is the error which I have faced in one of my clients place. The scenario goes like this
Because of some virus problem the server was abnormally shutdown. Next time when I tried to open the database I got this error:
SQL> startup
ORACLE instance started.
Total System Global Area 202447572 bytes
Fixed Size 453332 bytes
Variable Size 117440512 bytes
Database Buffers 83886080 bytes
Redo Buffers 667648 bytes
Database mounted.
ORA-00368: checksum error in redo log block
ORA-00353: log corruption near block 6165 change 136535232 time
05/18/2006 13:03:22
ORA-00312: online log 1 thread 1: 'D:\ORACLE\ORADATA\NCRCL\REDO01.LOG'
The group happens to be the current group.
SQL> select * from v$log;
GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS
FIRST_CHANGE# FIRST_TIME
1 1 2480 104857600 1 NO CURRENT
136527225 18:MAY:06-12:11:08
2 1 2478 104857600 1 NO INACTIVE
136470398 18:MAY:06-10:10:28
3 1 2479 104857600 1 NO INACTIVE
136504477 18:MAY:06-11:48:21
The error says at SCN 136535232 there is one log corruption. So what we decided is to recover the database until change (136535225):
Sql> Recover database until change 136535226;
After giving this when we tried to open the database we got this error:
Sql> Alter database open resetlogs;
Error: File 1 needs more recovery to be consistent , can’t open the database.
Note : The client hasn’t implemented any kind of backup strategy.
Could you please solve the issue

ORA-00353: log corruption near block string change string time string
Cause: Some type of redo log corruption has been discovered. This error describes the location of the corruption. Accompanying errors describe the type of corruption.
Action: Do recovery with a good version of the log or do incomplete recovery up to the indicated change or time.
go through below link
Redolog Corrupted

Similar Messages

Current log group is corrupt

Hello freinds,
What will we do if current log group is corrupt ( archivelog and noarchivelog)?
Regards

No, there are cases when archiver couldn't archive the redo log. Then you have to use UNARCHIVED. But then you should perform a backup asap because you cannot fully recover your database.
This command isnt for the current group because you cannot clear it. These logfile group information are needed for instance recovery. If you could clear the current logfile group, after a crash your instance would be in a inconsistence state and oracle does't have enough information to make it consistence. I posted this command because I overread the word "current" in your post.
>
Total Questions: 139 (98 unresolved)
>
and please mark your posts as answered and helpful/correct...
HTH..
- wiZ

Two "current" log groups

Hello,
11.2.0.1
It might be "common" but so far I've seem no more than one log group with status "current":
select group#, status from v$log;
GROUP# STATUS
1 CURRENT
2 INACTIVE
3 CURRENT
4 INACTIVE
Should I be worried and any suggestions for fixing?
Thx,

{code select
thread#, group#, status
from
v$log; 2    3    4
   THREAD#     GROUP# STATUS
         1          1 CURRENT
         1          2 INACTIVE
         2          3 INACTIVE
         2          4 CURRENT

Redo log group always active or current

Hi,
on 11G R2 on Win 2008, I try ro drop a redolog group but it is always CURRENT or ACTIVE. I do alter system switch logfile repeatedly but it does not become inactive .
Any idea ?
Thank you.

If the group stays in the active state for a longer time, it means that the DBWR is taking more time than needed to checkpoint its contents to the data file(s) or you are switching over to the log group more quickly than it would need to make it inactive. So you can do two things, one that you check that if you have any lag in the DBWR's work or there is any slowness in the IO while writing to the disk. Second, make sure that you are not having the size of the log files and the number smaller than needed. You haven't told us about either of the things so we can't suggest anything till you share it. About being the Current, that's normal working and if you think that's a problem, have a read of the Concepts guide.
HTH
Aman....

Current redolog is corrupt

my database is in archive mode and current redolog is corrupt.How to recover and up the database .

If it is CURRENT redo logfile that is corrupted then user can not clear it.
SQL> select group#,a.SEQUENCE#,a.status from V$log a;
      GROUP# SEQUENCE# STATUS
         2         33 ACTIVE
         1         34 CURRENT
1* ALTER DATABASE CLEAR UNARCHIVED LOGFILE GROUP 1
SQL> /
ALTER DATABASE CLEAR UNARCHIVED LOGFILE GROUP 1
ERROR at line 1:
ORA-01624: log 1 needed for crash recovery of instance indorama (thread 1)
ORA-00312: online log 1 thread 1: 'D:\ORACLE\ORADATA\REDO\REDO01.LOG'Regards!

The system failed to flush data to the transaction log. Corruption may occur.

We have a windows server 2008 R2 Virtual machine and we are getting the following Warning Event.
Event 51 Volmgr
The system failed to flush data to the transaction log. Corruption may occur.
Any idea what is wrong with this server? Why this event is occurring?

Hi Jitender KT,
Before going further, would you please let me know the complete error message that you can find (such as a
screenshot if you can provide)? Please check and confirm in Event Viewer if there other related event you can find, such as Event 57 and so on. Meanwhile, can you remember what operations you have done before the warning occurred?
Based on current message that you provided, please run
Chkdsk command to check if you can find error. The issue seems to be related to the storage device. Please refer to the following similar question.
http://social.technet.microsoft.com/Forums/windowsserver/en-US/044b10af-c253-46de-b40d-ce9d128b83d7/event-id-57-source-volmgr?forum=winservergen
In addition, please also refer to the following link. It should be helpful.
http://www.eventid.net/display-eventid-57-source-volmgr-eventno-8865-phase-1.htm
Hope this helps.
Best regards,
Justin Gu

Transaction log shipping restore with standby failed: log file corrupted

Restore transaction log failed and I get this error: for only 04 no of database in same SQL server, renaming are working fine.
Date
9/10/2014 6:09:27 AM
Log
Job History (LSRestore_DATA_TPSSYS)
Step ID
1
Server
DATADR
Job Name
LSRestore_DATA_TPSSYS
Step Name
Log shipping restore log job step.
Duration
00:00:03
Sql Severity        0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted
0
Message
2014-09-10 06:09:30.37 *** Error: Could not apply log backup file '\\10.227.32.27\LsSecondery\TPSSYS\TPSSYS_20140910003724.trn' to secondary database 'TPSSYS'.(Microsoft.SqlServer.Management.LogShipping) ***
2014-09-10 06:09:30.37 *** Error: An error occurred while processing the log for database 'TPSSYS'.
If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log.
An error occurred during recovery, preventing the database 'TPSSYS' (13:0) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.
RESTORE LOG is terminating abnormally.
Processed 0 pages for database 'TPSSYS', file 'TPSSYS' on file 1.
Processed 1 pages for database 'TPSSYS', file 'TPSSYS_log' on file 1.(.Net SqlClient Data Provider) ***
2014-09-10 06:09:30.37 *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
2014-09-10 06:09:30.37 *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
2014-09-10 06:09:30.37 Skipping log backup file '\\10.227.32.27\LsSecondery\TPSSYS\TPSSYS_20140910003724.trn' for secondary database 'TPSSYS' because the file could not be verified.
2014-09-10 06:09:30.37 *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
2014-09-10 06:09:30.37 *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
2014-09-10 06:09:30.37 *** Error: An error occurred restoring the database access mode.(Microsoft.SqlServer.Management.LogShipping) ***
2014-09-10 06:09:30.37 *** Error: ExecuteScalar requires an open and available Connection. The connection's current state is closed.(System.Data) ***
2014-09-10 06:09:30.37 *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
2014-09-10 06:09:30.37 *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
2014-09-10 06:09:30.37 *** Error: An error occurred restoring the database access mode.(Microsoft.SqlServer.Management.LogShipping) ***
2014-09-10 06:09:30.37 *** Error: ExecuteScalar requires an open and available Connection. The connection's current state is closed.(System.Data) ***
2014-09-10 06:09:30.37 *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
2014-09-10 06:09:30.37 *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
2014-09-10 06:09:30.37 Deleting old log backup files. Primary Database: 'TPSSYS'
2014-09-10 06:09:30.37 *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
2014-09-10 06:09:30.37 *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
2014-09-10 06:09:30.37 The restore operation completed with errors. Secondary ID: 'dd25135a-24dd-4642-83d2-424f29e9e04c'
2014-09-10 06:09:30.37 *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
2014-09-10 06:09:30.37 *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
2014-09-10 06:09:30.37 *** Error: Could not cleanup history.(Microsoft.SqlServer.Management.LogShipping) ***
2014-09-10 06:09:30.37 *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
2014-09-10 06:09:30.38 ----- END OF TRANSACTION LOG RESTORE
Exit Status: 1 (Error)

I Have restore the database to new server and check with new log shipping but its give this same error again, If it is network issue i believe issue need to occur on every database in that server with log shipping configuration
error :
Message
2014-09-12 10:50:03.18   *** Error: Could not apply log backup file 'E:\LsSecondery\EAPDAT\EAPDAT_20140912051511.trn' to secondary database 'EAPDAT'.(Microsoft.SqlServer.Management.LogShipping) ***
2014-09-12 10:50:03.18   *** Error: An error occurred while processing the log for database 'EAPDAT'. If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log.
An error occurred during recovery, preventing the database 'EAPDAT' (8:0) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.
RESTORE LOG is terminating abnormally.
can this happened due to data base or log file corruption, if so how can i check on that to verify the issue
Its not necessary if the issue is with network it would happen every day IMO it basically happens when load on network is high and you transfer log file which is big in size.
As per message database engine was not able to restore log backup and said that you must rebuild log because it did not find out log to be consistent. From here it seems log corruption.
Is it the same log file you restored ? if that is the case since log file was corrupt it would ofcourse give error on wehatever server you restore.
Can you try creating logshipping on new server by taking fresh full and log backup and see if you get issue there as well. I would also say you to raise case with Microsoft and let them tell what is root cause to this problem
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Articles

Recover from currnet log file corruption in archive mode

Hi,
I am using oracle 10.2.0 on windows xp. my database is in archivelog mode. I am learning recovery. I take backup of database using
RMAN> backup database;
Starting backup at 03-SEP-09
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00004 name=D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\USERS01.DBF
input datafile fno=00001 name=D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSTEM01.DBF
input datafile fno=00003 name=D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSAUX01.DBF
input datafile fno=00002 name=D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\UNDOTBS01.DBF
channel ORA_DISK_1: starting piece 1 at 03-SEP-09which completed.
my current logfile and current sequence no is
SQL> select * from v$log;
    GROUP#    THREAD# SEQUENCE#      BYTES    MEMBERS ARC STATUS
FIRST_CHANGE# FIRST_TIM
         1          1         88   52428800          1 NO CURRENT
      4475270 01-SEP-09
         2          1         86   52428800          1 YES INACTIVE
      4426127 31-AUG-09
         3          1         87   52428800          1 YES INACTIVEThen i delete my only one redolog file in my current group. my instance crashes i want to recover now first i try
SQL> startup
ORACLE instance started.
Total System Global Area 289406976 bytes
Fixed Size                  1248576 bytes
Variable Size              92275392 bytes
Database Buffers          188743680 bytes
Redo Buffers                7139328 bytes
Database mounted.
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1:
'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO01.LOG'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
SQL> select open_mode from v$database;
OPEN_MODE
MOUNTED
SQL> recover database until cancel;
ORA-00279: change 4500421 generated at 09/03/2009 10:49:48 needed for thread 1
ORA-00289: suggestion : D:\1\ARC00088_0693601900.001
ORA-00280: change 4500421 for thread 1 is in sequence #88
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
cancel
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSTEM01.DBF'
ORA-01112: media recovery not startedit doesn't work then i do
RMAN> restore database
2> ;
Starting restore at 03-SEP-09
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSTEM01.DBF
restoring datafile 00002 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\UNDOTBS01.DBF
restoring datafile 00003 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSAUX01.DBF
restoring datafile 00004 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\USERS01.DBF
channel ORA_DISK_1: reading from backup piece D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2009_09_03
KP
channel ORA_DISK_1: restored backup piece 1
piece handle=D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2009_09_03\O1_MF_NNNDF_TAG20090903T104947_5
channel ORA_DISK_1: restore complete, elapsed time: 00:02:16
Finished restore at 03-SEP-09
RMAN>
RMAN> recover database until sequence 87;
Starting recover at 03-SEP-09
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 09/03/2009 11:06:06
RMAN-06556: datafile 1 must be restored from backup older than scn 4444743It means i need an older backup but i have new backup how to restore or get my database up.
Thanks
umesh

Thanks for reply
i have this in my hand
RMAN> list backupset;
List of Backup Sets
===================
BS Key Type LV Size       Device Type Elapsed Time Completion Time
1       Full    1.38G      DISK        00:02:21     03-SEP-09
        BP Key: 1   Status: AVAILABLE Compressed: NO Tag: TAG20090903T104947
        Piece Name: D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2009_09_03\O1_MF_NNNDF_TAG20090903T104947_59YNHNSK_.BKP
List of Datafiles in backup set 1
File LV Type Ckp SCN    Ckp Time Name
1       Full 4500421    03-SEP-09 D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSTEM01.DBF
2       Full 4500421    03-SEP-09 D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\UNDOTBS01.DBF
3       Full 4500421    03-SEP-09 D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSAUX01.DBF
4       Full 4500421    03-SEP-09 D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\USERS01.DBF
BS Key Type LV Size       Device Type Elapsed Time Completion Time
2       Full    6.80M      DISK        00:00:03     03-SEP-09
        BP Key: 2   Status: AVAILABLE Compressed: NO Tag: TAG20090903T104947
        Piece Name: D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2009_09_03\O1_MF_NCSNF_TAG20090903T104947_59YNN8J9_.BKP
Control File Included: Ckp SCN: 4500486      Ckp time: 03-SEP-09
SPFILE Included: Modification time: 03-SEP-09
RMAN> restore database preview;
Starting restore at 03-SEP-09
using channel ORA_DISK_1
List of Backup Sets
===================
BS Key Type LV Size       Device Type Elapsed Time Completion Time
1       Full    1.38G      DISK        00:02:21     03-SEP-09
        BP Key: 1   Status: AVAILABLE Compressed: NO Tag: TAG20090903T104947
        Piece Name: D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2009_09_03\O1_MF_NNNDF_TAG20090903T104947_59YNHNSK_.BKP
List of Datafiles in backup set 1
File LV Type Ckp SCN    Ckp Time Name
1       Full 4500421    03-SEP-09 D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSTEM01.DBF
2       Full 4500421    03-SEP-09 D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\UNDOTBS01.DBF
3       Full 4500421    03-SEP-09 D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSAUX01.DBF
4       Full 4500421    03-SEP-09 D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\USERS01.DBF
archive logs generated after SCN 4500421 not found in repository
Media recovery start SCN is 4500421
Recovery must be done beyond SCN 4500421 to clear data files fuzziness
Finished restore at 03-SEP-09
RMAN> backup archivelog all ;
Starting backup at 03-SEP-09
using channel ORA_DISK_1
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=60 recid=3 stamp=694522772
input archive log thread=1 sequence=61 recid=4 stamp=694543115
input archive log thread=1 sequence=62 recid=5 stamp=694693173
input archive log thread=1 sequence=63 recid=6 stamp=694707783
input archive log thread=1 sequence=64 recid=7 stamp=694785054
input archive log thread=1 sequence=65 recid=8 stamp=694787797
input archive log thread=1 sequence=66 recid=9 stamp=694794198
input archive log thread=1 sequence=67 recid=10 stamp=694799765
input archive log thread=1 sequence=68 recid=11 stamp=694806827
input archive log thread=1 sequence=69 recid=12 stamp=694809124
input archive log thread=1 sequence=70 recid=13 stamp=694868744
input archive log thread=1 sequence=71 recid=14 stamp=695132728
input archive log thread=1 sequence=72 recid=15 stamp=695210729
input archive log thread=1 sequence=73 recid=16 stamp=695330401
input archive log thread=1 sequence=74 recid=17 stamp=695399695
input archive log thread=1 sequence=75 recid=18 stamp=695412690
input archive log thread=1 sequence=76 recid=19 stamp=695511043
input archive log thread=1 sequence=77 recid=20 stamp=695557945
input archive log thread=1 sequence=78 recid=21 stamp=695597432
input archive log thread=1 sequence=79 recid=22 stamp=695728451
input archive log thread=1 sequence=80 recid=23 stamp=695729334
input archive log thread=1 sequence=81 recid=24 stamp=695729976
input archive log thread=1 sequence=82 recid=25 stamp=695835471
input archive log thread=1 sequence=83 recid=26 stamp=695988878
input archive log thread=1 sequence=84 recid=27 stamp=696160938
input archive log thread=1 sequence=85 recid=28 stamp=696333853
input archive log thread=1 sequence=86 recid=29 stamp=696360658
input archive log thread=1 sequence=87 recid=30 stamp=696454218
channel ORA_DISK_1: starting piece 1 at 03-SEP-09
channel ORA_DISK_1: finished piece 1 at 03-SEP-09
piece handle=D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2009_09_03\O1_MF_ANNNN_TAG20090903T115246_59YR5VRV_.BKP tag=TAG20090903T1
=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:01:08
Finished backup at 03-SEP-09
RMAN> restore database preview;
Starting restore at 03-SEP-09
using channel ORA_DISK_1
List of Backup Sets
===================
BS Key Type LV Size       Device Type Elapsed Time Completion Time
1       Full    1.38G      DISK        00:02:21     03-SEP-09
        BP Key: 1   Status: AVAILABLE Compressed: NO Tag: TAG20090903T104947
        Piece Name: D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2009_09_03\O1_MF_NNNDF_TAG20090903T104947_59YNHNSK_.BKP
List of Datafiles in backup set 1
File LV Type Ckp SCN    Ckp Time Name
1       Full 4500421    03-SEP-09 D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSTEM01.DBF
2       Full 4500421    03-SEP-09 D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\UNDOTBS01.DBF
3       Full 4500421    03-SEP-09 D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSAUX01.DBF
4       Full 4500421    03-SEP-09 D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\USERS01.DBF
archive logs generated after SCN 4500421 not found in repository
Media recovery start SCN is 4500421
Recovery must be done beyond SCN 4500421 to clear data files fuzziness
Finished restore at 03-SEP-09now i have two backup one is full database backup which will not work another is backup of all archivelog upto sequence 87 i think it should work.
but rman is choosing full database backup for restore.
so i need to force rman to choose archivelog backups for restore but don't know how to do it. please suggest.
Thanks
umesh

How to get the name of currently logged in user in the network

Hi all,
I want to know if there's a way to get the name of the currently logged in user in the network.
SYS_CONTEXT('USERENV','OS_USER') won't work for me because our users do not loggin in portal.
Any ideas?
Thanks in advance.
Brett

Hello, I had the same problem. Here is a smaller version to find the Group of the current User.
The VI get the members of a Group and match it with the Username.
Note :
If the User belongs to multiple Groups the the VI returns only the 1st Groupname
If the User belongs to no Group then the VI returns "unknown Group"
The VI is written with LabVIEW 2010 and TestStand 4.2.1
Attachments:
current user group.vi ‏20 KB
TestStand get Group of current User.PNG ‏43 KB

Log file corrupt and can't open the database.

I use Replication Manager to manage my Replication; and there is only one site currently in my application.
I killed the App process with signal -9. (ie. $ kill -9 appID).
Then I try to restart the App, but the event_callback function got a PANIC event when to open the envirment.
The open flag is:
flags = DB_CREATE | DB_INIT_LOCK | DB_INIT_LOG | DB_INIT_MPOOL |
DB_INIT_REP | DB_INIT_TXN | DB_RECOVER | DB_THREAD;
ret = dbenv->open(dbenv, path, flags | DB_SYSTEM_MEM, 0);
What's the reason cause this problem?
How can recover it ?
The logs list as below:
[D 11/19 09:44] dbpf using shm key: 977431433
[E 11/19 09:44] [src/io/dbpf-mgmt.c, 400]
[E 11/19 09:44] yuga: DB_LOGC->get: LSN 1/9776: invalid log record header
[E 11/19 09:44] yuga: Log file corrupt at LSN: [1][9906]
[E 11/19 09:44] yuga: PANIC: Invalid argument
[E 11/19 09:44] [src/io/dbpf-mgmt.c] Rep EventGot a panic: Invalid argument (22)
Edited by: dbnicker on Nov 18, 2010 6:08 PM

First, what version of Berkeley DB are you running and on what system?
The error indicates something amiss in the log. The LSN values are quite
small. Can you run 'db_printlog -N -h <env path>' and post the log
contents?
If you are using BDB 5.0 or later, can you also post the contents of
the __db.rep.diag00 file in the environment home directory? Thanks.
Sue LoVerso
Oracle

Confused about standby redo log groups

hi masters,
i am little bit confuse about creating redo log group for standby database,as per document number of standby redo group depends on following equation.
(maximum number of logfiles for each thread + 1) * maximum number of threads
but i dont know where to fing threads? actually i would like to know about thread in deep.
how to find current thread?
thanks and regards
VD

is it really possible that we can install standby and primary on same host??
yes its possible and i have done it many times within the same machine.
For yours confusion about spfile ,i agree document recommend you to use spfile which is for DG broker handling if you go with DG borker in future only.
There is no concern spfile using is an integral step for primary and standby database implementation you can go with pfile but good is use spfile.Anyhow you always keep pfile on that basis you created spfile,i said you make an entry within pfile then mount yours standby database with this pfile or you can create spfile from this pfile after adding these parameter within pfile,i said cause you might be adding this parmeter from SQL prompt.
1. logs are not getting transfered(even i configure listener using net manager)
2.logs are not getting archived at standby diectory.
3.'ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION' NEVER COMPLETE ITS RECOVERY
4. when tried to open database it always note it 'always' said system datafile is not from sufficiently old backup.
5.i tried 'alter database recover managed standby database camncel' also.Read yours alert log file and paste the latest log here..
Khurram

Standby redo log group for particular thread

hi masters,
actually i am performing an experiment to create physical standbyt database on the same machine as my primary database.
i ma going according to 'data guard admin guide'. while section for ading standby redo log group,it says that you have to add standby redo log group to "thread"....
what is this thread? and how can i foind to which thread i have to assign the next redo log group??
how can i find current thread??
what if i dont add "to thread' clause in my statement:-
ALTER DATABASE ADD STANDBY LOGFILE THREAD 5
2> ('/oracle/dbs/log1c.rdo','/oracle/dbs/log2c.rdo') SIZE 500M;
thanks and regards
VD

Vikrant,
First a question: Do you have a RAC instance? If so the paragraph even doesn't apply to you and I'm not sure why you are questioning it.
Secondly
"The THREAD clause is required only if you want to add one or more standby redo log
file groups to a specific primary database thread. If you do not include the THREAD
clause and the configuration uses Real Application Clusters (RAC), Data Guard will
automatically assign standby redo log file groups to threads at runtime as they are
needed by the various RAC instances."
this means you dont have to specify thread for RAC,as it will allocate one according to current thread.
Your conclusion is incorrect.
Where do you read the word 'current'?
Oracle will likely simply make sure each instance has sufficient standby redolog groups, the requirement is 1 standby redolog group per group + 1 extra.
Sybrand Bakker
Senior Oracle DBA

After increasing redo log groups we are getting given alerts continvously

earlier having 6 redo log groups with 32 MB.but 7 days back our database was hangs .no one was able to login into sqlplus except sys user ,but not able to perform any dml operation.after rebooting our 2-node RAC instances it was running fine nearly about 6-7 hrs and again hangs.we did 4-5 times and same thing happend again and again.so we had added more redo logs of 100 MB size and removed previous one.then our hangs problem resolved but continvously getting given things in alert logs for both RAC instances(9.2.0.8).our os is linux
{color:#ff0000}Wed Dec 3 05:04:31 2008
ARC1: Completed archiving log 15 thread 1 sequence 282036
ARC1: Evaluating archive log 17 thread 1 sequence 282037
ARC1: Unable to archive log 17 thread 1 sequence 282037
Log actively being archived by another process
ARC1: Evaluating archive log 13 thread 1 sequence 282038
ARC1: Beginning to archive log 13 thread 1 sequence 282038
Creating archive destination LOG_ARCHIVE_DEST_2: 'SBMEMS'
Creating archive destination LOG_ARCHIVE_DEST_1: '/MemsArchive/0001_0000282038.arc'
Wed Dec 3 05:04:31 2008
Thread 1 advanced to log sequence 282040
Current log# 15 seq# 282040 mem# 0: /MemsRedoA/redo15_1.log
Current log# 15 seq# 282040 mem# 1: /MemsRedoB/redo15_2.log
Wed Dec 3 05:05:21 2008
ARC1: Completed archiving log 13 thread 1 sequence 282038
ARC1: Evaluating archive log 17 thread 1 sequence 282037
{color}{color:#ff0000}*ARC1: Unable to archive log 17 thread 1 sequence 282037*
Log actively being archived by another process
ARC1: Evaluating archive log 18 thread 1 sequence 282039
ARC1: Beginning to archive log 18 thread 1 sequence 282039
Creating archive destination LOG_ARCHIVE_DEST_2: 'SBMEMS'
Creating archive destination LOG_ARCHIVE_DEST_1: '/MemsArchive/0001_0000282039.arc'
Wed Dec 3 05:05:21 2008
ARC0: Completed archiving log 17 thread 1 sequence 282037
ARC0: Evaluating archive log 18 thread 1 sequence 282039
ARC0: Unable to archive log 18 thread 1 sequence 282039
Log actively being archived by another process
ARC0: Evaluating archive log 18 thread 1 sequence 282039
{color}{color:#ff0000}*ARC0: Unable to archive log 18 thread 1 sequence 282039*
Log actively being archived by another process
ARC0: Evaluating archive log 18 thread 1 sequence 282039
{color}{color:#ff0000}*ARC0: Unable to archive log 18 thread 1 sequence 282039*
Log actively being archived by another process
ARC0: Evaluating archive log 18 thread 1 sequence 282039
ARC0: Unable to archive log 18 thread 1 sequence 282039
Log actively being archived by another process
ARC0: Evaluating archive log 18 thread 1 sequence 282039
ARC0: Unable to archive log 18 thread 1 sequence 282039
Log actively being archived by another process
ARC0: Evaluating archive log 18 thread 1 sequence 282039
ARC0: Unable to archive log 18 thread 1 sequence 282039
Log actively being archived by another process
Wed Dec 3 05:05:49 2008
ARC1: Completed archiving log 18 thread 1 sequence 282039
Wed Dec 3 09:01:02 2008
Thread 1 advanced to log sequence 282041
Current log# 17 seq# 282041 mem# 0: /MemsRedoA/redo17_1.log
Current log# 17 seq# 282041 mem# 1: /MemsRedoB/redo17_2.log
Wed Dec 3 09:01:02 2008
ARC1: Evaluating archive log 15 thread 1 sequence 282040
ARC1: Beginning to archive log 15 thread 1 sequence 282040
Creating archive destination LOG_ARCHIVE_DEST_2: 'SBMEMS'
Creating archive destination LOG_ARCHIVE_DEST_1: '/MemsArchive/0001_0000282040.arc'
Wed Dec 3 09:01:29 2008
ARC0: Evaluating archive log 15 thread 1 sequence 282040
{color}{color:#ff0000}*ARC0: Unable to archive log 15 thread 1 sequence 282040*
Log actively being archived by another process
Wed Dec 3 09:01:37 2008
ARC1: Completed archiving log 15 thread 1 sequence 282040
{color}ORADB1:MEMS1:oracle$
please suggest solution for this.
Thanks

As Sybrand pointed out, this msg can be ignored. It clearly states that a given arch process cannot archive a given redo because that redo is already being handled by a different arch process. If you follow your alert log a little further, you'll see that the referenced thread is eventually completed.
I'd be curious to see the alert log from when you were locked up and only sysdba could log on. See what led you to believe that adding more redo log groups would solve your problem.

GPUpdate /force in Task Sequence as current logged on user

Hi,
I am currently trying to "upgrade" around 800 installations of Microsoft Office Standard 2010 to Microsoft Office 2010 Professional Plus. To do this, I'll have to:
1: Install Office 2010 ProPlus
2: Uninstall Office 2010 Standard
3: Repair Office 2010 ProPlus
Due to these steps, I've decided to make a task sequence to do the magic.
So far, so good, the "upgrade" is installing, and the MAP toolkit reports are showing the correct results from my test lab.
During the repair of Office 2010 ProPlus, the Office applications cannot
run, so I've created a task to copy a custom group policy to %systemroot%\System32\GroupPolicy to deny the affected users to start the applications.
After applying the group policies, I manually run a gpupdate /force on my test computer. The applications are not starting. Also - so far so good.
Ok, so here is my challenge:
Since the Task Sequence is running in context of the SYSTEM account, the applied group policy will not refresh the GPO's of the current logged on user. Meaning; during the installation / repair of Office 2010, the user can open all the applications regardless
of the applied GPO's, and I'd very much like to avoid that. The TS will fail otherwise. Yes, I know I can perform a restart to apply the policies, but I'd like to avoid that as well.
Any idea how can I solve this?

I think you're making it very complex for yourself. I think that the PowerShell App Deployment Toolkit would be very benificial for a situation like this. For more information have a look here:
https://psappdeploytoolkit.codeplex.com/
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

All redo log groups is active

Hello dear gurus!
After shutting database with option "abort"
we have unconsisten state of datafiles.
I ask to explain :
1) - does the ARCH background processes flash whole redo buffer into redolog ?
(In other words how reached consistency if all redo log groups was in active state before shutting down ?)
2) Where buffer contents in this case are dumped ?
Thanks and best regards,
Pavel
Edited by: Pavel on Jul 19, 2012 9:49 PM

Pavel wrote:
Hello dear gurus!
After shutting database with option "abort"
we have unconsisten state of datafiles.That's expected as checkpoint didn't happen. Issue a startup and instance recovery should take care of everything.
I ask to explain :
1) - does the ARCH background processes flash whole redo buffer into redolog ?ARCH process or LGWR? How does this relates to your current question?
(In other words how reached consistency if all redo log groups was in active state before shutting down ?)As I said, issue a startup of the instance and it should take care of the things.
2) Where buffer contents in this case are dumped ?Which case? Your questions are a bit fuzzy you see. Let's stick to one question at one time and follow it shall we?
Aman....

Current log group corruption

Similar Messages

Maybe you are looking for