Archiving log / nologging / direct path insert

Could you please confirm if the following are true or correct me if my interpretation is wrong:

Log mode archive 1) and logging is necessary to deal with the media recovery; It was not necessary for the recovery of the instance.

(2) IF the insert is no. APPEND mode, redo is generated, even if the table is in nologging mode and database is in log noachive mode. This recovery is necessary for recovery of the instance.

(3) direct path insert ignore cancel the generation and can jump redo generation if the object is in nologging mode.

Thank you.

In case if it is relevant, I'm using Oracle 11.2.0.3.

(1) Yes, archive logs is required for media recovery.
2 and 3) even if the table is in nologging mode, it generates little recovery data dictionary and index maintenance. After a reboot of a failure - Oracle reads the online redo logs and replay any what transaction it finds in there. It's the little "roll forward." The binary redo information are used to re-read everything that did not get written to the data files. This review included refreshing the information for CANCELLATION (UNDO is protected by roll forward).

After the restoration has been applied, the database is generally available for use now - and restore begins. For any transaction that was being processed when the instance failed - we have to revert his changes, roll back. We do this by treating the cancellation of all uncommitted transactions.

The database is now fully recovered.

Also read he following link
http://docs.Oracle.com/CD/B19306_01/server.102/b14220/startup.htm
http://asktom.Oracle.com/pls/asktom/f?p=100:11:0:P11_QUESTION_ID:5280714813869

Tags: Database

Similar Questions

Insert / * + Append * / and direct-path INSERT
Hi guys

Insert / * + Append * / hint cause Oracle 10 G using direct-path INSERT?
and so insert / * + Append * / suspicion causes an Oracle of using direct-path INSERT, insert / * + Append * / is subject to the same restrictions as direct-path, such as "the target table cannot have any triggers or referential integrity constraints defined on it.»

Thank you
How it would be difficult for you to look for the answer in the documentation and do not abuse this forum asking questions doc and flaming posters colleagues?

------------
Sybrand Bakker
Senior Oracle DBA

Redo generation for Direct path Inserts

Hello, I'm trying to understand some test results confused I see this morning on the generation of redo direct path for the pads. Based on my understanding of Tom to ask several discussions directly inserts path on a set of data to force the record should generate much less remake a traditional insert because the insertion of the direct route does not generate as much cancel which in turn should generate less do on cancellation.
https://asktom.Oracle.com/pls/asktom/f?p=100:11:0:P11_QUESTION_ID:5280714813869
Of course, always connect the actual inserted rows but I expected to the remake was less because less cancel has been generated. Instead the roll forward is actually bigger and I don't know why.
Here's a test case to prove my example.
```
set autotrace traceonly;
create table test_redo as select * from all_tables where 1=0;
insert into test_redo select * from all_tables;
rollback;
insert /*+ append */ into test_redo select * from all_tables;
rollback;
```
```
Stats without Append Hint

Statistics
----------------------------------------------------------
        387  recursive calls
       1275  db block gets
      19604  consistent gets
          9  physical reads
    2409204  redo size
        501  bytes sent via SQL*Net to client
        897  bytes received via SQL*Net from client
          4  SQL*Net roundtrips to/from client
          4  sorts (memory)
          0  sorts (disk)
       9031  rows processed

Stats with Append Hint

Statistics
----------------------------------------------------------
         59  recursive calls
        162  db block gets
      18675  consistent gets
          0  physical reads
    2596904  redo size
        490  bytes sent via SQL*Net to client
        911  bytes received via SQL*Net from client
          4  SQL*Net roundtrips to/from client
          2  sorts (memory)
          0  sorts (disk)
       9031  rows processed
```
Any ideas on what I'm missing?
Thank you

The / * + append * / copies all blocks Oracle in roll forward, with a little extra for recording etc. headers.

The standard insert creates change descriptions which save odd odd little bits of space and adds little bits of information links (as well as some redo to describe a very small amount to cancel)...

The difference between the two has always been pretty low (assuming that you are running in archivelog mode, or force logging) on a right append. It is possible that curious little details of efficiencies in future versions of the average of the Oracle that the standard Insert wins a place a bit more efficient - it used to be the other way around in earlier versions.

Concerning

Jonathan Lewis

Insert adds parallel sessions expect "direct path read temp".
Hi all.

The database is 11.2.0.3 on a linux machine.

I published the following query, and I found that parallel query sessions were waiting for "direct path read temp.

And SDPCSM. Table SDP_CHILD_SVC_PROFATTR_HIS does NOT index and is in nologging mode.

Why the pq sessions expect "direct path read/write temp?
```
insert /*+ append parallel (8) */ into SDPCSM.SDP_CHILD_SVC_PROFATTR_HIS
select /*+ parallel (SDP_CHILD_SVC_PROFATTR_HIS_E, 8) */ * from SDPCSM.SDP_CHILD_SVC_PROFATTR_HIS_E@tb_link;
```
Thanks in advance.
Best regards.
Please check this blog:
http://www.Confio.com/blog/Oracle-wait-event-explained-direct-path-read-temp

Direct-path (without) Archivelog and recovery

Hello

Our database is in a Data Warehouse environment, NOARCHIVELOG. When we do an Insert / * + APPEND * / an attribute table withLOGGING, a miniminal redo log is generated.
We want to move the database in ARCHIVELOG mode and change the attribute of the table in NOLOGGING.

My question is, is body recovery work?

I made a matrix of the effect of a crash all in a way direct insertion operation:

Database mode                   Table mode               Instance recovery                      Media recovery
----------------------------------------------------------------------------------------------------------------------------------
NOARCHIVELOG                     LOGGING                        OK                                     NOT OK
ARCHIVELOG                       LOGGING                        OK                                     OK
ARCHIVELOG                       NOLOGGING                      OK                                     NOT OK

Do you agree with this matrix ?

Concerning

Yes, instance recovery will work regardless of its direct-path use access and nologgging.

Here is an example with Oracle XE on Windows (database is running in ARCHIVELOG mode and FORCE_LOGGING is not defined):

c:\tmp>rman target /

Recovery Manager: Release 11.2.0.2.0 - Production on Jeu. Janv. 12 20:05:32 2012

Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.

connected to target database: XE (DBID=2642463371)

RMAN> report unrecoverable;

using target database control file instead of recovery catalog
Report of files that need backup due to unrecoverable operations
File Type of Backup Required Name
---- ----------------------- -----------------------------------

RMAN> exit

Recovery Manager complete.

c:\tmp>sqlplus xxx/xxx @nolog.sql

SQL*Plus: Release 11.2.0.2.0 Production on Jeu. Janv. 12 20:05:48 2012

Copyright (c) 1982, 2010, Oracle.  All rights reserved.

Connected to:
Oracle Database 11g Express Edition Release 11.2.0.2.0 - Production

SQL> select log_mode, force_logging from v$database;

LOG_MODE     FOR
------------ ---
ARCHIVELOG   NO

SQL> drop table tnl purge;

Table dropped.

SQL> create table tnl(x int) nologging tablespace users;

Table created.

SQL> insert /*+ APPEND */ into tnl select object_id from all_objects;

17971 rows created.

SQL> commit;

Commit complete.

SQL> connect / as sysdba
Connected.
SQL> startup force
ORACLE instance started.

Total System Global Area 1071333376 bytes
Fixed Size                  1388352 bytes
Variable Size             658505920 bytes
Database Buffers          406847488 bytes
Redo Buffers                4591616 bytes
Database mounted.
Database opened.
SQL> exit
Disconnected from Oracle Database 11g Express Edition Release 11.2.0.2.0 - Production

c:\tmp>rman target /

Recovery Manager: Release 11.2.0.2.0 - Production on Jeu. Janv. 12 20:07:34 2012

Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.

connected to target database: XE (DBID=2642463371)

RMAN> report unrecoverable;

using target database control file instead of recovery catalog
Report of files that need backup due to unrecoverable operations
File Type of Backup Required Name
---- ----------------------- -----------------------------------
4    full or incremental     C:\ORACLEXE\APP\ORACLE\ORADATA\XE\USERS.DBF

RMAN> exit

Recovery Manager complete.

c:\tmp>

Edited by: P. Forstmann on 12 Jan. 2012 20:08

Multithreading works only with the direct path load

Oracle DB version: Oracle Database 11 g Enterprise Edition Release 11.2.0.4.0 - 64 bit Production
I'm on my way live load to load data from a flat file into a table using SQL * Loader. I also kept as parallel. However, I can't in multithreading is used at all, based on the report of the log file.
I use the settings according to the true value in the sqlldr: -.
```
parallel=true , multithreading=true , skip_index_maintenance=true
```
Output in the journal sqlldr:-
```
Path used: Direct Insert option in effect for this table: APPEND 
Trigger DEV."R_TM_BK_BORROWER" was disabled before the load.
DEV."R_TM_BK_BORROWER" was re-enabled.
The following index(es) on table "YO"."TM_BK_BORROWER" were processed:
index DEV.I_NK_TM_BK_BORR_1 loaded successfully with 1554238 keys
index DEV.I_NK_TM_BK_BORR_2 loaded successfully with 1554238 keys
index DEV.I_NK_TM_BK_BORR_3 loaded successfully with 1554238 keys
index DEV.I_NK_TM_BK_BORR_31 loaded successfully with 1554238 keys
 
Bind array size not used in direct path.
Column array rows : 5000
Stream buffer bytes: 256000
Read buffer bytes: 1048576 


Total logical records skipped: 1 
Total logical records read: 1554241 
Total logical records rejected: 48 
Total logical records discarded: 2 
Total stream buffers loaded by SQL*Loader main thread: 7695 
Total stream buffers loaded by SQL*Loader load thread: 0 
```
So, I can still see the newspaper sqlldr that all data flow buffers loaded by the main thread and load wire is not always used.
SQL * Loader load wire do not unload the SQL * Loader main thread. If the load wire supports the current stream buffers, then it allows the primary thread to build the buffer to the next stream while the thread of load load the current stream to the server. We have a server CPU 24.
I'm not able to find a clue on Google too. Any help is appreciated.

People, Tom Kyte has finally responded to my message. Here's the thread on asktom-

http://asktom.Oracle.com/pls/Apex/f?p=100:11:0:P11_QUESTION_ID:1612304461350 #7035459900346550399

Manually apply archive logs waiting

RDBMS Version: 11.2.0.4
OS: RHEL 6.6
As I understand it, if I want to manually apply archive logs, I do the 2 steps.
But, how can I do watch DB to accept (add it as part of the eve DB) logs archiving transferred manually?
That is to say. How can force you standby DB to add these archiving logs to its control file?
Step 1. First stop the current recovery process (MRP) as
ALTER database recover managed standby database cancel;
Then transfer must all logs archiving of primary school next door waiting and apply manually using below command.
Step 2. recover a database on hold until cancel;

Hello

To do this manually, you must:

(a) manually transfer logs archived redo of primary site on backup site

(b) lets say to the backup site, you have this path ' / archives/database / ' and in this way, there are the archived redo logs

Then, in the backup site, you must catalog the logs archived redo with RMAN

RMAN > CATALOGUE START WITH "/ archives/database /";

(c) Once catalogued recovery logs archived, you can start the recovery media

change recover managed standby database disconnect log file using current;

or

ALTER database recover managed standby database disconnect;

(d) monitor the alerts log to see if this transferred manually and asking unregistered archived redo logs

Kind regards

Juan M

Problem with the archive log when you use RMAN for backup and restore (11g 2)

Hello world
Please help me solve this problem.
I'm just beginner in Oracle Database (11 g 2). Today, I had a problem, I tried to back up and restore my db by RMAN. I delete all the files in /u01/app/oracle/oradata/orcl / * , then I restore them easily, but the point is I have a table, I can restore Hungarian, but cannot restore anything ranks in it (something wrong with step restore database). I'll tell the detail below.
-First, I create a 'Day' with command table create table hr.day (varchar (20)) day. Then I backup complete by this:
run{ allocate channel bkp device type DISK FORMAT '/u01/backup/DB_FULL_%d_%T_s%s_p%p' ; backup as compressed backupset incremental level 0 tag 'DB_FULL' database include current controlfile; backup as compressed backupset tag 'ARCL_BKP_FULL' archivelog all delete input; crosscheck archivelog all; crosscheck backup; delete noprompt obsolete; release channel bkp; }

D ' other hand, I have insert 'Monday' to table. then do an incremental backup by this:
run{ allocate channel bkp device type DISK FORMAT '/u01/backup/DB_INC_%d_%T_s%s_p%p' ; backup as compressed backupset incremental level 1 tag 'DB_INC' database include current controlfile; backup as compressed backupset tag 'ARCL_BKP_INC' archivelog all delete input; crosscheck archivelog all; crosscheck backup; delete noprompt obsolete; release channel bkp; }
Repeat 7 times (Monday-> Saturday). And I got these files:
[oracle@rac ~]$ ls -l /u01/backup/ total 400280 -rw-r----- 1 oracle oinstall 10158080 Jan 20 07:23 c-1428943247-20160120-01 -rw-r----- 1 oracle oinstall 10158080 Jan 20 08:04 c-1428943247-20160120-02 -rw-r----- 1 oracle oinstall 10158080 Jan 20 08:05 c-1428943247-20160120-03 -rw-r----- 1 oracle oinstall 10158080 Jan 20 08:06 c-1428943247-20160120-04 -rw-r----- 1 oracle oinstall 10158080 Jan 20 08:08 c-1428943247-20160120-05 -rw-r----- 1 oracle oinstall 10158080 Jan 20 08:08 c-1428943247-20160120-06 -rw-r----- 1 oracle oinstall 10158080 Jan 20 08:09 c-1428943247-20160120-07 -rw-r----- 1 oracle oinstall 10158080 Jan 20 08:32 c-1428943247-20160120-08 -rw-r----- 1 oracle oinstall 296337408 Jan 20 07:23 DB_FULL_ORCL_20160120_s89_p1 -rw-r----- 1 oracle oinstall   1130496 Jan 20 07:23 DB_FULL_ORCL_20160120_s90_p1 -rw-r----- 1 oracle oinstall   2266624 Jan 20 07:23 DB_FULL_ORCL_20160120_s91_p1 -rw-r----- 1 oracle oinstall   4073984 Jan 20 07:23 DB_FULL_ORCL_20160120_s92_p1 -rw-r----- 1 oracle oinstall 11201536 Jan 20 07:23 DB_FULL_ORCL_20160120_s93_p1 -rw-r----- 1 oracle oinstall   1130496 Jan 20 08:05 DB_INC_ORCL_20160120_s100_p1 -rw-r----- 1 oracle oinstall    146944 Jan 20 08:05 DB_INC_ORCL_20160120_s101_p1 -rw-r----- 1 oracle oinstall    884736 Jan 20 08:06 DB_INC_ORCL_20160120_s103_p1 -rw-r----- 1 oracle oinstall   1130496 Jan 20 08:06 DB_INC_ORCL_20160120_s104_p1 -rw-r----- 1 oracle oinstall     82432 Jan 20 08:06 DB_INC_ORCL_20160120_s105_p1 -rw-r----- 1 oracle oinstall    294912 Jan 20 08:07 DB_INC_ORCL_20160120_s107_p1 -rw-r----- 1 oracle oinstall   1130496 Jan 20 08:07 DB_INC_ORCL_20160120_s108_p1 -rw-r----- 1 oracle oinstall     18944 Jan 20 08:08 DB_INC_ORCL_20160120_s109_p1 -rw-r----- 1 oracle oinstall    155648 Jan 20 08:08 DB_INC_ORCL_20160120_s111_p1 -rw-r----- 1 oracle oinstall   1130496 Jan 20 08:08 DB_INC_ORCL_20160120_s112_p1 -rw-r----- 1 oracle oinstall    131584 Jan 20 08:08 DB_INC_ORCL_20160120_s113_p1 -rw-r----- 1 oracle oinstall    647168 Jan 20 08:09 DB_INC_ORCL_20160120_s115_p1 -rw-r----- 1 oracle oinstall   1130496 Jan 20 08:09 DB_INC_ORCL_20160120_s116_p1 -rw-r----- 1 oracle oinstall      8704 Jan 20 08:09 DB_INC_ORCL_20160120_s117_p1 -rw-r----- 1 oracle oinstall   2203648 Jan 20 08:04 DB_INC_ORCL_20160120_s95_p1 -rw-r----- 1 oracle oinstall   1130496 Jan 20 08:04 DB_INC_ORCL_20160120_s96_p1 -rw-r----- 1 oracle oinstall   1899008 Jan 20 08:04 DB_INC_ORCL_20160120_s97_p1 -rw-r----- 1 oracle oinstall    327680 Jan 20 08:05 DB_INC_ORCL_20160120_s99_p1
And
RMAN> list backup summary; List of Backups =============== Key     TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag ------- -- -- - ----------- --------------- ------- ------- ---------- --- 80      B 0 A DISK        20-JAN-16       1       1       YES        DB_FULL 81      B 0 A DISK        20-JAN-16       1       1       YES        DB_FULL 82      B A A DISK        20-JAN-16       1       1       YES        ARCL_BKP_FULL 83      B A A DISK        20-JAN-16       1       1       YES        ARCL_BKP_FULL 84      B A A DISK        20-JAN-16       1       1       YES        ARCL_BKP_FULL 85      B F A DISK        20-JAN-16       1       1       NO         TAG20160120T072332 86      B 1 A DISK        20-JAN-16       1       1       YES        DB_INC 87      B 1 A DISK        20-JAN-16       1       1       YES        DB_INC 88      B A A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC 89      B F A DISK        20-JAN-16       1       1       NO         TAG20160120T080440 90      B 1 A DISK        20-JAN-16       1       1       YES        DB_INC 91      B 1 A DISK        20-JAN-16       1       1       YES        DB_INC 92      B A A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC 93      B F A DISK        20-JAN-16       1       1       NO         TAG20160120T080545 94      B 1 A DISK        20-JAN-16       1       1       YES        DB_INC 95      B 1 A DISK        20-JAN-16       1       1       YES        DB_INC 96      B A A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC 97      B F A DISK        20-JAN-16       1       1       NO         TAG20160120T080657 98      B 1 A DISK        20-JAN-16       1       1       YES        DB_INC 99      B 1 A DISK        20-JAN-16       1       1       YES        DB_INC 100     B A A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC 101     B F A DISK        20-JAN-16       1       1       NO         TAG20160120T080801 102     B 1 A DISK        20-JAN-16       1       1       YES        DB_INC 103     B 1 A DISK        20-JAN-16       1       1       YES        DB_INC 104     B A A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC 105     B F A DISK        20-JAN-16       1       1       NO         TAG20160120T080844 106     B 1 A DISK        20-JAN-16       1       1       YES        DB_INC 107     B 1 A DISK        20-JAN-16       1       1       YES        DB_INC 108     B A A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC
My configuration of rman:
RMAN> show all; RMAN configuration parameters for database with db_unique_name ORCL are: CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS; CONFIGURE BACKUP OPTIMIZATION ON; CONFIGURE DEFAULT DEVICE TYPE TO DISK; CONFIGURE CONTROLFILE AUTOBACKUP ON; CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u01/backup/%F'; CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET; CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT   '/u01/backup/backup_df%t_s%s_s%p'; CONFIGURE MAXSETSIZE TO UNLIMITED; # default CONFIGURE ENCRYPTION FOR DATABASE OFF; # default CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0/dbhome/dbs/snapcf_orcl.f'; # default
- Thirdly, i removed all file in /u01/app/oracle/oradata/orcl/*. then restore control file from the newest backup control file (saturday backup) + restore database. Seem nothing's wrong here. RMAN> restore controlfile from '/u01/backup/c-1428943247-20160120-08'; Starting restore at 20-JAN-16 allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID=18 device type=DISK allocated channel: ORA_DISK_2 channel ORA_DISK_2: SID=20 device type=DISK channel ORA_DISK_2: skipped, AUTOBACKUP already found channel ORA_DISK_1: restoring control file channel ORA_DISK_1: restore complete, elapsed time: 00:00:09 output file name=/u01/app/oracle/oradata/orcl/control01.ctl output file name=/u01/app/oracle/flash_recovery_area/orcl/control02.ctl Finished restore at 20-JAN-16 RMAN> alter database mount; database mounted released channel: ORA_DISK_1 released channel: ORA_DISK_2 RMAN> restore database; Starting restore at 20-JAN-16 Starting implicit crosscheck backup at 20-JAN-16 allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID=20 device type=DISK allocated channel: ORA_DISK_2 channel ORA_DISK_2: SID=18 device type=DISK Crosschecked 29 objects Finished implicit crosscheck backup at 20-JAN-16 Starting implicit crosscheck copy at 20-JAN-16 using channel ORA_DISK_1 using channel ORA_DISK_2 Finished implicit crosscheck copy at 20-JAN-16 searching for all files in the recovery area cataloging files... no files cataloged using channel ORA_DISK_1 using channel ORA_DISK_2 channel ORA_DISK_1: starting datafile backup set restore channel ORA_DISK_1: specifying datafile(s) to restore from backup set channel ORA_DISK_1: restoring datafile 00001 to /u01/app/oracle/oradata/orcl/system01.dbf channel ORA_DISK_1: restoring datafile 00002 to /u01/app/oracle/oradata/orcl/sysaux01.dbf channel ORA_DISK_1: restoring datafile 00003 to /u01/app/oracle/oradata/orcl/undotbs01.dbf channel ORA_DISK_1: restoring datafile 00004 to /u01/app/oracle/oradata/orcl/users01.dbf channel ORA_DISK_1: restoring datafile 00005 to /u01/app/oracle/oradata/orcl/example01.dbf channel ORA_DISK_1: reading from backup piece /u01/backup/DB_FULL_ORCL_20160120_s89_p1 channel ORA_DISK_1: piece handle=/u01/backup/DB_FULL_ORCL_20160120_s89_p1 tag=DB_FULL channel ORA_DISK_1: restored backup piece 1 channel ORA_DISK_1: restore complete, elapsed time: 00:01:15 Finished restore at 20-JAN-16
-Fourth, the problem here, I got the database; .. .every oky until this line... starting media recovery channel ORA_DISK_1: starting archived log restore to default destination channel ORA_DISK_1: restoring archived log archived log thread=1 sequence=15 channel ORA_DISK_1: reading from backup piece /u01/backup/DB_INC_ORCL_20160120_s117_p1 channel ORA_DISK_1: piece handle=/u01/backup/DB_INC_ORCL_20160120_s117_p1 tag=ARCL_BKP_INC channel ORA_DISK_1: restored backup piece 1 channel ORA_DISK_1: restore complete, elapsed time: 00:00:01 archived log file name=/u01/app/oracle/flash_recovery_area/ORCL/archivelog/2016_01_20/o1_mf_1_15_c9xsyx9k_.arc thread=1 sequence=15 unable to find archived log archived log thread=1 sequence=1 RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of recover command at 01/20/2016 08:50:22 RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 1 and starting SCN of 1205841 The error said that it is impossible to find the archived log thread = 1 sequence = 1. Then I check it with this command always there (oh, I'm wrong?) RMAN> list backup of archivelog all; List of Backup Sets =================== BS Key Size       Device Type Elapsed Time Completion Time ------- ---------- ----------- ------------ --------------- 82      2.16M      DISK        00:00:00     20-JAN-16              BP Key: 82   Status: AVAILABLE Compressed: YES Tag: ARCL_BKP_FULL         Piece Name: /u01/backup/DB_FULL_ORCL_20160120_s91_p1 List of Archived Logs in backup set 82 Thrd Seq     Low SCN    Low Time Next SCN   Next Time ---- ------- ---------- --------- ---------- --------- 1    1       1154833    20-JAN-16 1177422    20-JAN-16 BS Key Size       Device Type Elapsed Time Completion Time ------- ---------- ----------- ------------ --------------- 83      3.88M      DISK        00:00:00     20-JAN-16              BP Key: 83   Status: AVAILABLE Compressed: YES Tag: ARCL_BKP_FULL         Piece Name: /u01/backup/DB_FULL_ORCL_20160120_s92_p1 List of Archived Logs in backup set 83 Thrd Seq     Low SCN    Low Time Next SCN   Next Time ---- ------- ---------- --------- ---------- --------- 1    1       1162729    20-JAN-16 1188784    20-JAN-16 BS Key Size       Device Type Elapsed Time Completion Time ------- ---------- ----------- ------------ --------------- 84      10.68M     DISK        00:00:01     20-JAN-16              BP Key: 84   Status: AVAILABLE Compressed: YES Tag: ARCL_BKP_FULL         Piece Name: /u01/backup/DB_FULL_ORCL_20160120_s93_p1 List of Archived Logs in backup set 84 Thrd Seq     Low SCN    Low Time Next SCN   Next Time ---- ------- ---------- --------- ---------- --------- 1    2       1177422    20-JAN-16 1201833    20-JAN-16 BS Key Size       Device Type Elapsed Time Completion Time ------- ---------- ----------- ------------ --------------- 88      1.81M      DISK        00:00:01     20-JAN-16              BP Key: 88   Status: AVAILABLE Compressed: YES Tag: ARCL_BKP_INC         Piece Name: /u01/backup/DB_INC_ORCL_20160120_s97_p1 List of Archived Logs in backup set 88 Thrd Seq     Low SCN    Low Time Next SCN   Next Time ---- ------- ---------- --------- ---------- --------- 1    3       1201833    20-JAN-16 1204844    20-JAN-16 1    4       1204844    20-JAN-16 1204893    20-JAN-16 1    5       1204893    20-JAN-16 1204958    20-JAN-16 BS Key Size       Device Type Elapsed Time Completion Time ------- ---------- ----------- ------------ --------------- 92      143.00K    DISK        00:00:00     20-JAN-16              BP Key: 92   Status: AVAILABLE Compressed: YES Tag: ARCL_BKP_INC         Piece Name: /u01/backup/DB_INC_ORCL_20160120_s101_p1 List of Archived Logs in backup set 92 Thrd Seq     Low SCN    Low Time Next SCN   Next Time ---- ------- ---------- --------- ---------- --------- 1    6       1204958    20-JAN-16 1205034    20-JAN-16 1    7       1205034    20-JAN-16 1205253    20-JAN-16 BS Key Size       Device Type Elapsed Time Completion Time ------- ---------- ----------- ------------ --------------- 96      80.00K     DISK        00:00:00     20-JAN-16              BP Key: 96   Status: AVAILABLE Compressed: YES Tag: ARCL_BKP_INC         Piece Name: /u01/backup/DB_INC_ORCL_20160120_s105_p1 List of Archived Logs in backup set 96 Thrd Seq     Low SCN    Low Time Next SCN   Next Time ---- ------- ---------- --------- ---------- --------- 1    8       1205253    20-JAN-16 1205354    20-JAN-16 1    9       1205354    20-JAN-16 1205433    20-JAN-16 BS Key Size       Device Type Elapsed Time Completion Time ------- ---------- ----------- ------------ --------------- 100     18.00K     DISK        00:00:00     20-JAN-16              BP Key: 100   Status: AVAILABLE Compressed: YES Tag: ARCL_BKP_INC         Piece Name: /u01/backup/DB_INC_ORCL_20160120_s109_p1 List of Archived Logs in backup set 100 Thrd Seq     Low SCN    Low Time Next SCN   Next Time ---- ------- ---------- --------- ---------- --------- 1    10      1205433    20-JAN-16 1205519    20-JAN-16 1    11      1205519    20-JAN-16 1205559    20-JAN-16 BS Key Size       Device Type Elapsed Time Completion Time ------- ---------- ----------- ------------ --------------- 104     128.00K    DISK        00:00:00     20-JAN-16              BP Key: 104   Status: AVAILABLE Compressed: YES Tag: ARCL_BKP_INC         Piece Name: /u01/backup/DB_INC_ORCL_20160120_s113_p1 List of Archived Logs in backup set 104 Thrd Seq     Low SCN    Low Time Next SCN   Next Time ---- ------- ---------- --------- ---------- --------- 1    12      1205559    20-JAN-16 1205624    20-JAN-16 1    13      1205624    20-JAN-16 1205739    20-JAN-16 BS Key Size       Device Type Elapsed Time Completion Time ------- ---------- ----------- ------------ --------------- 108     8.00K      DISK        00:00:00     20-JAN-16              BP Key: 108   Status: AVAILABLE Compressed: YES Tag: ARCL_BKP_INC         Piece Name: /u01/backup/DB_INC_ORCL_20160120_s117_p1 List of Archived Logs in backup set 108 Thrd Seq     Low SCN    Low Time Next SCN   Next Time ---- ------- ---------- --------- ---------- --------- 1    14      1205739    20-JAN-16 1205796    20-JAN-16 1    15      1205796    20-JAN-16 1205840    20-JAN-16
If i ignore it and open the database, just my table in full backup come back but rows was not restored. I'm sure the problem is my archive log backup but i don't know how to solve it. Plz help me.
Sorry for a long post.
> 1 and from the 1205841 SNA sequence The SCN that indicates Oracle is above the range of SNA that you have in the ArchiveLog backups for sequence 1 to 15 (15 sequence ends at 1205840). The message channel ORA_DISK_1: restoring archives Journal Archives journal thread = 1 sequence = 15 channel ORA_DISK_1: backup/u01/backup/DB_INC_ORCL_20160120_s117_p1 piece reading channel ORA_DISK_1: piece handle = / u01/backup/DB_INC_ORCL_20160120_s117_p1 tag = ARCL_BKP_INC indicates that he has restored the sequence up to 15 You can check the log file alert database instance for messages on the fact of recovery. He is now asking sequence #1 it seems you did a RESETLOGS after sequence #15. Note: If you have NOT issued a COMMIT after the line is INSERTED in the table 'Day', the recovery of the database will have no * transactions * to retrieve. An uncomitted transaction is cancelled. Hemant K Collette

 
            
            
		     Multiplex Archived Logs 
			 With the help of 11.2.0.4.0
I am trying to mux the newspapers archived (duplicate); However, do not know if I'm doing things.
I followed this http://docs.oracle.com/cd/B28359_01/server.111/b28310/archredo004.htm and made the following
LOG_ARCHIVE_DEST_1 = 'LOCATION=Z:\FlashRecoveryArea\archlogs\'
LOG_ARCHIVE_DEST_2 = 'LOCATION=\\backupserver\archlogs_location'
I thought I was doing the right thing with handwritten copies in both places when I run
"alter newspaper archive of the current system. However, to take a closer look, looks like maybe it's different.
Z:\FlashRecoveryArea\archlogs has the logs archived LOG_1_68_xxxx. ARC and LOG_1_71_xxxx. ARC
\\backupserver\archlogs_location archived LOG_1_69_xxxx newspapers. ARC, LOG_1_70_xxxx. ARC and LOG_1_71_xxxx. ARC
I misunderstood the document? This is not duplication of archived newspapers?
Thank you
			 I think your problem is the backup archivelog and remove that happens at the same time as the journal was cheating (i.e. newspaper is too slow).
Just do this - see crossouts and "BOLD" text 'everything '...
RUN
{
SQL "alter session set nls_date_format = 'MON-DD-YYYY HH24:MI:SS' ';"
overlap archivelog all;
cross-checking of backup;
SQL 'alter system archive log current';
SQL 'alter system archive log current';
backup
(database FORMAT '\backupserver\full\FULLBKUP_%d.DBID%I.%T.%s.%p.rman')
more all archivelog delete all input FORMAT '\\backupserver\full\ARCHLOGBKUP_%d.%e.DBID%I.%T.%s.%p.rman' TAG = "FULLBKUP_PLUS_ARCHLOG";
window recovery obsolete report of 5 days;
delete noprompt obsolete recovery window of 5 days;
SPFile FORMAT '\\backupserver\full\SPFILE_BKUP_%d.DBID%I.%T.%s.%p.rman' label backup = "BKUP_SPFILE";
SQL 'alter controlfile backup database path as "\\backupserver\full\ctlfilePROD.txt" RE-USE";
SQL "' create pfile =" \\backupserver\full\pfile_PROD.ora "of spfile"; "
SQL 'alter system archive log current';
SQL 'alter system archive log current';
backup FORMAT '\\backupserver\full\ARCHLOGBKUP_%d.%e.DBID%I.%T.%s.%p.rman' archivelog delete all all the entries TAG = "BKUP_ARCHLOG";
backup current controlfile FORMAT '\\backupserver\full\CTLFILE_BKUP_%d.DBID%I.%T.%s.%p.rman' TAG = "BKUP_CTLFILE";
}
		   
 
            
            
		     Archives generate the different path compared with the path mentioned in LOG_ARCHIVE_DEST_1 
			 Hi all
I have 2 Installation RAC + ASM from the node. Here, I found that generate the archives on the different path compared to the path mentioned in log_archive_dest_1.
O/P to the list of archive logs:
Database log mode Fashion Archive
Automatic archiving Activated
Destination of archive + ORAARCH
Sequence of journal online oldest 2307
Log sequence archive 2309
Current log sequence 2309
Archives to generate the path are: (to 17 July 2015)
+ ORAARCH, ABCDB, ARCHIVELOG, 2015_07_17
Please guide why such difference?
			 


Destination of archive
+ ORAARCH



Above location is diskgroup name in ASM (OMF), all files created in the DISKGROUP/DBNAME/FILETYPE format.

2015_07_17 is the DATE of generation of the Archive.
		    
            
            
		     Current archive log has been deleted, how to recover using the previous archive log? 
			 Hello


My current log sequence #819 and it has been deleted and no other choice to get it back and I have previous newspapers archived with sequences #814 à 818.


When I start my database is to show that the use ' MUST USE RESETLOGS or NORESETLOGS option of database open, then I used the command


SQL > ALTER DATABASE OPEN RESETLOGS;
ALTER DATABASE OPEN RESETLOGS
*
ERROR on line 1:
ORA-01113: file 1 needs media recovery
ORA-01110: data file 1: ' E:\APP\ADMINISTRATOR\ORADATA\ORCL\SYSTEM01. DBF'


SQL > alter database recover;
ALTER database recover
*
ERROR on line 1:
ORA-00283: cool cancelled due to errors
ORA-01610: recovery using BACKUP CONTROLFILE option must be
SQL > alter database recovery using backup controlfile;
change the database recovery using backup controlfile
*
ERROR on line 1:
ORA-00279: change 8433746 September at 15/01/2013 19:51:59 needed to screw 1
ORA-00289: suggestion:
E:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2013_01_16\O1_MF_1_819_


% U_. ARC
ORA-00280: change 8433746 thread 1 is in sequence #819


now, I don't have the log archiving with 819 sequence, I recover from 818. Please tell me how to do?			 Hello
1. select * from v$log and see which log file is current. Query v$logfile to check physical file location belonging to current log group.
2. Take bacup of your curent control file using copy/paste of your OS
3. Issue following command in mount state
recover database until cancel using backup controlfile
4. When it finishes applying available archived logs, still it will ask for the location of archived logs which have not been applied, here provide path of current redo log file you got in first step. Here your recovery will finish after applying current redo log
5.alter database open resetlogs.

Salman
		    
            
            
		     How to control too many archived log generation 
			 Hello


This is one of the interview questions,


I answered it. Just as what the answer to this.


How can we control the excessive generation of archived log?


Thank you			 Hello;
Archive is to ensure the recovery of the database, which can be done with NOLOGGING who does not put it at risk? (Data copy from one table to the other, for example).
Excessive diagnosis Redo generation - limited with Nologging [ID 199298.1]
Best regards
mseberg
		    
            
            
		     Archive log deletion with no backup of the archive logs 
			 I suffer from enormous size archive of the newspaper. In my previous post, I asked for help. I almost 480 GB archive log every day in our database of 11 2 under redhat linux 5.8 GR. Now, if you please help me in another case.


If I take backup of archive logs and run delete archivelog everything until ' sysdate-1' with each backup database of day how it affects. " In my opinion there should be no problem in that I have the last incremental backup and recovery 1 days archive log in archivelog destination. If I do not archive log backups to how it will be different. Help, please.			 >
Hello
Sir, I know how to remove. But in my opinion delete up to sysdate-1 and taking no backup of the Archives of newspapers will
no effect. Is in my opinion is right or wrong, that is the question.
What I read in your original post, is that you take a daily incremental backup - Yes? I'm assuming that you also take
a full backup on a regular basis (Sunday?).
I was working on the assumption that the foregoing is available? I worked on a project where installation has been similar. We
tested regularly backups - I hope that you do the same thing?
What we used to do was FTP (script Unix - cron job - if you Google you will find Python or Perl to do the same thing - that is)
what I wanted to, but was cancelled - very 1980, anyway) the archived redo logs on to a specific computer that holds only these files.
After FTP "d - they have been removed from the server, freeing up space.
Now, you say you have TB 0.5 per day - while more than a week, you will need a machine with ~ 3 TB of disk - if you can get a kind
the scenario as this place and running, then you will have both your incremental backup and your archived redo logs for the last
24 hours and the full backup with recovery archived records dating back to this full backup. You can also always archive on tape if
suits. So, you will have redundant coverage - 'belt and braces' as the Americans say.
But, to answer your question directly, "take no backup of archive logs have no effect" - that is true - it
will not affect the operation of the database server, but if I were you, I would hang on to enough archived redo log to return to the
last backup. That's just my humble OPINION.
HTH,
Paul...
Published by: Paulie July 21, 2012 19:28
		    
            
            
		     direct path load question 
			 I do not understand why, in the course of a direct path load insert an exclusive lock on the table is required.


Suppose I have a T table without any indexes or constraints, why can't update the table in a session and in bulk load in another session above the HWM?


Thanks in advance			 Claire wrote:
I do not understand why, in the course of a direct path load insert an exclusive lock on the table is required.
Suppose I have a T table without any indexes or constraints, why can't update the table in a session and in bulk load in another session above the HWM?
What would ensue if/when another session DML requiring HWM be triggered BEFORE the completed direct path loading?
		    
            
            
		     How do duplex CARS DB archiving logs? 
			 Hello


I need to set up the location on the spare, local disk for archiving for two nodes RAC, apart from ASMjournals.
The reason behind this is to transfer the logs (as well as full backups) at a remote location to ensure the security of the data.
I have traced same remote directory a: Drive on both nodes.


2-node RAC Standard Database 11.2.0.2
Windows 2008 R2 Standard
+ ASM DATA storage


SYS@proton2x1 > list of archive logs
Database log mode Archive Mode
Active AutoArchive
Destination of archive USE_DB_RECOVERY_FILE_DEST
Sequence of journal online oldest 1750
Log sequence archive 1752
Current log sequence 1752


SYS@proton2x1 > display recov
VALUE OF TYPE NAME
db_recovery_file_dest chain + DATA


----


The problem is when I put in duplex rental:
SQL > alter system set log_archive_duplex_dest =' LOCATION = R:' SCOPE = spfile;
nodes to restart and go online newspapers 3 times it crashes and no archiive of newspapers are written in the R:\ directory.
Alert log says:
LGWR: Error 16017 validate archivelog destination information


I played in a manner similar to other parameters:
ALTER system set log_archive_dest_1 =' LOCATION = + DATA REQUIRED ' SCOPE = spfile;
ALTER system set log_archive_dest_2 =' LOCATION = R: OPTIONAL ' SCOPE = spfile;


with the same question.



The question is, how to set up the second location of the archivelogs, ASM storage?
or maybe someone has another idea how do to transfer/copy archivelogs to remote storage?
I have of course command "cp" on asmcmd tool, but it would be difficult to synchronize the source and target locations.			 I thhink you cannot use a drive mapped in the Windows environment. Search the metalink if there is a way to mount the drive.
The error says that the device is not accessible.
********************************
ERROR on line 1:
ORA-02097: the parameter cannot be changed because specified value is not valid
ORA-16032: parameter LOG_ARCHIVE_DEST_2 destination string cannot be translated.
ORA-09291: sksachk: invalid device specified for the destination of archive
OSD-04018: cannot access the specified directory or device.
S/O-error: (OS 3) the system cannot find the path specified.
**************************************
Try to use a local disk folder just to test and eliminate the issue mounted.
Let us know if on a local disk, the log_archive_dest_2 is working.sf
Edited by: ADaniel March 20, 2012 20:53

 
		 
          Maybe you are looking for 
           
            
		     Firefox is already running? 
			 After following the instructions to stop firefox in the Task Manager (he was not also running), I tried to find my profile. I followed the instructions by going to the Start button and entering % APPDATA%\Mozilla\Firefox\Profiles\, but could not find 
		    
            
		     HP Envy Phoenix 860-112nf: information for HP Envy Phoenix 860-112nf HW 
			 Hello I need detailed HW utilisateur5 my HP Envy Phoenix 860-112nf I need certain information such as: -What type of module of memory is necessary to upgrade to 16 GB? -Which USB ports are 2.0 or 3.0 -are there an IDE port to plug the old hard drive  
		    
            
		     launch Subvi in the background on target RT 
			 I would like to run a Subvi in the background on a RT of RIO target.  I did it in the past on the local computers by using references and knots, but not on the RT RIO target.  I need the vi to run in the background and transfer data to the main vi ru 
		    
            
		     I have a sony ericsson phone with data cable but cannot import pictures on pc 
			 I have a sony ericsson phone with data cable but cannot import pictures on pc 
		    
            
		     Need new version DLL File of speech 
			 Dragon Naturally head told me that windows speech DDL is version 2.0.210208 and I need the 4.0.4.2512 version for naturally Speeking to run correctly how can I fix this problem?

Database log mode	Fashion Archive
Automatic archiving	Activated
Destination of archive	+ ORAARCH