Hello Elke,
you are absolutly right. There is a endless loop.
But I don't see eny reason for it.
My result is OK into correct treelevel (I have nodes in levels 1,2,3).
And then there is added level 4 the same as level 2,
level 5 the same as level 3, ...
The manual says:
"It is ensured, however, tha
Sven Köhler wrote:
we recompiled with NPTL on Sles9 without modification on thread
coding and it works (only two processes left ;-), but such a version
would not run on Sles8 or other Linux versions, that use a non NPTL
enhanced kernel.
In other words: if the NPTL-people would compile MaxDB ins
Hi,
Currently we are backing up every hour.
Due to a type of failure we had recently where memory in our db server
failed and DELETED some database config files and some data files I do all
backups for MIGRATION.
Currently I am backing up complete once per night, and incremental every
hour, but
Hi,
Rather than adjust settings, and crash sometimes to get the settings I need,
I have just directly applied the settings below, as the setup sounds very
similar to mine.
Copy into sysctl.conf, sysctl -p /etc/sysctl.conf
Using ipcs -l then gives me
-- Shared Memory Limits
max num
Hi,
Does this happen after a backup?
-Original Message-
From: Donatas Ciuksys [mailto:[EMAIL PROTECTED]
Sent: Friday, 4 June 2004 12:46 AM
To: [EMAIL PROTECTED]
Subject: JDBC error: restart required
Hi,
I'm using MaxDB 7.5.00.12, JDBC driver 7.5.01.00, Apache jakarta DBCP
(database
we recompiled with NPTL on Sles9 without modification on thread coding and it works (only two processes left ;-), but such a version would not run on Sles8 or other Linux versions, that use a non NPTL enhanced kernel.
In other words: if the NPTL-people would compile MaxDB instead of using
the pre-
Hello All,
I have done extensive searching for the answer to this question but keep
getting different answers.
Does MaxDB 7.5.0.12 and above have XA support?
I have heard that the JDBC driver is faking it, it is supported, and it
is not supported.
Thanks,
Dan
--
MaxDB Discussion Mailing Lis
Hi all.
I have weird problem here with the loader. Installed:
Linux SuSE 8.2, SAPDB 7.4.3.32. Sample database create
script fails on load_systab: "loader.LoaderError:
loader.LoaderError: [-25004] A connection to the
database could not be established: 1 = unknown host
(see /etc/hosts)."
Same thing
Hi,
we recompiled with NPTL on Sles9 without modification on thread coding and it works
(only two processes left ;-), but such a version would not run on Sles8 or other Linux
versions, that use a non NPTL enhanced kernel.
Not only the user level internal structures of 'linuxthread' and 'NPTL'
Hello Donatas,
the JDBC is possibly not the culprit, it only detects that the database instance
seems down ...
Could you look into the knldiag file of the instance
(http://sapdb.2scale.net/moin.cgi/knldiag)
whether there is something that looks suspicious around the time that error happens,
or
> I know there is the LD_ASSUME_KERNEL workaround for use MaxDB
> with nptl-enabled systems, and I have been using it successfully.
> But is there some plan to allow it to run in nptl systems
> without this workaround? I know there is some methods to
> detect in runtime if the system have or not
Hi,
I know there is the LD_ASSUME_KERNEL workaround for use MaxDB with
nptl-enabled systems, and I have been using it successfully.
But is there some plan to allow it to run in nptl systems without this
workaround? I know there is some methods to detect in runtime if the system
have or not nptl, m
Deadlockdetecktion and "tab_share" locks resulting from foreign keys...
Below a little example how easy it is to produce a deadlock:
Table and Data structure:
--
/*
PARENT
| |
| |
CHILD1 CHILD2
*/
DROP TABL
Hi there,
we are trying to restore a sapdb 7.3.0.28 with the following script :
#/bin/sh
DBMUSER=user
DBMPASS=password
SID=E01
dbmcli -d $SID -uUTL $DBMUSER,$DBMPASS -u $DBMUSER,$DBMPASS << EOF
db_start
util_connect $DBMUSER,$DBMPASS
util_execute init config
util_connect $DBMUSER,$DBM
> What prompted you to increase the settings in sysctl.conf?
> Was it problems similar to mine? Or prior knowledge/documents?
Since we have many sessions connecting to the database (5 application
servers) we also ran in a similiar problem. Decreasing the number of work
processes connecting helped
Hi,
This means, when I have the following backup parts
/*
FULLBACKUP
LOGSAVE 1
LOGSAVE 2
LOGSAVE 3
[...]
LOGSAVE n
INCRBACKUP
LOGSAVE 10
[...]
LOGSAVE 19
*/
..., I need to restore: FULLBACKUP + INCRBACKUP + LOGSAVE 10 .. 19
Regards, Timo
Heinrich, Tilo wrote:
Hello Timo,
But why does 'backup_histo
Hi,
Thanks, your backup settings are similar to mine. I will keep this in mind.
What prompted you to increase the settings in sysctl.conf? Was it problems
similar to mine? Or prior knowledge/documents?
Regards
Michael Andrewes
-Original Message-
From: Döhr, Markus ICC-H [mailto:[EMAIL
We're running also 8 GB DB Server (SAP) with the following settings in
/etc/sysctl.conf
# Kernel settings (for SAP R/3)
#
kernel.shmmax=4113682943
kernel.sem=4096 512000 1600 2048
kernel.msgmax=16384
kernel.shmall=4113682943
kernel.msgmni=1024
vm.heap-stack-gap=256
Shared memory and IPC parameter
sysctl: interesting, thanx
On Thu, 2004-06-03 at 12:06, Jean-Michel OLTRA wrote:
>
> bonjour,
>
>
> Le jeudi 03 juin 2004, Filip Sergeys a écrit...
>
>
> > You have to either recompile your kernel with to correct values or write
> > an rc script that sets the correct values at boot time
Hello Timo,
>But why does 'backup_history_list -r LAST' also report the log files
>between main backup and incremental backup, e.g.
because 'backup_history_list -r LAST' lists all backups starting at the last complete
backup.
Best Regards,
Tilo Heinrich
SAP Labs Berlin
>-Original Message-
Hi,
You segments, max number of arrays, etc is much larger than mine (4x xeon
HThreading cpu, 8 gig).
What is a standard output of your ipcs -u ?
Here's mine, as current during standard operation, and incremental backup.
(8:44 here now so I'll adjust the values tomorrow)
-- Shared Memory St
Hi,
thanks for this answer but there are the same results
about 40 sec to connect to maxdb !!!
As compared with a MSSQL-Server on the same host ( connect time about 2
sec )
tom
"Mensing, Joerg" <[EMAIL PROTECTED]>
03.06.2004 08:41
An: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED
bonjour,
Le jeudi 03 juin 2004, Filip Sergeys a écrit...
> You have to either recompile your kernel with to correct values or write
> an rc script that sets the correct values at boot time.
man sysctl.conf
CONFIG_SYSCTL=y in kernel configuration
--
jm
--
MaxDB Discussion Mailing
Hi Christoph,
Christoph Weser [mailto:[EMAIL PROTECTED] wrote:
>
> But now I detected a new issue with it:
>
> When loading an image in jpeg-format, he cuts the file off.
> The original image has a size of around 81KB. When it is in
> the DB and I
> make an export to a file using the SQL Studio
Hi to all
We are working for a porting from Oracle to MaxDB. Inside our project there are a lot
of query with data comparison through the to_date function and we use the DD/MM/
date format, on the contrary MaxDB uses the ISO format -MM-DD.
We don't want to change the date format at the ap
Hi,
I've tried to restoer a database with a log files, e.g.
/*
db_admin
util_connect
util_execute INIT CONFIG
medium_put data /space/data200405211800 file data
medium_put logs /space/log file log
recover_start data data
recover_start logs log 012
recover_replace logs /space/log.013
[...]
recover_re
with 8 gig of ram the value in shmmax corresponds to: 12884901888
Remember that values manually set in the /proc system are not retained
per reboot.
You have to either recompile your kernel with to correct values or write
an rc script that sets the correct values at boot time.
Regards,
Filip
On
Ok I reproduces the Deadlock.
the behaviour I described below is a fact.
this means:
update parenttable set primarykeyfield=10,otherfields=... where primarykeyfield=10;
...will result in "temp" "tab_share" locks on all child tables.
(and it doesn't matter that in fact the value of primarykeyfie
Hello everybody.
I waited for a fix in the repmcli. In version 7.4.3.32 it came.so far so
good.
But now I detected a new issue with it:
When loading an image in jpeg-format, he cuts the file off.
The original image has a size of around 81KB. When it is in the DB and I
make an export to a fil
correction, shmmax is the shared memory setting, not the semaphores.
the semaphore settings are in /proc/sys/kernel/sem
the command ipcs can provide you some more information
ipcs -l shows you the limits (for the semaphores, the information is
retrieved from /proc/sys/kernel/sem)
ipcs -u shows y
Hi,
I have 8 gig of ram, the current size is shmmax is 33554432, or 32 meg, at
1.5 would this be 24 meg?
What would you suggest I set this to?
I am doinng regular nightly backups (around 2 gig now, was 10-15 before the
major crash).
Hourly incremental, overwriting the existing file (copying off s
H [mailto:[EMAIL PROTECTED]:
>
> Odd Timestamp default problem - the default works when my insert statement
> is short, a longer one however does not work.
>
> In Case 1 the timestamp column named "recordcreated" works fine...
>
> In Case 2 it does not why? The only difference is the numbe
I believe it is in the shmmax file.
cd /proc/sys/kernel
echo xxx > shmmax #where xxx is 1,5 x the RAM size in bytes.
However it does noet hurt if you take a much higher number. It has no
performance impact.
Greets,
Filip
On Thu, 2004-06-03 at 09:33, Michael Andrewes wrote:
> Hi,
>
> I
Hi,
I'm unfamiliar with the term semaphores in regards to my operating system
(redhat linux 7.3).
I've googled and can see they are used for controlling concurrent access to
memory/resource, but am unfamiliar with how
To allocate more, or if it would actually assist my problem.
Could you please
34 matches
Mail list logo