Hi All,There is an unpublished Oracle bug (32919011) involving with JDBC proxy connections which will cause this issue when PDB name and the service name are same . Try to rename/create the service name which will distinct from PDB name and try.This fails:PDB_name = pdbservice_name = pdb.acme.comJDBC URL: jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(PORT=1521)(HOST=<HOST>))(CONNECT_DATA=(SERVICE_NAME=pdb.acme.com)))But this works:PDB_name= pdbservice_name = pdb1.acme.comJDBC URL: jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(PORT=1521)(HOST=<HOST>))(CONNECT_DATA=(SERVICE_NAME=pdb1.acme.com)))Thanks !
May be it is a time out from the reverse proxy. Try to cross check the server timeout time and TCP idle timeout value of the proxy. If the values are almost like, increase the TCP idle time value from the proxy server and check. (Wonder what is proxy used)
It cloud be due to the Oracle Bug 34775863 (Patch 34775863 ). Solution is any of the following (from Oracle): 1. Upgrade to a database version where this fix is included, note this will be included in 19.19.0.0.230418DBRU which will release April 2023. 2. Apply Patch 34775863 if available for your platform and database version, if a patch is not available please create an SR with support to request one. 3. Use the following workaround:alter system set "_nlj_batching_enabled"=0;
Hi, You will use the update_http_certificates.cmd/.sh in your instance/bin folder. https://docs.ifs.com/techdocs/foundation1/020_installation/020_installing_fresh_system/040_installing_ifs_applications/030_deploy_middle_tier/hidden_itd/280_change_certificates.htm /Upul Hi Upul,It seems SSO using customers in SSL passthrough, are facing 500 error while trying to access over Admin Gateway after latest SSL certificate update. Following has been already attempted but issue persist. Appreciate if there are any comments for possible workaround.- update_http_certificates.cmd- rollover Certificate- apply cert in no load-balancer, then to ssl passthroughBest Regards,Binu
HI, It is possible to set the timeout from keycloak. But it will not persist. With the next delivery it will reset to default. /Subhashini Hi Subhashini,Could you please share some steps alter the keycloak timeout ?Hope it be used as a post delivery workaround until 23R2 release. Best Regards,Binu
@ChaGenegP Hope issue have been resolved by now.“Could not find file <ifs_home>/ifsdoc/doc_node.conf” usually occur when you running a cluster.cmd after a failed attempt of previous cluster installation. After a failed attempt, please delete all the files inside the cluster ifs home then unzip cluster.zip freshly.At the first failed attempt, verify C:\Program Files\Oracle\Inventory\ContentsXML has been created or there is already instance record saved. If already exist, remove the record and try with fresh cluster.zip unzip again.Regarding “Call to addMachine was not successful.” issue, verify node manager services in the main node is running and you can connect with telnet.CMD> telnet <main_node_host> <nodemanager_port> /Binu
@bdoucette There can be multiple reasons, please cross check the following.1. Both IFSPRINT F1 user and database user is active/open.2. Try using Crystal server IP instead name on application “System Parameters” window.3. Check Crystal Web Service/Services are up and running (restart IIS if necessary)4. Check database is accessible from Crystal server with given TNS name and IFSPRINT user.5. Retrieve Crystal logs from server (wwwroot/IFSCRWebSetup/logs/) or from application (“Crystal Web Service Logs” → Fetch Logs) then check for any errors which appears in the same time when you are viewing the report.(FYI : Depend on the number of instance copies, there can be multiple log files. Use the tile frames to identify the exact log)Good Luck,Binu
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.
