Next log sequence
The archive log list gives the following output:
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination f:\ora9i\oradata\db01\archive
Oldest online log sequence 26
Next log sequence to archive 28
Current log sequence 28
My question is if the oldest online log sequence is 26, then the next and current log sequence should be 27. But why it is 28?
Regards,
Aqueel.
Generally speaking, if the archiver (ARCn) is up-to-date with archiving, ARCn will begin archiving log 1 as soon as (within a second or so) LGWR switches to log 2. There are no guarantees that this will always happen.
For example, if you have 3 redo logs, and it takes ARCn 15 seconds to write each log off to the archive destination, and somebody submits a large update that fills each log in 3 seconds, then you have a situation like this:
T + 0 Update submitted
T + 3 Log 1 filled switch to log 2
T + 4 ARCn begins archiving log 1
T + 6 Log 2 filled switch to log 3
T + 9 log 3 filled try to switch to log 1
But it is not archived yet so wait - no transactions can happen in the database at all until ARCn is finished.
t + 14 ARCn finishes archiving log 1 LGWR can write and transactions are allowed again
HTH
John
Similar Messages
-
Next log sequence to archive in Standby Database (RAC Dataguard Issue)
Hi All,
I just had implemented Data Guard in our server. My primary Database is RAC configured, but it is only single node. The other Instance was removed and converted it to Developement Instance. For the reason I kept the primary as RAC is when I will implement dataguard, my Primary Database is RAC with 7 nodes.
The first test is successful, and I was able to "switchover" from my primary to standby. I failed in the 'FAILOVER" test.
I restore my primary server and redo the setup.
BTW, my standby DB is physical standby.
When I try to switchover again and issue archive log list, below is my output.
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 38
*Next log sequence to archive 0*
Current log sequence 38
SQL> select open_mode, database_role from v$database;
OPEN_MODE DATABASE_ROLE
MOUNTED PHYSICAL STANDBY
===============================================
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 38
*Next log sequence to archive 38*
Current log sequence 38
SQL> select open_mode, database_role from v$database;
OPEN_MODE DATABASE_ROLE
READ WRITE PRIMARY
In my first attempt to switchover before I failed in "FAILOVER" test, I also issue +archive log list+ in both primary and standby database, and if I remember it right, next log sequence on both should be identical. Am I right on this?
Thanks in Advance.
Jay AOr Am i just overthinking on this?
Is dataguard only looking for the current and oldest log sequence? -
Next log sequence to archive is different
Hi,
I have doubt on standby (DR) concept.
I can see that in my standby database next log sequence to archive shows 0.
Is this ok or something is wrong?
PRODUCTION
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /u006/app/archive/XXPROD/arch
Oldest online log sequence 2627
Next log sequence to archive 2631
Current log sequence 2631
STANDBY
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /u006/app/archive/XXPROD/arch
Oldest online log sequence 2627
Next log sequence to archive 0
Current log sequence 2631Hello;
Short answer no nothing is wrong.
Its the same on mine :
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 5069
Next log sequence to archive 0
Current log sequence 5071
SQL> I use v$archived_log to check mine standby :
SELECT name as STANDBY, SEQUENCE#, applied, completion_time from v$archived_log WHERE DEST_ID = 2 AND NEXT_TIME > SYSDATE -1;Against my Primary I get the last log :
select max(sequence#) from v$archived_log where NEXT_TIME > sysdate -1;Data Guard has a set of v$ views to check results, 8archive log list8 isn't so good since with Data Guard you have two copies of the same database in different roles.
Another query I like is : (Run on the standby)
select process, status, sequence#, block# from v$managed_standby;The Oracle doc E10700-02 has several example in chapter 9 "Monitoring Primary, Physical Standby, and Snapshot Standby Databases"
Also section "3.2.7 Verify the Physical Standby Database Is Performing Properly"
Best Regards
mseberg -
Very Urgent: Thread 1 cannot allocate new log, sequence 6 : Script stuck
I am running one script, it is stuck with log file showing:
Thread 1 cannot allocate new log, sequence 6
All online logs needed archiving
Current log# 7 seq# 5 mem# 0: /u13/sjmarte/oradata/redo7a.log
I have checked the database: it is in archivelog mode
Checked the archvie dest: we have space in TB's
And almost 24GB's occupied by log files each of 6GB's.
====================================
Can any one please help us how to get rid of this issueSorry I m new to this forum.
We dont have a seperate FRA in this case.
This is the log file information:
Wed May 18 13:28:23 2011
Thread 1 advanced to log sequence 5 (LGWR switch)
Current log# 7 seq# 5 mem# 0: /u13/sjmarte/oradata/redo7a.log
Current log# 7 seq# 5 mem# 1: /u14/sjmarte/oradata/redo7b.log
Wed May 18 13:31:58 2011
ORACLE Instance sjmarte - Can not allocate log, archival required
Wed May 18 13:31:58 2011
Thread 1 cannot allocate new log, sequence 6
All online logs needed archiving
Current log# 7 seq# 5 mem# 0: /u13/sjmarte/oradata/redo7a.log
Current log# 7 seq# 5 mem# 1: /u14/sjmarte/oradata/redo7b.log
Here is archive log list
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /backup/oracle/sjmarte/archive
Oldest online log sequence 2
Next log sequence to archive 2
Current log sequence 5
Edited by: 784786 on May 18, 2011 11:35 AM -
Log sequence difference among RAC Instances
RDBMS Version : 11.2
Platform : Solaris 10
In our RAC DB, we have 6 redo logs.
SQL> select * from v$logfile order by 1,2;
GROUP# STATUS TYPE MEMBER IS_
1 ONLINE +ORCL_ARCH01/ORCL_ARCH/orcl_log01.dbf NO
2 ONLINE +ORCL_ARCH01/ORCL_ARCH/orcl_log02.dbf NO
3 ONLINE +ORCL_ARCH01/ORCL_ARCH/orcl_log03.dbf NO
4 ONLINE +ORCL_ARCH01/ORCL_ARCH/orcl_log04.dbf NO
5 ONLINE +ORCL_ARCH01/ORCL_ARCH/orcl_log05.dbf NO
6 ONLINE +ORCL_ARCH01/ORCL_ARCH/orcl_log06.dbf NO
6 rows selected.
Logically or shall I say 'internally' , 3 redo logs are allocated per thread. But they all belong to one database.
SQL> select group#,thread#,members from v$log order by 1,2;
GROUP# THREAD# MEMBERS
1 1 1
2 1 1
3 1 1
4 2 1
5 2 1
6 2 1
6 rows selected.
SQL> exit;If all these 6 redo log files belong to one database, then why do they have different max (sequence#) ?
ie. The 'Oldest online log sequence' in Node1 shows 3432 and
''Oldest online log sequence' in Node2 shows 3188 (a difference of 244 )
-- Instance1 in Node1
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination +ORCL_ARCH01/ORCL_ARCH
Oldest online log sequence 3432 ------------------------->
Next log sequence to archive 3434
Current log sequence 3434
-- Instance 2 in Node2
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination +ORCL_ARCH01/ORCL_ARCH
Oldest online log sequence 3188 ------------------------> ( 3432 - 3188 = 244)
Next log sequence to archive 3190
Current log sequence 3190So, this means Node1 is more loaded than Node2 ?
So, in a properly configured RAC set both instances should show almost similar number for 'Oldest online log sequence' ? (ignoring the manual switches) -
Third party backup software, how is the log sequence working?
Me and a colleague had a discussion about how third party software and full backups locally on the SQL works together.
If we use TSM that do full backups and then logbackups every hour in between for example.
If I between the two full backups from TSM accidently do a "non copy-only" full backup do I then also break the whole log sequence backup from then and untill the next TSM backup is?
Or can I use the full backup from my mistake and then take the log backups from TSM that occured after that fail and restore the database?
I guess this depends on the third party backup software, but in my mind it should work but according to him it doesn't.
Try to "paint" how I mean:
I = full TSM backup
- = log TSM
F = my fail backup full but not copy only.
I---F-------I
^ is where I would want to restore with both my full one and the logs from TSM. Hope you understand what I mean.yes, you should be able to use the full backup taken in middle and use the rest of the log backups taken afterwards to restore the database.while I do not use TSM, we use QUEST(DELL) LITESPEED, that takes full backup once a day and log backups
every 15mins.
if someone accidentally takes full backup in the middle of day with out 'copy only',
log sequence will break and successive log backups depend on this full back up.
while this should be prevented from happening in first place, you can still restore from native full backup and then apply log backups taken from third party taken after the native Full backup.
if this happens, I would restore the FULLBACKP with NORECOVERY using NATIVE SQL and then use lite speed syntax to restore the log backups.Remember, native sql cannot read third party formatted backups(atleast litespeed), thats why I restore the full backup
using native sql, since it was taken with native sql backup and log backups using litespeed syntax.
Hope it Helps!!
Thanks, well it was just a theory discussion we had about the issue. But none of us could find info on the internet easy to prove our point :) Thanks. -
Thread 1 advanced to log sequence (redo log)
Hi All,
db:oracle 10gR2(10.2.0.4)
os:solaris10
My alert log file shows following information all the time....can you please explain me whats going on??
Mon Jan 30 01:40:30 2012
Thread 1 advanced to log sequence 253305
Current log# 2 seq# 253305 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO02.LOG
Mon Jan 30 01:45:40 2012
Thread 1 advanced to log sequence 253306
Current log# 3 seq# 253306 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO03.LOG
Mon Jan 30 01:51:21 2012
Thread 1 advanced to log sequence 253307
Current log# 1 seq# 253307 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO01.LOG
Mon Jan 30 01:56:53 2012
Thread 1 advanced to log sequence 253308
Current log# 2 seq# 253308 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO02.LOG
Mon Jan 30 02:01:57 2012
Thread 1 advanced to log sequence 253309
Current log# 3 seq# 253309 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO03.LOG
Mon Jan 30 02:06:31 2012
Thread 1 advanced to log sequence 253310
Current log# 1 seq# 253310 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO01.LOG
Mon Jan 30 02:11:37 2012
Thread 1 advanced to log sequence 253311
Current log# 2 seq# 253311 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO02.LOG
Mon Jan 30 02:16:44 2012
Thread 1 advanced to log sequence 253312
Current log# 3 seq# 253312 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO03.LOG
Mon Jan 30 02:21:51 2012
Thread 1 advanced to log sequence 253313
Current log# 1 seq# 253313 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO01.LOG
Mon Jan 30 02:27:11 2012
Thread 1 advanced to log sequence 253314
Current log# 2 seq# 253314 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO02.LOG
Mon Jan 30 02:32:31 2012
Thread 1 advanced to log sequence 253315
Current log# 3 seq# 253315 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO03.LOG
Mon Jan 30 02:37:25 2012
Thread 1 advanced to log sequence 253316
Current log# 1 seq# 253316 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO01.LOG
Mon Jan 30 02:42:15 2012
Thread 1 advanced to log sequence 253317
Current log# 2 seq# 253317 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO02.LOG
Mon Jan 30 02:47:05 2012
Thread 1 advanced to log sequence 253318
Current log# 3 seq# 253318 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO03.LOG
I appreciate your response......
thanks.This information shows that the log switch has occured.
The LGWR writes the redo information from the redo log buffer to the online redo log file. When the current online redo log file fills, LGWR begins writing to the next available online redo log file. In the mean time, the ARC process archives the contents of the filled online redo log file (If the database is in archivelog mode. If its in noarchive mode, then the filled online redo log file would not be archived). These archives are given a unique log sequence number.
In your case 253305, 253306..are the log sequence numbers.
You can refer http://docs.oracle.com/cd/B10501_01/server.920/a96521/onlineredo.htm for a detailed information -
I don't know if this can be done with VI Logger or need to use Labview V7.1.
After browsing through the VI Logger User Manual, it looks like the triggering that you are hoping to accomplish is possible. However, incrementing the filename for the next logging event is not going to be possible. VI Logger does exactly what its name tells - logs data. I don't think the automation that you are hoping to accomplish is possible.
For help with setting up your application, if you do choose to stay with VI Logger, make sure to chek out the Getting Started with VI Logger Manual.
Best of luck.
Jared A -
Hi guys,
as I am still new to RMAN I would be greatfull to You for some help and guidance here.
I am cloning database with RMAN duplicate database command and at the and of the script I got RMAN-06055: could not find log sequence 86362 thread 1 .
The script is :
RMAN> RUN {
2> allocate channel t1 type 'SBT_TAPE';
3> ALLOCATE AUXILIARY CHANNEL aux1 type 'SBT_TAPE';
4> ALLOCATE AUXILIARY CHANNEL aux2 type 'SBT_TAPE';
5> send 'NSR_ENV=(NSR_SERVER=servername,NSR_CLIENT=clientname)';
6> SET UNTIL TIME "to_date( '25.03.2008 08:00:00','dd.mm.yyyy hh24:mi:ss')";
7> DUPLICATE TARGET DATABASE TO GMIGR3
8> DB_FILE_NAME_CONVERT =('/lun0/prod/','/u01/lun0/gmigr3/'
9> '/lun1/prod/','/u01/lun0/gmigr3/'
10> '/lun2/prod/','/u01/lun0/gmigr3/'
11> '/lun3/prod/','/u01/lun0/gmigr3/'
12> '/lun4/prod/','/u01/lun0/gmigr3/'
13> )
14> PFILE = '?/dbs/initGMIGR3.ora'
15> LOGFILE
16> GROUP 1 ('/u01/lun0/gmigr3/log1a.dbf', '/u01/lun0/gmigr3/log1b.dbf') SIZE 100M,
17> GROUP 2 ('/u01/lun0/gmigr3/log2a.dbf', '/u01/lun0/gmigr3/log2b.dbf') SIZE 100M,
18> GROUP 3 ('/u01/lun0/gmigr3/log3a.dbf', '/u01/lun0/gmigr3/log3b.dbf') SIZE 100M,
19> GROUP 4 ('/u01/lun0/gmigr3/log4a.dbf', '/u01/lun0/gmigr3/log4b.dbf') SIZE 100M,
20> GROUP 5 ('/u01/lun0/gmigr3/log5a.dbf', '/u01/lun0/gmigr3/log5b.dbf') SIZE 100M REUSE
21> ;
22> release channel aux1;
23> release channel aux2;
24> release channel t1;and here is the log,
so what would be your advice on this :
allocated channel: t1
channel t1: sid=1339 devtype=SBT_TAPE
channel t1: NMO v4.5.0.0
allocated channel: aux1
channel aux1: sid=870 devtype=SBT_TAPE
channel aux1: NMO v4.5.0.0
allocated channel: aux2
channel aux2: sid=872 devtype=SBT_TAPE
channel aux2: NMO v4.5.0.0
sent command to channel: t1
sent command to channel: aux1
sent command to channel: aux2
executing command: SET until clause
Starting Duplicate Db at 25-MAR-08
contents of Memory Script:
set until scn 8177337546005;
set newname for datafile 1 to
"/u01/lun0/hanfa2/system01.dbf";
set newname for datafile 2 to
"/u01/lun0/hanfa2/system02.dbf";
set newname for datafile 3 to
"/u01/lun0/hanfa2/system03.dbf";
set newname for datafile 4 to
"/u01/lun0/hanfa2/system04.dbf";
set newname for datafile 5 to
"/u01/lun0/hanfa2/system05.dbf";
set newname for datafile 6 to
"/u01/lun0/hanfa2/ctxd01.dbf";
set newname for datafile 7 to
"/u01/lun0/hanfa2/owad01.dbf";
set newname for datafile 8 to
"/u01/lun0/hanfa2/a_queue02.dbf";
set newname for datafile 9 to
"/u01/lun0/hanfa2/odm.dbf";
set newname for datafile 10 to
"/u01/lun0/hanfa2/olap.dbf";
set newname for datafile 11 to
"/u01/lun0/hanfa2/xxcounter03.dbf";
set newname for datafile 12 to
"/u01/lun0/hanfa2/xxcounter02.dbf";
set newname for datafile 13 to
"/u01/lun0/hanfa2/xxcounter01.dbf";
set newname for datafile 14 to
"/u01/lun0/hanfa2/sysaux01.dbf";
set newname for datafile 15 to
"/u01/lun0/hanfa2/system12.dbf";
set newname for datafile 16 to
"/u01/lun0/hanfa2/undo06.dbf";
set newname for datafile 17 to
"/u01/lun0/hanfa2/disco01.dbf";
set newname for datafile 18 to
"/u01/lun0/hanfa2/disco02.dbf";
set newname for datafile 19 to
"/u01/lun0/hanfa2/disco03.dbf";
set newname for datafile 20 to
"/u01/lun0/hanfa2/a_conv01.dbf";
set newname for datafile 21 to
"/u01/lun0/hanfa2/a_conv02.dbf";
set newname for datafile 22 to
"/u01/lun0/hanfa2/a_conv03.dbf";
set newname for datafile 23 to
"/u01/lun0/hanfa2/a_conv04.dbf";
set newname for datafile 24 to
"/u01/lun0/hanfa2/a_int02.dbf";
set newname for datafile 25 to
"/u01/lun0/hanfa2/tools.dbf";
set newname for datafile 26 to
"/u01/lun0/hanfa2/a_txn_data04.dbf";
set newname for datafile 27 to
"/u01/lun0/hanfa2/a_txn_ind06.dbf";
set newname for datafile 28 to
"/u01/lun0/hanfa2/undo05.dbf";
set newname for datafile 29 to
"/u01/lun0/hanfa2/undo04.dbf";
set newname for datafile 30 to
"/u01/lun0/hanfa2/undo03.dbf";
set newname for datafile 31 to
"/u01/lun0/hanfa2/undo02.dbf";
set newname for datafile 32 to
"/u01/lun0/hanfa2/undo01.dbf";
set newname for datafile 33 to
"/u01/lun0/hanfa2/a_ts_mview03.dbf";
set newname for datafile 34 to
"/u01/lun0/hanfa2/a_ts_mview02.dbf";
set newname for datafile 35 to
"/u01/lun0/hanfa2/a_ts_mview01.dbf";
set newname for datafile 36 to
"/u01/lun0/hanfa2/foglight_ts.dbf";
set newname for datafile 37 to
"/u01/lun0/hanfa2/a_txn_data05.dbf";
set newname for datafile 38 to
"/u01/lun0/hanfa2/a_txn_data06.dbf";
set newname for datafile 39 to
"/u01/lun0/hanfa2/a_txn_data07.dbf";
set newname for datafile 40 to
"/u01/lun0/hanfa2/a_txn_ind07.dbf";
set newname for datafile 41 to
"/u01/lun0/hanfa2/a_txn_ind08.dbf";
set newname for datafile 42 to
"/u01/lun0/hanfa2/dwh01.dbf";
set newname for datafile 43 to
"/u01/lun0/hanfa2/dwh02.dbf";
set newname for datafile 288 to
"/u01/lun0/hanfa2/system10.dbf";
set newname for datafile 295 to
"/u01/lun0/hanfa2/system06.dbf";
set newname for datafile 314 to
"/u01/lun0/hanfa2/portal01.dbf";
set newname for datafile 351 to
"/u01/lun0/hanfa2/system07.dbf";
set newname for datafile 352 to
"/u01/lun0/hanfa2/system09.dbf";
set newname for datafile 353 to
"/u01/lun0/hanfa2/system08.dbf";
set newname for datafile 354 to
"/u01/lun0/hanfa2/system11.dbf";
set newname for datafile 392 to
"/u01/lun0/hanfa2/a_txn_data01.dbf";
set newname for datafile 393 to
"/u01/lun0/hanfa2/a_txn_ind01.dbf";
set newname for datafile 394 to
"/u01/lun0/hanfa2/a_ref01.dbf";
set newname for datafile 395 to
"/u01/lun0/hanfa2/a_int01.dbf";
set newname for datafile 396 to
"/u01/lun0/hanfa2/a_summ01.dbf";
set newname for datafile 397 to
"/u01/lun0/hanfa2/a_nolog01.dbf";
set newname for datafile 398 to
"/u01/lun0/hanfa2/a_archive01.dbf";
set newname for datafile 399 to
"/u01/lun0/hanfa2/a_queue01.dbf";
set newname for datafile 400 to
"/u01/lun0/hanfa2/a_media01.dbf";
set newname for datafile 401 to
"/u01/lun0/hanfa2/a_txn_data02.dbf";
set newname for datafile 402 to
"/u01/lun0/hanfa2/a_txn_data03.dbf";
set newname for datafile 403 to
"/u01/lun0/hanfa2/a_txn_ind02.dbf";
set newname for datafile 404 to
"/u01/lun0/hanfa2/a_txn_ind03.dbf";
set newname for datafile 405 to
"/u01/lun0/hanfa2/a_txn_ind04.dbf";
set newname for datafile 406 to
"/u01/lun0/hanfa2/a_txn_ind05.dbf";
set newname for datafile 407 to
"/u01/lun0/hanfa2/a_ref02.dbf";
restore
check readonly
clone database
executing Memory Script
executing command: SET until clause
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting restore at 25-MAR-08
channel aux2: starting datafile backupset restore
channel aux2: specifying datafile(s) to restore from backup set
restoring datafile 00024 to /u01/lun0/hanfa2/a_int02.dbf
restoring datafile 00402 to /u01/lun0/hanfa2/a_txn_data03.dbf
channel aux2: reading from backup piece /full_PROD_s7jc4d6g_1_1/
channel aux1: starting datafile backupset restore
channel aux1: specifying datafile(s) to restore from backup set
restoring datafile 00395 to /u01/lun0/hanfa2/a_int01.dbf
restoring datafile 00404 to /u01/lun0/hanfa2/a_txn_ind03.dbf
channel aux1: reading from backup piece /full_PROD_s8jc4d6g_1_1/
channel aux1: restored backup piece 1
piece handle=/full_PROD_s8jc4d6g_1_1/ tag=TAG20080325T041511
channel aux1: restore complete, elapsed time: 00:48:09
channel aux1: starting datafile backupset restore
channel aux1: specifying datafile(s) to restore from backup set
restoring datafile 00026 to /u01/lun0/hanfa2/a_txn_data04.dbf
restoring datafile 00030 to /u01/lun0/hanfa2/undo03.dbf
channel aux1: reading from backup piece /full_PROD_s9jc4ene_1_1/
channel aux2: restored backup piece 1
piece handle=/full_PROD_s7jc4d6g_1_1/ tag=TAG20080325T041511
channel aux2: restore complete, elapsed time: 00:59:15
channel aux2: starting datafile backupset restore
channel aux2: specifying datafile(s) to restore from backup set
restoring datafile 00027 to /u01/lun0/hanfa2/a_txn_ind06.dbf
restoring datafile 00401 to /u01/lun0/hanfa2/a_txn_data02.dbf
channel aux2: reading from backup piece /full_PROD_sajc4evd_1_1/
channel aux1: restored backup piece 1
piece handle=/full_PROD_s9jc4ene_1_1/ tag=TAG20080325T041511
channel aux1: restore complete, elapsed time: 00:25:44
channel aux1: starting datafile backupset restore
channel aux1: specifying datafile(s) to restore from backup set
restoring datafile 00031 to /u01/lun0/hanfa2/undo02.dbf
restoring datafile 00397 to /u01/lun0/hanfa2/a_nolog01.dbf
channel aux1: reading from backup piece /full_PROD_sbjc4fbo_1_1/
channel aux2: restored backup piece 1
piece handle=/full_PROD_sajc4evd_1_1/ tag=TAG20080325T041511
channel aux2: restore complete, elapsed time: 00:26:55
channel aux2: starting datafile backupset restore
channel aux2: specifying datafile(s) to restore from backup set
restoring datafile 00039 to /u01/lun0/hanfa2/a_txn_data07.dbf
restoring datafile 00403 to /u01/lun0/hanfa2/a_txn_ind02.dbf
channel aux2: reading from backup piece /full_PROD_scjc4fkl_1_1/
channel aux1: restored backup piece 1
piece handle=/full_PROD_sbjc4fbo_1_1/ tag=TAG20080325T041511
channel aux1: restore complete, elapsed time: 00:26:14
channel aux1: starting datafile backupset restore
channel aux1: specifying datafile(s) to restore from backup set
restoring datafile 00025 to /u01/lun0/hanfa2/tools.dbf
restoring datafile 00037 to /u01/lun0/hanfa2/a_txn_data05.dbf
channel aux1: reading from backup piece /full_PROD_sdjc4g03_1_1/
channel aux2: restored backup piece 1
piece handle=/full_PROD_scjc4fkl_1_1/ tag=TAG20080325T041511
channel aux2: restore complete, elapsed time: 00:21:14
channel aux2: starting datafile backupset restore
channel aux2: specifying datafile(s) to restore from backup set
restoring datafile 00028 to /u01/lun0/hanfa2/undo05.dbf
restoring datafile 00393 to /u01/lun0/hanfa2/a_txn_ind01.dbf
channel aux2: reading from backup piece /full_PROD_sejc4g5i_1_1/
channel aux1: restored backup piece 1
piece handle=/full_PROD_sdjc4g03_1_1/ tag=TAG20080325T041511
channel aux1: restore complete, elapsed time: 00:22:02
channel aux1: starting datafile backupset restore
channel aux1: specifying datafile(s) to restore from backup set
restoring datafile 00032 to /u01/lun0/hanfa2/undo01.dbf
restoring datafile 00038 to /u01/lun0/hanfa2/a_txn_data06.dbf
channel aux1: reading from backup piece /full_PROD_sfjc4gf3_1_1/
channel aux2: restored backup piece 1
piece handle=/full_PROD_sejc4g5i_1_1/ tag=TAG20080325T041511
channel aux2: restore complete, elapsed time: 00:23:13
channel aux2: starting datafile backupset restore
channel aux2: specifying datafile(s) to restore from backup set
restoring datafile 00352 to /u01/lun0/hanfa2/system09.dbf
restoring datafile 00392 to /u01/lun0/hanfa2/a_txn_data01.dbf
channel aux2: reading from backup piece /full_PROD_sgjc4gkj_1_1/
channel aux1: restored backup piece 1
piece handle=/full_PROD_sfjc4gf3_1_1/ tag=TAG20080325T041511
channel aux1: restore complete, elapsed time: 00:21:12
channel aux1: starting datafile backupset restore
channel aux1: specifying datafile(s) to restore from backup set
restoring datafile 00400 to /u01/lun0/hanfa2/a_media01.dbf
restoring datafile 00405 to /u01/lun0/hanfa2/a_txn_ind04.dbf
channel aux1: reading from backup piece /full_PROD_shjc4gtq_1_1/
channel aux2: restored backup piece 1
piece handle=/full_PROD_sgjc4gkj_1_1/ tag=TAG20080325T041511
channel aux2: restore complete, elapsed time: 00:16:32
channel aux2: starting datafile backupset restore
channel aux2: specifying datafile(s) to restore from backup set
restoring datafile 00033 to /u01/lun0/hanfa2/a_ts_mview03.dbf
restoring datafile 00406 to /u01/lun0/hanfa2/a_txn_ind05.dbf
channel aux2: reading from backup piece /full_PROD_sijc4h14_1_1/
channel aux1: restored backup piece 1
piece handle=/full_PROD_shjc4gtq_1_1/ tag=TAG20080325T041511
channel aux1: restore complete, elapsed time: 00:15:51
channel aux1: starting datafile backupset restore
channel aux1: specifying datafile(s) to restore from backup set
restoring datafile 00022 to /u01/lun0/hanfa2/a_conv03.dbf
restoring datafile 00029 to /u01/lun0/hanfa2/undo04.dbf
channel aux1: reading from backup piece /full_PROD_skjc4hcm_1_1/
channel aux2: restored backup piece 1
piece handle=/full_PROD_sijc4h14_1_1/ tag=TAG20080325T041511
channel aux2: restore complete, elapsed time: 00:13:42
channel aux2: starting datafile backupset restore
channel aux2: specifying datafile(s) to restore from backup set
restoring datafile 00035 to /u01/lun0/hanfa2/a_ts_mview01.dbf
restoring datafile 00041 to /u01/lun0/hanfa2/a_txn_ind08.dbf
channel aux2: reading from backup piece /full_PROD_sjjc4h9n_1_1/
channel aux1: restored backup piece 1
piece handle=/full_PROD_skjc4hcm_1_1/ tag=TAG20080325T041511
channel aux1: restore complete, elapsed time: 00:12:13
channel aux1: starting datafile backupset restore
channel aux1: specifying datafile(s) to restore from backup set
restoring datafile 00040 to /u01/lun0/hanfa2/a_txn_ind07.dbf
restoring datafile 00353 to /u01/lun0/hanfa2/system08.dbf
channel aux1: reading from backup piece /full_PROD_sljc4hjo_1_1/
channel aux2: restored backup piece 1
piece handle=/full_PROD_sjjc4h9n_1_1/ tag=TAG20080325T041511
channel aux2: restore complete, elapsed time: 00:12:53
channel aux2: starting datafile backupset restore
channel aux2: specifying datafile(s) to restore from backup set
restoring datafile 00001 to /u01/lun0/hanfa2/system01.dbf
restoring datafile 00034 to /u01/lun0/hanfa2/a_ts_mview02.dbf
channel aux2: reading from backup piece /full_PROD_smjc4hkr_1_1/
channel aux1: restored backup piece 1
piece handle=/full_PROD_sljc4hjo_1_1/ tag=TAG20080325T041511
channel aux1: restore complete, elapsed time: 00:10:21
channel aux1: starting datafile backupset restore
channel aux1: specifying datafile(s) to restore from backup set
restoring datafile 00396 to /u01/lun0/hanfa2/a_summ01.dbf
restoring datafile 00399 to /u01/lun0/hanfa2/a_queue01.dbf
channel aux1: reading from backup piece /full_PROD_sojc4hrb_1_1/
channel aux2: restored backup piece 1
piece handle=/full_PROD_smjc4hkr_1_1/ tag=TAG20080325T041511
channel aux2: restore complete, elapsed time: 00:08:08
channel aux2: starting datafile backupset restore
channel aux2: specifying datafile(s) to restore from backup set
restoring datafile 00016 to /u01/lun0/hanfa2/undo06.dbf
restoring datafile 00023 to /u01/lun0/hanfa2/a_conv04.dbf
channel aux2: reading from backup piece /full_PROD_snjc4hr8_1_1/
channel aux1: restored backup piece 1
piece handle=/full_PROD_sojc4hrb_1_1/ tag=TAG20080325T041511
channel aux1: restore complete, elapsed time: 00:06:39
channel aux1: starting datafile backupset restore
channel aux1: specifying datafile(s) to restore from backup set
restoring datafile 00014 to /u01/lun0/hanfa2/sysaux01.dbf
restoring datafile 00015 to /u01/lun0/hanfa2/system12.dbf
channel aux1: reading from backup piece /full_PROD_sqjc4i1a_1_1/
channel aux2: restored backup piece 1
piece handle=/full_PROD_snjc4hr8_1_1/ tag=TAG20080325T041511
channel aux2: restore complete, elapsed time: 00:07:21
channel aux2: starting datafile backupset restore
channel aux2: specifying datafile(s) to restore from backup set
restoring datafile 00008 to /u01/lun0/hanfa2/a_queue02.dbf
restoring datafile 00394 to /u01/lun0/hanfa2/a_ref01.dbf
channel aux2: reading from backup piece /full_PROD_srjc4i49_1_1/
channel aux1: restored backup piece 1
piece handle=/full_PROD_sqjc4i1a_1_1/ tag=TAG20080325T041511
channel aux1: restore complete, elapsed time: 00:02:30
channel aux1: starting datafile backupset restore
channel aux1: specifying datafile(s) to restore from backup set
restoring datafile 00398 to /u01/lun0/hanfa2/a_archive01.dbf
restoring datafile 00407 to /u01/lun0/hanfa2/a_ref02.dbf
channel aux1: reading from backup piece /full_PROD_ssjc4i7s_1_1/
channel aux2: restored backup piece 1
piece handle=/full_PROD_srjc4i49_1_1/ tag=TAG20080325T041511
channel aux2: restore complete, elapsed time: 00:04:01
channel aux2: starting datafile backupset restore
channel aux2: specifying datafile(s) to restore from backup set
restoring datafile 00295 to /u01/lun0/hanfa2/system06.dbf
restoring datafile 00351 to /u01/lun0/hanfa2/system07.dbf
channel aux2: reading from backup piece /full_PROD_stjc4ia7_1_1/
channel aux1: restored backup piece 1
piece handle=/full_PROD_ssjc4i7s_1_1/ tag=TAG20080325T041511
channel aux1: restore complete, elapsed time: 00:03:51
channel aux1: starting datafile backupset restore
channel aux1: specifying datafile(s) to restore from backup set
restoring datafile 00042 to /u01/lun0/hanfa2/dwh01.dbf
channel aux1: reading from backup piece /full_PROD_spjc4huk_1_1/
channel aux2: restored backup piece 1
piece handle=/full_PROD_stjc4ia7_1_1/ tag=TAG20080325T041511
channel aux2: restore complete, elapsed time: 00:11:11
channel aux2: starting datafile backupset restore
channel aux2: specifying datafile(s) to restore from backup set
restoring datafile 00002 to /u01/lun0/hanfa2/system02.dbf
restoring datafile 00003 to /u01/lun0/hanfa2/system03.dbf
channel aux2: reading from backup piece /full_PROD_sujc4ics_1_1/
channel aux1: restored backup piece 1
piece handle=/full_PROD_spjc4huk_1_1/ tag=TAG20080325T041511
channel aux1: restore complete, elapsed time: 00:13:32
channel aux2: restored backup piece 1
piece handle=/full_PROD_sujc4ics_1_1/ tag=TAG20080325T041511
channel aux2: restore complete, elapsed time: 00:03:56
channel aux1: starting datafile backupset restore
channel aux1: specifying datafile(s) to restore from backup set
restoring datafile 00288 to /u01/lun0/hanfa2/system10.dbf
restoring datafile 00354 to /u01/lun0/hanfa2/system11.dbf
channel aux1: reading from backup piece /full_PROD_t0jc4if5_1_1/
channel aux2: starting datafile backupset restore
channel aux2: specifying datafile(s) to restore from backup set
restoring datafile 00004 to /u01/lun0/hanfa2/system04.dbf
restoring datafile 00005 to /u01/lun0/hanfa2/system05.dbf
channel aux2: reading from backup piece /full_PROD_svjc4ieu_1_1/
channel aux1: restored backup piece 1
piece handle=/full_PROD_t0jc4if5_1_1/ tag=TAG20080325T041511
channel aux1: restore complete, elapsed time: 00:04:46
channel aux2: restored backup piece 1
piece handle=/full_PROD_svjc4ieu_1_1/ tag=TAG20080325T041511
channel aux2: restore complete, elapsed time: 00:04:46
channel aux1: starting datafile backupset restore
channel aux1: specifying datafile(s) to restore from backup set
restoring datafile 00020 to /u01/lun0/hanfa2/a_conv01.dbf
restoring datafile 00021 to /u01/lun0/hanfa2/a_conv02.dbf
channel aux1: reading from backup piece /full_PROD_t1jc4ihg_1_1/
channel aux2: starting datafile backupset restore
channel aux2: specifying datafile(s) to restore from backup set
restoring datafile 00006 to /u01/lun0/hanfa2/ctxd01.dbf
restoring datafile 00036 to /u01/lun0/hanfa2/foglight_ts.dbf
channel aux2: reading from backup piece /full_PROD_t3jc4iiu_1_1/
channel aux1: restored backup piece 1
piece handle=/full_PROD_t1jc4ihg_1_1/ tag=TAG20080325T041511
channel aux1: restore complete, elapsed time: 00:01:45
channel aux1: starting datafile backupset restore
channel aux1: specifying datafile(s) to restore from backup set
restoring datafile 00013 to /u01/lun0/hanfa2/xxcounter01.dbf
restoring datafile 00018 to /u01/lun0/hanfa2/disco02.dbf
channel aux1: reading from backup piece /full_PROD_t4jc4ijd_1_1/
channel aux2: restored backup piece 1
piece handle=/full_PROD_t3jc4iiu_1_1/ tag=TAG20080325T041511
channel aux2: restore complete, elapsed time: 00:01:46
channel aux2: starting datafile backupset restore
channel aux2: specifying datafile(s) to restore from backup set
restoring datafile 00043 to /u01/lun0/hanfa2/dwh02.dbf
channel aux2: reading from backup piece /full_PROD_t2jc4ihh_1_1/
channel aux1: restored backup piece 1
piece handle=/full_PROD_t4jc4ijd_1_1/ tag=TAG20080325T041511
channel aux1: restore complete, elapsed time: 00:00:36
channel aux1: starting datafile backupset restore
channel aux1: specifying datafile(s) to restore from backup set
restoring datafile 00009 to /u01/lun0/hanfa2/odm.dbf
restoring datafile 00314 to /u01/lun0/hanfa2/portal01.dbf
channel aux1: reading from backup piece /full_PROD_t6jc4ijs_1_1/
channel aux1: restored backup piece 1
piece handle=/full_PROD_t6jc4ijs_1_1/ tag=TAG20080325T041511
channel aux1: restore complete, elapsed time: 00:01:16
channel aux2: restored backup piece 1
piece handle=/full_PROD_t2jc4ihh_1_1/ tag=TAG20080325T041511
channel aux2: restore complete, elapsed time: 00:01:51
channel aux1: starting datafile backupset restore
channel aux1: specifying datafile(s) to restore from backup set
restoring datafile 00017 to /u01/lun0/hanfa2/disco01.dbf
restoring datafile 00019 to /u01/lun0/hanfa2/disco03.dbf
channel aux1: reading from backup piece /full_PROD_t5jc4ijs_1_1/
channel aux2: starting datafile backupset restore
channel aux2: specifying datafile(s) to restore from backup set
restoring datafile 00011 to /u01/lun0/hanfa2/xxcounter03.dbf
restoring datafile 00012 to /u01/lun0/hanfa2/xxcounter02.dbf
channel aux2: reading from backup piece /full_PROD_t7jc4ik0_1_1/
channel aux1: restored backup piece 1
piece handle=/full_PROD_t5jc4ijs_1_1/ tag=TAG20080325T041511
channel aux1: restore complete, elapsed time: 00:00:55
channel aux2: restored backup piece 1
piece handle=/full_PROD_t7jc4ik0_1_1/ tag=TAG20080325T041511
channel aux2: restore complete, elapsed time: 00:00:55
channel aux1: starting datafile backupset restore
channel aux1: specifying datafile(s) to restore from backup set
restoring datafile 00007 to /u01/lun0/hanfa2/owad01.dbf
restoring datafile 00010 to /u01/lun0/hanfa2/olap.dbf
channel aux1: reading from backup piece /full_PROD_t8jc4ik0_1_1/
channel aux1: restored backup piece 1
piece handle=/full_PROD_t8jc4ik0_1_1/ tag=TAG20080325T041511
channel aux1: restore complete, elapsed time: 00:00:45
Finished restore at 25-MAR-08
sql statement: CREATE CONTROLFILE REUSE SET DATABASE "HANFA2" RESETLOGS ARCHIVELOG
MAXLOGFILES 32
MAXLOGMEMBERS 5
MAXDATAFILES 512
MAXINSTANCES 8
MAXLOGHISTORY 7303
LOGFILE
GROUP 1 ( '/u01/lun0/hanfa2/log1a.dbf', '/u01/lun0/hanfa2/log1b.dbf' ) SIZE 100 M ,
GROUP 2 ( '/u01/lun0/hanfa2/log2a.dbf', '/u01/lun0/hanfa2/log2b.dbf' ) SIZE 100 M ,
GROUP 3 ( '/u01/lun0/hanfa2/log3a.dbf', '/u01/lun0/hanfa2/log3b.dbf' ) SIZE 100 M ,
GROUP 4 ( '/u01/lun0/hanfa2/log4a.dbf', '/u01/lun0/hanfa2/log4b.dbf' ) SIZE 100 M ,
GROUP 5 ( '/u01/lun0/hanfa2/log5a.dbf', '/u01/lun0/hanfa2/log5b.dbf' ) SIZE 100 M REUSE
DATAFILE
'/u01/lun0/hanfa2/system01.dbf'
CHARACTER SET UTF8
contents of Memory Script:
switch clone datafile all;
executing Memory Script
datafile 2 switched to datafile copy
input datafile copy recid=1 stamp=650311810 filename=/u01/lun0/hanfa2/system02.dbf
datafile 3 switched to datafile copy
input datafile copy recid=2 stamp=650311810 filename=/u01/lun0/hanfa2/system03.dbf
datafile 4 switched to datafile copy
input datafile copy recid=3 stamp=650311810 filename=/u01/lun0/hanfa2/system04.dbf
datafile 5 switched to datafile copy
input datafile copy recid=4 stamp=650311810 filename=/u01/lun0/hanfa2/system05.dbf
datafile 6 switched to datafile copy
input datafile copy recid=5 stamp=650311810 filename=/u01/lun0/hanfa2/ctxd01.dbf
datafile 7 switched to datafile copy
input datafile copy recid=6 stamp=650311810 filename=/u01/lun0/hanfa2/owad01.dbf
datafile 8 switched to datafile copy
input datafile copy recid=7 stamp=650311810 filename=/u01/lun0/hanfa2/a_queue02.dbf
datafile 9 switched to datafile copy
input datafile copy recid=8 stamp=650311810 filename=/u01/lun0/hanfa2/odm.dbf
datafile 10 switched to datafile copy
input datafile copy recid=9 stamp=650311810 filename=/u01/lun0/hanfa2/olap.dbf
datafile 11 switched to datafile copy
input datafile copy recid=10 stamp=650311810 filename=/u01/lun0/hanfa2/xxcounter03.dbf
datafile 12 switched to datafile copy
input datafile copy recid=11 stamp=650311810 filename=/u01/lun0/hanfa2/xxcounter02.dbf
datafile 13 switched to datafile copy
input datafile copy recid=12 stamp=650311810 filename=/u01/lun0/hanfa2/xxcounter01.dbf
datafile 14 switched to datafile copy
input datafile copy recid=13 stamp=650311810 filename=/u01/lun0/hanfa2/sysaux01.dbf
datafile 15 switched to datafile copy
input datafile copy recid=14 stamp=650311810 filename=/u01/lun0/hanfa2/system12.dbf
datafile 16 switched to datafile copy
input datafile copy recid=15 stamp=650311810 filename=/u01/lun0/hanfa2/undo06.dbf
datafile 17 switched to datafile copy
input datafile copy recid=16 stamp=650311810 filename=/u01/lun0/hanfa2/disco01.dbf
datafile 18 switched to datafile copy
input datafile copy recid=17 stamp=650311810 filename=/u01/lun0/hanfa2/disco02.dbf
datafile 19 switched to datafile copy
input datafile copy recid=18 stamp=650311810 filename=/u01/lun0/hanfa2/disco03.dbf
datafile 20 switched to datafile copy
input datafile copy recid=19 stamp=650311810 filename=/u01/lun0/hanfa2/a_conv01.dbf
datafile 21 switched to datafile copy
input datafile copy recid=20 stamp=650311810 filename=/u01/lun0/hanfa2/a_conv02.dbf
datafile 22 switched to datafile copy
input datafile copy recid=21 stamp=650311810 filename=/u01/lun0/hanfa2/a_conv03.dbf
datafile 23 switched to datafile copy
input datafile copy recid=22 stamp=650311810 filename=/u01/lun0/hanfa2/a_conv04.dbf
datafile 24 switched to datafile copy
input datafile copy recid=23 stamp=650311810 filename=/u01/lun0/hanfa2/a_int02.dbf
datafile 25 switched to datafile copy
input datafile copy recid=24 stamp=650311810 filename=/u01/lun0/hanfa2/tools.dbf
datafile 26 switched to datafile copy
input datafile copy recid=25 stamp=650311810 filename=/u01/lun0/hanfa2/a_txn_data04.dbf
datafile 27 switched to datafile copy
input datafile copy recid=26 stamp=650311810 filename=/u01/lun0/hanfa2/a_txn_ind06.dbf
datafile 28 switched to datafile copy
input datafile copy recid=27 stamp=650311810 filename=/u01/lun0/hanfa2/undo05.dbf
datafile 29 switched to datafile copy
input datafile copy recid=28 stamp=650311810 filename=/u01/lun0/hanfa2/undo04.dbf
datafile 30 switched to datafile copy
input datafile copy recid=29 stamp=650311810 filename=/u01/lun0/hanfa2/undo03.dbf
datafile 31 switched to datafile copy
input datafile copy recid=30 stamp=650311810 filename=/u01/lun0/hanfa2/undo02.dbf
datafile 32 switched to datafile copy
input datafile copy recid=31 stamp=650311810 filename=/u01/lun0/hanfa2/undo01.dbf
datafile 33 switched to datafile copy
input datafile copy recid=32 stamp=650311810 filename=/u01/lun0/hanfa2/a_ts_mview03.dbf
datafile 34 switched to datafile copy
input datafile copy recid=33 stamp=650311810 filename=/u01/lun0/hanfa2/a_ts_mview02.dbf
datafile 35 switched to datafile copy
input datafile copy recid=34 stamp=650311810 filename=/u01/lun0/hanfa2/a_ts_mview01.dbf
datafile 36 switched to datafile copy
input datafile copy recid=35 stamp=650311810 filename=/u01/lun0/hanfa2/foglight_ts.dbf
datafile 37 switched to datafile copy
input datafile copy recid=36 stamp=650311810 filename=/u01/lun0/hanfa2/a_txn_data05.dbf
datafile 38 switched to datafile copy
input datafile copy recid=37 stamp=650311810 filename=/u01/lun0/hanfa2/a_txn_data06.dbf
datafile 39 switched to datafile copy
input datafile copy recid=38 stamp=650311810 filename=/u01/lun0/hanfa2/a_txn_data07.dbf
datafile 40 switched to datafile copy
input datafile copy recid=39 stamp=650311810 filename=/u01/lun0/hanfa2/a_txn_ind07.dbf
datafile 41 switched to datafile copy
input datafile copy recid=40 stamp=650311810 filename=/u01/lun0/hanfa2/a_txn_ind08.dbf
datafile 42 switched to datafile copy
input datafile copy recid=41 stamp=650311810 filename=/u01/lun0/hanfa2/dwh01.dbf
datafile 43 switched to datafile copy
input datafile copy recid=42 stamp=650311810 filename=/u01/lun0/hanfa2/dwh02.dbf
datafile 288 switched to datafile copy
input datafile copy recid=43 stamp=650311810 filename=/u01/lun0/hanfa2/system10.dbf
datafile 295 switched to datafile copy
input datafile copy recid=44 stamp=650311810 filename=/u01/lun0/hanfa2/system06.dbf
datafile 314 switched to datafile copy
input datafile copy recid=45 stamp=650311810 filename=/u01/lun0/hanfa2/portal01.dbf
datafile 351 switched to datafile copy
input datafile copy recid=46 stamp=650311810 filename=/u01/lun0/hanfa2/system07.dbf
datafile 352 switched to datafile copy
input datafile copy recid=47 stamp=650311811 filename=/u01/lun0/hanfa2/system09.dbf
datafile 353 switched to datafile copy
input datafile copy recid=48 stamp=650311811 filename=/u01/lun0/hanfa2/system08.dbf
datafile 354 switched to datafile copy
input datafile copy recid=49 stamp=650311811 filename=/u01/lun0/hanfa2/system11.dbf
datafile 392 switched to datafile copy
input datafile copy recid=50 stamp=650311811 filename=/u01/lun0/hanfa2/a_txn_data01.dbf
datafile 393 switched to datafile copy
input datafile copy recid=51 stamp=650311811 filename=/u01/lun0/hanfa2/a_txn_ind01.dbf
datafile 394 switched to datafile copy
input datafile copy recid=52 stamp=650311811 filename=/u01/lun0/hanfa2/a_ref01.dbf
datafile 395 switched to datafile copy
input datafile copy recid=53 stamp=650311811 filename=/u01/lun0/hanfa2/a_int01.dbf
datafile 396 switched to datafile copy
input datafile copy recid=54 stamp=650311811 filename=/u01/lun0/hanfa2/a_summ01.dbf
datafile 397 switched to datafile copy
input datafile copy recid=55 stamp=650311811 filename=/u01/lun0/hanfa2/a_nolog01.dbf
datafile 398 switched to datafile copy
input datafile copy recid=56 stamp=650311811 filename=/u01/lun0/hanfa2/a_archive01.dbf
datafile 399 switched to datafile copy
input datafile copy recid=57 stamp=650311811 filename=/u01/lun0/hanfa2/a_queue01.dbf
datafile 400 switched to datafile copy
input datafile copy recid=58 stamp=650311811 filename=/u01/lun0/hanfa2/a_media01.dbf
datafile 401 switched to datafile copy
input datafile copy recid=59 stamp=650311811 filename=/u01/lun0/hanfa2/a_txn_data02.dbf
datafile 402 switched to datafile copy
input datafile copy recid=60 stamp=650311811 filename=/u01/lun0/hanfa2/a_txn_data03.dbf
datafile 403 switched to datafile copy
input datafile copy recid=61 stamp=650311811 filename=/u01/lun0/hanfa2/a_txn_ind02.dbf
datafile 404 switched to datafile copy
input datafile copy recid=62 stamp=650311811 filename=/u01/lun0/hanfa2/a_txn_ind03.dbf
datafile 405 switched to datafile copy
input datafile copy recid=63 stamp=650311811 filename=/u01/lun0/hanfa2/a_txn_ind04.dbf
datafile 406 switched to datafile copy
input datafile copy recid=64 stamp=650311811 filename=/u01/lun0/hanfa2/a_txn_ind05.dbf
datafile 407 switched to datafile copy
input datafile copy recid=65 stamp=650311811 filename=/u01/lun0/hanfa2/a_ref02.dbf
contents of Memory Script:
set until time "to_date( '25.03.2008 08:00:00','dd.mm.yyyy hh24:mi:ss')";
recover
clone database
delete archivelog
executing Memory Script
executing command: SET until clause
Starting recover at 25-MAR-08
starting media recovery
channel aux1: starting archive log restore to default destination
channel aux1: restoring archive log
archive log thread=1 sequence=86375
channel aux1: restoring archive log
archive log thread=1 sequence=86376
channel aux1: restoring archive log
archive log thread=1 sequence=86377
channel aux1: restoring archive log
archive log thread=1 sequence=86378
channel aux1: restoring archive log
archive log thread=1 sequence=86379
channel aux1: restoring archive log
archive log thread=1 sequence=86380
channel aux1: restoring archive log
archive log thread=1 sequence=86381
channel aux1: restoring archive log
archive log thread=1 sequence=86382
channel aux1: restoring archive log
archive log thread=1 sequence=86383
channel aux1: restoring archive log
archive log thread=1 sequence=86384
channel aux1: restoring archive log
archive log thread=1 sequence=86385
channel aux1: restoring archive log
archive log thread=1 sequence=86386
channel aux1: restoring archive log
archive log thread=1 sequence=86387
channel aux1: restoring archive log
archive log thread=1 sequence=86388
channel aux1: restoring archive log
archive log thread=1 sequence=86389
channel aux1: restoring archive log
archive log thread=1 sequence=86390
channel aux1: restoring archive log
archive log thread=1 sequence=86391
channel aux1: restoring archive log
archive log thread=1 sequence=86392
channel aux1: restoring archive log
archive log thread=1 sequence=86393
channel aux1: restoring archive log
archive log thread=1 sequence=86394
channel aux1: restoring archive log
archive log thread=1 sequence=86395
channel aux1: restoring archive log
archive log thread=1 sequence=86396
channel aux1: restoring archive log
archive log thread=1 sequence=86397
channel aux1: restoring archive log
archive log thread=1 sequence=86398
channel aux1: reading from backup piece /arch1_PROD_tdjc4jd7/
channel aux1: restored backup piece 1
piece handle=/arch1_PROD_tdjc4jd7/ tag=TAG20080325T060110
channel aux1: restore complete, elapsed time: 00:07:36
channel aux1: starting archive log restore to default destination
channel aux1: restoring archive log
archive log thread=1 sequence=86356
channel aux1: restoring archive log
archive log thread=1 sequence=86357
channel aux1: restoring archive log
archive log thread=1 sequence=86358
channel aux1: restoring archive log
archive log thread=1 sequence=86359
channel aux1: restoring archive log
archive log thread=1 sequence=86360
channel aux1: restoring archive log
archive log thread=1 sequence=86361
channel aux1: restoring archive log
archive log thread=1 sequence=86362
channel aux1: restoring archive log
archive log thread=1 sequence=86363
channel aux1: restoring archive log
archive log thread=1 sequence=86364
channel aux1: restoring archive log
archive log thread=1 sequence=86365
channel aux1: restoring archive log
archive log thread=1 sequence=86366
channel aux1: restoring archive log
archive log thread=1 sequence=86367
channel aux1: restoring archive log
archive log thread=1 sequence=86368
channel aux1: restoring archive log
archive log thread=1 sequence=86369
channel aux1: restoring archive log
archive log thread=1 sequence=86370
channel aux1: restoring archive log
archive log thread=1 sequence=86371
channel aux1: restoring archive log
archive log thread=1 sequence=86372
channel aux1: restoring archive log
archive log thread=1 sequence=86373
channel aux1: restoring archive log
archive log thread=1 sequence=86374
channel aux1: reading from backup piece /arch1_PROD_tcjc4jd7/
ORA-19870: error reading backup piece /arch1_PROD_tcjc4jd7/
ORA-19510: failed to set size of 182123 blocks for file "/u01/lun0/hanfa2/arch/prodarch_23b63f7_1_625608313_86358.log" (blocksize=512)
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 9
channel aux1: starting archive log restore to default destination
channel aux1: restoring archive log
archive log thread=1 sequence=86399
channel aux1: restoring archive log
archive log thread=1 sequence=86400
channel aux1: restoring archive log
archive log thread=1 sequence=86401
channel aux1: restoring archive log
archive log thread=1 sequence=86402
channel aux1: restoring archive log
archive log thread=1 sequence=86403
channel aux1: restoring archive log
archive log thread=1 sequence=86404
channel aux1: reading from backup piece /arch1_PROD_tgjc4qf4/
channel aux2: starting archive log restore to default destination
channel aux2: restoring archive log
archive log thread=1 sequence=86356
channel aux2: restoring archive log
archive log thread=1 sequence=86357
channel aux2: restoring archive log
archive log thread=1 sequence=86358
channel aux2: restoring archive log
archive log thread=1 sequence=86359
channel aux2: restoring archive log
archive log thread=1 sequence=86360
channel aux2: restoring archive log
archive log thread=1 sequence=86361
channel aux2: restoring archive log
archive log thread=1 sequence=86363
channel aux2: restoring archive log
archive log thread=1 sequence=86364
channel aux2: restoring archive log
archive log thread=1 sequence=86365
channel aux2: restoring archive log
archive log thread=1 sequence=86366
channel aux2: restoring archive log
archive log thread=1 sequence=86367
channel aux2: restoring archive log
archive log thread=1 sequence=86368
channel aux2: restoring archive log
archive log thread=1 sequence=86369
channel aux2: restoring archive log
archive log thread=1 sequence=86370
channel aux2: restoring archive log
archive log thread=1 sequence=86371
channel aux2: restoring archive log
archive log thread=1 sequence=86372
channel aux2: restoring archive log
archive log thread=1 sequence=86373
channel aux2: restoring archive log
archive log thread=1 sequence=86374
channel aux2: reading from backup piece /arch1_PROD_t9jc4iki/
channel aux1: restored backup piece 1
piece handle=/arch1_PROD_tgjc4qf4/ tag=TAG20080325T080139
channel aux1: restore complete, elapsed time: 00:01:56
channel aux1: starting archive log restore to default destination
channel aux1: restoring archive log
archive log thread=1 sequence=86405
channel aux1: restoring archive log
archive log thread=1 sequence=86406
channel aux1: restoring archive log
archive log thread=1 sequence=86407
channel aux1: restoring archive log
archive log thread=1 sequence=86408
channel aux1: reading from backup piece /arch1_PROD_tfjc4qf4/
channel aux1: restored backup piece 1
piece handle=/arch1_PROD_tfjc4qf4/ tag=TAG20080325T080139
channel aux1: restore complete, elapsed time: 00:02:05
channel aux1: starting archive log restore to default destination
channel aux1: restoring archive log
archive log thread=1 sequence=86409
channel aux1: reading from backup piece /arch1_PROD_tkjc51fm/
channel aux1: restored backup piece 1
piece handle=/arch1_PROD_tkjc51fm/ tag=TAG20080325T100124
channel aux1: restore complete, elapsed time: 00:02:15
channel aux2: restored backup piece 1
piece handle=/arch1_PROD_t9jc4iki/ tag=TAG20080325T054759
channel aux2: restore complete, elapsed time: 00:12:10
archive log filename=/u01/lun0/hanfa2/arch/prodarch_23b63f7_1_625608313_86356.log thread=1 sequence=86356
channel clone_default: deleting archive log(s)
archive log filename=/u01/lun0/hanfa2/arch/prodarch_23b63f7_1_625608313_86356.log recid=44 stamp=650313112
archive log filename=/u01/lun0/hanfa2/arch/prodarch_23b63f7_1_625608313_86357.log thread=1 sequence=86357
channel clone_default: deleting archive log(s)
archive log filename=/u01/lun0/hanfa2/arch/prodarch_23b63f7_1_625608313_86357.log recid=45 stamp=650313112
archive log filename=/u01/lun0/hanfa2/arch/prodarch_23b63f7_1_625608313_86358.log thread=1 sequence=86358
channel clone_default: deleting archive log(s)
archive log filename=/u01/lun0/hanfa2/arch/prodarch_23b63f7_1_625608313_86358.log recid=37 stamp=650313085
archive log filename=/u01/lun0/hanfa2/arch/prodarch_23b63f7_1_625608313_86359.log thread=1 sequence=86359
channel clone_default: deleting archive log(s)
archive log filename=/u01/lun0/hanfa2/arch/prodarch_23b63f7_1_625608313_86359.log recid=38 stamp=650313085
archive log filename=/u01/lun0/hanfa2/arch/prodarch_23b63f7_1_625608313_86360.log thread=1 sequence=86360
channel clone_default: deleting archive log(s)
archive log filename=/u01/lun0/hanfa2/arch/prodarch_23b63f7_1_625608313_86360.log recid=52 stamp=650313135
archive log filename=/u01/lun0/hanfa2/arch/prodarch_23b63f7_1_625608313_86361.log thread=1 sequence=86361
channel clone_default: deleting archive log(s)
archive log filename=/u01/lun0/hanfa2/arch/prodarch_23b63f7_1_625608313_86361.log recid=40 stamp=650313085
unable to find archive log
archive log thread=1 sequence=86362
Oracle Error:
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/u01/lun0/hanfa2/system01.dbf'
released channel: t1
released channel: aux1
released channel: aux2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 03/25/2008 18:32:26
RMAN-03015: error occurred in stored script Memory Script
RMAN-06055: could not find log sequence 86362 thread 1
Recovery Manager complete.Yes :-).
Also when i run recover database using backup controlfile;and try to apply redo logs i am getting:ORA-00309: log belongs to wrong database Do you have any advice on this ? -
In Noarchivelog mode "Thread 1 cannot allocate new log, sequence 3298"
Hi,My database mode is noarchivelog but i see my alert.log "Thread 1 cannot allocate new log, sequence 3298"
what it`s mean?
I have enough disk space.This is very similar to the your still open thread cannot allocate new log, sequence
Better protocol would surely be to acknowledge the references given then, and why you think they do or do not apply.
Please get one of these threads marked as answered and continue on the other.
Please also indicate:
1) is your database hung.
2) Output form this query:
select log_mode from v$database;
3) Database Version:
4) Are there any other messages in alert log.
5) In sqlplus connected as SYSDBA show output from
archive log list
Rgds - bigdelboy. -
Thread 1 cannot allocate new log, sequence 714 - Checkpoint not complete
I'm working in a Oracle 10g database, running on RHEL. The alert_*.log file is putting out this type of text for the past few months:
Thread 1 advanced to log sequence 713 (LGWR Switch)
Current log#2 seq# 713 mem# 0: /dbfiles/..../onlinelog/filename.log
Current log #2 ..........
Thread 1 cannot allocate new log, sequence 714
Checkpoint not complete
Any ideas to get me pointed in the right direction is appreciated,
Thank you in advance,
WesThe immediate fixes Vishal suggests are the standard answer, but there is more to it, as the MOS doc he references shows. Additional questions I would ask:
How long is the delay between the inability to switch and when it actually switches? How many datafiles do you have? What is waiting in the db?
In general, I find making log files sized for the rare massive updates, then using the built-in timeouts to switch every 20 or 30 minutes (depending on management recoverability expectations), helps avoid some of these problems. More specifically, run a statspack or awr (if licensed) report for maybe an hour during heavy times, and see what it thinks the waits are. Tuning is an iterative process, and sometimes different things can cause similar symptoms. Sometimes fixing the biggest problem (which is often poor SQL) can radically change the symptoms observed. Other times you find you have dying hardware, or someone messed up a switch configuration. -
Thread 1 cannot allocate new log, sequence in Alert log
Could someone help, I am getting the below message in my alert log
System: AIX6.1 - Oracle 11r2
GROUP# THREAD# MEMBER ARCHIVED STATUS MB
1 1 +DATA01/mydb/redolog_group1_member1 NO INACTIVE 1536
1 1 +DATA01/mydb/redolog_group1_member2 NO INACTIVE 1536
2 1 +DATA01/mydb/redolog_group2_member2 NO CURRENT 1536
2 1 +DATA01/mydb/redolog_group2_member1 NO CURRENT 1536
3 1 +DATA01/mydb/redolog_group3_member2 NO INACTIVE 1536
3 1 +DATA01/mydb/redolog_group3_member1 NO INACTIVE 1536
Tue Jul 10 18:37:48 2012
Thread 1 advanced to log sequence 28831 (LGWR switch)
Current log# 1 seq# 28831 mem# 0: +DATA01/mydb/redolog_group1_member1
Current log# 1 seq# 28831 mem# 1: +DATA01/mydb/redolog_group1_member2
Tue Jul 10 19:12:01 2012
Thread 1 advanced to log sequence 28832 (LGWR switch)
Current log# 2 seq# 28832 mem# 0: +DATA01/mydb/redolog_group2_member1
Current log# 2 seq# 28832 mem# 1: +DATA01/mydb/redolog_group2_member2
Tue Jul 10 19:39:00 2012
Thread 1 cannot allocate new log, sequence 28833
Private strand flush not complete
Tue Jul 10 19:39:18 2012
Current log# 2 seq# 28832 mem# 0: +DATA01/mydb/redolog_group2_member1
Current log# 2 seq# 28832 mem# 1: +DATA01/mydb/redolog_group2_member2
Tue Jul 10 19:41:21 2012
Thread 1 advanced to log sequence 28833 (LGWR switch)
Current log# 3 seq# 28833 mem# 0: +DATA01/mydb/redolog_group3_member1
Current log# 3 seq# 28833 mem# 1: +DATA01/mydb/redolog_group3_member2
Tue Jul 10 20:15:28 2012
Thread 1 cannot allocate new log, sequence 28834
Private strand flush not complete
Current log# 3 seq# 28833 mem# 0: +DATA01/mydb/redolog_group3_member1
Current log# 3 seq# 28833 mem# 1: +DATA01/mydb/redolog_group3_member2
Tue Jul 10 20:16:21 2012Could an increase on the redo log file sizes solve this problem? Unfortunately I do not have a test platform, where I could have tested this.mseberg wrote:
It just a warning. I would read these two notes:
I suspect the OP is more worried about the apparent two minute gap between the "cannot switch" and the "advanced" at 19:39:18 and 19:41:12 respectively. Did the switch really have to wait for that two minutes, or is this a spurious threat caused by an anomaly in the writing of the alert log.
As a cross check, I would examine v$event_histogram (or an AWR/Statspack for the interval) for time spent in the event "log file switch (private strand flush incomplete)". In prinicple I wouldn't expect to see waits longer than a few (less than 10) milliseconds; if the histogram shows long waits consistent with the alert log reports than I'd contact Oracle because something odd is happening.
(Footnote - it's possible that the event times out after a limited interval, log file sync used to time out after 1 second and has recently changed to something shorter and adjustable, so 2 seconds may (for example) appear as 20 x 0.1 seconds.)
Regards
Jonathan Lewis -
In production database 8.1.6
I got a message at a particular time
cannot allocate log sequence seq#
Thread 1 advanced log sequence seq#
After this, I increased the log buffer value
and number of log files also.
But I am getting the same error. Is there
any suggestions please?Check the status of the log files by using following query
select * from v$log;
On log file should have status='CURRENT' and should have the highest sequence number;
Other's should have status = 'INACTIVE' and ARC=Y.
Its possible that the redo logs are waiting to be archived because of space problem.
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by maran:
In production database 8.1.6
I got a message at a particular time
cannot allocate log sequence seq#
Thread 1 advanced log sequence seq#
After this, I increased the log buffer value
and number of log files also.
But I am getting the same error. Is there
any suggestions please?<HR></BLOCKQUOTE>
null -
Cannot allocate new log, sequence Checkpoint not complete
Hi,
Im having very frequent log switches and Im getting error as
" cannot allocate new log, sequence Checkpoint not complete"
I was having 3 redo log groups with 50 MB each. After I found this error in the alert log; I increased teh number of redo log groups to 6 with 50MB each. Still the issue is not getting resolved.
Please suggest what will be the best solution for this.
Following is a snippet from alertlog.
==================================================
Sun Apr 19 09:14:08 2009
Thread 1 advanced to log sequence 5811
Current log# 2 seq# 5811 mem# 0: /u01/app/oracle/oradata/mview/redo02.log
Thread 1 cannot allocate new log, sequence 5812
Checkpoint not complete
Current log# 2 seq# 5811 mem# 0: /u01/app/oracle/oradata/mview/redo02.log
Sun Apr 19 09:14:18 2009
Thread 1 advanced to log sequence 5812
Current log# 3 seq# 5812 mem# 0: /u01/app/oracle/oradata/mview/redo03.log
Thread 1 cannot allocate new log, sequence 5813
Checkpoint not complete
Current log# 3 seq# 5812 mem# 0: /u01/app/oracle/oradata/mview/redo03.log
Thread 1 advanced to log sequence 5813
Current log# 1 seq# 5813 mem# 0: /u01/app/oracle/oradata/mview/redo01.log
Thread 1 cannot allocate new log, sequence 5814
Checkpoint not complete
Current log# 1 seq# 5813 mem# 0: /u01/app/oracle/oradata/mview/redo01.log
Sun Apr 19 09:14:32 2009
Thread 1 advanced to log sequence 5814
Current log# 2 seq# 5814 mem# 0: /u01/app/oracle/oradata/mview/redo02.log
Thread 1 cannot allocate new log, sequence 5815
Checkpoint not complete
Current log# 2 seq# 5814 mem# 0: /u01/app/oracle/oradata/mview/redo02.log
Thread 1 advanced to log sequence 5815
Current log# 3 seq# 5815 mem# 0: /u01/app/oracle/oradata/mview/redo03.log
Thread 1 cannot allocate new log, sequence 5816
Checkpoint not complete
Current log# 3 seq# 5815 mem# 0: /u01/app/oracle/oradata/mview/redo03.log
Sun Apr 19 09:14:44 2009
=========================================================
Regards
PratheejAnand... wrote:
Hi Sir,
Although i too had suggested increasing the redo logfile size, but after going through [http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:69012348056] i was little confused as Tom has mentioned
Another way is to make the log files smaller, hence increasing the frequency with which we checkpoint ---- Can you explain why so.
I was a little surprised when I read that posting - but noticed it was dated May 2000 - when databases were still quite small and less busy. (And Tom suggested 25MB as being "modest" rather than "tiny" - which is probably what many people would call 25MB these days). And May 2000 probably means 8.0 or 8.1 - and the whole log buffer, redo generation, checkpointing technology has changed a lot since then.
Basically, if you hit "checkpoint not complete", you need more online log space so that it's possible during the busiest times to keep generating redo log information while the checkpoint queues are being cleared far enough to allow older log files to be recycled.
You can do this by adding more log files, or by increasing the sizes of the log files you use. Tom's point, I think, was that if you chose the option to add more files and kept them small (or even made them smaller) then the volume of dirty data blocks that you could create while filling a log file would be small, so the database writer wouldn't have to do much work to make each log file available for re-use. (I'm not sure I'd agree with the approach, though - even for 8i - because it could easily lead to an increase in the volume of datablocks written, even if it did bypass the checkpoint issue).
Regards
Jonathan Lewis
http://jonathanlewis.wordpress.com
http://www.jlcomp.demon.co.uk
"For every expert there is an equal and opposite expert."
Arthur C. Clarke -
Cannot allocate new log, sequence
Hi ,I see my alert.log which writed 'Thread 1 cannot allocate new log, sequence '
what is Thread 1 cannot allocate new log, sequence ?Please see the following for a similar discussion:
Thread 1 cannot allocate new log, sequence 1196,Checkpoint not complete
Maybe you are looking for
-
atualizei o firefox para a versão atual e através da versão antiga não quis atualizar seguindo as instruções desinstalei o navegador e baixei e instalei a versão 36.0.1 disponível apesar de escolher a opção de torna lo navegador padrão na instalação
-
Issue regarding bdc for capturing error records
Hi All, My requirement is to capture the error record and download the error record to a flat file . I have done recording for MM01 transaction . I am getting a problem like no error records are downloaded into the flat file .It is downloadin
-
When entering the digits from an Anti Spam Image they are not accepted by the host web site why
In e-bay when required to enter the digits from an anti spam image, ebay rejects the entered digets. This only occurs when using Firefox, Internet explorer works fine. Any body know why?
-
Automatic standby - does it do anything?
I've tried this at 2 and 3 hours - but even if I then go out for the day the box is still on when I return. Does automatic standby work as my box has never gone into standby on its own? Solved! Go to Solution.
-
DDE commands to process in background
Hi I am using Forms4.5 and trying to print a letter (with data populated from oracle) using DDE/Word2000 commands. Is it possible to print the letter without displaying the Word document ?, and to avoid the Microsoft message while closing the documen