The requirement for the Oracle client is for Metadata service that is not using the JDBC driver, since its a Golang application and not JAVA, therefore in order to support the connection between Artifactory < > Database, we would need to install the thin client (type 4) and the OCI (type 2).
The above error message indicates that it is unable to insert a row. Thus, when you are setting up a new Oracle database for Artifactory to use, Artifactory requires RESOURCE, CONNECT, CREATE SEQUENCE and ALTER privileges.
You can refer to this Knowledge Base Article which explains this further.
Once the valid permissions are granted, in some cases, you may have to ensure that the access_schema_version table exists and if it has any duplicate values such as the same table but in upper case letters (ACCESS_SCHEMA_VERSION). If that is the case, copy the content from the upper case table to the lower case table.
2023-04-07T05:37:45.975Z [1;33m[jfac ][0;39m [31m[WARN ][0;39m [a4e2087d3c885808] [o.j.s.u.DbStatementUtils:62 ] [Catalina-utility-1 ] - Failed to execute query: ORA-01950: no privileges on tablespace 'ARTIFACTORY': CREATE TABLE access_tokens( token_id VARCHAR2(36) NOT NULL, subject VARCHAR2(255) NOT NULL, owner VARCHAR2(255) NOT NULL, created NUMBER(19, 0) NOT NULL, expiry NUMBER(19, 0), refresh_token VARCHAR2(128), scope VARCHAR2(255), token_type VARCHAR(255), username VARCHAR(255), description VARCHAR2(1024), payload VARCHAR2(4000), hashed_reference VARCHAR2(255), CONSTRAINT access_tokens_pk PRIMARY KEY (token_id) ) 2023-04-07T05:37:45.978Z [1;33m[jfac ][0;39m [1;31m[ERROR][0;39m [a4e2087d3c885808] [.s.d.u.AccessJdbcHelperImpl:77] [Catalina-utility-1 ] - Could not initialize database: java.lang.IllegalStateException: Could not initialize database: ORA-01950: no privileges on tablespace 'ARTIFACTORY'
The above error message indicates that it is unable to insert a row. Thus, when you are setting up a new Oracle database for Artifactory to use, Artifactory requires RESOURCE, CONNECT, CREATE SEQUENCE and ALTER privileges.
You can refer to this Knowledge Base Article which explains this further.
Once the valid permissions are granted, in some cases, you may have to ensure that the access_schema_version table exists and if it has any duplicate values such as the same table but in upper case letters (ACCESS_SCHEMA_VERSION). If that is the case, copy the content from the upper case table to the lower case table.