Topic
  • 1 reply
  • Latest Post - ‏2007-09-13T08:22:07Z by SystemAdmin
SystemAdmin
SystemAdmin
17917 Posts

Pinned topic ERROR SQL2071N after redirect restore during connect to database

‏2007-09-12T14:52:00Z |
Hi All,
I am getting below error when i try to connect to database after redirect restore of the database backup.

SQL2071N An error occurred while accessing the shared library
"/data/HOMEDEPOT/db2inst2/sqllib/adsm/libtsm.a". Reason code: "2".
One of the reason of this error may be is source database is configured as archival logging on TSM. when i try to update the db cfg parameter it doesn't allow me to update configuration parameter because it is not able to connect to database.

How to resolve this error?
Thanks
Dave
Updated on 2007-09-13T08:22:07Z at 2007-09-13T08:22:07Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    17917 Posts

    Re: ERROR SQL2071N after redirect restore during connect to database

    ‏2007-09-13T08:22:07Z  

    Hi Dave,

    the explanation for the error is:

    "Ensure that you are specifying the correct library. If your
    system can run 32-bit and 64-bit binaries, ensure that you are
    instructing DB2 to load a library of the right format."

    Are you sure you have the right libraries installed (32 vs. 64-bit)? This error could also occur when you did install a FixPak, but didn't upgrade the instance. You could also try to "db2iupdt" the instance.

    Hope this helps,
    Bogdan

    > Hi All,
    > I am getting below error when i try to connect to
    > database after redirect restore of the database
    > backup.
    >
    > SQL2071N An error occurred while accessing the
    > shared library
    > "/data/HOMEDEPOT/db2inst2/sqllib/adsm/libtsm.a".
    > Reason code: "2".
    >
    >
    > One of the reason of this error may be is source
    > database is configured as archival logging on TSM.
    > when i try to update the db cfg parameter it doesn't
    > allow me to update configuration parameter because it
    > is not able to connect to database.
    >
    > How to resolve this error?
    >
    >
    > Thanks
    > Dave