SQL2048N occured when backup database

dnl...@my-deja.com

unread,

Oct 25, 2000, 3:00:00 AM10/25/00

to

Hello,
On NT server,when I use the following command to backup database:
"db2 backup database testdb"
I got an error message which indicates "SQL2048N Access
object 'DB2RHIST.ASC' failure. Reason code='4'"
What is the problem?
Thanks a lot.

PS.
1. Only this database encounters this problem.
The other database can be backup successfully.

Sent via Deja.com http://www.deja.com/
Before you buy.

Mitch

unread,

Oct 25, 2000, 3:00:00 AM10/25/00

to

Which version of UDB are you running - I believe that there was a fix
for this in fp3 for 6.1

Richard “Mitch” Mitchell
Senior Database Administrator
IBM Certified Solutions Expert - DB2 UDB v6.1 Database Administration
for UNIX, Windows and OS/2

Fracta Networks

In article <8t6dqi$as$1...@nnrp1.deja.com>,

--
- Mitch

Larry Menard

unread,

Oct 25, 2000, 3:00:00 AM10/25/00

to

If you do "db2 ? sql2048" from a command line, it tells you that in
your case it sounds like your database needs to be recovered before it
can be backed up.

dnl...@my-deja.com wrote:

> Hello,
> On NT server,when I use the following command to backup database:
> "db2 backup database testdb"
> I got an error message which indicates "SQL2048N Access
> object 'DB2RHIST.ASC' failure. Reason code='4'"
> What is the problem?
> Thanks a lot.
>
> PS.
> 1. Only this database encounters this problem.
> The other database can be backup successfully.
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.

--
Larry Menard
IBM Workstation Database (DB2) Performance Team
Defender of Geese and of all things Natural

Mitch

unread,

Oct 26, 2000, 2:31:52 AM10/26/00

to

Larry

Sorry to disagree with you on this - I went through this loop many
months ago, when running v6.1 on AIX at ibooks.com. Your labs did
confirm to me under a PMR that I raised that it was a corrupt history
file, that, as a work around, could be deleted (db2jobsm.* and
db2jobht.* files).

I believe the fix was related to APAR JR14171 - but I could be wrong on
this - my memory aint "that" good when it comes down to actual APARS/

Richard "Mitch" Mitchell
Senior Database Administrator
IBM Certified Solutions Expert - DB2 UDB v6.1 Database Administration
for UNIX, Windows and OS/2

Fracta Networks

In article <39F6EB9E...@ca.ibm.com>,

--
- Mitch

Larry Menard

unread,

Oct 26, 2000, 8:16:27 AM10/26/00

to

Mitch, please feel free to keep me honest. ;-)

Thanks for the info. (BTW, I don't consider it a "disagreement" but an
"augmentation"... without definitely knowing that the history file is bad, I
still might be right. ;-)

Mitch

unread,

Oct 26, 2000, 9:53:39 AM10/26/00

to

So long as we are still friends :-)

Richard “Mitch” Mitchell
Senior Database Administrator
IBM Certified Solutions Expert - DB2 UDB v6.1 Database Administration
for UNIX, Windows and OS/2

Fracta Networks

In article <39F8209B...@ca.ibm.com>,

alicej...@gmail.com

unread,

Feb 1, 2017, 5:39:37 AM2/1/17

to

There is a need to create a VHD from the Disk Management snap-in or you the command line and to do so, you can follow the below steps to fix this issue:
• Right-click Disk Management and the simply click Create VHD, follow the instructions that appear on the screen.
• Now right-click the new disk and then simply click Initialize Disk and then click OK.
• After the above steps, there is a need to right-click the new disk and then click New Simple Volume and then follow the instructions that appear on the screen.
Or you can also log on to the below link where you will get to know everything about DB2 database and how to fix any kind of error if you ever come across:
http://db2.filerepairtool.net