SAP HANA Developer Edition 1.00 SPS10
In all the hustle and hubbub of SAP TechEd in Barcelona this past week some of you may have missed the fact we launched the brand new SAP HANA Developer Edition sporting revision 101 and SPS10!
As in previous versions this one sports several pre-loaded applications and demos as well as pre-configured users and information. You can also easily enabled HTTPS communication using the self signed certificate and quickly import Delivery Units (DU). It also has Smart Data Streaming pre-loaded – so plenty of reasons to check it out!
You can find it through the SAP Developer Center, HANA Developer Center: Start Developing with HANA | SAP
Also be sure to check out the HANA EFFECTS podcast, very interesting stuff for those diving into the HANA world.
I didn't miss it! Thanks very much, enjoying playing with SPS10!
What does one do however, when the the es_server logs are filled up?
ES Server process has stopped as it's data and log volumes are chock-a-block (/hana/shared/HDB/data_es/ and /hana/shared/HDB/log_es/). I've had a look at resizing the volumes in AWS, but they're all labelled xvdf through xvdq, and I don't know which corresponds to what. Have also performs diagnosis file deletion, but to little effect.
You can just clear the log files.
Hi Craig, thanks for the reply.
So the trouble is that the data file is also full-up. Is this as simple as deleting the physical log file? i.e. /hana/shared/HDB/log_es/HDB/mnt00001/es/eslog? There are two log files in there - is it safe to just delete them?
Performing a backup and then issuing the command ALTER SYSTEM RECLAIM LOG will clear the log files. Never delete any of them directly at the file system level.
if you can't perform the backup then try this note
1. Stop the database:
2. Change into the folder mnt00001 of the logvolume (Default: /usr/sap/<SID>/global/hdb/log):
3. You have to move one of the logvolumes temporarily to another volume where enough space is available. You should free at least 2 GB of space to ensure that the database has enough space to start. To find out the space consumption of each volume execute:
du -sh *
4. Move a volume which consumes at least 2 GB of space (e.g. hdb00003) to a volume with enough free space, e.g. to the data volume (Default: /usr/sap/<SID>/global/hdb/data):
mv hdb00003 /usr/sap/<SID>/global/hdb/data
5. Create a symbolic link to the new folder in the old location:
ln -s /usr/sap/<SID>/global/hdb/data/hdb00003 /usr/sap/<SID>/global/hdb/log/mnt00001/hdb00003
6. Start the database (HDB start) and perform a backup.
7. Wait until log backups are performed.
8. Use the following SQL-Statement to clean up the logvolume:
ALTER SYSTEM RECLAIM LOG;
9. Stop the database again and remove the symbolic link:
rm -f /usr/sap/<SID>/global/hdb/log/mnt00001/hdb00003
11. Move the log volume back to its original location:
mv /usr/sap/<SID>/global/hdb/data/hdb00003 /usr/sap/<SID>/global/hdb/log/mnt00001
12. Start the database (HDB start)
it was a dynamic tiering issue, which Robert Waywell resolved for me.
Thank you for your suggestions and time.