{"id":4340,"date":"2018-09-26T13:00:59","date_gmt":"2018-09-26T12:00:59","guid":{"rendered":"https:\/\/www.data-protector.org\/wordpress\/?p=4340"},"modified":"2018-10-26T15:13:57","modified_gmt":"2018-10-26T14:13:57","slug":"appserver-issues-when-upgrading-to-10-x","status":"publish","type":"post","link":"https:\/\/www.data-protector.org\/wordpress\/2018\/09\/appserver-issues-when-upgrading-to-10-x\/","title":{"rendered":"AppServer issues when upgrading to 10.x"},"content":{"rendered":"<p>The AppServer has become an integral part of Data Protector. When it fails neither user authentication, scheduling or reporting will work. A critical issue has been identified that may cause upgrades to fail and\/or run-time issues caused by invalid data stored in the <em>jce_service_description<\/em> and <em>jce_service_property<\/em> tables in the Data Protector JCE database.<\/p>\n<p><strong>Symptoms<\/strong><\/p>\n<p>During or after the upgrade from 8.1x or 9.x to 10.x you notice some or all of the following:<\/p>\n<ul>\n<li>AppServer is unresponsive or slowly responding when running\u00a0<em>omnidbutil -migrate_schedules<\/em>\n<ul>\n<li><i>Java process is <\/i>causing very high CPU load on Cell Manager<\/li>\n<li>The progress is slow and only returns errors (e.g.\u00a0pausing quartz scheduler&#8230;failed)<\/li>\n<\/ul>\n<\/li>\n<li>Java Exceptions and stack overflow getting logged in AppServer <em>server.log<\/em><\/li>\n<li>Backup sessions not getting executed while scheduler is active and jobs are scheduled<\/li>\n<li>Data Protector JCE database (part of IDB, used by Advanced and Consolidated Scheduler) is very large\n<ul>\n<li>Check the file size of <em>dpjce-data.idb<\/em> generated by\u00a0<em>omnidbutil -writedb<\/em> prior to the upgrade<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p><!--more--><\/p>\n<p><strong>Workaround<\/strong><\/p>\n<ul>\n<li>Perform an IDB backup (e.g. IDB online backup or <em>omnidbutil -writedb<\/em>)<\/li>\n<li>Stop the Data Protector services, but leave the IDB up by executing<\/li>\n<\/ul>\n<pre><em style=\"font-family: Consolas, Monaco, monospace;\">omnisv -stop -noidb<\/em><\/pre>\n<ul>\n<li>(Optional) Remove old logfiles from the <em>log\/AppServer<\/em> directory<\/li>\n<li>On <strong>Linux\/HP-UX<\/strong> Cell Managers execute:<\/li>\n<\/ul>\n<pre><em>cd \/opt\/omni\/sbin\/dbscripts\/CPE\r\nomnidbutil -run_script\u00a0QCCR2A65778_jce_purge_expired_records.sql -jce -detail<\/em><\/pre>\n<ul>\n<li>On <strong>Windows<\/strong> Cell Managers execute:<\/li>\n<\/ul>\n<pre><em style=\"font-family: Consolas, Monaco, monospace;\">cd \"%DP_HOME_DIR%\\bin\\dbscripts\\CPE\"\r\nomnidbutil -run_script QCCR2A65778_jce_purge_expired_records.sql -jce -detail<\/em><\/pre>\n<ul>\n<li>Start the remaining services by executing<\/li>\n<\/ul>\n<pre><em>omnisv -start<\/em><\/pre>\n<ul>\n<li>Run whatever command previously failed (e.g. <em>omnidbutil -migrate_schedules<\/em>, <em>perl\u00a0userMigrate.pl, etc.<\/em>)<\/li>\n<\/ul>\n<p><strong>Notes<\/strong><\/p>\n<p>The procedure above can be executed prior or after the upgrade. Just make sure to restart the AppServer after executing the SQL script.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The AppServer has become an integral part of Data Protector. When it fails neither user authentication, scheduling or reporting will work. A critical issue has been identified that may cause upgrades to fail and\/or run-time issues caused by invalid data stored in the jce_service_description and jce_service_property tables in the Data Protector JCE database. Symptoms During [&hellip;]<\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_mi_skip_tracking":false,"spay_email":""},"categories":[24,11],"tags":[],"translation":{"provider":"WPGlobus","version":"2.8.8","language":"en","enabled_languages":["en","de"],"languages":{"en":{"title":true,"content":true,"excerpt":false},"de":{"title":true,"content":true,"excerpt":false}}},"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p28cjj-180","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":4379,"url":"https:\/\/www.data-protector.org\/wordpress\/2018\/10\/data-protector-upgrade-paths\/","url_meta":{"origin":4340,"position":0},"title":"Data Protector Upgrade Paths","date":"29. October 2018","format":false,"excerpt":"{:en} Lately, we've been receiving more requests for potential Data Protector upgrade paths. This post includes a simple overview to guide you including intermediate steps necessary to upgrade to the latest version of the software. To reduce the amount of manual effort to a minimum you should always use the\u2026","rel":"","context":"In &quot;History&quot;","img":{"alt_text":"DP_Upgrade_Paths","src":"https:\/\/i0.wp.com\/www.data-protector.org\/wordpress\/wp-content\/uploads\/2018\/10\/DP_upgrade_paths_10-20.jpg?resize=350%2C200&ssl=1","width":350,"height":200},"classes":[]},{"id":1838,"url":"https:\/\/www.data-protector.org\/wordpress\/2014\/02\/current-patches-dp-8-0\/","url_meta":{"origin":4340,"position":1},"title":"Data Protector 8 &#8211; Patch Bundle 8.01","date":"3. February 2014","format":false,"excerpt":"{:en}On 2014\/01\/31 HP released patch bundle 8.01 for Linux, HP-UX and Windows. The update will fix many problems since version 8.00 was released, some were already addresses by SSP's - site specific patches. When looking at the patch description, about 100 fixes and some new features (support for vSphere 5.1\u2026","rel":"","context":"In &quot;DP A.08.00&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1365,"url":"https:\/\/www.data-protector.org\/wordpress\/2013\/05\/ipc-invalid-packet-size\/","url_meta":{"origin":4340,"position":2},"title":"IPC Invalid Packet Size","date":"8. May 2013","format":false,"excerpt":"{:en}After the upgrade to DP 7.01 in some environments the rarley error IPC Invalid Packet Size has been seen while accessing a changer or tape device. The problem might be related to a slow name resolutuion on the media agent. The INET may run into a timeout before sending data\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":4083,"url":"https:\/\/www.data-protector.org\/wordpress\/2018\/05\/sysbackup-oracle-12c\/","url_meta":{"origin":4340,"position":3},"title":"SYSBACKUP for Oracle 12c","date":"28. May 2018","format":false,"excerpt":"{:en}Starting with Oracle 12c three new administrative roles and users have been introduced to conform the principle of access to the least privilege. The users and roles named SYSBACKUP, SYSDG and SYSKM will be created when the database is created with their account in expired and locked status.\u00a0SYSBACKUP is used\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":3097,"url":"https:\/\/www.data-protector.org\/wordpress\/2016\/06\/hpe-data-protector-7-0x-8-0x-eol\/","url_meta":{"origin":4340,"position":4},"title":"HPE Data Protector 7.0X and 8.0X &#8211; EOL","date":"3. June 2016","format":false,"excerpt":"{:en} The time has come, this month the support for Data Protector 7.0x and 8.0x Data Protector will end. Support for version 8.1x will end 30\/06\/2017. Of course, all customers with an active maintenance contract can upgrade to the current Data Protector version 9.0x. Data Protector 9.0x includes enhancements like:\u2026","rel":"","context":"In &quot;Data Protector Links&quot;","img":{"alt_text":"","src":"https:\/\/i0.wp.com\/www.data-protector.org\/wordpress\/wp-content\/uploads\/2016\/06\/eol.png?resize=350%2C200&ssl=1","width":350,"height":200},"classes":[]},{"id":1412,"url":"https:\/\/www.data-protector.org\/wordpress\/2013\/06\/basics-installation-order-patches\/","url_meta":{"origin":4340,"position":5},"title":"Installation order of Patches","date":"3. June 2013","format":false,"excerpt":"{:de}Immer wieder stellt sich die Frage in welcher Reihenfolge die Patches f\u00fcr Data Protector installiert werden. Zwischen den einzelnen Patches ergeben sich Abh\u00e4ngigkeiten, welche man in den Beschreibungsdateien zum Patch nachlesen kann; diese m\u00fcssen bei der Installation eingehalten werden. Generell gilt folgende Reihenfolge f\u00fcr die Installation: sofern vorhanden: Patchbundle, Core,\u2026","rel":"","context":"In &quot;History&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"_links":{"self":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/4340"}],"collection":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/comments?post=4340"}],"version-history":[{"count":29,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/4340\/revisions"}],"predecessor-version":[{"id":4367,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/4340\/revisions\/4367"}],"wp:attachment":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/media?parent=4340"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/categories?post=4340"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/tags?post=4340"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}