This is a short article that focuses on the method of how to send an…
Upgrading to PostgreSQL 12 Error
Background: This UIP was on multiple two machines (OA_Metadata & VA_MidTier)
Note: During UIP there was no error or warning message occurred on both servers.
We’ve followed these steps for upgrade PostgreSQL to 12 using this link on both servers: https://documentation.sas.com/doc/en/pgmsascdc/9.4_3.5/whatsdiff/p1quw1jx2w8eyxn1bt9l85mf296z.htm
Steps:
- Run the SAS Deployment Wizard from your software depot.
- Select Install SAS software and click Next.
- Select an existing SAS Home and click Next.
- Select Install Additional Software and click Next.
- Select the SAS Web Infrastructure Platform Data Server check box and click Next.
- Click Next through the next several steps, and then click Start.
- When the installation has completed successfully, click Next and Finish.
But we’re getting this error message below when try to run.bat script (run.bat –metaserver abc.local.com –metaport 8561 –metauser sasadm@saspw –metapass XXXXXX –upgrade) under this directory <SASHome>/SASWebInfrastructurePlatformDataServer/9.4/scripts/upgrade in OA_Metadata server
2022.04.28_16:46:05 ERROR: The system reached a timeout while waiting for the server to come up. Processing will not continue for this dataserver.
Caught: java.io.FileNotFoundException: D:\SAS\Config\Lev1\WebInfrastructurePlatformDataServer\data\pg_hba.conf (The system cannot find the path specified)
java.io.FileNotFoundException: D:\SAS\Config\Lev1\WebInfrastructurePlatformDataServer\data\pg_hba.conf (The system cannot find the path specified)
at pgupdate.UpdatePostgres.disableSecurity(UpdatePostgres.groovy:958)
at pgupdate.UpdatePostgres$disableSecurity$24.callCurrent(Unknown Source)
at pgupdate.UpdatePostgres.updateInstance(UpdatePostgres.groovy:1166)
at pgupdate.UpdatePostgres$updateInstance$3.call(Unknown Source)
at pgupdate.SearchForPGInstances.updateDBInstance(SearchForPGInstances.groovy:294)
at pgupdate.SearchForPGInstances$updateDBInstance$16.call(Unknown Source)
at pgupdate.SearchForPGInstances$_main_closure4.doCall(SearchForPGInstances.groovy:848)
at pgupdate.SearchForPGInstances.main(SearchForPGInstances.groovy:723)
D:\Program Files\SASHome\SASWebInfrastructurePlatformDataServer\9.4\scripts\upgrade>
Resolution steps are listed below:
- We’ve noticed these three folders under this directory <SASHome>/SASWebInfrastructurePlatformDataServer
- 9.4 –> Run this script to check Postgre version <SASHome>\SASWebInfrastructurePlatformDataServer\9.4\bin\postgres.exe –version and the version is 12.9
- 9.4_PREVIOUS –> Run this script to check Postgre version <SASHome>\SASWebInfrastructurePlatformDataServer\9.4_PREVIOUS-yyyy-mm-dd-HH.MM.SS\bin\postgres.exe –version and the version is 12.3
- 9.4_PREVIOUS-yyyy-mm-dd-HH.MM.SS –> Run this script to check Postgre version <SASHome>\SASWebInfrastructurePlatformDataServer\9.4_PREVIOUS-yyyy-mm-dd-HH.MM.SS\bin\postgres.exe –version and the version is 9.1*
We renamed these two directories:
- 9.4_PREVIOUS to 9.4_PREVIOUS_Hold
- 9.4_PREVIOUS-yyyy-mm-dd-HH.MM.SS to 9.4_PREVIOUS
And we run this script run.bat (run.bat –metaserver abc.local.com –metaport 8561 –metauser sasadm@saspw –metapass XXXXXX –upgrade) under this directory <SASHome>/SASWebInfrastructurePlatformDataServer/9.4/scripts/upgrade via command prompt (CMD) and now this time no error or warning was occurred.
On VA_MidTier server, the PostgreSQL is already upgraded to 12.9. So no need to run this script run.bat (<SASHome>/SASWebInfrastructurePlatformDataServer/9.4/scripts/upgrade)
