Issue with SAP Netweaver trial version, maybe due to database size

[Former Member]

Hi community,

I installed SAP Netweaver 702 Trial version with MaxDB on my home PC (run on Windows 😎 two years ago.

All was going fine, but since last days I am not able to open a SAP session anymore.

Management console indicators were in yellow state (messages "SAP MMC running but dialog queue standstill" and "SAP MMC running but bad queue time") but this issue has disappeared on its own since I have launched SAP MMC just after PC startup, no other application running... so this is OK.

But now, although SAP MMC indicators are in green state, when I open a SAP session and log in, nothing happens, the log screen is just waiting and my initial screen never comes.

Last thing I did when SAP was working fine, was to load a big amount of data into a specific table (mass loading from input files). It make me think that there may be some issue with database size. I have read some old threads about MaxDB logvolumes, but I do not understand what I should do. I am a developer but have not any administration skills.

Could you please suggest what I should do ?

Please keep in mind my OS is Microsoft Windows.

Thanks a lot.

Phil

[Former Member]

Hi Matt,

Thanks but I was unable to use successfully these commands .

But I have found the solution.

Actually there is a tool named "Database Manager" that has not been automatically installed with initial SAP installation. I have manually installed it. For me the installer was located here : NWABAPTRIAL70206_64\MAXDBTOOLS\DBM76.exe

Executing it, there is a "Backup" menu, then I have to connect to the Database Instance (for me it was named NSP) and log in with a Database Manager Operator account (SUPERBDA + password defined during the initial SAP installation).

After that, I did a full database backup, then a log backup, and finally activated the automatic log backup.

Now my SAP system is working again. 🙂

[Matt_Fraser]

Great news! Please mark your answer (or Martin's, if you think that is more appropriate) as "accepted" so that others can see the answer if they have the same problem.

Cheers,
Matt

[former_member233657]

Hi,

first you should install the MaxDB Studio. Afterwards you can easily administer your DB.

https://wiki.scn.sap.com/wiki/display/MaxDB/Database+Studio+7.9.08+News

I also believe that the logs are full. In your case, maybe the overwrite mode could be usefull.

http://maxdb.sap.com/doc/7_7/19/d2235b234b4339b07627c8a1f2bfab/content.htm

Kind regards,

Martin

[Former Member]

Hi Martin,

I just submitted my answer one minute after your message. Thank you for your information about MaxDB Studio.

Actually as you can read it below, I solved the problem with the MaxDB Database Manager provided in the SAP installation package.

[former_member233657]

Great. Just one more hint.

As of SAP MaxDB version 7.7, Database Studio replaces the Database Manager GUI, SQL Studio and Synchronization Manager tools.

https://wiki.scn.sap.com/wiki/display/MaxDB/SAP+MaxDB+Tools

Kind regards,
Martin

[Former Member]

Well noted with thanks 😉

[Former Member]

Hi Matt,

Thanks for your time and your answer.

OK so your advice is to begin with a backup of the log. How could I achieve this ? Among Windows programs installed with SAP trial version, the only relevant one is "SAP MaxDB Command Prompt". There is no MaxDB Database Manager GUI. I have no idea of the commands to be used to get a log backup.

Some web pages like this one provide commands examples but they do not work for me.

Thank you.

[Matt_Fraser]

Again, I'm no expert with MaxDB, but I imagine you can find what you're looking for here: https://wiki.scn.sap.com/wiki/display/MaxDB/HowTo+-+SAP+MaxDB+Backup+with+Database+Manager+CLI.

Cheers,
Matt

[Matt_Fraser]

Hi Phil,

The most likely cause is that the transaction log is full. I'm not a MaxDB expert -- I work with SQL Server -- but generally speaking if the transaction logs are full, then the database stops. You'll find advice out there about simply truncating the log, but that is not a best practice, as it can lead to data loss. The correct thing to do, at least with SQL Server, would be to get a backup (aka "dump") of the log, which should clear it and allow the database to operate again. If you can't back it up, that may indicate that you've never done a full backup of your database.

And to prevent this from happening again, take regular full and log backups of the database -- or set it to the MaxDB equivalent of "simple" mode, i.e. no logging, so the log doesn't fill up.

Cheers,
Matt