If the installation of FCC Studio is unsuccessful, you must reinstall the application after performing the required cleanup tasks.
To reinstall FCC Studio, follow these steps:
1. Execute the following command to delete the namespace of FCC Studio:
kubectl delete namespace <Namespace>
2. Navigate to the <Studio_Installation_Path> path and correct the parameters or files as suggested by the error.
3. Navigate to <Studio_Installation_Path>/secrets directory and re-enter the values of sensitive information in the studio-env.yml file. For example, STUDIO_DB_PASSWORD, HADOOP_PASSWORD-ALIAS, and so on.
4. Perform database clean up by performing the following:
Schema |
Applicable for OFSAA |
Applicable for non-OFSAA |
|---|---|---|
Yes |
Yes |
|
Yes |
No |
|
Yes |
No |
5. Redeploy FCC Studio. For more information, see Deploying FCC Studio on the K8s Cluster.
To clean up the Studio schema, follow these steps:
1. Drop the existing Studio schema and create a new Studio schema.
NOTE |
The username and password credentials of the Studio Schema in the wallet files must be updated accordingly. (If applicable) |
2. Grant the following permissions to the newly created Oracle Database Schema:
§ GRANT create session TO <Schema User>;
§ GRANT create table TO <Schema User>;
§ GRANT create view TO <Schema User>;
§ GRANT create any trigger TO <Schema User>;
§ GRANT create any procedure TO <Schema User>;
§ GRANT create sequence TO <Schema User>;
§ GRANT execute on dbms_rls TO <Schema User>;
§ GRANT execute on sys.dbms_session TO <Schema User>;
§ ALTER USER <Schema User> QUOTA 100M ON users;
§ GRANT create sequence TO <Schema User>;
§ GRANT create SYNONYM TO <Schema User>;
§ GRANT ALL privileges TO <Studio Schema User>;
NOTE |
If dropping the schema is not an option, drop the tables and sequences as mentioned in Appendix - Tables and Sequences. |
To clean up the BD or ECM Atomic Schema, follow these steps:
1. Log in to the BD or ECM Atomic Schema.
2. Truncate the DATABASECHANGELOG and DATABASECHANGELOGLOCK tables using the following command:
TRUNCATE TABLE DATABASECHANGELOGLOCK;
TRUNCATE TABLE DATABASECHANGELOG;
To clean up the BD or ECM Config schema, follow these steps:
1. Log in to the BD or ECM Config Schema.
2. Truncate the DATABASECHANGELOG and DATABASECHANGELOGLOCK tables using the following command:
TRUNCATE TABLE DATABASECHANGELOGLOCK;
TRUNCATE TABLE DATABASECHANGELOG;