LO64981: "FIELD IS TOO LARGE (32K) OR VIEW'S COLUMN & SELECTION FORMULAS ARE TOO LARGE" ERROR COPYING DATABASE

APAR status

• Closed as fixed if next.

Error description

• When you attempt to copy an existing database the copy fails
  with the error "Field is too large (32K) or View's column &
  selection formulas are too large". If you take a copy of the
  database design only without documents then the error is not
  raised. This confirms there is no issue with the design rather
  with the documents.
  

Local fix

• In one case the issue was corrected by executing the following
  code to scan through each field in each document in the problem
  database:
  
  Sub Initialize
   Dim nsn As New NotesSession
   Dim ndb As NotesDatabase
   Dim ndc As NotesDocumentCollection
   Dim ndo As NotesDocument
   Dim nit As NotesItem
   Dim count As Integer
  
   On Error GoTo errHandler
  
   Set ndb =
  nsn.GetDatabase("","[DatabasePathAndName]")
   If Not ndb.IsOpen() Then
    Call ndb.Open("","")
   End If
  
   Set ndc = ndb.AllDocuments
   Set ndo = ndc.getFirstDocument
  
   count=1
   Do While Not (ndo Is Nothing)
  
    Print Str(count) & ": " & ndo.UniversalID
  
    ForAll it In ndo.Items
     Set nit = it
     'Print "Doc: " & ndo.UniversalID & ", field: " & nit.Name
    End ForAll
  nextDoc:
    count = count + 1
    Set ndo = ndc.GetNextDocument(ndo)
   Loop
   Exit sub
  errHandler:
  
   MsgBox "Doc: " & ndo.UniversalID
   'Uncomment the following line to delete the problem document
  
   'Call ndo.Removepermanently(True)
  
   Resume nextDoc
  End Sub
  
  
  This code identified a problem document where all fields
  appeared blank and the document had no Universal ID. After
  removing this document from the database the issue was resolved.
  
  In the example code above the "[DatabasePathAndName]" should be
  replaced with the path and database name for the problem
  database.
  
  Uncommenting the code "Call ndo.Removepermanently(True)" will
  result in the document being permanently removed from the
  database. The code should first be tested without removing the
  document in this way as you may be seeing a different issue.
  
  Note: An OS copy of the database should be taken before carrying
  out any of the steps suggested above.
  

Problem summary

• This APAR is closed as FIN. We have deferred the fix to a
   future release.
  

Problem conclusion

Temporary fix

Comments

• This APAR is associated with SPR# DPOL8MYLRP.
  This APAR is closed as FIN. We have deferred the fix to a
   future release.
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

• R802 PSN

     UP