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, |, "D:\ManageEngine\ServiceDesk\pgsql\bin\psql.exe", -U, postgres, -p, 65432, -h, 127.0.0.1, -w, servicedesk new]
- Jul 11, 2023 2:16:28 AM [com.zoho.postgres.migrate.DumpMigration] [INFO] : psql: warning: extra command-line argument "new" ignored
- Jul 11, 2023 2:16:28 AM [com.zoho.postgres.migrate.DumpMigration] [WARNING] : Error :::: psql: FATAL: database "servicedesk" does not exist
Cause :
In the Build version 14300(SDP) and 7000 (AE), PostgreSQL is upgraded to 11.17 from 10.21. During this upgrade, data migration will be taken place. In the process of migrating the data, above command will be executed. since the <database name> has a blank space in between, breaks into two arguments when we execute this in the command prompt.
Workaround : Rename the database to a name without space.
- Shut Down the Application service.
- Navigate to <Application_home_directory>\bin directory and execute "startDB.bat or startDB.sh"
- Navigate to <Application_home_directory>\pgsql\bin directory and connect as "postgres" user with the below command (Refer this KB) without entering the database name.
For Windows,
- psql.exe -U <username> -p <port> -h <server address>
For Linux.
- ./psql -U <username> -p <port> -h <server address>
- Execute the below command to rename the database,
Do not connect the database that you are going to rename
- ALTER DATABASE "<current database name>" RENAME TO "<database_name_without_space>";
- Update the modified name into the application, by executing "changeDBServer.bat or changeDBServer.sh"
- Stop the Database server by executing "stopDB.sh or stopDB.bat"
After these steps, invoke the upgrade.
New to ADSelfService Plus?
Related Articles
Upgrade failure when migrating privileges for removed functions
LOG Trace : 03.08.2023 12:50:36 [com.zoho.postgres.migrate.DumpMigration] [SCHWERWIEGEND] : Problem during upgrade.com.zoho.postgres.exception.MigrationFailureException: Restoration failed for PRE_DATA at ...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 ...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 ...How to Connect External Postgres
Install a External Postgres such that the version of that postgres is currently in the series of inbuilt postgres of our Application. Say for example, In Servicedeskplus Application version 14010, which has postgres version 10.21, then you should ...Error While connecting default Postgres Database
If you are getting the below error while connecting the postgresDB , please follow the steps below : Error : psql: FATAL: no pg_hba.conf entry for host “::1”, user “postgres”, database “servicedesk”,SSL off Please open pg_hba.conf under [ServiceDesk ...