Discussions
Categories
- 197K All Categories
- 2.5K Data
- 546 Big Data Appliance
- 1.9K Data Science
- 450.8K Databases
- 221.9K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 552 MySQL Community Space
- 479 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.1K ORDS, SODA & JSON in the Database
- 556 SQLcl
- 4K SQL Developer Data Modeler
- 187.2K SQL & PL/SQL
- 21.4K SQL Developer
- 296.4K Development
- 17 Developer Projects
- 139 Programming Languages
- 293.1K Development Tools
- 111 DevOps
- 3.1K QA/Testing
- 646.1K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 161 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.2K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 19 Java Essentials
- 162 Java 8 Questions
- 86K Java Programming
- 81 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 205 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 475 LiveLabs
- 39 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 175 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 233 Portuguese
log file initialization after db_dump/db_load

61890
Member Posts: 1
Greetings,
I have the need to db_dump/db_load a large customer database in their production environment. According to the documentation on "Log File Limits", after running db_dump/db_load, I should remove all log files and restart my application. The problem I have is my application has a check to insure that at least 1 log file exists. I cannot make changes to the application in the customers environment and cannot get a release into their environment in time to fix this issue. I have experimented with "touch log.0000000001" and this appears to work. My application starts normally and after some period of activity I can see, via db_printlog, normal activity in the log file. Is this an acceptable way to "initialize" the log file?
I am using Berkeley DB version 4.1.25 running on Solaris 9.
Thanks,
Nick
I have the need to db_dump/db_load a large customer database in their production environment. According to the documentation on "Log File Limits", after running db_dump/db_load, I should remove all log files and restart my application. The problem I have is my application has a check to insure that at least 1 log file exists. I cannot make changes to the application in the customers environment and cannot get a release into their environment in time to fix this issue. I have experimented with "touch log.0000000001" and this appears to work. My application starts normally and after some period of activity I can see, via db_printlog, normal activity in the log file. Is this an acceptable way to "initialize" the log file?
I am using Berkeley DB version 4.1.25 running on Solaris 9.
Thanks,
Nick
Comments
-
The code will do the right thing if the first log file is empty. That is it will write a proper log file header and go on from there. Since the system must be able to recovery even if we fail just after creating a log file, it seems like this should continue to work.
Michael Ubell
Oracle
This discussion has been closed.