Skip to main content
Skip to search
Powered by Zoomin Software. For more details please contact
Zoomin
Home
Home
English
English
Čeština
Deutsch (Germany)
Español (Spain)
Français (France)
Italiano (Italy)
Português (Brasil)
日本語
Русский (Russia)
中文 (简体) (China)
中文 (繁體, 台灣) (Taiwan)
ar-AR
Login
Manage the OpenEdge Database
Loss of the DB files, BI files, or both
Save PDF
Save selected topic
Save selected topic and subtopics
Save all topics
Share
Share to email
Copy topic URL
Print
Table of Contents
Expand
Collapse
Database Basics
Create and Delete Databases
Ways to create an OpenEdge database
Database creation and large file support
Create a database with PROSTRCT CREATE
Create a structure description file
Extent pathnames and naming conventions
Rules for creating storage areas and extents
Extent length
Example structure description file
Example structure description file for large files
Create a database structure extent
Add schema to a void database
Create a database with the PRODB utility
PRODB maintains pathname convention
Create a database with a Data tool
Convert an OpenEdge Release 11 Database to OpenEdge Release 12
Use the Schema Mover
Convert an OpenEdge Release 10 database to OpenEdge Release 12
Database conversion utilities
Copy a database
Copy a database using PROCOPY
PROCOPY uses absolute pathnames
Delete a database
OpenEdge RDBMS Limits
Database block sizes
Maximum number of records per block
Number and size of storage areas
Recovery sizes
Table and index limits
Number and size of sequences
Maximum size of the primary recovery (BI) area
Maximum database size
Number of connections per database
Number of simultaneous transactions per database
OpenEdge database name limits
File Handles
Shared memory
Data types and values
Collation and character set information
Start Up and Shut Down
Unified Broker Framework
OpenEdge Management
OpenEdge Explorer
Manage database configurations
Use the DBMAN command-line utility
Start a server or broker
Specify international character sets
Specify the operating character set
Specify the character set name of the database log file
Network addressing using -S and -H
Start multiple brokers using the same protocol
Access a server behind a firewall
Start database brokers for TLS connections
Check the database state
Threaded Database Server Functionality Delivered on Windows NT64 and Linux64 Platforms
Initiate a Threaded Server Process
Monitor Threaded Servers and Remote Connections
Start and stop background writers and before-image manager
Start and stop an APW
Start and stop a BIW
Start and stop an AIW
Start and stop a BIM
Stop a server or broker
PROSHUT command
PROMON shut down database option
Protecting Your Data
Backup Strategies
Identify files for backup
Determine the type of backup
Full backups
Incremental backups
Online backups
Offline backups
Backups with compression
Choose backup media
Create a backup schedule
Database integrity
Database size
Time
Unscheduled backups
Back Up a Database
Use PROBKUP
Perform an online full backup with PROBKUP
UNIX full backup example
Backup Counter Increment limits using the PROBKUP Utility with Type I storage areas
Test backups
Archive backups
Perform an offline backup
Perform an online backup
Improve performance of an online backup
Use database quiet points
Back up with compression
Run a multi-threaded backup
Perform an operating system backup
Database backup examples
Incremental backup example
Full backup example
Verify a backup
CRC codes and redundancy in backup recovery
CRC codes
Error-correction blocks
Restore a database
Use the PROREST utility to restore a database
Important rules for restoring backups
Obtain storage area descriptions using PROREST
Obtain backup file descriptions using PROREST -describe utility
Run a multi-threaded restore
Database restore examples
Full backup restore example
Incremental backup restore example
Recover a Database
Introduction to recovery mechanisms
Crash recovery
Roll-forward recovery
Two-phase commit
File locations that ensure safe recovery
Develop a recovery plan
Time needed for recovery
Recovery guidelines
Sample recovery plans
Example 1: Low availability requirements
Example 2: Moderate availability requirements
Example 3: Moderate-to-high availability requirements
Example 4: high availability requirements
Sample recovery scenarios
After-imaging and roll-forward recovery commands
Recover from system failures
System crash while running RFUTIL ROLL FORWARD
System crash while running other utilities
System crash while backing up the database
System crash while database is up
Recovering from media failures
Loss of the DB files, BI files, or both
Loss of the AI file
Loss of database backup
Loss of transaction log file
Recover from a full disk
After-image area disk
Control or primary recovery area disk
BI file not on full disk
BI file on the full disk
Transaction log file disk
Truncate the BI file
Release shared memory
Recover from a lost or damaged control area
Unlock damaged databases
Dump tables from a damaged database
Force access to a damaged database
After-imaging
After-image areas and extents
Fixed-length extents
Variable-length extents
Estimate after-imaging disk space requirements
Create after-image areas
Add AI areas to an existing database
Enable after-imaging offline
Enable encrypted after-imaging offline for an encryption-enabled database
Enable unencrypted after-imaging offline for an encryption-enabled database
Enable after-imaging online
Enable encrypted after-imaging online for an encryption-enabled database
Enable unencrypted after-imaging online for an encryption-enabled database
After-image file summary
Show an after-image file summary
Manage after-imaging files
Monitor AI file status
Switch to a new AI file
Switch to the next extent in the sequence
Archive an AI file
Schedule backups
Perform the backup
Protect the backup
Extract AI blocks
Make an AI file available for reuse
AI File Management utility
Automatic extent archiving
Timed mode archiving process without OpenEdge Replication
Timed mode archiving process with OpenEdge Replication
On-demand archiving process without OpenEdge Replication
On-demand archiving process with OpenEdge Replication
Enable your database for automated AI file management
Enable an offline database for automated AI file management
Enable an online database for automated AI file management
Enable an online database for automated AI file management during backup
Additional info for enabling automated AI file management
Monitor and adjust automated AI file management
Restart the AI file management utility daemon
Archived extents
Archive log file