FAQ

I see many sections with (-1) result lines. What does it mean?

(-1) result means that the SQL that is executed to extract the data from the OCI360 model failed by some reason, and most of the times is because the underlying accessed table does not exists. Usually when the table is not created is because the json file is not inside the zip. And most of the times, when the json is not generated is because you don't have any data at all (or access permissions) for that particular type.

• Check if you have the json file for that table inside your extraction ZIP. The relation TABLE <> JSON can be checked via oci_table_json.csv.
• Check for any loading errors at 00009_oci360_0a_internal.log file (section 8b) within the output zip.

My database tables are not getting populated even though the json ZIP is there.

• Ensure oci360_load_mode is unset before calling @oci360.sql.
• Check for any loading errors at 00009_oci360_0a_internal.log file (section 8b) within the output zip.

The oci_json_export.sh is taking hours to export the OS-Objects (oci_os_object.json).

Unfortunately when you have hundreds of thousands of Objects in the OS, the oci-cli will take time on this section.

• You can skip this section running "export OCI_JSON_EXCLUDE='OS-Objects'" before calling the oci_json_export.sh.

When I open section 1a, I get an error "Failed to load ontology. WebVOWL runs in a local instance...".

If you open the OCI360 zip locally in your computer instead of through a web server, the CORS functionality of Chrome and Firefox will prevent it from automatically opening the ontology. You can workaround this issue by manually uploading the json file:

PS: You can optionally temporarily disable CORS:

• In Firefox though "about:config" and change the security.fileuri.strict_origin_policy from true to false.
• In Chrome, starting the browser passing the --disable-web-security parameter.

I'm getting ORA- errors on Search Index creation

On search index creation, sometimes you can get locked this Oracle Database bug.

CREATE SEARCH INDEX "OCI360_TMP_OCI360_INDEX"
*
ERROR at line 1:
ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-20000: Oracle Text error:
DRG-50857: oracle error in drixmd.PurgeKGL
ORA-20000: Oracle Text error:
DRG-50857: oracle error in drdmlpo
ORA-20000: Oracle Text error:
DRG-10502: index 5394 does not exist
DRG-10507: duplicate index name: OCI360_TMP_OCI360_INDEX
ORA-06512: at "CTXSYS.DRUE", line 183
ORA-06512: at "CTXSYS.DRVXMD", line 45
ORA-06512: at line 1
ORA-06510: PL/SQL: unhandled user
ORA-30576: ConText Option dictionary loading error
ORA-06510: PL/SQL: unhandled user-defined exception
ORA-06512: at "CTXSYS.DRIXMD", line 2543
ORA-00001: unique constraint (CTXSYS.DRC$IDX_
DRG-50610: internal error: kglpurge []
ORA-06512: at "CTXSYS.DRUE", line 183
ORA-06512: at "CTXSYS.TEXTINDEXMETHODS", line 320

This is a bug.

The easiest solution for now is to recreate your whole schema.