Hi Mike,
Good to know problem is resolved. Please close this thread.
Regards,
Deepak Kori
Hi Mike,
Good to know problem is resolved. Please close this thread.
Regards,
Deepak Kori
Dear community,
I try to install "maxdb-studio-desktop-win-64bit-x86_64-7_9_08_20". I facedwith the same erroras inthis discussion http://scn.sap.com/thread/3225605
But i dont understand how i can solve my issue.
1)At the path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Windows i created registry key Param: SystemDirectory, Value %SystemRoot%\system32
2) Reboot
But it do not help me. Please help .
Dear Community,
Please tell me, where is mistake?
I try to reset password of DBA user SAPR3 using sqlcomand:
sqlcli -d SDB -u superdba,superdba ALTER PASSWORD SAPR3 SAPR3
but it not work and i recive answer of the system like :
0 rows affected (3772 usec)
Please help/
Hi Albert,
I didn't know a DBA user with the name SAPR3 in MaxDB. But there is a user SAP<SID>.
Maybe that is the mistake?
Regrads
Matthias
Hi Albert,
This looks to be a duplicate thread. REquest you to close this thread and monitor the resonse in other thread.
Regards,
Deepak Kori
Hello Albert,
your password has been altered. You can ignore the message. For DDL commands the row count
isn't set and will display '0 rows affected'
check the password change with
sqlcli -d SDB -u SAPR3,SAPR3 select user from dual
Regards,
Burkhard
It seems like it is ok, can you give somthing more comands for checking SAPR3 user new password?
Duplicate thread closed by moderator.
Please repeat your solution.
SOLVED:
I corrected reg.key :
Path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Windows
Param:SystemDirectory
Val: C:\Windows\System32
Type:REG_EXPAND_SZ
Hi Urs,
I triggered the colleagues again to check if only the version information -> The package includes versions 7.6.06.24, 7.7.07.45 and 7.8.02.37 for .... is wrong or if we really still have the old versions for download which is definitely wrong.
Thanks for the hint.
Regards, Christiane
Thanks for response. You`re right
Hello Chris,
There is some connections to MaxDB which interferes with the restore. In my case I was connected via dbmcli utility to the database, but the SSH session went down for network timeout leaving a process in hang status on the OS level. To avoid the error I manually killed the process and the restore started and finished successfully
Regards,
Valerio
Thanks for your reply! I solved this similarly myself by using the dbmcli instead of any GUIs. I tried many versions of the GUI and they all had this problem but when using the CLI, no such problems. Seems like a the GUI was trying to connect more than once or something similar.
Hi all,
I have a question regarding the usage of parameter MAXCPU. I have set it the value 3. But I do see only one cpu used and almost at 100% with the command "top".
My release is MAXDB 7.7 and the kernel for Linux is SMP.
Someone can tell me what influence this behaviour?
thank you all
Hi David,
We checked that note 1547309 and installed the MaxDB client once again.
Installation: S6E /sapdb/S6E/db
Base 7.9.08.21 valid 64 bit
DB Analyzer 7.9.08.21 valid 64 bit
Database Kernel 7.9.08.21 valid 64 bit
Fastload API 7.9.08.21 valid 64 bit
JDBC 7.6.09.00 valid
Loader 7.9.08.21 valid 64 bit
Messages MSG 0.10302 valid
ODBC 7.9.08.21 valid 64 bit
Redist Python 7.9.08.21 valid 64 bit
SAP Utilities 7.9.08.21 valid 64 bit
SQLDBC 7.9.08.21 valid 64 bit
SQLDBC 76 7.6.06.27 valid 64 bit
SQLDBC 77 7.9.08.21 valid 64 bit
Server Utilities 7.9.08.21 valid 64 bit
However the dump is still there in the system... any idea what couldbe wrong here?
Thanks
- Avi
His boss told us "Why there's a problem? That way we repaired the system last time."
epic...
Hi Avi,
You can check in SE14 for the table RSEUMOD and see if there have any inconsistencies.
Regards,
David
The program "SAPLSENA" has exceeded the maximum permitted runtime without
interruption and has therefore been terminated.
Can someone help me with the solution please?
Hello David,
Even running a DB consistency check in SE14 ends up in a dump.
Is there any other way to figure whats wrong with the DB tables. They seem to be in read only mode.
Warm Regards
- Avi