Warnings During Property Graph Creation

When creating a property graph, the property graph wizard validates the designed graph and reports any validation errors or warnings.

You can still create a property graph by ignoring these warnings. However, in most cases, the graph cannot be loaded into the in-memory graph server (PGX).

The following table lists the warning messages that are generated during property graph creation.

Warning Message Reason How to Fix

Warning Message	Reason	How to Fix
`Vertex table <table_name> has composite key (<composite_key>) which will prevent this graph from being loaded into memory.`	Vertex table cannot have a composite key. Note that this applies only for PGQL property graphs.	If you do not plan to load this graph into the in-memory graph server (PGX) for analysis, you can ignore this warning. Otherwise, to fix this warning, choose one of the following options: If you are using Oracle AI Database 26ai, then create a SQL property graph instead of a PGQL property graph. If the graph already exists, Graph Studio can help you to automatically convert it to a SQL Property graph. See Convert a PGQL Property Graph to SQL Property Graph for more information. If you are using Oracle Database 19c, then first upgrade it to Oracle AI Database 26ai. You can then convert the PGQL property graph into a SQL property graph (see Convert a PGQL Property Graph to SQL Property Graph). If SQL property graph is not an option, modify the vertex table which has composite keys to have a new column with unique IDs and declare that column as single primary key. This can be easily implemented using an `IDENTITY` column in the vertex table. Subsequently, you must alter all the edge tables pointing to this vertex to have an additional column that points to the new `IDENTITY` column. This can be achieved by first adding the column to the edge table and then having it filled through an `UPDATE` statement.
`Column <column_name> of table <table_name> will prevent this graph from being loaded into memory.`	Vertex or edge table columns must be one of the following types: `VARCHAR`, `VARCHAR2`, `NVARCHAR2`, `CHAR`, `NCHAR`, `NUMBER`, `BINARY_FLOAT`, `BINARY_DOUBLE`, `CLOB`, `DATE`, `TIMESTAMP`, `TIMESTAMP_WITH_LOCAL_TIME_ZONE`, `TIMESTAMP_WITH_TIME_ZONE`	If you do not plan to load this graph into the in-memory graph server (PGX) for analysis, you can ignore this warning. Otherwise, to fix this warning, choose one of the following options: Ensure that you do not declare the columns with incompatible types as properties in your graph. Include the columns in the graph definition, but exclude them when loading the graph into memory. See Manage Property Graphs for more information on loading a subset of graph properties into memory. Try to convert the data types of the columns into one of the supported types.
`Table <vertex/edge_table_name> does not have an index.`	Index is missing in the underlying database table for one or more of the following - vertex key, edge key, source, and destination key columns. Graph Studio recommends indexing the key columns to optimize graph query traversals and ensuring faster retrieval of nodes and edges.	Click Create Index on the warning message to add index for the specific column. Ensure that you to have the `CREATE INDEX` privilege on the underlying table. Otherwise, request the owner of the table to create the index. In this case, if you ignore the warning, the graph will still be loaded into the in-memory graph server (PGX).

Vertex table <table_name> has composite key (<composite_key>) which will prevent this graph from being loaded into memory.

Vertex table cannot have a composite key. Note that this applies only for PGQL property graphs.

If you do not plan to load this graph into the in-memory graph server (PGX) for analysis, you can ignore this warning.

Otherwise, to fix this warning, choose one of the following options:

If you are using Oracle AI Database 26ai, then create a SQL property graph instead of a PGQL property graph. If the graph already exists, Graph Studio can help you to automatically convert it to a SQL Property graph. See Convert a PGQL Property Graph to SQL Property Graph for more information.
If you are using Oracle Database 19c, then first upgrade it to Oracle AI Database 26ai. You can then convert the PGQL property graph into a SQL property graph (see Convert a PGQL Property Graph to SQL Property Graph).
If SQL property graph is not an option, modify the vertex table which has composite keys to have a new column with unique IDs and declare that column as single primary key. This can be easily implemented using an IDENTITY column in the vertex table. Subsequently, you must alter all the edge tables pointing to this vertex to have an additional column that points to the new IDENTITY column. This can be achieved by first adding the column to the edge table and then having it filled through an UPDATE statement.

Column <column_name> of table <table_name> will prevent this graph from being loaded into memory.

Vertex or edge table columns must be one of the following types:

VARCHAR, VARCHAR2, NVARCHAR2, CHAR, NCHAR, NUMBER, BINARY_FLOAT, BINARY_DOUBLE, CLOB, DATE, TIMESTAMP, TIMESTAMP_WITH_LOCAL_TIME_ZONE, TIMESTAMP_WITH_TIME_ZONE

If you do not plan to load this graph into the in-memory graph server (PGX) for analysis, you can ignore this warning.

Otherwise, to fix this warning, choose one of the following options:

Ensure that you do not declare the columns with incompatible types as properties in your graph.
Include the columns in the graph definition, but exclude them when loading the graph into memory. See Manage Property Graphs for more information on loading a subset of graph properties into memory.
Try to convert the data types of the columns into one of the supported types.

Table <vertex/edge_table_name> does not have an index.

Index is missing in the underlying database table for one or more of the following - vertex key, edge key, source, and destination key columns.

Graph Studio recommends indexing the key columns to optimize graph query traversals and ensuring faster retrieval of nodes and edges.

Click Create Index on the warning message to add index for the specific column. Ensure that you to have the CREATE INDEX privilege on the underlying table. Otherwise, request the owner of the table to create the index.

In this case, if you ignore the warning, the graph will still be loaded into the in-memory graph server (PGX).