Hello,
Check the error message in KnlMsg file.
You could connect to DB using database studio & check the logs, initialize the database and change the parameters at param init step, if it will be needed.
Regards, Natalia Khlopina
Hello,
Check the error message in KnlMsg file.
You could connect to DB using database studio & check the logs, initialize the database and change the parameters at param init step, if it will be needed.
Regards, Natalia Khlopina
Hi,
2) I only care that this log file won't grow more and increase the size of my VM. I checked the note you sent me, but I didn't figure out how to really decrease the size of this file -> the size of the log file is related to the log configuration. When you installed the database you were configuring the space for the log file -> check with Database Analyzer your log configuration -> log area - here you'll find the size you configured for your log area.
You can use Q&A number 8 of the log note 869267 to decrease the size of the log area.
3) table DOMAIN.VERSIONS - is a database system table which is not available in SAP data Dictionary - it is not a mismatch between SAP DDIC and Database. It looks like the CCMS ABAP coding is not correct for database version 7.6 -> please check as Christian already wrote note 382312 - check which basis support package you are using ->
SAP MaxDB Version 7.6: The adjustments are provided in Basis Support Package 10.
is necessary to run 640 with MaxDb version 7.6.
Regards, Christiane
My backup script doesn't work with dbmcli version 7.9.08.10.
If you store your MaxDB data sets on NetApp-Filer volumes you can use NetApp-Snapshots to backup them. Since MaxDB version 7.8 this is supported by MaxDB with device type EXTERNAL.
After creating an new backup template (e.g. NETAPP) with device type EXTERNAL you can use the dbmcli commands
"backup_start NETAPP DATA"
and
"backup_finish NETAPP ExternalBackupID $SNAPSHOT"
The first command "backup_start NETAPP DATA" tells maxdb to do a savepoint and take a temporay MaxDB snapshot. Now you can backup the database with operating system tools e.g. draw a NetApp-Filer snapshot. The second dbmcli command registers the backup in the backup history list and deletes the temporay MaxDB snapshot.
Unfortunatly you have to submit the two dbmcli commands within the same database session. This is no problem if you do the backup of your MaxDBs in dialog mode. But if you want to script the backup you need to sumbit the NetApp snapshot command from within one dbmcli session between backup_start and backup_finish. I have done it until now with a HERE script:
dbmli -Uc -d <SID> >/dev/null 2>&1 <-HERE
db_connect
backup_start NETAPP DATA
!ssh sapfiler snap create dbvol $SNAPSHOT
backup_finish NETAPP ExternalBackupID $SNAPSHOT
db_release
quit
HERE
Earlier versions of MaxDB knew the statement "exec_command". This is long gone. But the undocumented feature "!" to start os commands survived in dbmcli until 7.9.08.05. Now they declared this bitter needed feature to a security risk. Since 7.9.08.06 you get an error (unkown command).
Searching for a solution I tried the "background_server" commands. But they only usable in dialog mode.
Any suggestions?
Regards
Günter Hoeth
Hello,
how does I activate E-Mail Sending in Event Dispatcher (MAXDB) when the Event LogAboveLimit raises ? I am getting the following error during Activating:
Execution of program "sdbmail "<subject>Test</subject> <body
onKeyDown='return KeyDown();' onKeyUp='KeyUp();'>The
database name is H98</body>
<recipient>hartwig.latz@hydac.com</recipient>"" not allowed
Execution of program "sdbmail "<subject>Test</subject> <body
onKeyDown='return KeyDown();' onKeyUp='KeyUp();'>The
database name is H98</body>
<recipient>hartwig.latz@hydac.com</recipient>"" not allowed
(See also Screenshot)
I use the following Syntax for sdbmail:
sdbmail "<subject>Test</subject> <body onKeyDown='return KeyDown();'
onKeyUp='KeyUp();'>The database name is H98</body>
<recipient>hartwig.latz@hydac.com</recipient>"
How can Sending of E-Mails be established with event Dispatcher of
MAXDB ?
Kind Regards
Hartwig Latz
DANKE, Christiane !!
This solved the problem !!! Thank GOD I had to install only one SP, which turned out to be really cumbersome, as the import wasn't starting and I was getting some ridiculous tp errors. Here is the
solution, in case somebody shall stumble over this too:
cd /usr/sap/trans/bin and execute tp connect SID pf=TP_DOMAIN_SID.PFL
Mmmh, does no one knows how to get to the bottom of this issue? At the moment the database crashes at least once a week on our production server. The MaxDB installation on our test infrastructure remains stable, so it's maybe related to some performance things.
At the bug report #1242614 nothing happens :-(
Hello Sven,
after migration to the version 7.7.07.33 this problem didn't occurred again. So, my advice is, to use newest 7.7.x.x version of MaxDB instead of 7.8.x.x.
Best regards, Dusan
Hi Günter,
you are right - MaxDB does not support executation of external commands via DBMCLI ! anymore because of security reasons.
Regards, Christiane
Hi Christiane,
I understand the security risk - but SAP cannot give up important functionality for backup without supplying an alternative. Since 7.8 MaxDB supports I/P consitent EXTERNAL snapshots:
db_connect
backup_start <template_name>
<create the IO consistent Snapshot clone>
backup_finish <template_name> ExternalBackupID <external_backup_ID>
db_release
Now these snapshots are not longer possible. We need to start an external script from within dbmcli.
You have already a concept for that: Events are allowed to start scripts which are listed in dbm_whitelist.cfg.
Regards Günter
Hello Günter,
use the pyton script belo with the sapdb.dbm interface and call it with
x_python -d <SID> -u CONTROL,CONTROL
Kind regards,
Burkhard
#!/usr/bin/env python
import sys
import string
import optlib
import sapdb.dbm
import os
def _options ():
return [
('n', 'host' , ':', 'localhost' , 'specifies servernode'),
('d', 'dbname' , ':', 'SDB' , 'specifies the database name'),
('u', 'userpwd' , ':', 'DBM,DBM' , 'specifies user and password'),
]
def main (options, args):
session = sapdb.dbm.DBM (options.host, options.dbname, '', options.userpwd)
result = session.cmd('backup_start NETAPP DATA')
os.system('ssh sapfiler snap create dbvol $SNAPSHOT')
result = session.cmd('backup_finish NETAPP ExternalBackupID $SNAPSHOT')
if __name__ == "__main__":
optlib.optMain2 (main, _options ())
Reason for the error was that the Central- & Dialog Instance of the SCM server have been installed
on both cluster nodes already. With this the Livecache client software has been installed and a registry key “SAP DB Tech” exists.
This registry key prevents sapinst from performing the required installation steps for the Livecache software.
The workaround in this case was to delete the registry key. After that sapinst completed the installation successfully.
Finally, this confirmed my first guess that something in the overall installation procedure is not correct.
It’s better to install the Livecache before you install central- or dialog instance on the same server.
SAP already updated the following notes: 1710950, 1083639, 1651606.
And they will also update the installation documentation for the next Livecache releases accordingly.
As we hit this issue in a MSCS environment I would also recommend to follow this procedure in a single server setup.
Hello,
I am trying to fetch rows from MaxDB with limit and offset. However, I cannot use the offset syntax found at http://help.sap.com/saphelp_erp60_sp/helpdata/de/40/1312152fa511d3a98100a0c9449261/content.htm.
I am able to fetch e.g. result 1 to 15 by using "limit 15", but if I try to get result 15 to 30 by using "limit 15,15" i get the following error:
"Error Executing 'Processing result rows' SAP DBTech JDBC: [-7085]: Function not allowed for this cursor.[-7085]: Function not allowed for this cursor"
Could my SQL syntax contain errors, or does MaxDB not support the use of offset with the limit clause?
My MaxDB Version is 7.6.06.03.
Hello Burkhard,
thanks for your script. Never work with python before but I tried to start it. Had to call x_python it with full path even after setting the environement with .dbenv.sh. Now I get an ImportError: No module named sapdb.dbm.
I searched the whole volume /sapdb for such a module but could not find one.
Regards
Günter
Hello Günter,
my fault. The module name has been changed from sapdb to sdb.
Change in the script the strings sapdb.dbm to sdb.dbm. It occures twice.
If you like to know from where python loads the modules you can use
x_python
>>> import sdb.dbm
>>> sdb.dbm
<module 'sdb.dbm' from 'D:\sapdb\clients\D73\lib\python2.3\sdb\dbm.pyd'
Kind regards,
Burkhard
I'm experiencing issue while trying to stablish a linked connection from sqlserver to maxDB using ODBC
What I've done:
1. I downloaded the 32bits driver for MaxDb ODBC from Here!
2. Installed the driver and by typing the command "odbcad32" on command prompt (or going to controla panel/administrative tools/ODBC Data sources) I got this following window after I added the SAP DB odbc data source:
3. With the above setup, in theory the ODBC datasource for a maxDB connection shold be ready.
4. Then I went to excel and created a connection using this pre-configured ODBC datasource and it worked
5. The next step was SQL Server and the creation of a liked connection..I went to SqlServer management studio and tried to stablish a connection to maxDB using the pre-configured ODBC datasource and I wasnt able to get it working. I've tried several things but nothing worked out for me. The following image shows how the linked connection was tried to be setup and gave then the following error:
The above gave me the following error:
Then I tried to force a login with no look, getting the same error above:
Please any advice ??
Thanks in advance,
Ruben
Hi Alberto, I know this is al old post but thing is you experienced the same issue I'm dealing with right now.
I just created the ODBC connection correctly but there is no way for me to successfully create the linked connection to that ODBC data source. I've tried several things but there is no way for me to get this working, I got same error like you, the #7399 one.
Please what did you meant with:
I have the connection tested and running, without errors: I had to force the authentication before actually creating it.
Looks like someway you forced the authentication for the ODBC datasource..how did you do that ?
Thanks in advance for any help
Hi Christiane,
thank alot for your reply.
unfortunately we are not a SAP customer.
Our x-CIO was an x-SAP Employee! he brought MaxDB to us and then let us alone with it.
i have started the Database Analyzer but coulndt find anything unusuall, there is 3 Warrings but not more.
thanks alot
regards
Hello Richard, Deepak,
I'm facing the exact same problem.
MaxDB 7.9 is indeed not released for ERP 6.0 EHP5 on windows server X64 (dixit PAM).
How did you solve the problem?
Kr,
Adam
Edward PlaisanceThank you, thank you, thank you!
Hello Burkhard,
now I get following error:
/sapdb/J06/db/bin/x_python -d J06 -u CONTROL,CONTROL
Traceback (most recent call last):
File "J06", line 5, in ?
import sdb.dbm
ImportError: /sapdb/J06/db/lib/python2.3/sdb/dbmmodule.so: undefined symbol:
_ZN20RTEIPC_ObjectManager8InstanceEv
By the way: There is no subdirectory "python2.3" in the MaxDB clients path at our site:
find /sapdb/* -name "*python*"
/sapdb/J06/db/bin/x_python
/sapdb/J06/db/pgm/python
/sapdb/J06/db/lib/python2.3
/sapdb/J06/db/lib/python23.zip
We are working with SLES11SP2 (64-bit). The python version is python-2.6.8-0.15.1.
sdbregview -l
Installation: Global /sapdb/programs
Global Listener 7.9.08.03 valid 64 bit
Installation Compatibility 7.9.08.03 valid 64 bit
Installer 7.9.08.03 valid
SAP Utilities Compatibility 7.9.08.03 valid 64 bit
Installation: J06 /sapdb/J06/db
Base 7.9.08.03 valid 64 bit
DB Analyzer 7.9.08.03 valid 64 bit
Database Kernel 7.9.08.03 valid 64 bit
Fastload API 7.9.08.03 valid 64 bit
JDBC 7.6.06.09 valid
Loader 7.9.08.03 valid 64 bit
Messages MSG 0.10302 valid
ODBC 7.9.08.03 valid 64 bit
Redist Python 7.9.08.03 valid 64 bit
SAP Utilities 7.9.08.03 valid 64 bit
SQLDBC 7.9.08.03 valid 64 bit
SQLDBC 76 7.6.06.22 valid 64 bit
SQLDBC 77 7.9.08.03 valid 64 bit
Server Utilities 7.9.08.03 valid 64 bit
Installation: CL_J06 /sapdb/clients/J06
Base 7.9.08.03 valid 64 bit
Fastload API 7.9.08.03 valid 64 bit
JDBC 7.6.06.09 valid
Messages MSG 0.10302 valid
ODBC 7.9.08.03 valid 64 bit
SAP Utilities 7.9.08.03 valid 64 bit
SQLDBC 7.9.08.03 valid 64 bit
SQLDBC 76 7.6.06.22 valid 64 bit
SQLDBC 77 7.9.08.03 valid 64 bit
Kind regards
Günter