Quantcast
Channel: SCN: Message List - SAP MaxDB
Viewing all 2539 articles
Browse latest View live
↧

IOWait Deadlock 7.8.02.36

September 24, 2013, 5:08 am
$
0
0

I've got IOWait (R) (041) and IOwait (W) (044). Cant login into the database to do a restart for example.

Cant log a SAP call right now as I don't have the pw for the correct S-user available at the moment.

 

I know it means a data read/write deadlock, but how to fix it ?

 

List of suspend reasons:

========================

 

total suspends:  522238

 

Vwait          :       3 (   0.00% ) k53wait

IOWait(R)(041) :     100 (   0.02% ) b13get_node: await read              :-(

IOWait(W)(044) :       4 (   0.00% ) b13pfree_pno                         :-(

PagerWaitWritr :    5758 (   1.10% ) Pager_Controller::WaitForPagerWritReply

JobWait Redo   :       6 (   0.00% ) Rst_RedoManager::RedoLog

SVP-End  (230) :       1 (   0.00% ) Log_SavepointSync::LockSVPSyncEntry

NoRedoJob(231) :      12 (   0.00% ) Rst_RedoTrafficControl::ExecuteJobs()

LogIOwait(234) :   40378 (   7.73% ) Log_Queue::UserTaskEOTReady

SVP-wait (243) :       2 (   0.00% ) Log_Savepoint::StartSavepointAndWait

No-Work  (255) :  475974 (  91.14% ) Task is waiting for work

 

Environment:
NW 7.30 Java, MaxDB 7.8.02.036. Steps: SUM10SP08_06 patch preparation steps, Kernel 721_REL patch 100.

 

Thanks and Regards, Norbert

↧
Search

Re: IOWait Deadlock 7.8.02.36

September 24, 2013, 7:59 am
$
0
0

Maybe it is a 'dbmsrv' problem? I have looked at the attached 'x_cons' file, but there were not even any user tasks connected and I could not see any database activity - based on that a deadlock seems unlikely.

 

I would recommend to check the database log file 'KnlMsg' for errors and if there are none, then run a 'ps -afe | grep dbmsrv' to identify the running dbmsrv processes.

 

Thorsten

↧
↧

Re: SAP Content Server HA and load balancing

September 24, 2013, 9:18 am
$
0
0

Thank you Deepak,

 

the note clearly says.

 

At the moment there is no tool-supported cluster integration for the Content

Server databases.

 

I have done this for LC/Maxdb and it works, not sure how to get HA configured for Content Server.

 

Yogesh

↧

Re: IOWait Deadlock 7.8.02.36

September 24, 2013, 2:40 pm
$
0
0

Thanks for checking Torsten.

 

The issues started when we noticed a login via dbmcli was not possible, all login types were rejected.

The SAP system had been shutdown (gracefully), proably explains why there are no client connections.

 

Unusual entries in KernelMsg seem to start with a lot of connect/connection released
messages like this:

ask108  2013-09-24 15:57:31 CONNECT12633:  Connect req. (DSL, T108, connection obj. 0x8013a49b0, Node:'uan112-se', PID: 15922)
Thread 0x23CE Task108  2013-09-24 15:57:31 CONNECT12651:  Connection released (DSL, T108, connection obj. 8013a49b0)
Thread 0x23CE Task108  2013-09-24 15:58:36 CONNECT12633:  Connect req. (DSL, T108, connection obj. 0x8013a49b0, Node:'uan112-se', PID: 15922)
Thread 0x23CE Task108  2013-09-24 15:58:36 CONNECT12651:  Connection released (DSL, T108, connection obj. 8013a49b0)

 

 

Failed login like this:

ask168  2013-09-24 16:09:09 RTESec     2:  User control attempts to connect
                           2013-09-24 16:09:09 RTESec     0:  Authentication rejected
                           2013-09-24 16:09:09 RTESec     0:  Authentication method: SCRAMMD5V1
                           2013-09-24 16:09:09 RTESec     0:  Authentication rejected
                           2013-09-24 16:09:09 RTESec     0:  Authentication method: SCRAMMD5

 

We did restart the x_server a number of times.

 

Then an error occurs with the Watchdog

ask  -  2013-09-24 17:38:13 ERR RTEKernel125:  The watchdog process is no longer alive,_FILE=RTEKernel_StartupUnix+noPIC.cpp,_LINE=408

 

                                                                       ACTION:

 

                                                                       Contact your system administrator. Show him the error message which points to an operating system

 

and looks like the DB tries an emergency shutdown:

Thread 0x2391 Task  -  2013-09-24 17:56:21 RTEKernel114:  Caught STOP signal
Thread 0x2390 Task  -  2013-09-24 17:56:21 RTE    20225:  Database tries automatic shutdown
Thread 0x7A5E Task  -  2013-09-24 17:56:21 ERR RTE    20126:  Database automatic shutdown failed,_FILE=RTE_ExternalCall+noPIC.cpp,_LINE=937
Thread 0x2390 Task  -  2013-09-24 17:56:21 WNG RTEKernel121:  Kernel is being stopped in ONLINE state
Thread 0x2390 Task  -  2013-09-24 17:56:22 RTEKernel 61:  rtedump written to file 'rtedump'
Thread 0x2390 Task  -  2013-09-24 17:56:22 RunTime    3:  State changed from ONLINE to KILL
Thread 0x2390 Task  -  2013-09-24 17:56:22 RTEKernel111:  Tracewriter resumed
Thread 0x2390 Task  -  2013-09-24 17:56:22 RTEKernel 94:  Waiting for tracewriter to finish work
Thread 0x23C7 Task  3  2013-09-24 17:56:22 Trace  20000:  Start flush kernel trace
Thread 0x2390 Task  -  2013-09-24 17:56:22 RTEKernel116:  Tracewriter termination timeout: 60 seconds
Thread 0x23C7 Task  3  2013-09-24 17:56:22 Trace  20001:  Stop flush kernel trace
Thread 0x23C7 Task  3  2013-09-24 17:56:22 Trace  20002:  Start flush kernel dump
Thread 0x23C7 Task  3  2013-09-24 17:56:24 Trace  20003:  Stop flush kernel dump
Thread 0x23AE Task  -  2013-09-24 17:56:33 ERR RTEKernel125:  The watchdog process is no longer alive,_FILE=RTEKernel_StartupUnix+noPIC.cpp,_LINE=408

 

                                                                       ACTION:

 

                                                                       Contact your system administrator. Show him the error message which points to an operating system configuration error and then contact the database support if your system administrator can not fix the error.
Thread 0x23C7 Task  3  2013-09-24 17:56:39 RTEKernel110:  Releasing tracewriter
Thread 0x2390 Task  -  2013-09-24 17:56:39 TENANT 13008:  Requestor for tenant database DSL has stopped
Thread 0x2390 Task  -  2013-09-24 17:56:39 RTEThread 13:  The thread LegacyRequestor is finished
Thread 0x23B0 Task  -  2013-09-24 17:56:39 RTE    20214:  CONSOLE thread stopped
Thread 0x2390 Task  -  2013-09-24 17:56:39 RTEKernel 58:  Backup of diagnostic files will be forced at next restart
Thread 0x2390 Task  -  2013-09-24 17:56:39 RTEKernel118:  SERVERDB DSL has stopped
                           2013-09-24 17:56:39 RTEKernel 14:  Kernel version: Kernel7.8.02   Build 036-121-248-298
Thread 0x2390 Task  -  2013-09-24 17:56:39 RunTime    3:  State changed from KILL to STOPPED
Thread 0x2390 Task  -  2013-09-24 17:56:39 RTEThread 13:  The thread Requestor is finished
Thread 0x2390 Task  -  2013-09-24 17:56:39 TENANT 13005:  Tenant database DSL has stopped
Thread 0x2390 Task  -  2013-09-24 17:56:40 RTEKernel119:  Kernel aborts

 

The last entry in the KrnlMsg file was several hours before the x_cons suspends where noticed.

 

The running  dbmsrv processes are

uan112:sqddsl 1002> ps -ef |grep dbmsrv|grep DSL

sdb       5652  5651  0 Sep24 ?        00:00:05 /sapdb/DSL/db/pgm/dbmsrv -sdbstarter 3600 3600 A -P 0000000300000007000000080000000B

sdb      11302     1 94 Sep24 ?        13:45:32 /sapdb/DSL/db/pgm/dbmsrv -sdbstarter 3600 3600 A -P 0000000300000007000000080000000B

sdb      13644     1  4 07:37 ?        00:00:00 /sapdb/DSL/db/pgm/dbmsrv -P 0000000b0000000e0000000f00000012

sdb      13873     1  4 07:37 ?        00:00:00 /sapdb/DSL/db/pgm/dbmsrv -P 0000000b0000000e0000000f00000012

sdb      13978     1  4 07:37 ?        00:00:00 /sapdb/DSL/db/pgm/dbmsrv -P 0000000b0000000e0000000f00000012

 

As the DB seems to be down I might kill them later and try to start the DB from scratch.

↧

Re: IOWait Deadlock 7.8.02.36

September 25, 2013, 4:32 am
$
0
0

Hmm, I would suggest creating a SAP OSS ticket for this. I think we would need to look at the Database Analyzer log files plus the error protocol files like KnlMsg, dbm.prt...

OS connection would help plus the exact time when you noticed that logon via dbmcli did not work any more.

Have you checked the OS log file e.g. /var/log/messages (Linux)?

 

Thorsten

↧
↧

MaxDb Parameter to be increased? - 1027504

September 25, 2013, 4:58 am
$
0
0

Hi All,

 

 

As per the note 1027504 i have to increase the InterpreterWorkStackSize to 262136 bytes, When i check the parameters in MaxDb Studio 7.9  for increasing the parameter value its not listed.

 

Any Idea?

 

Warm Regards,

Sudhakar G

↧

Re: MaxDb Parameter to be increased? - 1027504

September 25, 2013, 2:20 pm
$
0
0

Hello Mr Sudhakar,

 

 

What is the version of MaxDB software ?

 

If you are using database studio to change the parameter, go to

 

Administration -> Command Line (Tab)

 

Run:

(depending on the version of MaxDB installed, one of these should work)

 

param_directget _WORKSTACK_SIZE

                        

                         (OR)

 

param_directget InterpreterWorkStackSize

 

 

To change the parameter value, use the command

 

param_directput <parameter_name> <value>

 

This parameter can only be changeable in OFFLINE mode, so you need to restart the instance for the changes to take effect.

 

Regards,

Yashwanth

↧

Re: MAXDB in Hotbackup mode ?

September 25, 2013, 2:31 pm
$
0
0

Hello Tony,

 

I am not sure about hot-backup mode in oracle, but MaxDB do have "High Availability" solutions to minimize the downtime:

 

One among these solutions is "Hot Standby"

 

Hot Standby:

With Hot Standby, SAP MaxDB/liveCache reduces the downtime to a few seconds during the switch to the second host. With Hot Standby, a database works on a second host with a separate data area. In standby operation, the database reads logentries immediately from the log area of the master and redoes them. After the transfer, the former standby database continues working with the log of the master. The data area of the standby database is automatically initialized using a flash copy or a symclone copy. A cluster agent monitors the master and automatically switches to standby if the master is not available.

 

If you are a SAP customer, refer to the SAP Note- 952783 - FAQ: SAP MaxDB high availability

for different MaxDB high availability solutions

 

Also refer Doc:

 

http://maxdb.sap.com/doc/7_7/44/c36eb3865960efe10000000a155369/content.htm

 

 

Regards, Yashwanth

↧
Search

Re: Emergency shutdown problem

September 26, 2013, 5:41 am
$
0
0

Hi Thorsten,

disabling the UseSharedSQL-parameter seems to fix the problem so far. Since 3 weeks the database keeps running :-)

↧
↧

Re: How to take MaxDB 7.7 backup on Windows Network share drive through DBMGUI

November 13, 2013, 9:51 am
$
0
0

Hello KLNR,

 

When you create the medium definition for the backup to a network location, make sure you use the complete UNC path \\hostname\directory\filename
instead of mapped network drive (eg: M:\)

 

In addition refer to SAP Note: 1377148 FAQ: SAP MaxDB backup/recovery (Section 21)

Also refer to SAP Note: 85736 for additional requirements.

 

Regards, Yashwanth

↧

Re: How to take MaxDB 7.7 backup on Windows Network share drive through DBMGUI

November 14, 2013, 5:03 am
$
0
0

Hi Yaswanth,

 

Thanks for your prompt response.

 

1) I am not getting what is UNC, but I am taking backup to the network path (Netapp directory): \\NETAPP01\SAPbackup\SID_Backup\SID_COM9 ( I believe I followed complete UNC path)


2) I have gone through the note 85736 and the below are the solution points mentioned in the note and actions I did

 

a) The owner of the database service (sapservice<SID> or <SID>adm) must be known on the target host

I am not getting this point, what to do for this??? We are trying to take backup on Netapp directory (\\NETAPP01).

 

Both hosts should belong to one domain.

Both hosts on the same domain

 

b) The owner must be determined for the database service. User ID and the password of the database user are provided in the Control Panel -> Services for service ADABAS:<SID> or MaxDB:<SID> under 'This Account'

Bo

Earlier the Database service MaxDB: <SID> and Xserver started with a local system and now I have changed to: <SID>adm and maintained the password

 

c) I have changed the parameter USE_BACKUP_SECURITY_DESCRIPTOR to NO

 

Still backup is not success giving same error. Please suggest us.

 

Thanks and Regards

KLNR

 

 

 

 

 

 



↧

Re: How to take MaxDB 7.7 backup on Windows Network share drive through DBMGUI

November 14, 2013, 11:53 pm
$
0
0

Hi All,

 

Can anybody help on this to resolve this....

 

Thanks and Regards

KLNR

↧

Re: Download from the download-site not working?

November 15, 2013, 1:45 am
$
0
0

Are there no ftp accounts or something else to download the latest linux x86_32bit version?

 

Would be helpful to get the installers right now.

 

Is there no solution to get the files?

 

regards

sebastiano

↧
↧

Re: Download from the download-site not working?

November 15, 2013, 4:36 am
↧

Re: MaxDB install on Ubnutu 10.04 Lucid

November 15, 2013, 5:17 am
$
0
0

I think you are all riht, but on Ubuntu 13.X the libs: png and tiff are not in /usr/lib, they are in /usr/lib/i386/linux/gnu/lib*

 

so symlinking to the correct files(alt. search with find)

should help you.

 

regards

sebastiano

↧
Search

Re: How to take MaxDB 7.7 backup on Windows Network share drive through DBMGUI

November 15, 2013, 10:53 am
$
0
0

Hello KLNR,

 

Are you using the <sid>adm OS user to run the backup ? Check if the <sid>adm OS user have write access to this network location. Check if the OS user running the backup is in the SDB Operators group.

 

If you still having problem, please open a CSS ticket and attach the database logs to the message. Run DBM command diag_pack and attach the 'diagpack.tgz' file generated under the run directory to the CSS ticket.

 

Regards, Yashwanth

↧

Better approach to migrate 7.6 to 7.8 on a new Linux machine

November 16, 2013, 3:39 am
$
0
0

Hi,

 

I have an old machine with CentOS 5 and MaxDB 7.6 64bits community edition, and I plan to install a new machine with CentOS 6.4 and MaxDB 7.8 64bits, what is the better approach for this type of migration?

 

  1. Install MaxDB 7.6 on new machine, restore backup and upgrade to 7.8?
  2. Install MaxDB 7.8 on new machine and use loader with data that was exported from 7.6?
  3. Install MaxDB 7.8 on new machine and restore backup from 7.6? (this one I dont know if works)
  4. Install MaxDB 7.6 on new machine, restore backup, upgrade to 7.7 then upgrade to 7.8?

 

backup was made with follow command:

 

backup_start completeF MIGRATION

 

analyzing some threads on forum I think that the better approach was the number 4, but I like more the approach 3.

 

thanks for any tip.

↧
↧

Re: Better approach to migrate 7.6 to 7.8 on a new Linux machine

November 16, 2013, 4:49 am
$
0
0

I don't remember this in detail but isn't it possible to simply restore the 7.6 backup on 7.8?

I know there was the special backup for migration option in older versions but I'm not sure that was still required for 7.6 -> 7.8.

 

To make sure everything works as expected why not simply try it on a test installation?

 

Regards,

Simon

↧

Installing sap trial 7.02-import abap taking long time?

November 16, 2013, 12:56 pm
$
0
0

Hi everyone

 

Im installing the abap trial 7.02 Its has been installing it for 9 hours and its on ``import abap`` step.im not sure its still running or not?Do u have any suggestions for me?

 

Is this possible to take long time like 9 hours or more?

↧

Re: Installing sap trial 7.02-import abap taking long time?

November 17, 2013, 11:09 pm
$
0
0
Hi KUTAY BEKTAS,

 

We request you to provide your system configuration here and we give  good solution for you.

 

Are you using the installation any Real time server or your desktop pc or In virtual machine..?

 

 

Thanks

K.Mahendran

↧
Viewing all 2539 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>