If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > Adabas > Nat3049

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 01-13-05, 20:55
linux_mr linux_mr is offline
Registered User
 
Join Date: Feb 2004
Location: Mex, Mex City
Posts: 6
Nat3049

Somebody can help me what does nat3049 mean?
And how can I fix the problem...

Thanks in advance
Reply With Quote
  #2 (permalink)  
Old 01-17-05, 10:35
urquel urquel is offline
Registered User
 
Join Date: Aug 2004
Posts: 330
Here is what the manual says.

***************** Text Below Copyright (c) 2005, SOFTWARE AG *****************
NAT3049 : Compressed record too long for internal buffer. DB/FNR :1:/:2:

Text Compressed record too long for internal buffer.

Expl. For Adabas Version 4, the compressed record must not exceed 3000 bytes.
For Adabas Version 5, the compressed record must not exceed the block
size of Data Storage.

Actn. Contact your database administrator.
****************************** BOTTOM OF DATA ********************************
Reply With Quote
  #3 (permalink)  
Old 01-20-05, 11:52
linux_mr linux_mr is offline
Registered User
 
Join Date: Feb 2004
Location: Mex, Mex City
Posts: 6
Nat3049

Thanks Urquel,
I contacted to my DBA and He tell me: "the problem is your file, you have a lot of periodic fields... you have to fix it"

I'm confused, how can the DBA help me?

Thanks...
Reply With Quote
  #4 (permalink)  
Old 01-31-05, 14:46
ad60 ad60 is offline
Registered User
 
Join Date: Aug 2004
Posts: 15
It is possible, but you should consider removing PEs/MUs

The problem that you are experiencing is the compressed record doesn't fit into the data storage block size. It has been many years since I worked with ADABAS, but there is a utility that the DBA can use to increase the blocksize of data storage, but when this is done, this can potentially affect database performance either positively or negatively. It would take benchmarking to determine what effect the larger blocksize would have. This is why they have recommended you remove some of your PEs or MUs. When you remove them, the record will be reduced in size and most likely fit into the block. Or if you can't remove the PEs or MUs, they can increase the blocksize and your record will fit in the block, but all other users of the database will also be using this larger blocksize, and they may not like this happening just for your application. Hope this helps. Jim D.
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On