We have been on 9.13 for a while have recently been getting reports of excel export issues for quite a few of our users. I wonder if any of you have experienced similar issue and may have any suggestion for us. Will appreciate any feedback I can get.
When they try to export a Search or Portlet results into an excel sheet, some of the column does not export a value but simply gives erorr message "Error 500: Unknown error" . And more critically, it does not export All the search results. Plus, interesting thing is, I as an Admin am not able to replicate the issue on my end. But when they try it, the issue apprers for them. This is affecting Serach Results, Portlet output as well as Request Browser results.
While trying to Export, unnecessary password prompts appear saying "window security". They can simply Cancel and move on but most people are irritated by the multiple password prompts they get while exporting.
Actually, I was also trying to move on to 9.14 but during research, i discovered that one of the critical patches of 9.14 (Patch 9.14.003) is NOT compatible with compressed tables and table spaces. Unfortunatley, we do have a couple of compressed table spaces as a result of PPM DMS implimentation. HP 9.13 Release doc had suggestion for compression for DMS so we did. Now it seems patch that was released well after that does not support compression. So, we are in kind of limbo :-( ... Strangely..Support is suggesting us to wait for the next SP. They said there were other customers with similar issues. So, wanted to check if anyone had any suggestion on that regard.
I confirmed the 0004 patch would be release around Nov 23.
Now, 0004 will have same compression dependency like patch 0003. I checked and this limitation in the installation/upgrade has been since PPM 9.1 SP1. You can see this on page 10 of PPM 9.1 SP1 release notes:
"The current release of PPM Center does not support table or tablespace compression in Oracle. If you use compressed tables or compressed tablespaces, the upgrade scripts will fail."
So, since that version you are able to see that note in all the release note of 9.12, 9.13, 9.14 and 9.14.0001/0002/0003.
Now, I checked the "PPM Center Database DMS Solution" white paper (attached to my response) and I'm able to see this note on page 3 (Technical Overview section):
"By default, document contents are stored in the default PPM tablespace USER_CLOB, while the metadata and the TEXT indexes (when created) are stored in the default PPM tablespace USER_DATA. DBAs can change the tablespaces used by PPM Center Database DMS. For example, to save DB disk space by compressing documents contents, or by tuning tablespace-level settings that would provide better performance for their specific usage. Such tablespace customizations are supported, but out of the scope of this document."
The recommendation provided here is to create separate tablesapaces used only by the DMS and not for PPM and then compress only those DMS tablespaces. Doing that you avoid the compress problem when upgrading PPM.
So the best option is to decompress the tablespaces, then create tablespaces for the DMS feature and compress them and the you will be able to upgrade to any PPM patch version.
Thanks Jonathan but I think I am a little confused here..
I am trying to verify this 100 % again with DBA again, but I don't think we have whole PPM DB compressed.
Our DBA only helped us in creating two “Compressed” dedicated table spaces FOR two BLOB columns called DOC_CONTENTS in KNTA_DOCUMENT_TIP_CONTENTS & KNTA_DOCUMENT_HISTORY_CONTENTS Tables. I think both these tables are only related to DMS. No?
So, does that mean, we should be OK even right now ?
Even though I provided the same information like I did in my last post, one of the Support Techs was not sure and cautioned me about data corruption possibilites and suggested me to hold off on applying SP 4. So, we haven't tried this at all. ... I think I will have to give this a try now in Non-Prod and hope everything does well.
However, please give me a couple of days. I have contacted the PPM RnD department to confirm what I found.
I'm pretty sure it will work. Since you already are in 9.13, where compressed tablespaces are not allowed and using DMS with a compressed tablespace for those tables, and this is working fine so the same should be for 9.14 and 9.14.xxxx
Thank You for Confirming this Jonathan. I am almost ready but thinking that since I alrady got held up this long, maybe I should wait till the end of this Nov and then apply the new .004 patch instead. Any way, Thanks Again !!