In-Memory Database Management Certificate (Open HPI)

I am please to announce that i have taken the Open HPI course and passed the quizzes + Final Exam and rewarded with ‘Record of Achievement’ .

openHPI is a platform for massive open online courses (MOOC) in the field of computer science and information technology. It is hosted at the Hasso Plattner Institute (HPI) in Potsdam, Germany. openHPI is open for everyone, participation is free of costs. Everybody can register and enroll for courses without any prerequisites. openHPI’s courses are derived from HPI’s bachelor and master programs in IT-Systems Engineering and cover both, foundations of information technology as well as highly topical innovations.

The Course was  taught by Prof. Hasso Plattner ( He is the Co-founder of SAP-AG Company and currently Chairman of the company), he is the person who envisioned SAP HANA and saw the importance of in-memory database in Enterprise Systems. He is an AMAZING pioneer & very well in teaching !!

My Certificate:

OpenHPI Certificate - In-Memory Data Management Implications on Enterprise Systems
OpenHPI Certificate – In-Memory Data Management Implications on Enterprise Systems

For certificate verification and authentication:

The Course is amazing and beneficial for DBA’s, IT Professionals, Project Managers, Enterprise System Architects.



EXPDP ORA-31693 ORA-02354 ORA-01555

while taking an export  (my Oracle Release is, i have faced with the below errors in the log file:

ORA-31693: Table data object “TESTSCHMA”.”VALUE_TABLE” failed to load/unload and is being skipped due to error:
ORA-02354: error in exporting/importing data
ORA-01555: snapshot too old: rollback segment number 9 with name “_SYSSMU9_2795927347$” too small

To Resolve this problem perform the following:


SQL>set pages 1000
SQL>set lines 300
SQL> show parameter undo;

———————————— ———– ——————————
undo_management string AUTO
undo_retention integer 900
undo_tablespace string UNDOTBS1
increase the undo_retention size:

SQL> alter system set undo_retention = 16500 scope = BOTH;

The LOB “retention” will not change automatically for LOB segements to verify this use the below query:

select table_name, column_name, nvl(retention, 0) retention, pctversion from dba_lobs where OWNER=’TESTSCHMA’;

To find all columns that have lobs use the following query:

select table_name, column_name from dba_lobs where OWNER=’TESTSCHMA’;

Then, use the “alter” command to change invidually each lob:

SQL> alter table TESTSCHMA.GRID_TABLE modify lob (SQLSTATEMENT) (retention);