cancel
Showing results for 
Search instead for 
Did you mean: 

Error 19502 Closing archive log file

Former Member
0 Kudos

Hi ,

System : Solution manager installed on Linux with Oracle database

below are the details from the trace file . I could not login to SAP application.Database is in open state.

      • 2009-07-09 06:28:02.853 60408 kcrr.c

ARCH: Error 19502 Closing archive log file '/oracle/SM1/oraarch/SM1arch1_3373_662815273.dbf'

      • 2009-07-09 06:28:02.853 58670 kcrr.c

kcrrfail: dest:1 err:19502 force:0 blast:1

ORA-16038: log 4 sequence# 3373 cannot be archived

ORA-19502: write error on file "", blockno (blocksize=)

ORA-00312: online log 4 thread 1: '/oracle/SM1/origlogB/log_g14m1.dbf'

ORA-00312: online log 4 thread 1: '/oracle/SM1/mirrlogB/log_g14m2.dbf'

what could have happened , there were no maintenace/backup acitivity recently .

Thanks & Regards

ganesh

Accepted Solutions (0)

Answers (7)

Answers (7)

Former Member
0 Kudos

Ganesh first try to start ur system in No archive log mode. once it has started and u r abel to login with SAP then read the different error logs. i think by this u will get batter picture because once a system is in working mode or do function we will get exact error.

Thanks

presu

Former Member
0 Kudos

Hi All --

The issue could be with File system mount points .Below is the

error when i had run BRTOOLS -->Check database.

ORA-27091: unable to queue I/O

ORA-27072: File I/O error

Linux-x86_64 Error: 22: Invalid argument

Additional information: 4

Additional information: 1

Additional information: -1

The above error logs relates to note number 914177.

STEP1: Can you please let me know what are consequences if we do a

remount of /oracle with notail option .

What are the prerequiste steps do we need to take ?

STEP2 :Secondly i observed the parameter "FILESYSTEMIO_OPTIONS = setall " from initSID.ora .

Can you please suggest what should be the right value for this parameter (either ASYNCH or NONE)? Oracle is 10g

Can you also please confirm that do we need to make perform step1&2 changes or Only Step2 is enough inorder to overcome these Errors

Thanks & Regards

Ganesh

Former Member
0 Kudos

Sample steps

su -root

cd /etc

cp fstab fstabbackup

vi fstab

A sample entry for HPUX

/dev/vgapp/lvol1 /oracle vxfs rw,suid,largefiles,delaylog,datainlog 0 2

-- Suman

sunny_pahuja2
Active Contributor
0 Kudos

Hi Ganesh,

Check SAP Note 391 - Archiver stuck

Thanks

Sunny

stefan_koehler
Active Contributor
0 Kudos

Hello Ganesh,

which file systems do you use for the archive log file system?

If you use ReiserFS without the "notail" mount option you can get these problems.

It is described in metalinknote #399764.1

Regards

Stefan

Former Member
0 Kudos

Hi Stefan,

File system is reiserfs and I could see that Oracle is not mounted with option "notail " .

Unfortunatlely , I could not acess the note from metalink

Note 399764.1 Title: Newly created Oracle database on Reiser filesystem - archiver

Can you please let me know what are consequences if we do a remount of /oracle from /etc/fstab.

Please provide me the steps to perform this task.

Cheers

ganesh

stefan_koehler
Active Contributor
0 Kudos

Hello Ganesh,

thanks for the additional information with the error "Linux-x86_64 Error: 22: Invalid argument".

Then i am sure that this problem is pointing to the ReiserFS mount option problem.

If you can't read the metalinknote .. SAP describes the same in sapnote #914177 for the error "Error: 22: Invalid argument".

Just follow the steps from this sapnote.

The only problem is that you need to create/recreate these file systems again. I have seen this issue on sapdata<X>, origlog<X>, mirrlog<X>, saparch and <ORACLE_HOME>. I would recreate all these file systems with the notail option (we are running SAP on SLES with notail option and with file system I/O option "SETALL").

Regards

Stefan

Former Member
0 Kudos

Hi,

First Check archive log directory space then restart

or run below command

SQL>alter system archive log current;

Surendra Jain

Former Member
0 Kudos

A common reason for this kind of error messages:

Your oraarch directory might be full.

Former Member
0 Kudos

Thanks a ton it worked for me

cheers !

Former Member
0 Kudos

Hi Ganesh,

Just stop and start your sap and db once,every thing will be ok.

Regards

Ashok Dalai