Navaneeth's Blog

Tuesday, April 3, 2012

Standby database redo transfer by different modes

Redo transferred by different modes to standby database:

   Here in the standby database, if realtime apply is enabled, the redo data will be applied from the redolog file directly before archiving.Otherwise it will be archived and after it will be applied to the standby database.

And the redo applying(either by block wise or SQL wise) will be differed based on the physical and logical standby database.

1.Using Archiver Processes (ARCn) to Archive Redo Data

By default, redo transport services use ARCn processes to archive the online redo log files on the primary database. ARCn archival processing supports only the maximum performance level of data protection in Data Guard configurations. You must use the LGWR process to transmit redo data to standby locations that operate in other data protection modes.

Archiving to Local Destinations Before Archiving to Remote Destinations

2.Using the Log Writer Process (LGWR) to Archive Redo Data

You can optionally enable redo transport services to use the LGWR process to transmit redo data to remote destinations.

Using the LGWR process differs from ARCn processing (described in Section 5.3.1), because instead of waiting for the online redo log to switch at the primary database and then writing the entire archived redo log at the remote destination all at once, the LGWR process selects a standby redo log file at the standby site that reflects the log sequence number (and size) of the current online redo log file of the primary database. Then, as redo is generated at the primary database, it is also transmitted to the remote destination. The transmission to the remote destination will either be synchronous or asynchronous, based on whether the SYNC or the ASYNC attribute is set on the LOG_ARCHIVE_DEST_n parameter. Synchronous LGWR processing is required for the maximum protection and maximum availability modes of data protection in Data Guard configurations. 

 LGWR SYNC Archival to a Remote Destination with Standby Redo Log Files

Thanks & Regards,

Navaneeth

Wednesday, March 28, 2012

Command to disable or enable firewall

netsh firewall set opmode mode = mode 

Mode = enable or disable

Thank you

Regards,

Navaneeth

Rename a datafile in the primary and propogate the changes to the standby database

Rename a datafile in the primary database and manually propagate the changes to the standby database.

PRIMARY

1. Set STANDBY_FILE_MANAGEMENT=MANUAL on both Primary and Standby Database. 

SQL> show parameter standby_file_manag

NAME                                 TYPE        VALUE

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

standby_file_management              string      AUTO

SQL> col value format a50

SQL>  select name,value from v$parameter where name like 'db_unique_name';

NAME               VALUE

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

db_unique_name   orcl11g

SQL>

SQL> alter system set standby_file_management=MANUAL;

System altered.

SQL>  show parameter standby_file

NAME                                 TYPE        VALUE

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

standby_file_management              string      MANUAL

2. Take the Tablespace offline on the Primary Database: 

SQL> select * from v$tablespace;

       TS# NAME                           INC BIG FLA ENC

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

         0 SYSTEM                         YES NO  YES

         1 SYSAUX                         YES NO  YES

         2 UNDOTBS1                       YES NO  YES

         4 USERS                          YES NO  YES

         3 TEMP                           NO  NO  YES

         6 FDB                            YES NO  YES

6 rows selected.

SQL> alter tablespace users offline;

Tablespace altered.

3. Rename Datafile on Primary Site: 

   copy the file using OS command to the new location

4. Rename the Datafile in the Primary Database. 

SQL> alter tablespace users rename datafile 'D:\app\nvcob\oradata\orcl11g\USERS01.DBF' TO 'D:\app\nav6cob\oradata\orcl11g_1\USERS01.DBF';

Tablespace altered.

5. Bring the Tablespace back online: 

SQL> ALTER TABLESPACE USERS ONLINE;

Tablespace altered.

SQL> ALTER SYSTEM SWITCH LOGFILE;

System altered.

SQL>

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

STANDBY 

SQL> alter system set standby_file_management=MANUAL;

System altered.

SQL> select name,value from v$parameter where name like 'db_unique_name';

NAME                                                                             VALUE

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

db_unique_name                                                                   11gstdby

SQL> show parameter standby_file

NAME                                 TYPE        VALUE

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

standby_file_management              string      MANUAL

SQL>

1. Stop Redo Apply on Standby Database.

SQL> recover managed standby database cancel;

Media recovery complete.

2. Shutdown the Standby Database.

SQL> shutdown immediate

ORA-01109: database not open

Database dismounted.

ORACLE instance shut down.

3. Move the Datafile to the new location at the Standby site.

Copy the file using OS command to the new location.

4. Start and mount the Standby Database.

SQL> startup mount

ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance

ORACLE instance started.

Total System Global Area  535662592 bytes

Fixed Size                  1375792 bytes

Variable Size             209715664 bytes

Database Buffers          318767104 bytes

Redo Buffers                5804032 bytes

Database mounted.

5.Rename the Datafile in the Standby Database control file. 

SQL> alter database rename file 'D:\app\nav6cob\oradata\11gstdby\USERS01.DBF' to 'D:\app\nav6cob\oradata\11gstdby_1\USERS01.DBF';

Database altered.

6. On the Standby Database, restart Redo Apply: 

SQL> recover managed standby database disconnect from session;

Media recovery complete.

7. Set STANDBY_FILE_MANAGEMENT=AUTO on both Primary and Standby Database. 

SQL> alter system set standby_file_management=auto;

System altered.

SQL> show parameter standby_file

NAME                                 TYPE        VALUE

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

standby_file_management              string      AUTO

SQL>  select file#,name from v$datafile where name like '%USERS%';

     FILE# NAME

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

          4 D:\APP\NAV6COB\ORADATA\11GSTDBY_1\USERS01.DBF

SQL>

Oracle export/import done from Higher to lower version

Export :

[oracle@HN300949l ~]$ expdp test/test DUMPFILE=test10092011.dmp DIRECTORY=EXPDP SCHEMAS=test version=10.2.0.1

Export: Release 11.2.0.1.0 - Production on Mon Oct 10 12:52:15 2011

Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production

With the Partitioning, OLAP, Data Mining and Real Application Testing options

Starting "TEST"."SYS_EXPORT_SCHEMA_01": test/******** DUMPFILE=test10092011.dmp DIRECTORY=EXPDP SCHEMAS=test version=10.2.0.1

Estimate in progress using BLOCKS method...

Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA

Total estimation using BLOCKS method: 55.68 MB

Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA

Processing object type SCHEMA_EXPORT/TYPE/TYPE_SPEC

Processing object type SCHEMA_EXPORT/TABLE/TABLE

Processing object type SCHEMA_EXPORT/TABLE/INDEX/INDEX

Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/CONSTRAINT

Processing object type SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS

Processing object type SCHEMA_EXPORT/TABLE/COMMENT

Processing object type SCHEMA_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS

. . exported "TEST"."DEDUPLICATE_TAB" 9.552 MB 1000 rows

. . exported "TEST"."NOCOMPRESS_TAB" 9.552 MB 1000 rows

. . exported "TEST"."KEEP_DUPLICATES_TAB" 9.552 MB 1000 rows

. . exported "TEST"."COMPRESS_TAB" 9.552 MB 1000 rows

. . exported "TEST"."SF_TAB" 5.335 KB 1 rows

. . exported "TEST"."BF_TAB" 5.335 KB 1 rows

. . exported "TEST"."MY_CUSTOMERS" 6.335 KB 1 rows

. . exported "TEST"."TEST" 6.382 KB 1 rows

. . exported "TEST"."OUTER_NTAB" 0 KB 0 rows

. . exported "TEST"."INNER_NTAB" 0 KB 0 rows

. . exported "TEST"."STU_TAB" 0 KB 0 rows

. . exported "TEST"."PER_TAB" 0 KB 0 rows

. . exported "TEST"."TIME_TABLE" 0 KB 0 rows

Master table "TEST"."SYS_EXPORT_SCHEMA_01" successfully loaded/unloaded

******************************************************************************

Dump file set for TEST.SYS_EXPORT_SCHEMA_01 is:

/u01/app/oracle/test10092011.dmp

Job "TEST"."SYS_EXPORT_SCHEMA_01" successfully completed at 12:57:30

****************************************** -----------------------------------------------------------*********************************************************

Import :

D:\oracle\product\10.2.0\db_1\BIN>

D:\oracle\product\10.2.0\db_1\BIN>impdp 'sys/database as sysdba' directory=DATA_PUMP_DIR dumpfile=test10092011.dmp

Import: Release 10.2.0.1.0 - Production on Monday, 10 October, 2011 13:50:20

Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production

With the Partitioning, OLAP and Data Mining options

Master table "SYS"."SYS_IMPORT_FULL_01" successfully loaded/unloaded

Starting "SYS"."SYS_IMPORT_FULL_01": 'sys/******** AS SYSDBA' directory=DATA_PUMP_DIR dumpfile=test10092011.dmp

Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA

Processing object type SCHEMA_EXPORT/TYPE/TYPE_SPEC

Processing object type SCHEMA_EXPORT/TABLE/TABLE

Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA

. . imported "TEST"."DEDUPLICATE_TAB" 9.552 MB 1000 rows

. . imported "TEST"."NOCOMPRESS_TAB" 9.552 MB 1000 rows

. . imported "TEST"."KEEP_DUPLICATES_TAB" 9.552 MB 1000 rows

. . imported "TEST"."COMPRESS_TAB" 9.552 MB 1000 rows

. . imported "TEST"."SF_TAB" 5.335 KB 1 rows

. . imported "TEST"."BF_TAB" 5.335 KB 1 rows

. . imported "TEST"."MY_CUSTOMERS" 6.335 KB 1 rows

. . imported "TEST"."TEST" 6.382 KB 1 rows

. . imported "TEST"."OUTER_NTAB" 0 KB 0 rows

. . imported "TEST"."INNER_NTAB" 0 KB 0 rows

. . imported "TEST"."STU_TAB" 0 KB 0 rows

. . imported "TEST"."PER_TAB" 0 KB 0 rows

. . imported "TEST"."TIME_TABLE" 0 KB 0 rows

Processing object type SCHEMA_EXPORT/TABLE/INDEX/INDEX

Processing object type SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS

Processing object type SCHEMA_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS

Job "SYS"."SYS_IMPORT_FULL_01" successfully completed at 13:51:04

Regards,

Navaneeth

Oracle DB cloning Simple steps using RMAN

   1) Install Oracle Home software on new server. Make the Oracle Home directory structure same as old server.

2) Create an Oracle Service same as on old server from OS prompt:

cd \bin

set ORACLE_SID=

oradim -new -sid %ORACLE_SID% -intpwd MYSECRETPASSWORD -startmode M

3) Configure listener on new server using netca utility from OS prompt.

4) Create/check same directory structure on new server for controlfiles, datafiles, redo logfiles, dump files, networking files like sqlnet.ora, tnsnames.ora, listener.ora. This information can be obtained as follows on old server:

conn / as sysdba

select member from v$logfile ;

select name from v$datafile ;

For rest of the files (e.g. controfiles, dump/trace,log files), see parameter file on old server.

5. copy the backup files to the same location which RMAN access it from.

      5.1 Startup nomount using pfile (taken backup)

6. Restore controlfile from backup

7. restore database

8. open database

Reagrds,

Navaneeth 

Thursday, March 22, 2012

Simple RMAN Script for Creating Standby database

RMAN Script for creating standby database:

run {

   allocate channel prmy1 type disk;

    allocate channel prmy2 type disk;

    allocate channel prmy3 type disk;

    allocate channel prmy4 type disk;

    allocate auxiliary channel stby type disk;

    duplicate target database for standby from active database

    spfile

        parameter_value_convert 'orcl','orclsby1'

        set db_unique_name='orclsby1'

        set db_file_name_convert='/orcl/','/orclsby1/'

        set log_file_name_convert='/orcl/','/orclsby1/'

        set control_files='/u01/app/oracle/oradata/orclsby1.ctl'

        set log_archive_max_processes='5'

        set fal_client='orclsby1'

        set fal_server='orcl'

        set standby_file_management='AUTO'

        set log_archive_config='dg_config=(orcl,orclsby1)'

        set log_archive_dest_1='service=orcl ASYNC 

valid_for=(ONLINE_LOGFILE,PRIMARY_ROLE) db_unique_name=orcl';

     }

Adding standby redologs in standby database:

alter database add standby logfile

('/u01/app/oracle/oradata/orcl/srl01.log',

'/u01/app/oracle/oradata/orcl/srl02.log',

'/u01/app/oracle/oradata/orcl/srl03.log',

'/u01/app/oracle/oradata/orcl/srl04.log')

size 52428800

/

Regards,

Navaneeth

Standby recovery done in production environment 9i

http://dbaspot.com/forums/oracle-server/71881-physical-standby-database-cannot-close-gap-if-any-gap-exists.html

'ORA-00280: change 3220290269 for thread 1 is in sequence #17219
ORA-00278: log file 'D:\ORADATA\sys8\ARCHIVE\LOG_1_17218.ARC' no longer needed for this recovery

ORA-00279: change 3220290274 generated at 04/11/2010 19:03:32 needed for thread 1
ORA-00289: suggestion : D:\ORADATA\sys8\ARCHIVE\LOG_1_17220.ARC
ORA-00280: change 3220290274 for thread 1 is in sequence #17220
ORA-00278: log file 'D:\ORADATA\sys8\ARCHIVE\LOG_1_17219.ARC' no longer needed for this recovery

ORA-00279: change 3220300520 generated at 04/11/2010 23:27:08 needed for thread 1
ORA-00289: suggestion : D:\ORADATA\sys8\ARCHIVE\LOG_1_17221.ARC
ORA-00280: change 3220300520 for thread 1 is in sequence #17221
ORA-00278: log file 'D:\ORADATA\sys8\ARCHIVE\LOG_1_17220.ARC' no longer needed for this recovery

ORA-00279: change 3220300533 generated at 04/11/2010 23:27:16 needed for thread 1
ORA-00289: suggestion : D:\ORADATA\sys8\ARCHIVE\LOG_1_17222.ARC
ORA-00280: change 3220300533 for thread 1 is in sequence #17222
ORA-00278: log file 'D:\ORADATA\sys8\ARCHIVE\LOG_1_17221.ARC' no longer needed for this recovery

ORA-00279: change 3220304453 generated at 04/12/2010 01:05:52 needed for thread 1
ORA-00289: suggestion : D:\ORADATA\sys8\ARCHIVE\LOG_1_17223.ARC
ORA-00280: change 3220304453 for thread 1 is in sequence #17223
ORA-00278: log file 'D:\ORADATA\sys8\ARCHIVE\LOG_1_17222.ARC' no longer needed for this recovery

ORA-00279: change 3220304456 generated at 04/12/2010 01:05:53 needed for thread 1
ORA-00289: suggestion : D:\ORADATA\sys8\ARCHIVE\LOG_1_17224.ARC
ORA-00280: change 3220304456 for thread 1 is in sequence #17224
ORA-00278: log file 'D:\ORADATA\sys8\ARCHIVE\LOG_1_17223.ARC' no longer needed for this recovery

ORA-00279: change 3220429248 generated at 04/12/2010 09:49:53 needed for thread 1
ORA-00289: suggestion : D:\ORADATA\sys8\ARCHIVE\LOG_1_17225.ARC
ORA-00280: change 3220429248 for thread 1 is in sequence #17225
ORA-00278: log file 'D:\ORADATA\sys8\ARCHIVE\LOG_1_17224.ARC' no longer needed for this recovery

ORA-00308: cannot open archived log 'D:\ORADATA\sys8\ARCHIVE\LOG_1_17225.ARC'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.

SQL>
SQL> recover standby database until cancel;
ORA-00279: change 3220429248 generated at 04/12/2010 09:49:53 needed for thread 1
ORA-00289: suggestion : D:\ORADATA\sys8\ARCHIVE\LOG_1_17225.ARC
ORA-00280: change 3220429248 for thread 1 is in sequence #17225

Specify log: {=suggested | filename | AUTO | CANCEL}
AUTO
ORA-00279: change 3220572194 generated at 04/12/2010 10:46:06 needed for thread 1
ORA-00289: suggestion : D:\ORADATA\sys8\ARCHIVE\LOG_1_17226.ARC
ORA-00280: change 3220572194 for thread 1 is in sequence #17226
ORA-00278: log file 'D:\ORADATA\sys8\ARCHIVE\LOG_1_17225.ARC' no longer needed for this recovery

ORA-00279: change 3220627014 generated at 04/12/2010 11:06:36 needed for thread 1
ORA-00289: suggestion : D:\ORADATA\sys8\ARCHIVE\LOG_1_17227.ARC
ORA-00280: change 3220627014 for thread 1 is in sequence #17227
ORA-00278: log file 'D:\ORADATA\sys8\ARCHIVE\LOG_1_17226.ARC' no longer needed for this recovery

ORA-00279: change 3220627289 generated at 04/12/2010 11:06:51 needed for thread 1
ORA-00289: suggestion : D:\ORADATA\sys8\ARCHIVE\LOG_1_17228.ARC
ORA-00280: change 3220627289 for thread 1 is in sequence #17228
ORA-00278: log file 'D:\ORADATA\sys8\ARCHIVE\LOG_1_17227.ARC' no longer needed for this recovery

ORA-00279: change 3220763002 generated at 04/12/2010 12:27:59 needed for thread 1
ORA-00289: suggestion : D:\ORADATA\sys8\ARCHIVE\LOG_1_17229.ARC
ORA-00280: change 3220763002 for thread 1 is in sequence #17229
ORA-00278: log file 'D:\ORADATA\sys8\ARCHIVE\LOG_1_17228.ARC' no longer needed for this recovery

ORA-00279: change 3220899620 generated at 04/12/2010 13:24:57 needed for thread 1
ORA-00289: suggestion : D:\ORADATA\sys8\ARCHIVE\LOG_1_17230.ARC
ORA-00280: change 3220899620 for thread 1 is in sequence #17230
ORA-00278: log file 'D:\ORADATA\sys8\ARCHIVE\LOG_1_17229.ARC' no longer needed for this recovery

ORA-00279: change 3221036980 generated at 04/12/2010 14:44:50 needed for thread 1
ORA-00289: suggestion : D:\ORADATA\sys8\ARCHIVE\LOG_1_17231.ARC
ORA-00280: change 3221036980 for thread 1 is in sequence #17231
ORA-00278: log file 'D:\ORADATA\sys8\ARCHIVE\LOG_1_17230.ARC' no longer needed for this recovery

ORA-00279: change 3221165247 generated at 04/12/2010 16:11:07 needed for thread 1
ORA-00289: suggestion : D:\ORADATA\sys8\ARCHIVE\LOG_1_17232.ARC
ORA-00280: change 3221165247 for thread 1 is in sequence #17232
ORA-00278: log file 'D:\ORADATA\sys8\ARCHIVE\LOG_1_17231.ARC' no longer needed for this recovery

ORA-00279: change 3221302585 generated at 04/12/2010 17:30:15 needed for thread 1
ORA-00289: suggestion : D:\ORADATA\sys8\ARCHIVE\LOG_1_17233.ARC
ORA-00280: change 3221302585 for thread 1 is in sequence #17233
ORA-00278: log file 'D:\ORADATA\sys8\ARCHIVE\LOG_1_17232.ARC' no longer needed for this recovery

ORA-00279: change 3221437356 generated at 04/12/2010 18:37:11 needed for thread 1
ORA-00289: suggestion : D:\ORADATA\sys8\ARCHIVE\LOG_1_17234.ARC
ORA-00280: change 3221437356 for thread 1 is in sequence #17234
ORA-00278: log file 'D:\ORADATA\sys8\ARCHIVE\LOG_1_17233.ARC' no longer needed for this recovery

ORA-00279: change 3221499410 generated at 04/12/2010 19:02:44 needed for thread 1
ORA-00289: suggestion : D:\ORADATA\sys8\ARCHIVE\LOG_1_17235.ARC
ORA-00280: change 3221499410 for thread 1 is in sequence #17235
ORA-00278: log file 'D:\ORADATA\sys8\ARCHIVE\LOG_1_17234.ARC' no longer needed for this recovery

ORA-00279: change 3221499630 generated at 04/12/2010 19:03:02 needed for thread 1
ORA-00289: suggestion : D:\ORADATA\sys8\ARCHIVE\LOG_1_17236.ARC
ORA-00280: change 3221499630 for thread 1 is in sequence #17236
ORA-00278: log file 'D:\ORADATA\sys8\ARCHIVE\LOG_1_17235.ARC' no longer needed for this recovery

ORA-00279: change 3221663610 generated at 04/12/2010 20:36:12 needed for thread 1
ORA-00289: suggestion : D:\ORADATA\sys8\ARCHIVE\LOG_1_17237.ARC
ORA-00280: change 3221663610 for thread 1 is in sequence #17237
ORA-00278: log file 'D:\ORADATA\sys8\ARCHIVE\LOG_1_17236.ARC' no longer needed for this recovery

ORA-00279: change 3221809532 generated at 04/12/2010 21:37:13 needed for thread 1
ORA-00289: suggestion : D:\ORADATA\sys8\ARCHIVE\LOG_1_17238.ARC
ORA-00280: change 3221809532 for thread 1 is in sequence #17238
ORA-00278: log file 'D:\ORADATA\sys8\ARCHIVE\LOG_1_17237.ARC' no longer needed for this recovery

ORA-00279: change 3221951748 generated at 04/12/2010 22:41:44 needed for thread 1
ORA-00289: suggestion : D:\ORADATA\sys8\ARCHIVE\LOG_1_17239.ARC
ORA-00280: change 3221951748 for thread 1 is in sequence #17239
ORA-00278: log file 'D:\ORADATA\sys8\ARCHIVE\LOG_1_17238.ARC' no longer needed for this recovery

ORA-00279: change 3222098577 generated at 04/12/2010 23:39:32 needed for thread 1
ORA-00289: suggestion : D:\ORADATA\sys8\ARCHIVE\LOG_1_17240.ARC
ORA-00280: change 3222098577 for thread 1 is in sequence #17240
ORA-00278: log file 'D:\ORADATA\sys8\ARCHIVE\LOG_1_17239.ARC' no longer needed for this recovery

ORA-00279: change 3222248037 generated at 04/13/2010 00:55:46 needed for thread 1
ORA-00289: suggestion : D:\ORADATA\sys8\ARCHIVE\LOG_1_17241.ARC
ORA-00280: change 3222248037 for thread 1 is in sequence #17241
ORA-00278: log file 'D:\ORADATA\sys8\ARCHIVE\LOG_1_17240.ARC' no longer needed for this recovery

ORA-00279: change 3222264966 generated at 04/13/2010 01:05:47 needed for thread 1
ORA-00289: suggestion : D:\ORADATA\sys8\ARCHIVE\LOG_1_17242.ARC
ORA-00280: change 3222264966 for thread 1 is in sequence #17242
ORA-00278: log file 'D:\ORADATA\sys8\ARCHIVE\LOG_1_17241.ARC' no longer needed for this recovery

ORA-00279: change 3222265468 generated at 04/13/2010 01:06:02 needed for thread 1
ORA-00289: suggestion : D:\ORADATA\sys8\ARCHIVE\LOG_1_17243.ARC
ORA-00280: change 3222265468 for thread 1 is in sequence #17243
ORA-00278: log file 'D:\ORADATA\sys8\ARCHIVE\LOG_1_17242.ARC' no longer needed for this recovery

ORA-00279: change 3222405780 generated at 04/13/2010 02:19:18 needed for thread 1
ORA-00289: suggestion : D:\ORADATA\sys8\ARCHIVE\LOG_1_17244.ARC
ORA-00280: change 3222405780 for thread 1 is in sequence #17244
ORA-00278: log file 'D:\ORADATA\sys8\ARCHIVE\LOG_1_17243.ARC' no longer needed for this recovery

ORA-00308: cannot open archived log 'D:\ORADATA\sys8\ARCHIVE\LOG_1_17244.ARC'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.

SQL> disc
Disconnected from Oracle9i Enterprise Edition Release 9.2.0.7.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.7.0 - Production
SQL> conn / as sysdba
Connected.
SQL>
SQL> set pages 100
SQL> set lines 1000
SQL>
SQL> select sequence#,archived,applied,deleted from v$archived_log where completion_time like '12-APR-10%';

SEQUENCE# ARC APP DEL
---------- --- --- ---
     17222 YES YES NO
     17223 YES YES NO
     17224 YES YES NO
     17225 YES YES NO
     17226 YES YES NO
     17227 YES YES NO
     17228 YES YES NO
     17229 YES YES NO
     17230 YES YES NO
     17231 YES YES NO
     17232 YES YES NO
     17233 YES YES NO
     17234 YES YES NO
     17235 YES YES NO
     17236 YES YES NO
     17237 YES YES NO
     17238 YES YES NO
     17239 YES YES NO

18 rows selected.

SQL> select sequence#,archived,applied,deleted from v$archived_log where completion_time like '13-APR-10%';

SEQUENCE# ARC APP DEL
---------- --- --- ---
     17240 YES YES NO
     17241 YES YES NO
     17242 YES YES NO
     17243 YES YES NO

SQL> select sequence#,archived,applied,deleted from v$archived_log where completion_time like '13-APR-10%';

SEQUENCE# ARC APP DEL
---------- --- --- ---
     17240 YES YES NO
     17241 YES YES NO
     17242 YES YES NO
     17243 YES YES NO
     17244 YES NO NO

SQL> select sequence#,archived,applied,deleted from v$archived_log where completion_time like '13-APR-10%';

SEQUENCE# ARC APP DEL
---------- --- --- ---
     17240 YES YES NO
     17241 YES YES NO
     17242 YES YES NO
     17243 YES YES NO
     17244 YES NO NO
     17245 YES NO NO

6 rows selected.

SQL> select sequence#,archived,applied,deleted from v$archived_log where completion_time like '13-APR-10%';

SEQUENCE# ARC APP DEL
---------- --- --- ---
     17240 YES YES NO
     17241 YES YES NO
     17242 YES YES NO
     17243 YES YES NO
     17244 YES NO NO
     17245 YES NO NO

6 rows selected.

SQL> select sequence#,archived,applied,deleted from v$archived_log where completion_time like '13-APR-10%';

SEQUENCE# ARC APP DEL
---------- --- --- ---
     17240 YES YES NO
     17241 YES YES NO
     17242 YES YES NO
     17243 YES YES NO
     17244 YES NO NO
     17245 YES NO NO

6 rows selected.

SQL> select sequence#,archived,applied,deleted from v$archived_log where completion_time like '13-APR-10%';

SEQUENCE# ARC APP DEL
---------- --- --- ---
     17240 YES YES NO
     17241 YES YES NO
     17242 YES YES NO
     17243 YES YES NO
     17244 YES YES NO
     17245 YES YES NO

6 rows selected.

SQL> select sequence#,archived,applied,deleted from v$archived_log where completion_time like '13-APR-10%';

SEQUENCE# ARC APP DEL
---------- --- --- ---
     17240 YES YES NO
     17241 YES YES NO
     17242 YES YES NO
     17243 YES YES NO
     17244 YES YES NO
     17245 YES YES NO

6 rows selected.

SQL> exit
Disconnected from Oracle9i Enterprise Edition Release 9.2.0.7.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.7.0 - Production

C:\Documents and Settings\Administrator>

Regards,
Navaneeth