Error Occurred While Accessing Object Db2rhist Asc
is corrupted. SQL2048N; Backup ; recovery history file Technote (troubleshooting) Problem(Abstract) DB2 Backup fails with SQL2048N RC 4 when the recovery history file is corrupted Symptom Following errors will be noticed in the db2diag.log about DB2 Backup failure due to damaged history file: 2014-06-21-00.32.19.304000-420 I85598107H614 LEVEL: Error PID : 2580 TID : 6948 PROC : db2syscs.exe INSTANCE: DB2 NODE : 000 DB : SAMPLE APPHDL : 0-6998 APPID: XXXX AUTHID : TEST EDUID : 6948 EDUNAME: db2bm.4380.0 (SAMPLE) FUNCTION: DB2 UDB, database utilities, sqluhVerifyHistoryFiles, probe:254 MESSAGE : SQL2161N A damaged recovery history file could not be fixed. The specified action failed. DATA #1 : String, 48 bytes Error encountered in verifying the history file. 2014-06-21-00.32.19.304000-420 E85598723H640 LEVEL: Severe PID : 2580 TID : 6948 PROC : db2syscs.exe INSTANCE: DB2 NODE : 000 DB : SAMPLE APPHDL : 0-6998 APPID: XXXX AUTHID : TEST EDUID : 6948 EDUNAME: db2bm.4380.0 (SAMPLE) FUNCTION: DB2 UDB, database utilities, sqlubProcessHistoryFile, probe:484 DATA #1 : Sqlcode, PD_TYPE_SQLCODE, 4 bytes -2048 DATA #2 : Hexdump, 21 bytes 0x39611714 : 00F8 FFFF 6462 3272 6869 7374 2E61 7363 ....db2rhist.asc 0x39611724 : 0004 0000 00 ..... 2014-06-21-00.32.19.304000-420 E85599365H961 LEVEL: Severe PID : 2580 TID : 6948 PROC : db2syscs.exe INSTANCE: DB2 NODE : 000 DB : SAMPLE APPHDL : 0-6998 APPID: XXXX AUTHID : TEST EDUID : 6948 EDUNAME: db2bm.4380.0 (SAMPLE) FUNCTION: DB2 UDB, database utilities, sqlubProcessHistoryFile,
Technology and Trends Enterprise Architecture and EAI ERP Hardware IT Management and Strategy Java Knowledge Management Linux Networking Oracle PeopleSoft Project and Portfolio Management SAP SCM Security Siebel Storage UNIX Visual Basic Web Design and Development Windows < Back CHOOSE A DISCUSSION GROUP Research Directory TOPICS Database Hardware Networking SAP Security Web Design MEMBERS Paul_Pedant DACREE MarkDeVries Inside-ERP MacProTX VoIP_News Inside-CRM I_am_the_dragon maxwellarnold Michael Meyers-Jouan TerryCurran Chris_Day Andrew.S.Baker Ramnath.Awate JoeTorre bracke Locutus Dennis Stevenson Craig Borysowich DukeGanote Richard http://www-01.ibm.com/support/docview.wss?uid=swg21677560 PCMag mircea_luca Nikki Klein iudithm AbhaiTripathi knowscognosdoi Clinton Jones Iqbalyk bluesguyAZ59 COMPANIES Thawte Oracle CloudLock Epicor Software ... View All Topics View All Members View All Companies Toolbox for IT Topics Database Groups Ask a New Question DB2 LUW The DB2 LUW (Linux, Unix, Windows) group is for the discussion of technical issues related to the installation, http://database.ittoolbox.com/groups/technical-functional/db2-l/sql2048n-an-error-occurred-while-accessing-object-32-3017517 configuration, or daily administration of IBM DB2 LUW databases. Home | Invite Peers | More Database Groups Your account is ready. You're now being signed in. Solve problems - It's Free Create your account in seconds E-mail address is taken If this is your account,sign in here Email address Username Between 5 and 30 characters. No spaces please The Profile Name is already in use Password Notify me of new activity in this group: Real Time Daily Never Keep me informed of the latest: White Papers Newsletter Jobs By clicking "Join Now", you agree to Toolbox for Technology terms of use, and have read and understand our privacy policy. SQL2048N An error occurred while accessing object "32 ramat asked Sep 25, 2009 | Replies (1) Hi, We are unable to thke the db2 database backup.we got the error 25.09.2009 10:00:15 Backup_Dev: SQL Message: SQL2048N An error occurred while accessing object "32 I have checke the all the tablespace status db2 list tablespaces.The all the tablespace in normal state.But the table
code: "4". I have never had this problem before. What causes it and how do? Thank you, Barbara Top db2rhist.asc error by eric schat » Thu, 11 Jan 2001 15:12:17 hi barbara, we had this error a couple of http://www.verycomputer.com/164_10e27f919ac08c71_1.htm times on our 1000+ db2 v6 installations. don't know what the cause is. to solve the problem we delete the corrupt file and move a empty db2rhist.asc (fom a other, newly created, db) to the folder, usually c:\Db2\Node0000\Sql0000x (where sql0000x is the folder of the db concerned). hope this helps eric Barbara schrieb: Quote:> Hi, > my backups are falling over with the following error: > SQL2048N An error occurred while accessing object "db2rhist.asc". > Reason error occurred code: "4". > I have never had this problem before. What causes it and how do? > Thank you, > Barbara Top db2rhist.asc error by Gert van der Kooi » Fri, 12 Jan 2001 03:34:07 says... Quote:> hi barbara, > we had this error a couple of times on our 1000+ db2 v6 installations. > don't know what the cause is. > to solve the problem we delete the corrupt file and move a error occurred while empty > db2rhist.asc (fom a other, newly created, db) > to the folder, usually c:\Db2\Node0000\Sql0000x (where sql0000x is the > folder of the db concerned). > hope this helps > eric > Barbara schrieb: > > Hi, > > my backups are falling over with the following error: > > SQL2048N An error occurred while accessing object "db2rhist.asc". > > Reason code: "4". > > I have never had this problem before. What causes it and how do? > > Thank you, > > Barbara Hi, You can also restore the history file from the last backup with the 'restore database... history file only' option if you need the information it contains (or for any other reason :) Top 1. Corruption of db2rhist.asc file From time to time we get the following message when trying to perform backup of a database: backup database XDJO00 to /data2/DB2BACKUP SQL2048N An error occurred while accessing object "db2rhist.asc". Reason code: "4". Then we have to rename the db2rhist.asc file and resubmit the backup command a couple of times, and then everything works fine for a couple of weeks until the same happens again. What is curious is that we have many DB2 databases, both on NT, AIX and Solaris. BUT this situation we have only experienced on Solaris. Is there a known bug with DB2 and Solaris ( We run