Hi @Manashati Execute the bellow steps to rebuild the Index to resolve the above errors.1. Go to the specific search domain (“CustomerInvoices”.) details and RMB2. Select Drop Search Index3. Refresh search domain4. RMB and select Schedule Domain Activation5. Select a date/time to activate the search domain (Please select an OFFPEAK time).6. The system will rebuild the search domain and enable it in the given date/time.Additionally,Execute the following two statements log in as SYS user; which would first grant UTL_HTTP package to CTXSYS & then compile the invalid DRVDML package. In a multitenant (CDB) environment, connect as SYS to Container DB (not to PDB).GRANT EXECUTE ON UTL_HTTP TO CTXSYS; ALTER PACKAGE CTXSYS.DRVDML COMPILE BODY;Once done, disable & enable the search domains again. Try the additional steps and see if that helps!
try restarting the database and refresh the server cache from the application window
Hi @Rusiiiru,Not necessarily you need to do a reconfiguration after a server spec change. If the server has been restarted during the spec change then I would say doing a clean restart through the script would be beneficial.
Hi @Malin Norgren,IFSADMIN is a privileged superuser. As you know, authentication is not tied to WebLogic anymore. Instead, client apps interact with a single container called IFSIAM (IFS Identity and Access Management) to get authenticated. If an issue occurs at the IAM identity provider (Keycloak), you won’t have access to the application until it's fixed. In such a scenario, the IFSADMIN user becomes handy, as it provides a backdoor way to access the application. Do the admin access users have this privilege?
Hi @PROAHARPlease check if the below post helps your SSL wild card update. If not please share a screenshot of the error you get as the issue is not clear to me.
Hi @PROAHAR,You may find your current kubectl version and HELM version from the main_config.json file inside your config folder. If it has outdated versions according to the error you get, then you need to go to your build place and download the latest bootstrap files and bootstrap binary files and merge the zip as you did during the initial installation and make that as the main configuration location (rename the old ifsroot folder as ifsroot_old and make the new one as ifsroot) and move/copy the yaml files to it and run the SSL certificate update again. Hope this helps!
Here you go
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.