New answers tagged db2
This was the first search result for me: FORCE APPLICATION command Forces local or remote users or applications off the system to allow for maintenance on a server. Source: IBM Knowledge Center. You can start with reading the above manual page for more details.
The db cfg parameters that affect how backups is retained is: NUM_DB_BACKUPS REC_HIS_RETENTN You can find a description of these at for example: https://www.ibm.com/support/knowledgecenter/SSEPGG_9.8.0/kc_gen/plugin-root-config-gen2.html I don't use datastudio myself, so perhaps there is a dedicated function in there, but I guess you can always use the ...
The defect with only the first character of the column name being returned is described in IBM APAR SE63700: http://www-912.ibm.com/n_dir/nas4apar.NSF/b6c9b771e38b5ea2862564c00079d110/0f43bb0435716de586257f340041ed7a?OpenDocument The fix should be integrated into the new version of the IBM Access Client Solutions Application Package for Linux, due mid-July ...
There is an API called db2ReadLog() that you can use to read transaction logs and collect information about deleted records. IBM also sells a product called Recovery Expert that will help you do this and generate undo SQL statements.
Database or tablespace recovery is the only* way to go back in time and find deleted records if you haven't planned for this. To minimize the impact on the production environment you can always perform a restore on a different machine, export the records and import them in production. That does not require any downtime. HADR with delayed replay, possibly in ...
No, it's not possible to specify a default location. The best way to do this would be to write a shell script (which specifies your location of choice) to handle your backups. You can have DB2 remove old backups (using the AUTO_DEL_REC_OBJ database configuration parameter with proper values for NUM_DB_BACKUPS and REC_HIS_RETENTN), but that will only occur ...
It is Java version 1.8.0. General availability date of Db2 LUW 11.1 is today by the way....
Yes, Ian is correct here. I am sure your issue is resolve now. Also, archive logs can still exist in Active log path if we set LOGARCHMETH1 to LOGRETAIN correctly . Details at Information Center can give better overview .Hope it helps !
Firstly, the expression values current_date - 1 would only be valid if Oracle compatibility mode were in effect -- it mimics the Oracle's datetime arithmetic where the default interval is expressed in (potentially fractional) days. I think that regardless of Oracle compatibility, the range bounds should be comparable as integers, and comparing DATE values ...
You can start by creating the database without using AUTOCONFIGURE. Once it is created use AUTOCONFIGURE with the option APPLY NONE. It will show you what DB2 thinks are better settings. Many DBAs then use the output of APPLY NONE as input to manually setting the values using update db cfg, it is a common approach.
Top 50 recent answers are included