Hi Sharath,
for the first time, you can input any password. Next time, you need to remember the password.
Does it work?
Best regards,
James
Hi Sharath,
for the first time, you can input any password. Next time, you need to remember the password.
Does it work?
Best regards,
James
hi James
As soon as i launch MaxDB studio.. it straight away is asking for password... it does not give any option to set password.. any password i give, it says cannot incorrect password
Regards
sharath
Hi Sharath,
Please rename file:
c:\users\<username>.eclipse\org.eclipse.eqinox.security
Then you can input the first password again.
Best regards,
James
Thanks a lot James.. it worked.. it asked me set new password... it is fine now
regards
sharath
Hi Sharath,
You are welcome.
Best regards,
James
Hi DB experts,
during a "harmless looking" SUM operation with MaxDB 7.9.8.34
ALTER TABLE "DAAG_PTO" modify ("PARTITIONING_OBJECT" VARCHAR2 (000030))
we got a
SQL-error "-602-POS(1) System error: Move error" in DDL statement for "DAAG_PTO "
In Kernel log we have:
20011: Bad parameter: source size [8192] dest size [8192], source addr [0x7fc40ad6b048]+1, dest addr [0x7fc49214f000]+81, -515 bytes to copy; module vbd37+noPIC.cpp, pos 584,_FILE=vbd37+noPIC.cpp,_LINE=584
Thread 0x13BD Task 74 2015-11-29 13:36:18 ERR SYSERROR 51080: Move error
Thread 0x13BD Task 74 2015-11-29 13:36:18 ERR MOVECODE 20011: Bad parameter: source size [8192] dest size [8192], source addr [0x7fc40ad6b048]+1, dest addr [0x7fc49214f000]+81, -515 bytes to copy; module vbd37+noPIC.cpp, pos 584,_FILE=vbd37+noPIC.cpp,_LINE=584
2015-11-29 13:36:18 ERR MOVECODE 20013: Module vbd37+noPIC.cpp, pos 584,_FILE=SAPDB_RangeCode+noPIC.cpp,_LINE=86
Thread 0x13BD Task 74 2015-11-29 13:36:21 ERR MOVECODE 20011: Bad parameter: source size [8192] dest size [8192], source addr [0x7fc40ad6b048]+1, dest addr [0x7fc4ac507000]+81, -515 bytes to copy; module vbd37+noPIC.cpp, pos 584,_FILE=vbd37+noPIC.cpp,_LINE=584
There where some PTS fixed in lower releases but it seems not in DDL context.
Anybody fixed this already ?
Thanks in advance,
Matthias
Hi Mathias,
this seems to be a new error. I will check this with development team and let you know as soon as we have the reason about it.
Regards, Christiane
Hi Matthias,
would you please open an OSS ticket for this issue and store there as well how we can connect the system in the secure area. SAPDB connection to this system would be helpful.
We need to have more information about the table strucutre etc.
Please tell us the OSS ticket number.
Thanks,
Christiane
Hi Christiane,
thanks for the quick help. We opend a OSS ticket. Could you follow me in SCN, than I'll pass you the ticket number and the contact details.
Thanks,
Matthias
hi James
Hope you can help me on another issue.. on the studio, when i am adding LC servers and trying to connect with the user and password, it is not connecting... saying wrong username/password... The same username and password are being used by my colleagues and it connects for them
regards
sharath
Hi Experts,
We are working on setting up Content Server on HA(as per my knowledge HA for Content server in not available). Here we are installing MAXDB(software- local disks and DB-shared disks) on node 1 and only maxdb software executables on node2, trying to achieve HA for MAXDB ...
HowTo - Embed SAP MaxDB in MSCS - MaxDB - SCN Wiki
I am following above link along with many other sap notes
1726396 - Integration of SAP MaxDB/liveCache 7.8/7.9 into MSCS
1727123 - FAQ SAP MaxDB/liveCache Isolated Software
1694323 - FAQ: SAP MaxDB remote SQL server and DBM server
I am struck at registering MAXDB in cluster manager
I executed the command "sapdbmscsman -C" as per the wiki, the maxdb group should appear in the Microsoft Cluster Management Console-MCMC(I don't see any in my MCMC)
2. Adding the network resource to the MaxDB cluster group:
set network="external LAN connection"
set ipaddress=<virtual IP address for DB host>
set netmask=<netmask>
%WINDOWS%\Cluster\sapdbmscsman -B "%network%,%ipaddress%,%netmask%,Disk D:"
Should I run the set commands or can i directly execute "sapdbmscsman -B "%network%,%ipaddress%,%netmask%,Disk D:"
Any suggestions?
Regards,
Leela.
Hi again,
thanks to the quick response of the MaxDB support team.
They investigated the reason and created the note http://service.sap.com/sap/support/notes/2253487
to fix the actual issue and prevent potentionally future issus.
Best regards,
Matthias
Hi sharath,
Are you able to connect maxdb via dbmcli command?
dbmcli -d <dbsid> -u <username>,<password> db_state
If your colleague can connect database with the same user and password, then I would say the problem is from the client side.
Best regards,
James
Hi Daniela,
please check the SQLMode which you are using during the import into MaxDB.
I expect that you are doing the import with SQLMODE Internal which is the MaxDB syntax.
If you switch to the SQLMode ORACLE ( which is a partly oracle compatible mode) todate is available in this mode.
You set this SQLMODe during connect. See MaxDB docuemntation for more details about the SQLMODE.
Regards, Christiane
Hi All,
we are planning to move our Live cache stand alone database which is SAP MAX DB 7.9 from 2008R2 to 2012R2(Vmware) due to hardware license expiry.
Requesting to let me know which standard procedure do i have to follow?
More information of versions involved:
==========================
SCM 7.02
SAP MAXDB 7.9
Current procedure which we are planning to follow:
1)Matching resources in between source and target.
2)Installing SAP MAX DB software and SAP MAX DB studio in target a head.
3)Taking the full backup from source.
4)Restoring full backup into target which taken from source.
5)change the configuration items in LC10
6)Start Live cache.
Please let me know if we have any standard document to follow for this activity.
Hi Edy,
1. Error message -> -4011 Unkown index name
This error tells you that the index which should be dropped does not exist on the database level.
You can check with MaxDb System table indexes if this index really does not exist on database level -> select * from domain.indexes where indexname = 'E071K~ULI'
If this index does not exist on database level this error message can be ignored.
2. Error message -1452 duplicate secondary key
This error message sounds like there is already an index created on the table ZMIMT_DRP_STO to check this use the folowing commands
select * from domain.indexes where tablename = 'ZMIMT_DRP_STO' check the output if the index
ZMIMT_DRP_STO~Z01 already exist.
If the index already exists everything looks fine. and as well this error message can be ignored.
The reason why such error can happen can be if you stop and restart the import, then it can happen the actions logged in the table INDEXSTATEMENTS are already executed but not deleted from the table. This is an error in the logic of the import but no database error.
Regards, Christiane
Thank you Christiane,
I will test this.
Best regards,
Daniela
http://service.sap.com/sap/support/notes/1007129
This note will give some hints for the migration.
Please check as well the SAP migration docuemntation for the steps before and after the migration.
Regards, Christiane
http://service.sap.com/sap/support/notes/39439
You can use SAP note to create the xuser entries.
Regards, Christiane