Kbase P160160: Unable to start newly created target database in 10.2B, getting error message (10386).
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/18/2011 |
|
Status: Unverified
SYMPTOM(s):
Unable to start newly created target database in 10.2B, getting error message (10386).
The source and target databases must both have large files enabled. (10386)
Source database does not have large files enabled.
Target database log file has message: (9426) Large database file access has been enabled.
Largest fixed extent had 2097152 blocks.
Target database was created with the same .st file as the source.
FACT(s) (Environment):
In earlier versions of OpenEdge (ie 10.1C, 10.1B, 10.2A) a fixed extent with 2097152 blocks was not treated as being over 2 GB.
All Supported Operating Systems
OpenEdge Replication 10.2B 32-bit
OpenEdge Replication 10.2B 64-bit
CAUSE:
Large files are enabled when the extent size is equal to or greater than 2 GB.
The earlier versions of Progress were not enabling large files when the value was equal to 2 GB as they should have been, only when the value exceeded 2 GB.
This was not proper behavior.
FIX:
The Target database must be re-established and the .st file should be edited so there are no extents larger than 2087152.
There are three workarounds:
1. Workaround 1
Delete the target database.
Edit the .st file so no extents are greater than 2087152.
Restore the database and enable for replication as a target database.
2. Workaround 2
Delete the target database.
Edit the source database .st file so no fixed extents are greater than 2087152.
Re-enable replication on the source database.
This new .st file may also be used to establish the target database without issues.
3. Workaround 3
Enable large files on the source database.
proutil <dbname> -C EnableLargeFiles.