Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sZSyt-001CnD-K6 for pgsql-general@arkaria.postgresql.org; Thu, 01 Aug 2024 10:24:23 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sZSxt-0075Iu-Jl for pgsql-general@arkaria.postgresql.org; Thu, 01 Aug 2024 10:23:21 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sZSxs-0075Im-WC for pgsql-general@lists.postgresql.org; Thu, 01 Aug 2024 10:23:21 +0000 Received: from mail-yw1-x112a.google.com ([2607:f8b0:4864:20::112a]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sZSxp-002WqR-Hd for pgsql-general@postgresql.org; Thu, 01 Aug 2024 10:23:19 +0000 Received: by mail-yw1-x112a.google.com with SMTP id 00721157ae682-654cf0a069eso50834777b3.1 for ; Thu, 01 Aug 2024 03:23:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1722507797; x=1723112597; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=P0YJV5XZKfmEKnYv0s3Xbnu/nDTl3cD85GK9EESPwzs=; b=Ls21fBoBALz4x2Tl570OaibRWieV5dnzSLR5KQjqidwdNWKIiH2Ucy8hsrqBcm7RhH VC3LJYx/Gfs3ed5qGaCQj0lJDaImwZ5PxgAby0OYpDbIKY8knP/HJXEWRoHREMqRRA5o kgO3mmT12Ct8XJkmU0FpQkOdz2ftKbKTuc3egzAf33RbZsOKrQSJCwOWfEwwgZQBgF8a jvpyosc89hxpPJjzKV0KEoGj2TStcDiuXkT/dHEJgWo/1+F9GKZ8s/ismHKOICVIBWUj CVTlVZIvwU+klGBrbME6oRHZUKcTrMYRpWezgKFV9B9O0VeBGP7ZUpzK5irCSnoBUKfE cbWA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1722507797; x=1723112597; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=P0YJV5XZKfmEKnYv0s3Xbnu/nDTl3cD85GK9EESPwzs=; b=I27ke9OUxDO4glVzJDd3bYPPi/hgA8z4XYIzxyngPvegqRRuLbFUHj+oteyotjMoxq fgMyvcOUF/rkyqUsZYv4C7ZYWUdoXBTjxIwdWzaWPYjk3SrIWPuFZz/kRLjsJRjK5gTF vCZ/cd6oLvGJuIk8IWzuL36mbgJwpOKTIzW9v1MrX3RPJ/B3LOBUxg7OyBfXM7hODYsm UTR2Xl1dwe5W81KCBOYKjHMw6Hr/habXCh3als8VlKOr3jWhtPUDoknirWrkncxLDLQG hnwCVS2ClNIyXwrmx5SW/E19qF97yQeHBmkjWTCcK6FAxbT8EAw7pfja2vvzpfF/T/KY zfcA== X-Gm-Message-State: AOJu0YzDPgddHBhnkbWlnFiuqkkzmKUanJMZ25eENmWa5Xfm5zLuGRmE Dhr2BIdxPRApRp/CQbMlNwryppE9PDi0l+fxAhLGssIhTvz8JK9XBdJJ1OvArtWA4/4c+atILjn bncFCCkS5pXEwOpVCsmWqumNSOkE= X-Google-Smtp-Source: AGHT+IE0VRm3CTGP2p4OAccG9P0OzVvBi+FEyUj9BuCUUl+BHu+vw+nyYiNbzrxw+eCcw7+/c7GkY8xYc3Fxe6U2FHY= X-Received: by 2002:a0d:d0c2:0:b0:65f:6322:d3b9 with SMTP id 00721157ae682-6874ba6cca0mr153477b3.20.1722507796656; Thu, 01 Aug 2024 03:23:16 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: KK CHN Date: Thu, 1 Aug 2024 16:02:08 +0530 Message-ID: Subject: Re: PgBackRest PTR recovery: After table drop to get dropped state To: Kashif Zeeshan Cc: pgsql-general Content-Type: multipart/alternative; boundary="00000000000057bd36061e9c999e" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000057bd36061e9c999e Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable The logs are here. https://pastecode.io/s/s5dp8ur1 On Thu, Aug 1, 2024 at 3:30=E2=80=AFPM Kashif Zeeshan wrote: > Hi > > On Thu, Aug 1, 2024 at 2:54=E2=80=AFPM KK CHN wrote: > >> List, >> >> *Not working (start EPAS server always fails):* >> >> 1. Testing PTR using PgBackRest(2.52.1) on RHEL9 EPAS-16, and RHEL9 ( >> Repo Server) >> >> When I do a PTR >> >> 1. After doing a table drop and then >> 2. Noting down the time stamp and then >> 3. Taking an incremental backup in hope that If I do a restore from this >> incr Backup, that won't contain the dropped table. >> 4. Correct me if I am conceptually wrong here. >> 5. I am *never *successful in restoring the EPAS server in this >> scenario. >> >> >> *I know the following will work for me, w*hy not the above one if I >> really want that state of cluster also ? >> >> *This is Working. * >> 1. Create table >> 2. Noting down the timestamp >> 3. Taking incremental backup on RepoServer. >> 4. drop the created table . >> 5. Then stop the EPAS server and do a PTR, by the --set=3Dstep 3 incr >> backup and target=3D step 2 time stamp .. It finished the pgaback resto= re >> and promote command >> 6. I am able to start back the EPAS server and see the dropped table >> recovered there. >> >> But If I want a PTR as in the first section it fails.. Why ? >> >> Thank you, >> Krishane >> >> >> >> >> >> *What I have done and results obtained: * >> >> Created a table important_table4 in my EPAS and note down the time after >> creation of this table it is ( t1 : "01-AUG-24 14:08:32.447796+05:30" = ) >> >> Then I performed an Incremental backup (incr backup: >> 20240729-160137F_20240801-141148I ) >> timestamp start/stop: 2024-08-01 14:11:48+05:30 / 2024-08-01 >> 14:11:52+05:30 >> >> >> Now I dropped the table table4 from the EPAS and noted down the time >> >> >> I want to restore the table4,, so I stopped EPAS and executed >> >> $ sudo -u enterprisedb pgbackrest --stanza=3DDemo_Repo --delta >> --set=3D20240729-160137F_20240801-141148I --target-timeline=3Dcurrent >> --type=3Dtime --target=3D"01-AUG-24 14:08:32.447796+05:30" >> --target-action=3Dpromote restore >> >> IT WORKS AS EXPECTED .. after restarting the EPAS I am able to get the >> important_table4 back. >> >> root@service01 ~]# sudo -u enterprisedb psql edb >> psql (16.3.0) >> Type "help" for help. >> >> edb=3D# \dt >> List of relations >> Schema | Name | Type | Owner >> --------+------------------+-------+-------------- >> public | important_table | table | enterprisedb >> public | important_table2 | table | enterprisedb >> public | important_table3 | table | enterprisedb >> public | important_table4 | table | enterprisedb >> (4 rows) >> >> SO all works fine !!!! . >> >> >> *But Now the PROBLEM Statement. * >> >> *1. I am dropping the table table 4 again * >> edb=3D# \q >> [root@service01 ~]# sudo -u enterprisedb psql -c "begin; drop table >> important_table4; commit;" edb >> BEGIN >> DROP TABLE >> COMMIT >> *2 . [root@service01 ~]#* sudo -u enterprisedb psql -Atc "select >> current_timestamp" edb 01-AUG-24 14:23:22.085076 +05:30 >> Noting the time as : (01-AUG-24 14:23:22.085076 +05:30 ) >> >> 3. Now I am performing an incremental backup after step 2 on REPO >> SErver ( Hoping that this latest INCR Backup is without dropped >> important_table4, so that a recovery of the cluster shouldn't show the >> table4 again. ) >> >> incr backup details. : 20240729-160137F_20240801-142433I >> timestamp start/stop*: 2024-08-01 14:24:33+05:30 / >> 2024-08-01 14:24:36+05:30* >> >> 4. Now I want to test the database recovery after dropping the table4 i= n >> step1 to verify that my EPAS restores from the backup in step 3 and time >> stamp (01-AUG-24 14:23:22.085076 +05:30, so that the restored EPAS >> cluster doesn't contain the important_table4. >> >> 5. $ sudo -u enterprisedb pgbackrest --stanza=3DDemo_Repo --delta >> --set=3D20240729-160137F_20240801-142433I --target-timeline=3Dcurrent >> --type=3Dtime --target=3D"01-AUG-24 14:23:22.085076+05:30" >> --target-action=3Dpromote restore >> ------------ >> ------------- >> INFO: restore command end: completed successfully (1035ms) >> >> *ISSUE: I am unable to get the EPAS Server* in running state after >> step 5 >> >> *What am I doing wrong ? OR am I conceptually wrong ?* >> >> >> >> >> OUTPUT on executing step 5. >> >> [root@service01 ~]# sudo -u enterprisedb pgbackrest --stanza=3DDemo_Repo >> --delta --set=3D20240729-160137F_20240801-142433I --target-timeline=3Dc= urrent >> --type=3Dtime --target=3D"01-AUG-24 14:23:22.085076+05:30" >> --target-action=3Dpromote restore >> >> 2024-08-01 14:30:03.535 P00 INFO: restore command begin 2.52.1: --delt= a >> --exec-id=3D82738-b5fe7415 --log-level-console=3Dinfo --log-level-file= =3Ddebug >> --pg1-path=3D/var/lib/edb/as16/data --pg-version-force=3D16 >> --repo1-host=3D10.10.20.7 --repo1-host-user=3Dpostgres >> --set=3D20240729-160137F_20240801-142433I --stanza=3DDemo_Repo >> --target=3D"01-AUG-24 14:23:22.085076+05:30" --target-action=3Dpromote >> --target-timeline=3Dcurrent --type=3Dtime >> 2024-08-01 14:30:03.880 P00 INFO: repo1: restore backup set >> 20240729-160137F_20240801-142433I, recovery will start at 2024-08-01 >> 14:24:33 >> 2024-08-01 14:30:03.881 P00 INFO: remove invalid files/links/paths fro= m >> '/var/lib/edb/as16/data' >> 2024-08-01 14:30:04.567 P00 INFO: write updated >> /var/lib/edb/as16/data/postgresql.auto.conf >> 2024-08-01 14:30:04.569 P00 INFO: restore global/pg_control (performed >> last to ensure aborted restores cannot be started) >> 2024-08-01 14:30:04.569 P00 INFO: restore size =3D 75.9MB, file total = =3D >> 2171 >> 2024-08-01 14:30:04.569 P00 INFO: restore command end: completed >> successfully (1035ms) >> *[root@service01 ~]# systemctl start edb-as-16.service* >> >> *Now If I check the server status : Its dead * >> >> [root@service01 ~]# systemctl status edb-as-16.service >> =C3=97 edb-as-16.service - EDB Postgres Advanced Server 16 >> Loaded: loaded (/etc/systemd/system/edb-as-16.service; disabled; >> preset: disabled) >> *Active: failed* (Result: exit-code) since Thu 2024-08-01 14:30:58 >> IST; 4s ago >> Duration: 228ms >> Process: 82752 ExecStartPre=3D/usr/edb/as16/bin/edb-as-16-check-db-d= ir >> ${PGDATA} (code=3Dexited, status=3D0/SUCCESS) >> Process: 82757 ExecStart=3D/usr/edb/as16/bin/edb-postgres -D ${PGDAT= A} >> (code=3Dexited, status=3D1/FAILURE) >> Main PID: 82757 (code=3Dexited, status=3D1/FAILURE) >> CPU: 325ms >> >> Aug 01 14:30:56 service01 systemd[1]: Starting EDB Postgres Advanced >> Server 16... >> Aug 01 14:30:56 service01 edb-postgres[82757]: 2024-08-01 14:30:56 IST >> LOG: redirecting log output to logging collector process >> Aug 01 14:30:56 rservice01 edb-postgres[82757]: 2024-08-01 14:30:56 IST >> HINT: Future log output will appear in directory "log". >> Aug 01 14:30:58 service01 systemd[1]: Started EDB Postgres Advanced >> Server 16. >> Aug 01 14:30:58 service01 systemd[1]: edb-as-16.service: Main process >> exited, code=3Dexited, status=3D1/FAILURE >> Aug 01 14:30:58 service01 systemd[1]: edb-as-16.service: Killing process >> 82758 (edb-postgres) with signal SIGKILL. >> A*ug 01 14:30:58 service01 systemd[1]: edb-as-16.service: Failed with >> result 'exit-code'.* >> [root@service01 ~]# >> >> Any hints/guidance most welcome. >> >> Can you please share the DB Server log as it contains the exact error > which is causing the server not to start. > > Thanks > --00000000000057bd36061e9c999e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
The logs are here.=C2=A0=C2=A0

<= /div>
O= n Thu, Aug 1, 2024 at 3:30=E2=80=AFPM Kashif Zeeshan <kashi.zeeshan@gmail.com> wrote:
Hi

On Thu, Aug 1, 2024 at 2:54=E2=80=AFPM KK CHN <kkchn.in@gmail.com> wrote:=
List,

Not working (start EPAS server alw= ays fails):=C2=A0

1. Testing PTR using=C2=A0 P= gBackRest(2.52.1)=C2=A0 on RHEL9=C2=A0 EPAS-16, and RHEL9 ( Repo=C2=A0 =C2= =A0 =C2=A0 =C2=A0Server)=C2=A0

=C2=A0 When I do a = PTR

1.=C2=A0 After doing a table drop and then
2. Noting down the time stamp and then=C2=A0
3. Taking an = incremental=C2=A0backup in hope that If I do a restore=C2=A0from this incr = Backup, that won't=C2=A0 contain the=C2=A0 dropped table.=C2=A0
4.=C2=A0Correct me=C2=A0 if I=C2=A0am=C2=A0 conceptually wrong here.=C2= =A0=C2=A0
5.=C2=A0 I am never successful in restoring the = EPAS server in this scenario.


I know the following=C2=A0will work for me, why not the above one = if I really want=C2=A0that state of cluster also=C2=A0 ?=C2=A0

This is Working.=C2=A0
=C2=A01. Create ta= ble=C2=A0
2. Noting down the timestamp
3.=C2=A0 Taking = incremental backup on RepoServer.
4. drop the created table .
5. Then stop the EPAS server and do a=C2=A0 PTR, by the=C2=A0 --set= =3Dstep 3 incr backup=C2=A0 and target=3D step 2 time stamp .. It finished = the pgaback=C2=A0restore and promote=C2=A0command
6. I am able to= start back the=C2=A0 EPAS server and see the dropped table recovered there= .

But If I want a PTR as in the first section it f= ails.. Why ?=C2=A0

Thank you,
Krishane





What I have done and results obtained:=C2=A0

=
Created a table important_table4 in my EPAS and note down the ti= me after creation of this table it is=C2=A0 ( t1 :=C2=A0 "01-AUG-24 14= :08:32.447796+05:30" )

Then I performed an In= cremental backup=C2=A0 =C2=A0(incr backup: 20240729-160137F_20240801-141148= I )
timestamp start/stop: 2024-08-01 14:11:48+05:30 / 2024-08-01 = 14:11:52+05:30


Now I dropped th= e table table4 from the EPAS and noted down the time=C2=A0


I want to=C2=A0 restore the table4,, so I stopped E= PAS and executed=C2=A0

$ sudo -u enterprisedb pgba= ckrest --stanza=3DDemo_Repo --delta --set=3D20240729-160137F_20240801-14114= 8I =C2=A0--target-timeline=3Dcurrent --type=3Dtime =C2=A0--target=3D"0= 1-AUG-24 14:08:32.447796+05:30" --target-action=3Dpromote restore
<= /div>

IT WORKS AS EXPECTED .. after restarting the EPAS = I am able to get the important_table4 back.=C2=A0

= root@service01 ~]# sudo -u enterprisedb psql edb
psql (16.3.0)
Type &= quot;help" for help.

edb=3D# \dt
=C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0 List of relations
=C2=A0Schema | =C2=A0 =C2= =A0 =C2=A0 Name =C2=A0 =C2=A0 =C2=A0 | Type =C2=A0| =C2=A0 =C2=A0Owner
-= -------+------------------+-------+--------------
=C2=A0public | importa= nt_table =C2=A0| table | enterprisedb
=C2=A0public | important_table2 | = table | enterprisedb
=C2=A0public | important_table3 | table | enterpris= edb
=C2=A0public | important_table4 | table | enterprisedb
(4 rows)
SO all works fine !!!! .=C2=A0

But Now the PROBLEM Statement.=C2=A0
<= br>
1. I am dropping the table table 4=C2=A0again=C2=A0
edb=3D# \q
[root@service01 ~]# sudo -u enterprisedb psql -c &quo= t;begin; drop table important_table4; commit;" edb
BEGIN
DROP TA= BLE
COMMIT
2 .=C2=A0 [root@service01 ~]# sudo -u enterprisedb = psql -Atc "select current_timestamp" edb=C2=A0 01-AUG-24 14:23:22= .085076 +05:30
Noting the time as :=C2=A0 =C2=A0(01-AUG-24 14= :23:22.085076 +05:30 )

3. Now=C2=A0 I am perfo= rming an incremental backup after step 2=C2=A0 on REPO SErver ( Hoping that= this latest INCR Backup is without dropped important_table4, so that a rec= overy of the cluster=C2=A0 shouldn't show the table4 again. )=C2=A0

=C2=A0 =C2=A0 =C2=A0 =C2=A0 incr backup details. : 20= 240729-160137F_20240801-142433I
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 timestamp start/stop: 2024-08-01 14:24:33+05:30 / 2024-08-01 14:24:3= 6+05:30

4. Now I want to test the database= recovery=C2=A0 after dropping the table4 in step1 to verify that my EPAS r= estores from the backup in step 3 and time stamp (01-AUG-24 14:23:22.085076= +05:30,=C2=A0 =C2=A0so that=C2=A0 the restored EPAS cluster doesn't co= ntain the important_table4.

5.=C2=A0 $ sudo -u ent= erprisedb pgbackrest --stanza=3DDemo_Repo --delta=C2=A0 =C2=A0--set=3D20240= 729-160137F_20240801-142433I =C2=A0--target-timeline=3Dcurrent --type=3Dtim= e =C2=A0--target=3D"01-AUG-24 14:23:22.085076+05:30" --target-act= ion=3Dpromote restore
=C2=A0------------
-------------<= /div>
INFO: restore command end: completed successfully (1035ms)

ISSUE:=C2=A0 =C2=A0 I am unable to get the EPAS S= erver in running state after step 5=C2=A0

=C2= =A0What am I doing=C2=A0wrong ?=C2=A0 OR am I conceptually wrong ?




OUTPUT= on executing step 5.=C2=A0

[root@service01 ~]# su= do -u enterprisedb pgbackrest --stanza=3DDemo_Repo --delta --set=3D20240729= -160137F_20240801-142433I =C2=A0--target-timeline=3Dcurrent --type=3Dtime = =C2=A0--target=3D"01-AUG-24 14:23:22.085076+05:30" --target-actio= n=3Dpromote restore

2024-08-01 14:30:03.535 P00 =C2=A0 INFO: = restore command begin 2.52.1: --delta --exec-id=3D82738-b5fe7415 --log-leve= l-console=3Dinfo --log-level-file=3Ddebug --pg1-path=3D/var/lib/edb/as16/da= ta --pg-version-force=3D16 --repo1-host=3D10.10.20.7 --repo1-host-user=3Dpo= stgres --set=3D20240729-160137F_20240801-142433I --stanza=3DDemo_Repo --tar= get=3D"01-AUG-24 14:23:22.085076+05:30" --target-action=3Dpromote= --target-timeline=3Dcurrent --type=3Dtime
2024-08-01 14:30:03.880 P00 = =C2=A0 INFO: repo1: restore backup set 20240729-160137F_20240801-142433I, r= ecovery will start at 2024-08-01 14:24:33
2024-08-01 14:30:03.881 P00 = =C2=A0 INFO: remove invalid files/links/paths from '/var/lib/edb/as16/d= ata'
2024-08-01 14:30:04.567 P00 =C2=A0 INFO: write updated /var/lib= /edb/as16/data/postgresql.auto.conf
2024-08-01 14:30:04.569 P00 =C2=A0 I= NFO: restore global/pg_control (performed last to ensure aborted restores c= annot be started)
2024-08-01 14:30:04.569 P00 =C2=A0 INFO: restore size = =3D 75.9MB, file total =3D 2171
2024-08-01 14:30:04.569 P00 =C2=A0 INFO:= restore command end: completed successfully (1035ms)
[root@service01= ~]# systemctl =C2=A0start edb-as-16.service

Now=C2=A0 If I check the server=C2=A0 status=C2=A0 :=C2=A0 =C2=A0Its = dead=C2=A0

[root@service01 ~]# systemctl = =C2=A0status edb-as-16.service
=C3=97 edb-as-16.service - EDB Postgres A= dvanced Server 16
=C2=A0 =C2=A0 =C2=A0Loaded: loaded (/etc/systemd/syste= m/edb-as-16.service; disabled; preset: disabled)
=C2=A0 =C2=A0 =C2=A0= Active: failed (Result: exit-code) since Thu 2024-08-01 14:30:58 IST; 4= s ago
=C2=A0 =C2=A0Duration: 228ms
=C2=A0 =C2=A0 Process: 82752 ExecS= tartPre=3D/usr/edb/as16/bin/edb-as-16-check-db-dir ${PGDATA} (code=3Dexited= , status=3D0/SUCCESS)
=C2=A0 =C2=A0 Process: 82757 ExecStart=3D/usr/edb/= as16/bin/edb-postgres -D ${PGDATA} (code=3Dexited, status=3D1/FAILURE)
= =C2=A0 =C2=A0Main PID: 82757 (code=3Dexited, status=3D1/FAILURE)
=C2=A0 = =C2=A0 =C2=A0 =C2=A0 CPU: 325ms

Aug 01 14:30:56 service01 systemd[1]= : Starting EDB Postgres Advanced Server 16...
Aug 01 14:30:56 service01 = edb-postgres[82757]: 2024-08-01 14:30:56 IST LOG: =C2=A0redirecting log out= put to logging collector process
Aug 01 14:30:56 rservice01 edb-postgres= [82757]: 2024-08-01 14:30:56 IST HINT: =C2=A0Future log output will appear = in directory "log".
Aug 01 14:30:58 service01 systemd[1]: Star= ted EDB Postgres Advanced Server 16.
Aug 01 14:30:58 service01 systemd[1= ]: edb-as-16.service: Main process exited, code=3Dexited, status=3D1/FAILUR= E
Aug 01 14:30:58 service01 systemd[1]: edb-as-16.service: Killing proce= ss 82758 (edb-postgres) with signal SIGKILL.
Aug 01 14:30:58 service0= 1 systemd[1]: edb-as-16.service: Failed with result 'exit-code'.
[root@service01 ~]#

Any hints/guidance mo= st welcome.=C2=A0

Can you pleas= e share the DB Server log as it contains the exact error which is causing t= he server not to start.

Thanks=C2=A0
--00000000000057bd36061e9c999e--