The recovery depends on where the failure happened. For example,
if the RDFM_ view is there but application table is empty, then we need
to rebuild the application table and its index(es).
In any event, the MDSYS.RDF_LINK$ partition (for your model) should always
contain the triple data. The temporary table (behind the scenes) used to
hold unique triples is named 'RDFX_' || to_char(model_id, 'FMXXXXXXXXXXXXXXXX')
If you encounter this problem again, please note down the error message and
file a service request.
It occurs each time you call sem_apis.remove_duplicates on a totally new and empty semantic model.
This exception makes the underlying objects of the model unusable. Then one must must drop and recreate the Model :-\
To prevent from that crash, you have to test the NOT EMPTY state of the model before any call to sem_apis.remove_duplicates.
Here is a script output (188.8.131.52) to reproduce the issue :
SQL> CREATE TABLE family_rdf_data (id NUMBER, triple SDO_RDF_TRIPLE_S);