Upgrade Failure due to the presence of CtrlZ Failure
This issue (SD-118352) in fixed in version 14710. Post this release, these characters are handled in the migration itself. If you are planning to migrate from version less than 14610 to 14610, then you can directly migrate to 14710, to handle this ctrlz characters automatically. In certain upgrade flow in ServicedeskPlus, (refer below table), the postgres database bundled with the product is upgraded. During this upgrade process, data from the current postgres instance will be migrated to the new upgraded postgres instance 11.17. During this process, we use PostgreSQL tools pg_dump and pg_restore, to take backup and restore data from the old to the new PostgreSQL setup.
The below trace identified from logs shows that the issue is due to the presence of ^Z(ctrl+Z) character in your database. The presence of this character in any column interferes with the execution of the data migration of the consecutive column data of the same row. To Solve this issue we need to replace the ^Z characters using English sentences or words or even space would be fine. We have created an tool to clear this problematic characters from the database in order to proceed with migration.
For older releases, such as build version less than 10500, Refer this article to resolve this issue.
| Upgrade from version | Upgrade to Version |
Build Version < 14300 | 14300 |
Build Version < 14610 | 14610 and above |
Log Trace :
- Aug 3, 2023 11:19:19 AM [com.zoho.postgres.migrate.DumpMigration] [WARNING] : Error :::: ERROR: missing data for column "columnoldvalue"
- Aug 3, 2023 11:19:19 AM [com.zoho.postgres.migrate.DumpMigration] [INFO] : ERROR: missing data for column "columnoldvalue"
- Aug 3, 2023 11:19:19 AM [com.zoho.postgres.migrate.DumpMigration] [INFO] : CONTEXT: COPY hwaudithistory, line 8557585: "8479381 1443439 HardDiskInfo SERIALNUMBER H…øÿÿ�?ø"
(OR)
- Dec 4, 2023 8:52:33 PM [com.zoho.postgres.migrate.DumpMigration] [WARNING] : Error :::: ERROR: extra data after last expected column
- Dec 4, 2023 8:52:33 PM [com.zoho.postgres.migrate.DumpMigration] [INFO] : ERROR: extra data after last expected column
- Dec 4, 2023 8:52:33 PM [com.zoho.postgres.migrate.DumpMigration] [INFO] : CONTEXT: COPY aaaaccount, line 6057: "6845 6845 1 2 14921675104876846 6846 1 2 1492167511205"
Steps To Execute the Tool :
- Download the attached zip and extract it on the <servicedeskplus home> directory. A folder will be created at <servicedeskplus_home>\ctrlZScanner.
- Start the ServiceDeskPlus Service \ Database server.
- Navigate into <servicedeskplus_home>\ctrlZscanner folder and execute run.bat once the server is started.
- A log file named ctrlZScanner.log will be created.
- Stop the application server.
- Try upgrading the application after this.
Check whether the upgrade is a success. If the upgrade fails, a log file named ctrlZScanner.log will be created. share it with us. attach the logs folder too.
New to ADSelfService Plus?
Related Articles
solution for postgres 11 upgrade issues
When Supportcenter Plus is upgraded to 14300 or later, postgres is also upgraded to 11.17. If you are using bundled postgres, data migration through pgdump and restore mechanism also happens. To ensure efficiency in Postgres 11.17, make sure your ...SDP MSP solution for postgres 11 upgrade issues
When ServiceDesk Plus MSP is upgraded to 14300 or later, postgres is also upgraded to 11.17. If you are using bundled postgres, data migration through pgdump and restore mechanism also happens. To ensure efficiency in Postgres 11.17, make sure your ...Migration failure for Postgres Database with a blank space in it
Trace : \ManageEngine\ServiceDesk\Patch\AdventNet_ManageEngine_ServiceDesk_Plus-14.2.0-SP-1.0.0\SERVICEDESK\PreInstall\pg_migrate\pgsql_old\bin\pg_dumpall.exe", -U, postgres, -p, 65433, -h, 127.0.0.1, -r, -w, |, ...10.5 Linux Upgrade failure and solutions
Traces in logs : 1. java.lang.Exception: InitPgsqlScript exited with value :: 1 at com.adventnet.persistence.PostgresPreProcessor.executeInitPgsqlScript(PostgresPreProcessor.java:1733) 2. PGSQL Permission related errors. 3. SDP MSP installed as root ...Upgrade failure - Trying to start PostgresSQL server failed
Traces within the logs: [SYSERR] [INFO] : java.lang.Exception: java.net.ConnectException: Trying to start PostgresSQL server failed Please follow the steps below to address the same : 1. Stop the ServiceDesk Plus MSP service. 2. Open the command ...