When occurs crash recovery,why use active online redo log not archived log?
If current redo log had archived, but it's still 'ACTIVE'. As we all know, archived log is just an archived copy of the current redo log which is still 'ACTIVE', they have the same data. But why use active online redo log not archived log for crash recovery?(I think, if crash recovery can use archived log, then whether the online redo log is 'ACTIVE' or not, it can be overwritten)
Quote:
Re: v$log : How redo log file can have a status ACTIVE and be already archived?
Hemant K Chitale
If your instance crashes, Oracle attempts Instance Recovery -- reading from the Online Redo Logs. It doesn't need ArchiveLogs for Instance Recovery.
TanelPoder
Whether the log is already archived or not doesn't matter here, when the instance crashes, Oracle needs some blocks from that redolog. Archivelog is just an archived copy of the redolog, so you could use either the online or achive log for the recovery, it's the same data in there (Oracle reads the log/archivelog file header when it tries to use it for recovery and validates whether it contains the changes (RBA range) in it what it needs).
Aman.... wrote:
John,
Are you sure that the instance recovery (not the media recovery) would be using the archived redo logs? Since the only thing that would be lost is the isntance, there wouldn't be any archived redo log generated from the Current redo log and the previous archived redo logs, would be already checkpointed to the data file, IMHO archived redo logs won't participate in the instance recovery process. Yep, shall watch the video but tomorrow .
Regards
Aman....
That's what I said. Or meant to say. If Oracle used archivelogs for instance recovery, it would not be possible to recover in noarchive log mode. So recovery relies exclusively on the online log.
Sorry I wasted your time, I'll try to be less ambiguous in future
Similar Messages
-
Open database if an active online redo log is missing
Hi,
Sorry for the rather long post, but I specified all the steps I performed and couldn't make it shorter :-(
I need an advice on how to open the database if an active online redo log is missing.
For test purposes I intentionally performed a shutdown abort when the redo log group 1 was in active state and then renamed its only member (REDO01.LOG) so that the database couldn't perform crash recovery using it. Then upon startup I obviously got the message:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: 'H:\ORADATA\TESTDB\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.Ok, so I checked the state of the logs:
{noformat}
SQL>SELECT a.GROUP#, first_change#, SEQUENCE#, a.status, SUBSTR(b.MEMBER, 1, 40) MEMBER, b.status mem_status, a.archived
2 FROM v$log a, v$logfile b
3 WHERE a.GROUP# = b.GROUP#
4 ORDER BY a.GROUP#, b.MEMBER;
GROUP# FIRST_CHANGE# SEQUENCE# STATUS MEMBER MEM_STA ARC
1 592134 29 ACTIVE H:\ORADATA\TESTDB\REDO01.LOG YES
2 592268 30 CURRENT C:\ORADATA\TESTDB\REDO02.LOG NO
3 592129 28 ACTIVE C:\ORADATA\TESTDB\REDO03.LOG YES
{noformat}Since opening the database to perform a log switch and thus change the status of the redo log group 1 from ACTIVE to INACTIVE to recreate the member isn't possible, I performed database recovery.
SQL>recover database until cancel;
ORA-00279: change 592129 generated at 02/04/2009 10:31:15 needed for thread 1
ORA-00289: suggestion : C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\TESTDB\ARCHIVELOG\2009_02_04\O1_MF_1_28_%U_.ARC
ORA-00280: change 592129 for thread 1 is in sequence #28
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 592134 generated at 02/04/2009 10:31:28 needed for thread 1
ORA-00289: suggestion : C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\TESTDB\ARCHIVELOG\2009_02_04\O1_MF_1_29_%U_.ARC
ORA-00280: change 592134 for thread 1 is in sequence #29
ORA-00278: log file 'C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\TESTDB\ARCHIVELOG\2009_02_04\O1_MF_1_28_4RLR3JS9_.ARC' no longer needed for this rec
overy
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
'C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\TESTDB\ARCHIVELOG\2009_02_04\O1_MF_1_29_4RLR4MF3_.ARC'
ORA-00279: change 592268 generated at 02/04/2009 10:32:03 needed for thread 1
ORA-00289: suggestion : C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\TESTDB\ARCHIVELOG\2009_02_04\O1_MF_1_30_%U_.ARC
ORA-00280: change 592268 for thread 1 is in sequence #30
ORA-00278: log file 'C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\TESTDB\ARCHIVELOG\2009_02_04\O1_MF_1_29_4RLR4MF3_.ARC' no longer needed for this rec
overy
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
'C:\ORADATA\TESTDB\REDO02.LOG'
Log applied.
Media recovery complete.
SQL>So for log sequence #28 I accepted the proposed archived redo log in the FRA, for sequence #29 (that's the online redo log that is missing!) I manually specified its archived copy, and for sequence #30 I specified the CURRENT online redo log. And as it seems the media recovery was successful.
Next I tried to open the database but again got the error:
SQL>alter database open noresetlogs;
alter database open noresetlogs
ERROR at line 1:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: 'H:\ORADATA\TESTDB\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.
The status of the log groups and its members is exactly as it was in the first query I wrote above, i.e. the redo log group 1 is still ACTIVE, so it's needed for crash recovery (which I had already done manually if I understand correctly how Oracle works!). I also checked if the datafiles are inconsistent (described in metalink doc id 1015544.102):
SQL>SELECT DISTINCT CHECKPOINT_CHANGE#, FUZZY FROM V$DATAFILE_HEADER;
CHECKPOINT_CHANGE# FUZ
592269 NOSo, everything seems ok as far as datafile consistency is concerned.
My question is: how can I rename/drop/clear/whatever the member of redo log group 1 to open the database?
I tried to rename the log file member, to add another member to it, to open the database with resetlogs, to clear the logfile group 1, but all without success:
1)
SQL>alter database clear logfile group 1;
alter database clear logfile group 1
ERROR at line 1:
ORA-01624: log 1 needed for crash recovery of instance testdb (thread 1)
ORA-00312: online log 1 thread 1: 'H:\ORADATA\TESTDB\REDO01.LOG'
2)
SQL>alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01139: RESETLOGS option only valid after an incomplete database recovery
3)
SQL>alter database rename file 'H:\ORADATA\TESTDB\REDO01.LOG' to 'C:\ORADATA\TESTDB\REDO01.LOG';
alter database rename file 'H:\ORADATA\TESTDB\REDO01.LOG' to 'C:\ORADATA\TESTDB\REDO01.LOG'
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01512: error renaming log file H:\ORADATA\TESTDB\REDO01.LOG - new file C:\ORADATA\TESTDB\REDO01.LOG not found
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
4)
SQL>alter database add logfile member 'C:\ORADATA\TESTDB\REDO01.LOG' to group 1;
alter database add logfile member 'C:\ORADATA\TESTDB\REDO01.LOG' to group 1
ERROR at line 1:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: 'H:\ORADATA\TESTDB\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.Sorry again for the long post and thank you in advance for any suggestion.
Regards,
JureYou could check if the recovery was complete by (re)creating the controlfile with the resetlogs option.
<CREATE CONTROLFILE REUSE DATABASE define_db_name RESETLOGS NOARCHIVELOG
...>Thanks for the hint. If possible, could you only check if the steps I'm going to perform are ok.
I did an "alter database backup controlfile to trace;" and then extracted the create controlfile definition part. So in essence I should run the following statements:
CREATE CONTROLFILE REUSE DATABASE "TESTDB" RESETLOGS ARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 292
LOGFILE
GROUP 1 'C:\ORADATA\TESTDB\REDO01.LOG' SIZE 20M,
GROUP 2 'C:\ORADATA\TESTDB\REDO02.LOG' SIZE 20M,
GROUP 3 'C:\ORADATA\TESTDB\REDO03.LOG' SIZE 20M
-- STANDBY LOGFILE
DATAFILE
'C:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\SYSTEM01.DBF',
'C:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\UNDOTBS01.DBF',
'C:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\SYSAUX01.DBF',
'C:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\USERS01.DBF'
CHARACTER SET EE8MSWIN1250
ALTER DATABASE OPEN RESETLOGS;
ALTER TABLESPACE TEMP ADD TEMPFILE 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\TEMP01.DBF' REUSE;Is that correct?
About the RMAN backups: Wouldn't a 'CATALOG RECOVERY AREA' populate the controlfile with backup information again (I'm not using a recovery catalog in this case)?
Thanks for the help!
Regards,
Jure -
Asynch Hot Log mode does not use hot (online) redo logs
Version 10.2
We have just set up a test of the Asynch Hot Log replication according to Chap 16 of the Data Warehousing guide.
We can see data put into the change table. However, it seems that data gets written to the change table ONLY after a log switch. This would suggest that the capture process is not reading the online logs, but is only reading the archived logs.
I don't think this can be correct behavior because the docs indicate that Oracle "seamlessly switches" between the online and the archived redo logs.
Is there a flag or something to set to cause the online logs to be available to the capture process? Or is this a bug? Has anyone else observed this behavior?
Thanks for any insight.
-- Chris CurzonAccording to the 10g Dataguard docs, section 2.5.1:
"Physical standby databases do not use an online redo log, because physical standby databases are not opened for read/write I/O."yes, those are used when database is open.
You should not perform any changes in Standby. Even if those exist online redo log files, whats the difficulty you have seen?
These will be used whenever you performed switchover/failover. So nothing to worry on this.
Is this a case of the STANDBY needing at least a notion of where the REDO logs will need to be should a failover occur, and if the files are already there, the standby database CONTROLFILE will hold onto them, as they are not doing any harm anyway?Then oracle functionality itself harm if you think in that way. When they not used in open then what the harm with that?
Standby_File_management --> for example if you add any datafile, those information will be in archives/redos once they applied on standby those will be added automatically when it is set to AUTO if its manual, then it creates a unnamed file in $ORACLE_HOME/dbs location later you have to rename that file and recovery need to perform .
check this http://docs.oracle.com/cd/B14117_01/server.101/b10755/initparams206.htm
HTH. -
Archive all the active online redo logs
Hi,
in 9.2.0 and in archivelog mode, how can I archive all the active online redo logs ?
Thank you.Is ur database already running in archivelog mode?? If yes and if automatic archiving is enabled then ur redo will be archived automatically. I think first you need to check whether ur DB is in archive log mode or not?? Post the output of (from sqlplus):
archive log list
Daljit Singh -
Error -2146960888 when opening excel from labview using active x
attempting to open an instance of excel from labview using active x, I even tried using the "open excel and make visible.vi" found on this site. I get errors every time, Inserting a break right after the property node, I found that it does open excel with no active workbook. once the program runs to ompletion excel terminates. The error is on the line right after the property node executes.
http://sine.ni.com/apps/we/niepd_web_display.DISPLAY_EPD4?p_guid=B45EACE3F15456A4E034080020E74861&p_node=DZ53003&p_submitted=N&p_rank=&p_answer=&p_source=External
Attachments:
XL97table.zip 29 KB -
TS4083 When I send an email using iCloud Mail, it does not appear in the send box.
When I send an email using iCloud Mail, it does't appear in the send box. Not in icloud, nor on any other devices. Any idea why not?
not all mail providers sync the send mail part of the mail box
you can try to contact yahoo if this is the case with them -
Oracle Restore from Online backup without any archive logs
Hi,
May be a dumb question. If I have a good online backup (say it took 2 hours to do that. And there is database activity while backup is going on), and lost all the archive logs happened after the online backup, is it possible at all to do the restore using that backup? complete or incomplete? and bring back the database to normal operation mode? Some details on this.
Thanks.Let us see the reasoning behind this.
Database:WORLDDB
WORLDDB configuration:-
TBSP_WDB
->TBSP_WDB_01.dbf
->TBSP_WDB_02.dbf
SYSTEM
->SYSTEM.dbf
USERS
and so on for the tablespaces.
CASE 1:-
User managed backup.
You issue
ALTER TABLESPACE TBSP_WDB BEGIN BACKUP;
DB keeps working all transactions are recorded in the redo stream, the scn information is not updated in the file header.
Also note that the other tablespaces were been continuously worked on hence their scn numbers are a moving target.
http://download-east.oracle.com/docs/cd/B10501_01/server.920/a96572/osbackups.htm#10012
So if you begin tablespace TBSP_WDB backup at time t1 and by the time you are done with your backups you are at time t2, you will need all of the archive log's between time t1 and t2.
CASE 2:-
If we do with rman, rman takes care of the file header update information and goes on its merry way, those details are hidden from the end user. If one of the tablespace is fractured, updated while backups are going on , rman knows about it and will re-read the affected blocks in question.
My thinking would be that you might need archive logs, unless it is a cold backup, with switch logfiles in between.
If you do hot backups you need archivelogs is my thought. The number of archivelogs required will be decreased considerably through rman.
http://download-east.oracle.com/docs/cd/B10501_01/server.920/a96566/rcmconc1.htm#458821
Summary:-
Either way archivelogs are needed. -
Using 2 file systems to place archive logs
We currently have LOG_ARCHIVE_DEST parameter set to place archive logs to /u10 file system. However it no longer has enough space and system admin added second dedicated file system /u11 to place archive logs. So we would like to start using both of them. If first gets full we want to make sure second is in use until backup job deletes them. If this possible to do in current version that we have (8.1.7) and what changes should we make to start utilizing both file systems.
Thanks.
Edited by: user594143 on Sep 8, 2008 3:47 PMI am not sure whether this was introduced from 8i but 9i & 10g both versions have this feature.
You can use the ALTERNATE feature of log_archive_dest_n to set an alternate destination if the primary destination fails. In the sense, if the primary (mandatory) archive log destination fails because of either full or any other reason, the database starts archiving to the ALTERNATE destination. After you clear the primary destination, you have to manually switch the destinations to PRIMARY and ALTERNATE.
SQL> alter system set log_archive_dest_1='LOCATION=/u00/app/oracle/admin/archive_1 MANDATORY NOREOPEN ALTERNATE=log_archive_dest_2';
SQL> alter system set log_archive_dest_2='LOCATION=/u01/app/oracle/admin/archive_2 OPTIONAL';
SQL> alter system set log_archive_dest_state_1=enable;
SQL> alter system set log_archive_dest_state_2=alternate;
Thanks,
Harris. -
Any 3rd party Database Activity Monitoring products that read Archive Logs?
I've been doing lots of research to find auditing-related 3rd party software products that read Oracle's archive log files. Many products are available for 'log' monitoring for security etc., but so far I've not found any that read the actual archive log files themselves. LogMiner is useful, but need to know if other products exist.
Any info is appreciated! Thanks.....Thanks for your reply, Satish
-
Why my activated CTS BADI is not working ?
Hello,
I'm using the BADi CTS_EXPORT_FEEDBACK. To do this, I used the transaction SE19, created a new implementation, add my own code and activated implementation, class and method.
The problem is that when I export an order, the code I've written is not run.
My BADI is activated and I noticed that in the transport protocol new lines appears :
DEV Developpement
Checks at Operating System Level 03.09.2010 16:39:00 (0) Successfully Completed
Pre-Export Methods 03.09.2010 16:39:06 (0) Successfully Completed
Export 03.09.2010 16:39:12 (0) Successfully Completed
Import steps not specific to transport request
Feedback after export or import 03.09.2010 16:39:13 (0) Successfully Completed
INFORM SAP-SYSTEM OF TP TERMINATION
Transport request : ALL
Start: Executing method FEEDBACK_AFTER_EXPORT for business add-on CTS_EXPORT_FEEDBACK
End: Executing method FEEDBACK_AFTER_EXPORT for business add-on CTS_EXPORT_FEEDBACK
INFORM SAP-SYSTEM OF TP TERMINATION
End date and time : 20100903163913
Ended with return code: ===> 0 <===
I tried in my code to write in DB for example but no lines are added. My code works fine when I'me testing the BADI.
So it's very strange, everything seems to be activated and running but nothings done.
Another info, the BADI is launched from the program RDDFDBCK (l.348) and when I test this part of the code (call function...) everythings working fine...
Any idea ?
Thanks in advance.
SimonOk, I solved the problem Myself.
If anybody has the same problem.. here is the solution.
The job RDDFDBCK is running in backgroung. I ran a DEBUG thanks to the tip in this page : [SDN|http://wihttp//wiki.sdn.sap.com/wiki/display/ABAP/ABAP%20Debugger#ABAPDebugger-HowdoIdebugrunningbackgroundprocessesorasynchronousprocesses%3F]
I created a block While l_int = 0. Endwhile. In my BADI implementation in order to make the job duration long enough to enter in debug with SM50.
Here I saw that my SELECT didn't returning lines.
Finally, I found in SM37 that the main job was launched with the mandant 000 => and my tables contained a field MDNT.
So the BADI was launched but nothing was done cause to the mandant. I just removed the field MDNT of my customs tables to solve the problem.
Simon -
we have a server and all of use the server's url to work on it. when i log out from the application, the session with the server doesnt end.
mailto : [email protected]If the old ID is yours, and if your current ID was created by editing the details of this old ID (rather than being an entirely new ID), go to https://appleid.apple.com, click Manage my Apple ID and sign in with your current iCloud ID. Click edit next to the primary email account, change it back to your old email address and save the change. Then edit the name of the account to change it back to your old email address. You can now use your current password to turn off Find My iDevice, even though it prompts you for the password for your old account ID. Then save any photo stream photos that you wish to keep to your camera roll. When finished go to Settings>iCloud, tap Delete Account and choose Delete from My iDevice when prompted (your iCloud data will still be in iCloud). Next, go back to https://appleid.apple.com and change your primary email address and iCloud ID name back to the way it was. Now you can go to Settings>iCloud and sign in with your current iCloud ID and password.
-
Archive Records using object MM_SPSTOCK, MSKA records not archived.
Hello ,
I am trying to Archive some material using object MM_SPSTOCK, i used Tcode MM74, I have just checked only "other special stock " option and executed. its giving me below error messages :
MSKA: 18345 EN30 EN31 E V57292 000100 unrestricted-use stock exists for previous period
MSSA: 18345 EN30 E V57292 000100 dependent sales order stock records exist
I have checked the stock, its cleared. In table MSKA, i can see one records with 0 stock.
I have also checked the stock using MMBE, but no stock found.
Can you guide me why above errors are coming, because of this i am not able to archive my sales order.
Regards,
Sujeet MishraFM MSKA_EXTEND is used to check previous period stock.
the message and I told you already that you have stock in a previous period.
And I told you to read OSS 30656 as this note explains how to remove stock in a previous period.
further I told you that it does not make sense to archive something what is still in use, which is the case for a special stock if it has stock in the previous period.
There is no legal work around.
Please open a message at SAP Support and have them confirm what was said, or raise a developement request directly -
Are archived logs useful for crashed instance?
when the machine powers off,and start it again,the database will experience instance recover,will this kind of recover use archived log£¿I see if the database worked under unarchive mod before,then instance recover will not use archived log(no archived log).
surpose that oracle makes a commit,and the commited
data are already written into log file,but are not
written back to datafile,and if the log file is
archived,at this time OS crash.when oracle startup again
it will user the online redo,and some of the latest
archvied log to recover the committed data.and if the
archvied log accidentally lost,how can oracle recovery.
Or oracle will not reuse the online redo log until
its data are written back to the datafile under archived
log mod? -
Crash recovery: recreating invalid indexes
I want to discuss a phaenomen, which we often have saw during crash recoveries:
The "startsap db" is hanging, because after the crash recocvery itself is completed (according to db2diag.log), the connection to the database ist still hanging because the database recreate invalid indexes.
sf503:db2p02 10% db2 list utilities
ID = 2
Type = RESTART RECREATE INDEX
Database Name = P02
Partition Number = 0
Description = Recreating Invalid Index Objects
Start Time = 05/08/2007 09:37:42.721072
Sometimes this can take up to 25 minutes until this is finished and the connect is finished.
The strange thing is:
If a 2. connection to the database is made during "recreating indexes", this 2. connection is successfull and selects from t000 are successfull.
So, it is possible to execute "startsap r3" while the first connection is still blocked with recreating indexes.
I don't understand this behaviour:
- If the database really needs the recreation of invalid index objects for sucessfull database operation, then it should block ALL connections and not only the first one.
- If it's not urgently necessary, the database should done the recreating indexes in background and not block the first connection.
Also in the Recovery& High Availibility IBM Handbook I have nothing found about the "recreating invalid index objects"-feature.
Kind regards
UtaHello Jens,
thanks for the detailed answer!
As you wrote, the only workarond with changing db cfg parameter from "restart" to "access" needs some manual intervention if we don't want to risk the limit of maximum dialog runtime. So actually we will leave it as it is. We have a workaround with starting sap in a second window, when the crash recovery is finished according to db2diag.log and the 1. connection (startsap db) ist still recreating invalid indexes.
How can one determine the invalid indexes, who need recreation ?
Joachim: we don't have a real problem at our site. Fortunatelly we have crash recoveries only in the rare cases of system crashes, etc. So we are lucky not to have it every day....
Hopefully the behaviour will be changed to background index recreation in some later DB release. -
"Beginning crash recovery of 1 threads"
Hi there!
Can you please inform if this is a problem? I'm getting "Beginning crash recovery of 1 threads" on every database startup (alert.log)
ThanksHere is my alert log from a few days:
Sun May 30 00:01:31 2010
ORACLE V10.2.0.4.0 - 64bit Production vsnsta=0
vsnsql=14 vsnxtr=3
Windows NT Version V6.0 Service Pack 2
CPU : 8 - type 8664, 8 Physical Cores
Process Affinity : 0x0000000000000000
Memory (Avail/Total): Ph:17900M/20477M, Ph+PgF:36037M/37825M
Sun May 30 00:01:31 2010
Starting ORACLE instance (restrict)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
IMODE=BR
ILAT =18
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.4.0.
System parameters with non-default values:
processes = 150
__shared_pool_size = 1526726656
__large_pool_size = 0
__java_pool_size = 16777216
__streams_pool_size = 0
nls_language = AMERICAN
nls_territory = AMERICA
sga_target = 10737418240
control_files = E:\ORADATA\MYDB\CONTROL01.CTL, F:\ORADATA\MYDB\CONTROL02.CTL, H:\ORADATA\MYDB\CONTROL03.CTL
db_block_size = 8192
__db_cache_size = 9177137152
compatible = 10.2.0.3.0
log_archive_dest_1 = LOCATION=g:\archives\MYDB
log_archive_format = ARC%S_%R.%T
db_file_multiblock_read_count= 16
undo_management = AUTO
undo_tablespace = UNDOTBS1
remote_login_passwordfile= EXCLUSIVE
db_domain =
dispatchers = (PROTOCOL=TCP) (SERVICE=MYDBXDB)
local_listener = (ADDRESS=(PROTOCOL=TCP)(HOST=192.2.6.154)(PORT=1521))
remote_dependencies_mode = SIGNATURE
job_queue_processes = 10
audit_file_dest = H:\ADMIN\MYDB\ADUMP
background_dump_dest = H:\ADMIN\MYDB\BDUMP
user_dump_dest = H:\ADMIN\MYDB\UDUMP
core_dump_dest = H:\ADMIN\MYDB\CDUMP
db_name = MYDB
open_cursors = 300
pga_aggregate_target = 1073741824
PMON started with pid=2, OS id=1808
PSP0 started with pid=3, OS id=4848
MMAN started with pid=4, OS id=4824
DBW0 started with pid=5, OS id=4604
LGWR started with pid=6, OS id=776
CKPT started with pid=7, OS id=2012
SMON started with pid=8, OS id=4404
RECO started with pid=9, OS id=4484
CJQ0 started with pid=10, OS id=4396
MMON started with pid=11, OS id=5088
Sun May 30 00:01:31 2010
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=12, OS id=4552
Sun May 30 00:01:31 2010
starting up 1 shared server(s) ...
Oracle Data Guard is not available in this edition of Oracle.
Sun May 30 00:01:31 2010
alter database "MYDB" mount exclusive
Sun May 30 00:01:35 2010
Setting recovery target incarnation to 2
Sun May 30 00:01:36 2010
Successful mount of redo thread 1, with mount id 4241184411
Sun May 30 00:01:36 2010
Database mounted in Exclusive Mode
Completed: alter database "MYDB" mount exclusive
Sun May 30 00:01:36 2010
alter database open
Sun May 30 00:01:37 2010
Beginning crash recovery of 1 threads
Sun May 30 00:01:37 2010
Started redo scan
Sun May 30 00:01:37 2010
Completed redo scan
895 redo blocks read, 112 data blocks need recovery
Sun May 30 00:01:37 2010
Started redo application at
Thread 1: logseq 8835, block 70913
Sun May 30 00:01:37 2010
Recovery of Online Redo Log: Thread 1 Group 3 Seq 8835 Reading mem 0
Mem# 0: H:\ORADATA\MYDB\REDO03.LOG
Sun May 30 00:01:37 2010
Completed redo application
Sun May 30 00:01:37 2010
Completed crash recovery at
Thread 1: logseq 8835, block 71808, scn 282384241
112 data blocks read, 112 data blocks written, 895 redo blocks read
Sun May 30 00:01:37 2010
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=16, OS id=1780
Sun May 30 00:01:37 2010
ARC0: Archival started
ARC1: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC1 started with pid=17, OS id=2524
Sun May 30 00:01:37 2010
Thread 1 advanced to log sequence 8836 (thread open)
Thread 1 opened at log sequence 8836
Current log# 1 seq# 8836 mem# 0: H:\ORADATA\MYDB\REDO01.LOG
Successful open of redo thread 1
Sun May 30 00:01:37 2010
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no SRL' ARCH
Sun May 30 00:01:37 2010
ARC1: Becoming the heartbeat ARCH
Sun May 30 00:01:37 2010
SMON: enabling cache recovery
Sun May 30 00:01:39 2010
Successfully onlined Undo Tablespace 1.
Sun May 30 00:01:39 2010
SMON: enabling tx recovery
Sun May 30 00:01:39 2010
Database Characterset is WE8ISO8859P1
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=18, OS id=4716
Sun May 30 00:01:42 2010
Completed: alter database open
Sun May 30 00:01:43 2010
ALTER SYSTEM disable restricted session;
Sun May 30 00:07:39 2010
Thread 1 advanced to log sequence 8837 (LGWR switch)
Current log# 2 seq# 8837 mem# 0: H:\ORADATA\MYDB\REDO02.LOG
Sun May 30 00:10:27 2010
Thread 1 advanced to log sequence 8838 (LGWR switch)
Current log# 3 seq# 8838 mem# 0: H:\ORADATA\MYDB\REDO03.LOG
Sun May 30 00:11:25 2010
Thread 1 advanced to log sequence 8839 (LGWR switch)
Current log# 1 seq# 8839 mem# 0: H:\ORADATA\MYDB\REDO01.LOG
Sun May 30 00:12:30 2010
Thread 1 advanced to log sequence 8840 (LGWR switch)
Current log# 2 seq# 8840 mem# 0: H:\ORADATA\MYDB\REDO02.LOG
Sun May 30 00:17:07 2010
Thread 1 advanced to log sequence 8841 (LGWR switch)
Current log# 3 seq# 8841 mem# 0: H:\ORADATA\MYDB\REDO03.LOG
Sun May 30 00:21:15 2010
Thread 1 advanced to log sequence 8842 (LGWR switch)
Current log# 1 seq# 8842 mem# 0: H:\ORADATA\MYDB\REDO01.LOG
Sun May 30 00:22:31 2010
Thread 1 advanced to log sequence 8843 (LGWR switch)
Current log# 2 seq# 8843 mem# 0: H:\ORADATA\MYDB\REDO02.LOG
Sun May 30 00:23:44 2010
Thread 1 advanced to log sequence 8844 (LGWR switch)
Current log# 3 seq# 8844 mem# 0: H:\ORADATA\MYDB\REDO03.LOG
Sun May 30 00:26:44 2010
Thread 1 advanced to log sequence 8845 (LGWR switch)
Current log# 1 seq# 8845 mem# 0: H:\ORADATA\MYDB\REDO01.LOG
Sun May 30 00:27:51 2010
Thread 1 advanced to log sequence 8846 (LGWR switch)
Current log# 2 seq# 8846 mem# 0: H:\ORADATA\MYDB\REDO02.LOG
Sun May 30 00:30:51 2010
Thread 1 advanced to log sequence 8847 (LGWR switch)
Current log# 3 seq# 8847 mem# 0: H:\ORADATA\MYDB\REDO03.LOG
Sun May 30 01:01:42 2010
Thread 1 advanced to log sequence 8848 (LGWR switch)
Current log# 1 seq# 8848 mem# 0: H:\ORADATA\MYDB\REDO01.LOG
Sun May 30 01:01:58 2010
Thread 1 advanced to log sequence 8849 (LGWR switch)
Current log# 2 seq# 8849 mem# 0: H:\ORADATA\MYDB\REDO02.LOG
Sun May 30 01:02:13 2010
Thread 1 advanced to log sequence 8850 (LGWR switch)
Current log# 3 seq# 8850 mem# 0: H:\ORADATA\MYDB\REDO03.LOG
Sun May 30 01:02:29 2010
Thread 1 advanced to log sequence 8851 (LGWR switch)
Current log# 1 seq# 8851 mem# 0: H:\ORADATA\MYDB\REDO01.LOG
Sun May 30 01:02:44 2010
Thread 1 advanced to log sequence 8852 (LGWR switch)
Current log# 2 seq# 8852 mem# 0: H:\ORADATA\MYDB\REDO02.LOG
Sun May 30 01:02:54 2010
Thread 1 advanced to log sequence 8853 (LGWR switch)
Current log# 3 seq# 8853 mem# 0: H:\ORADATA\MYDB\REDO03.LOG
Sun May 30 13:00:58 2010
Thread 1 advanced to log sequence 8854 (LGWR switch)
Current log# 1 seq# 8854 mem# 0: H:\ORADATA\MYDB\REDO01.LOG
Dump file h:\admin\MYDB\bdump\alert_MYDB.log
Mon May 31 00:00:33 2010
ORACLE V10.2.0.4.0 - 64bit Production vsnsta=0
vsnsql=14 vsnxtr=3
Windows NT Version V6.0 Service Pack 2
CPU : 8 - type 8664, 8 Physical Cores
Process Affinity : 0x0000000000000000
Memory (Avail/Total): Ph:18101M/20477M, Ph+PgF:35984M/37825M
Mon May 31 00:00:33 2010
Starting ORACLE instance (restrict)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
IMODE=BR
ILAT =18
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.4.0.
System parameters with non-default values:
processes = 150
__shared_pool_size = 1526726656
__large_pool_size = 0
__java_pool_size = 16777216
__streams_pool_size = 0
nls_language = AMERICAN
nls_territory = AMERICA
sga_target = 10737418240
control_files = E:\ORADATA\MYDB\CONTROL01.CTL, F:\ORADATA\MYDB\CONTROL02.CTL, H:\ORADATA\MYDB\CONTROL03.CTL
db_block_size = 8192
__db_cache_size = 9177137152
compatible = 10.2.0.3.0
log_archive_dest_1 = LOCATION=g:\archives\MYDB
log_archive_format = ARC%S_%R.%T
db_file_multiblock_read_count= 16
undo_management = AUTO
undo_tablespace = UNDOTBS1
remote_login_passwordfile= EXCLUSIVE
db_domain =
dispatchers = (PROTOCOL=TCP) (SERVICE=MYDBXDB)
local_listener = (ADDRESS=(PROTOCOL=TCP)(HOST=192.2.6.154)(PORT=1521))
remote_dependencies_mode = SIGNATURE
job_queue_processes = 10
audit_file_dest = H:\ADMIN\MYDB\ADUMP
background_dump_dest = H:\ADMIN\MYDB\BDUMP
user_dump_dest = H:\ADMIN\MYDB\UDUMP
core_dump_dest = H:\ADMIN\MYDB\CDUMP
db_name = MYDB
open_cursors = 300
pga_aggregate_target = 1073741824
PMON started with pid=2, OS id=1068
PSP0 started with pid=3, OS id=4512
MMAN started with pid=4, OS id=4452
DBW0 started with pid=5, OS id=784
LGWR started with pid=6, OS id=4608
CKPT started with pid=7, OS id=4524
SMON started with pid=8, OS id=1976
RECO started with pid=9, OS id=3808
CJQ0 started with pid=10, OS id=4056
MMON started with pid=11, OS id=4792
Mon May 31 00:00:33 2010
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=12, OS id=4208
Mon May 31 00:00:33 2010
starting up 1 shared server(s) ...
Oracle Data Guard is not available in this edition of Oracle.
Mon May 31 00:00:33 2010
alter database "MYDB" mount exclusive
Mon May 31 00:00:37 2010
Setting recovery target incarnation to 2
Mon May 31 00:00:37 2010
Successful mount of redo thread 1, with mount id 4241228001
Mon May 31 00:00:37 2010
Database mounted in Exclusive Mode
Completed: alter database "MYDB" mount exclusive
Mon May 31 00:00:37 2010
alter database open
Mon May 31 00:00:38 2010
Beginning crash recovery of 1 threads
Mon May 31 00:00:38 2010
Started redo scan
Mon May 31 00:00:38 2010
Completed redo scan
815 redo blocks read, 108 data blocks need recovery
Mon May 31 00:00:38 2010
Started redo application at
Thread 1: logseq 8854, block 31079
Mon May 31 00:00:38 2010
Recovery of Online Redo Log: Thread 1 Group 1 Seq 8854 Reading mem 0
Mem# 0: H:\ORADATA\MYDB\REDO01.LOG
Mon May 31 00:00:38 2010
Completed redo application
Mon May 31 00:00:38 2010
Completed crash recovery at
Thread 1: logseq 8854, block 31894, scn 282601383
108 data blocks read, 108 data blocks written, 815 redo blocks read
Mon May 31 00:00:38 2010
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=16, OS id=1792
Mon May 31 00:00:38 2010
ARC0: Archival started
ARC1: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC1 started with pid=17, OS id=5048
Mon May 31 00:00:38 2010
Thread 1 advanced to log sequence 8855 (thread open)
Thread 1 opened at log sequence 8855
Current log# 2 seq# 8855 mem# 0: H:\ORADATA\MYDB\REDO02.LOG
Successful open of redo thread 1
Mon May 31 00:00:38 2010
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
Mon May 31 00:00:38 2010
ARC0: Becoming the heartbeat ARCH
Mon May 31 00:00:38 2010
SMON: enabling cache recovery
Mon May 31 00:00:40 2010
Successfully onlined Undo Tablespace 1.
Mon May 31 00:00:40 2010
SMON: enabling tx recovery
Mon May 31 00:00:40 2010
Database Characterset is WE8ISO8859P1
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=18, OS id=4612
Mon May 31 00:00:42 2010
Completed: alter database open
Mon May 31 00:00:42 2010
ALTER SYSTEM disable restricted session;
Mon May 31 00:06:45 2010
Thread 1 advanced to log sequence 8856 (LGWR switch)
Current log# 3 seq# 8856 mem# 0: H:\ORADATA\MYDB\REDO03.LOG
Mon May 31 00:09:34 2010
Thread 1 advanced to log sequence 8857 (LGWR switch)
Current log# 1 seq# 8857 mem# 0: H:\ORADATA\MYDB\REDO01.LOG
Mon May 31 00:10:33 2010
Thread 1 advanced to log sequence 8858 (LGWR switch)
Current log# 2 seq# 8858 mem# 0: H:\ORADATA\MYDB\REDO02.LOG
Mon May 31 00:11:38 2010
Thread 1 advanced to log sequence 8859 (LGWR switch)
Current log# 3 seq# 8859 mem# 0: H:\ORADATA\MYDB\REDO03.LOG
Mon May 31 00:16:13 2010
Thread 1 advanced to log sequence 8860 (LGWR switch)
Current log# 1 seq# 8860 mem# 0: H:\ORADATA\MYDB\REDO01.LOG
Mon May 31 00:20:09 2010
Thread 1 advanced to log sequence 8861 (LGWR switch)
Current log# 2 seq# 8861 mem# 0: H:\ORADATA\MYDB\REDO02.LOG
Mon May 31 00:21:28 2010
Thread 1 advanced to log sequence 8862 (LGWR switch)
Current log# 3 seq# 8862 mem# 0: H:\ORADATA\MYDB\REDO03.LOG
Mon May 31 00:22:37 2010
Thread 1 advanced to log sequence 8863 (LGWR switch)
Current log# 1 seq# 8863 mem# 0: H:\ORADATA\MYDB\REDO01.LOG
Mon May 31 00:25:42 2010
Thread 1 advanced to log sequence 8864 (LGWR switch)
Current log# 2 seq# 8864 mem# 0: H:\ORADATA\MYDB\REDO02.LOG
Mon May 31 00:26:47 2010
Thread 1 advanced to log sequence 8865 (LGWR switch)
Current log# 3 seq# 8865 mem# 0: H:\ORADATA\MYDB\REDO03.LOG
Mon May 31 00:29:52 2010
Thread 1 advanced to log sequence 8866 (LGWR switch)
Current log# 1 seq# 8866 mem# 0: H:\ORADATA\MYDB\REDO01.LOG
Mon May 31 10:43:39 2010
Thread 1 advanced to log sequence 8867 (LGWR switch)
Current log# 2 seq# 8867 mem# 0: H:\ORADATA\MYDB\REDO02.LOG
Mon May 31 11:30:27 2010
Thread 1 advanced to log sequence 8868 (LGWR switch)
Current log# 3 seq# 8868 mem# 0: H:\ORADATA\MYDB\REDO03.LOG
Mon May 31 12:57:56 2010
Thread 1 advanced to log sequence 8869 (LGWR switch)
Current log# 1 seq# 8869 mem# 0: H:\ORADATA\MYDB\REDO01.LOG
Mon May 31 15:19:50 2010
Thread 1 advanced to log sequence 8870 (LGWR switch)
Current log# 2 seq# 8870 mem# 0: H:\ORADATA\MYDB\REDO02.LOG
Mon May 31 22:00:52 2010
Thread 1 advanced to log sequence 8871 (LGWR switch)
Current log# 3 seq# 8871 mem# 0: H:\ORADATA\MYDB\REDO03.LOG
Mon May 31 22:01:02 2010
Thread 1 advanced to log sequence 8872 (LGWR switch)
Current log# 1 seq# 8872 mem# 0: H:\ORADATA\MYDB\REDO01.LOG
Mon May 31 22:01:27 2010
Thread 1 advanced to log sequence 8873 (LGWR switch)
Current log# 2 seq# 8873 mem# 0: H:\ORADATA\MYDB\REDO02.LOG
Mon May 31 22:01:47 2010
Thread 1 advanced to log sequence 8874 (LGWR switch)
Current log# 3 seq# 8874 mem# 0: H:\ORADATA\MYDB\REDO03.LOG
Mon May 31 22:02:09 2010
Thread 1 advanced to log sequence 8875 (LGWR switch)
Current log# 1 seq# 8875 mem# 0: H:\ORADATA\MYDB\REDO01.LOG
Mon May 31 22:02:24 2010
Thread 1 advanced to log sequence 8876 (LGWR switch)
Current log# 2 seq# 8876 mem# 0: H:\ORADATA\MYDB\REDO02.LOG
Mon May 31 22:02:30 2010
Thread 1 advanced to log sequence 8877 (LGWR switch)
Current log# 3 seq# 8877 mem# 0: H:\ORADATA\MYDB\REDO03.LOG
Mon May 31 22:02:37 2010
Thread 1 advanced to log sequence 8878 (LGWR switch)
Current log# 1 seq# 8878 mem# 0: H:\ORADATA\MYDB\REDO01.LOG
Mon May 31 22:02:45 2010
Thread 1 advanced to log sequence 8879 (LGWR switch)
Current log# 2 seq# 8879 mem# 0: H:\ORADATA\MYDB\REDO02.LOG
Mon May 31 22:02:50 2010
Thread 1 advanced to log sequence 8880 (LGWR switch)
Current log# 3 seq# 8880 mem# 0: H:\ORADATA\MYDB\REDO03.LOG
Mon May 31 22:02:54 2010
Thread 1 advanced to log sequence 8881 (LGWR switch)
Current log# 1 seq# 8881 mem# 0: H:\ORADATA\MYDB\REDO01.LOG
Mon May 31 22:02:58 2010
Thread 1 advanced to log sequence 8882 (LGWR switch)
Current log# 2 seq# 8882 mem# 0: H:\ORADATA\MYDB\REDO02.LOG
Mon May 31 22:03:15 2010
Thread 1 advanced to log sequence 8883 (LGWR switch)
Current log# 3 seq# 8883 mem# 0: H:\ORADATA\MYDB\REDO03.LOG
Dump file h:\admin\MYDB\bdump\alert_MYDB.log
Tue Jun 01 00:01:05 2010
ORACLE V10.2.0.4.0 - 64bit Production vsnsta=0
vsnsql=14 vsnxtr=3
Windows NT Version V6.0 Service Pack 2
CPU : 8 - type 8664, 8 Physical Cores
Process Affinity : 0x0000000000000000
Memory (Avail/Total): Ph:18247M/20477M, Ph+PgF:36004M/37825M
Tue Jun 01 00:01:05 2010
Starting ORACLE instance (restrict)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
IMODE=BR
ILAT =18
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.4.0.
System parameters with non-default values:
processes = 150
__shared_pool_size = 1526726656
__large_pool_size = 0
__java_pool_size = 16777216
__streams_pool_size = 0
nls_language = AMERICAN
nls_territory = AMERICA
sga_target = 10737418240
control_files = E:\ORADATA\MYDB\CONTROL01.CTL, F:\ORADATA\MYDB\CONTROL02.CTL, H:\ORADATA\MYDB\CONTROL03.CTL
db_block_size = 8192
__db_cache_size = 9177137152
compatible = 10.2.0.3.0
log_archive_dest_1 = LOCATION=g:\archives\MYDB
log_archive_format = ARC%S_%R.%T
db_file_multiblock_read_count= 16
undo_management = AUTO
undo_tablespace = UNDOTBS1
remote_login_passwordfile= EXCLUSIVE
db_domain =
dispatchers = (PROTOCOL=TCP) (SERVICE=MYDBXDB)
local_listener = (ADDRESS=(PROTOCOL=TCP)(HOST=192.2.6.154)(PORT=1521))
remote_dependencies_mode = SIGNATURE
job_queue_processes = 10
audit_file_dest = H:\ADMIN\MYDB\ADUMP
background_dump_dest = H:\ADMIN\MYDB\BDUMP
user_dump_dest = H:\ADMIN\MYDB\UDUMP
core_dump_dest = H:\ADMIN\MYDB\CDUMP
db_name = MYDB
open_cursors = 300
pga_aggregate_target = 1073741824
PMON started with pid=2, OS id=2724
PSP0 started with pid=3, OS id=5088
MMAN started with pid=4, OS id=4436
DBW0 started with pid=5, OS id=4400
LGWR started with pid=6, OS id=792
CKPT started with pid=7, OS id=4036
SMON started with pid=8, OS id=4220
RECO started with pid=9, OS id=1856
CJQ0 started with pid=10, OS id=332
MMON started with pid=11, OS id=4224
Tue Jun 01 00:01:05 2010
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=12, OS id=4784
Tue Jun 01 00:01:05 2010
starting up 1 shared server(s) ...
Oracle Data Guard is not available in this edition of Oracle.
Tue Jun 01 00:01:05 2010
alter database "MYDB" mount exclusive
Tue Jun 01 00:01:10 2010
Setting recovery target incarnation to 2
Tue Jun 01 00:01:10 2010
Successful mount of redo thread 1, with mount id 4241292930
Tue Jun 01 00:01:10 2010
Database mounted in Exclusive Mode
Completed: alter database "MYDB" mount exclusive
Tue Jun 01 00:01:10 2010
alter database open
Tue Jun 01 00:01:10 2010
Beginning crash recovery of 1 threads
Tue Jun 01 00:01:10 2010
Started redo scan
Tue Jun 01 00:01:11 2010
Completed redo scan
893 redo blocks read, 96 data blocks need recovery
Tue Jun 01 00:01:11 2010
Started redo application at
Thread 1: logseq 8883, block 18558
Tue Jun 01 00:01:11 2010
Recovery of Online Redo Log: Thread 1 Group 3 Seq 8883 Reading mem 0
Mem# 0: H:\ORADATA\MYDB\REDO03.LOG
Tue Jun 01 00:01:11 2010
Completed redo application
Tue Jun 01 00:01:11 2010
Completed crash recovery at
Thread 1: logseq 8883, block 19451, scn 283448451
96 data blocks read, 96 data blocks written, 893 redo blocks read
Tue Jun 01 00:01:11 2010
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=16, OS id=1804
Tue Jun 01 00:01:11 2010
ARC0: Archival started
ARC1: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC1 started with pid=17, OS id=4988
Tue Jun 01 00:01:11 2010
Thread 1 advanced to log sequence 8884 (thread open)
Thread 1 opened at log sequence 8884
Current log# 1 seq# 8884 mem# 0: H:\ORADATA\MYDB\REDO01.LOG
Successful open of redo thread 1
Tue Jun 01 00:01:11 2010
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
Tue Jun 01 00:01:11 2010
ARC0: Becoming the heartbeat ARCH
Tue Jun 01 00:01:11 2010
SMON: enabling cache recovery
Tue Jun 01 00:01:11 2010
Successfully onlined Undo Tablespace 1.
Tue Jun 01 00:01:11 2010
SMON: enabling tx recovery
Tue Jun 01 00:01:11 2010
Database Characterset is WE8ISO8859P1
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=18, OS id=244
Tue Jun 01 00:01:13 2010
Completed: alter database open
Tue Jun 01 00:01:13 2010
ALTER SYSTEM disable restricted session;
Tue Jun 01 00:07:16 2010
Thread 1 advanced to log sequence 8885 (LGWR switch)
Current log# 2 seq# 8885 mem# 0: H:\ORADATA\MYDB\REDO02.LOG
Tue Jun 01 00:10:00 2010
Thread 1 advanced to log sequence 8886 (LGWR switch)
Current log# 3 seq# 8886 mem# 0: H:\ORADATA\MYDB\REDO03.LOG
Tue Jun 01 00:10:58 2010
Thread 1 advanced to log sequence 8887 (LGWR switch)
Current log# 1 seq# 8887 mem# 0: H:\ORADATA\MYDB\REDO01.LOG
Tue Jun 01 00:12:03 2010
Thread 1 advanced to log sequence 8888 (LGWR switch)
Current log# 2 seq# 8888 mem# 0: H:\ORADATA\MYDB\REDO02.LOG
Tue Jun 01 00:16:44 2010
Thread 1 advanced to log sequence 8889 (LGWR switch)
Current log# 3 seq# 8889 mem# 0: H:\ORADATA\MYDB\REDO03.LOG
Tue Jun 01 00:20:52 2010
Thread 1 advanced to log sequence 8890 (LGWR switch)
Current log# 1 seq# 8890 mem# 0: H:\ORADATA\MYDB\REDO01.LOG
Tue Jun 01 00:22:10 2010
Thread 1 advanced to log sequence 8891 (LGWR switch)
Current log# 2 seq# 8891 mem# 0: H:\ORADATA\MYDB\REDO02.LOG
Tue Jun 01 00:23:28 2010
Thread 1 advanced to log sequence 8892 (LGWR switch)
Current log# 3 seq# 8892 mem# 0: H:\ORADATA\MYDB\REDO03.LOG
Tue Jun 01 00:27:03 2010
Thread 1 advanced to log sequence 8893 (LGWR switch)
Current log# 1 seq# 8893 mem# 0: H:\ORADATA\MYDB\REDO01.LOG
Tue Jun 01 00:28:23 2010
Thread 1 advanced to log sequence 8894 (LGWR switch)
Current log# 2 seq# 8894 mem# 0: H:\ORADATA\MYDB\REDO02.LOG
Tue Jun 01 00:32:03 2010
Thread 1 advanced to log sequence 8895 (LGWR switch)
Current log# 3 seq# 8895 mem# 0: H:\ORADATA\MYDB\REDO03.LOG
Maybe you are looking for
-
New windows 8.1 clients getting certificate error
We are running exchange 2010 and one of our end-users just recently purchased a windows 8.1 laptop. When he tries to connect to exchange using the built-in mail app, he gets the error, "To connect to this account, you need a valid certificate on thi
-
Please explain why SMPT error message is occurring and how to find my password
SMPT error message is occurring every time I try and send an email. How do I recover this password? I do not remember what it would be.
-
Missing Add DHCP Reservations Option
I have an older Airport Extreme Base Station (flying saucer variety...version 5.7...purchased approx. 2005(?) 802.11b/g). I am using an iMac with AirPort Utility 5.5.3. I am attempting to set up my AEBS to allow Remote Management from my MacBook Pr
-
Hi, I just have DEV instance ready without TMS configured, but QAS server not ready. My developers will be using DEV soon, in order for their TR (transport request) to be transportable when QAS is ready, i need to setup a virtual QAS. is there any gu
-
I have a rarely and barely used G4 w/ 10.3.9. I bought it only for music recording purposes AND to become more familiar with mac (and to bask in the aura of god given superiority reserved for mac users.)Alas, I dwell in the purgatorial abyss. Right n