Solved

SAP HANA backup failure

  • 14 April 2022
  • 4 replies
  • 5651 views

Userlevel 1
Badge +6

Backup failed for SAP HANA database

ERROR CODE: [18:146]

DESCRIPTION: SAP HANA Error [hdbsql execution Failed, Database may not be online; Otherwise check the connection credentials].

NOTE: The command line logs backup completed with no error (I think this mean the database is online and the credentials are correct)

JOB LOGS:

12268 3454  04/14 09:22:31 34691 Servant    [---- IMMEDIATE BACKUP REQUEST ----], taskid [8254] Clnt[mhdanadev] AppType[SAP HANA][135] BkpSet[MHD] SubClnt[default] BkpLevel[Full][1]

 

12268 1140  04/14 09:22:32 34691 Scheduler  Phase [4-Database Backup] (0,0) started on [mhdhanadev.egc.local] in [0] second(s) - ClSapAgent   BACKUP -j 34691 -a 2:190 -t 1 -jt 34691:4:1:0:56048 -data -at 135 -d HQ-COMMSRV.MiningSector.lcl*hq-commsrv*8400

 

12268 1a40  04/14 09:22:32 34691 Servant    Reg [Control] received. Client [mhdhanadev] plattype = 4. Token [34691:4:1:0:56048]

 

12268 573c  04/14 09:22:34 34691 Scheduler  Set pending cause [SAP HANA Error [hdbsql execution Failed.

 

12268 1a40  04/14 09:22:34 34691 Scheduler  Phase [Failed] message received from [mhdhanadev.egc.local] Module [ClHanaAgent] Token [34691:4:1:0:56048] restartPhase [0]

 

12268 1a40  04/14 09:22:34 34691 Delay Msg  successfully deleteSavedJMJobUpdateMsgByJob

 

12268 1a40  04/14 09:22:34 34691 JobSvr Obj Phase [4-Database Backup] for Backup Job Failed. Backup will continue with phase [Database Backup].

 

12268 1a40  04/14 09:22:34 34691 ArchiveMgr JMArMgr::releaseAllJobStreams() Calling CvResourceManager::releaseJobStreams(jobType=1,appType=135,logicalRelease=true)

 

12268 573c  04/14 09:22:34 34691 Database   DB Token [34691:4:2] doesn't match with the token [34691:4:1:0:56048] provided by client. Error :[The job token is for an older attempt than that of the job. AttemptNo in client token [1]. Current AttemptNo of job [2].]

 

12268 573c  04/14 09:22:34 34691 Scheduler  Phase [Failed] message for the wrong token [34691:4:1:0:56048] from [mhdhanadev.egc.local] Module [ClHanaAgent]. Ignoring the message.

 

12268 1a40  04/14 09:22:34 34691 Database   DB Token [34691:4:2] doesn't match with the token [34691:4:1:0:56048] provided by client. Error :[The job token is for an older attempt than that of the job. AttemptNo in client token [1]. Current AttemptNo of job [2].]

 

12268 1a40  04/14 09:22:34 34691 Scheduler  Job [Failed] message for the wrong token [34691:4:1:0:56048] from [mhdhanadev.egc.local] Module [ClHanaAgent]. Ignoring the message.

icon

Best answer by Mostafa Amin 18 April 2022, 09:49

View original

If you have a question or comment, please create a topic

4 replies

Userlevel 7
Badge +23

Try this:

SAPHANA0002: SAP HANA Restore from a Selective Copy Fails

Issue

If you restore from a selective copy, the restore may fail because the software cannot find the catalog. You may get an error similar to the following:

Error Code: [18:146] Description: SAP HANA Error [One or more files could not be located on the media]. Source: hana02, Process: backint_hana

Solution:

Set the CV_restCopyPrec configuration file parameter to 0 and then perform the restore.

 

https://documentation.commvault.com/11.24/expert/22517_troubleshooting_sap_hana_data_agent_01.html

Userlevel 1
Badge +6

@Mike Struening 
Thank you for replying
But my issue is a backup issue not a restore issue.
Also I don’t use selective copy for this instance.

Userlevel 5
Badge +13

@Mostafa Amin 

The command line backups will succeed even when the credentials configured in the GUI aren’t correct, because they are initiated by HANA directly.

Here the error message is indicating hdbsql command is failing by some reason.

12268 573c  04/14 09:22:34 34691 Scheduler  Set pending cause [SAP HANA Error [hdbsql execution Failed.

 

Can you try to update the SAP HANA instance properties from GUI and see if it throws the same error?

 

Thanks,

Sunil-

 

Userlevel 1
Badge +6

@Sunil 
Thank you,
I contacted the SAP HANA team, they reset the password of the user.
Then I updated the password on the Commcell console.
Everything work fine now.