Quantcast
Channel: SCN : Discussion List - SAP on Oracle
Viewing all articles
Browse latest Browse all 1892

problem with oracle

$
0
0

Hello all

 

I have problem with oracle 11 in Suse. We try upgrade Suse from 11.1 to Suse 11.2. Our scenario is:

 

We install new system (SLES for SAP Applications  11.2 (x86_64)) and copy all file from old  SAP system on Sles system (10). All OS setting is copy from 11.1 to 11.2. We use this scenario in all other systems, and work property (on ERP, EP, XI dev & test), but not in this system (prodution XI on NW 7.0).

So, after copy all file from orginal system to new one we start oracle, but oracle not working properly, after some time, its crash. I found that the problem is when system try switch logfile (in original system its working correct). See steps to reproduce crash:

 

SQL> startup

ORACLE instance started.

Total System Global Area 2472083456 bytes

Fixed Size                  2230792 bytes

Variable Size             872416760 bytes

Database Buffers         1577058304 bytes

Redo Buffers               20377600 bytes

Database mounted.

Database opened.

SQL> alter system switch logfile;

System altered.

SQL> alter system switch logfile;

System altered.

SQL> alter system switch logfile;

System altered.

SQL> alter system switch logfile;

 

and now oracle do nothing, system can't finish this step. When I shutdown oracle in abort mode (in other system can't stop), on OS level I have still working proces ora_lgwr, which I can't kill, because this process wait for I/O (I think for disk write).

I have snapshot for this installation, and I tried to do different trials (change OS limits, change size/number of redo log, change redolog destination, change block size in dysk) and  always system crash.

On alert log, I can not find anything interesting, on OS level the same.

 

Anybody can help me ?

 

Best regards

Paweł


Viewing all articles
Browse latest Browse all 1892

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>