Home
HCL Domino Designer Basic User Guide and Reference
This guide provides information on using HCL Domino Designer and programming language reference information.
Application Management
Welcome to the Application Management section of Domino® Designer Help.
Procedure for optimizing and troubleshooting databases
Troubleshooting replication problems
The following topics suggest solutions to common problems associated with scheduled replications.
Database replicas are different sizes
Database replicas may be different sizes for the following reasons:

HCL Domino Designer Basic User Guide and Reference
This guide provides information on using HCL Domino Designer and programming language reference information.
- What's new in HCL Domino Designer 12?
  The following features are new for developers in HCL Domino® Designer 12.
- Accessibility and keyboard shortcuts
  Accessibility features assist users who have a disability, such as restricted mobility or limited vision, to use information technology content successfully.
- Application Design
  Welcome to the Application Design section of Domino® Designer Help.
- Application Management
  Welcome to the Application Management section of Domino® Designer Help.
  - Security in an application
    Domino® offers a multi-layered approach to security. Server administrators can secure databases, servers, and domains. Database designers and managers control the following:
  - Completing an application and managing design changes
    As you prepare to deploy an application, consider these finishing touches:
  - Deploying an application
    The tasks involved with application design, database design, database management, and DominoTMsystem administration may overlap, depending on the size of your organization and the structure of job responsibilities. In some organizations, an application developer may be responsible for both application and database design, while in others, a database manager may handle all database design and management tasks. In addition, database management overlaps with Domino® system administration.
  - Procedure for optimizing and troubleshooting databases
    - Properties that improve database performance
      Properly setting database properties can improve the performance of an active database. Setting database performance properties on many databases or on one, large, active database can also improve server performance. In addition, some of these property settings also help reduce the size of databases.
    - To set database properties that optimize database performance
    - Controlling database size
      Databases whose size is monitored and minimized show increased performance: database operations require less I/O and fewer CPU resources; view rebuilding and updating is quicker; and memory and disk space allocation is improved. The maximum database size is 64GB on Windows™ and UNIX™. Use the following methods to regularly monitor the size of databases and minimize database size:
    - Document archiving tool
    - Monitoring replication of a database
      If there are replicas of a database, use any of these methods to monitor replication daily.
    - Monitoring database activity
      Monitor database activity regularly. If database activity is high and users report performance problems, do any of the following:
    - Notifying users of a moved database
      After you move a database, create a new database with the same file name and path as the database before you moved it. In the new database, create a form and document that provides the following information:
    - Troubleshooting database performance
      You can reduce database performance problems by using:
    - Troubleshooting replication problems
      The following topics suggest solutions to common problems associated with scheduled replications.
      - A database replica does not contain all the documents it should
        If none of the following explanations apply, clear the replication history by using the File - Replication - History dialog box in the Notes® client.
      - A database replica is not receiving design changes
        To receive design changes from a source server, the database replica on the destination server must give the source server at least Designer access and the source server replica must give the destination server at least Reader access.
      - Changes to the database title do not replicate
        If the replication setting "Do not send changes in database title & catalog info to other replicas" is selected on the source server replica, the title won't replicate. Deselect this setting to replicate a database title. To view this setting, choose File - Replication - Settings and click the "Send" tab in the Notes® client.
      - Database replicas are different sizes
        Database replicas may be different sizes for the following reasons:
      - The database stops replicating
        If a user changes a local or remote server database replica's ACL when the "Enforce a consistent access control list across all replicas of this database" option is selected, the database stops replicating. This option is found on the Advanced panel of the Access Control List dialog box. The message in the log file is:
      - The database replica has not received ACL changes
        To receive ACL changes from a source server, the database replica on the destination server must give the source server Manager access and the source server must give the destination server at least Reader access.
      - The new replica contains the ACL of the source server but you did not copy the ACL
        A replica stub is an empty replica that has not yet been populated with documents. When you choose File - Replication - New Replica, Notes® creates a replica stub and populates it with documents, either immediately or at the next scheduled replication, depending on the option you select.
      - You see the message "Database is not fully initialized yet"
      - Deletions are not replicating
      - Unexpected deletions occur in a replica
        Check these replication settings by choosing File - Replication - Settings in the Notes® client:
      - Deleted documents reappear
- Domino® Query Language
  Domino® Query Language (DQL) is a facility running on a Domino server that provides a terse, shorthand syntax for finding documents. It supports a wide variety and complexity of search terms. It leverages existing design elements, avoiding the need to write detailed code to access them. DQL consolidates all methods in Domino for searching document contents.
- Composite Applications - Design and Management
  Composite applications are a key element in a service-oriented architecture (SOA) and contextual collaboration strategy. The ability to create and edit composite applications lets you easily integrate different types of components and technologies.
- DB2® Access views
  Domino® Designer includes two types of design elements to assist you in managing data contained in DB2® enabled Notes® databases:
- Programming Overview and User Interface
  This section contains general guidelines and examples that show where to use Java, LotusScript, and the formula language.
- Formula Language
  This section documents the formula language.
- LotusScript® Language
  Welcome to the LotusScript® Language section of Domino® Designer Help.
- LotusScript/COM/OLE Classes
- Java/CORBA Classes
  This section documents the Java/CORBA classes.
- Connectors
  Connectors provide native access to a wide variety of DBMS products, ODBC, the platform File system, Enterprise Resource Planning systems, and Transaction Processing systems.
- Javadoc™ for Domino® Designer related APIs
  As part of providing additional Java™ reference documentation, Domino® Designer ships with a help plugin that contains Javadoc™ for additional Domino Designer related APIs.

Database replicas are different sizes

Database replicas may be different sizes for the following reasons:

Replication settings

Some replication settings cause one replica to receive only a subset of documents and features from another replica.

Access Control List

The ACL prevents a replica from receiving all documents or design elements from a source server replica.

Read ACL or Reader Names fields

A destination server isn't included in a Read ACL or Reader Names field and therefore doesn't receive all documents from a source server replica.

View indexes

A view is used in one replica but not in another, and the replica containing the unused view is smaller because no index is built for the unused view.

Private agents or personal views or folders

If these features are used on one replica, but not on another, there can be a size disparity between the replicas.

Deletions are not replicated

Check these replication settings by choosing File - Replication - Settings in the Notes® client:

On the Advanced panel, make sure that the Deletions option under "Replicate incoming" is not selected.
On the Send panel, make sure that the "Do not send deletions made in this replica to other replicas" option is selected.

Unused space

One replica has been compacted while another has not been compacted.