cancel
Showing results for 
Search instead for 
Did you mean: 

Error after cloning an instance - maxdb 7.6

Former Member
0 Kudos

Hi,

I am trying to clone a database in order to do some testing but it crashes when I execute the db_online command.

I issue the following commands to get the full data backup.

util_connect

medium_put MY_BACKUP "/tmp/my_backup" FILE DATA 0 8 NO

db_connect

backup_start MY_BACKUP

After the backup process is finished, I issue the following comands

to load the data backup in the new instance.

medium_put MY_BACKUP "/tmp/my_backup" FILE DATA 0 8 YES

db_admin

db_connect

db_activate RECOVER MY_BACKUP

db_online

Looks like db_activate works fine but db_online crashes.

---

>db_activate RECOVER MY_BACKUP

OK

Returncode 0

Date 20090122

Time 00092429

Server myserver

Database MYDATABASE

Kernel Version Kernel 7.6.05 Build 009-121-191-997

Pages Transferred 170536

Pages Left 0

Volumes 1

Medianame MY_BACKUP

Location /tmp/MY_BACKUP

Errortext

Label DAT_000001433

Is Consistent true

First LOG Page 670

Last LOG Page

DB Stamp 1 Date 20090122

DB Stamp 1 Time 00085015

DB Stamp 2 Date

DB Stamp 2 Time

Page Count 170515

Devices Used 1

Database ID myserver:MYINSTANCE_20090122_085318

Max Used Data Page 0

Converter Page Count 112

---

>db_online

ERR

-24988,ERR_SQL: SQL error

-31001,(no error text available from database kernel)

Looking at knldiag.err I see the following errors:

2009-01-21 13:38:37 --- Starting GMT 2009-01-21 12:38:37 7.6.05 Build 009-121-191-997

2009-01-21 13:54:59 6787 ERR 51261 TRIGGER system trigger failed with rc *1001

2009-01-21 13:55:01 6787 ERR 3 Admin Database state: OFFLINE

2009-01-21 13:55:01 6787 ERR 2 Admin + A fatal error caused EMERGENCY SHUTDOWN. core is written

2009-01-21 13:55:01 6787 ERR 11196 DBCRASH vabort:Emergency Shutdown, Kernel_Administration.cpp: 619

2009-01-21 13:55:01 6787 ERR 11599 BTRACE -


> Emergency Stack Back Trace <----

...

...

...

2009-01-21 13:55:01 6787 ERR 11599 BTRACE -


> End of Stack Back Trace <----

2009-01-21 13:55:02 6787 ERR 7 Messages Begin of dump of registered messages

2009-01-21 13:55:02 6787 ERR 2 Admin A fatal error caused EMERGENCY SHUTDOWN. core is written

2009-01-21 13:55:02 6787 ERR 2 Admin A fatal error caused EMERGENCY SHUTDOWN. core is written

2009-01-21 13:55:02 6787 ERR 8 Messages End of the message list registry dump

2009-01-21 13:55:02 6787 ERR 51105 AK CACHE AK00001.dmp written: 0

2009-01-21 13:55:02 6787 ERR 11196 DBCRASH vabort:Emergency Shutdown, Task: 207

2009-01-21 13:55:02 0 ERR 12006 DBCRASH Kernel exited without core and exit status 0x200

2009-01-21 13:55:02 0 ERR 12010 DBCRASH Kernel exited exit code 2

2009-01-21 13:55:02 ___ Stopping GMT 2009-01-21 12:55:02 7.6.05 Build 009-121-191-997

Thanks in advance,

Xavi

Edited by: Xavi Graci on Jan 22, 2009 2:30 PM

Accepted Solutions (1)

Accepted Solutions (1)

markus_doehr2
Active Contributor
0 Kudos

> 2009-01-21 13:55:01 6787 ERR 11599 BTRACE -


> Emergency Stack Back Trace <----

> ...

> ...

> ...

> 2009-01-21 13:55:01 6787 ERR 11599 BTRACE -


> End of Stack Back Trace <----

Unfortunately you missed exactly the "interesting" part of the knldiag

Markus

Former Member
0 Kudos

Ops!

I send my logs again and the stack back trace.

2009-01-21 13:38:37 --- Starting GMT 2009-01-21 12:38:37 7.6.05 Build 009-121-191-997

2009-01-21 13:54:59 6787 ERR 51261 TRIGGER system trigger failed with rc *1001

2009-01-21 13:55:01 6787 ERR 3 Admin Database state: OFFLINE

2009-01-21 13:55:01 6787 ERR 2 Admin + A fatal error caused EMERGENCY SHUTDOWN. core is written

2009-01-21 13:55:01 6787 ERR 11196 DBCRASH vabort:Emergency Shutdown, Kernel_Administration.cpp: 619

2009-01-21 13:55:01 6787 ERR 11599 BTRACE -


> Emergency Stack Back Trace <----

2009-01-21 13:55:01 6787 ERR 11599 BTRACE (0):0x8c26bfb [0x97689e78](0x0,0x0,0x0,0x150003)

2009-01-21 13:55:01 6787 ERR 11599 BTRACE (2):0x8c26d93 [0x97689e98](0x0,0x0,0x0,0x8ff98c0)

2009-01-21 13:55:01 6787 ERR 11599 BTRACE (4):0x8c26dea [0x97689eb8](0x0,0x0,0x97689ed8,0x8c8a03d)

2009-01-21 13:55:01 6787 ERR 11599 BTRACE (6):0x8c54150 [0x97689ed8](0x9020aa0,0x97689fe4,0x1,0x0)

2009-01-21 13:55:01 6787 ERR 11599 BTRACE (8):0x8b4349d [0x97689f18](0x1,0x1,0x8e1f089,0x8e1f094)

2009-01-21 13:55:01 6787 ERR 11599 BTRACE (10):0x8b01cc8 [0x97689f48](0x9768bf30,0x97689fe0,0x8e192ad,0x8e18ea2)

2009-01-21 13:55:01 6787 ERR 11599 BTRACE (12):0x876f45b [0x9768a048](0x900d1e0,0x9768a100,0x1,0x1)

2009-01-21 13:55:01 6787 ERR 11599 BTRACE (14):0x84963b3 [0x9768a168](0x1,0x2,0x68,0x9768a43f)

2009-01-21 13:55:01 6787 ERR 11599 BTRACE (16):0x84977e0 [0x9768a3a8](0x9768a930,0x0,0x0,0x9768a43f)

2009-01-21 13:55:01 6787 ERR 11599 BTRACE (18):0x8b13f16 [0x9768a488](0x9768a930,0x9768a926,0x9768a4a7,0xb7dc6814)

2009-01-21 13:55:01 6787 ERR 11599 BTRACE (20):0x8b14288 [0x9768a8d8](0x50105120,0x2,0x9768a930,0xb7d84e30)

2009-01-21 13:55:01 6787 ERR 11599 BTRACE (22):0x8bb3557 [0x9768bf98](0x50105120,0x0,0x0,0x8ff98c0)

2009-01-21 13:55:01 6787 ERR 11599 BTRACE (24):0x8c8a286 [0x9768bfb8](0x3281,0x3,0x8e2d70e,0x8e39f24)

2009-01-21 13:55:01 6787 ERR 11599 BTRACE (26):0x4abb8b [0x9768bfe8](0x0,0x0,0x0,0x0)

2009-01-21 13:55:01 6787 ERR 11599 BTRACE -


> Module List <----

2009-01-21 13:55:01 6787 ERR 11599 BTRACE |.text Start |.text End | Module File Name

2009-01-21 13:55:01 6787 ERR 11599 BTRACE | 0x00450000 | 0x0046a000 | /lib/ld-2.5.so

2009-01-21 13:55:01 6787 ERR 11599 BTRACE | 0x0046a000 | 0x0046b000 | /lib/ld-2.5.so

2009-01-21 13:55:01 6787 ERR 11599 BTRACE | 0x00473000 | 0x005b3000 | /lib/i686/nosegneg/libc-2.5.so

2009-01-21 13:55:01 6787 ERR 11599 BTRACE | 0x005b3000 | 0x005b5000 | /lib/i686/nosegneg/libc-2.5.so

2009-01-21 13:55:01 6787 ERR 11599 BTRACE | 0x005bb000 | 0x005bd000 | /lib/libdl-2.5.so

2009-01-21 13:55:01 6787 ERR 11599 BTRACE | 0x005bd000 | 0x005be000 | /lib/libdl-2.5.so

2009-01-21 13:55:01 6787 ERR 11599 BTRACE | 0x005c1000 | 0x005d4000 | /lib/i686/nosegneg/libpthread-2.5.so

2009-01-21 13:55:01 6787 ERR 11599 BTRACE | 0x005d4000 | 0x005d5000 | /lib/i686/nosegneg/libpthread-2.5.so

2009-01-21 13:55:01 6787 ERR 11599 BTRACE | 0x005da000 | 0x005ff000 | /lib/i686/nosegneg/libm-2.5.so

2009-01-21 13:55:01 6787 ERR 11599 BTRACE | 0x005ff000 | 0x00600000 | /lib/i686/nosegneg/libm-2.5.so

2009-01-21 13:55:01 6787 ERR 11599 BTRACE | 0x00665000 | 0x0066c000 | /lib/i686/nosegneg/librt-2.5.so

2009-01-21 13:55:01 6787 ERR 11599 BTRACE | 0x0066c000 | 0x0066d000 | /lib/i686/nosegneg/librt-2.5.so

2009-01-21 13:55:01 6787 ERR 11599 BTRACE | 0x008a9000 | 0x008b4000 | /lib/libgcc_s-4.1.2-20080102.so.1

2009-01-21 13:55:01 6787 ERR 11599 BTRACE | 0x08048000 | 0x08e62000 | /opt/sdb/7605/pgm/kernel

2009-01-21 13:55:01 6787 ERR 11599 BTRACE | 0x8e8f8000 | 0x8eb23000 | /opt/sdb/7605/lib/liboms.so

2009-01-21 13:55:01 6787 ERR 11599 BTRACE | 0xb7db9000 | 0xb7dc2000 | /lib/libnss_files-2.5.so

2009-01-21 13:55:01 6787 ERR 11599 BTRACE | 0xb7dc2000 | 0xb7dc3000 | /lib/libnss_files-2.5.so

2009-01-21 13:55:01 6787 ERR 11599 BTRACE | 0xb7f0a000 | 0xb7fb9000 | /usr/lib/libstdc++.so.5.0.7

2009-01-21 13:55:01 6787 ERR 11599 BTRACE | 0xb7fcc000 | 0xb7fcd000 | [vdso]

2009-01-21 13:55:01 6787 ERR 11599 BTRACE

2009-01-21 13:55:01 6787 ERR 11599 BTRACE -


> Symbolic Stack Back Trace <----

2009-01-21 13:55:01 6787 ERR 11599 BTRACE 0: 0x08c26bfb eo670_CTraceContextStackOCB +0x002b

2009-01-21 13:55:01 6787 ERR 11599 BTRACE /opt/sdb/7605/pgm/kernel

2009-01-21 13:55:01 6787 ERR 11599 BTRACE Frameinfo [0x97689e78] (0x0,0x0,0x0,0x150003)

2009-01-21 13:55:01 6787 ERR 11599 BTRACE 1: 0x08c26d93 eo670_CTraceStackOCB +0x0043

2009-01-21 13:55:01 6787 ERR 11599 BTRACE /opt/sdb/7605/pgm/kernel

2009-01-21 13:55:01 6787 ERR 11599 BTRACE Frameinfo [0x97689e98] (0x0,0x0,0x0,0x8ff98c0)

2009-01-21 13:55:01 6787 ERR 11599 BTRACE 2: 0x08c26dea eo670_CTraceStack +0x002a

2009-01-21 13:55:01 6787 ERR 11599 BTRACE /opt/sdb/7605/pgm/kernel

2009-01-21 13:55:01 6787 ERR 11599 BTRACE Frameinfo [0x97689eb8] (0x0,0x0,0x97689ed8,0x8c8a03d)

2009-01-21 13:55:01 6787 ERR 11599 BTRACE 3: 0x08c54150 vabort +0x0030

2009-01-21 13:55:01 6787 ERR 11599 BTRACE /opt/sdb/7605/pgm/kernel

2009-01-21 13:55:01 6787 ERR 11599 BTRACE Frameinfo [0x97689ed8] (0x9020aa0,0x97689fe4,0x1,0x0)

2009-01-21 13:55:01 6787 ERR 11599 BTRACE 4: 0x08b4349d Z9RTECrashRK20SAPDBErr_MessageList +0x016d

2009-01-21 13:55:01 6787 ERR 11599 BTRACE /opt/sdb/7605/pgm/kernel

2009-01-21 13:55:01 6787 ERR 11599 BTRACE Frameinfo [0x97689f18] (0x1,0x1,0x8e1f089,0x8e1f094)

2009-01-21 13:55:01 6787 ERR 11599 BTRACE 5: 0x08b01cc8 ZN21KernelAdministration7OfflineERK20SAPDBErr_MessageListbb +0x0498

2009-01-21 13:55:01 6787 ERR 11599 BTRACE /opt/sdb/7605/pgm/kernel

2009-01-21 13:55:01 6787 ERR 11599 BTRACE Frameinfo [0x97689f48] (0x9768bf30,0x97689fe0,0x8e192ad,0x8e18ea2)

2009-01-21 13:55:01 6787 ERR 11599 BTRACE 6: 0x0876f45b gg999Abort +0x025b

2009-01-21 13:55:01 6787 ERR 11599 BTRACE /opt/sdb/7605/pgm/kernel

2009-01-21 13:55:01 6787 ERR 11599 BTRACE Frameinfo [0x9768a048] (0x900d1e0,0x9768a100,0x1,0x1)

2009-01-21 13:55:01 6787 ERR 11599 BTRACE 7: 0x084963b3 ak93sending +0x0283

2009-01-21 13:55:01 6787 ERR 11599 BTRACE /opt/sdb/7605/pgm/kernel

2009-01-21 13:55:01 6787 ERR 11599 BTRACE Frameinfo [0x9768a168] (0x1,0x2,0x68,0x9768a43f)

2009-01-21 13:55:01 6787 ERR 11599 BTRACE 8: 0x084977e0 a93_user_commands +0x0310

2009-01-21 13:55:01 6787 ERR 11599 BTRACE /opt/sdb/7605/pgm/kernel

2009-01-21 13:55:01 6787 ERR 11599 BTRACE Frameinfo [0x9768a3a8] (0x9768a930,0x0,0x0,0x9768a43f)

2009-01-21 13:55:01 6787 ERR 11599 BTRACE 9: 0x08b13f16 Z7SQLTaskR20takall_command_globRhb +0x0086

2009-01-21 13:55:01 6787 ERR 11599 BTRACE /opt/sdb/7605/pgm/kernel

2009-01-21 13:55:01 6787 ERR 11599 BTRACE Frameinfo [0x9768a488] (0x9768a930,0x9768a926,0x9768a4a7,0xb7dc6814)

2009-01-21 13:55:01 6787 ERR 11599 BTRACE 10: 0x08b14288 Z11KernelMainR13RTETask_ITask +0x02c8

2009-01-21 13:55:01 6787 ERR 11599 BTRACE /opt/sdb/7605/pgm/kernel

2009-01-21 13:55:01 6787 ERR 11599 BTRACE Frameinfo [0x9768a8d8] (0x50105120,0x2,0x9768a930,0xb7d84e30)

2009-01-21 13:55:01 6787 ERR 11599 BTRACE 11: 0x08bb3557 RTETask_TaskMain +0x0047

2009-01-21 13:55:01 6787 ERR 11599 BTRACE /opt/sdb/7605/pgm/kernel

2009-01-21 13:55:01 6787 ERR 11599 BTRACE Frameinfo [0x9768bf98] (0x50105120,0x0,0x0,0x8ff98c0)

2009-01-21 13:55:01 6787 ERR 11599 BTRACE 12: 0x08c8a286 Z23en88CallKernelTaskMainP9TASK_TYPE +0x00c6

2009-01-21 13:55:01 6787 ERR 11599 BTRACE /opt/sdb/7605/pgm/kernel

2009-01-21 13:55:01 6787 ERR 11599 BTRACE Frameinfo [0x9768bfb8] (0x3281,0x3,0x8e2d70e,0x8e39f24)

2009-01-21 13:55:01 6787 ERR 11599 BTRACE 13: 0x004abb8b ___tls_get_addr@@GLIBC_2.3 +0x38b8b

2009-01-21 13:55:01 6787 ERR 11599 BTRACE /lib/i686/nosegneg/libc-2.5.so

2009-01-21 13:55:01 6787 ERR 11599 BTRACE Frameinfo [0x9768bfe8] (0x0,0x0,0x0,0x0)

2009-01-21 13:55:01 6787 ERR 11599 BTRACE -


> End of Stack Back Trace <----

2009-01-21 13:55:02 6787 ERR 7 Messages Begin of dump of registered messages

2009-01-21 13:55:02 6787 ERR 2 Admin A fatal error caused EMERGENCY SHUTDOWN. core is written

2009-01-21 13:55:02 6787 ERR 2 Admin A fatal error caused EMERGENCY SHUTDOWN. core is written

2009-01-21 13:55:02 6787 ERR 8 Messages End of the message list registry dump

2009-01-21 13:55:02 6787 ERR 51105 AK CACHE AK00001.dmp written: 0

2009-01-21 13:55:02 6787 ERR 11196 DBCRASH vabort:Emergency Shutdown, Task: 207

2009-01-21 13:55:02 0 ERR 12006 DBCRASH Kernel exited without core and exit status 0x200

2009-01-21 13:55:02 0 ERR 12010 DBCRASH Kernel exited exit code 2

2009-01-21 13:55:02 ___ Stopping GMT 2009-01-21 12:55:02 7.6.05 Build 009-121-191-997

lbreddemann
Active Contributor
0 Kudos

Hmm...

> 2009-01-21 13:54:59 6787 ERR 51261 TRIGGER system trigger failed with rc *1001

this looks odd.

Were the system tables correctly loaded on the source system?

Anyhow, you may try to change the parameter ENABLE_SYSTEM_TRIGGERS = NO and try the db_online again.

regards,

Lars

Former Member
0 Kudos

this looks odd.

Were the system tables correctly loaded on the source system?

It is odd, indeed!

I have two systems running copies of this instance without problems. Perharps this is because the souce database was migrated from maxdb 7.5 to 7.6.

Anyhow, you may try to change the parameter ENABLE_SYSTEM_TRIGGERS = NO and try the db_online again.

Anyway, now it's working like a charm in my test lab.

Thank you Lars and Markus! .-)

Melanie
Advisor
Advisor
0 Kudos

Hi,

are you sure that the system tables were loaded successfully on the source system?

Could you please check (on the target system) if you can load the system tables now, enable the system triggers again and restart the database? Does this work?

Thanks,

Melanie

Former Member
0 Kudos

are you sure that the system tables were loaded successfully on the source system?

Yes, they were.

Could you please check (on the target system) if you can load the system tables now, enable the system triggers again and restart the database? Does this work?

I've tried to load the system tables, but I can't. This is weird!

---

/opt/sdb/programs/bin/dbmcli on MY_DATABASE>db_online

OK

/opt/sdb/programs/bin/dbmcli on MY_DATABASE>load_systab

ERR

-24909,ERR_DBAUNKNOWN: SYSDBA unknown

/opt/sdb/programs/bin/dbmcli on MY_DATABASE>load_systab -u FOO,BAR

ERR

-24964,ERR_EXECUTE: error in program execution

256,/opt/sdb/7605/bin/x_python /opt/sdb/7605/env/lsystab.py -R /opt/sdb/7605 -d MY_DATABASE -u FOO,*

-


Traceback----


-


Error----


sql.SQLError: [-4008] (at 1) Unknown user name/password combination

Traceback (most recent call last):

File "/opt/sdb/7605/env/lsystab.py", line 202, in ?

connectAndInstall (install, install.__doc__)

File "/opt/sdb/7605/env/installib.py", line 404, in connectAndInstall

session = connect (options)

File "/opt/sdb/7605/env/installib.py", line 353, in connect

alterUserNotExclusive(options)

File "/opt/sdb/7605/env/installib.py", line 341, in alterUserNotExclusive

session.release()

AttributeError: 'NoneType' object has no attribute 'release'

Thanks for your help,

Xavi

Former Member
0 Kudos

Could it be the way I've created the destination instance?

I copy from our wiki the commands I should issue whenever I create a new instance. I've revised this procedure several times and checked your docs and howtos before opening this thread. It works fine when cloning a fresh instance.

/opt/sdb/programs/bin/dbmcli db_create DATABASENAME ADMIN,PASSWORD

opt/sdb/programs/bin/dbmcli -d DATABASENAME -u ADMIN,PASSWORD

param_startsession

param_init

param_put SESSION_TIMEOUT 900

param_put _UNICODE NO

param_put SERVERDBFOR_SAP YES

param_put MAXDATAVOLUMES 64

param_put MAXUSERTASKS 200

param_checkall

param_commitsession

param_addvolume 1 DATA DAT_0001 F 2621440

param_addvolume 1 LOG LOG_001 F 32000

param_addvolume 2 LOG LOG_002 F 32000

param_addvolume 3 LOG LOG_003 F 32000

param_addvolume 4 LOG LOG_004 F 32000

db_admin

Notice that USER != ADMIN !!

db_activate USER,PASSWORD

load_systab

auto_update_statistics ON

auto_extend ON

db_execute SET LOG AUTO OVERWRITE ON

Thanks,

Xavi

Melanie
Advisor
Advisor
0 Kudos

Hello Xavi,

with the described procedure you get an empty database. Which steps did you change to get the data from the source system intop your new database? Better: what did you do exactly?

Error -4008 means 'unknown user/password combination'. When you restored a backup from

one system to another, the SYSDBA user is also copied. So the user specified during load_systab needs to be the same as on the source system.

Can you perform a 'sql_connect FOO,BAR'?

Regards,

Melanie

Former Member
0 Kudos

with the described procedure you get an empty database. Which steps did you change to get the data from the source system intop your new database? Better: what did you do exactly?

I described the process in my first post

I issue the following commands to get the full data backup.

util_connect

medium_put MY_BACKUP "/tmp/my_backup" FILE DATA 0 8 NO

db_connect

backup_start MY_BACKUP

After the backup process is finished, I issue the following comands

to load the data backup in the new instance.

medium_put MY_BACKUP "/tmp/my_backup" FILE DATA 0 8 YES

db_admin

db_connect

db_activate RECOVER MY_BACKUP

db_online

Can you perform a 'sql_connect FOO,BAR'?

I can. It returns OK.

Melanie
Advisor
Advisor
0 Kudos

>

> I described the process in my first post

Yes, sorry, I saw that after I sent my answer...

>

>

>

> Can you perform a 'sql_connect FOO,BAR'?

>

> I can. It returns OK.

Hmm, that's strange.

After that sql_connect, what returns this:

sql_execute select sysdba from dual

Regards,

Melanie

Former Member
0 Kudos

Hi Melanie,

Hmm, that's strange.

After that sql_connect, what returns this:

sql_execute select sysdba from dual

/opt/sdb/programs/bin/dbmcli on MYDATABASE>sql_connect FOO,BAR

OK

---

/opt/sdb/programs/bin/dbmcli on MYDATABASE>sql_execute select sysdba from dual

OK

END

'FOO'

Regards,

Xavi

Melanie
Advisor
Advisor
0 Kudos

Hello Xavi,

could you please check the following:

1. Could you please confirm that you issued the "db_create DATABASENAME ADMIN,PASSWORD"

with a different user than FOO?

2. In file knldiag the parameters are listed in the beginning. Is the value listed there for CONTROLUSERID your correct dbm user (i.e. not FOO but ADMIN)?

3. Please check the sql connection with sqlcli:

sqlcli -d MYDATABASE -u FOO,BAR

sqlcli> select user from dual

Is that working as well?

Best regards,

Melanie

Former Member
0 Kudos

1. Could you please confirm that you issued the "db_create DATABASENAME ADMIN,PASSWORD"

with a different user than FOO?

ok. FOO has been ADMIN all the time. So, should it be the user used while issuing 'db_activate' command? I mean when creating an instance.

2. In file knldiag the parameters are listed in the beginning. Is the value listed there for CONTROLUSERID your correct dbm user (i.e. not FOO but ADMIN)?

knldiag:2009-01-23 08:55:24 12772 20235 RTE CONTROLUSERID=FOO

3. Please check the sql connection with sqlcli:

sqlcli -d MYDATABASE -u FOO,BAR

sqlcli> select user from dual

USER is no ADMIN --> db_activate USER,PASSWD

/opt/sdb/programs/bin/dbmcli -u USER,PASSWD -d DATABSE

Error! Connection failed to node (local) for database DATABASE:

-24950,ERR_USRFAIL: User authorization failed

Thanks for your help,

Xavi

Melanie
Advisor
Advisor
0 Kudos

Hello Xavi,

I'm getting confused...

We have two different users for MaxDB:

1. dbm operator - this user is specified during db_create

2. SYSDBA - this user is either specified during db_activate (when you create a new, empty instance) or taken from the backup (when you perform a system copy).

These have to be different user names!

Please tell me, which user name you used for which action. From knldiag it looks as if you used FOO for db_create but it is also the SYSDBA in the source (and therefore as well in the target) system.

Regards,

Melanie

Former Member
0 Kudos

Hi Melanie,

These have to be different user names!

I've reviewed again our documentation and I've found you are right. Although the procedure we use to create new instances is right, there was a mistake defining what users mean in this context. In other words, I was using a wrong user (operator) to create my new instance.

My new instance is working and I've been able to load a backup to clone the original database.

Thank you very much for your help and I apologize the inconvenience.

Regards,

Xavi

Melanie
Advisor
Advisor
0 Kudos

Hi Xavi,

thanks for the information.

I'm glad that it works now!

Best regards,

Melanie

Answers (1)

Answers (1)

markus_doehr2
Active Contributor
0 Kudos

Are source and target database software versions the same?

Markus

Former Member
0 Kudos

Yes, they are. The platform and the OS are also the same.

MaxDB 7.6.05

RHEL 5.2 x86

Xavi