@Lee Pinchbeck , thank you very much for the ping.Seems I had missed this post, my apologies. My colleague the other “Supun Ranatunge” had been tagged to the post As I recall we did mention to the customer that the recommended method is to use the installer & mentioned there won’t be any changes to the database.However their team was more concerned about several client files they had customized in some way, and was keen on not running the installer. On the topic of manually changing files:It’s always best to follow the R&D recommended method, which is using the installer. But for learning purposes it would be handy to know which client files to change manually in order to configure https on an FSM instance. So any reply/suggestion/discussion is welcome in this thread Thanks & Best Regards,Supun Ranatunga.
Hi All, I managed to find the cause.The upgrade is executed on a multi-tenant database, using the pluggable database as the upgrade DB.Now the pluggable DB had it’s job_queue_processes set to 16 when I checked.However the Container Database (CDB) had been set to job_queue_processes=0 It appears although the upgrade scripts are executed on the PDB, for some tables to enable rowkeys, job_queue_processes of the CDB must be enabled as well. Otherwise the rowkey enabling will partially progress and appear hanged at a certain table (as shown in the _enable_rowkey.log) Solution:Log into the CDB as SYS Execute the following query to set job_queue_processesALTER SYSTEM SET job_queue_processes=10; Now check the _enable_rowkey.log again and you will notice gradually it’s getting completed and other scripts begin to execute. P.S.While checking on this issue I noticed that sometimes there could be a bug where enabling rowkeys can get hung up when the DB is massive.For this instance however, that wa
Here is my follow-up comment to let you know troubleshooting steps up to now. First I tried running the upgrade with Rowkeys enabled for 3 hours.Once the upgrade came to the standstill point above, I checked active sessions to the database and it showed the session where the query showed as:BEGIN Database_SYS.Enable_Rowkey_Table('FND_ROLE_TAB'); Dbms_Output.Put_Line('Table FND_ROLE_TAB loaded at ' || TO_CHAR(SYSDATE,'YYYY-MM-DD HH24:MI:SS'));END; Now the row count of this table ‘FND_ROLE_TAB’ was 132 rows, which I assume is fairly low count & should not take this amount of time to finish. Then since I have all backups available, I killed the session to see what will happen. Once I killed the session, rest of the upgrade steps began to execute but with errors from time to time. Second time I ran the upgrade with Rowkeys Disabled Again we met with the same issue mentioned. Stuck with the log showing:Enabling of all rowkeys is not selected. Only keys designed as mandatory will be
Already have an account? Login
No account yet? Create an account
Enter your username or 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.
