Forum Discussion

pasilva1's avatar
pasilva1
Level 0
2 years ago

The Oracle backup did not start

27/10/2023 09:04:35 - Info bpbrm (pid=60323) The data-in-transit encryption (DTE) is disabled for the client (MY_SERVER) as the global DTE mode is set to 'Preferred Off' and the client DTE mode is set to 'Automatic'
27/10/2023 09:04:35 - Info nbjm (pid=3655) starting backup job (jobid=51594) for client MY_SERVER, policy MY_INSTANCEDB, schedule Logs
27/10/2023 09:04:35 - Info nbjm (pid=3655) requesting MEDIA_SERVER_ONLY resources from RB for backup job (jobid=51594, request id:{FF058B7C-74C0-11EE-9D5A-40257A45A3BC})
27/10/2023 09:04:35 - requesting resource  dp_nbumsdpa-stu
27/10/2023 09:04:35 - estimated 0 kbytes needed
27/10/2023 09:04:35 - Info nbjm (pid=3655) started backup (backupid=MY_SERVER_1698408275) job for client MY_SERVER, policy MY_INSTANCEDB, schedule Logs on storage unit 
27/10/2023 09:04:35 - started process bpbrm (pid=60323)
27/10/2023 09:04:36 - Info bpbrm (pid=60323) MY_SERVER is the host to backup data from
27/10/2023 09:04:36 - Info bpbrm (pid=60323) reading file list for client
27/10/2023 09:04:36 - Info bpbrm (pid=60323) starting bphdb on client
27/10/2023 09:04:36 - Info bphdb (pid=8080) Backup started
27/10/2023 09:04:36 - connecting
27/10/2023 09:04:36 - connected; connect time: 0:00:00
27/10/2023 09:04:37 - Info bphdb (pid=8080) INF - ************************************************************
27/10/2023 09:04:37 - Info bphdb (pid=8080) INF - Backup Information:
27/10/2023 09:04:37 - Info bphdb (pid=8080) INF -  Client: MY_SERVER
27/10/2023 09:04:37 - Info bphdb (pid=8080) INF -  ORACLE_SID: MY_INSTANCE
27/10/2023 09:04:37 - Info bphdb (pid=8080) INF -  ORACLE_HOME: /u01/app/oracle/product/12.1.0/dbhome_1
27/10/2023 09:04:37 - Info bphdb (pid=8080) INF -  Objects being backed up:
27/10/2023 09:04:37 - Info bphdb (pid=8080) INF -  Archive Logs
27/10/2023 09:04:37 - Info bphdb (pid=8080) INF -  Control File
27/10/2023 09:04:37 - Info bphdb (pid=8080) INF -  Number of channels to allocate (archive logs): 1
27/10/2023 09:04:37 - Info bphdb (pid=8080) INF -  Oracle Authentication is being used
27/10/2023 09:04:37 - Info bphdb (pid=8080) INF -  RMAN Default Limits will be used (Archive Logs)
27/10/2023 09:04:37 - Info bphdb (pid=8080) INF -  Backup File Name Formats:
27/10/2023 09:04:37 - Info bphdb (pid=8080) INF -  Archive Log: arch_d%d_u%u_s%s_p%p_t%t
27/10/2023 09:04:37 - Info bphdb (pid=8080) INF -  Control File: ctrl_d%d_u%u_s%s_p%p_t%t
27/10/2023 09:04:37 - Info bphdb (pid=8080) INF - End of Backup Information
27/10/2023 09:04:37 - Info bphdb (pid=8080) INF - ************************************************************
27/10/2023 09:04:48 - Error bpbrm (pid=60323) from client MY_SERVER: ERR - bphdb exit status = 5455: The Oracle backup did not start.
27/10/2023 09:04:48 - Info bphdb (pid=8080) done. status: 5455: The Oracle backup did not start.
27/10/2023 09:04:48 - end writing
The Oracle backup did not start.  (5455)

20
Linux
  • RamNagalla's avatar
    RamNagalla
    Moderator
    2 years ago

    please check https://www.veritas.com/support/en_US/article.100053912

    Cause

    1) Although these libraries like libclntsh.so and libnnz19.so are present at the Oracle home path, but when backup runs via Oracle Intelligent Policy, it looks for these libraries at /usr/openv/lib

    2) Check the user which customer trying has got sufficient permission to access the libraries or isolate it.

    Solution

    1) Implement the following work around in case you root cause is missing libraries.

    - Check the bpdbsbora logs and make a note of the libraries that the backup job is failing on.

    - Copy these libraries from the Oracle home path to /usr/openv/lib

    - Also create a soft link for library libclntsh.so  as shown in example below, and then the backup will work.

    Example:

    After analyzing the bpdbsbora log, below libraries must be copied from the Oracle home path to /usr/openv/lib and a soft link created to allow the backup job to be successful.

    -rwxrwxrwx  1 root root  6587832 Aug 31 16:38 libnnz19.so
    -rwxrwxrwx  1 root root  8040712 Aug 31 16:42 libclntshcore.so.19.1
    -rwxrwxrwx  1 root root 79942576 Aug 31 16:42 libclntsh.so.19.1
    lrwxrwxrwx  1 root root       17 Aug 31 16:44 libclntsh.so -> libclntsh.so.19.1

    2) Try following if the issue is with the user permission.

    - Please try the SYS or SYSTEM user from oracle to register the OIP from master. As these are power user, 

    we should able to register the instance. which indicates the issue with user customer facing issue with. Adding the 

    right permission on the preferred user should fix the issue.

    3) Check whether RMAN catalog check box is checked and the credentials for the same are correct, This can occur due to communication issues with the RMAN Catalog Server in the oracle application, The dba have to look into it.

  • Hamza_H's avatar
    Hamza_H
    Moderator
    2 years ago

    Please share more details to better understand the issue here, as putting only DS won't give us much..

    is it a new installation? was it working before? did you check bphdb logs?

    from the error and the behavior that you have, I think the TN shared by RamNagalla is a good start, but please always share more details.

    Thanks,