on 04-08-2009 9:38 AM
Hello,
I hope I'm right here to find a solution for my migration problem.
I have the SAPDB 7.4 in my own application. Now I want to migrate it to a newer Community version 7.6 or 7.7. Since MaxDB is back to SAP I will post my question here.
In a MySQL mailing list I found a comment that the migration from 7.4 to 7.6 should be done by simplify make a backup from 7.4 and restore it into 7.6 (http://lists.mysql.org/maxdb/26124)
I tried this with the DBM GUI. When I start a recovery with initialisation it says "Recovery has completed sucessfully". But than I can't restart the database instance:
-24988 SQL errir [info STATE -d]; -4004,Unknown table name:INFO_STATE
After this the instance is in online mode, but when I try to load the system tables I get:
-24964 error in program execution [load_systab ...]; 3,""C:\test\sapdb\depend\bin\x_python" "C:\test\sapdb\depend\env\lsystab.py" -R "C:\test\apdb\depend" -d MYDB -u dbam*"
I also found a post where some steps described for a migration from 7.3 to 7.6 (http://lists.mysql.com/maxdb/28720), but my source database is 7.4 and the command util_execute migrate give my a SQL error on 7.4
-24988,ERR_SQL: sql error
Is there any HowTo or tutorial how to migrate from SAPDB 7.4 to 7.6 or 7.7?
I hope, someone can help me....
Thanks in advanced and best regards,
Thomas
@Lars: Thanks for your response.
I also tried to use the update program SDBUPD.exe.
At first a popup window apperas twice with the message that SapNi.dll was not found:
Die Anwendung konnte nicht gestartet werden, weil SapNi.dll nicht gefunden wurde. Neuinstallation der Anwendung könnte das Problem beheben.
Than the upgrade process continues and finished until the system tables will be loaded and I get the same error message:
checking parameters...
switch database state to ADMIN
switch database state to ONLINE
loading system tables...
loading system tables failed
load_systab
ERR
-24964,ERR_EXECUTE: error in program execution
3,""C: estsapdbdepend inx_python" "C: estsapdbdependenvlsystab.py" -R "C: estsapdbdepend" -d MYDB -u dba,*"
Removing obsolete objects
Installing Loader tables
Installing messages and help
Installing SYSDBA tables
Installing comments for SYSDBA tables
Installing precompiler tables
Installing system tables for R3 backup information
Installing ODBC tables
Installing system tables for ORACLE (V7) mode
Installing data dictionary tables and views
Installing synonyms for oracle system tables
Installing comments on oracle sytem tables
Installing tables for WebAgent
Installing tables for Repository (WebDAV)
---------Traceback---------------
File "C: estsapdbdependenvinstallib.py", line 412, in connectAndInstall
installRoutine (session, options)
File "C: estsapdbdependenvlsystab.py", line 190, in install
"DBANA"
File "C: estsapdbdependenvinstallib.py", line 163, in include
install (session, options)
File "C: estsapdbdependenvREPOSITORY.py", line 415, in install
""")
---------Command-----------------
ALTER TABLE WEBDAV_PROPERTY MODIFY SHORT_VALUE CHAR(499) ASCII NOT NULL
---------Error-------------------
loader.LoaderError: [-25010] SQL [-8004] Constant must be compatible with column type and length (error position: 1)
MaxDB instance update exited abnormally at We, Apr 08, 2009 at 13:51:40
Is something wrong with my database?
I already took a look in the documentation but I can't find anything about migration from 7.4 to 7.6.
Btw. I don't have access to the SAP Marketplace and so I can't read some notes and documentation which are stored there.
Best regads,
Thomas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I also tried to use the update program SDBUPD.exe.
At first a popup window apperas twice with the message that SapNi.dll was not found:
Die Anwendung konnte nicht gestartet werden, weil SapNi.dll nicht gefunden wurde. Neuinstallation der Anwendung könnte das Problem beheben.
Never saw this one --- did you use the download package here from SDN ?
Than the upgrade process continues and finished until the system tables will be loaded and I get the same error message:
-
-
Command----
-
ALTER TABLE WEBDAV_PROPERTY MODIFY SHORT_VALUE CHAR(499) ASCII NOT NULL
-
-
Error----
-
loader.LoaderError: SQL Constant must be compatible with column type and length (error position: 1)
Did the load_sytab run through without problems before you performed the upgrade?
Is something wrong with my database?
I'd say - probably yes.
Do you use the WEBDAV_PROPERTY table?
If not you may circumvent this issue by dropping it...
I already took a look in the documentation but I can't find anything about migration from 7.4 to 7.6.
Btw. I don't have access to the SAP Marketplace and so I can't read some notes and documentation which are stored there.
Shouldn't be necessary.
regards,
Lars
Now it works.
Thanks a lot for the fast help.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hello friends,
i have in a is-u ecc6.0 with maxdb 7.6.04.16 the folowing six corrupt indieces:
SYSREPOSITORY WEBDAV_PROPERTY WEBDAV_PROPERTY_X1
SYSREPOSITORY WEBDAV_PROPERTY_NAME WEBDAV_PROPERTY_NAME_X1
SYSREPOSITORY WEBDAV_PROPERTY_NAMESPACE WEBDAV_PROPERTY_NAMESPACE_X1
SYSREPOSITORYSHARED WEBDAV_PROPERTY WEBDAV_PROPERTY_X1
SYSREPOSITORYSHARED WEBDAV_PROPERTY_NAME WEBDAV_PROPERTY_NAME_X1
SYSREPOSITORYSHARED WEBDAV_PROPERTY_NAMESPACE WEBDAV_PROPERTY_NAMESPACE_X1
can i recovery these indices without problems. i cant run a db_verify because these indices are corrupt.
many thanks,
christoph
> i have in a is-u ecc6.0 with maxdb 7.6.04.16 the folowing six corrupt indieces:
>
> SYSREPOSITORY WEBDAV_PROPERTY WEBDAV_PROPERTY_X1
> SYSREPOSITORY WEBDAV_PROPERTY_NAME WEBDAV_PROPERTY_NAME_X1
> SYSREPOSITORY WEBDAV_PROPERTY_NAMESPACE WEBDAV_PROPERTY_NAMESPACE_X1
> SYSREPOSITORYSHARED WEBDAV_PROPERTY WEBDAV_PROPERTY_X1
> SYSREPOSITORYSHARED WEBDAV_PROPERTY_NAME WEBDAV_PROPERTY_NAME_X1
> SYSREPOSITORYSHARED WEBDAV_PROPERTY_NAMESPACE WEBDAV_PROPERTY_NAMESPACE_X1
>
> can i recovery these indices without problems. i cant run a db_verify because these indices are corrupt.
Yes, you may simply run 'sql_recreateindex' without any problem.
regards,
Lars
ok, i just deleted all system tables wich started with WebDAV_* before I made a backup.
And now I can restore the backup into 7.6. I also will try it to use MaxDB 7.7.
Is this the right way to delete the tables?
Best Regards,
Thomas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
>
> ok, i just deleted all system tables wich started with WebDAV_* before I made a backup.
>
> And now I can restore the backup into 7.6. I also will try it to use MaxDB 7.7.
>
> Is this the right way to delete the tables?
Well, let's say it looks like it works
No, obviously, this is not how it should be and usually one should analyze this thing in more detail.
Anyhow, as you wrote that you don't use/need the WEBDEV feature and since the system tables get reloaded with load_systab anyhow, I see no harm in doing it 'the rough' way this time.
BTW: you DO have backups of your original database, right?
regards,
Lars
select * from WEBDAV_PROPERTY gives me some binary data
and the property of _UNICODE is true.
Currently we don't use WebDAV repository but it seams that there are some system tables for WebDAV.
I have deleted the WEBDAV_PROPERTY table and now the "load system tables"-command will insert something in this table:
Installing tables for Repository (WebDAV)
---------Traceback---------------
File "C:\test\sapdb\depend\env\installib.py", line 412, in connectAndInstall
installRoutine (session, options)
File "C:\test\sapdb\depend\env\lsystab.py", line 190, in install
"DBANA"
File "C:\test\sapdb\depend\env\installib.py", line 163, in include
install (session, options)
File "C:\test\sapdb\depend\env\REPOSITORY.py", line 298, in install
'W/""" + guid + """')
---------Command-----------------
INSERT WEBDAV_PROPERTY (CID, PROPERTY_ID, PROPERTY_SHORT_VALUE) VALUES
(x'000000000000000000000000000000000000000000000000',
x'000000000000000000000000000000000000000000000011',
'W/00000001ffed2b4500000d0400004e4880a5ebfb51996e52')
---------Error-------------------
How can I disable the whole WebDAV support in my old database?
Best regards,
Thomas
(P.s Sorry for my dumb question, but I'm not a database specialist)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
>
> Hello,
>
> I hope I'm right here to find a solution for my migration problem.
>
> I have the SAPDB 7.4 in my own application. Now I want to migrate it to a newer Community version 7.6 or 7.7. Since MaxDB is back to SAP I will post my question here.
Good choice.
> In a MySQL mailing list I found a comment that the migration from 7.4 to 7.6 should be done by simplify make a backup from 7.4 and restore it into 7.6 (http://lists.mysql.org/maxdb/26124)
Well - actually this is not the recommended procedure.
In fact this it not tested at all. It should work, yep - but there's no guarantee for it.
Why don't you simply use the standard way to upgrade your database?
Use SDBUPD or SDBSETUP and all necessary steps will be done automatically.
> I tried this with the DBM GUI. When I start a recovery with initialisation it says "Recovery has completed sucessfully". But than I can't restart the database instance:
>
-24988 SQL errir [info STATE -d]; -4004,Unknown table name:INFO_STATE
>
> After this the instance is in online mode, but when I try to load the system tables I get:
>
-24964 error in program execution [load_systab ...]; 3,""C:\test\sapdb\depend\bin\x_python" "C:\test\sapdb\depend\env\lsystab.py" -R "C:\test\apdb\depend" -d MYDB -u dbam*"
>
> I also found a post where some steps described for a migration from 7.3 to 7.6 (http://lists.mysql.com/maxdb/28720), but my source database is 7.4 and the command util_execute migrate give my a SQL error on 7.4
-24988,ERR_SQL: sql error
>
> Is there any HowTo or tutorial how to migrate from SAPDB 7.4 to 7.6 or 7.7?
Sure it's called 'documenation'.
You may want to take a look... [Installation Manual|http://maxdb.sap.com/doc/7_7/44/dd1681a23819d9e10000000a422035/content.htm].
In general it's a good idea to ensure that the system tables are properly loaded before you try the upgrade and that you use the most current patch of your old version (if available).
regards,
Lars
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I forgot something:
When I try to load the system tables for the recovered database I got this output too:
ERR
-24964,ERR_EXECUTE: error in program execution
3,""C:\test\sapdb\depend\bin\x_python" "C:\test\sapdb\depend\env\lsystab.py" -R "C:\test\sapdb\depend" -d SEETEC -u dba,*"
Removing obsolete objects
Installing Loader tables
Installing messages and help
Installing SYSDBA tables
Installing comments for SYSDBA tables
Installing precompiler tables
Installing system tables for R3 backup information
Installing ODBC tables
Installing system tables for ORACLE (V7) mode
Installing data dictionary tables and views
Installing synonyms for oracle system tables
Installing comments on oracle sytem tables
Installing tables for WebAgent
Installing tables for Repository (WebDAV)
---------Traceback---------------
File "C:\test\sapdb\depend\env\installib.py", line 412, in connectAndInstall
installRoutine (session, options)
File "C:\test\sapdb\depend\env\lsystab.py", line 190, in install
"DBANA"
File "C:\test\sapdb\depend\env\installib.py", line 163, in include
install (session, options)
File "C:\test\sapdb\depend\env\REPOSITORY.py", line 415, in install
""")
---------Command-----------------
ALTER TABLE WEBDAV_PROPERTY MODIFY SHORT_VALUE CHAR(499) ASCII NOT NULL
---------Error-------------------
loader.LoaderError: [-25010] SQL [-8004] Constant must be compatible with column type and length (error position: 1)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.