Hi Siva,
As your using Comvault for the backup solution do check below things:-
when you run the backup do the pipe_mem1 get created under below folders, which will confirm that the issue is not at SAP end if the files are getting created.
/db2/SID/sapdb/data/files
Reading the Backint for MaxDB configuration file '/commvault/opt/simpana/SapMaxDbAgent/backint.conf'.
Found keyword 'BACKINT' with value '/commvault/opt/simpana/SapMaxDbAgent/backint'.
Found keyword 'INPUT' with value '/commvault/opt/simpana/SapMaxDbAgent/in'.
Created temporary file '/commvault/opt/simpana/SapMaxDbAgent/err' as error output for Backint for MaxDB.
Writing '/db2/SID/sapdb/data/files/pipe_mem1 #PIPE' to the input file.
Also i can see for the logs the backup opration is timing out.:-
Prepare passed successfully.
015-03-02 00:03:47 The database is working on the request.
2015-03-02 00:04:37 The database is working on the request.
2015-03-02 00:05:03 Canceling Utility-task after a timeout of 300 seconds elapsed ...
OK.
2015-03-02 00:05:04 The database has finished work on the request.
Receiving a reply from the database kernel.
Reply from db-kernel:
SQL-Code :-903
End of reply from db-kernel.
The backup operation has ended.
So check with the backup team about the Backup media server where your taking backups to tape is it timing out. Check the backinit file for same.
Also can you let me know if your using dbmcli command lines and version of your MAXdb as there are some limitation for version support by comvault.
And in meantime can you try to reinstall the Comvault agent and install a SAPMaxDB agent as we are using the specific SAPMAxDB agent of comvault in our setup.
Let me know if this helps.
Regards,
Ram