Db2 Sqlcode 2071 Error
Contents |
on DB2 for Linux, UNIX, and WindowsWhere is this place located?All Places SAP on DB2 for Linux, UNIX, and Windows 8 Replies Latest reply: https://scn.sap.com/thread/1557963 Dec 16, 2009 2:32 PM by Olaf Balzer Tweet Not able to connect to DB due to SQL2071N error Joean Yun Dec 15, 2009 10:34 AM Currently http://support.bull.com/ols/product/storage/backup/calypso/v10/article?p=products/db2/backup_troubleshooting.htm Being Moderated Hi, We restored an SAP BI 7.0 system running on AIX 5.3 and DB2 9.1.0.4 FixPack 4 64-bit system using UNIX file level restoration db2 sql on an existing AIX server from a backup media. After restoration, I changed the hostnames and file permissions and managed to be able to issue "db2start" and "db2stop" successfully for the restored database. However I am currently facing a problem connecting to the database, eventhough I am able to issue the command db2 sql error u201Cdb2startu201D successfully to start the Database Manager, whenever I try to execute u201Cdb2 connect to DBXu201D, I get the following error: SQL2071N An error occurred while accessing the shared library "/usr/tivoli/tsm/tdp_r3/db264/libtdpdb264.a". Reason code: "2". Iu2019ve done some Googling and some people have had similar issue (http://www.dbforums.com/db2/1638554-sql1651n-during-redirect-restore.html) , and they recommended using the command u201Cdb2 update db cfg for DBX using LOGARCHMETH1 offu201D to change the value of LOGARCHMETH1 to u2018OFFu2019. I tried updating the DB CFG parameter value of LOGARCHMETH1 to u2018OFFu2019, but for some reason eventhough the system replied that the update was successful, everytime I retrieve the value of LOGARCHMETH1 again (through "db2 get db cfg for DBX | grep -i log") itu2019s still showing u201CVENDOR:/usr/tivoli/tsm/tdp_r3/db264/libtdpdb264.au201D, even after I tried u201Cdb2stopu201D and u201Cdb2startu201D again. From this SDN forum thread ( Re: SQL1651N - during Redirect Restore), they recommended to use the program brdb6brt and version recovery method using "without rolling
DB20006: Log only backup fails after a DB2 upgrade from 32-bit to 64-bit DB20007: Log backup fails DB20008: Backup jobs fail with one or more errors DB20009: Database is in the BACKUP_PENDING state DB20010: DB20010: A DB2 Backup Fails with Error Code 19:1334 DB20012: Target Database Cannot Access Latest Log Chain During a Cross-Machine Restore Vendor Code Troubleshooting Return Code 1: Troubleshooting backup failures after a new DB2 Agent install Return Code 6 Return Code 11 Return Code 18 Return Code 30 Effective Troubleshooting Backup DB20006: Log only backup fails after a DB2 upgrade from 32-bit to 64-bit Issue Log Only Backups fail after a DB2 upgrade from 32-bit to 64-bit. Symptom Log Only Backups fail after a DB2 upgrade from 32-bit to 64-bit. Resolution The sqllib/lib library is not linked to the correct 64-bit library. Link the sqllib/lib library to a correct lib64 for 64bit DB2 . DB20007: Log backup fails Issue If you create the directories, subdirectories or files under Calypso Log Archive/Retrieve/Audit Error paths, the log backups may fail. Symptom Log Backups fail. In the example, the "db2inst1/DB5290/NODE0000/C0000000//lost+found" directory exists under "/home/db2inst1/db2Archive" path. Hence, the log backups failed. The following error message is displayed in ClDb2Agent.log: 11443 40476940 11/12 16:20:52 192887 Db2UserExit::OpenLogFile() - 1: fopen(/home/db2inst1/db2Archive/db2inst1/DB5290/NODE0000/C0000000//lost+found) 11443 40476940 11/12 16:20:52 192887 Db2Util::Db2StringToULong() - 0: ERROR: db2str.size()=10 < i 11443 40476940 11/12 16:20:52 192887 Db2UserExit::PopulateLogFileHeader() - 0: Util.Db2StringToULong(lost+found) failed. 11443 40476940 11/12 16:20:52 192887 Db2UserExit::BackupLogsFromPath() - 0: PopulateLogFileHeader() failed. 11443 40476940 11/12 16:20:52 192887 Db2UserExit::BackupFromAD() - 0: BackupLogsFromPath failed. 11443 40476940 11/12 16:20:52 192887 Db2UserExit::Backup() - 0: BackupFromAD() failed: . 11443 40476940 11/12 16:20:52 192887 ClDb2Agent::LogsBackup() - 0: Before delete ue...: ue->Backup() failed: errorHelpString=<>. 11443 40476940 11/12 16:20:52 192887 ClDb2Agent::LogsBackup() - 1: SetPendingCauseAndEvent:DB2_LOGBACKUP_FAILED 11443 40476940 11/12 16:20:52 192887 Db2JobObject::Db2JobObject::SetPendingCauseAndEvent() - 1: Setting the pending cause successful. Resolution If you have created any directories, subdirectories or files under Calypso Log Archive/Retrieve/Audit Error paths, move them to anoth