cancel
Showing results for 
Search instead for 
Did you mean: 

7.5.00.23 (x64) on Scientific Linux 5.5 (x64)

Former Member
0 Kudos

I would appreciate any assistance you might lend to the problem I am have as explained below.. thanks in advance.

I need to get our maxdb instance running on a virtual machine. I have installed the same maxdb version package (listed above) on scientific linux (x64) as is installed on our current server (SuSE 9.1 x64) and a run of sdbverify shows all is well.

[root @ host]# /etc/init.d/sapdb start

The software appears to start and run fine but when I try to add it to my server list in dbmgui I get "-4 session released".

Trying to create a database instance using the dbmcli I get the following:

****************************************************************

[root @ host]# dbmcli db_create SOMEDB someuser,somepass

DBM-Api error ( -4'Reading header from pipe:(0:NO ERROR(0))')

****************************************************************

Below is the output of the xserver log file when I enable debug level 9. (Sensitive info was <snipped>)

****************************************************************

-


Date Time PID Typ MsgID Label Message-Text

-


2010-09-30 13:30:03 3077 12902 XSERVER started, 'X64/LINUX 7.5.0 Build 023-123-087-292'

2010-09-30 13:30:03 3077 12904 XSERVER Service port is 7210

2010-09-30 13:30:03 3077 12922 ENVIRON Command line arguments

2010-09-30 13:30:03 3077 12924 ENVIRON [1] -D9

2010-09-30 13:30:03 3077 12924 ENVIRON [2] start

2010-09-30 13:30:03 3077 12923 ENVIRON Command line argument dump completed

2010-09-30 13:30:03 3077 12898 ENVIRON Resource limit dump start

2010-09-30 13:30:03 3077 12898 ENVIRON Started by user id 0 group id 0

2010-09-30 13:30:03 3077 12898 ENVIRON Current user id 502 effective id 502

2010-09-30 13:30:03 3077 12898 ENVIRON Current group id 502 effective id 502

2010-09-30 13:30:03 3077 12898 ENVIRON cpu time unlimited

2010-09-30 13:30:03 3077 12898 ENVIRON number of processes 16352

2010-09-30 13:30:03 3077 12898 ENVIRON number of open files 1024

2010-09-30 13:30:03 3077 12898 ENVIRON core size 0 KBytes

2010-09-30 13:30:03 3077 12898 ENVIRON file size unlimited

2010-09-30 13:30:03 3077 12898 ENVIRON heap memory size unlimited

2010-09-30 13:30:03 3077 12898 ENVIRON stack memory size 10240 KBytes

2010-09-30 13:30:03 3077 12898 ENVIRON lockable memory size 32 KBytes

2010-09-30 13:30:03 3077 12898 ENVIRON virtual memory size unlimited

2010-09-30 13:30:03 3077 12898 ENVIRON resident set size unlimited

2010-09-30 13:30:03 3077 12898 ENVIRON Resource limit dump completed

2010-09-30 13:30:03 3077 12898 ENVIRON Environment dump start

2010-09-30 13:30:03 3077 12898 ENVIRON HOSTNAME=<snipped>

2010-09-30 13:30:03 3077 12898 ENVIRON TERM=xterm

2010-09-30 13:30:03 3077 12898 ENVIRON SHELL=/bin/bash

2010-09-30 13:30:03 3077 12898 ENVIRON HISTSIZE=1000

2010-09-30 13:30:03 3077 12898 ENVIRON LC_ALL=POSIX

2010-09-30 13:30:03 3077 12898 ENVIRON USER=root

2010-09-30 13:30:03 3077 12898 ENVIRON LS_COLORS=no=00:fi=00:di=00;34:ln=00;36:

2010-09-30 13:30:03 3077 12898 ENVIRON pi=40;33:so=00;35:bd=40;33;01:cd=40;33;0

2010-09-30 13:30:03 3077 12898 ENVIRON 1:or=01;05;37;41:mi=01;05;37;41:ex=00;32

2010-09-30 13:30:03 3077 12898 ENVIRON :.cmd=00;32:.exe=00;32:.com=00;32:.b

2010-09-30 13:30:03 3077 12898 ENVIRON tm=00;32:.bat=00;32:.sh=00;32:*.csh=00

2010-09-30 13:30:03 3077 12898 ENVIRON ;32:.tar=00;31:.tgz=00;31:*.arj=00;31:

2010-09-30 13:30:03 3077 12898 ENVIRON .taz=00;31:.lzh=00;31:.zip=00;31:.z=

2010-09-30 13:30:03 3077 12898 ENVIRON 00;31:.Z=00;31:.gz=00;31:.bz2=00;31:

2010-09-30 13:30:03 3077 12898 ENVIRON .bz=00;31:.tz=00;31:.rpm=00;31:*.cpio=

2010-09-30 13:30:03 3077 12898 ENVIRON 00;31:.jpg=00;35:.gif=00;35:*.bmp=00;3

2010-09-30 13:30:03 3077 12898 ENVIRON 5:.xbm=00;35:.xpm=00;35:.png=00;35:.

2010-09-30 13:30:03 3077 12898 ENVIRON tif=00;35:

2010-09-30 13:30:03 3077 12898 ENVIRON COLUMNS=80

2010-09-30 13:30:03 3077 12898 ENVIRON PATH=/sata1/sapdb/iprogram/bin:/usr/kerb

2010-09-30 13:30:03 3077 12898 ENVIRON eros/sbin:/usr/kerberos/bin:/usr/local/s

2010-09-30 13:30:03 3077 12898 ENVIRON bin:/usr/local/bin:/sbin:/bin:/usr/sbin:

2010-09-30 13:30:03 3077 12898 ENVIRON /usr/bin:/root/bin

2010-09-30 13:30:03 3077 12898 ENVIRON MAIL=/var/spool/mail/root

2010-09-30 13:30:03 3077 12898 ENVIRON PWD=/root

2010-09-30 13:30:03 3077 12898 ENVIRON INPUTRC=/etc/inputrc

2010-09-30 13:30:03 3077 12898 ENVIRON LANG=en_US.UTF-8

2010-09-30 13:30:03 3077 12898 ENVIRON LINES=24

2010-09-30 13:30:03 3077 12898 ENVIRON SSH_ASKPASS=/usr/libexec/openssh/gnome-s

2010-09-30 13:30:03 3077 12898 ENVIRON sh-askpass

2010-09-30 13:30:03 3077 12898 ENVIRON HOME=/root

2010-09-30 13:30:03 3077 12898 ENVIRON SHLVL=2

2010-09-30 13:30:03 3077 12898 ENVIRON LOGNAME=root

2010-09-30 13:30:03 3077 12898 ENVIRON LESSOPEN=|/usr/bin/lesspipe.sh %s

2010-09-30 13:30:03 3077 12898 ENVIRON DISPLAY=:0.0

2010-09-30 13:30:03 3077 12898 ENVIRON G_BROKEN_FILENAMES=1

2010-09-30 13:30:03 3077 12898 ENVIRON XAUTHORITY=/root/.xauth0M7pJP

2010-09-30 13:30:03 3077 12898 ENVIRON =/sata1/sapdb/iprogram/bin/xserver

2010-09-30 13:30:03 3077 12898 ENVIRON DBROOT=/sata1/sapdb/iprogram

2010-09-30 13:30:03 3077 12898 ENVIRON Environment dump completed

2010-09-30 13:30:30 3077 12908 XSERVER Accepting ...

2010-09-30 13:30:30 3077 12872 XSERVER Accepted connection, socket: 7 Id 1

2010-09-30 13:30:30 3077 12873 XSERVER 1 | Client node '<snipped>'

2010-09-30 13:30:30 3120 ERR 11934 XSERVER Connect request: Stop request rejected

2010-09-30 13:30:30 3120 12858 SERVER Exiting pid 3120 exit code 4

2010-09-30 13:30:30 3077 12857 SERVER Forked child pid 3120

-


current write position

Accepted Solutions (1)

Accepted Solutions (1)

markus_doehr2
Active Contributor
0 Kudos

> 2010-09-30 13:30:03 3077 12902 XSERVER started, 'X64/LINUX 7.5.0 Build 023-123-087-292'

Any reason why you use an ancient software version?

Markus

Former Member
0 Kudos

Yes there is a very good set of reasons but your query is not relevant to the issue at hand.

I will state the DB is a mission critical but legacy backend that needs to get off ancient hardware before the hardware fails and into a VM so we can then do the work necessary to bring everything up to date but we need certainty of stability first.

With that said do you have any insight as to how to fix the issue I have reported Markus?

Thanks

markus_doehr2
Active Contributor
0 Kudos

> Yes there is a very good set of reasons but your query is not relevant to the issue at hand.

This is not necessarily true.

Old MaxDB versions use a different threading model, depending on the operating system the "old" thread model is supported - or not.

> With that said do you have any insight as to how to fix the issue I have reported Markus?

Did you set LD_ASSUME_KERNEL to 2.4.1 before starting the x_server?

Markus

Former Member
0 Kudos

No I didn't because that is not set on our existing server. The existing server is a SuSE 9.1 x64 installation. I will check to see if SuSE 9.1 uses a different threading model than does RH5.

markus_doehr2
Active Contributor
0 Kudos

> No I didn't because that is not set on our existing server. The existing server is a SuSE 9.1 x64 installation. I will check to see if SuSE 9.1 uses a different threading model than does RH5.

SuSE 9.1 uses the "old" threads, here the software is running with the default settings.

Redhat 5 is very new (Kernel 2.6 with NTPL) and has no possibility to set the "old" threading model.

Newer versions of MaxDB (7.6.x and higher) use the new threading model automatically.

Markus

Former Member
0 Kudos

Per getconf GNU_LIBPTHREAD_VERSION

SuSE 9.1 x64 = NPTL 2.3.3

Scientific Linux 5.5 x64 = 2.5

Former Member
0 Kudos

The kernels on each are

SuSE = 2.6.8-24.20-smp x86_64

SL = 2.6.18-194.11.3.el5 SMP x86_64

markus_doehr2
Active Contributor
0 Kudos

> SuSE 9.1 x64 = NPTL 2.3.3

> Scientific Linux 5.5 x64 = 2.5

"Red Hat Enterprise Linux 5.x uses the Native Posix Threading Library, a POSIX-compatible threading implementation, for threading. Unlike former versions of RHEL, using LinuxThreads for older applications by way of setting the environment variable LD_ASSUME_KERNEL to 2.4.1 doesn't work anymore"

Markus

Former Member
0 Kudos

Yes, i forgot to put NPTL in front of the 2.5. Just for giggles I did set the LD_ASSUME_KERNEL to 2.4.1 and tried to start maxdb and it barked:

/bin/sh: error while loading shared libraries: libdl.so.2: cannot open shared object file: No such file or directory

markus_doehr2
Active Contributor
0 Kudos

> Yes, i forgot to put NPTL in front of the 2.5. Just for giggles I did set the LD_ASSUME_KERNEL to 2.4.1 and tried to start maxdb and it barked:

>

> /bin/sh: error while loading shared libraries: libdl.so.2: cannot open shared object file: No such file or directory

Well - the software is very old - and the OS is very new.

Use the latest build for 7.5 and you should be safe.

Markus

Former Member
0 Kudos

I think the only clue to why the db cannot be contacted are these lines.

Accepted connection, socket: 7 Id 1 2010-09-30 13:30:30 3077

12873 XSERVER 1 | Client node '' 2010-09-30 13:30:30

3120 ERR 11934 XSERVER Connect request: Stop request rejected 2010-09-30 13:30:30

3120 12858 SERVER Exiting pid

3120 exit code 4 2010-09-30 13:30:30

3077 12857 SERVER Forked child pid 3120

Former Member
0 Kudos

Use the latest build for 7.5 and you should be safe.

Would I be able to directly import my .23 full dump without doing a migration? What is the link to the latest 7.5 version since I'm not having to much luck getting downloads from the new site. Last time I tried to download maxdb from your site it bombed .. I will try again but a link to the version you recommend would be appreciated.

markus_doehr2
Active Contributor
0 Kudos

Please check knldiag also.

I still wonder why you just don't try with a newer (supported) build instead of an old software. From a functionality point of view nothing will change - it's just that tons of bugs are fixed and that it's support on your current platform.

Even if you get it to "trick" to run on RHEL 5.5 (or derivatives of that) you'll need to change that again if you update to a higher build

Markus

markus_doehr2
Active Contributor
0 Kudos

> Would I be able to directly import my .23 full dump without doing a migration?

Yes.

> What is the link to the latest 7.5 version since I'm not having to much luck getting downloads from the new site. Last time I tried to download maxdb from your site it bombed .. I will try again but a link to the version you recommend would be appreciated.

I'm not working for SAP.

You can use the build here:

ftp://ftp.sap.com/pub/maxdb/current/7.5.00/maxdb-srv75-7.5.0.44-1.x86_64.rpm

The very latest build is 58 but that one is only available if you're a SAP customer. 7.5 is pretty old and no more developed. I would migrate to 7.6 or better 7.7 which is available here on the SDN but I'd try to first get the 7.5 build running.

Markus

Former Member
0 Kudos

I don't have a knldiag in .../idata/wrk/.M750023 and I don't have a db instance so no knldiag. The db server runs but I cannot create a new db instance or connect to it remotely via dbmgui .

Per the 7.5 install page ( [original link is broken]) I found this snippet:

Requirements: glibc >= 2.3.3, gtk 2.x, X server (the root user must be able to access a display). Additionally, Linux i386 requires glibc with TLS (thread local storage) support.

I have gtk2 installed. Also the glibc TLS support is also curious.

I would gladly use a newer 7.5 version if I can import my full backup without issue. Do you know if a build .23 will go into whatever you found to be the latest 7.5 build? I'm looking for the latest 7.5 build but no luck finding it just yet.

Former Member
0 Kudos

Thanks for the link Markus, our posts crossed paths. I will give the latest build a try and see what I find.

Former Member
0 Kudos

TLS is supported in x86_64 at glibc version 2.3.2 and I am running glibc-2.5.

So my hope is that your suggestion pans out and that the issue I have is a bug in .23 that was correct in .44 which I am downloading now.

Former Member
0 Kudos

Would package PCR 7403 not being able to find libstdc++-libc6.2-2.so.3 be a problem when "ifconf -i -p .../runtime/7403" is trying to be installed/registed during installation of all packages (option #10 - all)?

Former Member
0 Kudos

Ok package PCR 7301 is consistent but not PCR 7403. That is the only thing sdbverify complains about so I'm going to ignore the PCR 7403 error and move on.

Former Member
0 Kudos

Arghhh! Trying to read the label of my full backup that I am using to create the new db instance gives

"-24999 common error [backup_labeloffline "myimportdb_file"]

I'm guessing that a warm backup from another system can't be used and I have to create a full backup while the source DB is in the offline state?

Former Member
0 Kudos

OK the label read from the properties tab emits my previously reported error but if you click next it will read the file and get you to the adjust parameters step. Reading the label was always my way of telling if the backup medium was good but I guess that doesn't apply when you are doing a clean import of a backup from another older system.

markus_doehr2
Active Contributor
0 Kudos

Nothing major changes between the backup of different builds of the same version, it's bugfixing.

Markus

Former Member
0 Kudos

FYI

I imported my full backup to the new server and whenever I try to take the db online I get a kernel crash (see below). I am going to destroy the instance and recreate (and possibly reinstall everything) to see if the second time will be a charm. The backup I am trying to import was created using "Save Warm". I have another fresh "warm backup" from last night so I am going to use it this go-around.

After importing the instance I issued the "db_execute clear log" but was unable to execute the "load_systab -u <user>,<pass> -ud <pass>" which barks at me with "ERR -24936 DBM ERR_DBNORUN: database is not running". Maybe I am mistaken but I thought the load_systab had to executed in admin mode.

2010-10-01 13:37:51 8705 ERR 11599 BTRACE -


> End of Stack Back Trace <----

2010-10-01 13:37:51 8705 ERR 11196 DBCRASH vabort:Emergency Shutdown, Task: 56

2010-10-01 13:37:53 0 ERR 11979 DBCRASH Kernel exited without core and exit status 0x200

2010-10-01 13:37:53 0 ERR 11983 DBCRASH Kernel exited exit code 2

markus_doehr2
Active Contributor
0 Kudos

> I imported my full backup to the new server and whenever I try to take the db online I get a kernel crash (see below).

Which MaxDB version do you use?

> After importing the instance I issued the "db_execute clear log"

Why do you do that?

> but was unable to execute the "load_systab -u <user>,<pass> -ud <pass>" which barks at me with "ERR -24936 DBM ERR_DBNORUN: database is not running". Maybe I am mistaken but I thought the load_systab had to executed in admin mode.

"load_systab" creates tables in the database and must be executed in online mode, otherwise you can't create tables in the database.

Don't start a recover on 7.6 with "recover_start" but using "db_activate recover", this will format the log automatically.

Markus

Former Member
0 Kudos

Which MaxDB version do you use?

7.5.00.44

Why do you do that?

Had to do that in the past to get imports in the online state so just following my notes from years past.

"load_systab" creates tables in the database and must be executed in online mode

Good deal, I don't have to worry about that just yet.

markus_doehr2
Active Contributor
0 Kudos

>

Which MaxDB version do you use?

> 7.5.00.44

Ok. If the database crashes in a very early state it's certainly something with the threading.

I must admit I have no idea how to solve that problem (but using a database version that works with a new OS).

>

Why do you do that?

> Had to do that in the past to get imports in the online state so just following my notes from years past.

If you create the database newly then the log is formatted. The "clear log" thing is undocumented because pretty dangerous

Markus

Former Member
0 Kudos

I'll try to give it another run with a new backup image. If that doesn't work then I'll try to step up to a higher version just to try and get something working.

Former Member
0 Kudos

Ahh the obvious little things you forget. After running a recovery (essentially an import) you must perform a full backup before attempting to take the db online. Thanks for the help Markus.

lbreddemann
Active Contributor
0 Kudos

>

> Ahh the obvious little things you forget. After running a recovery (essentially an import) you must perform a full backup before attempting to take the db online. Thanks for the help Markus.

No, that's plain wrong!

When you restore a database and want to keep using the same log area, then you use "recover_start".

If you don't want to use the existing data from the log area (e.g. because you perform a database copy) you use "db_activate RECOVER".

You only need to perform a new full backup in order to start a new backup history, so that you can start taking log backups.

If you set log mode to OVERWRITE you don't need to do that.

If you keep using the original log area you don't need to do that.

With 7.8, you don't need to do that either (as you can just tell the database that you just performed one).

Way easier then the DBMCLI commands would be to use the GUI tools, anyhow.

Just my two cents.

regards,

Lars

Former Member
0 Kudos

I am using the dbmgui not the dbmcli.

This is a import of a db from another server to a new server. However, the full backup wasn't the magic bullet I thought it was. I dropped the instance I actually got running to repeat the steps and make sure the process is repeatable. That instance I changed quite a few parameters to default values, ran a consistency check and did the full backup and it did eventually go to db_online status.

However, when doing another import of same media but not doing the consistency check I have not been able to get to the db_online state again. I also noticed that some of the parameters I was able to change in my successful attempt no longer allow me to change to the value I had previously. I am going to rerun the process again today just to make sure I am not missing a step.

lbreddemann
Active Contributor
0 Kudos

>

> However, when doing another import of same media but not doing the consistency check I have not been able to get to the db_online state again. I also noticed that some of the parameters I was able to change in my successful attempt no longer allow me to change to the value I had previously. I am going to rerun the process again today just to make sure I am not missing a step.

Ok - once again: WHAT ERROR MESSAGE DID YOU GET?

" I have not been able to get to the db_online state again" gives us 0 (zero) option to analyse your problem.

Check the KNLDIAG file when the database does not get online.

And which settings could you not change anymore?

INSTANCE_TYPE? Sure you can't as it's a setting that is fixed as of the creation of the instance.

regards,

Lars

Former Member
0 Kudos

Easy Lars, I am still experimenting. Once I have exhausted my scenario testing (hopefully today) I will put the relevant information here. As I said I did get one imported instance running so I think I just have to step back and methodically go through and retrace my steps. If I got one instance running that means I should be able to get others up as well, I just have to do it correctly.

I can tell you that MAXLOCKS isn't changeable. The default is 2500 but my import media has it at 19250. My attempts to put it back to 2500 are ignored.

MIN_CAT_CACHE_SUPPLY also isn't changeable (thus far anyway).

lbreddemann
Active Contributor
0 Kudos

>

> Easy Lars, I am still experimenting. Once I have exhausted my scenario testing (hopefully today) I will put the relevant information here. As I said I did get one imported instance running so I think I just have to step back and methodically go through and retrace my steps. If I got one instance running that means I should be able to get others up as well, I just have to do it correctly.

>

> I can tell you that MAXLOCKS isn't changeable. The default is 2500 but my import media has it at 19250. My attempts to put it back to 2500 are ignored.

Would be interesting to see how you do that.

MAXLOCKS can definitively be changed at all times...

> MIN_CAT_CACHE_SUPPLY also isn't changeable (thus far anyway).

Same for this one.

Anyhow - you're into experimenting, so this behavior likely is no software bug...

Answers (2)

Answers (2)

Former Member
0 Kudos

Using a newer version of the OLTP database server does not allow a correct import to occur.

Former Member
0 Kudos

FYI: I will post the knldiag stack dump in the next reply because this editor cannot handle direct copy-n-pastes from maxdb log files.

All but one previous attempts using MaxDB OLTP v7.5.00.44 to import a 7.5.00.23 instance failed with kernel aborts. Next step was to use newer software. Unable to download newest versions from SDN site (always get the contact support when it tries to start downloading) I grabbed the following from your FTP site and what follows is the result. Appears the software is having issues creating the syscatalog schema.

a) Installed MaxDB OLTP v7.6.03.015-123-173-107 (from sap ftp site)

b) Took source DB to admin and did full backup

c) Updated dbmgui to v7.6.03.10 (from sap ftp site)

d) Imported source instance db, did not change parameters, all went well

e) called db_execute clear log --> result OK

f) called db_online and the result is as follows

dbmgui error after attempting to go to db_online

-24895 shutdown of database occured [db_online -f]; -24994, ERR_RTE: Runtime environment error

Former Member
0 Kudos

2010-10-13 06:51:07 20666 20039 Admin Kernel state: 'REDO LOG' finished

2010-10-13 06:51:07 20666 20065 Log History: waiting for removal of complete history

2010-10-13 06:51:07 20666 54000 OBJECT /sata1/sapdb/depend/lib/liboms

2010-10-13 06:51:07 20666 51381 MIGRAT start of catalog migration : source is

2010-10-13 06:51:07 20666 51381 MIGRAT Kernel 7.5.0 Build 023-123-087-292

2010-10-13 06:51:07 20666 51381 MIGRAT start of schema migration

2010-10-13 06:51:07 20666 51381 MIGRAT migrating triggers

2010-10-13 06:51:07 20666 51381 MIGRAT migrating triggers

2010-10-13 06:51:08 20666 51381 MIGRAT migrating triggers

2010-10-13 06:51:08 20666 ERR 3 Catalog Creation of a catalog object failed,ERRORTEXT=-5001,SQLSTATEMENT=create schema syscatalog

2010-10-13 06:51:08 20666 ERR 11196 DBCRASH vabort:Emergency Shutdown, Catalog_Instance.cpp: 314

2010-10-13 06:51:08 20666 ERR 11599 BTRACE -


> Emergency Stack Back Trace <----

2010-10-13 06:51:08 20666 ERR 11599 BTRACE (0):0xeb9495

2010-10-13 06:51:08 20666 ERR 11599 BTRACE (1):0xeb94f9

2010-10-13 06:51:08 20666 ERR 11599 BTRACE (2):0xeb9642

2010-10-13 06:51:08 20666 ERR 11599 BTRACE (3):0xeb9677

2010-10-13 06:51:08 20666 ERR 11599 BTRACE (4):0xedbb77

2010-10-13 06:51:08 20666 ERR 11599 BTRACE (5):0xdf24ad

2010-10-13 06:51:08 20666 ERR 11599 BTRACE (6):0xd07449

2010-10-13 06:51:08 20666 ERR 11599 BTRACE (7):0xd07d69

2010-10-13 06:51:08 20666 ERR 11599 BTRACE (8):0xd08332

2010-10-13 06:51:08 20666 ERR 11599 BTRACE (9):0xcfd3e4

2010-10-13 06:51:08 20666 ERR 11599 BTRACE (10):0x70d0db

2010-10-13 06:51:08 20666 ERR 11599 BTRACE (11):0x70507f

2010-10-13 06:51:08 20666 ERR 11599 BTRACE (12):0x705941

2010-10-13 06:51:08 20666 ERR 11599 BTRACE (13):0x706404

2010-10-13 06:51:08 20666 ERR 11599 BTRACE (14):0x6f4d0d

2010-10-13 06:51:08 20666 ERR 11599 BTRACE (15):0x6f5727

2010-10-13 06:51:08 20666 ERR 11599 BTRACE (16):0x6f6409

2010-10-13 06:51:08 20666 ERR 11599 BTRACE (17):0x82d441

2010-10-13 06:51:08 20666 ERR 11599 BTRACE (18):0x82eb6f

2010-10-13 06:51:08 20666 ERR 11599 BTRACE (19):0x82ef2b

2010-10-13 06:51:08 20666 ERR 11599 BTRACE (20):0x82ffbb

2010-10-13 06:51:08 20666 ERR 11599 BTRACE (21):0x832b05

2010-10-13 06:51:08 20666 ERR 11599 BTRACE (22):0xdc9674

2010-10-13 06:51:08 20666 ERR 11599 BTRACE (23):0xdc9853

2010-10-13 06:51:08 20666 ERR 11599 BTRACE (24):0xe53278

2010-10-13 06:51:08 20666 ERR 11599 BTRACE (25):0xf02f6c

2010-10-13 06:51:08 20666 ERR 11599 BTRACE (26):0x39ec641870

2010-10-13 06:51:08 20666 ERR 11599 BTRACE -


> Module List <----

2010-10-13 06:51:08 20666 ERR 11599 BTRACE |.text Start |.text End | Module File Name

2010-10-13 06:51:08 20666 ERR 11599 BTRACE |0x0000000000400000|0x00000000010d4000| /sata1/sapdb/depend/pgm/kernel

2010-10-13 06:51:08 20666 ERR 11599 BTRACE |0x00000039ec200000|0x00000039ec21c000| /lib64/ld-2.5.so

2010-10-13 06:51:08 20666 ERR 11599 BTRACE |0x00000039ec41b000|0x00000039ec41c000| /lib64/ld-2.5.so

2010-10-13 06:51:08 20666 ERR 11599 BTRACE |0x00000039ec600000|0x00000039ec74e000| /lib64/libc-2.5.so

2010-10-13 06:51:08 20666 ERR 11599 BTRACE |0x00000039ec94d000|0x00000039ec951000| /lib64/libc-2.5.so

2010-10-13 06:51:08 20666 ERR 11599 BTRACE |0x00000039eca00000|0x00000039eca82000| /lib64/libm-2.5.so

2010-10-13 06:51:08 20666 ERR 11599 BTRACE |0x00000039ecc81000|0x00000039ecc82000| /lib64/libm-2.5.so

2010-10-13 06:51:08 20666 ERR 11599 BTRACE |0x00000039ece00000|0x00000039ece02000| /lib64/libdl-2.5.so

2010-10-13 06:51:08 20666 ERR 11599 BTRACE |0x00000039ed002000|0x00000039ed003000| /lib64/libdl-2.5.so

2010-10-13 06:51:08 20666 ERR 11599 BTRACE |0x00000039ed200000|0x00000039ed216000| /lib64/libpthread-2.5.so

2010-10-13 06:51:08 20666 ERR 11599 BTRACE |0x00000039ed415000|0x00000039ed416000| /lib64/libpthread-2.5.so

2010-10-13 06:51:08 20666 ERR 11599 BTRACE |0x00000039eda00000|0x00000039eda07000| /lib64/librt-2.5.so

2010-10-13 06:51:08 20666 ERR 11599 BTRACE |0x00000039edc07000|0x00000039edc08000| /lib64/librt-2.5.so

2010-10-13 06:51:08 20666 ERR 11599 BTRACE |0x00000039fe400000|0x00000039fe40d000| /lib64/libgcc_s-4.1.2-20080825.so.1

2010-10-13 06:51:08 20666 ERR 11599 BTRACE |0x00002aaad4d6b000|0x00002aaad4f75000| /sata1/sapdb/depend/lib/liboms.so

2010-10-13 06:51:08 20666 ERR 11599 BTRACE |0x00002aade5b11000|0x00002aade5bd2000| /usr/lib64/libstdc++.so.5.0.7

2010-10-13 06:51:08 20666 ERR 11599 BTRACE |0x00002aade5f46000|0x00002aade5f50000| /lib64/libnss_files-2.5.so

2010-10-13 06:51:08 20666 ERR 11599 BTRACE |0x00002aade614f000|0x00002aade6150000| /lib64/libnss_files-2.5.so

2010-10-13 06:51:08 20666 ERR 11599 BTRACE

2010-10-13 06:51:08 20666 ERR 11599 BTRACE -


> Symbolic Stack Back Trace <----

2010-10-13 06:51:08 20666 ERR 11599 BTRACE 0: 0x0000000000eb8b2d eo670_UnixTraceStack +0x01ad

2010-10-13 06:51:08 20666 ERR 11599 BTRACE /sata1/sapdb/depend/pgm/kernel

2010-10-13 06:51:08 20666 ERR 11599 BTRACE Frameinfo [0x0]

2010-10-13 06:51:08 20666 ERR 11599 BTRACE 1: 0x0000000000eb94f9 eo670_CTraceContextStackOCB +0x0009

2010-10-13 06:51:08 20666 ERR 11599 BTRACE /sata1/sapdb/depend/pgm/kernel

2010-10-13 06:51:08 20666 ERR 11599 BTRACE Frameinfo [0x0]

2010-10-13 06:51:08 20666 ERR 11599 BTRACE 2: 0x0000000000eb9642 eo670_CTraceStackOCB +0x0032

2010-10-13 06:51:08 20666 ERR 11599 BTRACE /sata1/sapdb/depend/pgm/kernel

2010-10-13 06:51:08 20666 ERR 11599 BTRACE Frameinfo [0x0]

2010-10-13 06:51:08 20666 ERR 11599 BTRACE 3: 0x0000000000eb9677 eo670_CTraceStack +0x0017

2010-10-13 06:51:08 20666 ERR 11599 BTRACE /sata1/sapdb/depend/pgm/kernel

2010-10-13 06:51:08 20666 ERR 11599 BTRACE Frameinfo [0x0]

2010-10-13 06:51:08 20666 ERR 11599 BTRACE 4: 0x0000000000edbb77 vabort +0x0027

2010-10-13 06:51:08 20666 ERR 11599 BTRACE /sata1/sapdb/depend/pgm/kernel

2010-10-13 06:51:08 20666 ERR 11599 BTRACE Frameinfo [0x0]

2010-10-13 06:51:08 20666 ERR 11599 BTRACE 5: 0x0000000000df24ad Z9RTECrashRK20SAPDBErr_MessageList +0x008d

2010-10-13 06:51:08 20666 ERR 11599 BTRACE /sata1/sapdb/depend/pgm/kernel

2010-10-13 06:51:08 20666 ERR 11599 BTRACE Frameinfo [0x0]

2010-10-13 06:51:08 20666 ERR 11599 BTRACE 6: 0x0000000000d07449 ZN16CatalogInstance5AbortERK20SAPDBErr_MessageList +0x0039

2010-10-13 06:51:08 20666 ERR 11599 BTRACE /sata1/sapdb/depend/pgm/kernel

2010-10-13 06:51:08 20666 ERR 11599 BTRACE Frameinfo [0x0]

2010-10-13 06:51:08 20666 ERR 11599 BTRACE 7: 0x0000000000d07d69 ZN16CatalogInstance19ExecuteSqlStatementER15KSQL_ConnectionPKc +0x02f9

2010-10-13 06:51:08 20666 ERR 11599 BTRACE /sata1/sapdb/depend/pgm/kernel

2010-10-13 06:51:08 20666 ERR 11599 BTRACE Frameinfo [0x0]

2010-10-13 06:51:08 20666 ERR 11599 BTRACE 8: 0x0000000000d08332 ZN16CatalogInstance19CreateCatalogTablesEv +0x00e2

2010-10-13 06:51:08 20666 ERR 11599 BTRACE /sata1/sapdb/depend/pgm/kernel

2010-10-13 06:51:08 20666 ERR 11599 BTRACE Frameinfo [0x0]

2010-10-13 06:51:08 20666 ERR 11599 BTRACE 9: 0x0000000000cfd3e4 a103CreateCatalog +0x0014

2010-10-13 06:51:08 20666 ERR 11599 BTRACE /sata1/sapdb/depend/pgm/kernel

2010-10-13 06:51:08 20666 ERR 11599 BTRACE Frameinfo [0x0]

2010-10-13 06:51:08 20666 ERR 11599 BTRACE 10: 0x000000000070d0db a361migrate +0x0dbb

2010-10-13 06:51:08 20666 ERR 11599 BTRACE /sata1/sapdb/depend/pgm/kernel

2010-10-13 06:51:08 20666 ERR 11599 BTRACE Frameinfo [0x0]

2010-10-13 06:51:08 20666 ERR 11599 BTRACE 11: 0x000000000070507f ak36restart_second_part +0x027f

2010-10-13 06:51:08 20666 ERR 11599 BTRACE /sata1/sapdb/depend/pgm/kernel

2010-10-13 06:51:08 20666 ERR 11599 BTRACE Frameinfo [0x0]

2010-10-13 06:51:08 20666 ERR 11599 BTRACE 12: 0x0000000000705941 ak36restart +0x0151

2010-10-13 06:51:08 20666 ERR 11599 BTRACE /sata1/sapdb/depend/pgm/kernel

2010-10-13 06:51:08 20666 ERR 11599 BTRACE Frameinfo [0x0]

2010-10-13 06:51:08 20666 ERR 11599 BTRACE 13: 0x0000000000706404 a36_call_semantic +0x0214

2010-10-13 06:51:08 20666 ERR 11599 BTRACE /sata1/sapdb/depend/pgm/kernel

2010-10-13 06:51:08 20666 ERR 11599 BTRACE Frameinfo [0x0]

2010-10-13 06:51:08 20666 ERR 11599 BTRACE 14: 0x00000000006f4d0d ak35dbmcommands +0x012d

2010-10-13 06:51:08 20666 ERR 11599 BTRACE /sata1/sapdb/depend/pgm/kernel

2010-10-13 06:51:08 20666 ERR 11599 BTRACE Frameinfo [0x0]

2010-10-13 06:51:08 20666 ERR 11599 BTRACE 15: 0x00000000006f5727 ak35call_semantik +0x0657

2010-10-13 06:51:08 20666 ERR 11599 BTRACE /sata1/sapdb/depend/pgm/kernel

2010-10-13 06:51:08 20666 ERR 11599 BTRACE Frameinfo [0x0]

2010-10-13 06:51:08 20666 ERR 11599 BTRACE 16: 0x00000000006f6409 a35_asql_statement2 +0x0a09

2010-10-13 06:51:08 20666 ERR 11599 BTRACE /sata1/sapdb/depend/pgm/kernel

2010-10-13 06:51:08 20666 ERR 11599 BTRACE Frameinfo [0x0]

2010-10-13 06:51:08 20666 ERR 11599 BTRACE 17: 0x000000000082d441 ak92not_only_execute +0x0551

2010-10-13 06:51:08 20666 ERR 11599 BTRACE /sata1/sapdb/depend/pgm/kernel

2010-10-13 06:51:08 20666 ERR 11599 BTRACE Frameinfo [0x0]

2010-10-13 06:51:08 20666 ERR 11599 BTRACE 18: 0x000000000082eb6f ak92analyze_messagetype +0x09bf

2010-10-13 06:51:08 20666 ERR 11599 BTRACE /sata1/sapdb/depend/pgm/kernel

2010-10-13 06:51:08 20666 ERR 11599 BTRACE Frameinfo [0x0]

2010-10-13 06:51:08 20666 ERR 11599 BTRACE 19: 0x000000000082ef2b a92_mode_analyzer +0x009b

2010-10-13 06:51:08 20666 ERR 11599 BTRACE /sata1/sapdb/depend/pgm/kernel

2010-10-13 06:51:08 20666 ERR 11599 BTRACE Frameinfo [0x0]

2010-10-13 06:51:08 20666 ERR 11599 BTRACE 20: 0x000000000082ffbb ak93one_command +0x049b

2010-10-13 06:51:08 20666 ERR 11599 BTRACE /sata1/sapdb/depend/pgm/kernel

2010-10-13 06:51:08 20666 ERR 11599 BTRACE Frameinfo [0x0]

2010-10-13 06:51:08 20666 ERR 11599 BTRACE 21: 0x0000000000832b05 a93_user_commands +0x0545

2010-10-13 06:51:08 20666 ERR 11599 BTRACE /sata1/sapdb/depend/pgm/kernel

2010-10-13 06:51:08 20666 ERR 11599 BTRACE Frameinfo [0x0]

2010-10-13 06:51:08 20666 ERR 11599 BTRACE 22: 0x0000000000dc9674 Z7SQLTaskR20takall_command_globRhb +0x0074

2010-10-13 06:51:08 20666 ERR 11599 BTRACE /sata1/sapdb/depend/pgm/kernel

2010-10-13 06:51:08 20666 ERR 11599 BTRACE Frameinfo [0x0]

2010-10-13 06:51:08 20666 ERR 11599 BTRACE 23: 0x0000000000dc9853 Z11KernelMainR13RTETask_ITask +0x01b3

2010-10-13 06:51:08 20666 ERR 11599 BTRACE /sata1/sapdb/depend/pgm/kernel

2010-10-13 06:51:08 20666 ERR 11599 BTRACE Frameinfo [0x0]

2010-10-13 06:51:08 20666 ERR 11599 BTRACE 24: 0x0000000000e53278 RTETask_TaskMain +0x0038

2010-10-13 06:51:08 20666 ERR 11599 BTRACE /sata1/sapdb/depend/pgm/kernel

2010-10-13 06:51:08 20666 ERR 11599 BTRACE Frameinfo [0x0]

2010-10-13 06:51:08 20666 ERR 11599 BTRACE 25: 0x0000000000f02f6c Z23en88CallKernelTaskMainP9TASK_TYPE +0x00bc

2010-10-13 06:51:08 20666 ERR 11599 BTRACE /sata1/sapdb/depend/pgm/kernel

2010-10-13 06:51:08 20666 ERR 11599 BTRACE Frameinfo [0x0]

2010-10-13 06:51:08 20666 ERR 11599 BTRACE 26: 0x00000039ec641870 dltls_get_addr_soft@@GLIBC_PRIVATE +0x41870

2010-10-13 06:51:08 20666 ERR 11599 BTRACE /lib64/libc-2.5.so

2010-10-13 06:51:08 20666 ERR 11599 BTRACE Frameinfo [0x0]

2010-10-13 06:51:08 20666 ERR 11599 BTRACE -


> End of Stack Back Trace <----

2010-10-13 06:51:08 20666 11987 dump_rte rtedump written to file 'rtedump'

2010-10-13 06:51:08 20666 ERR 7 Messages Begin of dump of registered messages

2010-10-13 06:51:08 20666 ERR 3 Catalog Creation of a catalog object failed,ERRORTEXT=-5001,SQLSTATEMENT=create schema syscatalog

2010-10-13 06:51:08 20666 ERR 8 Messages End of the message list registry dump

2010-10-13 06:51:08 20666 12820 EXCEPT calling ak dump for T72

2010-10-13 06:51:08 20666 ERR 51105 AK CACHE AK00001.dmp written: 0

2010-10-13 06:51:08 20666 ERR 11196 DBCRASH vabort:Emergency Shutdown, Task: 72

2010-10-13 06:51:08 20666 12696 DBSTATE Change DbState to 'KILL'(29)

2010-10-13 06:51:08 20666 12697 DBSTATE Resuming tracewriter

2010-10-13 06:51:08 20637 1 MsgOutpu CMNDB 2010-10-13 06:51:08 20666 ERR 11196 DBCRASH vabort:Emergency Shutdown

2010-10-13 06:51:08 20666 12825 TASKING state 29 before shutkill(1)

2010-10-13 06:51:08 20637 1 MsgOutpu , Task: 72

2010-10-13 06:51:08 20666 WNG 11824 COMMUNIC Releasing T72 database shutdown

2010-10-13 06:51:08 20666 12768 UKT7 stopped

2010-10-13 06:51:08 20660 12825 TASKING state 29 before shutkill(1)

2010-10-13 06:51:08 20660 20000 Trace Start flush kernel trace

2010-10-13 06:51:09 20644 12696 DBSTATE Change DbState to 'TRACE_WRITER_WAIT'(29)

2010-10-13 06:51:10 20664 12825 TASKING state 29 before shutkill(1)

2010-10-13 06:51:10 20664 WNG 11824 COMMUNIC Releasing T36 database shutdown

2010-10-13 06:51:10 20664 12768 UKT5 stopped

2010-10-13 06:51:11 20660 20001 Trace Stop flush kernel trace

2010-10-13 06:51:11 20660 20002 Trace Start flush kernel dump

2010-10-13 06:51:11 20660 20003 Trace Stop flush kernel dump

2010-10-13 06:51:11 20660 12619 TASKING Releasing tracewriter

2010-10-13 06:51:11 20639 12624 EXCEPT Kernel aborts

2010-10-13 06:51:11 20637 1 MsgOutpu CMNDB 2010-10-13 06:51:11 20639 12624 EXCEPT Kernel aborts

+++++++++++++++++++++++++++++++++++++++ Kernel Exit ++++++++++++++++++++++++++++

2010-10-13 06:51:12 0 11987 dump_rte rtedump written by running kernel already (start time kernel: 2010-10-12 15:53:58, last access time rtedump: 2010-10-13 06:51:08)

2010-10-13 06:51:12 0 ERR 12006 DBCRASH Kernel exited without core and exit status 0x200

2010-10-13 06:51:12 0 ERR 12010 DBCRASH Kernel exited exit code 2

2010-10-13 06:51:12 0 12890 DIAGHIST Backup of diagnostic files will be forced at next restart

2010-10-13 06:51:12 0 12808 DBSTATE Flushing knltrace pages

2010-10-13 06:51:12 0 12696 DBSTATE Change DbState to 'OFFLINE '(29)

-


current write position -


Former Member
0 Kudos

Was able to get a 7.5.00.44 instance running on VM and import production server's data in and all appears well. See following link to get the full scoop. Thanks to all for the assistance.

Former Member
0 Kudos

Hi,

to be precise, nearly all parameter are changeable (INSTANCE_TYPE is one of those few, which is not).

But some of them are only changeable in offline-mode!

And, as far as I remember, MAX_LOCKS and this MIN_CAT_CACHE_... - thing belong to the list of only-offline-changeable parameters. Therefore one cannot say, that they are NOT changeable if they are only NOT changeable on the fly in an online system.

Elke

Former Member
0 Kudos

Is there anywhere I can upload a tar ball of the instance logs for a failed import? I realize these are logs against a 7.5.00.44 server version so you may not be interested but maybe you are?

Former Member
0 Kudos

Well one last thing to try and that is to put the source DB in admin mode and do a full backup to use. The backups I have been using all were created while the DB was online but I was doing instance create with initialization so I thought it would work but maybe not I guess.