Thanks for update Javier.
You may close the thread now.
Regards,
Deepak Kori
↧
Re: RUN_RSAIMMERGE_TRANSFER: Long runtime during upgrade to EhP7 MaxDB
↧
Re: SAP content server - Migration as well upgrade
Hi Deepak ,
Thanks for the answer.
Regards,
Prem
↧
↧
"Bad resume count detected" MaxDB 7.5
RHEL3update4 - 2.4 kernel in VM.
MaxDB 7.5.0.55
SAP Ent. 4.7 (6.40)
For the life of me I can't figure this out. Installed a system and restored from backup, the SAP system (4.7) runs for almost exactly 11 days and then crashes. In the knldiag.err file I get the message "T(some task #) Bad Resume Count Detected:138 (usually over 100)" I've tried upgrading the build to 55 for 7.5, with the same results. Only the DB crashes and not the SAP instance. The stack back trace seems to reference it being a kernel issue but I cannot seem to see what's going on.
I did see an SAP Note about this: http://maxdb.sap.com/webpts?wptsdetail=yes&ErrorType=0&ErrorID=1141905
It seems as though it might have to do with savepoints in the system, but I'm not sure where to begin regarding that. Maybe it's a parameter change I have to make?
We are unable to upgrade MaxDB any further due to lack of support contract and the legacy system of which this is installed. It should be worth noting I have a current system that's got the same CPU/Memory setup and I've tried to equalize the parameters to match but for some reason this *new one seems to crash where the other does not. Lastly, these are all running in VMs.
Help help is GREATLY appreciated (I know the setup is antiquated).
Chris
↧
Unable to view the status of DB in Database studio
Dear All,
I am trying to manage a standby server's MaxDB from Database studio, when i click on administration icon in studio i couldn't get the database details. In Progress tab i see Waiting status for all refreshing view to Overview, Data area, log area. It was working properly few days back, suddenly this happened. Please share your thoughts on this.
Note: I face the same issue when i try to access on host as well.
↧
Re: Unable to view the status of DB in Database studio
Hi Kathik,
Please check whether x_server is running or not MaxDB server. If possible restart x_server and check the results again.
Regards,
Deepak Kori
↧
↧
Re: "Bad resume count detected" MaxDB 7.5
Hi,
http://maxdb.sap.com/webpts?wptsdetail=yes&ErrorType=0&ErrorID=1141905
MaxDB PTS - Problem Tracking - Error 1141904: Kernel
Known bugs it seems like there is MaxDB patch to apply.
To apply patches for this you could follow:
1020175 - FAQ: SAP MaxDB installation, upgrade or applying a patch.
Sorry I cannot be of more help not a MaxDB expert
Kind Regards,
Johan
↧
Huge Memory Consumption
Hello Everyone,
I have been checking a maxdb system and can see huge memory consumption occurring:
top - 12:29:10 up 842 days, 2:59, 5 users, load average: 18.59, 17.80, 11.77
Tasks: 728 total, 2 running, 723 sleeping, 0 stopped, 3 zombie
Cpu(s): 8.5%us, 0.7%sy, 0.0%ni, 88.8%id, 0.3%wa, 0.0%hi, 0.3%si, 1.4%st
Mem: 47509M total, 47129M used, 379M free, 210M buffers
Swap: 20479M total, 1475M used, 19004M free, 5386M cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
26644 sdb 20 0 39.8g 38g 306m S 126 82.3 52654:06 kernel
7136 sdb 20 0 77304 16m 4692 S 8 0.0 1:12.69 dbmsrv
2860 root 20 0 0 0 0 S 3 0.0 2837:24 nfsiod
208 root 20 0 0 0 0 S 2 0.0 2448:01 rpciod/2
I could not see any long running db transactions, background jobs, deadlocks
Please provide any valuable inputs on how to check the issue further
Regards,
Vinay
↧
Re: Huge Memory Consumption
Hello Vinay,
what are you wondering about?
That the database uses 82.3% of the memory?
In MAXDB there exists a parameter called:
CACHE_SIZE (MaxDB < 7.7.03) respectively CacheMemorySize (MaxDB >= 7.7.03)
"The value specifies the i/o capable memory used by different
MaxDB components in particular the data cache, converter and
the shared catalog cache."
When the database starts it allocates the memory given by the parameter. This memory is reserved for the db. It will not become free if there is no activity on the db.
See also:
MaxDB Memory Sizing - MaxDB - SCN Wiki
Regards,
Michael
↧
Re: maxdb database studio 7.9 error in installation
Thanks Kim,
Your solution worked for me too. I had same issue 
↧
↧
How to stop maxDB consistent (Windows)
Hi experts,
I've one question, if we would like to make a snapshot of a server the DB needs to be consistent.
Is it therefore enough to stop the DB via DB Studio (set offline) or are there further services which I need to stop?
Like at sybase, there you also need to stop some services.
Thank you
↧
Re: How to stop maxDB consistent (Windows)
Hi Christian,
Snapshot of MaxDB server can be taken in ONLINE or ADMIN state, please check this
http://wiki.scn.sap.com/wiki/x/LB4B
regards
kartik
↧
Re: How to stop maxDB consistent (Windows)
But I am talking about a VM-Snap.
↧
Installation of MaxDB/LiveCache
Hi experts,
I need to install on our Solution Manager Host (HP-UX ia64) the MaxDB/LiveCache host, as I want to connect the DB of a SAP-System to DBACOCKPIT/Technical Monitoring.
Does somebody know, where I can find this software?
Thank you
↧
↧
Re: Installation of MaxDB/LiveCache
Hi Christian,
Your requirement is to have additional MaxDB database on the same server where solution Manager is running. This is need to configure remote DB monitoring from solution manager.
Is my understanding correct ?
Regards,
Deepak Kori
↧
Re: Installation of MaxDB/LiveCache
Hi Deepak,
yes, I want to configure the remote DB monitoring.
I want to connect the MaxDB of an other SAP System to the Solman.
But as the Solman has Sysbase ASE it seems as I have to install the MaxDB/LiveCache.
Kind regards
↧
Re: Installation of MaxDB/LiveCache
Hi Christian,
For downloading MaxDB you may refer below link
MaxDB Software Download Area now via SAP Store
Once the MaxDB is installed refer below SAP note for dbacockpit configuration
Note 1371928 - DBA Cockpit: SAP MaxDB/liveCache as remote database
Hope this helps.
Regards,
Deepak Kori
↧
SWPM asks for too much space at installation
Hello,
I'm trying to install ECC 6.0 EHP 7 SR1 with the most up to date SWMP on Windows with MaxDB.
At the step "Install Instance basics of ASCS01" the system raises the following error
"There is not enogh available space in 'F:/'. There are 143118 MB available. The required space is 230400 MB."
F:\ is the future backup partition, so I didn't put anything there.
My question: Where does the vale 230400 MB come from? Do I have a chance to change it during the installation?
Your help is very much appreciated.
↧
↧
Re: SWPM asks for too much space at installation
Hi Julian,
For installation of ERP 6.0 EHP7 with MaxDB database you may require DB space of around 230 GB.
This is derived based on the export DVDs used for the installation and this cannot be changed.
Please ensure enough space exists in the Drive used for installation.
Hope this helps.
Regards,
Deepak Kori
↧
Re: How to stop maxDB consistent (Windows)
Hi Christian,
I think your question is best addressed at VM / OS level. In general, if the VM snapshot guarantees that the I/O is consistent after the snapshot, then you probably should be fine (but this is at your own risk...).
If you are an SAP customer, have a look at SAP note 616814 discussing the MaxDB 'suspend logwriter' command used for cases when the OS / storage system cannot ensure a consistent point in time image.
Thorsten
↧
Re: "Bad resume count detected" MaxDB 7.5
Hi Chris,
hmm, there are two related bug fixes in our "problem tracking database", which are
- PTS1142584 (autosave_end suspends wrong task if autosave is running, fixed in 2009 with MaxDB 7.6.06).
- PTS1208411 (kernel crash, because resume count of 345 is out of range of the allowed 0-1 value, fixed in 2012 with 7.6.06.24).
But unfortunately for you these fixes were only downported to 7.6 and no correction was done for 7.5.
If you attach the callstack here, I can let you know if your crash indeed matches a known issue e.g. here is the callstack from PTS1208411:
2009-11-10 15:07:22
T71 Bad resume count detected:345
Symbolic Stack Back Trace 0: eo670_CTraceStackOCB
1: vabort
2: en56_StoreResumer_17_3
3: en56_remvresume
4: NextScheduledTask__21RTETask_TaskSchedulerFv
5: vsuspend
6: Suspend__12RTETask_TaskFUi
7: Run__13SrvTasks_TaskFv
8: Kernel_NonUserTask__FR13RTETask_ITaskR13Trans_ContextR20SAPDBErr_MessageList
9: Kernel_Main__FR13RTETask_ITask
10: RTETask_TaskMain
11: en88_CallKernelTaskMain__FP9TASK_TYPE
12: en88_CallCoroutineKernelTaskMain
...
Thorsten
↧